What’s inside
- Document control block with owner, version and review date
- Purpose, scope, roles and definitions
- Step table with action, expected result and owner
- Exceptions and troubleshooting table
- Quality checks and revision history
How to use it
- Write one SOP per task.
- Fill in document control and scope.
- Write each step as a single action starting with a verb, with its expected result.
- Test it with someone who has never done the task, then set a review date.
FAQ
How detailed should an SOP be?
Detailed enough that someone new can complete the task without asking. If they get stuck, add the missing step.
What is the difference between an SOP and a checklist?
An SOP explains how and why; a checklist only confirms what was done. Many SOPs end with a short checklist.
How often should SOPs be reviewed?
Every six to twelve months, or whenever the tool or process changes.
