The way your business runs, written down.

Every business already has a way it does things. The problem is that the way usually lives in one or two people's heads. When they are busy, on holiday or gone, quality wobbles and the same questions get asked again. A standard operating procedure fixes that by taking the best way to do a task out of someone's head and writing it down, in plain steps anyone can follow. Do this across the handful of tasks that decide your quality, and the business stops depending on heroics.

This page sets out what an SOP is, why it pays off commercially, how I turn the way you actually work into procedures your team will use, and what an engagement involves. It has a particular fit for restaurants and hospitality operators, where the same standard has to hold across shifts, sites and a steady churn of new starters.

What a standard operating procedure actually is

An SOP is a documented set of steps for completing a specific, recurring task to an agreed standard. It is deliberately narrow. One SOP covers one job: opening the kitchen, onboarding a new client in the CRM, processing a refund, closing the till. Each one answers the same simple question for whoever picks it up: what do I do, in what order, to get this right.

A good SOP is short, specific and written for the person doing the work, not for a filing cabinet. It names an owner, states when it applies, lists the steps in order, points to the tools or links needed, and says what "done well" looks like. That last part matters. A step that says "clean the station" means little; a step that says "wipe down, sanitise and restock to the line photo on the wall" can be followed and checked.

It helps to be clear about what an SOP is not. It is not a policy, which states a rule without telling you how to carry it out. It is not a training manual, which is broader and more about background. And it is not a process map. A process map shows the flow of a whole process and the handoffs between people; an SOP zooms into one task within that flow. The two work together, which is why SOP work so often follows on from process mapping: the map shows where the procedures need to exist, and the SOPs fill them in.

Why SOPs matter commercially

It is easy to treat documentation as housekeeping you will get to later. It is closer to insurance against the costs that quietly grow with you. Three of them in particular:

• Quality holds as you scale. At five people, everyone knows how things are done because they were there when it was decided. At twenty-five, the founders cannot be in every conversation, and standards drift unless the way of working is written down. An SOP is how the original quality survives the next ten hires.
• Onboarding gets faster and cheaper. Without SOPs, a new starter learns by shadowing whoever is free, picking up that person's habits and gaps along with the job. With them, they follow a tested procedure from day one and become useful in days rather than weeks. The cost of every hire drops.
• The business becomes less fragile. When the only person who knows how to run payroll, close the month or handle a key account leaves, that knowledge should not leave with them. SOPs move critical know-how out of individual heads and into the business, which protects you and, in time, makes the company easier to sell.

There is a quieter benefit too. Once a task is written down, you can finally improve it. You cannot optimise a process that only exists as a habit, because there is nothing to compare a change against. The SOP becomes the baseline, and every refinement sticks instead of evaporating the next time someone does it from memory.

How to write an SOP that gets followed

Most SOPs that gather dust were written the same way: someone sat at a desk and wrote down how they thought a task should be done. The result reads tidily and misses half of what really happens. The procedures people actually follow are built differently. Here is the approach I use.

Watch the work, do not imagine it

Start with the person who does the task well and watch them do it. Note every step, including the small ones they no longer think about, the tools they touch, the decisions they make and the points where things usually go wrong. The gap between how a task is described and how it is genuinely done is where SOPs live or die.

Write in plain, numbered steps

Each step should be one clear action, in the order it happens, written so a competent newcomer could follow it without asking. Use the words your team uses. Where a step involves a judgement, say what the judgement is and what to do at each branch. Add a screenshot or a photo where a picture is faster than a sentence, which in hospitality is often.

Name an owner and a standard

Every SOP needs one named owner who is responsible for keeping it accurate, and a clear statement of what the finished work should look like. Without an owner, the procedure rots the first time the task changes. Without a standard, nobody can tell whether it was followed properly.

Test it on someone new, then fix it

The real test is simple: hand the SOP to someone who has never done the task and watch them follow it. Every place they hesitate, guess or ask a question is a place the SOP is unclear. Fix those, and you have a procedure that works for the next person too, not just the one who wrote it.

Keep it where the work happens

An SOP saved in a folder nobody opens may as well not exist. It needs to live where the task is done: linked in the CRM record, pinned by the till, on the tablet in the kitchen. The easier it is to reach in the moment, the more likely it is to be used.

What goes in an SOP template

Using the same SOP template for every procedure makes the whole library easier to read, write and maintain, because the reader always knows where to look. A simple, reliable template includes the following.

Section	What it holds
Title and reference	A plain name for the task and a unique reference, so it can be found and linked.
Purpose	One line on what this procedure achieves and why it matters.
Scope	When the SOP applies and, just as usefully, when it does not.
Owner	The named person responsible for keeping it correct.
Steps	The numbered actions, in order, with any decision points spelled out.
Tools and links	The systems, files, logins or equipment needed to do the task.
Standard	What the finished output must meet to count as done well.
Review date	When the SOP is next checked, so it never silently goes stale.

Resist the urge to make the template longer. A heavy form with a dozen fields is a form nobody fills in. The aim is the least structure that keeps every SOP consistent and current.

How I approach the work

I do not start by writing procedures. I start by working out which ones are worth writing. Most businesses have hundreds of tasks and only a handful that genuinely decide quality, risk or cost. Those are where SOPs earn their keep, and where we begin.

Find the tasks that matter

Together we list the recurring tasks and rank them by impact: where do mistakes hurt most, where does onboarding drag, where does the business depend on one person. Often this sits on top of a wider view of how work flows, so SOP work pairs naturally with process mapping to see where the procedures belong before we write a word.

Capture the real procedure

For each chosen task I sit with the people who do it, watch the work and draft the steps with them, not for them. This is the part teams cannot easily do alone, because the people closest to a task are often too close to see which steps a newcomer would miss.

Wire SOPs into the systems

An SOP is far stronger when it lives inside the tool where the work is done. Where the task happens in the CRM, the procedure can be linked to the right record or stage, and the routine parts of it handed to CRM automation so the system does the remembering. This is where documentation stops being a separate chore and becomes part of the day.

Build the habit of upkeep

Finally we set the rhythm that keeps the library alive: owners, review dates and a simple way for anyone to flag a step that no longer matches reality. A set of SOPs is only as good as its last update, so the upkeep matters as much as the writing.

SOPs in restaurants and hospitality

Hospitality is where well-written SOPs show their worth fastest. The model runs on consistency the guest can feel, delivered across multiple shifts, often multiple sites, by a team that turns over far quicker than in most industries. A guest does not care who is on tonight; they expect the same plate, the same welcome and the same standard they had last time. SOPs are how that holds.

In practice that means written procedures for the tasks that protect the experience and the licence to operate: opening and closing checklists, food safety and hygiene steps, cleaning schedules, table service standards, reservation and complaint handling, cash and till routines. Each one means a new starter can be safe and useful in days, a manager can check a shift against a clear standard, and an inspector sees a business that documents what it does.

For multi-site operators the case is stronger again. SOPs are what let a second or third venue feel like the first rather than a looser copy of it, and they sit at the heart of the work I do on hospitality market entry across the Middle East, where a brand expanding into the region has to reproduce its standard in a new market with a new team. Get the procedures right and the brand travels. Leave them in someone's head and it does not.

Where SOPs sit in the bigger picture

SOPs rarely arrive on their own. They are usually part of getting the operation of a business onto solid ground, which is why this work connects to the wider growth consulting I do. A process map shows you the flow and the handoffs; the SOPs make each task in that flow repeatable; the CRM and its automation make the right procedure appear at the right moment. Together they turn a business that runs on memory into one that runs on a system, which is the difference between scaling and straining.

You do not need to document everything at once, and you should not try. Start with the five or ten tasks where consistency matters most, write those properly, prove they get followed, then widen out. A small set of SOPs that the team actually uses beats a thick manual that nobody opens, every time.