The template
Copy the structure below. Each field has one job; if a field is hard to fill in, that difficulty is the finding.
- Process name
- Verb plus object, as the team says it out loud. 'Route an inbound lead', not 'Lead Management Framework v2'.
- Owner
- One role accountable for the outcome. Not a committee, not a department.
- Last reviewed
- A date. Anything older than two quarters is presumed wrong until checked.
- Trigger
- The observable event that starts it. If the trigger is 'when someone notices', the process has no trigger yet.
- Inputs required
- What must exist before the process can start, and where each comes from.
- Decision rules
- The judgement calls inside the process, each with the rule and what to do when the answer is unclear.
- Exit condition
- How anyone else can verify it is genuinely finished.
- Exceptions
- The two or three situations that break the standard path, and the action for each.
- Escalation
- Who is told when it cannot be completed, and within what time.
- Related
- The systems and documents this touches, linked rather than copied.
A filled example
| Field | Content |
|---|---|
| Owner | Sales operations lead |
| Trigger | A lead record is created in the CRM from any source |
| Inputs required | Contact detail, source, and the form or call context |
| Decision rules | Existing account, route to the account owner. Otherwise territory rule, then round-robin among available reps. Unclear territory routes to the fallback owner rather than waiting. |
| Exit condition | Record has an owner, a due follow-up task, and an acknowledgement sent to the lead |
| Exceptions | Duplicate of an existing record: route to the existing owner and merge. Out of hours: assign, acknowledge with the next-window promise, and queue the task for the window opening. |
| Escalation | No first contact within the standard notifies the owner; at double the standard it notifies their manager |
Rules that keep SOPs alive
- One page. If it needs more, split the process — it is probably two.
- Describe decisions, not clicks. Interfaces change; judgement does not.
- Link it from the task or stage where it is needed, not from a folder.
- Update it in the same session as the process change, never later.
- Review on a fixed cadence and record the date on the document.
- Delete anything nobody has opened in two quarters — it is either wrong or unnecessary.
Related work
The failure this fixes is described in no SOPs, no accountability, and the audit that finds where documentation is missing is the operations audit playbook.
Muhammad Sameed Abid
Muhammad Sameed Abid is a business operations, automation and growth systems professional with 9+ years across operations management, workflow and CRM automation, marketing operations and customer success. He is currently Head of Customer Success at GHA Marketing and writes here about the operating layer underneath growth.