How to Write an SOP: Template, Example and a Free Generator
Most SOPs fail the same way: they are written once in a Word file, the process changes, and nobody updates the document. Start from the process diagram instead — who does what, in which order — and write the SOP from it. Here is the format, a full example, and the shortcut.
Process improvement · 2026-10-24 · 9 min read
What an SOP is for
A standard operating procedure describes how a recurring task is done so that anyone trained for it does it the same way: the same steps, the same checks, the same records. It is what a new hire learns from, what a quality or ISO auditor checks against, and what you fix when something keeps going wrong.
The sections every SOP needs
| Section | What goes in it |
|---|---|
| Header | Title, document number, version, owner, effective date |
| Purpose | Why the procedure exists and the result it guarantees |
| Scope | Where it starts and ends, who it applies to, what is out of scope |
| Definitions | Terms a newcomer may not know |
| Roles and responsibilities | Each role and what it owns |
| Procedure | Numbered steps: who, what, how, how long, what is produced |
| RACI matrix | Responsible, Accountable, Consulted, Informed for each step |
| Exceptions and escalation | What to do when a step fails or waits too long |
| Records | Evidence each step leaves and who keeps it |
| Revision history | Version, date, change, approver |
Step 1 — draw the process first
Before writing a sentence, draw the process as a swimlane diagram: one lane per role, one box per step, diamonds for decisions. It takes ten minutes and settles the questions that make SOPs vague — who exactly does this, what happens if the answer is no, where does it go next.
Example: A support ticket process: three roles, one decision, an escalation path.
Step 2 — turn each box into a numbered step
Follow the arrows from the start and number every box. Each step is written as Role — action, then 2–4 sentences on how to do it, what to check, and what it produces. Decisions become explicit rules:
- Step 3. Can L1 fix? (L1 Support) — If Yes (about 70% of cases) → go to step 4. The issue is understood and can be solved with L1 tools and access.
- If No (about 30%) → go to step 6. The cause is unclear or needs code or infrastructure access: escalate to L2 Engineers with the triage notes.
Tip: Write steps in the imperative — “Check the policy number”, not “The policy number should be checked”. It is shorter and leaves no doubt about who acts.
Step 3 — fill in the RACI matrix
For each step, mark one role R (does it) and exactly one A (owns the result). Usually the doer is also accountable (A/R) unless a review or approval in another lane follows. Mark I for whoever receives the hand-off and C for anyone whose input is needed.
| Step | Customer | L1 Support | L2 Engineers |
|---|---|---|---|
| 1. Raise ticket | A/R | I | |
| 2. Triage ticket | A/R | ||
| 3. Can L1 fix? | A/R | I | |
| 6. Investigate | A/R | ||
| 7. Fix and reply | I | A/R |
Step 4 — exceptions, records and targets
Look at every loop and every “No” branch in the diagram: each one is an exception the SOP must explain. Then list the records each step leaves (the ticket, triage notes, the reply). If you know how long steps take, add targets — time per case and cost per case — so the SOP doubles as a performance standard.
The shortcut: generate the SOP from the diagram
In AI Flowchart, open your swimlane or BPMN diagram and press 📄 SOP. The lanes become the roles, the boxes become numbered steps in arrow order, and decisions become “If… go to step…” rules, with a RACI matrix filled in from the hand-offs. ✨ Write full SOP with AI then writes the instructions, decision criteria, exceptions, records and training notes — without being able to add or reorder steps — and you download it as Word or PDF.
Open the support ticket SOP example →
Because the document is generated from the diagram, updating the process means editing the diagram and regenerating — the SOP never drifts out of date. Add step times and the process simulator puts the expected time and cost per case into the SOP too.
Frequently asked questions
How long should an SOP be?
As short as possible while still letting a trained newcomer do the task without asking. For a process of 5–15 steps that is usually 2–5 pages including the RACI matrix.
What is the difference between an SOP and a process map?
The process map (swimlane or flowchart) shows the flow at a glance; the SOP explains each step in words — how to do it, what to check, what to record. Good SOPs include or reference the map.
Who should approve an SOP?
The process owner (the role accountable for the outcome), plus quality or compliance if the process is audited. Record the approver and date in the revision history.