How to Write an SOP: A Simple 7-Step Framework

Define the trigger, outcome, owner, inputs, steps, exceptions, and proof of completion, then validate with another operator.

The 7 Elements

1. Trigger: when the SOP starts
2. Outcome: what successful completion looks like
3. Owner: who performs the task and who approves changes
4. Inputs: systems, files, permissions, templates, data
5. Steps: the exact actions in execution order
6. Exceptions: what to do when the normal path fails
7. Proof of completion: evidence the task was done correctly

Who Should Write an SOP?

• Operator: drafts steps (knows the actual work)
• Manager: checks alignment with policy and scope
• Process Owner: owns approval, review cycle, controlled changes

How Much Detail Is Enough?

A trained teammate can complete the task without asking the author for help. Test it: ask someone else to follow it cold.

---

Originally published at claudiasop.com