SOP: Procedure name
SOP – prerequisites, steps, escalation
How to use: Repeatable procedures. Write steps for someone doing it tired; `CRITICAL` marks what can't be skipped.
Preview
SOP: Procedure name
Standard Operating Procedure – the document that lets anyone do the task correctly without asking.
| Field | Value |
|---|---|
| SOP ID | SOP-NNN |
| Version | N.N |
| Owner | Role / @name |
| Approved by | @name |
| Effective | YYYY-MM-DD |
| Review cycle | Quarterly / yearly |
Purpose
What this procedure achieves and when it applies.
Scope
- Applies to: roles, situations
- Does not apply: exceptions
Definitions
| Term | Meaning |
|---|---|
| Term | Definition |
Prerequisites
- Access / permissions needed
- Tools or materials
- Training required before performing this SOP
Procedure
- Step one – action. Checkpoint: expected result.
- Step two – action.
- Sub-step detail
- Step three –
CRITICAL: what must not be skipped. - Verification – how to confirm the procedure succeeded.
Troubleshooting
| Symptom | Cause | Action |
|---|---|---|
| What you see | Why | What to do |
Escalation
When to stop and escalate, and to whom – role + contact.
Revision history
| Version | Date | Change | Author |
|---|---|---|---|
| 1.0 | YYYY-MM-DD | Initial | @name |