SOP Template
An SOP template gives you a ready-made structure for writing a standard operating procedure, so every process in your business gets documented the same clear, repeatable way. Use this free SOP template to capture who does what, in what order, and to what standard, then keep it live in your knowledge base where your team will actually find it.
Open in Claude
Open in ChatGPT
I need to write a SOP. Act as an expert technical writer and draft one for me. Use this structure, keeping each section clear, concise, and genuinely useful to the reader: 1. Title and identifier 2. Purpose 3. Scope 4. Roles and responsibilities 5. Prerequisites 6. Procedure 7. Standards and quality checks 8. Exceptions and escalation 9. Related documents 10. Revision history Before you begin, ask me for the details you need: the product, team, or audience this is for, and anything specific I should include. Then write the full SOP in clean, well-formatted Markdown.
Write a SOP using the structure below. Keep each section clear, concise, and genuinely useful to the reader. Structure: 1. Title and identifier 2. Purpose 3. Scope 4. Roles and responsibilities 5. Prerequisites 6. Procedure 7. Standards and quality checks 8. Exceptions and escalation 9. Related documents 10. Revision history Use rich formatting so it reads well in a knowledge base: - Clear headings and subheadings for each section. - Callout boxes for asides: a Tip callout for advice, a Note callout for helpful context, and an Important callout for anything a reader must not miss. - Tables for structured or comparison content. - Numbered lists for sequential steps and bulleted lists for options. - Bold for key terms and any values people must not get wrong.
## The SOP template
### 1. Title and identifier
Give the procedure a plain, searchable name (for example, "Onboarding a new customer account"). Add a short ID and version number so people can tell at a glance which SOP, and which revision, they are reading.
### 2. Purpose
One or two sentences on why this procedure exists and what a correct result looks like. Answer the question a reader is silently asking: "What am I trying to achieve here?"
### 3. Scope
State where this SOP applies and where it does not. Note the team, product, region, or system it covers, and call out any related procedure that picks up where this one ends.
### 4. Roles and responsibilities
List every role involved and what each is accountable for. Use roles, not names, so the SOP stays accurate when people change jobs.
- **Owner:** keeps the procedure current and correct
- **Performer:** carries out the steps
- **Approver:** signs off where a decision or check is required
### 5. Prerequisites
What needs to be true before someone starts: access and permissions, tools or systems, inputs or information to have on hand, and any training or certification required.
### 6. Procedure
The heart of the SOP. Break the work into numbered steps, one action per step, in the order they happen. Write each step so a capable new hire could follow it without asking questions.
1. **Step name.** The single action to take, plus the tool or screen where it happens. Note the expected result so the reader knows it worked.
2. **Step name.** If a step branches ("if the account is enterprise, do X"), show the decision clearly.
3. **Step name.** Call out anything easy to get wrong, and add a screenshot or short clip where a picture saves a paragraph.
### 7. Standards and quality checks
How to tell the work was done right: the checks to run, the values or thresholds to hit, and any compliance or safety requirements that apply.
### 8. Exceptions and escalation
What to do when a step fails or reality does not match the procedure. Give a clear rollback or escalation path, including who to contact and how.
### 9. Related documents
Link to the policies, work instructions, and reference material this SOP depends on. Cross-linking keeps each document short and stops the same detail being maintained in five places.
### 10. Revision history
A simple table of what changed, when, and who approved it, plus the next review date. This is what keeps an SOP trustworthy over time.
| Version | Date | Author | Change | Next review |
| --- | --- | --- | --- | --- |
| 1.0 | TODO | TODO | Initial version | TODO | The SOP template
Copy this structure into a new article and replace the guidance in each section with the specifics of your process. Keep the headings; they are what make one SOP feel like the next.
1. Title and identifier
Give the procedure a plain, searchable name (for example, “Onboarding a new customer account”). Add a short ID and version number so people can tell at a glance which SOP, and which revision, they are reading.
2. Purpose
One or two sentences on why this procedure exists and what a correct result looks like. Answer the question a reader is silently asking: “What am I trying to achieve here?“
3. Scope
State where this SOP applies and where it does not. Note the team, product, region, or system it covers, and call out any related procedure that picks up where this one ends.
4. Roles and responsibilities
List every role involved and what each is accountable for. Use roles, not names, so the SOP stays accurate when people change jobs.
- Owner: keeps the procedure current and correct
- Performer: carries out the steps
- Approver: signs off where a decision or check is required
5. Prerequisites
What needs to be true before someone starts: access and permissions, tools or systems, inputs or information to have on hand, and any training or certification required.
6. Procedure
The heart of the SOP. Break the work into numbered steps, one action per step, in the order they happen. Write each step so a capable new hire could follow it without asking questions.
- Step name. The single action to take, plus the tool or screen where it happens. Note the expected result so the reader knows it worked.
- Step name. If a step branches (“if the account is enterprise, do X”), show the decision clearly.
- Step name. Call out anything easy to get wrong, and add a screenshot or short clip where a picture saves a paragraph.
7. Standards and quality checks
How to tell the work was done right: the checks to run, the values or thresholds to hit, and any compliance or safety requirements that apply.
8. Exceptions and escalation
What to do when a step fails or reality does not match the procedure. Give a clear rollback or escalation path, including who to contact and how.
9. Related documents
Link to the policies, work instructions, and reference material this SOP depends on. Cross-linking keeps each document short and stops the same detail being maintained in five places.
10. Revision history
A simple table of what changed, when, and who approved it, plus the next review date. This is what keeps an SOP trustworthy over time.
| Version | Date | Author | Change | Next review |
|---|---|---|---|---|
| 1.0 | TODO | TODO | Initial version | TODO |
How to fill in this SOP template
A template only helps if the finished SOP is genuinely usable. A few habits make the difference:
- Write for the newest person on the team. If a step assumes knowledge they do not have yet, spell it out or link to the guide that does.
- One action per step. If a step contains an “and,” it is probably two steps.
- Show, do not just tell. A screenshot or short clip next to a fiddly step removes most of the questions you would otherwise get.
- Test it live. Have someone follow the SOP exactly as written and note anything that trips them up. The gaps you cannot see are the ones a first-timer hits immediately.
- Give it an owner and a review date. An SOP with no owner quietly rots. Assigning one keeps it current.
For a deeper walkthrough of turning a messy process into clean documentation, see our guide on process documentation.
