An SOP, or standard operating procedure, is a written set of step-by-step instructions for doing one routine task the same correct way every time, no matter who does it. That is the short answer to what is an SOP. The rest of this guide explains what the letters stand for, what an SOP contains, how it differs from a policy, a process and a work instruction, the formats SOPs come in, when you need one, and how to write your first.
What does SOP stand for?
SOP stands for standard operating procedure. Each word does a job: standard means there is one agreed way, operating means it covers day-to-day work rather than one-off projects, and procedure means it is a sequence of steps. The plural is SOPs, with no apostrophe.
You will see the same phrase in offices, factories, laboratories, hospitals, kitchens and the military, and it means the same thing in each. Outside operations the letters can mean something else: in university admissions, an SOP is usually a statement of purpose. This guide is about the operations meaning.
What is the purpose of an SOP?
An SOP makes important work repeatable. It gives the same result whoever does the task, cuts errors, shortens training for new people, and keeps the agreed method on record when experienced staff move on. In regulated work, an SOP is also part of the evidence that a controlled method exists.
- Consistency. Two people doing the same task get the same result, because they follow the same steps.
- Training. A new hire can learn from the document instead of borrowing hours from the most experienced person on the team.
- Safety and compliance. Warnings, checks and approvals are written into the steps rather than left to memory.
- Continuity. The method does not leave the company when the one person who knew it does.
- Improvement. You can only improve a method you can see. A written SOP gives the team something specific to question and change.
What does an SOP contain?
Most SOPs contain the same core parts: a header that identifies the document, the purpose, the scope, roles and responsibilities, the numbered steps, exceptions and escalation, and an owner with a review date. Many also add definitions, required tools and access, safety notes, related documents, a revision history and approvals.
| Part | What it holds | When to include it |
|---|---|---|
| Header | Title, SOP number, version, owner, effective and review dates | Always |
| Purpose | Why the task exists and what it produces | Always |
| Scope | Where the task starts and stops, and what it does not cover | Always |
| Roles and responsibilities | Who performs, approves and is informed | Always |
| Procedure | Numbered steps with the expected result of each | Always |
| Exceptions and escalation | What to do when the normal path does not apply | Almost always |
| Definitions | Terms, acronyms and system names | When a new starter would not know them |
| Tools, systems and access | What must be ready before step 1 | When setup or permissions matter |
| Safety and compliance notes | Warnings and rules that apply | When the task carries risk or regulation |
| Revision history and approvals | What changed, when, and who signed off | When work is audited or must be approved |
You do not need to build that structure from scratch. Our free SOP template has every part above in Word and PDF, with a filled-in example.
How is an SOP different from a policy, a process or a work instruction?
A policy says what must be true and why. A process shows how work flows across people from start to finish. An SOP sets the agreed method for one routine task, with roles and steps. A work instruction gives the detailed actions for one step on one system. They nest from broad to narrow: policy, process, SOP, work instruction.
| Document | Answers | Level of detail | Example |
|---|---|---|---|
| Policy | What is required, and why? | Rules and principles, no steps | Customers may get a refund within the refund window. |
| Process | How does work move from start to finish? | Stages, handoffs and decisions across teams | Order to cash: order, invoice, payment, reconciliation. |
| SOP | What is the agreed way to do this task? | Purpose, roles, numbered steps, exceptions | Refund a duplicate card charge. |
| Work instruction | Exactly how do I do this step here? | Clicks, fields, screenshots and checks | Issue a refund in the payments dashboard. |
| Checklist | Did I do everything? | Items to confirm, no explanation | Pre-release checklist. |
Companies draw these lines differently, so settle the vocabulary inside your own team rather than arguing about labels. What matters is that each document answers one kind of question. Our guides on writing work instructions and workflow documentation cover the levels on either side of the SOP.
What are the types of SOP formats?
SOPs come in four classic formats: a simple step-by-step list, a hierarchical list with sub-steps, a flowchart for tasks full of decisions, and a checklist for routine checks. A fifth, the video SOP, shows the task being done and suits work that happens on a screen. Many SOPs combine two of them.
- Step-by-step list. Numbered actions in order. Best for short, linear tasks such as resetting a password.
- Hierarchical list. Main steps with lettered sub-steps. Best for longer tasks where each stage has its own detail, such as a month-end close.
- Flowchart. Boxes and decision diamonds. Best when the right action depends on conditions, such as triaging a support request.
- Checklist. Items to tick. Best for people who already know the task and need to confirm nothing was missed, such as a release or an office lock-up.
- Video SOP. A recording of the task with narration, often paired with written steps. Best for software tasks, where seeing the screen answers questions that words cannot.
To see these formats applied, browse ten standard operating procedure examples from IT, support, finance, HR, marketing and operations, each with a note on which format suits it.
When do you need an SOP?
Write an SOP when a task is done often, by more than one person, or when mistakes are costly: money moves, customer data is touched, safety is involved, or a regulator or customer expects one. Skip it for one-off work, and for tasks so simple nobody ever gets them wrong.
- New people keep asking the same question about the same task.
- Two people do the same task in two different ways, with different results.
- The same mistake has happened more than once.
- Only one person knows how to do it, and a holiday would stop the work.
- An auditor, a large customer or a regulator has asked how the task is controlled.
How do you write an SOP?
Pick one task, watch or record someone doing it correctly, and write the steps in order, each starting with a verb. Then add purpose, scope, roles and exceptions, test the draft on someone who has never done the task, and publish it with an owner and a review date.
Our free SOP template walks through each of those steps section by section, with a Word and PDF download and a filled-in example. For the wider method, read how to document a process and how to write step-by-step instructions.
Where a video SOP fits
For tasks done in software, many teams now pair the written SOP with a short video of the task, because a new person can watch it once and then use the written steps as a reference. The two drift apart when they are made separately, so the easiest way to keep them in step is to make both from the same recording.
That is what stepvideo.io is built for. You record the task once with the Chrome extension, which records a browser tab, a window or your whole screen; click-accurate editing comes from tab capture with the extension. From that recording it builds a list of steps, an edited how-to video with AI voiceover and captions, and a written step-by-step guide with a screenshot for each step. You correct the steps rather than a timeline, then re-render. It covers the procedure section of the SOP; the purpose, scope, roles, exceptions and approvals still belong in your document. Plans are on the pricing page.
The short version
An SOP is one routine task written down as the agreed way to do it: why, who, the steps in order, and what to do when it goes wrong. Write them for the tasks that are frequent, shared or risky, keep each one short, give it an owner, and change it the moment the work changes.
Frequently asked questions
What is an SOP in simple terms?
An SOP is a written recipe for a work task. It lists the steps in order, says who does each one and describes what the finished result looks like, so anyone trained can do the task the same way. Companies use SOPs for routine work such as paying invoices, onboarding staff or resetting passwords.
What are the five parts of an SOP?
Lists vary, but five parts appear in almost every SOP: the purpose, the scope, the roles and responsibilities, the step-by-step procedure, and document control, meaning the owner, version and review date. Good SOPs also cover exceptions and escalation, because most mistakes happen when the normal path does not apply.
What is the difference between an SOP and a process?
A process describes how work flows from start to finish across people and teams, such as order to cash. An SOP zooms in on one task inside that process and sets the agreed way to do it, with roles and numbered steps. One process usually needs several SOPs, one for each task that needs a standard method.
Who writes SOPs?
Usually the person who does the task most reliably drafts it, or is recorded doing it, and the process owner edits and approves it. In regulated companies a quality team controls the format, numbering and approval route. Whoever writes it, the draft should be tested on someone new to the task before it is published.
How often should SOPs be reviewed?
Review an SOP whenever the system, policy or team behind it changes, and on a fixed schedule as a backstop; many teams review yearly, while regulated work often sets its own interval. Put the next review date in the header so it is visible, and record each change in the revision history.
Are SOPs only for regulated industries?
No. Many regulated industries require written procedures, but any team benefits from SOPs for frequent, error-prone or single-person tasks. Small companies use them to train new hires faster and to stop knowledge disappearing when someone leaves. Keep them short, and only write the ones people will actually use.