To track overdue grease trap pumping customers, in DynoRoute or any other dispatch system, you need three things: a recurring service interval for every trap, automatic flags on past-due accounts, and automatic reminders tied to local FOG rules.
An account is overdue when its last service date plus its interval is earlier than today. That one calculation should drive the board, so nobody has to remember who is late. A recurring schedule set once per trap also prevents missed appointments, because visits come up on a cycle instead of being booked by hand. The plan then has to respect what the truck can hold.
You’re probably reading this because a deadline got close, or got missed. Maybe a customer called after an inspection with a violation notice in hand, wanting to know how the trap they pay you to service ended up over the limit. That call is the worst version of this business, because the fine is theirs and the fault, in their eyes, is yours.
I build route planning software for vacuum-truck fleets, and I’ve spent this year interviewing the operators who run them: grease collectors, used-oil haulers, septic pumpers. The ones who never make that call run some version of the same system. The accounts that slip are almost never the ones on this week’s list. They’re the failed stop nobody re-routed, the overdue entry that turned out to be a lost customer, and the will-call that arrived mid-route.
1. Set a Recurring Interval for Every Trap
Every trap needs its own service interval. Most commercial traps end up somewhere between monthly and quarterly, but local rules can set the outer limit. Butler County, Ohio’s FOG rule, for example, requires grease interceptors to be pumped at least every 90 days unless the county approves a waiver. Use the table below as a starting point, then let the local ordinance and your pumped volumes set the real number.
| Example interval | When it fits |
|---|---|
| 30 days | The trap reaches the quarter-depth limit (grease and solids at 25% of its liquid depth) in about a month, or the local FOG program requires monthly service |
| 60 days | The trap stays under the rule at 30 days but not at 90 |
| 90 days | The trap is still under the rule at the 90-day visit, and the ordinance allows that gap |
- Recurring schedule: Set the cadence once per trap (for example monthly, every 60 days or quarterly) so visits dispatch on a cycle instead of being booked by hand. The dispatcher still reviews the board before the trucks roll.
- Trap-level tracking: Track gallons, condition notes and service dates per trap, not only per customer. A site with several devices can carry several due dates, and per-trap records keep them apart.
- Mixed cadences: Track trap pump-outs, interceptor cleanings and drain line jetting separately. One account date can hide a late interceptor behind an on-time trap.
- Interval upkeep: Kitchens change menus and volumes, so an interval set at signup drifts. One grease-collection operator I interviewed moves accounts from four-week to six-week cycles when the truck keeps coming back half-empty, and tightens them when a trap keeps hitting the quarter-depth limit early.
An interval that’s too long is a violation being scheduled in advance. For a deeper look, see how to set cleaning frequency across an account book.
2. Let Completed Jobs Recompute Next-Due Dates and Flag Overdue Accounts
Keeping deadlines takes a counting system, not a calendar. Log the completed pump-out and the next due date recalculates from that job, early or late, so the trap stays on the right cycle. Any account past its date then lands in an overdue queue without anyone asking for a report.
How does a weeks-to-go counter work?
Give every account two numbers: its service interval and the weeks remaining until it’s due. Zero means due this week. Negative means late.
The grease-collection operator runs his whole book this way, with a weekly report that surfaces everything at zero or below. In his words, when an account shows three weeks late, “something’s going on here that we need to find out.” The counter turns deadline management from remembering into reading.
What should the status tiers be?
Use three tiers on the board. The 14-day line is an example, so set yours to match how far ahead you plan routes.
| Status | Example rule | What the dispatcher does |
|---|---|---|
| Current (green) | Due date is more than 14 days out | Nothing yet |
| Due soon (yellow) | Due date is within 14 days | Send reminders and place the stop on a route |
| Overdue (red) | Due date has passed | Triage it and work the escalation ladder |
How do you keep the overdue list honest?
An overdue list only protects deadlines if the entries are real. The operations lead at a national grease-trap and used-oil collector put it bluntly when we walked through his overdue report: “these overdues aren’t necessarily real… They may be lost customers. They may be ones that we were into once and just never went back.” A list full of dead entries trains dispatchers to ignore it, and the one genuinely late account scrolls past with the rest.
Triage the list weekly and give every overdue entry one of three labels:
- Schedule it: The account is real and late.
- Fix it: The interval or the record is wrong.
- Close it: The account is gone.
He also flagged the opposite failure. Customers overstate their volumes at signup to win better pricing, which sets intervals too short and floods the due list with stops that don’t need service yet. Verify intervals against pumped gallons, not against what the customer said at the kitchen table.
3. Send Reminders Before the Due Date, Then Escalate
Automated reminders should go out before the due date, and a set ladder should take over after it. Reminder timing varies from shop to shop. For example, you might send reminders 14, 7 and 3 days out, or 7, 3 and 1 day out. Pick one pattern and use it across your whole book.
- Pre-due reminder: Send an SMS and email 7 to 14 days before the due date.
- Visit confirmation: Confirm the service window 24 to 72 hours before the truck arrives.
- Site access: Ask about gates, lids and parking in the same message. A locked gate found in advance doesn’t become a failed stop.
Once an account goes past due, work the ladder. These day bands are examples, not a standard.
| Days past due (example) | Action | Who owns it |
|---|---|---|
| Day 1-3 | Automated notice and a call or text offering the next route slot | Dispatcher |
| Day 7 | Direct call to the account contact, plus a written note of the missed date | Dispatcher or office lead |
| Day 14+ | Formal notice, and the account goes on the ops manager’s review list | Ops manager or owner |
4. Tie the Schedule to Local FOG Rules, the Quarter-Depth Rule and Per-Visit Records
Missed service is a regulatory problem before it’s a scheduling one, and regulators often reach an overdue account before the hauler does. Anchor each interval to the local rule, then keep records that prove you met it.
There is a reason cities push so hard on pump-outs. The U.S. Environmental Protection Agency’s FOG fact sheet for food service establishments cites its Report to Congress, which found that “grease from restaurants, homes, and industrial sources are the most common cause (47%) of reported blockages.” The same fact sheet says food service establishments “must be diligent in having their interceptor/collector devices serviced at regular intervals.” Your schedule is how your customers meet that rule.
What is the quarter-depth rule?
The quarter-depth rule says to pump when combined grease and solids reach a quarter of the trap’s liquid depth. Many municipal FOG programs use it, but the customer’s local ordinance governs. Where a program publishes compliance lists, cross-reference them against your accounts.
What does a missed pumpout cost?
A missed grease trap service costs three parties, in sequence: the customer eats the citation, you eat the emergency response and the trust damage, and the account often doesn’t survive the year.
- The citation: Fines are set locally and can be steep. Under the Butler County rule above, the county may fine up to $10,000 per day, per violation, on top of noncompliance fees.
- The permit: Repeat problems bring tighter control. The same rule lets the county put a non-compliant restaurant under a FOG discharge permit, with its own conditions and an annual fee.
- The clock: Deadlines after a finding are short. In Butler County, a restaurant has 15 days after a Notice of Violation to fix the problem. An interceptor found over the limit must be serviced within five business days, and immediately if there is an overflow or blockage.
- Your ledger: You take the after-hours emergency pump-out at cost, you risk a multi-location account moving all its traps to a competitor, and you may end up with a former customer who tells the story of the year they got fined.
Take an illustrative account: a restaurant on a monthly service contract, worth a year of recurring revenue and likely several times that over its life. Against that, keeping room on the routes for reattempts (a reattempt lane) costs a stop or two of route time per week, and weekly overdue triage is an hour of office work. Those are round illustrative numbers, but every operator I’ve interviewed describes the same lopsided math.
What should you log at each stop?
When the inspector arrives, your customer’s defense is your paperwork. Records hold up best when they’re created at the stop, with photo proof, by the driver. Log these for every visit:
- Service date and time
- Trap ID
- Gallons pumped
- Grease and solids depth
- Hauler identity
- Disposal site
- Timestamped photo and technician notes
Keep signed pump-out logs per stop. Some programs also want logs sent in. Butler County, for example, asks restaurants with a grease trap to submit a maintenance log once a month.
One accountable person: Name one person who confirms and documents each visit. When everyone owns the confirmation, nobody does.
5. Turn the Overdue List into a Route: Capacity, Disposal Trips and Who Goes Where
A full truck is why an overdue list stays overdue. Flagging a late account only gets it on the list. The dispatcher still has to fit that stop into what the vacuum truck can hold, and if the plan ignores the tank, the last stop drops and the account stays red. So build the day around what each vacuum truck can hold, not only the shortest drive.
- Fill limit: Set the tank level that sends each truck to unload, leaving some room for a trap that runs heavier than expected.
- Disposal run: Place the unload inside the route. Plan capacity limits by truck, expected gallons by stop, and receiving-site returns before the truck leaves the yard. Scheduling around disposal site cutoffs covers the timing.
- Worked route (illustrative numbers): Five pump-outs of 600, 700, 650, 550 and 750 gal need 3,250 gal in total, against a 2,800-gal truck. That’s 450 gal over capacity. The first four stops add up to 2,500 gal, which fits. Insert an unload after stop four, and the truck starts stop five empty with room for its 750 gal. All five get done, as long as the extra disposal trip and the site’s opening hours still fit the shift.
- Stop order: Start with the basics of how to plan grease trap pumping routes, then group overdue stops by area so one late account doesn’t take a truck across town alone.
- Who goes where: DynoRoute’s AI Dispatcher recommends a truck and driver for each job based on capacity, location, availability, workload, travel time and skills. Each suggestion shows a confidence score and its reasons, and conflicts such as double-bookings or not enough travel time get flagged. The dispatcher accepts, rejects or reassigns it. More on this in dispatching grease trap service trucks.
- Auto Mode: This is optional. It lets some suggestions go through automatically, within guardrails you choose and test.
Want to talk through your own book and trucks? Book a 30-minute intro call to go over fit and pricing.
How to Stop Missed Grease Trap Pumping Appointments: Why Booked Stops Get Dropped and How to Recover Them
Most missed services aren’t about forgetting. A recurring schedule, confirmations and logs prevent a lot of them. But they don’t explain why a stop that was already booked still gets dropped on the day.
Why do booked stops get dropped?
- Full truck: The tank hits its limit before the route ends, and the remaining stops roll to another day.
- Truck down: The day’s stops have no truck until someone re-splits them across the fleet.
- Driver out: The route is intact, but nobody qualified is assigned to run it.
- Canceled slot: A customer cancels, the slot sits empty, and a nearby overdue stop stays on the list.
- Locked gate: A locked gate, blocked interceptor lid or “come back later” fails the stop, and the truck moves on.
- Low-volume stop skipped: A small stop gets pushed because it doesn’t look worth the trip, until the customer calls.
What does the recovery protocol look like?
Every dropped stop needs a trigger, a decision and a move.
- Trigger: A job runs past its expected end by more than the number of minutes you allow. A canceled slot is also a trigger.
- Who decides: The dispatcher. In DynoRoute, recovery agents suggest a fix for a late-running job or a job to fill a canceled slot, and the dispatcher approves it unless Auto Mode is on.
- What moves: The later stop goes to another truck, an unassigned job fills the open slot, or a failed stop goes into the reattempt lane.
A small example, with illustrative times: A stop should finish at 10:00, and your late limit is 15 minutes. At 10:15 it’s still running, so the system prompts a recovery. The next stop on that route is already overdue. The dispatcher sees a suggested reassignment to another truck, checks it, and approves or changes it.
What should happen to a failed stop?
A failed stop is a missed deadline in progress. Unless something forces a reattempt, that account drifts past due while looking serviced in everyone’s memory. The grease-collection operator described this loop: fifteen stops planned, three failed, “and we need to take those three stops and get them back on another route again… We don’t want to send them out and fail again the second time or the third time. And right now, sometimes we do.”
Two rules break the loop:
- Failed stops go into a same-week reattempt lane with their own slot on a route, not a spot at the back of the queue.
- Every failure gets a recorded reason, so the reattempt doesn’t fail the same way. If the gate was locked at 10 AM, the reattempt goes out at 7.
That operator budgets a fixed overhead per stop, which makes a reattempted failed stop cost about twice a clean one. A failed stop that never gets reattempted can cost the whole account.
Which numbers should you watch weekly?
Watch four numbers. Keep the first, second and fourth at zero, and push the third as high as it goes.
- Accounts at negative weeks-to-go
- Failed stops older than seven days
- Reattempt success rate
- Services completed without a record
Grease Trap Pumping Missed Service Prevention Software: Spreadsheet vs Field-Service Software vs Capacity-Aware Dispatch
A spreadsheet works until several problems stack up at once: an out-of-date overdue list, a failed stop nobody rebooked, and an interval that no longer fits the trap. Here is what each option covers and where it stops.
| What you need | Spreadsheet | Field-service and pumping software | Capacity-aware dispatch (DynoRoute) |
|---|---|---|---|
| Recurring schedule | Someone carries each next date forward | Recurring contracts and intervals are common features | Weekly, biweekly, monthly, quarterly or custom cadence |
| Overdue flags and reminders | Only as current as the last update | Commonly built in; check how they surface | Due, unscheduled and overdue work shown to dispatch; SMS and email automation |
| Truck capacity | Not modeled | Varies by product | Plans around each truck’s gallons, up to a threshold you set |
| Disposal trips | Not planned | Varies by product | Built into the route, including sites away from the home yard |
| Late job or canceled slot | Phone calls and the whiteboard | Varies; some show late or missed jobs in real time | Recommends a fix or a gap-filler; the dispatcher approves |
| Manifests | Kept separately | Some products generate FOG manifests | No native manifest generation; captures gallons, disposal details, photos and signatures for your records |
| What it takes to adopt | Someone owns the upkeep | Setup and pricing vary by vendor | Quote on a 30-minute intro call; flat monthly plans with usage credits; month-to-month, no setup fee, no per-seat fees; drivers use iOS or Android phones |
What do the pumping and field-service platforms cover?
Each description below reflects what the vendor says on its own site (checked November 4, 2026). Get pricing and plan limits from each vendor directly. For a fuller comparison, see our grease trap software comparison.
- Essential: Due dates that update from completed work, mixed cadences tracked separately, and technicians logging depth measurements, photos and disposal details by phone.
- PumpDocket: Dispatch and field closeout on every plan. Recurring scheduling with reminders, and FOG manifests, start on its Team plan.
- Tank Track: Automatic service-due reminders by text and email, and waste manifest reports created as work is completed. Built for septic, grease trap and portable toilet operators.
- QuoteIQ: Recurring route scheduling, route optimization, job-completion photos and automated invoicing. Its own roundup says it does not generate FOG-specific regulatory manifests.
- ServiceCore: All-in-one software for liquid waste businesses, with auto-reminders for recurring service contracts, real-time updates for late or missed jobs, and automatic FOG disposal manifests. Sold through a demo, on an annual contract.
DynoRoute, best for: Hauling fleets whose day is limited by what the truck holds, not by miles. DynoRoute’s grease trap software is a planning tool the dispatcher reviews and signs off, not a replacement for the dispatcher. It uses flat monthly plans quoted on an intro call; see how DynoRoute pricing works.
What else should you check in any tool?
Run four more checks. A tool that can’t do one of these leaves that hole open.
- Failed-stop handling: A failure reason captured at the stop, and a reattempt that must be scheduled, not remembered.
- Records created at the stop: Timestamped, geotagged photo proof and gallons pumped attached to every visit.
- Interval evidence: Pumped-volume history per account, so cycles are set from data.
- A customer-facing trail: Service history you can hand an account manager or an inspector.
Whatever you evaluate, watch what it does with a failed stop. That is where deadlines actually die.
Three Questions to Ask About Your Own Operation
- How many trucks do you run, and is the work grease only or mixed with septic or used cooking oil?
- Do you need manifests generated natively in your dispatch tool, or does your current manifest process work?
- How many stops do you lose per week to a full or down truck?
Frequently asked questions
What makes a grease trap account overdue?
An account is overdue once its service interval has run out without a visit, meaning the last service date plus the interval falls before today. A weeks-to-go counter makes this easy to read: zero means due this week and a negative number means late. Not every overdue entry is a genuinely late account, because some are lost customers or have a wrong interval or record.
Why should service intervals be set from pumped gallons instead of what the customer says?
Customers sometimes overstate their volumes at signup to get better pricing. This produces intervals that are too short, so the due list fills with stops that don’t yet need service. Setting cycles from each account’s pumped-gallon history keeps intervals based on data rather than on what the customer claimed.
How do you know if a grease trap is full?
A grease trap is due for pumping when the combined grease and solids layer reaches a quarter of the trap’s liquid depth. Recording grease and solids depth at every stop shows how fast each trap fills. That history lets you tighten or lengthen the trap’s service interval.
What should grease trap cleaning software track per trap?
Track records per trap, not only per customer. At minimum, that means service dates, gallons pumped, condition notes, grease and solids depth, hauler identity, disposal site and a timestamped photo. A site with several devices can then carry several due dates, and a late interceptor can’t hide behind an on-time trap.
How do I start tracking overdue grease trap accounts this week?
Start with three steps: give every trap a service interval, log each completed pump-out so the next due date recalculates from that job, and pull every account at zero or negative weeks-to-go into one list. Then give each overdue entry one label: schedule it, fix it or close it. Add reminders and an escalation ladder once the list is trustworthy.
What is the fastest way to work down a backlog of overdue accounts?
Triage first, so only real, late accounts remain. Then group the overdue stops by area so a late account doesn’t send a truck across town alone, and size the day to what the tank holds, with a disposal trip planned before the last stop. Put any failed stop into a same-week reattempt lane with its own route slot.
What is the fine for not pumping a grease trap?
Fines vary by city and severity. Some rules allow fines per day: Butler County, Ohio, for example, can fine up to $10,000 per day, per violation. Repeat problems can also lead to tighter permit conditions. The fine goes to the food-service establishment, not the pumping company, which is exactly why missed service costs operators accounts rather than money.
Who enforces grease trap pumping requirements?
Often two authorities at once: the local wastewater utility (or sewer district) running the FOG pretreatment program, and the health department through food-safety inspections. Each can run its own inspections on its own schedule, so a restaurant can pass one inspection and still get a FOG citation from the other.
How long do grease trap records need to be kept?
It depends on the local rule, and the customer’s ordinance governs. Three years is a common minimum. Butler County, Ohio, for example, requires restaurants to keep pumping manifests, receipts and invoices for at least three years and show them to an inspector on request. Some places also want the latest record kept on site. Keeping complete digital service records for every stop covers most cases. Our grease trap manifest requirements guide covers contents, copies and retention.
What should a grease trap service record include?
At minimum: service date and time, gallons pumped, the hauler’s identity, and the disposal facility that received the waste—plus, in practice, a timestamped photo and the technician’s notes. Records created at the stop, rather than reconstructed later, are the ones that hold up when a customer needs to prove service history to an inspector.
