Building a Municipal FOG Control Program That Doesn't Rely on Restaurant Compliance Alone

Ask most municipalities what their FOG program covers, and you'll get the same answer: grease trap ordinances, restaurant inspections, interceptor sizing requirements. That's real work, and it matters. It's also, by definition, only looking at one source of the problem.

What a Restaurant-Only Program Actually Covers

FOG control ordinances are built around Food Service Establishments — that's the language in nearly every municipal FOG program on the books. Grease interceptors get sized, inspected, and enforced for restaurants and commercial kitchens. If a restaurant falls out of compliance, there's a permit, a notice of violation, sometimes a fine attached to it.

What that structure doesn't touch: <cite index="10-1">EPA's own Report to Congress on sewer overflow causes names restaurants, homes, and industrial sources together as FOG contributors</cite> — not restaurants in isolation. Every pour of bacon grease down a residential drain, every household that skips a "no grease" reminder, adds to the same collection system a restaurant compliance program is built to police. None of it shows up in a food service inspection.

Even the Covered Sources Aren't Fully Covered

Restaurant compliance has its own gaps, separate from the residential blind spot. In at least one jurisdiction we found, the utility identified a 73% non-compliance rate with its own grease trap ordinance among the restaurants it was supposed to be regulating. That's not a program failing to reach outside its scope — that's a program not fully catching what's already inside it.

Put those two gaps together, and the picture gets clearer: a restaurant compliance program, even running well, is enforcing rules on a subset of a subset of what's actually going into the collection system.

What a Full-System Program Adds

None of this is an argument against restaurant compliance — keep the inspections, keep the interceptor requirements, keep enforcing the ordinance. The gap is what happens after FOG from any source, restaurant or otherwise, is already in the pipe.

That's where a biological, upstream approach fits differently than an inspection program. It doesn't replace grease trap enforcement — it addresses what enforcement structurally can't reach: FOG that's already made it into the collection system, regardless of where it came from. Treatment dosed at the collection system level doesn't check a food service permit before it works.

One clarification worth making directly: this isn't the same as an additive poured into a grease trap. Some municipal ordinances specifically restrict biological additives inside traps without written approval — that's a trap-level rule. Collection system dosing operates downstream of that, treating the FOG that's already moved past any interceptor, from any source.

What This Looks Like in Practice

A municipal FOG program built around both layers typically includes:

• Restaurant compliance enforcement, unchanged — interceptor sizing, inspection schedules, permit requirements

• Collection system-level treatment, addressing FOG regardless of source, including the residential and industrial contributions restaurant ordinances were never built to catch

• Monitoring that reflects total system load, not just permitted-source compliance rates

The utilities dealing with recurring FOG-related blockages despite a functioning restaurant program are often looking at exactly this gap — a compliance structure doing its job, on a problem that was never fully inside its jurisdiction to begin with.

See the Gap in Your Own System

If your FOG-related maintenance calls keep showing up outside your permitted restaurant list, that's not a compliance failure — it's the structural blind spot doing what it always does. Talk to In-Pipe about a collection system FOG assessment and see what's building up outside your current program's reach.