What Storm Overflow Monitoring Data Shows

A storm overflow that spills for 20 minutes and one that spills for 20 hours may both appear as a single event in a headline figure. That distinction is why storm overflow monitoring data is indispensable, but never self-explanatory. It can reveal patterns that demand regulatory scrutiny, investment and local investigation. It cannot, by itself, tell communities the volume of sewage released, the pollutant load carried downstream, or the ecological harm caused.

For water-sector professionals, campaigners and informed residents, the task is not simply to count spills. It is to understand what the monitoring system records, where its blind spots lie and what further evidence is needed before drawing conclusions about compliance or environmental impact.

What storm overflow monitoring data records

Most monitored storm overflows in England are fitted with Event Duration Monitors, commonly known as EDMs. These devices use sensors within or around the structure to indicate when a discharge is occurring. Water companies provide the resulting returns to the Environment Agency, which publishes annual information on the number of spills and their duration at individual assets.

At its most useful, the dataset allows a reader to identify whether a named overflow discharged, how often it did so over a calendar year and the total time for which it was active. It also makes it possible to compare broad patterns between catchments, wastewater treatment works and water company areas.

This is a major advance on the position only a few years ago, when many overflows had no monitoring at all. Public reporting has made it harder for persistent discharges to remain invisible and has given regulators, river groups and local authorities a common starting point for questions about sewer capacity, asset operation and pollution risk.

But an EDM is not a water-quality instrument. It generally indicates that an overflow has operated; it does not take a sample of the discharge every time it activates. Nor does it directly measure flow volume. A spill count is therefore not a measure of the amount of sewage entering a river, coastal water or estuary.

Why spill numbers need careful interpretation

The annual number of activations attracts understandable attention because it is simple to communicate. Yet a high count can mean different things in different places. A catchment with frequent short rainfall events may generate numerous brief activations. Another may record relatively few events, but each could last for many hours and coincide with low river flows, when dilution is limited.

Duration adds useful context, but it also has limits. Long duration can point to sustained wet weather, infiltration into sewers, restricted treatment capacity, pumping problems or an operational fault. It may also reflect the way the monitoring equipment has recorded a continuing event. The cause cannot safely be inferred from duration alone.

The receiving environment matters just as much. A discharge upstream of a sensitive chalk stream, bathing water, shellfish water or designated habitat may carry greater consequences than a comparable event into a high-flow watercourse. Groundwater-fed rivers can be particularly vulnerable during dry periods, when natural flows are low and ecological communities have little resilience to further stress.

Seasonality is another essential consideration. Comparing one year with the next without considering rainfall can produce misleading claims, whether they are intended to praise or condemn. Wetter conditions may increase the likelihood of storm overflows operating, while dry-weather spills raise different and potentially more serious questions about whether a discharge was consistent with permit conditions and the proper operation of the sewerage network.

Monitoring is evidence, not a verdict

Storm overflows are designed to operate in exceptional circumstances to prevent sewage backing up into homes, streets and treatment works. That purpose does not give water companies a general licence to use rivers and coasts as routine relief valves. Their operation is governed by environmental permits, planning duties, investment obligations and wider legal requirements intended to protect receiving waters.

An EDM record does not establish illegality on its own. Regulators need to examine rainfall, flows, site operating records, telemetry, maintenance history, permit conditions and any evidence of pollution. They may also need to establish whether monitoring equipment was functioning correctly throughout the period in question.

Equally, the absence of a recorded event should not automatically be treated as proof that no discharge occurred. Equipment can fail, communications can be interrupted and data can require validation. Published datasets may flag data quality issues or incomplete reporting. These qualifications should not be used to dismiss the value of monitoring; they are reasons to demand dependable instrumentation, transparent assurance and prompt correction where records are uncertain.

For enforcement purposes, the strongest case is built from several sources. Event data can identify a pattern worth investigating. Flow monitoring can help estimate volume. Rainfall and river-flow records provide hydrological context. Water-quality sampling can identify concentrations of ammonia, phosphorus, bacteria or other pollutants. Ecological surveys can show whether repeated pressure is affecting fish, invertebrates or habitat condition.

The questions professionals should ask

A useful first question is whether the data covers the full year with reliable monitoring. A seemingly low spill total is less meaningful if there are long periods of missing or questionable data. The next is whether the overflow serves a combined sewer, a pumping station or a treatment works, since each has different operational pressures and potential failure modes.

Readers should then look beyond the individual asset. Are neighbouring overflows active on the same dates? Is there evidence of chronic infiltration from groundwater or surface water into foul sewers? Has new development increased impermeable area without sufficient drainage capacity? Is the catchment affected by misconnections, blocked sewers or constraints at the receiving treatment works?

For catchment managers, pairing overflow records with local monitoring can be particularly valuable. Citizen science samples should be collected using clear protocols and interpreted carefully, but they can help identify locations and times that warrant formal investigation. For local authorities, the findings may inform decisions on sustainable drainage, highway runoff, planning conditions and flood-risk management.

Water companies should not treat publication as the end of accountability. Data needs an accompanying explanation of asset condition, remedial action, expected delivery dates and how progress will be measured. A programme described only in terms of capital expenditure tells affected communities very little. They need to know which outfalls are being addressed, what standard is being targeted and whether ecological outcomes will improve.

From transparency to better decisions

The public availability of storm overflow records has changed the debate. It has shifted attention from occasional visible pollution incidents towards the cumulative pressure that wastewater systems place on rivers and coasts. That is valuable, particularly where repeated discharges coincide with communities already reporting poor water quality or declining river health.

Yet transparency can create a false sense of precision. League tables based solely on spill numbers may obscure the sites with the greatest environmental harm. Conversely, a water company pointing to reduced annual totals may be avoiding the harder question of whether discharges are still occurring in sensitive places, at damaging times or because basic infrastructure has not been maintained.

Better use of data means joining operational information to environmental outcomes. Regulators need adequate resources to interrogate records, inspect assets and pursue enforcement action where evidence justifies it. Water companies need investment plans that reduce dependency on overflows through sewer maintenance, treatment capacity, storage, separation where appropriate and catchment-based measures such as sustainable drainage. Monitoring must be sufficiently reliable that the public can trust both the figures and the decisions made from them.

The next time an overflow dataset is published, the most useful response is not simply to ask which company recorded the largest number. Ask what happened at the outfall, under what conditions, what entered the receiving water and what practical action will prevent a repeat. That is where monitoring data becomes a tool for protecting our waters rather than another annual statistic.