How to Write a Standard Operating Procedure Your Team Will Actually Use

In many small businesses, the most important processes live in one place: the owner’s head. Invoices get sent because the owner remembers. New clients get a good welcome because one employee knows the steps. That works until someone is sick, on holiday, or leaves. Then quality drops, mistakes repeat, and the owner gets pulled back into work they thought was handled.

A standard operating procedure, or SOP, is the fix. It is a short written guide that shows how a task is done, step by step, so anyone trained on it gets the same result. The problem is that many SOPs are written once, run to ten pages and are never opened again. Here is how to write one your team will actually use.

Step 1: Pick the right process first

Do not try to document everything at once. Start with one process that meets at least two of these tests:

• It happens often. Weekly or daily tasks give the fastest return.
• Mistakes are costly. Billing, client onboarding, payroll and data backups are good examples.
• Only one person knows it. If that person left tomorrow, the task would stall.
• You want to hand it off. Anything the owner does that someone else could do.

Write down three candidates and choose one. You can do the next one next week.

Step 2: Watch it being done, then write

The best SOPs come from watching the real work, not from memory. Ask the person who does the task to do it while you take notes, or have them record their screen and talk through each click. People skip steps they do without thinking, and those are exactly the steps a new person needs.

Capture three things as you go: each action in order, the tools or files used, and any decision point (“if the client has not paid the deposit, stop here and send reminder email B”).

Step 3: Use a simple, fixed format

Every SOP in your business should look the same, so people know where to find things. A one-page template with these sections is enough for most tasks:

1. Name and purpose: one line on what the process is and why it matters.
2. Owner: the person responsible for the process and for keeping the SOP up to date.
3. When it runs: the trigger, such as “every Friday” or “when a new client signs”.
4. What you need: logins, templates, files and tools.
5. Steps: numbered, one action per step, starting with a verb.
6. Done means: how you know the task is complete and correct.
7. Last reviewed: a date.

Keep steps short. “Open the client folder and copy the onboarding checklist” is better than a paragraph of explanation. Add a screenshot where a step is easy to get wrong.

Step 4: Test it with someone new

Hand the draft to someone who has never done the task and ask them to follow it exactly, without help. Sit nearby and stay quiet. Every time they hesitate, ask a question or get stuck, the SOP has a gap. Fix it, then test again. Two rounds usually make a draft solid.

Step 5: Store it where the work happens

An SOP nobody can find is no better than no SOP. Keep all of them in one shared place, such as a shared drive folder or a project management tool, with clear names. Link each SOP from the place the task starts: put the invoicing SOP link inside your accounting checklist, and the onboarding SOP link in your new-client template.

AI assistants can help here too. As we covered in our post on running projects with an AI assistant, a tool like Claude can turn rough notes or a screen recording transcript into a clean first draft in minutes. A person who does the work should still check every step.

Step 6: Review it on a schedule

Processes change: a new tool, a new price, a new rule. Give every SOP an owner and a review date, every six or twelve months for most tasks. Also update it any time someone finds a step that no longer matches reality. A short note at the bottom (“Updated 3 Nov: new invoice template”) keeps everyone confident they are reading the current version.

Key takeaways

• Start with one frequent, high-risk process that only one person knows.
• Write from watching the real work, not from memory.
• Use the same one-page format for every SOP, with numbered steps that start with a verb.
• Test each SOP with someone new and fix every point where they get stuck.
• Store SOPs where the work starts, and give each one an owner and a review date.

Need help documenting how your business runs?

Clear processes are the base of a business that can grow without the owner doing everything. Our management consulting services help small teams map, document and improve the work that matters most. Book a consultation and we will help you pick your first processes and get them written.