Operations

How to Write an SOP: Template and Example

The parts of a standard operating procedure, how to write each step so it can be checked, and the 11-step returns procedure that cut credits from 9 days to 3.

Updated 24 September 2026 · 7 min read · By a former Gartner Managing Partner

The short answer

A standard operating procedure (SOP) is the written, approved way a task is done. Write it as numbered steps, each with one owner and a measurable standard (“within 3 working days”, not “promptly”). Add the checks that catch errors, a rule for every exception rather than leaving it to judgement, a version number, an approver and a review date. Keep a one-page work instruction of the critical steps at the workstation.

What an SOP is, and what it is not

An SOP records how a recurring task is done so that anyone trained on it does it the same way. It is written for the person doing the work, and it is measured: every step has a standard someone can check.

It is not a policy, which says what must be achieved and why, and it is not a process map, which shows how work flows between teams. A work instruction is the short version of the SOP’s critical steps, kept where the task is done. A RACI chart, which lists who is Responsible, Accountable, Consulted and Informed for each step, often sits alongside it.

The parts of an SOP

PartWhat it contains
HeaderID, title, version, owner, approver and next review date
ScopeWhere the procedure starts and ends: “from return request received to credit issued”
StepsNumbered actions, each with one owner and a standard
ChecksPoints where an error is caught before it moves on
ExceptionsA rule for each known exception, including safety cases
MeasuresHow the procedure’s performance is tracked, and by whom

How to write one in six steps

1. Watch the task being done

Write down what people actually do, not what the manager believes they do. Where several people do the task differently, record each version; the differences are where errors come from.

2. Set the start and end points

State the trigger that starts the procedure and the output that ends it. Everything between belongs in the SOP.

3. Write numbered steps, one owner each

Each step starts with a verb and names one role. “The team” is not an owner.

4. Give every step a measurable standard

A time, a quantity or a condition: “same working day”, “both fields complete before step 5”, “invoice price, not current list price”.

5. Write a rule for every exception

Exceptions left to judgement are handled differently by each person. Where an exception has a safety consequence, the rule has no exceptions of its own.

6. Add the measures and the review date

Name the one or two numbers that show whether the procedure works, who reviews them, and when the SOP itself is next reviewed.

Worked example: Brennock Medical Supply

The scenario

A returns process that four people ran four different ways

Brennock distributes medical consumables to 1,900 clinics, with $64 million of revenue and about 26,000 orders a month. After a courier switch, on-time delivery fell from 96% to 81%, 6.2% of orders were shipped with the wrong item or quantity, and 4 of its top 50 clinics, worth $2.3 million a year, moved to a competitor. The returns process had never been written down: four people handled returns in four different ways.

9 daysaverage wait for a credit
1 in 5credits priced wrongly
$180Kof invoices disputed in two quarters

With no procedure, returns waited for whoever had time. Clinics waited an average of 9 working days for a credit and withheld payment in the meantime. Each person priced returns differently, so one credit in five was wrong. And temperature-controlled items had been put back into stock after being returned.

This is the procedure that replaced it:

#StepOwnerStandard
1Log the return request and issue a return numberCustomer serviceSame working day
2Book the courier collectionCustomer serviceCollection within 2 working days
3Receive the parcel and match it to the return numberGoods-inScanned on arrival
4Record lot number and expiry dateGoods-inBoth fields complete before step 5
5Quarantine temperature-controlled itemsGoods-inNever restocked. No exceptions
6Inspect other items and grade: restock, write off, return to manufacturerQualityGrade recorded against the return number
7–9Restock, write off or return to manufacturer, and update stockWarehouseStock updated the same day
10Price the credit from the original invoice lineFinanceInvoice price, not current list price
11Issue the credit and notify the clinicFinanceWithin 3 working days of receipt

SOP-WH-014, Customer returns. Version 1.0, owner Head of Quality, approved by the COO, review in 12 months. Measures: working days from receipt to credit (target 3, baseline 9) and credits disputed, reviewed monthly.

Three details in it do most of the work. Step 10 removes the pricing disagreement by fixing one source for the price. Step 5 turns a safety exception into a rule with no exceptions. And the standard in step 11 turns “as soon as possible” into a number the Head of Quality can review every month.

What a one-line prompt gets wrong

Where it goes wrongWhat usually comes backWhat the SOP needs
ContentA textbook version of the taskHow your team does it, differences included
Owners“Staff”, “the team”One role per step
Standards“Promptly”, “carefully”A time, quantity or condition
Exceptions“Use judgement”A written rule for each
ControlNo version, owner or review dateHeader, measures and review date

Try it: a shortened Prompt 02

This is a shortened version of Prompt 02 from the Operations & Process pack, set up to run on its own. Paste it into ChatGPT, Claude or Gemini and fill in the brackets.

A shortened version of Prompt 02, Standard Operating Procedure (SOP) & Work Instructions, from the Operations & Process pack
You are a former head of operations excellence who has written procedures for regulated warehouses and service centres. A procedure only works if every step has one owner and a standard someone can check, and every exception has a rule, so you never write "promptly", "as needed" or "use judgement".

THE TASK:
- What the procedure covers, from start to finish: [trigger and end point]
- How it is done today, including differences between people: [paste notes or describe]
- The roles involved: [teams or job titles]

WHAT GOES WRONG:
- Errors, delays and complaints today: [with figures if you have them]
- Exceptions and special cases: [including anything with a safety or legal consequence]
- Who approves the SOP: [role]

Produce:

1. THE HEADER. ID, title, scope, version, owner, approver and review date.

2. THE STEPS. Numbered steps as a table: step, one owner, measurable standard. Each step starts with a verb.

3. THE CHECKS AND EXCEPTIONS. Where errors are caught, and a written rule for every exception; safety exceptions have no exceptions of their own.

4. THE MEASURES AND WORK INSTRUCTION. The one or two measures that show the SOP works, and a one-page work instruction of the critical steps.

Where the right standard is not in my input, propose one and mark it [TO CONFIRM].

The full Prompt 02 has eight parts rather than four, including a RACI chart, and it reads the Process Brief built by prompt 01, so the procedure is written against the process as mapped on the floor.

Checks before approval

Questions

What is the difference between an SOP and a work instruction?

An SOP covers the whole procedure, with owners, standards, exceptions and measures. A work instruction is the short version of the critical steps, used at the workstation where the task is done.

What is the difference between an SOP and a policy?

A policy states what must be achieved and why. An SOP states how a specific task is done, step by step, to meet it.

How long should an SOP be?

As long as the steps require and no longer. Most fit on one or two pages as a numbered table. If it runs much longer, it may be several procedures.

How often should an SOP be reviewed?

At a set date, commonly every 12 months, and whenever the process, the system or the regulation behind it changes.

Written by a former Gartner Managing Partner and investment banking SVP

The guides and the prompt templates on this site come from a career spent building these documents: board decks, forecasts, business cases and hiring decisions, as Managing Partner at Gartner, SVP in investment banking and Country Manager at international subsidiaries. The worked examples are published in full on each product page. Browse the Prompt Library.

Brennock Medical Supply is a fictional company and its figures are illustrative.

Output from any AI tool should be reviewed before use.