The short version
WaterWatch exists because sewage data should not feel like insider information.
We monitor sewage overflow events in the Thames Water region and turn raw technical feeds into information that normal people can actually use. That means clear maps, plain-English summaries, and alerting that reaches you while an event is happening, not weeks later in a PDF.
This project is independent. It was started by one developer who was frustrated by how hard it is for the public to see what is happening to local rivers in real time. We are still early-stage, still improving, and very open about what our data can and cannot tell you.
If you care about cleaner rivers, accountability, or simply not being kept in the dark, you are exactly who this platform is for.
Why this project was built
A personal starting point: too many people were hearing about spills after the fact.
The idea for WaterWatch came from a simple question: if overflow events are recorded by sensors, why does it still feel so difficult for ordinary residents to get a straight answer about what is happening near them? You could find fragments of information. You could find annual totals. But in-the-moment visibility was limited, scattered, or hidden behind technical language.
So WaterWatch was built to close that gap. Not with another headline. With infrastructure. A live map. Per-site history. Alerts that trigger on start and stop events. Download tools for people who want to run their own analysis. Explainers for people who do not.
The mission is plain: make river-impact data understandable enough that communities can use it in real life, whether that is choosing where to swim, asking better questions at local meetings, or tracking whether promised upgrades are actually visible in outcomes.
How the system works
We take public source data and make it usable without changing the core events.
1) Source ingestion
We pull event data from publicly available monitoring feeds. For each overflow site, we track status changes over time and preserve event timing.
2) Context layering
We pair discharge events with nearby rainfall and river-level signals so users can interpret patterns rather than reading one isolated number.
3) Public delivery
Live map views, site-level timelines, rankings, and downloads are published in a format that non-specialists can navigate quickly.
4) Accountability tools
Alert subscriptions and historical comparisons help users track whether local conditions are changing, and in which direction.
In practical terms, that means someone checking river safety on a Friday evening and someone preparing evidence for a public consultation can both use the same platform, just at different depth.
Why normal people should care
This is not just “water sector” data. It affects health, trust, and local decisions.
If a spill happens near places where people swim or paddle, exposure risk can change quickly. If repeated events occur near the same neighbourhoods, local confidence in infrastructure drops. If public reporting is hard to understand, communities cannot challenge claims effectively. That is the core real-world impact.
We also try to avoid simplistic narratives. A fall in annual spill hours can be good news. It can also reflect a drier year. A rise can indicate poor performance, but it can also coincide with unusually extreme rainfall. Good analysis separates those effects instead of pretending they are the same thing.
At first glance, one headline number looks decisive. In reality, context decides whether that number means progress or warning.
Transparency and limits
Trust comes from being precise about uncertainty.
We are explicit about data constraints because we would rather be accurate than overconfident. Sensors can go offline. Some feeds can arrive late. Event timing does not equal full ecological impact. Missing context can mislead if you only read rankings.
That is why WaterWatch publishes methodology explainers and encourages users to inspect source-linked data. We do not smooth inconvenient periods or hide uncertain intervals. If something is ambiguous, we say so.
- Primary discharge events come from public EDM-based reporting.
- Rainfall and river context are included to reduce false interpretation.
- Historical comparisons are shown with caveats, not marketing language.
- The platform is free to use, with downloadable data where available.
Where to go next
If you are new here, start with these pages.
We are building this openly and iterating fast. If you spot an issue, want a feature, or want to collaborate on analysis, contact us. The aim is not to look polished from a distance. The aim is to be genuinely useful up close.
Have feedback, data questions, or a local lead?
Send it through. Useful public platforms are built with communities, not just for them.
Contact WaterWatch