HomeIndustriesSeptic Services
The tank belongs to the customer — tracking the schedule is on you
You're not renting anything: you're servicing an asset the customer already owns, on an interval set by regulation, often miles from the next stop. A missed interval usually surfaces the following year, when the municipality asks the question. OpsNode tracks every septic tank as a scheduled asset, not a line item on a rental fleet.
A customer-owned asset, an obligation that comes back on its own
A septic tank never enters your rental fleet: it stays the customer's property, and the service is simply showing up at the right interval, year after year. That interval is often set by regulation — annual or every two years depending on how the building is used — and it doesn't get renegotiated the way a rental term does. It gets missed silently: nobody calls to flag that a pump-out anniversary is coming up, except the regulation itself.
The territory served is usually rural: longer distances between stops, roads that don't follow a grid, a driver who can burn half a day fast if the route isn't sequenced on the real road network instead of a list sorted by street name. Group three nearby addresses badly, and that's three separate trips instead of one detour.
And at the end of the day, the municipality wants proof — not an invoice, but proof that the pumping happened, on the right date, on the right tank.
Built for the customer's asset, not just the rental fleet
The data model distinguishes what you rent out from what the customer already owns and you service on a schedule.
The asset belongs to the customer
A septic tank is registered as a customer-owned asset, serviced on a schedule — distinct from your rental fleet, but tracked with the same rigor.
Customer-owned asset, its own scheduleAnnual or every-two-years schedule
The regulatory interval is set once per tank; future visits generate themselves, with no dependency on a manual reminder in a spreadsheet.
Automatic generation from the scheduleRural roads count double
Stops group by address and sequence on the real road network — essential when the next tank is miles away, not around the corner.
Calculated on the real road networkProof for the municipality
A checklist specific to the visit, a timestamped photo, and the driver's location at completion — the proof exists the moment the visit happens, not reconstructed on request.
Timestamped photo + location at completionThe truck keeps working offline
In a rural area with no cell coverage, the driver's app keeps its stops queued locally and resyncs once signal returns, without duplicating a visit already completed.
Local queue, resync with no duplicatesReporting and billing that keep up
A configurable end-of-day report goes out by email; billable visits are detected automatically and the PDF invoice follows, with no manual spreadsheet rework.
Automatic detection of billable visitsA one- or two-year interval gets forgotten — a record doesn't
A full year can pass between two visits to the same tank — sometimes two. Over that stretch, a paper route sheet or a tracking spreadsheet gets lost, goes stale, or just waits for someone to remember to check it. Setting the schedule once per tank solves the problem at the source: the next visit already exists before anyone even has to think about it.
And when the municipality or the customer asks for proof, it's already there — tied to the right tank, the right date, with the photo and location captured on site at the moment of the visit, not written up from memory back at the office.
A pump-out schedule that no longer depends on a manual reminder?
Show us your territory and your current regulatory intervals — we'll show you how OpsNode would have generated and sequenced your routes.
See a demo