The run only works when I am the one driving it.
If you cannot take a week off without the round falling over, you do not have a business problem, you have a documentation problem wearing a business problem's clothes. Here is what actually has to be written down, and why it is the same job as proving the work.
The test
Could someone competent, who has never done your round, complete it tomorrow using only what is written down? Not someone you have trained for six months. Someone new, with the system in front of them.
For most route operators the answer is no, and it is not close. The order of the sites, the gate codes, the bin that lives behind the fence, the client who wants a text before you arrive, the tenancy that changed hands in March: it is all in one head. Usually yours.
A round that only works when you are driving it is not an asset. It is a job that happens to have customers attached to it.
What it costs you right now
- A sick day is a lost day of revenue, because there is nobody to hand it to.
- Hiring takes months to pay off. You cannot put a new driver on the round alone, so every new hire costs you two people's time until they have absorbed what is in your head.
- You cannot take on the next contract without personally absorbing it, which is the real reason growth stalls at a certain size.
- You cannot sell it, or not for what it should be worth, because a buyer is being asked to purchase your memory.
- You cannot take a proper holiday, which is usually the one that finally forces the issue.
Why writing a manual does not work
Most operators attempt this once, on a Sunday, in a document. It fails for two reasons. It is written from memory, so it is missing precisely the things that are so automatic you no longer notice doing them. And it is out of date within a month, because contracts change and nobody updates a document nobody reads.
The version that works is captured on the run instead of recalled off it. The driver records the site, the access detail and the exception at the moment it happens, because doing so is faster than not doing so. After two or three cycles the round has documented itself, and it stays current because it is a by-product of the work rather than a separate chore.
Documentation written from memory is always missing the things you no longer notice you know. Capture it on the truck, not at the kitchen table.
The convenient part
This is the same build as proving the work. The record that lets a new driver complete the round unaided, sites in order, access notes attached, exceptions logged, is the same record that lets you show a client the service happened and bill for everything you serviced.
That is why I treat owner-dependency and proof of work as one problem rather than two. Fix the record and both move. The billing side of it, including a waste operator whose unbilled servicing was evidenced at around $30,000 a month once the record existed, is on proof of work for service crews.
Where to start
Start on your own next run. Capture the sites in order, the access details, and every exception you hit, as you hit them. Do it for two cycles. Then hand the third to someone else and watch where they get stuck: those gaps are the actual specification, and they are never the ones you would have guessed.
If you would rather not build the habit by hand, that is what I build: from $1,500 fixed for a smaller one, $3,500 for a bigger one, or inside Ops Care from $1,500 a month. The Trades Tech Leak Audit is thirty minutes and a one-page finding, free, and it will tell you whether the run or the billing is the more expensive gap in your case.
What owner-operators ask me about handing the run over.
How do I get the round out of my head?
Not in one sitting, and not by writing a manual. Capture it while you drive it: each site, in order, with the access notes, the client quirks and the exceptions recorded at the moment they come up. Two or three cycles and you have a real record, built from the actual run rather than from what you remembered on a Sunday.
How long should it take a new driver to run the round solo?
If it takes more than two or three cycles, the knowledge is still in someone's head rather than in the system. That is the honest measure of whether this worked, and it is a better one than any feature list.
Does this actually change what the business is worth?
It changes what a buyer is buying. A round that only functions with you in the truck is a job with customers attached. A round any competent driver can complete is an asset. I am not going to put a multiple on that, because it depends entirely on your book, but every broker and buyer asks the question, and the answer is currently no.
My crew will say this is surveillance. What do I tell them?
That it is the opposite, and then make sure it is. The record exists so a driver can prove they did the work when a client says otherwise, and so nobody has to ring you to find out what a site needs. If you use it to time people rather than to back them, they will fill it in badly and you will deserve the data you get.
What does this cost?
A smaller build starts from $1,500 fixed and a bigger one from $3,500, scoped in writing before anything starts. Most route operators end up on Ops Care from $1,500 a month, because a run record is never finished: contracts change and the system has to change with them.
Not sure what fits your shop? Ask me, not a sales rep.
A 30-minute Tech Leak Audit and a one-page written finding inside 48 hours. Three prioritised fixes, no pitch, and the report is yours either way.