Both put untreated or partially treated sewage into a waterway. One is a known, permitted design condition in aging combined sewer systems. The other is essentially always a reportable failure — and the difference comes down to whether the pipe was ever supposed to carry that flow in the first place.
A combined sewer overflow (CSO) happens in a combined sewer system — one pipe network carrying both sanitary sewage and stormwater runoff together, common in older U.S. cities built before roughly the 1950s–70s. During heavy rain, the combined flow can exceed what the interceptor pipe and treatment plant can handle, so the system deliberately spills the excess — diluted sewage and stormwater together — at a built-in regulator structure, straight into a river, lake, or estuary. A sanitary sewer overflow (SSO) happens in a separate sanitary sewer system — a pipe that was built to carry only sewage, with stormwater running in its own, entirely separate storm drain network. An SSO occurs when something in that sanitary-only pipe fails: a grease or root blockage, a collapsed or undersized line, or infiltration/inflow (I/I) that overwhelms it during wet weather — and untreated sewage escapes through a manhole, a cleanout, or a broken pipe, because that pipe was never built with anywhere else for the excess to go.
The confusion between CSOs and SSOs almost always starts here: both events end with untreated or partially treated sewage in a stream, and both get reported in the news as "sewage overflow." But a CSO is a designed release point built into a combined system precisely so that, when wet-weather flow exceeds capacity, the excess has somewhere controlled to go instead of backing up into basements and streets across the whole city. An SSO has no such designed release point at all — a separate sanitary sewer is engineered on the assumption that 100% of its flow reaches the treatment plant, so any escape is, by definition, the system failing to do the one thing it was built to do.
A combined sewer was engineered from the start to carry stormwater and sanitary flow in the same pipe, on the explicit understanding that during large storms the combined volume would exceed what the interceptor and treatment plant could process. Regulator structures and CSO outfalls exist precisely to handle that predictable condition in a controlled way, at a known location, instead of letting the excess back up into thousands of basements and streets across the service area. A separate sanitary sewer was engineered on the opposite assumption — that it only ever needs to carry sewage, sized and designed to route 100% of that flow to a treatment plant with no relief valve. When something interrupts that — a grease clog, root intrusion, a collapsed pipe, or inflow/infiltration overwhelming a line during a storm it was never sized for — there is no designed place for the excess to go, so it escapes wherever the system is weakest: a manhole, a cleanout, a break. That is not a known operating condition being exercised; it is the system failing at the one thing it exists to do, which is exactly why regulators treat the two so differently.
No. A CSO from a properly permitted combined sewer system, occurring during a wet-weather event covered by the utility's NPDES permit and approved Long Term Control Plan, is a known, anticipated, and lawfully authorized discharge condition — closely monitored, aggressively regulated in frequency and volume under the EPA's CSO Control Policy, and not automatically a permit violation each time it happens. An SSO, by contrast, is essentially always a reportable event and typically treated as a violation regardless of cause. There is no permitted SSO discharge point anywhere in a separate sanitary system — it is engineered to contain 100% of its flow — so any escape, whether from a single tree root, a first-time pipe collapse, or a contractor cutting a line, triggers mandatory reporting, public notification in many states, cleanup, and often a corrective action plan. Treating the two as equivalent misses the entire reason the regulatory frameworks around them look so different: one is a managed condition inside a system built to expect it, and the other is that same system failing outright.
Explains why a combined sewer overflow (CSO) — a permitted, designed release point in older combined sewer systems that activates when wet-weather flow exceeds interceptor and treatment plant capacity — is regulated completely differently from a sanitary sewer overflow (SSO), which is an unauthorized escape of sewage from a separate sanitary-only sewer caused by a blockage, failure, or capacity overload, with no designed overflow point at all.
Both events are reported publicly as "sewage overflow," both put untreated or partially treated sewage into a waterway, and both trigger beach closures, fish kill concerns, and public health advisories. That shared visible outcome makes it easy to assume they are the same category of problem. They are not: a CSO happens in a combined sewer system deliberately built to carry stormwater and sanitary flow together, with regulator structures and permitted outfalls engineered in from the start to relieve excess wet-weather volume at a known point. An SSO happens in a separate sanitary sewer that was never designed to carry stormwater or to overflow anywhere — so when it does, something has gone wrong.
CSOs are governed in the U.S. by the EPA's 1994 CSO Control Policy, incorporated into the Clean Water Act, which requires combined sewer communities to implement nine minimum controls and develop a Long Term Control Plan (LTCP) — a capital program (often sewer separation, storage tunnels, or expanded treatment capacity) aimed at reducing CSO frequency and volume over time, typically under a court-enforceable consent decree. Individual CSO events during a permitted, covered wet-weather condition are tracked, monitored, and publicly reported, but are not automatically treated as a discrete permit violation the way an unpermitted discharge would be — the LTCP itself is the long-term compliance mechanism.
SSOs have no equivalent 'permitted condition.' EPA's SSO policy and most state programs require immediate reporting (often within 24 hours), public notification for events affecting waters used for recreation or drinking water supply, cleanup and disinfection of affected areas, and root-cause investigation. Utilities with recurring SSOs are frequently placed under consent decrees requiring capital investment in sewer rehabilitation (pipe lining, manhole rehabilitation, pump station upgrades) specifically to eliminate the failures — blockages, structural defects, and excess I/I — causing the overflows.
No — by definition an SSO occurs in a separate sanitary sewer. However, a combined sewer system can experience what is sometimes called a "dry-weather overflow" if a regulator structure malfunctions or a blockage causes sewage to escape even without a storm — that event is treated much more like an SSO for enforcement purposes, because it happens outside the wet-weather condition the CSO outfall was permitted for.
Mostly because they were built over a century ago in dense older cities, and fully separating a combined system into independent sanitary and storm networks means digging up nearly every street in the service area — an enormous, multi-decade capital cost. Instead, most cities with combined sewers are under long-term control plans that reduce CSO frequency and volume through storage tunnels, green infrastructure, and plant capacity upgrades rather than full separation.
Yes — a CSO becomes a violation if it occurs outside the conditions covered by the permit and LTCP (for example, during dry weather, from a malfunctioning regulator, or at a frequency/volume exceeding what the LTCP was approved for). The permit authorizes a defined, monitored condition, not unlimited discharge.
The most common causes are blockages from grease (fats, oils, and grease — "FOG"), tree root intrusion, and debris; structural failures like collapsed, cracked, or offset pipe; and capacity overload from excessive inflow and infiltration (I/I) — stormwater and groundwater entering the sanitary system through cracked pipes, illegal roof-drain connections, or leaky manholes during heavy rain.
In most states, yes, though the mechanism differs. CSO outfalls are typically posted permanently at the discharge point and events are logged and reported to the state and EPA as part of routine permit compliance. SSOs generally require active, event-specific notification — often within 24 hours to the state agency and, for overflows reaching a waterway, public notice — because each one is treated as an unplanned, reportable incident rather than a monitored recurring condition.
Try our Environmental & Water Resources Studio
More calculators, simulators, and guides for this discipline.