What does SOP stand for?
SOP stands for standard operating procedure. The SOP meaning is the same in every sector: a written, approved way of doing a task so that it is done the same way each time, whoever does it. In manufacturing an SOP might cover a line start-up, a changeover or a cleaning cycle; in a laboratory, a test method; in customer service, how a complaint is logged and answered.
What is an SOP in business? Outside the factory, standard operating procedures capture the routine tasks in any business process: onboarding a new starter, month-end close, handling a refund. The purpose is the same everywhere: reducing errors and variation, making training faster, and giving the organisation a company standard it can audit and improve. A business without SOPs relies on the memory of its most experienced people, and loses that knowledge when they leave.
What goes in an SOP?
An effective SOP is short, but it answers every question a trained person would ask before starting. Most include:
- Header and document control: title, ID, version, author, approver, effective date and next review date.
- Purpose: what the procedure achieves, in one or two sentences.
- Scope: which process, area, equipment and shifts it applies to, and what it does not cover.
- Roles and responsibilities: who performs each part, who checks it and who owns the document.
- Definitions: abbreviations and terms a new starter may not know.
- Materials, equipment and PPE: what is needed before the first step.
- The procedure: a set of step-by-step instructions in the order the task is done, each with its key points, settings and reasons.
- Safety and quality checks: where in the sequence each check happens, and what to do if it fails.
- Records: what is written down or captured, where and by whom.
- Revision history and approval: what changed in each version, why, and who approved it.
What are the 3 types of SOP format?
- Step-by-step (simple list). Numbered steps in order. Best for short, linear routine tasks with few decisions, such as a start-up check.
- Hierarchical. Main steps broken into sub-steps, with key points and reasons under each. Best for longer tasks, where experienced operators read the main steps and new starters need the detail.
- Flowchart. Boxes and decision points. Best when the task branches on conditions, such as fault finding or a quality hold decision.
Many operating procedures combine them: a flowchart for the overall process, with hierarchical steps behind each box.
How do you write an SOP?
Seven steps, whichever format you use:
- Pick the process. Start where variation hurts most: safety-critical tasks, frequent defects, high staff turnover or new equipment.
- Involve the people who do it. Operators know the details, the workarounds and the steps nobody wrote down. An SOP written without them describes how the task should work, not how it does.
- Observe at the gemba. Watch the task done several times at the place of work. Note the sequence, the key points that make or break quality and safety, and where people hesitate.
- Draft it. Use a standard SOP template so every procedure has the same structure. Write each step as an action, keep sentences short and add photos where words struggle.
- Test it. Ask someone who has not done the task to follow the draft while the author watches. Every question they ask is a gap in the document.
- Approve and train. The process owner approves the SOP, it is published where the work happens, and people are trained and assessed against this version.
- Review on a schedule and on change. Set a review date, and also review whenever the process, equipment or regulation changes, or an improvement is verified.
SOP example: a line start-up check
A food packaging line has a start-up SOP used by every shift. Purpose: confirm the line is safe, clean and set correctly before the first pack. Scope: one line, all products, first start of each shift. The shift operator performs it and the team leader verifies it. The steps: confirm the sanitation sign-off for the previous clean; check guards and emergency stops; set sealer temperature and film tension to the product settings sheet; run five test packs and check seal integrity, date code and label; record the results; then release the line. If any check fails, the line stays stopped and the team leader is called. The whole SOP fits on one page, with photos of the guard checks and the date code position. Start your own from the SOP template.
SOP vs work instruction vs standard work
The three terms overlap and organisations use them differently. A common way to separate them:
| SOP | Work instruction | Standard work | |
|---|---|---|---|
| Answers | What must be done, by whom and why | How to do one task, step by step | The current best way, with time and sequence |
| Detail | A procedure, often across roles | Step level, with photos and key points | Step level, with takt time, sequence and work in process |
| Owned by | Process owner or quality | Area or engineering | The team that does the work |
| Changes when | Policy, regulation or the process changes | The task or equipment changes | An improvement is verified |
| Usually kept | In document control | At the workstation | At the workstation and on the board |
An SOP for changeovers might reference a work instruction for each machine, while the team's standard work sets the sequence and time. All three should agree. Many sites now present work instructions on a screen at the point of use; see digital work instructions.
What are the common mistakes with SOPs?
- Written once and never revised. The process moves on and the SOP describes a line that no longer exists.
- Stored on a shared drive no one opens. If an operator cannot find the current version at the workstation in under a minute, they will work from memory.
- Too long. A twenty-page SOP for a ten-minute task is a compliance document, not a working one. Split it, or move detail into work instructions.
- Not linked to training. A signature on a read-and-understood form is not evidence that someone can do the task to the standard.
- Written by someone who doesn't do the job. The steps are tidy and the real workarounds are missing.
How do you keep SOPs alive?
An SOP is only as good as the last time someone checked it against the work. Four habits keep standard operating procedures current:
- Review dates and change triggers. A scheduled review as a backstop, plus a review whenever something changes.
- Audits at the work. Layered process audits and gemba walks check the SOP is followed and still right. A failed check is either a training gap or a sign the procedure needs to change.
- Training sign-off against the version. Link SOPs to the skills matrix, so a changed procedure shows who needs re-training.
- Access at the point of work. The current version on a phone, tablet or screen, searchable by task, instead of a binder in the office.
Run this way, SOPs become part of continuous improvement: each verified improvement updates the standard, and the updated standard becomes the baseline for the next one.