Plumbing
Sewer surcharge vs private blockage: which evidence decides the repair?
Use event timing, simultaneous sewer levels and camera evidence to separate a private restriction from public backwater and define the repair scope.
Direct answer
Compare time-matched water levels in the building lateral and public sewer, then test whether the backup follows building discharge, rising downstream head, or both. A private restriction is supported when water builds upstream of a located obstruction while the receiving sewer remains available. A public contribution is supported when event-time receiving head constrains lateral discharge; public surcharge means head above the crown of the public reach being measured. Rainfall timing and CCTV defects strengthen that diagnosis, but neither alone identifies which repair will stop the backup.
On this page
Which evidence separates surcharge from a private blockage?Where did the water enter the building?What should an event and rainfall timeline contain?How do you build an upstream-downstream level map?How long and how often should levels be monitored?What does CCTV standing water establish?Worked examples: what changes the repair decision?Which flow-path hypothesis fits the observations?What tests establish a private restriction and verify cleaning?Which repair follows each evidence pattern?What evidence should go to the utility?How should the investigation and repair be scoped?Open the related tool for the calculation, checklist, or packet.
FieldOS by AnvilfieldOffline-first FieldOS for job photos, proof packets, property memory, calculations, teams, billing, and owner-ready reports.Which evidence separates surcharge from a private blockage?
The repair decision comes from time-matched levels across the suspected restriction, the receiving sewer’s condition and the response to clearing. Upstream impoundment that disappears after a located private obstruction is removed supports private repair when discharge and downstream head remain comparable. Receiving head that constrains the lateral supports a public contribution; compare it with the public pipe crown before calling it main surcharge. Rainfall and CCTV findings identify useful tests, but the event hydraulics decide which scope addresses the backup.
A partial blockage can pass small flows and fail at higher demand; a public blockage can cause dry-weather backwater. [EPA’s Sanitary Sewer Overflow Frequent Questions](https://www.epa.gov/npdes/sanitary-sewer-overflow-sso-frequent-questions) identifies obstructions, extraneous water, inadequate facilities and equipment failures as separate causes, so neither weather nor ownership substitutes for finding the hydraulic bottleneck.
Backwater is an upstream level increase caused by a downstream control; [surcharge](/field-guides/glossary/surcharge/) identifies head above the crown of the named pipe reach. EPA’s [SWMM User’s Manual Version 5.2, February 2022, Section 9.2](https://www.epa.gov/system/files/documents/2022-04/swmm-users-manual-version-5.2.pdf) reports node surcharge relative to the highest connected conduit crown, so a node summary and a particular pipe section need explicit reference elevations. A main can constrain a low lateral before the main reaches its own crown. Surcharge, reversed flow and a building spill are separate findings.
What should the first cause statement say?
Write: “At [time/time zone], [access ID] was [water elevation/datum], while [receiving point] was [level]; [intervention] produced [response].” Separate observations, occupant reports and calculations, then state the supported cause, location and remaining test.
Confirm the receiving system: public main, private shared sewer or septic system. The utility handoff below assumes a public connection; hydraulic cause and ownership are separate findings.
Where did the water enter the building?
Trace the first entry point before assigning a sewer cause. Distinguish fixture overflow from entry through slab joints, doors, window wells, sumps or ejector basins. Record the opening, connection and elevation with photographs. Sewage spreading across a floor can obscure where it originally emerged.
[MSD Cincinnati’s investigation](https://prod.msdgc.org/programs/sewer-backup-sbu-program/sewer-backup-investigation/) covers public sewers, private cleanouts, drainage and the building’s lowest level. Separate sanitary evidence from [groundwater sump failure](/field-guides/plumbing/sump-pump-battery-backup-protection/).
A combined sewer intentionally carries stormwater and wastewater; a separate sanitary sewer can still receive unwanted rainwater. [Metropolitan St. Louis Sewer District’s backup guidance](https://msdprojectclear.org/customers/problems-tips/sewer-backups/) describes both arrangements in its service area.
Why is rainfall useful but insufficient?
Inflow enters through direct connections or openings; infiltration enters through defects from surrounding groundwater, as [RCAP’s July 24, 2023 collection-system guidance](https://www.rcap.org/assessing-your-collection-system-with-a-pipeline-camera-system/) explains. A rapid response is consistent with direct inflow, while a sustained response can fit groundwater infiltration. Rain can also load a defective private line, so a storm-linked symptom leaves both private and public paths open for investigation.
Record sump and foundation-drain connections, pump operation, valve state, antecedent groundwater and snowmelt. Include frozen or blocked surface drainage when present. Odor, water appearance and an unaffected neighbor are supporting observations, not measurements of receiving head.
During active sewage backup, stop building water use, as [Middleton’s current response instructions](https://www.cityofmiddleton.us/901/Handling-Sewer-Back-ups) direct. Keep occupants away from sewage. [CDC’s August 24, 2026 flooded-home guidance](https://www.cdc.gov/floods/safety/reentering-your-flooded-home-safety.html) says never operate electrical equipment or switch power while standing in water; if reaching the disconnect requires entering water, have an electrician isolate power.
Leave public manholes and sewer entry to the utility or its authorized crew. OSHA requires employers to identify and evaluate confined spaces under [29 CFR 1926.1203 for construction](https://www.osha.gov/laws-regs/regulations/standardnumber/1926/1926.1203) or [29 CFR 1910.146 for general industry](https://www.osha.gov/laws-regs/regulations/standardnumber/1910/1910.146). Use the separate [confined-space procedures](/field-guides/plumbing/confined-space-entry-permit-required/) and [sewage damage restoration](/field-guides/plumbing/water-damage-restoration-mitigation-iicrc-s500/) guides for those scopes.
What should an event and rainfall timeline contain?
Preserve native exports and add a comparison timeline in a stated time zone and UTC offset. Record clock corrections, including daylight-saving changes, without rewriting the original files.
Identify the rain gauge, its distance from the property, reporting interval, units and quality flags. State whether each value is interval depth, cumulative depth or intensity, and whether the timestamp marks the interval’s start or end. A distant gauge can miss a local burst.
Anvilfield recommends a common clock and 1 to 5 minute level records for short-rise investigations where the equipment supports that interval, retaining the rainfall source’s native resolution. The [ISCO 2150 manual, Rev CG, July 2024, Table 1-5](https://www.teledyneisco.com/en-us/Water_/Flow%20Meter%20Documents/Manuals/2150%20Flow%20Module%20User%20Manual.pdf) includes those storage choices, and the [USGS Charlotte-Mecklenburg rainfall network](https://nc.water.usgs.gov/charlotte/rainfallMap.php) supplies 5 minute precipitation. Sampling remains a project choice, not a national repair standard.
Event and rainfall timeline
| Event phase | Rainfall entry | Building/valve entry | Sewer entry | Interpretation/action |
|---|---|---|---|---|
| Dry comparison | Gauge ID, no-rain interval and antecedent conditions | Occupancy, fixture discharge, gate and pump status | Levels at private point C and utility points U/D | Establish baseline under known demand [S2, S5] |
| Rain begins | Native 5 minute rain where available; station ID and time zone | First symptom time or explicit no symptom | First level rise and logger clock offset | Compare onset order; correlation alone leaves multiple causes [S3, S4] |
| Backup begins | Incremental and accumulated rainfall, with units | Actual entry opening, photo time, water-use status | Simultaneous U/C/D levels or "not measured" | Test whether the receiving sewer can accept discharge [S2, S9] |
| Investigation/intervention | Continue rainfall record | Cleaning, pump-out, gate operation and test volume/time | Immediately before/after levels; debris removed | Preserve causal evidence before the intervention changes it [S2, S12] |
| Recession | Rain end plus later rainfall | Time fixture stops spilling and use resumes | Level recovery and sensor health | Look for common or isolated recovery [S5, S7] |
| Follow-up | Comparable later wet event and dry comparison | Recurrence or no recurrence under stated conditions | Same access IDs, datum and settings | Verify the diagnosed failure mode rather than only camera appearance [S7] |
Mark unavailable event-time public levels “not measured.” A later dry manhole inspection belongs at its actual time.
No fixed rainfall depth establishes responsibility. Use the utility’s event definition and retain the actual rainfall distribution, antecedent conditions and response. Two storms with equal totals can produce different peaks because their intensity, duration and starting groundwater conditions differ.
How do you build an upstream-downstream level map?
Label the lowest connected opening F, building-side access B, downstream private access C, lateral connection J and public manholes U and D. Show branches, valves, pumps and verified flow direction; upstream and downstream refer to the network, not the street’s slope.
Bring all reference and water-surface elevations to one datum, retaining survey method and uncertainty. Measure a level below a surveyed rim by subtracting the vertical distance from that rim’s elevation. Different depth readings in pipes at different elevations cannot be compared directly. A sonde depth below local pavement is not automatically a surveyed pipe-invert elevation.
Use [lateral route and connection details](/field-guides/plumbing/sanitary-building-sewer-lateral-connection/) to establish construction context and [cleanout access and inspection direction](/field-guides/plumbing/plumbing-cleanout-requirements-access/) to identify which reach each observation represents.
Upstream-downstream level map
| ID | Location | Elevations/condition to retain | Deciding comparison | Evidence source |
|---|---|---|---|---|
| F | Lowest connected opening | Actual spill elevation, connection route, valve protection | Receiving head versus opening elevation | Site investigation [S9]; Anvilfield geometry |
| B | Building-side access | Invert/crown, water surface, time, building use | B versus C under known discharge | Above/below method adapted from [S2] |
| C | Downstream private access | Invert/crown, water surface, valve side, time | C versus J/main during event | [S2, S9] |
| J | Lateral-to-main connection | Confirmed connection location and elevation; utility record confidence | Available receiving head at connection | Ownership/map context [S11] |
| U | Upstream public manhole | Asset ID, invert/crown, water surface, time | U and D around suspected main restriction | [S2], p. 14 |
| D | Downstream public manhole | Asset ID, invert/crown, water surface, time | D versus U and lateral connection | [S2], p. 14 |
A bottom pressure sensor adds depth to its sensing elevation; an overhead ultrasonic sensor subtracts air distance from its face elevation. An invert-referenced export already contains its configured offset. Verify that reference before adding anything, or the offset can enter twice. The [ISCO 2150 Rev CG manual](https://www.teledyneisco.com/en-us/Water_/Flow%20Meter%20Documents/Manuals/2150%20Flow%20Module%20User%20Manual.pdf) and [ADS TRITON+ A18 manual, December 2025](https://cdn.prod.website-files.com/69e92d288bd88ddc695b1bff/6a707aa46d2fe099774ddf60_TRITON%2BManual.pdf) describe their respective setup and offset procedures.
The decision boundaries below are Anvilfield’s interpretation of the cited measurement and hydraulic sources.
Hydraulic decision boundaries
| Comparison | What the result supports | What changes the decision |
|---|---|---|
| Water elevation above the named pipe crown | Surcharge at that pipe section | Confirm crown geometry and level uncertainty; a node summary uses its own crown definition |
| Receiving head raised but still below the main crown | Downstream backwater can still constrain a low lateral | Lateral connection elevation, slope and demand decide the effect |
| Receiving head above the connected opening | Public head is sufficient to create spill potential through an open hydraulic path | Valve state, intervening restrictions, duration, losses and actual entry observations decide whether water reached it |
| Receiving head below the opening | Main head alone has not reached that opening at the recorded instant | Building discharge against backwater, a private restriction or an unrecorded peak can still produce overflow |
| High B level with low C/J level under the same demand | A restriction between accessible points is a testable explanation | Ordinary slope/flow losses also create level differences; compare the normal baseline and intervention response |
| Difference no larger than combined measurement uncertainty | The ordering of the two levels remains unresolved | Improve datum/control and sensor checks; report overlapping ranges rather than a precise cause |
Record spill-opening, finished-floor and manhole-cover elevations separately so the protection designer has the references needed for the locally adopted rule. A manhole cover is not a universal hard ceiling on head. [EPA SWMM 5.2, Appendix D, Junction Properties](https://www.epa.gov/system/files/documents/2022-04/swmm-users-manual-version-5.2.pdf) permits added surcharge head to represent bolted covers, among other applications.
Do not interpolate connection head from remote manholes across an unverified branch, pump, drop or obstruction. Label modeled J levels as calculated, retaining boundaries and calibration. When public event records are missing, document the private finding and request monitoring for the next event rather than filling the gap with a later reading.
How long and how often should levels be monitored?
[ADS’s current I/I guidance](https://www.adsenv.com/faqs-inflow-and-infiltration) seeks 6 to 12 meaningful wet-weather responses and says a minimum 90 day monitoring period is often needed for a basin study. Start emergency incident response immediately; simultaneous evidence can resolve an individual incident. Extend monitoring when the relevant season, storm response or occupancy pattern has not occurred.
Level, velocity, discharge and flow direction answer different questions. [EPA’s Smart Sewer Technologies guidance](https://www.epa.gov/npdes/smart-sewer-technologies) treats flow, level and rainfall as complementary monitoring channels, alongside condition and capacity assessment.
ADS warns that downstream backwater or restriction can raise a level-only monitor’s reading without establishing an I/I increase, so sewer depth alone should not be converted into a claimed rainfall-derived inflow and infiltration volume. The instrument comparison below also distinguishes manufacturer capability from installed-system accuracy.
Instrument differences that change interpretation
| Instrument/source edition | Verified capability or condition | What it changes in this investigation |
|---|---|---|
| Teledyne ISCO 2150, manual Rev CG, July 2024, Tables 1-5/1-6 [S6] | Pressure level span 0.033 to 10 ft; optional 30 ft; stated level accuracy ±0.01 ft for maximum nonlinearity, hysteresis and temperature error; velocity range -5 to +20 ft/s | Keep expected head in configured span; record signed velocity and installation orientation; instrument accuracy does not include survey/installation error |
| ISCO 2150, same manual [S6] | Typical minimum velocity-measurement depth 0.08 ft; velocity accuracy ±0.1 ft/s in -5 to +5 ft/s and ±2% of reading above +5 ft/s, in water with a uniform velocity profile and sound speed of 1,480 m/s | Near-zero velocity needs uncertainty-aware interpretation; negative range capability alone is not proof of reverse flow |
| ADS TRITON+ AV|Gated, manual QR 775027 A18, December 2025 [S8] | Bottom-mounted pressure range is 0 to 10 psi, with stated pressure-depth accuracy ±2.8 inches; ultrasonic depth reaches full pipe and pressure supports surcharge | Use the correct depth channel across the transition; this pressure accuracy alone exceeds the worked example’s small spill-head margin |
| ADS TRITON+ ParaFlow, same manual, description of surcharge sensors [S8] | Top-mounted surcharge-pressure channel works when submerged; its surcharge velocity channel measures only when the pipe is full | A dry top pressure channel cannot replace ordinary partial-flow depth; a gap across crown can be a channel/application issue |
| ADS I/I FAQ, undated current web version [S5] | Level-only Manning conversion in a manhole channel becomes unreliable above about one-third to one-half pipe depth as flow spills to the bench | Bench geometry controls this warning; it is not a universal pipe-capacity or surcharge threshold. Do not convert these high-water records into RDII volumes |
Follow the installed model’s manual for sensor position, operating conditions and channel selection.
The ADS TRITON+ A18 manual sets AV|Gated direction to Forward by default and provides bidirectional choices for reversal investigations. Select the mode appropriate to sensor orientation and retain that setting with the export. An export without negative values does not exclude reversal when the instrument was set to forward-only. Retain its minimum-velocity setting too: the manual explains that readings within the configured band around zero are stored as zero.
Retain manual level checks, sensor elevations, offsets, fouling observations, vent and desiccant condition, clock drift and data gaps. Report a missed peak as missing rather than presenting interpolation as a measured maximum.
What does CCTV standing water establish?
CCTV establishes visible condition during the run. Record inspection time, rainfall, building discharge, prior cleaning and downstream level with the video.
[NASSCO’s February 2019 sag guidance](https://www.nassco.org/wp-content/uploads/2021/02/NASSCO_TechTipsFeb2019_Web.pdf) calls for recording the beginning, deepest point and return to normal water level, while checking whether deposits or increased flow explain the apparent sag. Use that historical Tech Tip as interpretation guidance; use the contract’s specified current PACP or LACP program for formal coding.
Camera limitations
| Observation | Establishes | Does not establish | Resolving evidence/source |
|---|---|---|---|
| Submerged lens/turbid pool | Water obscured that part of the inspection | Condition of hidden invert; exact grade; cause of water | Repeat when visibility and downstream condition are known [S3, S10] |
| Local pool with visible return to normal | Local water-level pattern during the run | Contribution to the reported backup by itself | Stations, grade/elevation evidence, cleaning response and event levels [S10; Anvilfield interpretation] |
| Water persists to end of reachable run | Elevated water in the visible/reachable segment | A sag endpoint or receiving-main level | Document endpoint limit; obtain downstream access/utility data [S2, S10] |
| Roots, grease or deposits | Visible intrusion or obstruction at recorded station | That this was the only event cause | Before/after cleaning, controlled discharge and public boundary [S1, S3] |
| Clean dry-weather post-cleaning video | Visible condition after intervention | Absence of prior or future public surcharge | Time-matched event evidence [S7] |
| Elevated camera with apparently deep water and dry lens | Camera position and reported water level conflict | Confirmed sag depth | Recenter/reinspect and check submerged deposits [S10] |
Water height, occupied area and capacity are different quantities. Report submerged and untraversed lengths as unobserved.
The companion [camera inspection, footage and locating guide](/field-guides/plumbing/sewer-camera-cctv-inspection/) covers inspection technique. To test a sag explanation, repeat the same reach after cleaning, with low receiving head and building discharge stopped long enough for the line to drain. Confirm that continuing infiltration or an upstream user is not sustaining the water level.
A repeatable pool bounded by a return to normal level supports a local depression once downstream controls and deposits are excluded. Survey the invert at both endpoints and the low point, or obtain a calibrated longitudinal profile, to establish the depression’s depth, length and outlet control. A pool that rises and falls with the receiving sewer calls for downstream hydraulic investigation before grade repair.
Worked examples: what changes the repair decision?
Published NASSCO case: a disputed sag
NASSCO Tech Tips Edition 52, February 2019, describes an inspection reported at 80% water level with a dry lens and a camera high in the pipe. The reviewer attributed the apparent sag to unseen debris or obstructions. A camera at NASSCO’s nominal center position would have a submerged lens at that reported water level. The dry lens therefore calls for checking camera height and submerged deposits before accepting the sag interpretation.
Published sag case: inputs and results
| Input/result | Value | Provenance/meaning |
|---|---|---|
| Reported water level | 80% | Published case [S10] |
| Lens condition | No water visible on lens | Published case [S10] |
| Camera position | High in pipe | Published case [S10] |
| Nominal camera-center reference | 50% of pipe height | General guidance in [S10], not an observed position in this case |
| Published review conclusion | Unseen debris/obstruction rather than the reported sag | [S10] |
| Rainfall, public-main head, survey grade | Not reported in the published case | Obtain event log, level map and grade evidence for a repair decision |
| Repair-scope result | Investigate/clear obstruction and repeat condition assessment before assigning grade correction | Anvilfield application of [S2, S3, S10] |
Worked event heads: separate the scopes
Use one local datum and feet throughout. Anvilfield’s estimate inputs dated 2026-11-05 place opening F at 101.00 ft, main crown at J at 99.00 ft, B invert at 100.00 ft and C invert at 99.00 ft. B and C bracket the private restriction, with C downstream. The selected layout has an open connection and no backwater valve between these points.
Worked event-head comparison
| Input condition | B water elevation, ft | C water elevation, ft | J water elevation, ft | Calculated comparison and scope |
|---|---|---|---|---|
| Dry baseline under recorded building discharge | 100.20 | 99.20 | 98.50 | B is 1.00 ft higher than C under ordinary gravity flow; that difference alone does not prove a blockage |
| Same discharge with a located private obstruction | 100.90 | 99.20 | 98.50 | B rises 0.70 ft above baseline while C/J stay unchanged; investigate the bracketed private restriction |
| Same discharge after removal of that obstruction | 100.20 | 99.20 | 98.50 | B returns by 0.70 ft with an unchanged receiving boundary; cleaning addresses this restriction |
| Later wet event, building discharge stopped; entry at F recorded | 101.05 | 101.15 | 101.20 | J is 2.20 ft above the main crown and 0.20 ft above F; the event requires a public-side investigation and property-protection scope as well |
Anvilfield estimates head differences by subtracting elevations referenced to the same datum. For a pressure sensor, add corrected depth to sensing elevation to obtain water elevation; subtract crown elevation for surcharge head and opening elevation for potential spill head. The equations are H = z + d, h_s = H - z_crown, and h_f = H_J - z_F.
With Anvilfield’s selected total error bound of ±0.03 ft per compared elevation, the conservative error bound on a difference is ±0.06 ft. The spill-head difference therefore spans 0.14 to 0.26 ft. A difference of 0.02 ft under those bounds leaves the ordering unresolved. These error inputs include datum and measurement effects.
Select the measurement system to meet the comparison’s error budget. The ADS pressure-channel accuracy in the instrument table is larger than this example’s spill-head margin, so that channel alone would leave the small margin unresolved. Datum control and independent level checks must support the selected error bound before using it on a job.
Scope private cleaning separately from public investigation and protection. Utility U/D levels and operating records distinguish a main obstruction, pump failure and capacity limitation. A head gradient supports a flow-path explanation; signed velocity with correct settings and corroborating observations establishes actual direction.
Which flow-path hypothesis fits the observations?
Interpret full or empty cleanouts using their connection, valve side, timestamp and simultaneous downstream condition.
Flow-path hypothesis matrix
| Possible cause | Expected pattern | Competing explanation | Deciding evidence | Repair direction |
|---|---|---|---|---|
| Private lateral restriction | Building use raises B; downstream C/main can receive flow | Restricted valve or a missed main-level peak | Located obstruction plus upstream/downstream response to removal | Clean or repair confirmed private restriction |
| Public-main obstruction | Public head rises upstream of main restriction; D lower | Pump/capacity constraint farther downstream | Utility U/D observations and localized clearing response | Utility main maintenance/repair |
| Wet-weather network surcharge | Public head exceeds the named main crown during the event; lateral discharge constrained | Private rain entry plus lateral restriction | Utility event levels/flow and private condition at same times | Network investigation, I/I/capacity work and property protection |
| Combined private/public causes | Restriction remains after public head recedes; both event signatures | Cleaning performed during natural recession | Independent dry comparison and later wet-event data | Separate private repair from public-side/protection scope |
| Closed or fouled backwater valve | Building-side water rises while discharge is trapped | Correct closure against high public head, or an upstream obstruction | Gate state plus levels on both sides and continued building-use record | Stop discharge to the closed branch; service a fault only when established; review protection layout |
| Ejector/lift failure | Basin high; pump/power/alarm abnormal | Discharge backpressure or blockage | Pump run, power and receiving-level records | Pump/control/discharge correction |
| Groundwater or overland entry | Water enters slab/cove, doors or window wells | Sanitary overflow spreading across floor | Entry-path photographs plus independent sanitary observations | Foundation/site drainage or storm scope |
This matrix is Anvilfield’s diagnostic synthesis of [EPA cause categories](https://www.epa.gov/npdes/sanitary-sewer-overflow-sso-frequent-questions), [MIIA response guidance](https://www.emiia.org/writable/risk_management_resources/files/2017_sewer_tool_kit_7.6.17.pdf) and [utility investigation practice](https://prod.msdgc.org/programs/sewer-backup-sbu-program/sewer-backup-investigation/). Several supported rows produce several scopes.
A correctly closed [backwater valve](/field-guides/glossary/backwater-valve/) can trap the building’s own discharge. [Oatey’s fixture-use FAQ](https://www.oatey.com/faqs?page=18) explains that water cannot pass a closed device and can back up at the lowest drain. Record gate state and both sides’ levels before calling successful closure a valve fault.
Pump investigations need basin level, run status, power, alarms and discharge receiving conditions. Use the guides to [sewage ejectors versus groundwater sumps](/field-guides/plumbing/sump-sewage-ejector-pump-sizing/) and [lift-station operating evidence](/field-guides/plumbing/sewage-lift-station-design-pumping/) to define that scope.
Neighbor reports help define the affected area only when connectivity and opening elevations are known. A higher or protected house can stay dry beside a property affected by the same main event.
What tests establish a private restriction and verify cleaning?
Record accessible levels, reachable video and removed material before clearing when conditions permit. [MIIA’s June 2017 sewer-backup response guide](https://www.emiia.org/writable/risk_management_resources/files/2017_sewer_tool_kit_7.6.17.pdf) directs crews to check flow in manholes above and below the backup location, making the receiving sewer’s condition part of the investigation rather than an inference from the private camera video. Its procedure also calls for preserving the blockage material where possible.
[Middleton, Wisconsin’s current backup instructions](https://www.cityofmiddleton.us/901/Handling-Sewer-Back-ups) ask residents to contact the city before a plumber so staff can check the public main. Report promptly and coordinate the public check with private response. Give emergency mitigation priority over collecting a perfect record, and log what changed before investigators arrived.
Once overflow is controlled and the downstream path is available, record a controlled building discharge’s source, volume and duration, with levels before, during and after. Anvilfield’s field procedure is to choose a volume the known system can receive, assign an observer and set a stop level below the lowest connected opening before starting. Stop if levels approach that mark or drainage deteriorates. Match the test to the discharge associated with the complaint; passing a small faucet flow does not establish performance during a larger appliance discharge.
A prompt fall after clearing supports obstruction relief when discharge and receiving head are comparable. If public head is falling too, repeat a dry comparison under recorded demand. Choose the [cleaning method for the obstruction](/field-guides/plumbing/drain-cleaning-jetting-snaking/), recording removed material and the treated reach.
Reinspect continuously over the same stations and locate structural findings. Where a pool persists, obtain surveyed or calibrated profile evidence; footage and handheld locator depth alone do not establish excavation grade. Anvilfield’s diagnostic procedure excludes deliberate flooding, improvised plugging and unplanned pump-out; these change the hydraulic boundary and can create another spill. Verify wet-weather performance with event evidence even when a clean dry line passes its discharge test.
Which repair follows each evidence pattern?
Cleaning follows a removable obstruction; a structural spot repair follows a located defect and defined extent; grade correction follows verified profile failure. Lining addresses suitable structural or leakage conditions but does not reset an adverse pipe profile. Use [lining, bursting and excavation scope](/field-guides/plumbing/trenchless-sewer-repair-pipe-lining-bursting/) after establishing which condition requires correction.
A public restriction calls for utility maintenance or repair. A wet-weather network limitation calls for flow and capacity investigation, then the appropriate I/I, capacity or reliability work. [EPA’s overflow guidance](https://www.epa.gov/npdes/sanitary-sewer-overflow-sso-frequent-questions) distinguishes those control approaches. Jetting a private lateral cannot supply missing receiving capacity in a public sewer.
Backwater protection is a separate risk-control scope. Record valve model, served fixtures, access and layout, then identify the adopted code edition and local amendments before design. Use the local protection rule to identify which fixtures need protection and which branches can remain available during valve closure; retain the surveyed reference elevations in the design record. The [backwater protection layout guide](/field-guides/plumbing/backwater-valve-sewer-backup-protection/) supplies installation context; stop use of served fixtures while closure blocks their discharge.
Match acceptance to the repaired mechanism. Cleaning needs visible clearance and a documented discharge response; grade work needs geometry and acceptance records; pumps and valves need operational evidence. Wet-weather performance needs comparable event records. If the next storm is weeks away, accept the completed private deliverable and state the outstanding event observation separately.
Set maintenance intervals from deposits, root regrowth, loading and access. Record the weather and elapsed observation window when reporting “no recurrence.”
What evidence should go to the utility?
Request event observations for the missing interval, asset IDs, maintenance history, level/pump records, the maintenance boundary and a written finding.
Prompt reporting and damage-claim filing are separate clocks. [MSD Cincinnati’s current action page](https://prod.msdgc.org/programs/sewer-backup-sbu-program/ive-experienced-a-sewer-backup-what-do-i-do-now/) says to report as soon as possible and allows two years from the backup for a completed claim. Its [investigation page](https://prod.msdgc.org/programs/sewer-backup-sbu-program/sewer-backup-investigation/) describes typical dispatch within four hours, while the action page allows hours to days during major rain. Those are local program terms, not a national deadline or guaranteed appointment.
Field checklist: utility handoff
The owner or contractor completes this record and sends the public-side requests to the utility. Attach original files and identify revisions.
- ☐ Address/contact: ______; incident ID: ______; first symptom/report times and time zone: ______.
- ☐ Entry opening and affected rooms: ______; dated photographs/file IDs: ______.
- ☐ Connection sketch with B/C/J/U/D IDs: ______; valve and pump locations: ______.
- ☐ Datum and invert/crown/opening elevations: ______; measurement method and uncertainty: ______.
- ☐ Native level/velocity/rain exports: ______; resolution, clock offsets, gauge location and flags: ______.
- ☐ Pre/post video, access, direction and stations: ______; hidden segments and removed material: ______.
- ☐ Water-use, cleaning, pump-out, valve and controlled-test chronology: ______.
- ☐ Utility event conditions and interventions received: ______; requested but unavailable records: ______.
- ☐ Maintenance boundary: ______; current reporting and claim instructions: ______.
- ☐ Supported cause: ______; competing explanation: ______; next test and scope recipient: ______.
End with the supported decision. If the peak remains unknown, identify the needed public monitoring point and event coverage. Keep claims eligibility in the utility’s administrative record.
How should the investigation and repair be scoped?
Buy a defined investigation deliverable: a located obstruction, a complete visible-condition record, an elevation survey or synchronized event data. A camera-only visit answers a narrower question than a wet-weather investigation. Require the proposal to identify the reach inspected, the conditions captured and the decision its report will support.
Quote access, cleaning, full-reach CCTV and locating, elevation work, logger deployment, data review and repeat-event visits separately. Depth, inaccessible cleanouts, traffic control, monitoring duration and restoration change the work. Owner and utility permissions define instrument access.
Separate investigation from repair in the bid: specify reaches, access IDs, supplied utility records, monitoring channels, event coverage and reporting format. Define authorization and acceptance. [PorchRocket Bid Control](/bidcontrol/plumbing) surfaces public plumbing solicitations and early signals from utility budgets and capital plans for estimators pursuing sewer investigation and rehabilitation contracts.
Diagnostic scope and acceptance deliverables
| Work package | Specify before mobilization | Required result |
|---|---|---|
| Access and cleaning | Reach, access ownership, obstruction and emergency response | Access record, removed material and pre/post level response |
| CCTV and locating | Direction, stations, cleaning state and required endpoints | Continuous video, defect locations and explicitly unobserved lengths |
| Elevation/profile survey | Datum, point IDs and acceptable uncertainty | Comparable opening, invert, crown and level elevations; grade where needed |
| Event monitoring | Channels, sensor range/accuracy, clock, event coverage and access | Native exports, configuration, quality checks, rainfall and event comparison |
| Evidence packet | Record owner, utility contact and report format | Chronology, source files, supported cause, unresolved question and scope recipient |
| Repair verification | Failure mechanism and acceptance observation | Clearance, geometry or operational result plus any outstanding wet-event observation |
These are Anvilfield scope recommendations. Set the next authorization by the missing evidence: poor visibility needs another camera run under suitable conditions; an unknown storm peak needs event monitoring.
Who owns the work and signs off on the finding?
Maintenance boundaries follow local utility rules and acceptance records. [St. Louis’s backup guidance](https://msdprojectclear.org/customers/problems-tips/sewer-backups/) assigns the lateral, including its main connection, to the property owner. Right-of-way and property lines alone do not establish maintenance boundaries.
The contractor documents private conditions and scope; the utility documents public assets and findings; the permit authority governs adopted installation requirements. Funding and damage eligibility follow the applicable program. Use [separate investigation and repair allowances](/field-guides/plumbing/plumbing-estimating-takeoff/) in the estimate.
Reviewed November 5, 2026. Update log: 2026-11-05: Rechecked source editions and numerical claims; corrected Middleton attribution, clarified camera and sensor limits, added safety authorities and sag verification, and revised investigation deliverables.
How to cite this page: Anvilfield, Sewer surcharge vs private blockage: which evidence decides the repair?, 2026, https://anvilfield.com/field-guides/plumbing/sewer-surcharge-versus-blockage-diagnosis/
FAQ
Sewer surcharge or private blockage: what hydraulic evidence decides the repair?
Compare simultaneous levels across the suspected restriction and at the receiving main, then record the response to an intervention. The level map and worked event-head comparison show how to separate the scopes.
How do you tell sewer surcharge from a lateral clog?
A located lateral restriction with downstream receiving capacity supports private blockage. Event-time public head constraining discharge supports a public contribution; compare that head with the named main crown before calling it main surcharge.
What belongs in a rainfall sewer-backup log?
Record gauge location, units, time resolution and timestamp convention, plus entry opening, building use, valve or pump state, sewer levels and every intervention. Preserve original exports and align the comparison timeline to one stated time zone.
Does CCTV standing water prove a sewer belly?
No. Repeat the cleaned reach with low downstream head and building discharge stopped long enough for drain-down. Check continuing inflows, camera position and deposits; locate the pool’s beginning, deepest point and return to normal, then verify the profile before assigning grade repair.
Can a sewer main surcharge without rain?
Yes. A public blockage or equipment failure can raise main head in dry weather. EPA identifies these separately from excess wet-weather inputs.
Does a full cleanout mean the city sewer is blocked?
No. Interpret it with its location, valve side, timestamp and simultaneous downstream condition. A private obstruction or a closed valve can also raise cleanout water.
Can a sewer camera see defects below dirty standing water?
Conventional CCTV cannot resolve an invert hidden by opaque water. Report the obscured length and repeat the inspection when visibility and receiving conditions permit.
What evidence is needed before ending wet-weather sewer monitoring?
Capture the relevant dry demand, wet-weather response and recovery at the private and public points. Use the event-count and duration guidance in the monitoring section for basin I/I studies; an individual incident can be resolved sooner when simultaneous evidence establishes the cause.
Will hydro jetting stop public sewer surcharge?
Jetting removes a confirmed obstruction within its work reach. An unavailable public receiving sewer needs a separate utility diagnosis and scope.
Will a backwater valve stop a backup caused by my own water use?
A closed valve blocks forward discharge through its served branch. Continued fixture use can cause an internal backup behind a functioning valve; verify gate state and levels on both sides before ordering valve repair.
What if the city inspected after the water went down?
Keep that reading at its actual time, request event-time records and monitor the next event if the earlier public boundary remains unknown. A later clear main does not resolve a missed peak.
Can a private defect and public surcharge both cause the same backup?
Yes. Test the private restriction under dry conditions and compare receiving head during the wet event. Independent signatures support separate private repair and public investigation or protection scopes.
People also ask
Codes cited in this guide
This guide is written and reviewed against the published standards below. Always confirm the current adopted edition with the authority having jurisdiction.
Sources checked
- S1: US EPA, Sanitary Sewer Overflow Frequent Questions, current undated web version Distinct obstruction, I/I, sizing, maintenance and equipment causes; matching control categories. Checked 2026-11-05.
- S2: MIIA/Weston & Sampson, Proper Sewer System Management, June 2017, pp. 13 to 16 and Appendix D Incident intake, above/below manhole inspection, response documentation and preservation of removed obstruction. Checked 2026-11-05.
- S3: RCAP, Assessing Your Collection System with a Pipeline Camera System, July 24, 2023 I/I mechanisms and complementary metering, smoke, dye and CCTV investigation methods. Checked 2026-11-05.
- S4: USGS, Charlotte-Mecklenburg Hydrologic Network rainfall page, current web version Actual 5 minute rainfall network, station IDs and station-history caution. Checked 2026-11-05.
- S5: ADS Environmental Services, FAQs: Inflow and Infiltration, undated current web version 6 to 12 meaningful responses, often 90 days, sensor selection, level-only RDII limitations and manhole bench spill effects. Checked 2026-11-05.
- S6: Teledyne ISCO, 2150 Area Velocity Flow Module User Manual, Rev CG, July 2024, Tables 1-5/1-6 Storage intervals, depth/velocity ranges and conditions, calibration and installation limits. Checked 2026-11-05.
- S7: US EPA, Smart Sewer Technologies, current web version Combined flow/level/rainfall monitoring and distinction between condition and capacity assessment. Checked 2026-11-05.
- S8: ADS, TRITON+ Installation, Operation and Maintenance Manual, QR 775027 A18, December 2025 AV|Gated and ParaFlow channel limits; Appendix A pressure-depth accuracy; direction modes and near-zero filtering; offsets and installation checks. Checked 2026-11-05.
- S9: Metropolitan Sewer District of Greater Cincinnati, Sewer Backup Investigation, current undated web version Public/private/site investigation and typical four-hour dispatch wording. Checked 2026-11-05.
- S10: NASSCO, Identifying and Classifying a True Miscellaneous Water Level Sag, Tech Tips Edition 52, February 2019 Real 80% case, nominal center reference, sag endpoints and deposit/camera-position confounding. Checked 2026-11-05.
- S11: Metropolitan St. Louis Sewer District, Sewer Backups, current web version Explicit local private lateral/connection ownership and combined/separate system distinctions. Checked 2026-11-05.
- S12: City of Middleton, Wisconsin, Handling Sewer Back-ups, current undated web version Stop water use and contact the utility before a plumber for a public-main investigation. Checked 2026-11-05.
- S13: MSD Cincinnati, I've experienced a sewer backup. What do I do now?, current web version Prompt reporting, storm response delays, separate claims, two-year completed-claim period and local program limits. Checked 2026-11-05.
- S16: US EPA, Storm Water Management Model User's Manual Version 5.2, EPA/600/R-22/030, revised February 2022 Section 3.4 flow regimes; Section 9.2 node-surcharge reporting; Appendix D Junction Properties permits added head for bolted covers; modeling concepts, not a local repair requirement. Checked 2026-11-05.
- S17: Oatey, FAQs, current undated web version, question on using fixtures during backwater-device closure Correctly closed valve prevents forward fixture discharge, explaining backup behind a functioning valve. Checked 2026-11-05.
- S18: CDC, Safety Guidelines: Reentering Your Flooded Home, updated August 24, 2026 Sewage exposure and electrical precautions; isolate power from a dry position and use an electrician when access requires entering water. Checked 2026-11-05.
- S19: OSHA, 29 CFR 1926.1203, Confined Spaces in Construction, current regulatory text Construction employer duties for identifying confined spaces, evaluating permit spaces and preventing unauthorized entry. Checked 2026-11-05.
- S20: OSHA, 29 CFR 1910.146, Permit-required confined spaces, current regulatory text General-industry scope and workplace evaluation; separate from construction requirements. Checked 2026-11-05.