How to Write Standard Operating Procedures Your Team Will Actually Follow

A standard operating procedure (SOP) describes how a recurring task is done so that anyone trained can do it consistently. Good SOPs reduce mistakes, make holidays and sick days less disruptive, and make it possible to hand work to new people. Bad SOPs sit in a shared folder that nobody opens.

The difference is rarely the template. It is whether the document is short, accurate and easy to find at the moment someone needs it.

Choose the right processes first

Do not try to document everything. Start with processes that are:

• Frequent: done weekly or more, so small errors add up.
• Costly when wrong: invoicing, payroll inputs, customer onboarding, safety checks.
• Dependent on one person: the "only Priya knows how to do that" tasks.

Five well-written SOPs that people use are worth more than fifty that nobody reads.

A simple SOP format

1. Title: verb plus object, e.g. "Process a customer refund".
2. Purpose: one sentence on why the process matters.
3. When to use it: the trigger, such as "when a refund request is approved".
4. Who does it: the role, not the person's name.
5. What you need: systems, access and information required before starting.
6. Steps: numbered, one action each.
7. Done means: how to know the task is complete and correct.
8. Owner and last reviewed date.

Write steps people can follow

• Start each step with a verb: "Open", "Check", "Enter", "Send".
• One action per step. If a step contains "and then", split it.
• Show, do not describe. A screenshot with the right button circled saves a paragraph.
• Put warnings before the step they apply to, not after.
• Include the decision points: "If the amount is over 500, get approval from the finance lead before continuing."

Checklist or step-by-step?

Experienced staff do not need instructions for every click; they need a reminder not to skip anything. For them, a checklist works best. New starters and rarely performed tasks need detailed steps. Many teams keep both: a one-page checklist that links to the detailed version.

Test it with someone who has never done the task

Ask a colleague who does not normally do the process to follow the SOP while you watch, without helping. Every time they hesitate, the document needs work. This single test improves an SOP more than any amount of editing.

Keep SOPs alive

• Give every SOP an owner responsible for keeping it accurate.
• Put the review date on the document and check high-impact SOPs every six to twelve months.
• Update it when the process changes, not later. A wrong SOP is worse than none.
• Make feedback easy: a comment box or a named contact for corrections.

Get people to use them

• Store SOPs where the work happens: linked from the tool, the ticket or the task, not buried in a folder tree.
• Use them in onboarding and refer to them when answering questions ("It's step 4 in the refund SOP").
• Thank people who suggest improvements. Ownership spreads quickly when it is noticed.

Documented processes also make it far easier to quote fixed prices and scale; see how to price a service business.