01 / THE BLUEPRINT
The problem to investigate
A community member may report a broken water point without knowing whether anyone received the request. First ask who owns the asset, who can repair it and how urgent incidents are handled. A public reporting tool cannot substitute for an actual maintenance service.
02 / THE BLUEPRINT
A possible solution
Create a ticket with a non-sensitive asset identifier, a structured fault report and a named operational owner. Show acknowledgement, investigation and closure as distinct states. Verify repair completion with the operator and an agreed follow-up process rather than assuming a closed ticket means safe water.
03 / THE BLUEPRINT
Start without an app
A public noticeboard and a staffed phone number may solve the feedback gap. Work with the existing water committee or operator rather than creating a competing reporting channel. Agree responsibilities and response expectations before inviting public reports.
04 / THE BLUEPRINT
Technology that could help
A low-bandwidth form, an offline-capable staff interface and permissioned SMS updates could help. Maps are optional and should avoid sensitive household locations. Keep an audit trail of status changes, but do not publish reporter contact details.
05 / THE BLUEPRINT
Your first experiment
- Identify a willing operator and map its current reporting and repair process.
- Use fictional incidents to test handovers, duplicate reports and out-of-hours escalation.
- Agree what information is public and how reporters receive an update.
- Run a limited, supervised trial only when someone is accountable for action and closure checks.
06 / THE BLUEPRINT
People, resources and cost drivers
You need an operator, a committee contact and maintenance capacity. Costs include communications, staff coordination, verification visits and technical support. Spare parts, skilled labour and water-quality assessment remain operational responsibilities outside the app.
07 / THE BLUEPRINT
What to validate — and when to stop
Check whether tickets reach a person with authority and whether public status reflects reality. Stop expansion if unresolved reports simply accumulate or the tool diverts urgent issues from working channels. Do not promise repair deadlines without an operational agreement.
08 / HYPOTHESIS TO TEST
Potential impact and how to measure it
The hypothesis is fewer lost reports and clearer feedback. Track acknowledgement time, unresolved handovers, duplicate requests and independently checked closures. A recorded repair is not proof of water safety; appropriate technical testing is a separate requirement.
09 / THE BLUEPRINT
Risks and safeguards
Publishing exact locations or reporter identities can create privacy or safety concerns. Provide a private reporting path and a phone alternative. Do not issue water-safety advice, certify repairs or encourage unqualified people to work on infrastructure.
10 / THE BLUEPRINT
Who might pay or maintain it
A responsible service operator or transparent community programme could fund coordination. Make ongoing ownership explicit and preserve exports for a change of operator. Avoid creating an unfunded public expectation that the software team itself will repair infrastructure.