On this page
The short version
- 1An SOP is the written, step-by-step way your team does one recurring task.
- 2Copy the template: purpose, scope, roles, what you need, the steps, checks and revisions.
- 3Start each step with a verb, one action per step, with the names on the screen.
- 4Have someone new follow it, and fix every place they get stuck.
- 5Add a short video of the procedure being done in the real tool.
- 6Give it an owner and a review date, and update it when the process changes.
What is an SOP?
A standard operating procedure (SOP) is a written set of step-by-step instructions for a task your team does again and again: issuing a refund, closing the books at the end of the month, setting up a new hire's accounts. It says who does the task, when, what they need, and every step in order.
An SOP is worth writing when a task is:
- Repeated, daily, weekly or every time a certain thing happens.
- Done by different people, so the result shouldn't depend on who did it.
- Costly to get wrong, such as payments, customer data or anything an auditor will check.
- Hard to learn by watching once, so new people keep asking the same questions.
A good SOP lets someone who has never done the task do it correctly on their own, and lets everyone else check that it was done the agreed way.
SOP, process, work instruction and policy
These four documents are often confused. Each answers a different question:
| What it answers | Example | |
|---|---|---|
| Policy | ||
| Policy | What must happen, and why | Refunds above a set amount need a manager's approval |
| Process | ||
| Process | The big picture: the stages, and who hands off to whom | From a refund request to money back |
| SOP | ||
| SOP | How one recurring task is done, step by step | Refund a customer invoice in the billing app |
| Work instruction | ||
| Work instruction | How to do a single step in detail | Enter a partial refund on the Refund screen |
Most teams need SOPs most of all: they're the documents people open while they do the work. Link each one to the policy it follows, and to work instructions only where a step needs more detail.
The SOP template
Copy this, replace the brackets, and delete any part with nothing in it. Short tasks often need only the title, the purpose, what you need, the steps and the check at the end.
- Title
- [Verb + task], for example: Refund a customer invoice
- SOP ID and version
- [SOP-000], version [1.0], effective [date]
- Purpose
- This procedure makes sure [the task] is done [correctly, the same way, on time] so that [the result].
- Scope
- Covers [which cases, teams and systems]. Doesn't cover [what's left out], which follows [other SOP].
- Roles
- [Role] does the steps. [Role] approves [what]. [Role] owns this SOP.
- Before you start
- You need [access, tools, information or forms]. Do this task [when, or how soon after what].
- Steps
- 1. [Verb] [what] in [where]. You should see [result]. 2. [Next step]. 3. [Next step].
- Check the result
- [How to tell it worked, and who to tell when it's done]
- If something goes wrong
- [Common problem]: [what to do]. Anything else: [who to ask].
- Related documents
- [The policy it follows, linked SOPs, forms, a video of the task]
- Revision history
- [Version], [date], [what changed], approved by [who]. Next review: [date].
An SOP example, filled in
Here's the same template filled in for refunds in an invoicing app:
- Title
- Refund a customer invoice
- SOP ID and version
- SOP-FIN-012, version 2.1, effective November 14, 2026
- Purpose
- So that every refund is approved, recorded against the right invoice and reaches the customer within 5 working days.
- Scope
- Covers full and partial refunds of paid invoices in Taskly. Doesn't cover chargebacks, which follow SOP-FIN-014.
- Roles
- Support agents do the steps. A finance lead approves refunds above the limit in the refund policy. The finance team owns this SOP.
- Before you start
- You need a Taskly account with the Billing role, the invoice number and the customer's reason. Do refunds on the day they're approved.
- Steps
- 1. Open Billing. 2. Search for the invoice number. 3. Check that the invoice says Paid; if it doesn't, stop and follow SOP-FIN-010. 4. Click Refund. 5. Choose Full or Partial. 6. Enter the amount. 7. Pick the reason from the list. 8. Add the ticket number as a note. 9. Click Confirm refund. The invoice now says Refunded, with today's date.
- Check the result
- The refund shows under Payments on the customer's account. Reply on the ticket with the amount and when to expect the money.
- If something goes wrong
- The Refund button is grey: the invoice isn't paid yet, or you don't have the Billing role. Anything else: ask the finance team.
- Related documents
- Refund policy, SOP-FIN-014 Chargebacks, and a two-minute video of this procedure
- Revision history
- 2.1, November 14, 2026, partial refunds added, approved by the finance lead. Next review: May 2027.
Notice that each step names the screen and the button exactly as the app shows them, and that the steps where people go wrong (an unpaid invoice, a missing role) say what to do instead of leaving them stuck.
A checklist SOP for simple tasks
Routine tasks that people already know don't need the full template. A checklist makes sure nothing gets skipped:
- Task
- [What gets done]
- When
- [Every day at, every Friday, whenever someone joins]
- Who
- [Role]
- Checklist
- [ ] [First thing] [ ] [Second thing] [ ] [Third thing] [ ] [Last thing]
- Done when
- [What finished looks like, and where to record it]
Which SOP format to use
| Best for | Example | |
|---|---|---|
| Numbered steps | ||
| Numbered steps | Short tasks that always go the same way | Reset a customer's password |
| Steps with sub-steps | ||
| Steps with sub-steps | Longer tasks with several stages | Close the books at the end of the month |
| Flowchart | ||
| Flowchart | Tasks with decisions along the way | Handle a refund request |
| Checklist | ||
| Checklist | Routine tasks people already know | Open the office in the morning |
Pick the simplest one that fits. A flowchart helps when the right step depends on an answer (is the invoice paid?), but most software tasks are a list of steps with one or two exceptions, which fit in the template above.
How to write each step
- Start with a verb. “Click Refund” or “Enter the amount”, not “The amount should be entered”.
- One action per step. If a step has “and then” in it, it's two steps.
- Use the names on the screen. Write Billing and Confirm refund exactly as the app does, so people can find them.
- Say what they should see. “The invoice now says Refunded” tells people the step worked before they move on.
- Put warnings before the step, not after it: by the time they read it, it's too late.
- Say what to do when it goes wrong, for the problems people actually run into.
- Write for someone new. Spell out the shortcuts and abbreviations your team uses.
Write it while the task is being done
Test it with someone new
Before you publish an SOP, give it to someone who has never done the task and watch them follow it without helping. Every time they pause, ask a question or do something you didn't expect, the SOP needs a fix there. Then have the owner approve it and record the version and date.
Mistakes to avoid
- Steps written from memory, with the obvious parts left out
- Several actions crammed into one step
- Button and screen names that don't match what the app shows
- No owner, so nobody updates it when the process changes
- No version or date, so nobody knows if it's current
- One SOP that covers five tasks
- Warnings that come after the step they're about
Add a video of the procedure
A written SOP is the reference people search and print. A short video shows what each step looks like, which is often faster to follow for a procedure in software. Keep one video per SOP, a minute or two long, and link it from the Related documents line.
Use the SOP's steps as your script: say each step as you do it, with the same names. Record it with the screen recorder your computer already has (see how to screen record) or the free online screen recorder, and use sample data so no real customer details show. The training video guide covers the recording itself.
For a procedure in a web app, you can describe it instead of recording it. In SayScreen, you give it the page where the procedure starts and describe the steps. Its AI uses your live app in a real browser, reads each screen, decides where to click and writes the narration, and a natural AI voice speaks it. You get an edited MP4 and an .srt caption file, and captions can go on the video too. When a screen changes, run the same request again; when only the wording changes, rewrite that line of narration and update the video without recording again. A demo or staging account with sample data is the best place to record, and SOP videos has example prompts.
A video for every SOP
$1 for your first 7 days, then $49 a month for 60 minutes of video, up to 8 minutes each. Cancel anytime.
Keep your SOPs up to date
- Give each SOP an owner, the person who updates it and answers questions about it.
- Set a review date, often once a year, and review it sooner when the process or the software changes.
- Keep a revision history: version, date, what changed and who approved it.
- Keep them in one place people can search, such as your wiki or help center, with one name pattern so they're easy to find.
- Update the video too. A video that shows an old screen does more harm than no video.
Questions
A standard operating procedure (SOP) is a written set of step-by-step instructions for a task your team does regularly, such as issuing a refund or setting up a new hire's accounts. It says who does the task, when, what they need and each step in order, so the work is done the same way every time and new people can learn it without someone beside them.
A title, an ID and version, the purpose, the scope (what it covers and what it doesn't), who is responsible, what you need before you start, the numbered steps, how to check the result, what to do when something goes wrong, related documents, and a revision history with the owner and the next review date.
Watch the task being done, or do it yourself, and write down every step as it happens. Start each step with a verb, keep to one action per step, use the names on the screen, and say what the person should see when the step worked. Then have someone who doesn't know the task follow it, fix the places where they got stuck, and get it approved.
The common ones are a numbered list for short tasks that always go the same way, hierarchical steps with sub-steps for longer tasks, a flowchart for tasks with decisions, and a checklist for routine tasks people already know. Pick the simplest format that fits the task.
An SOP describes a whole procedure: who does it, when and in what order. A work instruction goes deeper into a single step, such as how to use one tool or one screen. A policy sits above both and says what must happen and why, without the steps.
As short as it can be while someone new can still follow it alone. Many fit on one or two pages. If yours is much longer, it probably covers more than one task: split it into separate SOPs and link them together.
Whenever the process or the software it uses changes, and on a fixed schedule as well, often once a year. Give every SOP an owner and a next review date, and keep a revision history so people can see what changed.
Yes, and the two work best together: the written SOP is the reference people search and print, and a short video shows each step being done in the real tool. For a procedure in software, a narrated screen recording of one task, usually a minute or two, works well.