Template text
# [SOP title: name of the task]
| Field | Value |
|---|---|
| SOP no. | [SOP-001] |
| Version | [1.0] |
| Date | [YYYY-MM-DD] |
| Owner | [name, role] |
| Approver | [name, role] |
| Next review | [YYYY-MM-DD] |
## 1. Purpose
[Why does this SOP exist? Which outcome or risk does it protect? One or two sentences.]
## 2. Scope
- Applies when: [example: individual customer records only]
- Does not apply when: [example: corporate customers follow SOP-002]
## 3. Responsibilities
| Role | Responsibility |
|---|---|
| [Performer] | [Does the task as described in this SOP] |
| [Approver] | [Checks and approves the result] |
| [Owner] | [Keeps the SOP current] |
## 4. Prerequisites
- [Required access or permission]
- [Required document, form or information]
- [Required tool]
## 5. Procedure
1. [Start with a verb. Example: Click New record.]
2. [One action per step.]
3. [Link to a screenshot or work instruction if needed.]
4. [...]
## 6. Checkpoints
- [ ] [Where mistakes happen most: example, is the tax ID 10 digits?]
- [ ] [Was the record saved and the confirmation message shown?]
## 7. Error cases
| Situation | What to do | Who to tell |
|---|---|---|
| [Error message or situation] | [Resolution step] | [Person or channel] |
## 8. Related documents
- [Work instruction, form or another SOP]
## 9. Revision history
| Version | Date | Changed by | Change |
|---|---|---|---|
| [1.0] | [YYYY-MM-DD] | [name] | [First release] |
sop-template.md · A plain Markdown file that opens in any editor.How do you fill in the SOP template?
- Name one task in the title. “Close a refund request” is a good title; “customer service” is not.
- Keep purpose and scope short. One or two sentences each. Say in the scope what does not apply.
- Write responsibilities as roles. Names change, roles stay.
- Start steps with a verb. “Click Save”, “enter the amount”. One action per step.
- Draw checkpoints from real mistakes. Which error happened most recently?
- Test with someone who does not know the task. Fix where they get stuck, then publish and set a review date.
For the full method see what is an SOP and how to write one. When a single step is complicated, split it out with the work instruction template.
Which sections can I shorten?
For short, low-risk tasks, reduce Responsibilities, Error cases and Related documents to one line each. For error-prone tasks or tasks audited by a quality system, fill in every section. Never skip Revision history or the Owner field: keeping the document current depends on them.
How do you fill the Procedure section with Izly?
If the task happens in a web application, record section 5 instead of typing it. Start the Chrome extension and do the task once; each click becomes a step with a marked screenshot. Edit the text in the editor, add tip and warning blocks, redact sensitive areas, then put the guide link in the step list of the template or attach its PDF. See the guide on step-by-step guides with screenshots or start free.
Frequently asked questions
Can I use this template commercially?
Yes, you can copy and adapt it inside your organization. For legal or certification requirements, confirm with your own advisor or certification body.
Which tools can I use the template in?
It is plain Markdown, so you can paste it into any text editor, wiki or document tool. The tables come as Markdown tables; check the formatting when you move them into Word.
Is this template enough for ISO 9001?
It gives a common SOP structure. ISO 9001:2015 asks for “documented information”, and the extent varies by organization; numbering, approval and version rules still need to be defined in your quality system.
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 and share by link.