SOP Template¶
How to Use¶
Copy this file to a new, appropriately named concept file whenever you write a new SOP.
🧩 SOPs should be written so someone new can follow them without additional context.
SOP Title¶
SOP: {{SOP name}}
Purpose¶
{{What this SOP achieves and why it exists.}}
When to Use This SOP¶
{{Trigger conditions (e.g., "Use when a new client signs").}}
Owner¶
| Field | Value |
|---|---|
| Primary owner | {{Name / role}} |
| Backup owner | {{Name / role}} |
Inputs Required¶
| Input | Where it comes from | Notes |
|---|---|---|
| {{Input 1}} | {{Source}} | {{Notes}} |
| {{Input 2}} | {{Source}} | {{Notes}} |
Step-by-Step Process¶
Step 1: {{Step name}}¶
- {{Action}}
- {{Action}}
Step 2: {{Step name}}¶
- {{Action}}
- {{Action}}
Step 3: {{Step name}}¶
- {{Action}}
Quality Checklist¶
- Output matches acceptance criteria
- Work is documented (links, notes, decisions)
- Risks and assumptions are recorded
- Stakeholders informed (if needed)
Common Problems and Solutions¶
| Problem | Likely cause | Solution |
|---|---|---|
| {{Problem}} | {{Cause}} | {{Fix}} |
| {{Problem}} | {{Cause}} | {{Fix}} |
Escalation Path¶
| Severity | When to escalate | Who to escalate to | How |
|---|---|---|---|
| Low | {{Condition}} | {{Role}} | {{Slack/Email}} |
| Medium | {{Condition}} | {{Role}} | {{Slack/Email}} |
| High | {{Condition}} | {{Role}} | {{Call + message}} |
🚨 If client delivery is blocked, or a data/security risk is present, treat it as High severity.
Review Metadata¶
| Field | Value |
|---|---|
| Last reviewed date | {{YYYY-MM-DD}} |
| Review frequency | {{Monthly / Quarterly / Yearly}} |
| Next review due | {{YYYY-MM-DD}} |
Change Log (Optional)¶
| Date | Change | Owner |
|---|---|---|
| {{YYYY-MM-DD}} | {{What changed}} | {{Name}} |