By Aaron McLeish · 8 min read
Your best heating engineer calls one Tuesday morning. He’s got a job offer at a big commercial firm. Three weeks’ notice. Done.
You feel it in your stomach immediately. He’s been with you for five years. He knows your systems, your standards, your margins, which customers need hand-holding and which ones want you in and out. He’s done hundreds of boiler installs, load calculations, problem diagnostics. That knowledge is in his head. When he walks, it goes with him.
In my eyes, this is the central problem most trades businesses never solve. You’re not just losing a pair of hands. You’re losing years of accumulated know-how. And unless you’ve written that knowledge down beforehand, the next person won’t replicate what he did. They’ll start from scratch. Slower jobs. Quality dips. Margins sink. Customers notice.
Here’s what we’ll cover: why documenting your business knowledge is not optional, what happens when you don’t, and exactly how to start.
What we’re really talking about
When I say “document your business knowledge”, I don’t mean a dusty folder of PDFs nobody reads. I mean the working, living instructions and decision trees that let someone else do what your best team member does.
How you mark out a bathroom. The order of your callout process. What you check on a first visit before quoting. How you handle a customer complaint. Whether you call the supply house on Monday or Thursday to get the discount. These aren’t secret sauce. They’re your business. They need to exist outside anyone’s head.
What Happens If You Don’t Document Your Business Knowledge?
Let me walk you through the real cost.
A plumber I know in Bristol had a master fitter who’d been pricing jobs by feel for years. Smart guy, brilliant instinct. He could look at a bathroom and know whether it was a four-day job or a six-day job, and he was rarely wrong. One day he retired. Moved to Portugal. That knowledge went with him.
The plumber hired a replacement, competent but green. For six months, every quote came in either too high (lost jobs) or too low (profit evaporates). The business made less money in those six months than it had in any quarter for the previous three years. Why? Because the new fitter was learning by trial and error what the old one had known instinctively. And every job was a real job, with a real customer, so the mistakes were expensive.
Consider this: when a key team member leaves, the training time for a replacement is typically eight to twelve weeks of lower output, even with help. If you’re a heating company with three engineers and one walks, that’s instantly a 33 per cent productivity hit. Customers wait longer. Quality drops. You lose money while you’re learning how that person did things.
But here’s the worse part. If that person was doing something well—consistently getting callbacks, upselling service plans, managing site safety — and you never wrote down how, the next person invents their own way. It’s almost never as good. You’ve lost competitive advantage without realising you had it.
Picture this: a joiners’ firm loses their lead fitter to a bigger company. He was the one who knew which suppliers gave trade accounts, which ones were reliable, which cuts required which blades, the exact sequence for a fitted kitchen install. Twelve months later, the new fitter is still asking questions. Costs have drifted up. Some jobs take half again as long. The firm never put it together that they were worse because nobody wrote down what the expert knew.
Why You Need Documented Systems, Not Just People
Here’s the thing: when you run a business in your head, you’ve got a problem.
That problem has a name. It’s called the leaky bucket. You fill your business with knowledge and experience and skill. Then one person goes sick. Another gets a better offer. A third retires. The knowledge leaks out. By the time you’ve hired and trained a replacement, you’ve already lost months of work and profit. And you’re starting the learning curve from zero again.
The only way to plug those holes is to write your knowledge down before it walks away.
I’ve worked with hundreds of trades business owners. The successful ones, the ones scaling into four or five teams, all do the same thing. They document how things are done. Not perfectly. Not a beautifully bound manual. Just written down. Tested. Updated when it changes. Available for the next person to read and follow.
The businesses that don’t? They’re permanently stuck. They’re dependent on specific people. They can’t take a holiday. They can’t add another team. When someone leaves, they start again from the beginning.
Think of it like this: your business is only as good as the knowledge your team can actually access. Right now, most of that knowledge lives in the heads of one or two people. That’s not a business. That’s a job.
How Should You Document Your Business Knowledge?
You don’t need to reinvent the wheel. Let me explain what actually needs doing.
Start with a process that matters. Not everything. Pick something real. Something you do frequently. Something that, if a new person got it wrong, would cost you money or reputation.
Maybe it’s your first visit to a customer’s home. Maybe it’s how you diagnose a fault. Maybe it’s how you work with a particular supplier. Pick something.
Then describe it. Not beautifully. Just accurately. What do you do first? Then what? What do you check? What do you ask the customer? What are the common mistakes? Write it down. Have the person who knows it best read it and correct it. Let a newer team member follow it and tell you what’s missing. Update it. Done.
That’s one. Then pick the next thing.
You’re not building a 500-page operations manual. You’re building a living document of how your business actually works. What decisions happen and why. Which steps matter and which are nice-to-have. Where the money is made and where it’s wasted.
Here are the things that matter most to write down:
- How you handle a first customer contact or callout
- The steps of a standard job from start to finish
- Quality checks at each stage
- How you price or quote
- What to do if something goes wrong
- Who to contact for what
- Which suppliers or tools you use and why
The real win is this: once these things are written down, they’re the same every time. Your customer gets the same experience whether they book your best engineer or the new apprentice. Your job takes the same time. Your quality is consistent.
What Happens When Your Key Person Leaves: A Real Example
Let me explain why this matters with something actual.
An electrician in Manchester had one engineer who was brilliant with commercial jobs. High voltage, complex installations, the jobs that paid well. Everyone said “we need to keep him happy” and they did, paying him above market rate. They told themselves they couldn’t afford to lose him. That’s exactly what made it worse.
Nobody else had touched those jobs. He’d been doing them for seven years. When he got another offer and took it, the firm suddenly couldn’t quote commercial work. They lost three months of that revenue stream while they scrambled to either find someone new or figure out how to do it themselves.
If he’d been documenting the process as he went—even roughly—the next person could have shadowed him, read the notes, and learned it systematically instead of starting from zero.
That firm did eventually recover, but they lost money and market position in the meantime. They also woke up to the fact that they’d built a business dependent on one person.
Getting Started: The First Step
You don’t need software. You don’t need a consultant. You just need to start.
Pick one process. The one that, if you lost that person tomorrow, would hurt most. That’s your first one. Have them sit down for an hour, maybe two, and write down how it works. Not polished. Just real.
Then have someone else read it and try to follow it. They’ll find gaps. Fill them. Done.
Next week, pick the next one.
The businesses I see that win at this don’t hire a professional to come in and build their manual. They do it themselves, gradually, because they realised that knowledge was leaking out and it was costing them money.
The Takeaway
When your business depends on the people in it, you’re fragile. When your business depends on the knowledge that’s written down and accessible, you’re solid.
Documenting your business knowledge isn’t about creating busywork. It’s about building something that survives change. Something you could sell. Something you could scale. Something that doesn’t fall apart the moment someone leaves.
Start today. Pick one process. Write it down. Have someone test it. Fix it. Then move to the next one.
You’re not trying to be perfect. You’re trying to be better than you were, and better than the day you lose someone and realise you never wrote any of it down.
If you want to go deeper into this—how to build systems that actually work, how to hand over responsibility to your team, and how to stop being the linchpin everything depends on—I’d recommend picking up The Systems Handbook from our Together We Count shop (https://amzn.to/45aMvUH). Chapter 3 is about exactly this: why your trades business needs an administrator, and what changes when you start building systems instead of just managing people.
For now, reach out. Email info@togetherwecount.co.uk or connect with me on LinkedIn at https://linkedin.com/in/aaron-mcleish if you’re struggling with knowledge transfer or team turnover. Our team can walk you through where to start.
Aaron McLeish, Managing Director.
—