Skip to content

SOPs5 steps1 template

Write an SOP someone else can actually follow

Record, draft, test, fix: a simple method for procedures that survive the hand-off.

You’ll get
A tested SOP a teammate or contractor can run without asking you.
Best for
Anyone about to delegate a recurring task.
Time
1–2 hours per SOP
Level
Starter

Tools: A screen recorder · A doc or wiki · One person to test it

Overview

Most SOPs are written from memory, at a desk, by someone who has done the task a hundred times. That is exactly why they skip the steps that matter. This method writes the SOP from the work itself, then proves it with a real test.

5 steps · 1–2 hours per SOP

The steps

  1. Step 1: Record yourself doing it

    20 min

    Do the task once while recording your screen and talking through why each step matters. Don’t write anything yet.

  2. Step 2: Draft from the recording

    30 min

    Turn the recording into numbered steps. One action per step, each starting with a verb. Add a screenshot wherever a click is easy to miss.

  3. Step 3: Add the edges

    15 min

    The parts people forget to write down are the ones that cause mistakes.

    • Trigger: when does this run?
    • Done: what does finished look like?
    • Common mistakes and how to fix them
    • Who to ask when stuck
  4. Step 4: Test it with someone new

    20 min

    Hand it to someone who has never done the task. Watch without helping. Every question they ask is a missing line.

  5. Step 5: Fix, date and own it

    15 min

    Update the SOP, add a version date and an owner. Review it whenever the task or the tools change.

    Tip: An SOP nobody owns is out of date within a quarter.

Before you call it done

The checklist

0 of 7 done

Your ticks are saved in this browser only.

Free to download

Templates

Use this playbook

Want it running in your business, not just on paper?

Set it up with me

Keep building

All playbooks →