How to track consent decree milestones and SSO reporting to avoid EPA penalties

In the US, a wastewater utility rarely ends up in federal court because of one bad storm. Regulators usually act after years of sewage spills, missed permit limits, or repeated failures to fix a sewer system that cannot handle the flow. By that point, residents may have seen wastewater in streets, basements, rivers, or creeks more than once.

Operators use two terms for these spills. When wastewater escapes from a sewer built only for sewage, they call it a sanitary sewer overflow (SSO). In older cities, engineers built one pipe to carry sewage and stormwater together. During heavy rain, operators may find that the untreated mixture has spilled through an outfall because the shared pipe could not hold it. They call that release a combined sewer overflow (CSO).

After a pattern of illegal SSOs or excessive CSOs, the Environmental Protection Agency (EPA) may enforce the US Clean Water Act. The Department of Justice (DOJ) represents the federal government in court, and a state environmental agency may join the case. If the parties settle, a federal judge enters their agreement as a consent decree. The utility then has to complete a long program of repairs, construction, monitoring, and reporting by dates the court can enforce.

A utility under a consent decree must look decades ahead while accounting for what happened an hour ago. St. Louis Metropolitan Sewer District agreed to spend about $4.7 billion over 23 years and complete hundreds of separate duties. Utilities commonly carry programs of this size for 15 to 25 years, and the parties agree penalties in advance for missed dates. The utility can incur a daily charge as soon as staff miss one report or milestone, without DOJ filing a new case.

Milestones years away, reports due in hours

Most utility staff are comfortable with the years-long side of the work. Engineers plan sewer rehabilitation, pump stations, storage tunnels, monitoring programs, and construction deadlines years ahead. Kansas City agreed to spend about $2.5 billion over 25 years, with a final compliance date of December 31, 2035. Program teams can see projects of that scale in a capital schedule, discuss them at progress meetings, and assign people to recover lost time.

Operators have far less time when an overflow occurs. They may receive a pump-failure alarm on Saturday night, or a crew may find sewage leaving a manhole after heavy rain. Operators need to establish when staff discovered the spill, where it went, how much escaped, and what crews did next. Under many permits and decrees, compliance staff must notify the regulator within 24 hours when an SSO could reach surface water and send a written report afterward.

Compliance staff must check the utility's National Pollutant Discharge Elimination System permit, consent decree, and state rules for the exact deadline. EPA proposed a uniform national SSO reporting rule and later withdrew it, so utilities cannot rely on one national timetable. Staff must follow the specific rules that govern their system.

Teams see how easily the long deadlines and the sudden ones pull apart during a wet weekend. Control-room staff may record a pump alarm in the supervisory control and data acquisition system. A field crew may describe the blockage in a work order. Another team may store flow readings and rainfall data elsewhere. If nobody brings those facts together quickly, the utility can clear the blockage and still miss the reporting deadline.

Capital teams face the same gap. Crews and project managers naturally focus on visible construction, but a design submission, inspection certificate, monitoring result, or interim target may have no site and no crew attached to it. Staff can finish the physical work and still miss a separate duty that proves completion.

Compliance staff should track both kinds of work in one living record. They should enter every milestone and reporting duty as its own item, with the relevant decree clause, due date, named owner, warning period, current status, and required evidence. When staff discover an overflow, they should add the event immediately and calculate its deadline from the rules that apply. The person responsible can then see how many hours remain while capital teams continue to manage dates years away.

Recording the evidence as work happens

Staff who wait for the semiannual report have to reconstruct months of work just before submission. They may have to search for a missing inspection, ask a crew to remember an old incident, or explain why two systems record different times for the same overflow.

Staff should assemble the evidence when the work happens. For an overflow, they may need the alarm time, flow readings, field notes, photographs, work orders, asset details, rainfall data, and proof that staff sent each required notice. For a capital milestone, they may need an approved design, an inspection record, a commissioning certificate, monitoring results, or a formal submission receipt.

Staff should be able to answer a skeptical reader's basic questions for each item. What did the utility have to do? Who owned the work? Which deadline applied? What happened? Which dated record proves it? Staff should resolve a conflicting timestamp or missing document while the people involved still remember the event.

Utilities also need this discipline for work that produces a result over time. Crews may find groundwater entering a sanitary sewer through cracked pipes and stormwater entering through faulty connections or damaged manholes. Operators call this extra water inflow and infiltration. A court may order the utility to reduce it by a set date, so staff must connect repair records and monitoring results to the target in the consent decree. Staff cannot prove that the utility achieved the required reduction with a list of completed repairs alone.

People need to keep the record current between reporting periods. The named owner should update progress, attach dated evidence, flag a likely delay, and ask for a decision while the utility still has time to act. Compliance staff can then review the evidence before they make a claim to the regulator. By the end of the reporting period, they already have the material they need.

How regulators judge compliance

EPA and state reviewers do not watch crews clear every blockage or inspect every construction site. They judge the utility through its notices, reports, and supporting records. DOJ may use the same material if the parties dispute compliance, and a federal judge may review it during enforcement. Citizen groups can also challenge a utility's account at a public meeting, as groups have done in Baltimore.

Staff need to satisfy a skeptical audience. They must show when an overflow began, how they classified it, when crews responded, and when they sent each notice. If a utility claims that it completed a milestone, staff need to connect the claim to the exact clause and the evidence required by that clause. The utility may still face a finding after an on-time repair if nobody can prove when the work happened.

The parties call the pre-agreed charges in a decree stipulated penalties. Utilities commonly face about $1,000 to $50,000 per event per day when an SSO reaches surface water, depending on the decree, duration, or volume. They commonly face about $500 to $2,500 per day for a missed milestone or a late or deficient report, and some decrees increase the amount as the breach continues. Staff must use the schedule in their own decree because the parties negotiate each one separately.

Staff can prevent these penalties when they connect each claim in one current record to a person, a date, a governing clause, and the underlying evidence. They can also find problems while the utility still has time to fix them. A program manager can escalate a delayed design submission. An operator can correct an overflow classification before the notice period closes. A compliance lead can reject an unsupported completion claim before it reaches EPA.

When the court changes the schedule

Over a program that lasts two decades, utility leaders may need to change the construction plan. They may ask for more time to protect ratepayers from unaffordable increases. They may want to sequence CSO, SSO, and stormwater projects through an integrated plan. Engineers may propose rain gardens, permeable pavement, or green roofs for part of the work that a previous plan assigned to tunnels or storage.

The parties can negotiate a modification, and the court must approve any change to the binding schedule. DC Water plans to spend about $2.6 billion on its Clean Rivers program and build about 18 miles of deep tunnel. The court moved its final compliance date from 2025 to March 23, 2030. Lexington sought an extension to its SSO schedule in 2024, while Hartford and Youngstown pursued changes in 2025.

Once a judge approves a change, compliance staff must rebase every affected project, deadline, report, and evidence requirement. They should preserve the previous order, record the modification's effective date, and connect completed work to the version in force at the time. Otherwise, staff may prepare a report against an expired deadline or assess older work against a requirement that did not yet apply.

Utilities avoid EPA penalties when their staff manage the court order as a living obligation. Staff should connect the capital program, each fast overflow report, the evidence behind every claim, and every court-approved change in one current record. They can then see the next duty soon enough to meet it and prove what the utility did when regulators, DOJ, the court, or the public asks.