Confirm whether a POTW prohibits chemical, enzyme, or bacterial additives used to break down FOG in grease interceptors
domain: portland.gov · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Check the specific POTW's sewer-use or FOG ordinance directly (many explicitly prohibit adding chemicals, enzymes, bacteria, solvents, or emulsifiers to a grease interceptor) rather than assuming a blanket national rule, since this is set locally
For a live example, review Portland's Administrative Rule under its sewer/FOG code (Portland City Code Title 17 grease provisions) or Phoenix's published FOG Best Management Practices manual, both of which state such additives are prohibited
Understand the technical rationale typically cited: enzymatic/bacterial breakdown of FOG is often reversible, allowing free fatty acids to re-combine with glycerol downstream and re-form FOG that passes through the interceptor into the sewer rather than being removed
Confirm whether use of a prohibited additive disqualifies the facility from any local sewer-rate reduction, waiver, or variance program the utility offers, since some ordinances tie additive use to loss of such benefits
Verify enforcement mechanism (fines, permit revocation) and any required disclosure of cleaning products/additives used, per the specific ordinance
Known gotchas
This is a local-ordinance-level prohibition, not a single uniform EPA or national plumbing-code rule — the exact prohibited-substance list and penalties differ by POTW and must be confirmed against the specific utility's code
Some additive products are marketed as 'compliant' or 'natural' but still fall under a broad ordinance prohibition covering any chemical, enzyme, or bacterial agent intended to dissolve or emulsify FOG — read the ordinance's actual definition rather than trusting product marketing
Using a prohibited additive can retroactively invalidate maintenance records if an inspector determines the interceptor was not being properly maintained, since the FOG appeared removed without being physically extracted
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?