Establish a grease trap/interceptor cleaning frequency and manifest recordkeeping practice that satisfies typical FOG program requirements
domain: epa.gov · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Check the local sewer-use/FOG ordinance for a mandated minimum cleaning frequency (commonly monthly for smaller indoor hydromechanical units and quarterly for larger outdoor gravity interceptors), since specific intervals are set locally and vary widely
Layer the jurisdiction's percentage-based trigger (commonly around 25% of liquid depth, see separate rule) on top of the fixed calendar minimum — service whichever comes first
Contract only with a hauler holding the required local/state registration or permit to transport grease trap waste
Require the hauler to leave a manifest or trip ticket for every service documenting the date, hauler identity/permit number, and approximate volume/waste removed
Retain manifests/logs on-site for the retention period specified by the local ordinance (commonly in the range of two to three years) and make them available on demand to inspectors
Adopt kitchen-level best management practices — scraping plates/pans before washing, dry-wiping cookware, and never using hot water, caustics, solvents, or emulsifying agents to clean the interceptor — to reduce required cleaning frequency and avoid emulsifying FOG into a form that passes through the device
Known gotchas
Cleaning-frequency minimums and manifest retention periods are set by the local FOG ordinance, not a single national standard — figures differ city to city and must be confirmed locally rather than assumed from another jurisdiction's rule
Using hot water, caustics, or emulsifying agents to 'clean' a trap can temporarily pass FOG through as an emulsion, causing a compliance violation and downstream line blockages even though the trap appears empty
A hauler's local permit and any state-level transporter registration are two separate requirements — confirm both before contracting for pump-out service
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?