Path: Home · Guides · How to write an SOP that people actually follow
How to write an SOP that people actually follow
Most standard operating procedures are written to prove that a procedure exists. That is a different document from one written to be used while doing the work, and the two fail in opposite directions. The first is complete, defensible, and unread. The second is short enough to hold in one hand.
This guide covers the second kind. It ends with a template you can fill in.
Why SOPs get ignored
Four failure patterns account for most of it.
Written for the auditor. The document answers “can we demonstrate a controlled process?” rather than “what do I do now?” Symptom: a purpose statement that cites a policy number before it names a task.
No owner. Nobody is named as responsible for the document, so nobody updates it. Within two revision cycles of the underlying process, staff learn that the SOP is wrong and stop consulting it. The document is now worse than absent, because it still looks authoritative to anyone new.
Conditional logic buried in prose. “In cases where the request originates outside the department, and where the requester has not previously been assigned a file number, the intake officer will, prior to escalation, verify…” A reader executing this has to hold three conditions and a sequence constraint in working memory while doing something else with their hands.
No revision trigger. The review cadence is annual, so a process change in month two lives in an email thread for ten months. Cadence is a backstop, not a trigger.
Decide what the document is for before writing it
Four answers, written down, before the first section heading:
| Question | Bad answer | Useful answer |
|---|---|---|
| Scope — what does this cover? | “Records management.” | “Filing an incoming FOI request, from receipt to file-number assignment.” |
| Audience — who executes this? | “Staff.” | “Intake officers in their first six months, working without a supervisor present.” |
| Trigger — when does someone open this? | “As needed.” | “A request arrives by email or mail and has no file number.” |
| Success — what is true afterwards? | “The process is followed.” | “The request has a file number, an assigned officer, and a logged received-date.” |
The audience answer governs everything downstream. A procedure for someone in their first six months defines terms and states the obvious. A procedure for a specialist who runs it forty times a week does neither, and padding it wastes their attention. Write for one of them, not the average of both.
The eight sections an SOP needs
| # | Section | Purpose | Common error |
|---|---|---|---|
| 1 | Purpose | One sentence: what this procedure produces. | Opening with a policy citation rather than an outcome. |
| 2 | Scope | What is covered, and explicitly what is not. | Omitting the exclusions, so the document gets applied to cases it was never tested against. |
| 3 | Roles | Who does what, by role title, not personal name. | Listing roles that never appear in the steps. |
| 4 | Definitions | Terms a first-year reader will not know. | Defining terms everyone knows, and skipping the acronym in step 6. |
| 5 | Materials and access | Systems, forms, credentials, and equipment needed before starting. | Discovering mid-procedure that the reader needs an account nobody mentioned. |
| 6 | Procedure | The numbered steps. | Everything below. |
| 7 | Exceptions and escalation | What to do when a step fails or a condition does not hold. | Sending the reader to “consult your supervisor” for the three cases that actually occur. |
| 8 | Revision record | Version, date, owner, approver, and what changed. | A version number with no changelog, which tells a reader nothing about whether their memory of the old process is still valid. |
Sections 1 to 5 exist so section 6 can be short. If the procedure steps are carrying definitions and prerequisites inline, the front matter is not doing its job.
Writing the procedure steps
Nine rules. They are not stylistic preferences; each one removes a specific class of execution error.
- One action per step. If a step contains “and,” check whether it is two steps. A reader interrupted halfway through a compound step cannot tell where they stopped.
- Imperative verb first. “Enter the file number.” Not “The file number should be entered” and not “The intake officer enters the file number.” The reader knows who they are.
- Condition before action. “If the request has no return address, log it as incomplete.” The reader must be able to skip an inapplicable step without reading it fully.
- No nested conditionals beyond one level. Two levels of “if” inside a step means the step is a decision table. Make it one — a two-column table of condition and action outruns any prose formulation.
- Name the actor only when it changes. Steps stay in second person until the work hands off. At handoff, say so explicitly: “The records supervisor reviews the entry.”
- State the observable outcome. “The status field reads Assigned.” A reader needs to confirm the step worked before committing to the next one.
- Number for reference, not decoration. Numbered steps are sequential and mandatory. Anything optional, parallel, or explanatory is a bullet or a note. Mixing the two teaches readers that the numbers mean nothing.
- Cap steps at 15 to 20 words. The same limit the BC Web Style Guide sets for sentences. A step that will not fit is usually two steps or a step plus a note.
- Define each term once, in section 4. A term redefined in the steps is a term the writer did not trust the reader to have read. Fix the definition instead.
Screenshots and diagrams: include one only where the interface is genuinely ambiguous. Every screenshot is a maintenance liability that expires at the next interface update, and an SOP full of stale screenshots loses authority faster than one with none.
Formatting for accessibility
Public sector documents in British Columbia are held to WCAG 2.2 Level AA. The guidelines are written for web pages, but most procedures ship as Word or PDF, so the requirements have to be translated. Six that matter for procedures:
- Use real heading styles. Heading 1, Heading 2, Heading 3 — applied as styles, descending in order without skipping. Bold 14-point text is not a heading to a screen reader, and a procedure whose sections are invisible to assistive technology cannot be navigated at all.
- Build tables as tables. Header row marked as a header row, no merged cells, no blank rows used as spacing. Decision tables are the most useful structure in an SOP and the most commonly broken one.
- Write alt text that carries the information. For a process diagram, alt text describes the sequence, not the picture. “Flowchart” is not alt text. If the alt text cannot be written, the diagram is carrying information that belongs in the steps.
- Never let colour be the only cue. A red row meaning “stop” needs a word as well.
- Make link text stand alone. “See the intake form” rather than “click here.” Screen reader users routinely list a document’s links out of context.
- Tag the PDF. Export with tags, set the document language, and check the reading order. An untagged PDF of a perfectly structured Word file discards the structure at the last step.
None of this changes what the procedure says. All of it changes whether some of your staff can use it.
For the full requirement picture — what is mandatory, what is convention, and what the standards do not reach — see Plain language requirements in the BC public sector.
Testing it
An SOP is a piece of software that runs on people, and it gets tested the same way.
- Find someone who has not done the task. New staff are ideal; anyone outside the team works.
- Give them the document, the access they need, and a real case.
- Sit where you can see them. Say nothing.
- Write down every hesitation — a pause, a scroll back, a reread, a glance up.
- Answer questions only after they have given up on that step, and log what they asked.
Hesitation is the primary defect signal. Not failure. A reader who completes the task after rereading step 7 four times has found a defect in step 7, and will report the document as “fine” if you ask them afterwards. Watch, do not survey.
Two testers usually surface most of what a procedure gets wrong; longer documents need more. The second tester’s independent stumble on the same step is confirmation; a step only one person struggled with may be that person.
Keeping it current
Name an owner by role, in the document. “Records supervisor,” not a person who will change jobs.
Define revision triggers, not just a cadence. An SOP is revised when the underlying process changes, when a system it references is updated, when an exception occurs twice, or when testing finds a defect — and, as a backstop, annually. The trigger list belongs in the revision record section where the next editor will see it.
Log what changed, not just that something did. “v2.1 — step 6 now specifies the Assigned status value; previously ambiguous” tells a reader whether their memory of the old procedure is still safe. “v2.1 — minor updates” tells them nothing and costs them a full reread.
Keep the changelog in the document. Version history in a separate system is version history nobody reads.
Download the template
The SOP template is a fillable skeleton with all eight sections, inline guidance on what belongs in each, a completed one-page example, and a pre-publication checklist covering the step rules and the accessibility pass.
Use it, change it, strip the guidance out. It carries no attribution requirement.
Written by Adam Teeling, a technical writer in Vancouver, BC. For procedure and policy documentation work, see plain language editing and policy documentation.