Prompt Notebook

SOP · Process documentation · Operations

How to write an SOP: the parts, the steps and a filled-in example

Last updated By T. Krause

A standard operating procedure tells anyone trained how to do a repeating task the same way each time. Here are the parts an SOP needs, how to word the steps so people can follow them, and a complete example for processing a customer refund.

Most SOPs get written the week after something went wrong. A refund went out twice, or the one person who knew the month-end export was on holiday. Someone sits down, writes three pages from memory and saves them in a folder. Nobody opens the folder again until the next time it goes wrong.

A useful SOP is shorter and plainer than that. To write one, pick a task that repeats and that someone other than you will have to do. Watch it being done and write every action down as a numbered step that starts with a verb. Add who owns the task, what you need before you start, how to tell it is finished and what to do when it fails. Then hand it to someone who has never done the task and fix every step they get stuck on.

The rest of this guide goes through each part and each step, then shows a complete SOP for an example shop. If you'd rather start from a page that already has the headings, our SOP template has them in place.

What an SOP is, and when to write one

A standard operating procedure, or SOP, is a written description of a task your team repeats. It is detailed enough that anyone trained can do the task the same way. One SOP covers one task, says who is responsible for it and lists the steps in order.

A task earns an SOP when it comes round regularly, more than one person may have to do it, and a mistake costs money or a customer. Processing refunds, cashing up the till, setting up a new client and paying suppliers all fit. A one-off project doesn't need an SOP. Neither does a task only you will ever do, at least until you want to take a holiday.

When a checklist is enough

A checklist is a list of things to tick off, with no explanation. It works when the person doing the task already knows how to do every item and only needs a reminder not to skip one. Opening the shop with a trained team is a checklist job.

Write a full SOP when the reader might not know how. New staff are one case. A backup who does the task twice a year is another. So is any step with a right and a wrong way to do it, such as which account a refund comes out of. Most SOPs end with a short checklist anyway, so the person can confirm the task is done.

The parts of an SOP

Start with a title that names the task the way people ask about it. "Processing a customer refund" gets found when someone searches. "Finance procedure 4" doesn't. Under the title, an SOP has eight parts:

  1. Owner and review date. One line at the very top with the person responsible for the SOP, their backup, the date it was last checked and how often it gets checked. Readers see straight away whether they can trust it and who to ask.
  2. Purpose. One or two sentences on what the task achieves. The reader should know what a good result looks like before step one.
  3. Scope. What the SOP covers and what it leaves out. "Refunds for online orders. Wholesale credit notes have their own SOP."
  4. Roles. Who does the task, who covers and who approves anything unusual. Use names or job titles, whichever changes less often in your team.
  5. Prerequisites. What the person needs before starting, such as logins, access rights, documents and tools. Include what starts the task, whether that is a time of day or a customer email.
  6. Numbered steps. The actions in order, one per step.
  7. Checks. How the person knows the task is finished and done right, written as a short list they can tick.
  8. What to do when it goes wrong. The problems that really happen, each with a fix or the name of the person to contact.

Short SOPs can fold some of these into a single line. Scope and roles often fit in one sentence each. Don't drop a part without deciding to, though, because the missing one is usually the one somebody needs.

How to write an SOP in seven steps

1. Pick one task with a clear start and end

An SOP called "Finance" will never be finished. Pick a task with a trigger and an end point, for example from "a customer emails asking for a refund" to "the money is back and the customer has a confirmation". If the title needs the word "and", you are probably looking at two SOPs.

2. Watch the task being done

Sit next to the person who does the task most often, or do it yourself, and write down every action as it happens. Writing from memory skips the steps that have become automatic, and those are the steps a new person misses. Note the screen names, the button labels and every moment the person stops to think. Those pauses are where the decisions are.

3. Write one action per step

Each numbered step is one thing the reader does. "Check the order and issue the refund" is two steps, and the reader will forget the check. If a step needs more than two sentences, it is hiding a second step or a decision.

4. Start every step with a verb

"Open the order." "Copy the order number." "Select Refund." A verb at the front tells the reader what to do before they read anything else. Add the reason after the action, and only where someone would otherwise skip the step.

Use the exact words on the screen. If the button says Issue refund, write Issue refund, not "process the payment back".

5. Write decisions as if-then lines

Where the task branches, say what to check and what each answer means. "If the order is older than 30 days, stop and forward the email to Sam." Keep a short branch inside its step. If one branch turns into a procedure of its own, give it its own SOP and link to it.

6. Add the checks and the failure cases

Write the "done when" list next. Each item should be something the person can see, such as an email in the sent folder or a status in the order screen. Then add the problems that have actually happened, each with its fix. Ask the person who does the task what went wrong last time. Don't make up problems to look thorough.

7. Test it on someone who has never done the task

Give the SOP to a new hire or a colleague from another team and ask them to do the real task with it while you watch and stay quiet. Every time they hesitate, ask a question or do something you didn't expect, a step is unclear. Fix it straight after. One test run finds more than any amount of rereading, because you can't unknow the task and they don't know it yet.

How to keep SOPs current

An SOP starts to drift the day the software, a supplier or the team changes. An outdated SOP does more harm than a missing one, because people follow it. A few habits keep them true:

  • Give every SOP one owner. One name, not a team. The owner doesn't have to do the task. They decide when the page changes and they do the reviews.
  • Put the review date at the top. Write it next to the owner, with how often the SOP gets reviewed. Every six months suits most tasks. Anything that touches money or customer data may need a shorter cycle.
  • Change it when the task changes. Don't wait for the next review. Whoever notices the difference fixes the step and tells the owner. When an incident shows a step was wrong, fixing the SOP belongs on the action list of the postmortem.
  • Keep SOPs where people already look. A shared drive of documents goes stale faster than pages in the team wiki that people link to in chat. Our guide to building a team wiki people actually use covers owners and review routines for the whole wiki.
  • Delete SOPs for tasks you no longer do. Someone will find and follow them otherwise.

A filled-in example: processing a customer refund

The shop, the people and the rules below are invented. It is a small online shop that sells loose-leaf tea, run by three people. Lena handles orders and customer email. Sam looks after the money and covers for Lena when she is away.

SOP: Processing a customer refund

Owner: Sam Okafor. Backup: Lena Vogt. Last reviewed: 22 October 2026. Review: every six months.

Purpose

Every customer with an approved refund gets their money back and a confirmation email within two working days of asking.

Scope

Refunds for orders placed in the online shop, for faulty items, wrong items and returns within 30 days. Wholesale customers pay by invoice and follow the credit note SOP instead.

Roles

  • Does the refund: Lena
  • Covers when Lena is away: Sam
  • Approves refunds over €100 and anything outside this SOP: Sam

You need

  • Shop admin access with the Orders role
  • A login to the payment provider's dashboard with refund rights
  • The order number and the customer's reason
  • Timing: check the refunds inbox at 10:00 and 15:00 on working days

Steps

  1. Open the refund request in the shared inbox and copy the order number.
  2. Search for the order number in the shop admin and open the order.
  3. Check the order date. If the order is older than 30 days, forward the email to Sam and stop here.
  4. Check the reason. For a faulty or wrong item, ask the customer for a photo if the email has none, and wait for it before you go on.
  5. Look for an earlier refund in the order history. If there is one, reply with the date of that refund and stop here.
  6. Work out the amount. Faulty and wrong items get the item price plus shipping. Returns get the item price only, once the parcel is back in the shop.
  7. If the amount is over €100, send Sam the order number and the amount and wait for a yes.
  8. Find the payment by order number in the payment dashboard, select Refund and enter the amount from step 6.
  9. Set the order status to Refunded in the shop admin and paste the refund reference into the order notes.
  10. Send the customer the "Refund confirmed" email template with the amount and the date.
  11. Move the request to the Done folder.

Done when

  • The payment dashboard shows the refund as completed
  • The order says Refunded and the notes hold the refund reference
  • The customer has the confirmation email
  • The request is in the Done folder

If something goes wrong

  • The payment dashboard shows an error. Don't try again with a different amount. Take a screenshot and forward the request to Sam.
  • The customer wants the money on a different card. Refunds go back to the card they paid with. Say so in your reply and pass any exception to Sam.
  • You refunded the wrong amount. Don't refund the difference yourself. Write what happened in the order notes and tell Sam the same day.
  • A customer asks for a refund by phone. Ask them to email the request with the order number, so the request and the decision sit in one place.

Look at what the example leaves out. It doesn't explain what a payment dashboard is or why customers care about refunds. Lena knows both, and a new hire learns them in the first week. Every step is something Lena does, in the order she does it. Steps 3, 5 and 7 are the checks, and they stop a late refund, a refund paid twice and a large refund nobody approved. The amount rules sit in step 6, where she needs them, instead of in a policy document she would have to go and find.

To copy it, keep the headings, swap in your own task and replace the steps with the ones you wrote down while watching.

Writing SOPs in Prompt Notebook

Prompt Notebook is ours, so read this part with that in mind. The standard operating procedure template opens as a page with the headings from this guide. A line at the top holds the owner, the backup, the last review date and the review cycle. Below it are the purpose, when the task runs, what you need, numbered steps, a "Done when" checklist and an "If something goes wrong" section with each problem in a toggle. The sample is a month-end invoicing SOP, so you see a finished one before you replace it with your own.

You can also have the AI write the first version. It drafts a page from one sentence that describes the task, and the Draft a variant with AI button on the template page shows the result for a sample prompt. You insert, replace or discard what the AI suggests, then edit the page like any other. Treat the draft as a first version. It still needs step 2 and step 7 from this guide, because the AI hasn't watched your team do the task.

Page history takes a snapshot every 10 minutes while a page is being edited, so the owner can see what changed since the last review and restore an earlier version. If your SOPs live as sub-pages of the team wiki template, a share link on the wiki gives everyone access to every SOP under it. Ask your workspace can then answer "who approves refunds over €100?" with a numbered link to the page the answer came from.

Start from the SOP template and write the first one for the task your team asks about most.

Frequently asked questions

How long should an SOP be?

As long as the task needs. Most tasks a small team repeats fit on one screen. If an SOP runs past twenty steps, check whether it is really two tasks, or whether some steps belong in a separate SOP that this one links to.

What is the difference between an SOP and a policy?

A policy states the rule and why it exists. An SOP says how to carry it out. The tea shop's refund policy might say customers can return items within 30 days. The SOP above says what Lena does when one of them emails.

Who should write the SOP?

The person who does the task most often, with someone else checking it. The doer knows the steps, and the checker spots the ones the doer no longer notices. Name the owner once it is written, even if that is a different person from the writer.

Try it on your own notes

Prompt Notebook is free, with unlimited pages. Type one sentence and the AI drafts the first version.

Cookies and storage

Prompt Notebook needs one cookie to keep you signed in. Accepting turns on Google Analytics and Google's reCAPTCHA spam check on the contact form, and declining keeps the form working. Nothing optional runs until you choose.

Read the privacy notice