SOP guide · Evaluated September 2026
How to Write an SOP in 7 Steps
Best SOP Software reviewers · From vendor pricing, help-centre and product pages · Evaluated September 2026
Plain answer
To write an SOP, scope one task with a clear start and end, capture how an expert does it today, write numbered steps that start with a verb, add roles, checks and warnings, then get a second person to review it and an owner to approve it. Publish it where staff work, train people on it, and set a date to review it again. The fastest drafts come from recording the task; the SOPs that stay accurate have an owner and a review date.
The life of an SOP, and which tools document each stage
A tool is listed under a stage when its own public pages describe a feature for that stage. This shows what vendors document, not how the features perform in use. Sources are on each review.
| Stage | What happens | Tools that document it |
|---|---|---|
| 1 Draft | Capture or write the steps | |
| 2 Review | A second person checks it |
|
| 3 Approve | An owner signs off |
|
| 4 Publish | Staff can find the current version | |
| 5 Train | People read, practise, confirm |
|
| 6 Audit | Prove who changed what, when |
|
| 7 Revise | Update and re-approve |
What is an SOP, in one sentence?
A standard operating procedure is a written, approved description of how a recurring task is done, by whom, and how you know it was done right. It exists so the task comes out the same way whoever does it. For drug manufacturers the requirement is written into US regulation: 21 CFR 211.100 requires 'written procedures for production and process control' and says any deviation 'shall be recorded and justified'.
What are the 7 steps to write an SOP?
1. Scope one task
Name the task, where it starts and where it ends, and who it is for. 'Process a refund over $500 in the billing system' is an SOP. 'Customer service' is not. If the scope needs more than about 15 steps, split it into two SOPs or a process with linked SOPs.
2. Capture how it is done today
Watch or record an experienced person doing the task. A screen-capture tool (Haiku, Scribe, Tango or Whale's Step Recorder) turns each click into a numbered step with a screenshot, which is faster than writing from memory and catches steps experts skip without noticing.
3. Write the steps
One action per step, starting with a verb: 'Open', 'Select', 'Enter', 'Confirm'. Put the expected result after the action when it helps: 'Select Refund. The refund form opens.' Use the names that appear on screen, in bold. Keep numbers, limits and thresholds in the step, not in a separate note.
4. Add roles, checks and warnings
State who performs the task and who is accountable. Mark decision points ('If the amount is over $500, go to step 7'). Put warnings before the step they apply to, not after. Add a check at the end: how does the person know the task is complete?
5. Review it with a second person
Ask someone who did not write the SOP to follow it exactly. Every place they hesitate is a missing step or an unclear word. In SOP software this is a review or suggestion step: SweetProcess lets teammates suggest improvements, and Process Street lets reviewers approve or reject with comments.
6. Approve and publish it
A named owner signs off, the SOP gets a version number and an effective date, and the previous version is retired. Publish it where people do the work: a link in the tool, an embed in the help center, or a library staff already search.
7. Train, then schedule the next review
Tell the people affected, ask them to read it, and check they understood (a short quiz or a read confirmation). Set a review date, for example 12 months out or sooner for fast-changing systems. Whale's Review Intervals and Trainual's e-signatures are examples of tools that support this step.
What does a finished SOP look like?
Issue a refund over $500
SOP ID: FIN-014 · Version: 2.1 · Effective: 1 Oct 2026 · Owner: Billing operations lead · Review by: 1 Oct 2027
- Purpose
- Make sure refunds over $500 are approved and recorded the same way every time.
- Scope
- Applies to refunds over $500 in the billing system. Refunds of $500 or less follow FIN-013.
- Roles
- Billing specialist performs. Billing operations lead approves.
- Steps
- Open the customer account in the billing system.
- Select Refund on the invoice. The refund form opens.
- Enter the amount and the reason code.
- If the amount is over $2,000, stop and request finance approval (see FIN-020).
- Select Submit for approval.
- After approval, confirm the refund shows as Issued.
- Add a note to the account with the approval ID.
- Check
- The refund status is Issued and the account note contains the approval ID.
- Revision history
- 2.1 (Sep 2026) reason codes updated · 2.0 (Mar 2026) approval step added
What are the most common mistakes when writing an SOP?
- Writing the ideal process instead of the real one. Capture what people do, then fix it in review.
- Several actions in one step. If a step has 'and' in it twice, split it.
- No owner. An SOP without an owner is out of date within a year.
- No version or effective date, so nobody knows which copy is current.
- Screenshots that show personal or customer data. Blur them; Haiku, Scribe and Tango all offer blur or redaction.
- Stored where nobody looks. If staff cannot find it in under a minute, they will ask a colleague instead.
Where next?
Frequently asked questions
How long should an SOP be?
As long as the task needs and no longer. Most single-task SOPs run 5 to 15 steps. If yours is longer, split it into linked SOPs or turn it into a process with sub-procedures.
Can AI write an SOP?
AI can draft the steps, and capture tools can write each step from a recording. A person who does the task still needs to review it, and an owner still needs to approve it.
Who should write an SOP?
The person who does the task, or someone watching them, with a second person reviewing and the process owner approving.
How often should SOPs be reviewed?
Set a fixed review date when you publish. Many teams use 12 months, and sooner when the system or regulation behind the task changes.