Quick Answer
An operations manual is simply the written version of everything you currently carry in your head: how you quote, how you book jobs in, how you order materials, how you invoice, and what "done properly" looks like. You do not need fancy software or a hundred pages. You need your ten or so most important jobs written down in plain English so someone else can follow them. Start with one procedure, spend twenty minutes on it, and build from there. Do that and you stop being the bottleneck in your own business. Grab the free template below and write your first section today.
Table of Contents
- Why your business should not live in your head
- What an operations manual actually is
- Start with the jobs you do every week
- How to write one procedure in twenty minutes
- The seven sections of a simple operations manual
- Download the free template
- Where to keep it so people actually use it
- Get your team to help you build it
- Keep it alive and improve it
- What tradespeople are saying
- Recommended videos
- Frequently asked questions
- My take
Google Sheets
Excel
Google Calendar
WhatsAppYou do not need to buy a single piece of software to write your operations manual. A shared document, a spreadsheet for your checklists, a calendar for the jobs that repeat, and a group chat where the team can ask questions. That is more than enough to start. The tools above are ones most trades businesses already have. The manual is not the software. The manual is your thinking, written down.
Why your business should not live in your head
Let me start with something I hear almost every week from the owners I coach. "If I get hit by a bus, the whole thing stops." They laugh when they say it, but they are not really joking. They know that everything important is stored in one place: their own head. How the good customers like to be spoken to. Which supplier does the next-day delivery. What to charge for a boiler swap versus a full system. The order you do things in so a job does not come back on you.
That knowledge is worth a fortune. It is also completely invisible, which means it cannot be shared, checked, improved, or handed over. When it all lives in your head, three things happen. You cannot take a proper holiday. You cannot bring someone in without watching over their shoulder. And the day you do lose a key person, a huge chunk of how your business works leaves with them.
I have seen brilliant tradespeople hit a ceiling here. Not because the work dried up, but because they physically could not take on more without cloning themselves. Every quote went through them. Every problem came back to them. They were working sixty hours and still felt behind. That is not a work-rate problem. It is a systems problem, and an operations manual is where you start to fix it.
None of this is about turning your business into a faceless machine. It is about protecting yourself. The whole point of building a business, rather than just having a job with extra stress, is that it can run without you being on every single job. If you have read my piece on coming off the tools, you will know I bang this drum a lot. Systems are what let you step back without the wheels falling off.
Ask yourself one honest question about each part of your business: if you were off for two weeks with no phone, could someone else keep it running from what is written down? Every "no" is a page your operations manual still needs.
What an operations manual actually is
Let me clear up what this is, because the phrase "operations manual" scares people off. They picture a fat corporate binder that nobody reads, written in language no plumber would ever use. Forget that. Your operations manual is just a collection of your key processes, written simply, kept in one place your team can get to.
Think of it like the McDonald's approach, and stay with me here. Whether you walk into a McDonald's in Leeds or Lisbon, the fries taste the same. That is not luck. It is because every task is written down and followed the same way every time. They call it systemising. I sometimes call it the sausage machine: same ingredients in, same result out, no matter who is on shift. You want your business to feel like that, where the customer gets the same standard whether you turned up or one of your team did.
An operations manual is not a policy document, and it is not a legal contract. It does not need HR jargon or ten-syllable words. If a capable new starter could read a page and get the job done to your standard without ringing you, that page has done its job. That is the only test that matters.
A good operations manual is a working document, scruffy round the edges and always slightly out of date because you keep improving it. A perfect manual that took you six months and now sits in a drawer is worthless. A rough one your team actually uses is priceless.
Start with the jobs you do every week
The most common reason people never start is that they try to document everything at once. They sit down to write "the whole business" and give up by lunchtime. Do not do that. Start with the jobs you and your team repeat most often, because that is where written processes save you the most time and cause the fewest mistakes.
Grab a piece of paper and, for one week, jot down every repeatable task you or your team do. Not the one-offs. The things that happen again and again. It usually looks something like this:
- A new enquiry comes in: how it gets answered, logged, and turned into a booked visit.
- Quoting a job: how you price it, what goes in the quote, and how you follow it up.
- Booking and scheduling: how a confirmed job gets into the diary and onto the right person.
- Ordering materials: which suppliers, what accounts, how you avoid double-ordering.
- On-site standards: what a finished job looks like, how you leave a customer's home.
- Invoicing and getting paid: when the invoice goes out, how you chase a late payer.
- Handling a complaint: what to say, what to fix, when it comes to you.
That list right there is the skeleton of your operations manual. You do not need a hundred procedures. Most small trades businesses run beautifully on ten to fifteen. Prioritise the ones that go wrong most often or cost you the most when they slip. Those get written first.
If you only ever write two procedures, make them the ones tied to cash and to comebacks: how you quote, and how you invoice and chase payment. Get those consistent and you protect your margin and your cash flow at the same time.
How to write one procedure in twenty minutes
Here is the bit that trips people up. They think writing a procedure means producing a beautiful document. It does not. The fastest way to write one is to do the job and narrate it, either into your phone as a voice note or straight onto the page. You are not writing an essay. You are leaving instructions for the next person.
Use the same simple shape for every procedure and it becomes easy. Give it a clear title. Say who does it and when. List the steps in order, one line each, plain words. Note anything that tends to go wrong. Finish with what "done" looks like. That is it. Here is the shape I give the businesses I work with:
- Title: name the task the way your team would say it, for example "Booking in a boiler service".
- Who and when: who is responsible and at what point it happens.
- The steps: number them, one action per line, in the order you actually do them.
- Watch out for: the two or three mistakes people make, so they do not make them.
- Done looks like: a one-line description of a job finished to your standard.
Write it the way you speak. If you would say "give the customer a courtesy text the day before", write exactly that. Do not translate it into stiff business language. The person reading it is a tradesperson, not a lawyer. A photo or a quick screen recording often does more than a paragraph, so add those where they help.
The person who does a job every day is the best person to write that procedure, not you. Ask your most reliable engineer to talk you through how they book a job in, and write it up as they speak. It is quicker, it is more accurate, and it gives them a bit of pride and ownership.
Do not polish. Version one just needs to be usable. You will improve it the first time someone follows it and spots a gap. That is normal and it is a good sign, because it means the manual is being used rather than gathering dust.
The seven sections of a simple operations manual
Once you have a handful of procedures, you need somewhere sensible to keep them so people can find things fast. I use seven simple sections. They cover almost everything a trades business does, and they map neatly onto the free template further down the page. You will not fill every box on day one, and that is fine.
1. The basics
The one-pager that orients a new starter: who you are, what you do, your standards, your promise to customers, and who to ask about what. Short and human.
2. Getting work in
How enquiries are answered and logged, how you quote, and how you follow up. The front door of your business, written down.
3. Doing the work
Scheduling, materials, on-site standards, health and safety basics, and what a finished job looks like. The heart of the manual.
4. Getting paid
When and how you invoice, your payment terms, and exactly how you chase a late payer without it being awkward or forgotten.
5. Looking after customers
How you communicate, how you handle a complaint, and how you turn a happy customer into a repeat customer and a review.
6. Looking after the team
How someone joins, what their first week looks like, holiday and sickness basics, and where people go with a problem.
7. The numbers and the tools
Your key suppliers and accounts, the software and logins the team needs, and the handful of numbers you check every month.
Keep the same order every time and your team learns where to look. When a question comes up, the answer is "it is in section four" rather than "ring the boss". That single shift, from asking you to checking the manual, is what frees up your day.
Download the free template
To save you staring at a blank page, I have put the whole thing into a simple template. One file is the operations manual skeleton with the seven sections laid out and prompts in each one. The other is a one-page procedure template you can copy for every job you write up. Both are plain text, so you can paste them straight into a shared document, a Google Doc, or Notion and start typing.
Operations manual template
The seven-section skeleton with prompts in every section. Paste it into a shared document and fill it in a bit at a time.
Download the manual templateOne-page procedure template
The simple title, who and when, steps, watch-outs and done-looks-like shape. Copy it once per procedure.
Download the procedure templateDo not try to fill it all in one sitting. Print the first page, pin it up, and add one procedure a week. In three months you will have a proper manual and you will barely have noticed the effort.
Where to keep it so people actually use it
A manual nobody can open is not a manual. The single biggest mistake I see is a lovely document saved on the owner's laptop where the team cannot reach it. Keep it somewhere shared, somewhere everyone can get to on a phone from a van. That is the whole game.
You have simple options, and you almost certainly already pay for one of them. A shared folder with documents in it works fine. A spreadsheet is brilliant for checklists and logs. A group chat is where the team asks the quick questions, and the good answers get added to the manual. A shared calendar handles the jobs that repeat, like annual services and certificate renewals, so they never get forgotten.
Do not overthink the tool. Pick the one your team will actually open, set the permissions so people can read it, and put the link somewhere obvious. If your engineers live in a group chat, pin the manual link at the top of it. Meet people where they already are rather than making them learn a new system on top of the day job.
The fastest way to kill trust in a manual is to have three versions floating about. Keep one master copy in one place. When you change something, change it there. Everything else should link to that one home, not be a copy of it.
Get your team to help you build it
You do not have to write all of this yourself, and honestly you should not. Your team knows the detail of their own jobs better than you do now. Building the manual together does two jobs at once: it gets the work done faster, and it gets your people bought into using it, because it is partly theirs.
I talk a lot about treating people well because it is the thing that keeps a trades business standing. When someone helps write the way a job is done, they take pride in it. They spot the gaps. They suggest the better way. That is worth far more than a manual written in isolation by a knackered owner at eleven at night. If you want the bigger picture on keeping good people, I went deep on it in why your best tradesperson is about to leave.
There is a hiring win here too. When your processes are written down, a new starter gets up to speed in days, not months, because they are not waiting for you to have a spare minute to explain things. Onboarding stops being a drain on your time. It becomes "here is the manual, here is your buddy, ask questions". I have watched that turn a stressful first week into a calm one. It also makes a bad hire far less likely, which matters when you know what a wrong one costs, as I set out in the panic hire.
Every time someone asks "how do we do X", that is a signal a procedure is missing. Get into the habit of answering the question and then writing the answer into the manual. Do that for a few months and the thing builds itself.
Keep it alive and improve it
A manual is never finished, and that is a feature, not a bug. Your business changes. Suppliers change. You find a smarter way to do something. The manual should keep up. The trick is to make reviewing it a small, regular habit rather than a giant once-a-year job you dread.
Put a recurring reminder in the calendar, once a month, fifteen minutes, to look at one section and ask "is this still how we do it?" Update the bits that have drifted. Bin the bits you no longer do. Add the new procedures that have appeared since. Fifteen minutes a month keeps a manual accurate forever. Skip it for a year and you are back to square one.
Put a "last updated" date on each procedure. It tells the reader how much to trust it, and it makes the out-of-date ones easy to spot at a glance. A tiny habit that saves a lot of confusion.
Key Takeaways
- An operations manual is just your key processes written in plain English, kept somewhere the team can reach.
- Start with the ten to fifteen jobs you repeat most, and write the money and mistake ones first.
- Each procedure needs only five parts: title, who and when, steps, watch-outs, and what done looks like.
- Let your team write the procedures for the jobs they do. It is faster, more accurate, and builds ownership.
- Keep one master copy in one shared home, and spend fifteen minutes a month keeping it current.
- The payoff is real: easier holidays, calmer onboarding, less firefighting, and a business that does not depend on you alone.
What tradespeople are saying
This is not just my hobby horse. Owners have been wrestling with getting the business out of their own heads for as long as there have been small businesses. Here is a flavour of the conversation from the UK Business Forums.
Recommended videos
If you would rather watch than read, these walk through systemising a trades business and writing procedures. A few are aimed squarely at trades, and the rest are solid on the how-to of getting a process out of your head and onto the page.
How to Systemise Your Trade Business for Success
The Site Shed
Step-by-Step System for Systemizing Your Trades Business
systemHUB
How To Systemise Your Business In Just 12 Weeks
Ross Harkness
How to Write an SOP in 9 Minutes
Simpletivity
6 Steps to Systemize Your Business (Even If You Have No Time)
Layla at ProcessDriven
How To Make A Standard Operating Procedure
Visme
Frequently asked questions
Yes, and honestly you need it most of all. Writing down how you work is how you free yourself up to take on help, take a holiday, or sell the business one day. It also forces you to spot the daft, inefficient habits you have never questioned. Start small. Even five procedures will change how your week feels.
You can write your first procedure in twenty minutes today. A usable manual covering your key jobs is a few weeks of work if you do one procedure a week. Do not aim for perfect and finished. Aim for started and useful, then keep chipping away.
An SOP, a standard operating procedure, is the instructions for one task, like booking in a service. Your operations manual is the folder that holds all your SOPs together, plus the basics about your business. Think of each SOP as a page and the manual as the whole book.
They will if it is easy to reach and actually useful. Keep it where they already are, usually on their phones, and write it in normal language, not corporate speak. When they help write it, they use it. When it is handed down from on high, they ignore it. So build it together.
No. A shared document and a spreadsheet will get you a long way, and you almost certainly already have both. Fancy tools can help once you are bigger, but they are not the point. The value is in the thinking you write down, not the app you write it in.
Write the procedure for whatever goes wrong most often, or whatever costs you the most when it slips. For most trades businesses that is quoting and getting paid. Nail those two and you will feel the difference in your margin and your cash flow almost straight away.
My take
My verdict
Getting your business out of your head and onto the page is one of the highest-value things you will ever do as an owner, and it costs you nothing but a bit of time. You do not need a consultant, a fat binder, or clever software. You need your key jobs written down simply, kept somewhere your team can reach, and reviewed for a quarter of an hour each month. Start with one procedure today. Then another next week. Before long you will have a business that runs on systems rather than on your nerves, and that is what lets you finally step back. Please do let me know how you get on.
Best for: any trades business where too much only lives in the owner's head
Start with: your quoting and your invoicing procedures
Time to first win: twenty minutes for your first written procedure
Keep it alive: fifteen minutes a month, one section at a time
