DS105 group project · 2026

It's not just the rain

Are water companies right to blame the weather for sewage spills?

An introduction

Ufford Hole

The shallow pool in the village of Ufford in Suffolk was a great spot for chilling with friends on a hot summer day in the school holidays. Since the summer of 2022 the parish council has been putting up notices each time volunteer testing shows E. coli well above the bathing-water threshold.

The River Deben (pictured above) is a tidal estuary on the Suffolk coast. From its source near Debenham it runs about thirty miles south, past Wickham Market and Woodbridge, before opening out into the North Sea at Felixstowe Ferry. I've grown up around it: swimming, sailing, kayaking.

This project was motivated by the pollution affecting my local river, and spurred our interest in understanding the extent to which water companies are responsible.

— Jack

A national problem

Easy to blame the rain

Sewage in English rivers has been a story going round the news for years. Channel 4's Dirty Business, broadcast earlier in 2026, pulled together a version of the story most viewers will already have seen pieces of: chronic under-investment, ageing combined sewers, a regulator that struggles to keep up.

Storm overflows are a deliberate part of the network. Ofwat, the regulator for water companies, describes them as “relief valves when the sewerage system is at risk of being overwhelmed” — releasing excess rainwater and wastewater into rivers or seas to prevent sewage backing up into homes during heavy rainfall. Anything else, by the regulator's own definition, is outside their design intent. On the same page, Ofwat acknowledges growing public concern that overflows are operating when there has not been significant rainfall. That is the question this project sets out to test.

Every water company in England runs storm overflows. The standard reasoning, when challenged on a bad year, points to rainfall as the explanation. A wetter year mechanically produces more spills. This defence is partly true.

The question we set ourselves is to check whether the defence based on rainfall is sufficient. Once you control for rainfall, and not just total rainfall, but the kind of rainfall the sewage system is actually stressed by, how much of the variation in spills is left unexplained?

What's published, and what isn't

What the law lets us see

The Environment Act 2021 sets the floor for what water companies have to disclose about sewage discharges. Two sections do most of the work, and neither is shaped to help an outsider analyse the system.

Section 81 requires near-real-time reporting of spill events as they happen, but says nothing about preserving the historical record. A company has to tell you a spill is happening; nobody is obliged to keep the diary once it is over.

Section 80 requires an annual return: a single yearly count and total duration of spills per overflow location. For most of the country, that annual aggregate is the most granular long-run data anyone outside the water company is allowed to see.

The sensors that record those spills, called Event Duration Monitors (EDM), were only fully rolled out across the network by the end of 2023. Earlier years exist in the same aggregate format but with sparse sensor coverage.

And the entire spill datasets are self-reported. Water companies have been fined in the past for deliberately misreporting their performance data. Auditing them sits well outside what is possible from outside the regulator, therefore we've assumed their self-reported data is truthful in our analysis.

Part one

The national picture, at face value

Mean annual spills per active storm overflow monitor, by water company, drawn from the Environment Agency's mandatory EDM Annual Returns. Same source, same units, every operator on the same chart.

Figure 1

Five years of spill counts, ten water companies

Mean annual storm overflow spills per active monitor, by water company, 2021 — 2025.

Source: EA Event Duration Monitoring Annual Returns 2021 — 2025, full population (every storm overflow site that reported in each year, between roughly 11,300 sites in 2021 and 14,200 in 2025). Wessex Water did not report any sites in 2021 (its line begins in 2022). Means are taken across all active monitors each year to neutralise the network's expansion as Event Duration Monitor rollout completed in late 2023. All ten lines apply the EA's 12-24 hour counting rule, so they are directly comparable.

Part two

Thames Water, of all companies

There is one exception to the Section 80 ceiling. Thames Water publishes a detailed historical record of its own storm overflow events through a public API: start time, end time, location, going well beyond what the annual return contains. It is a voluntary disclosure, made in the middle of a long public row about the company's finances and environmental record.

The disclosure gives outsiders a resolution of data that the regulatory floor does not require of anyone. That happens to make Thames Water, the company often held up as a cautionary tale, the only one we can actually study at the event level.

Annual totals tell us whether a year was bad. Event-level data tells us why. With start and end times for every individual spill, we can see whether a given discharge happened during a storm, after a storm, or during a stretch of dry weather. The annual return doesn't have the resolution to answer any of that.

Thames Water's operating area runs from Gloucestershire to Kent, taking in urban and rural, chalk and clay. That internal range is enough for the rainfall-spill relationship to vary meaningfully within it, which is what the analysis depends on. The fuller question of how representative Thames Water is comes later, in the limitations.

Antecedent Precipitation Index (API)

API is a common hydrological metric that captures how wet the catchment is at a given time, based on recent rainfall. It applies a decay weighting to the rain that fell on each of the past seven days, giving more weight to recent rain and less to older rain that has had more time to drain away.
Specifically, we use a 7-day API with a decay factor of 0.85. The examples below show how the same total rainfall can produce a very different API depending on how that rain is distributed across the week.

Rain bunched at the end of the week

A real storm, with heavy rain in the last three days.

Total rainfall: 26 mmAPI today: 22.2 mm (above the 19 mm threshold)

Same total, spread out evenly

Light, persistent drizzle every day for a week.

Total rainfall: 26 mmAPI today: 16.5 mm (below the threshold)
Contribution to today's APIAlready drained away

The threshold of 19 mm is Thames Water's long-run mean API plus one standard deviation (mean 9.66 + σ 9.29 = 18.95 mm), "wetter than the typical week in Thames Water's catchment". Each company in the regression uses its own threshold computed the same way, so a wet week in Wessex is measured against Wessex norms, not London's. The recursive form used in the notebook (with k = 0.85) follows Kohler & Linsley (1951); the choice of k is discussed in the methodology doc.

Part three

What the event-level data reveals

We classify each Thames Water spill in 2025 by the catchment moisture on the day it began, using our rolling 7 day API rainfall metric.

Figure 2

Only 41% of Thames Water's 2025 spills started under wet conditions

Each 2025 discharge event is classified by the 7-day weighted antecedent rainfall index (API) on the day it began. The right panel tracks the share of spills that started after a completely dry week. Counts reflect the Thames Water API's raw start-to-stop pairs, which differ from the EDM Annual Return's 12-24 hour block-counted total.

Source: Thames Water Discharge Alerts API; n = 13,464paired discharges in 2025. The 19 mm threshold is Thames Water's long-run mean API + 1 standard deviation (mean 9.66 + σ 9.29 = 18.95 mm), so a spill in the >19 mmband started under conditions wetter than typical for the Thames Water operating area. 58.7% of 2025 events fell below it. 2022 and 2026 omitted from the right panel as partial years.

  • 1.3%·API = 0 (no rain in 7 days)
  • 12.6%·API < 5 mm (bone dry)
  • 12.4%·API 5–10 mm (lightly damp)
  • 32.4%·API 10–19 mm (wet but not anomalous)
  • 41.3%·API > 19 mm (wetter than typical for the catchment)

Share of spills starting after a dry week

Spills beginning with API < 5 mm, as % of all spills that year.

Part four

What it lets us say about the rest of the country

We visually verified the API metric-spill relationship for Thames Water, with one of the key supporting figures being shown in Validating our API metric against the Thames Water data.
We then ran a regression that strips rainfall stress and year out of every other company's annual spill counts, and looked at what's left. Each bar shows how far a company sits above or below the spill count the regression predicts for them given the rainfall they actually faced.

Figure 3

After controlling for rainfall, the company gap doesn't close

Each company's percentage above (+) or below (–) the spill count the regression predicts for them given the rainfall they actually faced. The rainfall stress is measured against each company's own catchment norms, not a national mm threshold.

Source: panel fixed-effects regression on n = 2,814 site-years (2021–2025) across nine EDM companies plus Thames Water event-level returns. The rainfall regressor counts days where both daily rainfall and 7-day antecedent rainfall exceeded each company's own long-run mean + 1σ (from rainfall between 2021 and 2025 across all sampled sites, from Open Meteo), so a wet day in chalk-stream Wessex is measured against Wessex's norms, not London's. Model R² = 18.6%. Confidence intervals are wide given ~20 sample sites per company.

Further analysis

The rainfall mechanism, in numbers

Our analysis thus far has found that more than half of Thames Water's 2025 spills started below our wet-anomaly (mean + 1 s.d.) threshold. However, this is worth balancing against the equally robust finding that, averaged across every monitor-day in the four-year panel, spill days really are much wetter than quiet days. The rainfall mechanism is real; the donut chart isn't claiming otherwise.

Figure 4

On average, spill days are nearly 4× wetter than quiet days

Mean daily rainfall and mean 7-day API on the days a Thames Water monitor recorded a new spill, compared against all other monitor-days. Drawn from the full event-level series of 76,848 spill events across 538 monitors, April 2022 to March 2026.

Days a monitor recorded a new spillAll other monitor-days

Source: Thames Water Alerts API. Across the full four-year daily series (one observation per monitor per day), the smoothed correlation between company-wide daily discharge count and 7-day API is r = 0.66. That's strong enough to confirm rainfall is the dominant immediate driver, weak enough that well over half of the day-to-day variance still sits with something other than the weather. As stated earlier, the discharge count that we use have from Thames Water's alerts ignores the 12-24 hour rule that is used in the Environment Agency reporting, so the spill counts are not directly comparable.

Conclusion

Partly the rain, and partly not

The rainfall mechanism is real. Across the four-year Thames Water panel, days with new spills are nearly four times wetter on average than quiet days, and the day-level correlation between discharge counts and antecedent rainfall is r ≈ 0.66. Rainfall is the dominant immediate driver of any individual spill event. Companies are not lying when they invoke the weather.

But it is not the whole story. For Thames Water, the only company we can study at event level, 59% of 2025 spills started below the wet-anomaly threshold, with a stable 4–9% across recent years beginning after fully dry weeks. And after stripping out the rainfall each network actually faced, the gap between the best- and worst-performing operators is still around 130 percentage points of rainfall-unexplained residual. That spread is too large to attribute to weather.

What is left sits with things this analysis cannot measure directly. Combined sewers built for Victorian populations clog more often than they used to. Blockages of fatbergs, wipes, and debris trigger discharges with no weather signal at all. Maintenance regimes vary by operator. Networks age. Pumping stations fail. Some companies appear to be running their systems harder than others, in ways that show up as systematically more discharges per unit of rainfall.

None of this is hard evidence in the strict sense. Event-level data exists only for Thames Water; the other nine companies give us a single annual count per outflow, with no event timing. Rainfall is measured on a ~9km Open-Meteo grid, not at each individual overflow. The spill counts themselves are self-reported, and have, on occasion, been deliberately misreported. The 1σ threshold and the regression specification are both analytical choices among several plausible ones. The findings should be read as directional, not as precise apportionments of blame.

Back at Ufford Hole on the Deben, the bathing-water notices are still going up. On this analysis, Anglian Water spills roughly a quarter less than rainfall alone would predict. They are not the standout bad actor of the national dataset. But "not the worst" is not the same as "fine". No amount of raw sewage pollution can reasonably be called "good" when it has such detrimental impacts on the environment and on people's lives.

The limitations of this analysis

The analysis is useful, but it is not exhaustive. These are the main reasons we treat the results as evidence rather than a final verdict.

The data is self-reported.

Water companies publish their own spill totals and monitor status. We cannot audit those figures here, so we treat them as the published record rather than the final truth.

Thames Water may not be representative of the whole country.

They are the only company that publishes event-level historical spill data, which is why the rainfall metric is possible at all. That makes them unusually useful, but not automatically representative of every company elsewhere in England.

It is also worth noting that we faced significant difficulty with using their API to collect their historical discharge alerts, with it continuously returning slightly different data (or none at all) for the exact same API query just moments apart. More detail on this can be found in the respective notebook.

All but one company only publish annual aggregates.

For the rest of the country, we only see one spill number per location per year. That means we can compare totals, but not the exact timing of each spill (and therefore the actual rainfall characteristics for each spill).

We do not use water quality sensor readings.

We originally hoped that we would be able to use water quality sensors to look for spikes in pollution readings as a proxy for spill events. However, the sensors are on average much too far from the overflows to be useful (often around 5km), and many sit upstream of the outflow rather than downstream. With this, it made no sense to use water quality sensor readings to enhance our analysis.

Local geology still matters.

Soils and geology change how fast rainwater reaches the sewer system. Comparing rainfall against local norms reduces that problem, but the adjustment is still imperfect. That said, Thames Water's area covers a wide range of geological conditions, which may help to mitigate some of these concerns.

EDM coverage improved over time.

Event Duration Monitor coverage was incomplete until the end of 2023. Earlier totals therefore undercount real spill activity, and part of what looks like a sharp 2023 increase is simply the monitoring network catching up. There are obvious risks of greater bias as a result of the smaller initial sample sizes.

Other pollution is also relevant.

We've implictly assumed in our analysis that spills are the primary concern, but other forms of pollution, such as agricultural runoff and houseboats discharging untreated sewage (which could be the case for the River Deben) also severely impact water quality. This analysis does not capture those impacts, though they are equally valid environmental concerns.

Further reading

For the methodology, technical decisions, and concepts behind the analysis, explore the detailed documentation.