
Could community reports improve rural water service monitoring?

Updated: 4 days ago
Rural water service monitoring is the work of knowing, week by week, whether each water point is delivering water people can use, and fixing it fast when it is not. The weak link is often the first one: a hand pump breaks and nobody who can repair it finds out for days or weeks. This post asks whether the people who use a water point, and the committees that look after it, could close that gap by reporting outages from a phone, using tools that already exist in the CitizenClimate app. Our borehole water monitoring walkthrough shows a fictional version of the idea with sensors; here we stay with what people can report themselves.
Concept note: Parts of this article describe an idea we are exploring, a water point status board. It is not available in the CitizenClimate app today, and there is no release date or price. Everything outside the "Concept" section describes features the app has now.
Why rural water service monitoring keeps missing breakdowns
The scale of the problem is well documented. According to the WHO and UNICEF Joint Monitoring Programme release of 26 August 2025, 2.1 billion people, 1 in 4 globally, "still lack access to safely managed drinking water", including 106 million who drink directly from untreated surface sources. The same release says safely managed coverage in rural areas rose from 50 per cent to 60 per cent between 2015 and 2024, and that rural areas still lag behind.
Access is also about whether a source works on the day. The JMP drinking water ladder counts a source as "basic" only when collection takes no more than 30 minutes for a round trip including queuing. When the nearest pump fails and people walk to the next one, a household can drop down that ladder overnight, and no annual survey will show it.
Breakdowns are common. A review of handpump data from 47 countries in sub-Saharan Africa and the Asia-Pacific region by Foster et al., published in the International Journal of Water Resources Development, found that "approximately one in four handpumps in sub-Saharan Africa are non-functional at any point in time".

What shortens a breakdown is information reaching someone who is paid and equipped to act. In Kenya, a maintenance company receiving data "from over 300 community handpumps serving over 50,000 rural Kenyans" reduced "the downtime of broken pumps from over 30 days to less than 3 days", according to REACH at the University of Oxford. In that case the data came from sensors in the pump handles. The lesson that carries over is the pairing: a signal that something is wrong, and a service with the job of responding.
The sector has worked hard on what to measure. The World Bank's Rural Water Metrics Global Framework proposes common indicators for rural water supply, and the Water Point Data Exchange pools water point records from many sources. Both depend on someone visiting or reporting on each water point regularly. Between those visits, the people collecting water are often the first to know.
What a useful outage report needs to hold
Before looking at any app, it helps to list what a district water officer or service provider would need from a report about a water point. Each item answers a different question.
Question | What the record would hold | Who uses it |
|---|---|---|
Which water point? | A GPS point, a photo of the source and a name or code | Mechanic, district office |
What is wrong? | A short choice: no water, low flow, broken part, long queue, water looks or smells wrong | Mechanic, service provider |
Since when? | The time the report was made, kept even if it was sent hours later | Service provider, funder |
Who else is affected? | Other reports on the same point, or votes on the same complaint | Service provider |
Was it fixed? | A status the reporter can see, and a note saying what was done | Users, water committee |
Can anyone check later? | Records that are kept, exported and not quietly deleted | Funder, auditor, regulator |
The first three rows are field evidence that users can supply. The last three are about accountability: whether a report leads anywhere, and whether anyone outside the office can see that it did.
How existing CitizenClimate features could be applied to rural water
No real water project is shown on the CitizenClimate website. The borehole page is a walkthrough of a fictional project, Lusiwa Wells. This section sticks to features described in the App Guide and the Data Integrity and Methodology Protocol, and says how a water programme could use them.

Reporting a broken water point, with or without signal
A project developer, in this case a service provider, NGO or district team, builds a survey in the app. According to the App Guide, "Questions can be multiple choice, text, numbers, dates, photos, videos, audio, species identification or GPS. Some only appear after certain answers." An outage survey could ask which water point is affected and what is wrong, with a follow-up question that only appears if the user picks "water looks or smells wrong".
Surveys can require a location. The App Guide says surveys that require a location "won't start without a GPS fix", and the Protocol stores the accuracy of each reading. A water point can have little or no mobile signal, which matters here: submissions made offline are saved "with the time and place you recorded them" and sent automatically when the phone is back online. The Protocol adds that for offline records "the original timestamp is preserved", with the sync date recorded separately. A report made at the pump at 07:00 and sent from town at 16:00 still says 07:00.
Household surveys on water access
The app includes survey templates for all 17 SDGs, according to the field data collection page. Our SDG impact walkthrough explains how household answers are weighted into a 0 to 100 score per goal and how indicators "can be tagged to official UN codes such as 6.1.1, safely managed drinking water". A water programme could run a short household survey each quarter on where people collect water and how long it takes. These are community-reported proxies mapped to SDG 6, not official statistics or laboratory results.

Complaints that stay on record
Some problems are not breakdowns. A user may want to say that a caretaker is charging more than agreed, or that a repair promised last month never happened. The app has a grievance mechanism for this. Each grievance moves from Pending to Under Review to Resolved, the project developer can reply with a resolution note, and other members can vote grievances up or down. The App Guide states: "Grievances can't be deleted, and your name isn't shown to the project developer or to other members."

What the service provider sees
The project developer opens a map of submissions, groups them by user, filters by any answer and exports raw records as CSV or JSON. The Protocol states that "Submissions can never be deleted": a wrong report is archived with a reason from a fixed list, such as duplicate submission or incorrect data. For a water programme, that means a funder could later compare outage reports with the service provider's own repair records, and a report cannot quietly disappear.
People can be thanked for the work. Members earn points and badges, and a project can choose to add a currency reward to a survey. Whether to offer one, and how much, is the project's decision.
Our 60-second borehole film shows a fictional project in which flow sensors and Bluetooth syncs add a second stream of data. Those devices and the repair alerts appear only in the walkthrough film; the App Guide does not describe them.
Concept: a water point status board
Concept, not a product feature. This describes an idea CitizenClimate is exploring. It is not available in the app today, and there is no release date or price.
Today a project developer can build an outage survey, and each submission is timestamped. Grievances are a separate record with their own Pending, Under Review and Resolved status. The idea we are exploring is a view that would group both by water point.
Here is how it could work:
A register of water points. The service provider would register each water point once at its location, so users could pick it from a list.
Days out of service. The first "no water" report on a point would start a count, and a "resolved" note from the mechanic would stop it. The board would show which points have been down longest.
Routing to the right person. Each report could be sent to the mechanic or caretaker responsible for that area, rather than waiting for someone to read the full list.
Users see the outcome. People who reported a point could see when it was marked fixed, and confirm or dispute that it is working again.
A board like this would not repair anything. It would only be useful where a funded maintenance service already exists, which is the lesson of the Kenyan example above. It would also rely on enough users reporting, which takes trust that reports lead somewhere.
Limits, and where this stops
Some things this approach cannot do, even with the concept built.
It is not a sensor network. User reports are slower and patchier than a reading every few minutes. They can, however, cover water points that have no sensor at all.
It does not test water. A report that water "looks or smells wrong" is a prompt for a proper test, not a result.
It needs a connection to finish some tasks. The App Guide lists features that need a connection, such as the forum. Surveys can be filled in offline and sent later.
It does not replace national systems. Records exported as CSV or JSON would still need to be matched to a district's own water point inventory.
Frequently asked questions
What is rural water service monitoring?
It is the regular checking of whether rural water points deliver water people can use: whether the source works, how long collection takes, whether the water is safe, and how fast breakdowns are repaired. It combines visits by service providers, household surveys, sensor data where it exists, and reports from users and water committees.
How common are hand pump breakdowns?
A review of handpump data from 47 countries in sub-Saharan Africa and the Asia-Pacific region by Foster et al., published in the International Journal of Water Resources Development, found that approximately one in four handpumps in sub-Saharan Africa are non-functional at any point in time. The authors note inconsistencies in the data, and say functionality in the Asia-Pacific varies widely, with data gaps that prevent a reliable regional estimate.
Can water point users report problems without mobile signal?
In the CitizenClimate app, yes for surveys. Submissions made offline are saved on the phone with the time and place they were recorded, then sent automatically when the phone reconnects, and the original timestamp is preserved. Some features, such as the forum and dashboards, need a connection.
Does CitizenClimate test drinking water quality?
No. The app records what people report, with photos and a location where the survey asks for them. A report that water looks or smells wrong can prompt a test, but it is not a laboratory result. Household SDG surveys gather community-reported answers mapped to SDG 6, not official statistics.
Try the parts that exist today
The water point status board is a concept. Offline surveys and grievances that cannot be deleted are in the app now, along with raw data exports. If you run a rural water programme and want to try them with a water committee, download the free app, or read the App Guide first.



Comments