Every business owner has been told to document their processes. Most have started, produced an impressive folder nobody opened, and quietly stopped.
The failure is almost always the same: it started with everything, in writing, done by the owner, during a week that turned out to be busy.
Here is the version that survives.
Why it matters more than it sounds
A business that only works when you are in it is worth very little to anyone else, and it is fragile for you. Illness, a family emergency, or simply a fortnight away turns into a genuine problem rather than an inconvenience.
Documentation is what turns "how we do this" from something in your head into something the business owns. It is also, bluntly, most of the difference between a business you can sell and a job you cannot leave.
Do not write them. Record them.
Writing a procedure from memory is slow, and it produces the version you think you follow rather than the one you do. You will also omit the parts you do automatically, which are exactly the parts a new person gets wrong.
Instead, the next time you do the task, record your screen or your phone and narrate what you are doing. It costs the length of the task plus nothing.
Then turn each recording into five short headings:
- Purpose — what this is for, in one line.
- Trigger — what makes this start.
- Inputs — what you need before you begin.
- Steps — what you actually do.
- Done — how you know it is finished and correct.
That last one is the one people skip and the one that matters most. "Done" is where quality lives, and without it you get work that follows the steps and still needs redoing.
The five to do first
Not everything. These five, because they are the ones that most often bottleneck on the owner.
1. How a new customer becomes a job. From first enquiry to work scheduled. This is where money is lost quietly, through slow replies and things falling between people.
2. Your core delivery. The thing you actually sell, done once, properly. If you do several things, pick the one you do most often.
3. What happens when a customer has a problem. Who responds, how fast, what they are allowed to decide without asking you. The last part is the whole point — a complaints process that ends in "check with the owner" has not removed you from anything.
4. Onboarding someone new. Everything a new person needs in their first week. You will write this once and use it every time, and it is the process that makes all the others adoptable.
5. The end-of-month routine. Invoicing, reconciling, chasing, reporting. It recurs, it is easy to get wrong, and it is usually entirely in one person's head.
Let the people doing the work own them
Once a procedure exists, the person who does that job should be able to edit it. This feels like a loss of control and is the opposite.
A procedure the team cannot change becomes wrong within a month and then gets ignored, which is worse than not having one — now there is a document that lies. A procedure they maintain stays true, and the act of maintaining it is how people notice the steps that make no sense.
Keep them in one place, and review them
One location, that everyone can reach, that is not a folder on your computer. Which tool matters far less than the fact that there is exactly one.
Then put a recurring reminder in the calendar to review them. Quarterly is enough for most businesses. Without that, documentation ages into fiction — and fiction that people were told to follow is a genuine liability when something goes wrong.
What good looks like after three months
You are not aiming for a manual. You are aiming for the point where:
- Someone else can do the end-of-month without asking you anything.
- A new person's first week does not consume yours.
- You can take a fortnight off and the phone does not follow you.
That is a realistic three-month outcome from five recordings and an afternoon. A complete operations manual is not, which is why so few of them exist.
What to do next
- Choose one of the five above — probably enquiry-to-job, since it touches revenue.
- Record yourself doing it the next time it comes up. Do not schedule a special session for it.
- Write the five headings under it. Twenty minutes.
- Give it to whoever else does that job and ask them to correct it.
- Then, and only then, start the second one.