SOPs (Standard Operating Procedures) document repeatable processes. Good SOPs are short, scannable, and outcome-focused.
Anatomy of a good SOP
- Title — verb-led (e.g. "Onboarding a new client").
- Purpose — 1–2 sentences on why this matters.
- Owner — the person responsible.
- Trigger — when this SOP runs (e.g. deal moves to Won).
- Steps — numbered, with clear actor for each.
- Definition of done — how you know it worked.
Template
## Purpose
Why this SOP exists.
## Owner
@person
## Trigger
What kicks this off.
## Steps
1. **[Role]** does [action] → [outcome].
2. ...
## Done when
- ✅ Customer received welcome email
- ✅ CRM updated with kickoff date
Tips
- One verb per step ("Send the invoice", not "Send the invoice and follow up").
- Link to related SOPs.
- Add screenshots for UI steps.
💡 Tip: Train your chatbot on your SOPs — it instantly becomes an internal helpdesk.