The most important system in your service business is one worker's memory. Here's how to get it out before they leave.
Every service business has one. The person who has been on the run longest, who knows that the side gate sticks unless you lift it, that the client at number 14 wants the bins back in before nine, that the alarm panel is behind the coat rack and not by the front door. Jobs go smoothly when they are on them. When they are sick, the phone starts ringing.
Ask most owners where their business's operating knowledge is stored and they will point at the job software, the price list, the accounts. Ask them what actually went wrong the last time someone new covered a regular job, and the answer is almost never in any of those. It was something everybody who had been there knew, and nobody had written down.
Why this knowledge never gets written down
Not because anyone is hiding it. Because of how it gets learned.
- It is learned by doing the job, one small surprise at a time. Nobody sits down to record that the hot water takes four minutes to come through. They just learn to turn it on first.
- It feels too small to write down. Each fact on its own is trivial. Together they are the difference between a job that takes the quoted time and a job that runs forty minutes over with a complaint at the end.
- The person who knows it doesn't need it written down. The only person who would benefit from the note is the one who isn't there yet.
- There is never a good moment. During the job they are working. After it, they are driving to the next one. The knowledge stays in their head by default, and default always wins.
What it costs when it walks out
The loss rarely shows up as one big failure. It shows up as a scatter of small ones in the weeks after someone leaves, goes on holiday, or moves to a different run. A missed instruction here, a locked-out worker standing on a doorstep there, a client who has to explain the same thing for the third time and starts to wonder whether you are paying attention.
Each one costs a little: a return trip, a discount to smooth things over, an hour of the owner's day on the phone. The real cost is the one you don't see on any invoice. Regular clients don't usually leave over one bad visit. They leave over the feeling that nobody remembers them.
Clients don't experience your systems. They experience whether the person at the door already knows what they told you last time.
Getting it out without a documentation project
The instinct is to announce a big effort: everyone writes up everything they know about every site. It never finishes, because it asks people to do an afternoon of writing on top of a full week of work, about things that feel too obvious to write. A few habits work much better than one project.
- Capture at the moment of surprise. The best time to record a site fact is the minute someone discovers it, on the job, on their phone. One line is enough: “Side gate sticks, lift and push.” A note written later from memory is half as accurate and twice as likely not to happen.
- Attach it to the place, not the person. A note that lives in someone's personal phone, or a group chat from last March, is still in one person's head as far as the business is concerned. Notes need to sit on the client or site record, where whoever is sent next will see them before they arrive.
- Use photos for anything spatial. Where the key safe is, which tap is the mains, what “the back room” means. A photo replaces a paragraph nobody would have written.
- Make reading the notes part of the job, not an option. If notes are tucked away three screens deep, nobody new will find them in the car before a job. They have to sit in front of the worker on the way in.
- Ask the leaver one specific question. When someone is moving on, don't ask them to “hand over everything.” Go through their regular jobs one at a time and ask: what would trip someone up here? Ten minutes per site, recorded on the site, while they still remember.
The test worth running this month
Pick one regular job and send someone who has never done it, with nothing but what is written down. Don't brief them in the car park. Then ask them afterwards what they had to guess, who they had to ring, and what they found out the hard way.
Everything on that list is knowledge your business currently stores in one person's memory. Write those things onto the site record, and run the test again on a different job next month. It is uncomfortable the first time. It is also the cheapest audit you will ever do, because it finds the gaps before a client does.
Where we land on it
We built Dispatch running a real field crew, and this is one of the problems that shaped it. Workers clock on from their phone at the site, work through the job checklist, and take before and after photos, all against the job, so what one person knows about a place has somewhere to live other than their head. It also works offline, which matters, because the sites where knowledge is hardest to find tend to be the ones with no signal.
But the software is the easy part. The habit is the hard part: noticing the surprise, writing the one line, and treating every unwritten site fact as a small risk you are choosing to carry. Your best worker's memory is a real asset. It is just a terrible place to keep one.
Software for service businesses — built by an operator.
Job management, books, and AI agents that actually know your business.