Most sewer systems go unnoticed until something goes wrong. The infrastructure runs underground, the maintenance happens quietly, and the public rarely thinks about where wastewater goes once it leaves a building. For the people who manage that system, though, the question was never really “what is a sanitary sewer overflow.” It is “where is the next one hiding, and will we find it before it finds us.”
This post is built for both readers. The first section is a quick refresher for anyone newer to the topic. Everything after it is for the leadership teams, supervisors, and engineers who already know what an SSO is and need to make decisions about preventing the next one.
The Definition, Briefly
A sanitary sewer overflow (SSO) is a release of untreated or partially treated wastewater from a collection system before it reaches a treatment facility. That discharge can reach streets, storm drains, waterways, and private property, carrying pathogens, nutrients, and other contaminants with it.
The distinction from a combined sewer overflow matters, because it drives how regulators respond. Combined systems carry wastewater and stormwater in a single pipe and are permitted to overflow under defined wet-weather conditions. Sanitary systems are designed to carry waste only and are not expected to overflow under any circumstances. That is why federal law treats an SSO as a violation rather than an anticipated event, and why the burden of proving you are managing the system falls on the utility.
Why This Is a Board-Level Issue, Not Just an Operations One
SSOs are regulated under the Clean Water Act through NPDES permits. The EPA estimates that 23,000 to 75,000 SSOs occur nationwide every year, and recurring or severe overflows can trigger consent decrees, which are legally binding agreements that put a court, not the utility, in control of the corrective work and its timeline.
For leadership, the part worth internalizing is that an SSO converts a problem you could have scheduled into one you no longer control. A proactive inspection and maintenance program is a budgetable operating expense, scoped and spread across fiscal years, that produces a durable asset in the form of condition data. An overflow produces the opposite: unplanned emergency cleanup, civil penalties, and court-ordered capital spending on someone else’s schedule.
The enforcement record shows the scale. The Metropolitan St. Louis Sewer District resolved Clean Water Act violations with a $1.2 million civil penalty plus a requirement to spend at least $30 million reducing inflow and infiltration. The City of Memphis paid roughly $1.29 million under a similar settlement. And between 2006 and 2012, the San Antonio Water System recorded roughly 2,200 overflows that discharged 23 million gallons of raw sewage, leading to a $2.6 million civil penalty and a sewer upgrade program reported at more than $1 billion. None of those figures is the cost of fixing pipes. They are the cost of having waited.
Stated plainly for a governing board: the dollars spent inspecting and maintaining a collection system are a fraction of the dollars a consent decree can compel, and the organization keeps control of how and when the planned dollars are spent.
What Actually Causes an SSO, and Why It Is Rarely a Surprise
Overflows are seldom the result of a single failure. They are the visible outcome of conditions that were in place long before the event, which is exactly why a system that monitors those conditions can see them coming. The common causes break down along lines that supervisors and engineers will recognize from the field.
Blockages. Fats, oils, and grease (FOG), root intrusion, debris, and non-flushable materials are the leading cause of dry-weather overflows. These are also the most addressable through routine cleaning and root control, which is why blockage-driven SSOs are often the clearest signal that a maintenance cycle is falling behind in a given basin.
Inflow and infiltration. I&I is the entry of stormwater and groundwater into the system through cracked pipes, deteriorated manholes, failed joints, and illicit connections like sump pumps and roof leaders. For engineers, I&I is the variable that turns a structurally compromised but quiet line into a wet-weather overflow point. Quantifying it, through flow monitoring, smoke testing, and condition inspection, is what separates a guess about capacity from a defensible one.
Insufficient capacity. Undersized pipes and pump stations, or service-area growth that outpaced the original design assumptions, produce overflows that cleaning alone will never solve. These point toward rehabilitation, upsizing, or capital projects rather than O&M, and distinguishing them from blockage and I&I issues is the difference between spending on the right fix and repeating the wrong one.
The throughline is that every one of these causes leaves evidence before it produces an overflow. A FOG-prone segment shows grease on camera. A deteriorating line shows cracks and infiltration. A capacity-constrained basin shows it in flow data. The organizations that avoid surprises are the ones capturing and acting on that evidence.
The Stakes Beyond Compliance
The regulatory and financial consequences are real, but they sit alongside direct public health and environmental exposure. Wastewater in waterways or public spaces can contaminate drinking water sources, close recreational areas, and expose residents to pathogens. The combined cost of cleanup, legal liability, infrastructure repair, and the reputational damage that follows a publicized overflow consistently exceeds what proactive maintenance would have cost. For a leadership team prioritizing infrastructure investment, that is the honest comparison: not prevention versus zero, but prevention versus a compounding liability that grows every year the underlying conditions go unaddressed.
Where Your Next Overflow Is Hiding, and How to Find It First
Knowing why SSOs happen is the easy part. Knowing where your specific system is most vulnerable is the part that requires data, and it is the difference between a program that reacts and one that prevents.
Utilities with comprehensive inspection records, pipe condition assessments, and maintenance histories can identify risk before it produces an overflow. Those without that data are making allocation decisions in the dark, which is how deferred conditions become active failures. Charlotte Water offers the clearest proof. Managing a 4,400-mile system serving more than a million people, the utility entered an EPA administrative order after a record number of SSOs, then drove annual overflows from 500 down to 155 over the following decade. ITpipes serves as the CCTV inspection and data management backbone of that program, with inspection data integrated into the utility’s work order system so that events can trigger automatic work assignments. The reduction was not luck. It was the result of consistently knowing the system. (Full story: Driving Down Overflows: Charlotte Water’s Data-Driven Sewer Strategy.)
That is what pipeline inspection data management makes possible: a centralized, accurate picture of system condition that becomes the foundation for emergency response, proactive maintenance, capital planning, and public accountability.
Next step: Download our Pipe Inspection Buyer’s Guide to evaluating inspection and condition assessment tools to support your proactive pipe management plan.
