Check freshness before volume
A tank reading should have a timestamp and sensor context. If it is old or absent, treat current supply as unknown instead of reporting zero or a reassuring level.
Operator guide
A daily water operations checklist for property managers
A practical sequence for reviewing water storage, customer balances and maintenance without getting lost in dashboard charts.
Property managersWater operationsDaily checklist
How it works
What you can expect
Start with three questions: what water is available, what needs attention, and who owns the next action? In the WaterPesa preview, those questions lead to the source-to-customer system, customer payment states and open maintenance reports. The sample is a way to learn the workflow before connecting a real property.
Outcomes
Why this matters
Follow up on the right balance
A pending mobile-money payment is not confirmed collection, but sending another payment request immediately can confuse the customer. Resolve the state first.
Assign the next action
An open issue needs a responsible team and a clear next check. Recording work done is separate from proving the water service has recovered.
Capabilities
What the workflow includes
First: water path
Inspect the source, pump, tank and inlet before looking at individual customer meters.
Next: customer exceptions
Filter overdue balances and inspect disputes or pending payments separately.
Then: maintenance
Review critical issues, work in progress and costs that still need approval.
Finally: reporting
Compare records in the same currency and period. Collections are not the same as profit.
Your next step
FAQ
Frequently asked questions
What is available in the demo?
A source-to-customer example, dated tank reading, sample customer history, reminder drafting, maintenance reports, invoice states and reporting preferences.
What should be checked before a live pilot?
Asset identity, sensor compatibility, organization access, data freshness, local protections and the team’s response process.
Keep exploring