How to Monitor Sewer Overflows in Real Time

A surcharge alarm at a pump station is useful. An alarm that identifies a rising sewer level, verifies whether an overflow has occurred and shows the likely receiving environment is operational intelligence. That is the difference when planning how to monitor sewer overflows across a council or utility network. The objective is not simply to collect more data. It is to give operators reliable, time-stamped evidence early enough to protect people, waterways, assets and regulatory obligations.
Start with the overflow pathway
A sewer overflow is rarely a single-point failure. It may result from wet-weather infiltration and inflow, a blocked gravity main, pump failure, power loss, a high tide restriction, debris at a screening point or a capacity constraint downstream. Monitoring needs to reflect that pathway.
Begin by mapping each candidate site from the upstream catchment through to the likely overflow point and receiving environment. Review previous incidents, customer complaints, wet-weather patterns, pump run times, maintenance records and hydraulic model outputs. This identifies whether the primary warning signal should be level, flow, pump status, pressure, water quality or a combination of measurements.
Not every maintenance hole needs the same instrumentation. A recurrent overflow adjacent to a creek deserves a different design to a remote surcharge location with no nearby waterway. The highest-value sites are generally known overflow structures, low-lying maintenance holes, pump stations, siphons, critical trunk mains and locations where an incident could affect public areas or sensitive environmental receptors.
How to monitor sewer overflows with layered measurement
A reliable system uses more than one indication where the consequence of a missed event is high. Level is usually the fastest and most direct signal of surcharge risk, but level alone does not always prove that sewage has escaped the network.
Measure sewer level before an overflow occurs
Non-contact radar level sensors are well suited to many sewer applications because they avoid direct contact with corrosive wastewater and floating material. Installed above the flow path, they can continuously track the rise from normal operating level towards the overflow crest or maintenance-hole cover.
Set alarm thresholds based on actual site geometry rather than a generic percentage of depth. A practical configuration often includes a pre-alarm level for investigation, a high-level alarm for urgent response and a critical alarm at, or immediately below, the known overflow elevation. The right spacing depends on how quickly levels can rise, the travel time for crews and the available storage upstream.
For pump stations, combine wet-well level with pump run status, duty/standby operation, power supply and discharge pressure where available. A high wet-well level with a failed duty pump is a materially different event from a high wet-well level during normal peak pumping.
Confirm whether discharge has reached the environment
At known overflow points, a second sensor can distinguish surcharge from an actual discharge. Depending on the structure, this may involve monitoring level in the overflow chamber, measuring flow in an overflow channel, or installing a water quality station downstream in the receiving water.
Conductivity, turbidity, dissolved oxygen, temperature and ammonium can help identify an abnormal wastewater influence in a creek, drain or estuary. No single parameter provides a universal sewer overflow signature. Rainfall, tidal conditions, industrial discharges and natural catchment variation can all affect readings. The strongest evidence comes from correlating water quality change with upstream sewer level, rainfall and site-specific hydraulic behaviour.
Add rainfall and network context
Rainfall is a crucial contextual input for wet-weather overflows. A local rain gauge can show whether a rapid level rise matches a storm cell, while historical data can reveal the rainfall intensity and antecedent wetness that tend to trigger surcharge.
Where the network is extensive, additional flow meters and level stations create a clearer picture of where the restriction or excessive inflow is developing. Monitoring a critical trunk main without visibility of key upstream sub-catchments can leave operators reacting to the final symptom rather than locating the cause.
Make telemetry and alarms operationally useful
Remote monitoring only delivers value when data arrives consistently and alarms lead to action. Field devices should transmit through communications appropriate to site coverage, power availability and criticality. Remote sites may require solar power, low-power instrumentation and communications that can retain data during short outages and forward it once the connection is restored.
Alarm logic should account for noise, temporary surges and sensor behaviour. A single brief high-level reading may warrant a notification, while sustained elevation or a rapidly rising trend may justify escalation to an on-call operator. Alarm delays, hysteresis and rate-of-rise rules reduce nuisance alarms without masking a real event.
Each alarm should include enough context to support a decision from a mobile or control room: current level, trend, alarm threshold, battery condition, communications status, recent rainfall and associated pump or flow status. Geo-mapped visualisation is especially valuable when managing distributed assets, because it helps teams see whether multiple sites are responding to the same storm event.
The escalation process also needs to be defined before the first event. Identify who receives the alarm, the expected response time, when field verification is required, how public health or environmental teams are notified and how the incident is recorded. Technology can shorten detection time, but it cannot replace a clear operating procedure.
Design for hostile sewer conditions
Sewer monitoring hardware operates in a difficult environment. Humidity, hydrogen sulphide, condensation, debris, corrosive gases, flooding, vandalism and restricted access all influence equipment selection and installation quality.
Choose enclosure ratings, mounting arrangements, cabling and sensor materials for the actual conditions at the site. Non-contact instruments can reduce fouling and maintenance, but they still require a clear measurement path and secure mounting. In submerged applications, consider sediment accumulation, ragging, access for cleaning and whether the sensor can be safely recovered without confined-space entry.
Power design is equally important. A mains-powered station may still need backup power during the very outage that prevents pumps from operating. Solar-powered installations need to account for shading, battery autonomy, seasonal generation and the energy demand of the sensor, telemetry and sampling interval.
Installation should include a surveyed reference level and documented overflow crest elevation. Without a reliable datum, historical trends are difficult to compare and alarm thresholds can be set incorrectly after maintenance or equipment replacement.
Treat data quality as part of overflow monitoring
Poor-quality data creates false confidence. Establish a commissioning process that checks sensor readings against manual observations, confirms communications, tests alarm delivery and verifies that cloud dashboards display the correct location, units and threshold settings.
Ongoing quality assurance should flag flat-lined readings, implausible jumps, battery decline, communications gaps and values outside the expected physical range. A level sensor reporting the same value through a major storm may indicate a stable sewer, but it may also indicate a blocked measurement path or failed device.
Trend data is valuable beyond immediate incident response. It can reveal recurring surcharge locations, quantify the effect of rehabilitation works, support wet-weather capacity planning and identify sites where pump control changes or infiltration reduction programmes are delivering measurable results. The best monitoring programmes turn individual alarms into a defensible long-term view of network performance.
Integrate field intelligence with existing systems
Utilities and industrial operators often already use SCADA, telemetry, maintenance management platforms and incident reporting systems. A new overflow monitoring deployment should complement these systems rather than create another isolated dashboard.
Use hardware that can support common industrial interfaces, including Modbus and 4-20 mA inputs where integration with existing assets is required. Cloud-based delivery can reduce the need for additional customer IT infrastructure, while still making validated data available to authorised operational and engineering teams.
TracWater deployments are designed around this end-to-end approach: field-proven sensors, remote communications, geo-mapped cloud visualisation and actionable alarm data in one utility-ready monitoring system. The correct configuration remains site-specific, particularly where legacy control systems, remote communications constraints or environmental compliance requirements apply.
Build a monitoring programme that crews can maintain
The most capable instrument is ineffective if crews cannot safely inspect, clean and verify it. Include maintenance access, calibration needs, cleaning intervals, spare parts, communications checks and battery replacement in the asset plan from the outset.
Review alarm performance after significant rain events and actual overflows. If alarms arrive too late, assess threshold positions, transmission intervals and upstream monitoring coverage. If alarms are excessive, investigate the hydraulic reason first, then refine logic without suppressing meaningful warnings.
A well-designed sewer overflow monitoring system gives operators time to intervene and gives asset managers evidence to prioritise capital works. Start at the sites where an overflow carries the greatest consequence, prove the measurement and response workflow, then expand the network with standards that remain practical in the field.





Comments