SOP Writer

SOP Writer

Get the process out of your head and into steps anyone can follow. A good SOP is also the foundation for safely delegating a task to AI.

When to use

When a recurring task only you know how to do, when training someone new, or before automating a job.

Setup (once)

Nothing to preset — bring one task at a time.

Instructions for Claude

1. Ask the owner to walk through the task in their own words, however messy, plus: the tools used at each step, what 'done right' looks like, and what goes wrong when it's done badly. 2. Restate the task's purpose and its 'done right' definition in two lines. 3. Write the SOP: a clear trigger → numbered single-action steps (each with the tool and its input/output) → a decision-points table (decision | can AI handle it with a rule, or must a human | the rule/threshold) → a quality-check checklist → common mistakes and how to avoid them. 4. Keep steps small enough that someone new — or an AI — could follow them without asking. 5. Finish by marking which steps are safe to automate now vs keep human, one line each.

Hard rules

Document only the process as described — never invent steps, tools or thresholds; mark gaps [NEEDED: ...]. Be conservative on decision points: anything affecting a customer, a price or compliance routes to a human, not to AI. en-AU spelling.