HomeIndustriesPortable Toilets
Every portable toilet runs on its own pump-out schedule
A job site that opens Monday, a festival that needs a pump-out every single day, a customer who swears their unit hasn't been serviced all week — this business doesn't run on one schedule stretched across the whole fleet. OpsNode tracks every unit individually, from delivery to pickup.
One fleet, as many rhythms as job sites
Demand doesn't follow a single calendar. A civil engineering site keeps its units for months with a weekly pump-out; a residential site keeps them for a few weeks; a festival needs a pump-out every day for its duration, then nothing at all. A single contract can cover ten sites that have nothing in common on frequency — except the truck that has to hit every one of them without mixing up the rhythm.
Fixed days matter too: some general contractors demand a visit precisely on Tuesday and Thursday, not "roughly twice a week." Others are fine with a floating interval as long as the frequency holds. A unit delivered mid-month inherits the site's service schedule — not a generic timetable reset at random.
And there's the question every superintendent or event organizer eventually asks: "was it actually pumped out this week?" Without a verifiable record, it's your word against theirs — and it's rarely the rental operator who gets the last word.
The data model covers the business, not just the contract
Every capability below exists because a real portable toilet on a real job site demands it — not because generic rental software needed a checkbox for it.
Per-unit service schedule
Weekly pump-out on the unit at job site A, twice a week on the one at job site B, daily for the length of a festival — with fixed days (Tuesday and Thursday) when the general contractor requires it.
Set unit by unit, not contract by contractVisits generate themselves
Once the schedule is set, future visits appear on their own and group by address — a job site with five units doesn't turn into five separate truck stops.
No manual route entryNo unit ever double-booked
Availability is calculated by date, directly in the database. Two overlapping rentals on the same unit are blocked before they can even be confirmed.
Enforced at the database level, not the interfaceRoutes on the real road network
Stop order follows the actual road network, not a straight line on a map. The driver runs the route in the order job sites actually appear on it.
Calculated on the real road networkThe truck keeps working offline
On a job site with no cell coverage, the driver's app keeps its stops queued locally and resyncs the moment signal comes back — without ever duplicating a visit already completed.
Local queue, resync with no duplicatesA swap in a single stop
A dirty unit that needs replacing mid-rental? Picking up the old one and dropping off the new one is scheduled as a single truck stop, not two separate visits.
Planned swap, one trip"It got pumped out" isn't enough anymore — you have to show it
Every visit follows a checklist specific to its type, with conditional steps — a unit that's dirty on arrival requires a photo, one that's already clean doesn't. The checklist also tracks where each item came from: checked off by the person on site, or filled automatically by a rule. A timestamped photo and the driver's location accompany completion, captured on site — not re-entered later back at the office.
Before the truck rolls, delivery or pickup confirmation can be requested from the customer — so a job site that changed address or date without saying so doesn't cost a wasted stop. At the end of the day, a configurable report goes out by email; billable visits are detected automatically instead of being reconstructed by hand at month-end, and the PDF invoice follows directly from them.
A Quebec operator in this business has been running OpsNode in production since June 17, 2026: 160 customers, 217 sites, 184 units and 2 drivers, as of July 31, 2026.
A pump-out route that plans itself?
Show us your current fleet — even a mix of long-term job sites and festivals — and we'll show you how OpsNode would have sequenced it this week.
See a demo