SOP template

Fill in every field. Delete the italic guidance before publishing. The companion guide explains the reasoning behind each section.

Download: SOP template (Word, .docx)

The Word version is formatted the way it tells you to format yours: real heading styles, tables with marked header rows, no merged cells, and no information carried by colour alone. Export to PDF with tagging enabled and the structure survives.


Part 1 — The template

[Procedure title]

A task, stated as a noun phrase. “Filing an incoming FOI request,” not “FOI Policy.”

FieldValue
Document ID[Identifier, if your organization uses one]
Version[1.0]
Effective date[YYYY-MM-DD]
Owner[Role title, never a personal name]
Approver[Role title]
Next scheduled review[YYYY-MM-DD]

1. Purpose

One sentence. What this procedure produces. Start with the outcome, not a policy citation.

2. Scope

This procedure covers: [the cases it was written and tested for]

This procedure does not cover: [the adjacent cases readers will try to apply it to. Name the document that does cover them, if one exists.]

3. Roles

RoleResponsibility in this procedure
[Role title][What they do here. If a role does not appear in the steps, delete the row.]

4. Definitions

TermDefinition
[Term or acronym][Plain-language definition. Include only terms your stated audience will not know.]

5. Materials and access

Before starting, you need:

  • [System, account, or permission]
  • [Form, template, or reference document]
  • [Equipment or physical materials]

6. Procedure

One action per step. Imperative verb first. Condition before action. 15 to 20 words maximum. State the observable outcome where a reader needs to confirm success.

  1. [Step.]
  2. [Step.]
  3. [Step.]

Note: [Optional or explanatory content. Notes are never numbered — numbers mean sequential and mandatory.]

Where a step branches, replace it with a decision table:

IfThen
[Condition][Action, or “go to step N”]
[Condition][Action]

7. Exceptions and escalation

SituationAction
[The failure or edge case that actually occurs][What to do — specifically. “Consult your supervisor” is an answer only when no rule exists.]

8. Revision record

This procedure is revised when:

  • the underlying process changes
  • a referenced system or form is updated
  • the same exception occurs twice
  • testing finds a defect
  • [add organization-specific triggers]
  • annually, as a backstop
VersionDateAuthorWhat changed
1.0[YYYY-MM-DD][Role]Initial release.

Part 2 — Worked example

A completed one-page SOP, for reference. The scenario is illustrative.

Assigning a file number to an incoming records request

FieldValue
Document IDREC-004
Version2.1
Effective date2026-09-04
OwnerRecords supervisor
ApproverManager, Information Services
Next scheduled review2027-09-04

1. Purpose

Assign a tracking file number to a records request so it can be logged, routed, and reported on.

2. Scope

This procedure covers: requests arriving by email or mail that have no existing file number.

This procedure does not cover: requests arriving through the online portal, which are numbered automatically (see REC-007), or requests that continue an existing file (see REC-005).

3. Roles

RoleResponsibility in this procedure
Intake officerRuns steps 1 to 7.
Records supervisorReviews the entry after step 7 and resolves exceptions.

4. Definitions

TermDefinition
Received dateThe date the request arrived at the organization, not the date it was opened or processed.
RTSRecords Tracking System, the database where requests are logged.

5. Materials and access

Before starting, you need:

  • an RTS account with intake permissions
  • access to the shared intake mailbox
  • the current fiscal-year prefix, posted on the team wiki

6. Procedure

  1. Open the request and confirm it contains a requester name and a return address.
  2. If either is missing, log the request as incomplete and stop. Follow section 7.
  3. In RTS, select New request.
  4. Enter the received date from the postmark or email timestamp.
  5. Enter the requester name and return address exactly as written on the request.
  6. Select Generate file number. Confirm the status field reads Assigned.
  7. Send the RTS entry to the records supervisor for review.

Note (step 1): A phone number is not a return address. Email addresses are.

7. Exceptions and escalation

SituationAction
Requester name or return address missingLog as incomplete in RTS, select reason Insufficient information, and send the standard incomplete-request notice within 2 business days.
RTS unavailableRecord the request on the paper intake log. Enter it in RTS within 1 business day of the system returning.
Received date cannot be establishedUse the earliest verifiable date and add a note in the comment field explaining the basis. Do not leave the field blank.

8. Revision record

This procedure is revised when: the underlying process changes; RTS or the intake form is updated; the same exception occurs twice; testing finds a defect; annually as a backstop.

VersionDateAuthorWhat changed
2.12026-09-04Records supervisorStep 6 now names the Assigned status value; previously ambiguous.
2.02026-03-11Records supervisorAdded exception for RTS unavailability. Split old step 4 into steps 4 and 5.
1.02025-06-02Records supervisorInitial release.

Part 3 — Pre-publication checklist

Run this against the document before it goes out. Every item is pass or fail.

Structure

  • ☐ All eight sections are present, or a deliberate decision was made to omit one
  • ☐ Purpose is one sentence and names an outcome, not a policy
  • ☐ Scope states what is not covered, and names the document that covers it
  • ☐ Every role listed in section 3 appears in the steps
  • ☐ Every term defined in section 4 appears in the steps
  • ☐ No term is defined twice
  • ☐ Materials list is complete enough that a reader can start without stopping

Steps

  • ☐ One action per step; no compound steps hiding behind “and”
  • ☐ Every step opens with an imperative verb
  • ☐ Conditions come before actions
  • ☐ No conditional is nested more than one level deep; deeper logic is a decision table
  • ☐ The actor is named only where the work hands off
  • ☐ Steps a reader could get wrong state an observable outcome
  • ☐ Numbers are used only for sequential, mandatory actions; notes and options are bullets
  • ☐ No step exceeds 20 words
  • ☐ Screenshots appear only where the interface is genuinely ambiguous

Accessibility (WCAG 2.2 Level AA)

  • ☐ Headings use real heading styles, descending in order, no levels skipped
  • ☐ Tables have marked header rows, no merged cells, no blank spacing rows
  • ☐ Every image has alt text that carries the information, not a label
  • ☐ No information is conveyed by colour alone
  • ☐ Link text makes sense read out of context
  • ☐ PDF exports are tagged, with document language set and reading order checked

Testing and maintenance

  • ☐ At least one person who has not done the task has run the procedure while observed
  • ☐ Every logged hesitation has been resolved or consciously accepted
  • ☐ An owner is named by role title
  • ☐ Revision triggers are listed, not just a review date
  • ☐ The changelog says what changed, not that something did

Template by Adam Teeling, AD-DOC Deliverables. Free to use and modify; no attribution required. Companion guide: How to write an SOP that people actually follow.