What are the sections of an SOP, in order?
| Section | What goes in it | Typical length |
|---|---|---|
| Header | Title naming one task, SOP number, version, date, owner, approver, next review | A small table |
| 1. Purpose | Why the SOP exists and what it protects | One or two sentences |
| 2. Scope | When it applies and when it does not | Two lines |
| 3. Responsibilities | Who performs, who approves, who keeps it current, as roles | Three rows |
| 4. Prerequisites | Access, documents and tools needed before starting | A short list |
| 5. Procedure | Numbered steps, one action each, starting with a verb | Five to fifteen steps |
| 6. Checkpoints | What to verify, taken from real mistakes | Two to four items |
| 7. Error cases | What to do when something goes wrong, and who to tell | A small table |
| 8. Related documents | Work instructions, forms, other SOPs | A short list |
| 9. Revision history | Version, date, who changed what | One row per change |
The SOP template follows this order and can be downloaded as Word or PDF. Filled-in versions are in the SOP examples. For what the term itself means, see what does SOP stand for.
What does the header look like when it is filled in?
The header is the part readers check first: is this the right document, and is it current? A filled-in header for a refund procedure looks like this.
| Field | Value |
|---|---|
| Title | Process a customer refund |
| SOP no. | SOP-012 |
| Version | 1.2 |
| Date | 2026-10-05 |
| Owner | Support manager |
| Approver | Operations director |
| Next review | 2027-04-05 |
The title names one task with a clear start and end. Owner and approver are roles, so the header survives a staff change. The review date is a real date, not “yearly”.
Which SOP format should I use: steps, hierarchy or flowchart?
| Layout | Best for | Looks like |
|---|---|---|
| Simple step list | Short tasks with no decisions, up to about ten steps | 1, 2, 3 |
| Hierarchical steps | Longer tasks where a step has several parts | 1, 1a, 1b, 2 |
| Flowchart | Tasks with several decisions and different paths | Boxes and arrows, yes or no branches |
When in doubt, start with a simple step list. Move to a hierarchy when steps need sub-steps: “3. Enter the customer details” becomes “3a. Type the company name”, “3b. Select the country”, “3c. Enter the tax number”. Add a flowchart only when readers have to choose between paths more than twice; a flowchart is harder to keep current than a list.
How do you format the steps themselves?
- Start with a verb: “Click Save”, “Enter the amount”.
- One action per step. Two actions joined by “and” are two steps.
- Name buttons and fields exactly as the screen shows them, in bold.
- Put a warning before the step it belongs to, not at the end of the page.
- Say what the reader should see when the step worked.
- Add a screenshot where the reader could hesitate.
What are the most common SOP format mistakes?
- The title names a department, not a task. “Accounting procedures” cannot be followed; “Enter a supplier invoice” can.
- The purpose repeats the title. Say what goes wrong without the SOP: late refunds, wrong tax rates, missing records.
- The scope has no exclusions. One line on what the SOP does not cover saves the reader from applying it to the wrong case.
- Names instead of roles. The document is out of date the day someone changes jobs.
- Checkpoints that say “check everything”. Name the two or three things that really go wrong.
- No owner and no review date. Without them nobody notices when the screens change.
How do you number SOPs and versions?
Keep it simple and consistent. A short prefix and three digits is enough for most organisations: SOP-001, SOP-002. Add a department prefix only if you have more than a few dozen documents. Use two-part versions: raise the second number for small corrections (1.1, 1.2) and the first for a changed process (2.0). Write one row in the revision history for every version, and keep older versions where readers do not find them by accident.
Is there one required SOP format?
No. ISO 9001:2015 asks for “documented information” and leaves the layout to the organisation; regulated industries may add their own rules. What matters most is that every SOP in your organisation uses the same format, so readers always find the scope, the steps and the owner in the same place.
How do you fill the procedure section with Izly?
If the task happens in a web application, record the procedure instead of typing it. Start the Chrome extension and do the task once; each click becomes a numbered step with a marked screenshot, already in the “one action per step” format. Edit the wording, add a warning block where a step is risky, then link the guide from section 5 or attach its PDF. Izly records browser tasks only, not desktop programs. The Free plan includes 10 guides. Start free.
Frequently asked questions
What is the standard format of an SOP?
A header, then purpose, scope, responsibilities, prerequisites, the numbered procedure, checkpoints, error cases, related documents and revision history. Small organisations often shorten responsibilities, error cases and related documents to one line each.
How many pages should an SOP be?
One or two pages for most everyday tasks. If the procedure passes about fifteen steps, split the SOP or move the detail into a work instruction.
Should an SOP be written in Word or as a web page?
Use what your team already opens every day. Word and PDF suit printed and audited documents; a web page or shared link suits software tasks that change often, because everyone sees the current version.
What is the difference between SOP format and SOP template?
The format is the order and content of the sections. A template is a file that already has that format, with fields for you to fill in.
Who should approve an SOP?
Someone who is responsible for the result of the process, usually the manager of the team that performs it. The person who wrote the SOP should not be the only one who approves it.
Related pages
Record it once and let the guide write itself
With Izly you do the task once in the browser. Clicks and screenshots become a step-by-step guide that you edit, share, turn into a narrated video or run again for every row of a table.