Skip to content
SayScreen

Templates

SOP template: how to write a standard operating procedure

A standard operating procedure (SOP) is the written, step-by-step way your team does a recurring task, so it gets done the same way whoever does it. Here's a template to copy, the same template filled in, a checklist version for simple tasks, and how to write steps that anyone can follow.

Updated

$1 for 7 days, then $49/month
On this page

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 a policy, a process, an SOP and a work instruction each describe
What it answersExample
Policy
PolicyWhat must happen, and whyRefunds above a set amount need a manager's approval
Process
ProcessThe big picture: the stages, and who hands off to whomFrom a refund request to money back
SOP
SOPHow one recurring task is done, step by stepRefund a customer invoice in the billing app
Work instruction
Work instructionHow to do a single step in detailEnter 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.

Standard operating procedure template
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:

Example: refund a customer invoiceTaskly is a made-up 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:

Checklist SOP template
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

SOP formats and when each one fits
Best forExample
Numbered steps
Numbered stepsShort tasks that always go the same wayReset a customer's password
Steps with sub-steps
Steps with sub-stepsLonger tasks with several stagesClose the books at the end of the month
Flowchart
FlowchartTasks with decisions along the wayHandle a refund request
Checklist
ChecklistRoutine tasks people already knowOpen 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

Steps written from memory skip the obvious parts, and the obvious parts are where new people get stuck. Do the task yourself, or sit with someone who does it, and write each step as it happens.

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

Paste the page where the procedure starts and describe the steps. You get a narrated walkthrough recorded in your live app, ready to download and add to the 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

Skip the recording. Describe the video instead.

Point SayScreen at your app, say what to teach, and get a narrated, edited video back.

$1 for 7 days, then $49/month · Cancel anytime