Standard operating procedures: the guide for businesses that live in the owner's head

Most guides to standard operating procedures are written for factories, laboratories and workplaces where somebody could get hurt. They are about safety and compliance, and they are good at that.

This one is for a different problem. You run the business, too much of it runs through you, and the only way to change that is to get what is in your head into a form somebody else can use.

That is harder than it looks, and it is barely a writing job. Most SOP projects fail because owners write down the steps and keep the decisions. A year later there is a folder full of procedures and the business still stops when they go away.

What is a standard operating procedure?

A standard operating procedure is a written description of how a task gets done, detailed enough that someone else can do it properly without asking you.

The last six words are the whole test. If a competent person can follow it and produce the right result without coming to find you, it is an SOP. If they still need you to fill in the gaps, it is notes.

What are the five parts of an SOP?

Most templates converge on the same five components.

Purpose. What the task achieves and why. Without it people follow steps without understanding and cannot handle anything unexpected.

Scope. When this applies and when it does not. The edges matter more than the middle.

Steps. What to do, in order, specifically enough to act on.

Roles. Who does it, and who decides when something goes wrong.

Review. When it gets checked, because a procedure describing how you worked two years ago is worse than nothing.

All five appear in every template. Roles decides whether anything changes, and it is the one owners leave thin.

The rule that decides whether an SOP works

Steps describe a task. Decisions transfer it.

A procedure listing what to do produces someone who can perform the mechanics and still checks with you at every judgement point. One that also states what the person may decide, and the threshold where they stop and come to you, produces someone who can finish the job. That is why a folder of well-written procedures can leave a business exactly as dependent as it was.

What does a good SOP look like? A worked example

Take quoting a job, which most trades and construction businesses have. Most owners would write this.

Every line is true and nobody could use it. "Work out the costs" and "add the margin" are the actual job, and neither says how. Which rate card? Which margin, and does it change on bigger jobs? A new person reads that and still has to come and ask you.

The usable version looks more like this.

The second version carries thresholds, permissions and a named point where someone stops and asks. That is the difference between describing your job and handing part of it over.

How does this apply to my business?

Quoting is the trades version. Every industry has the same shape somewhere: a task where the steps are obvious but the judgement is not.

In professional services it is scoping and pricing an engagement. In e-commerce it is a refund outside policy. In wholesale it is extending credit to a slow-paying account. In a clinic it is who gets seen when the day is full. In hospitality it is what staff can do to fix a complaint before someone rings you.

None are hard to perform. All are hard to hand over, because the right answer depends on things that live in your head: what this client is worth, how far you bend, what you do when it is marginal. Those are your first SOPs.

Three questions to test what you have written

Once you have drafted one, check it against these.

Could someone follow this without knowing what I would want? If it relies on the reader guessing your preference, nothing has transferred.

Does it say what they may decide alone? Not what to do. What they can settle without asking.

Does it name the number or situation where they stop and come to you? A handover without a stated limit invites them to check everything.

Answer no to any of the three and you have written a description.

How do you find the right processes to write first?

The instinct is to be thorough, so people start at the beginning and work through everything. Two months later they have documented onboarding, filing and the stationery order, nothing has changed, and none of those were routing through the owner anyway.

A simpler method works in any business. For one week, note every time someone comes to you with a question or a decision. Change nothing, fix nothing, just write down what arrives and who brought it.

At the end of the week you will have a list. Whatever appears three or four times is your first SOP. It is your own business telling you where the dependency is, rather than a template guessing.

Write those first few properly, thresholds and permissions included. Then hand one to the person who will do it and leave them alone with it, because what they get wrong tells you what the document is missing and you cannot get that any other way.

Then repeat, slowly. Five procedures people use are worth more than fifty nobody opens.

What do you get out of this?

Four things, and only the last one has a price attached.

Work stops queueing behind you. Each interruption cost you the time to answer plus the time to get back into what you were doing. That is the return you feel first.

New people become useful faster. The solid research here is about onboarding rather than SOPs specifically. Brandon Hall Group found organisations with a strong onboarding process improve new hire retention by 82 per cent and productivity by over 70 per cent, and SHRM found new hires are 50 per cent more productive where a standard process exists. Documented procedures are part of how that gets built, though attributing those numbers to SOPs alone would be overclaiming.

Mistakes stop repeating. A mistake fixed in a procedure is fixed once. A mistake fixed verbally is fixed until the next new person.

At sale it changes what a buyer sees. This is the one with a number on it. Buyers look for evidence, over time, that the business kept working while the owner was not in it. our guide to key person risk covers why they discount when they cannot find it.

Are SOPs a legal requirement?

For commercial processes like quoting or invoicing, no. Work health and safety is different. Safe Work Australia sets out the duty this way:

Written procedures are one of the control measures in that hierarchy, and SafeWork NSW lists administrative controls as implementing "safety procedures and safe work practices" where higher-order controls are not enough (SafeWork NSW). Risk assessments are mandatory for specified high-risk work (SafeWork SA). WHS duties sit with your state regulator, so check what applies to your work with them.

Where a document stops being enough

One honest thing to finish on.

A written procedure gets someone to the point where they can do the work. It cannot do the next part, where they do it differently to you and you decide whether that is wrong or just not your way.

That decision is where most of this work dies. The owner sees the variation, steps back in, and the process drifts back to them. No template covers that, because it turns on what you are willing to let go of and how much difference you can live with before you take it back.

Worth knowing that is coming, because it arrives about three weeks after the first good SOP.

Frequently asked questions