Running a Garbage Route From Memory: What Breaks First
Svoboda Sanitation Service is a family trash operation in Johnstown, ND. When I built their website, I found the real problem wasn't the website. The routes lived in someone's head and the billing lived on paper.
The Memory System
Plenty of small haulers run exactly like this: the person who drives the route knows the route. Which alley, which gate, which dog. The billing is a box of carbon-copy invoices and a mental list of who's behind. It works because one person carries the whole thing.
That sentence is also the problem. It works because ONE PERSON carries the whole thing.
What Breaks First
1. The new driver
The day someone else has to run the route, the memory system fails completely. The route isn't written anywhere. The new guy doesn't know the bin is behind the alley gate, doesn't have the gate code, and definitely doesn't know about the dog. Every stop becomes a phone call to the person who was supposed to get a day off.
2. The who-owes list
Paper billing means the answer to "who owes us?" lives in a shoebox. Adding it up is a winter evening project, so it happens a few times a year. In between, service quietly continues for people who stopped paying months ago. For a small route, a handful of non-payers is real money.
3. The rate change
Fuel goes up, rates have to follow. Now every paper record is wrong and someone has to remember who got told, who didn't, and which price applies to the bill from last spring. This is where paper systems produce their finest arguments.
4. The payment mystery
A check arrives with no note. A card payment comes through the website with an email nobody recognizes. Whose account does it go on? With paper, it goes on whoever the office thinks it goes on, and sometimes that's wrong, and with money, "sometimes wrong" is the whole ballgame.
What a Small Hauler Actually Needs
Not enterprise waste-management software with tonnage reports and transfer station modules. A one-or-two-truck operation needs:
- Routes written down: ordered stops for each day, with the note that matters at the curb printed right on the sheet
- A who-owes list that maintains itself from actual charges and payments
- Billing runs that post a month of charges in one reviewed batch
- A ledger nobody can quietly edit, so the books always add up
- Statements you can hand a customer that don't change after you print them
So I Built HaulerHQ
While building Svoboda's site I built the office tool to go with it, and it became HaulerHQ, route and billing software for small haulers.
Every customer and stop lives in one place. Route days print as driver sheets with the per-stop notes ("bin by the alley gate," "gate code on file," "dog on site"), or work from a phone with tap-to-call and directions. The dashboard opens on the who-owes list, aged by days past due, computed straight from the ledger.
The ledger is the part I'm proudest of, and the part you'll never look at: it's append-only, enforced by the database itself. Nothing gets edited or deleted, ever. A mistake gets a reversal entry that says what happened, the way a real accountant corrects a book. Rate changes open a new dated period instead of rewriting history, so last spring's bill still shows last spring's price. And online card payments match themselves to the right account through Stripe or wait in a review queue; the software never guesses whose money it is.
See It Yourself
There's a public demo loaded with a fictional hauler: one-click login, fake customers, resets itself. Open Monday's route sheet and hit print. Drag a stop to reorder the route. Record a payment on somebody in the who-owes list and watch it clear.
Like the storage software I built for my own lot, HaulerHQ is self-hosted with no monthly fee. One-time setup priced to your operation, and I load your customers from whatever you have. A spreadsheet, a notebook, the shoebox. I've worked from worse.
Run a Route or Two?
Poke at the demo, then tell me about your operation. If HaulerHQ fits, I'll say so. If you actually need the enterprise stuff, I'll say that too.