Your most reliable shipper quits on a Friday. By Monday, nobody recalls the order she checked the pick list in, two parcels go to the wrong province, and a customer calls. Owners usually ask what is an SOP right after a week like that. This guide answers it, then shows you a finished one. Elsewhere on the site: ERP Meaning.
An SOP is a standard operating procedure: a written, approved set of steps that tells one person how to complete one repeatable task the same way every time. It names the owner, the trigger, the steps, and the finish line. Good ones fit on a single page and read like instructions, not policy.
| Item | Detail |
|---|---|
| Full term | Standard operating procedure |
| Typical length | One page, under 600 words |
| Who drafts it | The person who already does the task |
| Who approves it | The manager who owns the result |
| Review cycle | Twelve months, or six months for fast-changing work |
| Common formats | Numbered steps, hierarchy, flowchart |
| Where it lives | One shared, searchable folder |
Key takeaways
- One SOP covers one task. Not a whole department.
- Write numbered steps a new starter could follow without asking anyone.
- Name an owner and an approver, or the document drifts within a quarter.
- Review stable tasks every twelve months, and fast-changing work every six.
- Test the draft on someone who has never done the job.
What an SOP actually contains

Seven parts do the work. Miss any of them, and the page turns into a memo people skim once and forget.
- Header: SOP number, version, owner, effective date, and next review date.
- Purpose: one sentence on why the task matters.
- Scope: where the procedure applies, and where it does not.
- Roles: who performs each step and who signs off.
- Materials: tools, logins, and forms to gather before starting.
- Steps: numbered actions, one instruction per step.
- What can go wrong: the two or three failures people hit, plus the fix.
What Is an SOP Used For?
Three jobs, mostly. Training comes first: a new starter reads the page and finishes the task without shadowing a colleague for a week. Consistency comes second, because one task done four ways produces four quality levels and a customer who cannot predict which one arrives.
Handover is the third, and it matters most to the founders who read our small business ownership guides. Written procedures let you take a week off without your phone ringing. They also make a business easier to hand to a buyer, because the value stops living in one person’s head. Documented procedures are also the backbone of recovery planning, which our guide to business continuity strategies covers alongside RTO and RPO.
Certification bodies want the same thing. An ISO 9001 auditor asks to see documented information for your main processes, and your procedures are what you hand over.
SOP, policy, process map or work instruction?

The difference between them is scope, and mixing the four is the most common documentation mistake in a growing firm.
| Document | Answers | Typical length | Example |
|---|---|---|---|
| Policy | What we require, and why | One to two pages | Every complaint gets a reply within one business day |
| Process map | Which steps happen, in what order, across roles | One diagram | Complaint intake through to resolution across three teams |
| SOP | How one role completes one task | One page | Logging and resolving a complaint in the helpdesk |
| Work instruction | How to operate one tool or screen | Half a page | Creating a ticket in the helpdesk tool |
Policy sets the rule. An SOP carries it out. A work instruction zooms in further, down to the buttons.
How to write an SOP in seven steps
Start with a task that goes wrong often, or one that only a single person knows how to do. Then work through the sequence below.
- Watch the task once, start to finish, and note every action, including the ones nobody thinks to mention.
- Write the purpose and the scope in two sentences.
- Draft the steps in the order they happen, one action per step, with the verb first.
- Add the header: SOP number, version, owner, effective date, and next review date.
- Hand the draft to a new team member who has never done the job. Watch the dry run and time it.
- Fix whatever confused them during that test, then send the corrected draft to the approving manager.
- Store the approved version in one shared folder, and clear every older copy off desktops.
Step five is the one people skip. It is also the only step that proves the writing works.
A worked example: a customer complaint SOP
Here is a complete SOP for a small online shop handling a customer complaint. Nothing is trimmed for the sake of the article, and this is roughly the length yours should run to.
| Field | Entry |
|---|---|
| SOP number | CS-014 |
| Version | 3 |
| Owner | Customer care lead |
| Effective date | August 3, 2026 |
| Next review | August 3, 2027 |
| Scope | Complaints arriving by email or web form, Ontario and Quebec orders |
- Open a ticket within one business day and tag it Complaint.
- Read the full order history before replying, so the customer doesn’t repeat anything.
- Acknowledge in writing with a named contact and a date for the answer.
- Decide the outcome: replacement, apology, or a clear explanation of why neither applies.
- Send the outcome, then close the ticket with a one-line summary of what happened.
- Log the root cause in the monthly complaint review.
Complaint volume climbs fastest at shops that changed their checkout recently, a pattern our ecommerce and inventory guides look at in more depth. Handling those complaints the same way each time is what keeps a bad week from becoming a bad quarter.
Version control and the review cycle
Version control sounds like paperwork until two copies of the same document disagree in front of a customer. Number every procedure, raise the version on each change, and keep one master folder. Older copies belong in an archive that nobody works from.
Set the review cycle by how fast the work changes. Twelve months suits stable tasks. Six months suits anything that touches a tool or a supplier who updates often.
Put the next review date in the header, not in someone’s calendar.
The Canadian details that trip people up

Workplace rules in Canada sit largely with the provinces rather than Ottawa. A procedure written for an Ontario warehouse can name a requirement that reads differently in Alberta or in British Columbia. Put the province in the scope line, and say which provincial rules you followed.
Write measurements in metric units. Kilograms, litres, degrees Celsius.
Serving customers in Quebec adds a bilingual layer, because French versions of customer-facing documents are a standing requirement there. Translate the procedure once the steps settle, not while the draft still changes weekly. Two languages double the maintenance, which is another argument for keeping the page short.
Mistakes that make an SOP useless
- Five tasks crammed into one document.
- Prose paragraphs where numbered steps belong.
- No named owner, so nobody updates it after the first change.
- Storing it where only the author can find it.
- Padding it to look thorough.
Hold to a one-page limit and plain language, or the document gets read once and filed. Nobody opens a fourteen-page procedure at 4 pm on a Tuesday. If you want a second pair of eyes on a first draft, contact the Bizverra team.
Where to start this week
Pick the task that broke last month. Write the seven parts, run the draft past a colleague who has never done the job, and get it approved by Friday. One good procedure beats a documentation project that never ships.
Frequently asked questions
A short written recipe for a job your business repeats. It says who does it, when it starts, what happens at each step, and how you know it finished properly.
Standard operating procedure. The phrase came out of military and clinical practice, where doing a task identically every time carries obvious weight, and it moved into ordinary business use from there.
A header with the SOP number, version, owner and dates, then purpose, scope, roles, materials, numbered steps and a short troubleshooting note. Anything else is usually padding.
The manager who owns the outcome, not the person who wrote it. Splitting drafting from approving catches wishful thinking, and it gives the document authority once it lands in the shared folder.
Twelve months for stable work, six for anything volatile. Review it immediately after an incident too, since the fix you agreed in the meeting rarely survives unless somebody writes it down.
One page. If the task genuinely needs more, that is a signal to split it into two procedures with a clear handoff between them.
