Running a Garbage Route From Memory: What Breaks First

The Memory System

While building Svoboda Sanitation Service's website, I found that the larger problem was in the office. This family trash business is in Johnstown, North Dakota. Routes lived in someone's head; bills lived on paper.

The driver knew the alley, the gate and the dog. Carbon-copy invoices held the billing, with memory supplying the list of people behind. One person carried the whole system.

What Breaks First

A different driver

Consider a substitute running an unwritten route. They need to know where the bin sits, which gate to use and where the code is kept. The dog matters too.

Without those notes, each stop can become another call to the person trying to have a day off. That was the problem the driver sheets needed to solve.

The who-owes list

Paper invoices leave that answer in a shoebox. Adding them up becomes a winter-evening job, done a few times a year. Between those checks, a route can keep serving customers months behind.

Even a few unpaid accounts matter to a small operation. The office needs the charges and payments together to see the balance.

A new rate

When fuel costs rise, an operator may need to raise prices. Now somebody has to track who was told and which rate belongs to last spring's bill. A rewritten paper record doesn't preserve that distinction.

A payment without an obvious owner

A check can arrive without a note. A website card payment may use an email the office doesn't recognize. Picking an account because it seems likely isn't good enough for money.

What I Built Around

The job called for a small-hauler office tool. Tonnage reports and transfer-station modules weren't the starting point. For an operation with one or two trucks, these were the useful jobs:

• Ordered daily stops, with the curbside note printed where the driver can find it.
• Unpaid balances derived from recorded charges and payments.
• A month's charges shown for review before the billing run posts.
• A ledger that corrects mistakes openly rather than silently overwriting them.
• Customer statements whose issued contents stay fixed.

So I Built HaulerHQ

I built the office tool alongside Svoboda's website. It became HaulerHQ.

Customer records hold the stops and their notes. Driver sheets carry reminders about an alley bin, a gate code on file or a dog nearby. From a phone, the route also offers calling and directions.

The opening dashboard shows unpaid balances aged by days overdue. Those figures come from the ledger, rather than a separately maintained list.

I'm proudest of the ledger. Its database enforces entries that can be added, but not edited or deleted. A money mistake gets a reversal explaining the correction, followed by the right entry.

A rate change starts a dated period. It leaves last spring's charge at last spring's price. Issued statements also stay fixed, rather than changing when later records change.

Stripe checks online payments before HaulerHQ posts them. An account number, saved customer link or single clear email match can identify the account. An unclear match waits for the office to review it.

Refunds and disputes still need manual handling in Stripe. The software doesn't settle those decisions for you.

See It Yourself

The public example uses a fictional hauler, fake customers and one-click login. Its shared records reset; settings, imports and backups are disabled. Keep real customer details out of it.

You can examine Monday's driver sheet, print that sample and compare reordered stops. A sample recorded payment changes the demonstration balance. Use the sample to decide whether its records cover the jobs your office needs.

HaulerHQ runs on your hosting and has no monthly software fee. I quote setup to the operation, including customer records, routes, rates and a walkthrough. Hosting and optional maintenance still have their own cost.

I can start from a spreadsheet, notebook or shoebox of records. I've worked from worse. We still need to agree what the records mean and which opening balances to carry over.