The Hidden Cost of FOG-Related SSOs (It's Not the Fine You Should Worry About)

Most people picture the wrong number when they think about FOG-related sanitary sewer overflows. They brace for a citation — a fine with a dollar sign on it, tied to one bad day. That's not usually how it goes. The real cost shows up later, when a pattern of FOG-related SSOs catches a regulator's attention. At that point, you're not writing a check. You're negotiating a consent decree.

What a Consent Decree Actually Means for You

A consent decree is a settlement, but it's also a court order. The EPA, DOJ, or your state environmental agency signs off, a federal judge approves it, and from that point forward it carries the force of law. It's not a one-time hit. It's a multi-year obligation with a judge watching.

This isn't hypothetical. Baltimore, the Metropolitan St. Louis Sewer District, Miami-Dade County, and Fort Smith, Arkansas have all had FOG named specifically in their consent decrees — usually meaning a formal FOG Control Program Plan submitted for EPA approval, an ongoing inspection and reporting schedule, and sometimes construction obligations tied to the capacity problems FOG helped create.

That's the real exposure. Not a fine on this year's budget. Years of federally mandated plans, reporting, and oversight that didn't exist before the pattern got noticed.

Why FOG Tends to Get Called Out by Name

In every consent decree we looked at, FOG wasn't lumped in with generic overflow language — it got its own named requirement, separate from I&I or aging infrastructure. That tracks with how FOG-driven SSOs tend to behave: they cluster in commercial corridors, spike around holidays when restaurant volume is highest, and keep coming back at the same manholes even after jetting, because jetting clears the blockage without touching the deposition problem underneath it.

Once your own incident reports start showing that shape, it's a hard pattern to wave off as incidental.

What FOG-related SSO Prevention Looks Like

The utilities that stay out of this conversation tend to be doing a few things differently:

• They're catching buildup before it blocks a pipe, not just running a jetting schedule that reacts once a call comes in

• They're not relying on restaurant compliance alone. Enforcing FOG rules on food service establishments matters, but it doesn't touch the grease that's already built up system-wide, including from sources no inspection program ever reaches

• They have something to point to. A documented, ongoing program is a very different answer to give a regulator than explaining a pattern after it's already shown up in your reporting
  

This is where a biological FOG control program earns its keep. Instead of chasing FOG downstream after it's already a blockage, treatment gets dosed upstream, so the grease and biofilm never get the chance to build up in the first place — across the whole system, not just the corridors with active complaints.

The Real Takeaway

The fine was never the number to watch. What matters is whether your FOG pattern reads like one bad stretch, or a system-wide gap. Your own SSO reports are already telling that story. The only question is whether anyone's read them that way yet.

Know Where You Actually Stand

Had more than one FOG-related SSO in the past few years? That's worth a hard look before someone else takes one. Talk to In-Pipe about a FOG risk review for your collection system. Find out where buildup is concentrated, and what a real prevention program could look like — before the pattern gets noticed for you.