The Leaky Bucket: How Undocumented Knowledge Is Draining Your Plumbing Business

Imagine this. Your best engineer calls in sick on a Monday morning. He’s the one who handles all your commercial service contracts. He knows the access codes, the contact names, the quirks of every system he’s worked on. None of it is written down.

What do you do? You scramble. You ring him while he’s lying in bed with flu. You send someone else who doesn’t know the site, doesn’t know the system, and ends up taking twice as long on a job that should have been straightforward.

That’s the Leaky Bucket Syndrome. And it’s silently draining plumbing and heating businesses across the UK every single day.

What Is the Leaky Bucket Syndrome?

The Leaky Bucket is what happens when your business relies on knowledge that lives inside people’s heads instead of inside a system. Every time someone is off sick, goes on holiday, or — worse — hands in their notice, knowledge leaks out of your business like water through a cracked fitting.

Consider this: how much of your business knowledge is actually documented? Not just the technical stuff, but the everyday things. How you quote a job. How you onboard a new customer. How you handle a complaint. How you order stock. How you close down a job and send the invoice.

If the honest answer is “most of it’s in my head” or “the team just knows,” then you’ve got a leaky bucket. And every time you lose someone or something changes, you lose knowledge that took months or years to build up.

What Does This Actually Cost You?

The cost isn’t always obvious. It’s not a line on your P&L. But it shows up everywhere:

• Wasted time — New starters take weeks longer to get up to speed because there’s nothing written down for them to follow.
• Inconsistent quality — Every engineer does things slightly differently. Some customers get a brilliant experience, others don’t.
• Mistakes and rework — Without clear processes, errors creep in. Parts get ordered wrong. Jobs get quoted too low. Follow-ups get missed.
• Owner dependency — You become the bottleneck because everyone has to ask you how things should be done.
• Stress — You can never fully switch off because the business can’t function properly without your input.

If you’ve ever come back from a holiday to find things in a mess, you’ve felt the impact of the leaky bucket first-hand.

The Solution: Standard Operating Procedures

The fix is straightforward in concept, even if it takes effort to implement. You need Standard Operating Procedures — SOPs.

An SOP is simply a documented way of doing something. It captures how a task should be completed so that anyone in your business can follow it and get a consistent result. No guesswork. No ringing the boss. No reinventing the wheel every time.

In my eyes, SOPs are the single most underused tool in trade businesses. Most plumbing and heating companies have zero. Not a single written process for anything. And yet they wonder why quality is inconsistent, why onboarding takes forever, and why they can’t step away from the day-to-day.

The 8 Types of SOPs You Can Use

When people hear “SOP,” they usually think of a long, boring document. But SOPs come in many forms, and the best one is whichever format your team will actually use. Here are eight types to consider:

1. Step-by-Step Documents

The classic written procedure. A numbered list of steps that walks someone through a task from start to finish. Great for processes like closing down a job or setting up a new customer account.

2. Flowcharts

Visual decision trees. Perfect for processes that have branching paths — like diagnosing a boiler fault or deciding whether a job needs a quote or can be priced on the spot.

3. Checklists

Simple tick-box lists. Ideal for tasks where the order doesn’t matter much but nothing should be missed — like a van stock check or a pre-job safety inspection.

4. Templates

Pre-built documents that your team fills in. Think quote templates, job completion forms, customer feedback forms. They standardise the output without requiring people to start from scratch.

5. Video Walkthroughs

Record yourself or a team member doing the task. This works brilliantly for hands-on procedures. A two-minute video of how you want a boiler service completed can be more effective than pages of text.

6. Mind Maps

Great for planning and brainstorming. Not always a standalone SOP, but useful for mapping out complex processes before you document them properly.

7. Scripts

Word-for-word guides for phone calls, customer interactions, or sales conversations. If you want your team to present quotes consistently, a script gives them the framework.

8. Policies

Higher-level documents that set out rules and standards. Things like your complaints policy, your health and safety policy, or your pricing policy. These set the boundaries within which everything else operates.

You don’t need all eight types on day one. Start with whichever format suits the task you’re documenting. A checklist for van checks. A step-by-step guide for onboarding. A script for handling enquiry calls. Keep it simple.

The KISS Principle: Keep It Stupidly Simple

This is where most people go wrong. They decide to write SOPs, sit down with a blank screen, and try to create the perfect document. Three hours later, they’ve written nothing and they’ve given up.

The KISS principle — Keep It Stupidly Simple — is your best friend here. Your SOPs don’t need to be works of art. They need to be clear enough that someone can follow them and get the right result.

Here’s a good rule of thumb: if a reasonably competent person can pick up your SOP and complete the task without asking questions, it’s good enough. You can always refine it later.

Some practical tips:

• Use short sentences and plain language.
• Include screenshots or photos where they help.
• Number your steps so they’re easy to follow.
• Don’t try to cover every possible scenario — cover the 80% that happens most of the time.
• Get someone else to test it. If they get stuck, improve that section.

What Happens When You Plug the Leaks

Let’s explore what your business looks like once you start documenting things properly.

• A new engineer joins and can handle their first service call within days, not weeks, because the process is written down.
• Someone goes on holiday and the work continues smoothly because the knowledge isn’t locked in their head.
• Your customers get the same standard of service regardless of which engineer turns up.
• You can spot problems quickly because there’s a defined standard to measure against.
• You start to feel like you’re running a business rather than holding everything together by sheer willpower.

If you’re thinking about growing from one van to a fleet, SOPs aren’t optional. They’re the foundation everything else is built on.

Practical Takeaways

• If knowledge in your business lives in people’s heads, it will leak out when those people aren’t available.
• SOPs are the fix — documented processes that anyone can follow to get a consistent result.
• There are eight different SOP formats. Choose the one that fits the task, not the one that looks most impressive.
• Keep it simple. An imperfect SOP that exists is infinitely better than a perfect one that doesn’t.
• Start with one process. Document it this week. Then do another next week. Build the habit.

Want the Complete Framework?

This article has given you the “what” — what the leaky bucket problem is, why SOPs matter, and the different types available to you. But the real power comes from the “how.”

The Systems Handbook by Aaron McLeish gives you the complete SOP framework built specifically for plumbing and heating businesses. It includes the “SOP for creating SOPs” template — a step-by-step method for documenting any process in your business quickly and effectively. No fluff. Just practical tools you can use straight away.

Get your copy on Amazon:

• The Systems Handbook — Kindle & Paperback
• The Systems Handbook — Hardcover Edition

Already have your SOPs started but struggling with pricing? The Quote Handbook helps you build a pricing system that’s consistent, profitable, and doesn’t rely on guesswork.