Preserve history
Keep the long-lived water/accountability record when hardware or upstream systems change.
Regulatory
WARIS / WASREB reporting
Map canonical WaterPesa data to versioned regulator fields, validate completeness and retain frozen source snapshots and submission evidence.
RegulatoryEvidenceAdaptersKenya-ready
Answer first
What this means in practice
WaterPesa answer
Map canonical WaterPesa data to versioned regulator fields, validate completeness and retain frozen source snapshots and submission evidence.
Outcomes
Why this matters
Operate from evidence
Show source quality, exceptions and ownership instead of hiding uncertainty.
Measure outcomes
Connect action to a verifiable water, service or financial result.
Capabilities
What the workflow includes
Canonical records
Customer, service point, meter installation, water, bill, payment and work records remain distinct.
Adapter boundary
Vendor-specific payloads stay behind normalized contracts.
Audit & approvals
Sensitive actions keep actor, reason, approval and evidence.
Export & portability
Raw and normalized history remain exportable.
“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
Does this require replacing existing systems?
No. WaterPesa is designed to integrate first and replace only when the deployment case supports it.
Are demo metrics guaranteed outcomes?
No. Production claims require a versioned baseline, source evidence and a defined verification method.
How is vendor lock-in avoided?
The canonical domain model and history are independent of meter, payment, GIS and billing adapters.
Keep exploring