# How to write SOPs your team will actually use

> How to write SOPs your team will actually use: what a standard operating procedure should include, a simple format, and how to keep SOPs current.

**To write an SOP your team will actually use, write it with the person who does the work, keep it to the steps, the owner and the checks, test it with someone new, and give it an owner and a review date.** Most SOPs fail not because they are badly written, but because nobody owns them once they are written.

## What is an SOP?

A standard operating procedure (SOP) is a written, step-by-step description of how a routine task is done, who does it and how you know it was done correctly. Good SOPs let work happen the same way whoever does it, and let a leader step back without things slipping.

## Why do most SOPs go unused?

- **They describe the ideal, not the reality,** so people quietly ignore them.
- **They are too long** to use while doing the job.
- **They live somewhere nobody looks,** such as a forgotten shared drive.
- **Nobody owns them,** so they go out of date and lose trust.
- **They were written to tick a box,** not to help the person doing the work.

## Which processes should you document first?

Start with processes that are frequent, that customers feel, or that only one person knows how to do. If work stops when one person is on holiday, that process needs an SOP. If you are not sure where the real problems are, [map the process first](/blog/what-is-business-process-mapping).

## What should an SOP include?

| Section | What it answers |
|---|---|
| Purpose | Why does this task exist? |
| Owner | Who is accountable for this SOP and for the result? |
| When it applies | What triggers the task, and what is out of scope? |
| Before you start | Which tools, access and information are needed? |
| Steps | What happens, in order, and who does each step? |
| Checks | How do you know it was done correctly? |
| Exceptions | What should someone do when something unusual happens? |
| Review date | When will the owner next check this is still right? |

## How do you write an SOP step by step?

1. **Watch the task being done,** or ask the person to talk you through it.
2. **Write the steps as they really happen,** including workarounds worth keeping.
3. **Start each step with a verb,** such as "check", "send" or "approve".
4. **Add the checks,** so the person doing it knows when it is right.
5. **Test it with someone new** and fix every point where they get stuck.
6. **Name an owner and a review date,** and store it where the work happens.

## How do you keep SOPs up to date?

Give every SOP an owner, review it on a set date and whenever the process or tool changes, and make it easy for the people using it to flag problems. An out-of-date SOP is worse than none, because people stop trusting all of them.

## Where does AI fit in?

AI can help draft an SOP from notes or a recording, but a person who does the work should check it, and a named owner should approve it. AI works best on processes that are already clear, and it should not be the only record of how work is done.

## How can VMS Ops help?

Our [Map Sprint](/map-sprint) maps how work really flows across your teams and tools, so you know which processes to document first and what good looks like. [Operations consulting](/operations-consulting) then helps put owners, SOPs and checks in place so decisions do not all run through the founder.

**Free 45-minute operations audit.** You get your top 3 bottlenecks in writing, a quick AI check, a 1 to 5 operations and AI readiness score and one recommended next step. No system access needed. [Book a call](/book-a-call).
## Related reading

- [What is business process mapping?](https://vmsops.com/blog/what-is-business-process-mapping)
- [When the founder is the bottleneck](https://vmsops.com/problems/founder-is-the-bottleneck)
- [Map Sprint: map the process before you write it down](https://vmsops.com/map-sprint)
- [Operations consulting](https://vmsops.com/operations-consulting)
- [More insights from VMS Ops](https://vmsops.com/blog)


## Frequently asked questions

### What is an SOP?

A standard operating procedure (SOP) is a written, step-by-step description of how a routine task is done, who does it and how you know it has been done correctly.

### What should an SOP include?

A clear purpose, an owner, when it applies, what is needed before starting, the steps in order, the checks that confirm it is done correctly, and a review date.

### How long should an SOP be?

As short as it can be while still letting someone new complete the task correctly. Many good SOPs fit on one or two pages.

### Who should write an SOP?

The person who does the work should help write it, with a manager or owner who approves it. SOPs written only by managers often describe how work should happen, not how it does.

---
Source: https://vmsops.com/blog/how-to-write-sops
Organisation: VMS Ops, operations consulting serving the US and UK. https://vmsops.com/
Book a call: https://vmsops.com/book-a-call (a short form, then a free 45-minute operations audit)
Last updated: 2026-11-09
Facts last verified: 2026-11-09