A process that only lives in one person's head isn't documented, it's a risk. This gives a new team member enough to follow the process without pulling you into it.
[Process name]
Last updated: [date] · Owner: [name]
Purpose
[One sentence describing what this SOP is for.]
Overview
[A short summary of the process or setup this document covers.]
Key resources
[Links to anything referenced within the process, tools, dashboards, related docs.]
Definitions
[Any terms someone new would need explained to follow this.]
| Stakeholder / team | Role in the process |
|---|---|
| [team name] | [what they're responsible for here] |
| [team name] | [what they're responsible for here] |
Process: Milestone 1: [name]
[Detailed steps in order, written as action statements starting with a verb. Note the systems used and link to a sample ticket or case that shows standard work.]
Process: Milestone 2: [name]
[Same structure. Break the process into as many milestones as it actually needs, don't force it into three if it's really five.]
Service level expectations
[Any timelines or turnaround expectations tied to this process.]
Quality control
[How success is measured, what gets checked, and who checks it.]
| Reviewer | Title | Date |
|---|---|---|
| [name] | [title] | [date] |