Start with evidence
Use the correct account, connection, meter, tariff and time period before diagnosing a water or billing issue.
Migration
How to run water-utility software in parallel before cutover
How to compare bills, payments, reads and operational state between an incumbent platform and WaterPesa without double-writing production state.
Parallel runCutoverReconciliation
Answer first
What this means in practice
WaterPesa answer
Use the same bounded population and time window, document cutoffs and tolerances, and treat every critical mismatch as a cutover blocker until reconciled.
Outcomes
Why this matters
Separate facts from estimates
Label actual, estimated, inferred and missing data so the reader can see what is known.
End with an action
Translate the explanation into the next customer, property or utility step.
Capabilities
What the workflow includes
Record lineage
WaterPesa keeps source IDs, timestamps and calculation versions attached to operational records.
Plain-language explanation
The interface turns raw readings and billing events into an understandable timeline.
Structured case workflow
When something cannot be resolved from data alone, the same evidence becomes a case or work order.
Exportable history
Authorized users can retain or export the relevant record without relying on screenshots.
“For every cubic metre entering the system: where did it go, what happened commercially, what action was taken, and what measurable result followed?”WaterPesa product invariant · derived from the connected Notion product specification
FAQ
Questions this page should answer
What is the first thing to check for How to run water-utility software in parallel before cutover?
Confirm the account/connection, meter identity, relevant date range and whether the source reading is actual or estimated.
Can WaterPesa confirm every issue automatically?
No. The product can surface evidence and anomalies, but field verification or provider review may still be required.
Why does data lineage matter?
It lets customers and operators explain how a result was produced and prevents later system or meter changes from rewriting the past.
Keep exploring