He'd been with the company for nine years.
Handled dispatch for six techs. Knew which customers wanted morning slots. Knew which properties had gate codes. Knew which invoices to chase and which clients to leave alone. Knew the supplier rep's cell number because he'd had it memorized since 2019.
He gave his notice on a Tuesday. By Friday, the owner was taking calls he hadn't handled in years.
This isn't a story about a bad employee or a bad exit. It's about a business that accidentally made one person load-bearing.
The trap is invisible while it's working.
When Dave shows up every day, the operation runs. Jobs get dispatched. Customers get called back. Invoices go out. You think the business is running well.
It is. But it's running on someone's memory, not on a system.
The difference only shows up when he leaves.
I see this pattern constantly in service businesses. A tech who's been with the company for seven years knows every quirk of every commercial property on his route. Keypad codes, equipment locations, which site manager is helpful and which one will make him wait 40 minutes. It's all in his head.
When he goes out sick, the job takes twice as long. When he quits, the next tech is starting from scratch.
The owner didn't build a bad business. He built a business that depends on institutional memory that was never institutionalized.
The fix isn't complicated. But it requires a decision.
The goal is to make the information escape the person and live in the system. Not a separate documentation project. Not a binder nobody reads. It happens inside the normal workflow.
Three things that actually work:
Custom fields on the client record. Property notes, gate codes, parking instructions, customer preferences - these should live on the client record in your job management software, not in a tech's phone or a dispatcher's head. Anyone who pulls up that client can see what the last person knew.
A notes field at job close. One or two lines: "anything the next person should know." What was different. What the client mentioned. What needs watching next visit. This isn't extra work - it's thirty seconds at job close that compounds into institutional knowledge over time.
Templates for repeatable situations. If your dispatcher does the same three things every Monday morning, that's a checklist. If your office manager sends the same follow-up after every large job, that's a template. Stop letting repeatable work live as verbal handoffs.
None of this is hard to build once you decide to build it.
The hard part is deciding it matters before the person leaves.
Most owners wait until there's a gap. Then they scramble to write things down while also trying to cover the gap. It's the worst time to build a system.
The businesses that handle turnover well built the systems when they didn't need them.
One question for you: how many things in your business does only one person know how to do?
Reply and let me know. I read every response.
Kevin Chan
The Ops Shortcut by ChanAutomation
https://www.chanautomation.com