How to write SOPs that people actually use

An SOP nobody opens is a document, not a procedure. Here is how to write the kind that gets used.

Write SOPs that people actually use by keeping each one to a single task on a single page, starting with the trigger, linking to the tools instead of describing them, keeping them where the work happens, and updating them the moment someone asks a question the SOP should have answered. A used SOP is short, current and easy to find. An unused one is long, stale and in a folder.

Why do most SOPs go unused?

Three reasons, all of them fixable.

  • They are too long. Written as manuals, with history and context and every possible case, so nobody reads them under time pressure.
  • They are hard to find. In a folder, in a document, in a system nobody opens during the working day.
  • They are out of date. The process changed, the SOP did not, so the team stopped trusting it.

Notice that none of these is about the team being lazy. They are about the document being badly designed for its job.

What does a usable SOP look like?

One page. One task. Five parts, the same as a good handover document: when this happens, what good looks like, the steps, the exceptions, who to ask.

Steps are short and start with a verb. Each one links directly to the template, form or tool it uses. Nobody should have to describe a screen in words when a link and a screenshot do it better.

If a task has more than about twelve steps, it is two tasks. Split it.

Where should SOPs live?

Where the work happens. If the team works in a project tool, the SOP is attached to the task template. If the work starts from an email, the SOP is linked in the email template. If the work happens in a spreadsheet, the SOP is a tab in the spreadsheet.

The test: can someone open the SOP in one click from the place they are when they need it? If not, move it.

How do you keep them current?

Make updating the SOP part of doing the task. Two rules:

  1. If anyone asks a question the SOP should have answered, the answer goes into the SOP that day, not into a chat message.
  2. If the process changes, the SOP changes in the same week, and the person who changed the process updates it.

Once a quarter, someone skims every SOP and archives the ones for tasks that no longer exist. A library of forty live SOPs is worth more than four hundred dead ones.

How does AI help with SOPs?

Two ways that save real time.

Writing. Record yourself doing the task once while talking through it. AI turns the transcript into a first draft in the five part format. You edit it down. An SOP that used to take an afternoon takes twenty minutes.

Answering. Put the SOP library behind an AI assistant the team can ask. "How do we handle a refund request?" returns the relevant SOP and a short answer. The library becomes something people talk to rather than search.

Where should you start?

With the ten tasks that generate the most questions. Not the most important tasks, the most asked about ones. Each written SOP removes a stream of interruptions immediately, and ten of them change the feel of the business in a month. Everything else can follow at one or two a week.

How long should the whole library take?

For a business under twenty people, roughly a quarter to write the core set, if it is done alongside the work rather than as a separate project. Recording tasks while doing them and letting AI draft the page is what makes that pace possible. A library written in a single crash week tends to be written from memory and to miss the exceptions.

How do you know it is working?

The founder stops getting asked how things are done. New people are productive in days. Mistakes drop, because the exceptions are written down. And when someone leaves, nothing leaves with them.

A complete SOP library, written and stored properly, is one of the main things a Full Build leaves behind, because it is what makes every other system durable.

Want this built inside your business?

I take on a small number of founders at a time. Start with a complimentary 30 minute conversation about your biggest bottleneck.

Book a private consultation

Complimentary. 30 minutes. Honest feedback either way.