# How to write SOPs your team will actually use

_Foundations · updated 2026-08-29 · 6 min read · Altiora Business Development Ltd_

An SOP gets used when it is short, written for the person doing the job, stored where the work happens, and owned by a named person with a review date. Most SOPs fail because they are written once, written for an auditor rather than an operator, and filed somewhere nobody opens.

## Key takeaways

- Write for the person doing the job, not for an inspector.
- Name the owner and set a review date, or it will rot.
- Store it where the work happens, not in a folder nobody opens.
- Write the ones that hurt when they go wrong, and the ones only one person knows.

## What an SOP is actually for

An SOP has three jobs: the same output regardless of who is on shift, a training asset that shortens how long a new person takes to become useful, and proof that the business runs on process rather than on one person's memory.

That last one matters more than owners expect. A business that only works when you are in it is a job. A business that runs on documented process is an asset.

## The seven parts of an SOP that works

1. **Purpose, in one line** What this procedure produces, and why it exists.
2. **Owner** A named person, not a department. Unowned procedures are nobody's problem.
3. **Trigger** What starts it. A date, an event, or a customer action.
4. **The steps** Numbered, in order, naming the exact button, menu or field. Update the record is not a step. Open the deal in HubSpot, set Stage to Quote Sent, save, is a step.
5. **The exceptions** What to do when it does not go to plan, and who to escalate to.
6. **Success criteria** How you know the step worked. Without this, the SOP describes activity rather than outcome.
7. **Review date** When it gets checked. Six or twelve months. A procedure with no review date is a procedure that will quietly become wrong.

## Write it while doing the job

The fastest way to write an SOP is to record yourself doing the task once, then write down what you did. It takes a fraction of the time and captures the small decisions you would otherwise forget to mention.

Then cut. Most first drafts are twice as long as they need to be, and length is the main reason people stop reading a procedure halfway through.

## Where SOPs go to die

- A folder nobody opens. If the procedure is not one click from where the work happens, it does not exist.
- Written by someone who does not do the job. They document the theory, not the exceptions.
- No named owner. Everyone assumed someone else was maintaining it.
- No review date. The software changed, the procedure did not, and now nobody trusts any of them.
- Too long. Eight pages of prose is a policy. Nobody follows a policy at 4pm on a Friday.

> The test is simple. Hand the SOP to someone who has never done the task and watch them try. Every place they hesitate is a step you have not written properly.

## Which SOPs to write first

Two piles. Write these before anything else.

- The ones that hurt when they go wrong. Anything touching money, safety, compliance or a customer relationship.
- The ones only one person knows. Every single-person dependency is a risk sitting on your books until it is written down.

Everything else can wait. A business does not need forty procedures. It needs the eight that carry the risk.

## Frequently asked questions

### How long should an SOP be?

One page where possible, two at most. If it needs more, it is more than one procedure.

### Who should write it?

The person who does the job, edited by whoever owns the outcome. Written by a manager alone, it will describe a process that does not exist.

### How often should SOPs be reviewed?

Every six to twelve months, and immediately after anything changes in the underlying system or regulation.

### Do I need SOP software?

No. A shared document store with clear naming and named owners works. Buy software once you have procedures worth managing, not before.

---

Source page: https://altiorabd.com/guides/how-to-write-sops

Altiora Business Development Ltd, Leeds. enquiries@altiorabd.com