Updated October 9, 2026

A 90-seat diner's grease trap sits off the back hallway, due for pumping by the calendar and about to get checked against its own history before anyone lifts the lid.

The grease trap visit, step by step

This diner pumps every eight weeks, and the stop is already on the route before the lunch rush ends. The visit looks simple from the curb. What makes the resulting record defensible happens in five moves, in order.

1. Pull the trap's history before opening the lid. Check the gallons and condition logged at the last two or three visits for this specific trap, not a route average. A trap that ran high and greasy last time earns a longer look at the hose connection and baffle before the first scoop comes out.
2. Measure before anything moves. Record the depth of the floating grease layer, the solids on the bottom and the total liquid depth. Those three numbers, not a guess, are what a city inspector or a customer's insurer can check against the last visit.
3. Pump and log the gallons as they come out. With CRO, drivers track gallons and capacity as part of the stop, supporting accurate billing and routing decisions, so the figure on the record is what the truck actually took on, not a rounded estimate written down later.
4. Inspect the empty trap and note its condition. Baffles, odor, a failing inlet tee or signs the trap is undersized for the kitchen's volume all belong in the notes, because they are what the next visit's history gets compared against.
5. Close the record before leaving the lot. CRO gives operators a driver app where photos, notes and a customer signature are captured on-site and attached to the job record, and the selected disposal destination ties to that same job record automatically, every time.

What the closed job record needs

Strip the visit down to what has to survive on paper or in an app, and a closed grease trap job record needs five fields, regardless of which city's form it eventually feeds:

• Date of service. Tied to the specific trap, not just the stop on the route.
• Gallons pumped. The measured figure from that visit, not a standing estimate for the account.
• Trap condition. What the operator saw at open and close, including anything that changed since the last visit.
• Disposal destination. Where the load went, tied to the job record rather than remembered after the fact.
• Signed proof of service. A customer or site signature plus photos and notes confirming the visit happened as recorded.

CRO gives operators FOG compliance reporting and grease trap performance tracking built on exactly these fields, so the same visit record that satisfies a restaurant customer's question is the one an operator hands to a municipal FOG program.

Reading a trap's history to judge pumping frequency

A calendar interval is a starting point, not the answer. The better read comes from comparing a specific trap's gallons and condition across its last several visits, the same history pulled at step one of the walkthrough above.

A trap that keeps showing up high and greasy before its scheduled window is up is telling the operator something a flat 30, 60 or 90-day interval will not catch on its own. A trap that consistently comes in low for its size may be a candidate to stretch, inside whatever minimum a city's FOG program sets.

This stays an operator call. CRO tracks the gallons and condition that make the comparison possible, but it does not score a trap or flag it as due for more frequent service; the read is the operator's, built from that trap's own record.

What a municipal FOG program actually requires

The federal floor behind every local rule

Every local FOG program sits on the same federal floor. The EPA's National Pretreatment Program is "a cooperative effort of federal, state, and local environmental regulatory agencies" built to "protect POTW infrastructure" and reduce pollutants reaching municipal sewer systems, with individual control authorities setting their own local limits underneath it. Within that framework, 40 CFR 403.5(b)(3) prohibits "solid or viscous pollutants in amounts which will cause obstruction" in a sewer system, and the EPA traces a large share of sewer blockages directly to restaurant grease. From there, enforcement is local: "more and more POTWs are addressing FOG discharges by imposing mandatory measures of assorted kinds, including inspections, periodic grease pumping, stiff penalties, and even criminal citations for violators," in the EPA's own description of current practice.

The stakes are real money. New York City currently sets its maximum penalty for a grease-interceptor violation at $10,000 per day, per violation, and routinely sends inspectors to check that interceptors are sized, installed and maintained correctly.

What local programs actually ask for, and why it varies by city

There is no single FOG report format every operator can fill in once and reuse everywhere. Three Minnesota cities alone show how much the form itself differs, and Texas, Connecticut and California each add a different layer on top.

A visit record built from gallons pumped, trap condition, disposal destination and a signed proof of service covers the fields every one of those programs actually asks for. Which form it goes on, how long the city wants it kept and whether a hauler needs a separate permit number stays a local question, worth confirming with the specific city or county before the first report is due.

Where CRO fits into the grease trap visit record

CRO gives operators FOG compliance reporting and grease trap performance tracking, gallon and capacity tracking for pump trucks, and a driver app where the selected disposal destination ties to the job record automatically, with photos and notes attached on-site. That turns the five-field record above into something the office can pull up for a restaurant customer's question or a municipal FOG request without rebuilding it from a paper ticket.

Two things stay outside that record and outside CRO. The exact format a specific city's FOG program wants, whether that is Rochester's depth-and-percent-full log or Austin's hauler manifest, is a local requirement an operator confirms directly with that city. And deciding which traps need a shorter interval is the operator's own read of a trap's gallon and condition history, not an automated flag inside the record.

For the fields a non-grease job record needs from pump-out to invoice, see how to track septic and liquid waste jobs from pump-out to invoice. For how dispatch decides whether a truck should unload before its next stop, see when a pump truck should unload before its next job.

Frequently asked questions

Sources

1. RapidWorks, CRO product page
2. RapidWorks, septic and liquid waste industry page
3. EPA, "Controlling Fats, Oils, and Grease Discharges from Food Service Establishments," EPA-833-F-12-003
4. EPA, National Pretreatment Program overview
5. New York City Department of Environmental Protection, "Disposing of Grease as a Business"
6. Connecticut Department of Energy and Environmental Protection, FOG Fact Sheet 6, Reporting and Record Keeping Requirements
7. City of Rochester, Minnesota, FOG Program Cleaning and Maintenance Log Sheet
8. City of West St Paul, Minnesota, Grease Trap/Interceptor Cleaning Log
9. City of Red Wing, Minnesota, FOG Program Cleaning and Maintenance Log Sheet
10. City of Austin, Texas, Grease Trap Maintenance requirements
11. Texas Commission on Environmental Quality, RG-389, grease trap and interceptor guidance
12. California Code of Regulations, Title 3, Section 1180.24, inedible kitchen grease manifest requirements
13. RapidWorks, "How to Track Septic and Liquid Waste Jobs From Pump-Out to Invoice"
14. RapidWorks, "When Should a Pump Truck Unload Before Its Next Job?"

About the author

Ellery Curran, Marketing Specialist, RapidWorks

Ellery Curran works in marketing at RapidWorks, a software company that serves waste, septic, and heavy equipment operations businesses. She focuses on content that helps operators evaluate and adopt field service technology.