Skip to content
LeanSuite

Practical guide · Standard work, SOPs and training

What is an SOP? SOP meaning, format, examples and how to write one

Short answer

SOP stands for standard operating procedure: a written, approved document that says how to do a routine task the same way every time, safely and to the required standard. A typical SOP format has a header, purpose, scope, responsibilities, materials and safety notes, numbered steps and a revision history.

SOP stands for standard operating procedure. It is a written, approved document that describes how to carry out a routine task consistently, safely and to the required standard, so the result does not depend on who does the job. The usual format has a header with a document number and revision, then the purpose, scope, responsibilities, definitions, materials and safety notes, numbered steps in order, records and a revision history. Keep one SOP to one task, write each step as an instruction with a single action, test it with someone new to the job, and keep the current version in one controlled place. Short work instructions at the station then carry the detail operators need while they work. In university admissions SOP also means statement of purpose, which is a different document.

Last reviewed:

SOP meaning: what does SOP stand for?

SOP is short for standard operating procedure. The full form is the same in every industry. "Standard" means everyone follows the same method. "Operating" means it covers routine work, not one-off projects. "Procedure" means it is a sequence of steps, not a policy statement. You will also see the plural, SOPs, and now and then standing operating procedure or standard operating practice. They mean the same document.

In business the meaning does not change. An SOP in a factory, a warehouse, a laboratory, a hospital or an office is a controlled document that tells a trained person how to do a defined task, in order, to a defined standard. What changes is the content: a plant SOP covers a changeover or an inspection, an office SOP covers month-end close or onboarding. One unrelated use: in university admissions SOP means statement of purpose, the essay in an application. If that is what you are looking for, this page will not help.

An SOP does three jobs. It trains new people, because the method is written down instead of living in one person's head. It gives supervisors and auditors something to check the work against. And it is the base for improvement: you cannot improve a method nobody has defined. Our glossary entry for SOP and the longer post on what a standard operating procedure is cover the definition in more detail.

What is an SOP for?

  • Consistency. The task gives the same result on every shift, whoever does it, because the method is fixed and written down.
  • Training. A new person learns the approved method instead of the habits of whoever happened to train them. The SOP is the base document for TWI job instruction and for the one-point lesson that follows a change.
  • Safety and quality. The warnings, limits and checks sit in the step where they matter, not in someone's memory.
  • Audits and customers. The SOP is what an auditor checks the work against, and the evidence that the method is controlled.
  • Improvement. When the team finds a better way, the SOP is where the change is recorded, and the old way stops.

A plant without SOPs is not a plant without procedures. It has as many procedures as it has operators, and nobody knows which one made the last defect.

SOP format: the sections an SOP document includes

No law fixes one format for all SOPs. Regulated industries may have rules for the content, so check the requirements that apply to you. The layout below is a common pattern and matches the free SOP template. The header matters more than it looks: the document number is how the SOP is referenced from training records and audits, and the revision and effective date are how anyone can tell whether the copy in their hand is current.

Sections of a typical SOP
SectionWhat goes in it
HeaderTitle, document number, revision, effective date, owner, approver.
PurposeOne or two sentences: why the procedure exists and what result it protects.
ScopeWhat task, which area or equipment it covers, and what it does not cover.
ResponsibilitiesWho performs it, who checks it, who approves changes.
DefinitionsOnly the terms a new person would not know.
Materials, tools and safetyWhat is needed, required protective equipment, and any warnings before step 1.
ProcedureNumbered steps in order, one action each, with a check or limit where it matters.
RecordsWhat is recorded, where and for how long.
ReferencesRelated drawings, specifications, other procedures.
Revision historyRevision, date, what changed, who approved.

A common pattern, not a mandated layout.

Four SOP formats: step-by-step, hierarchical, checklist and flowchart

The sections above stay the same. What changes between SOPs is how the procedure part is laid out, and four layouts cover nearly every task.

Common SOP formats and when each fits

  • Simple step-by-step

    Best for
    Short routine tasks, roughly ten steps or fewer, with no decisions along the way.
    Example
    Changing a label roll; a daily start-up check.
  • Hierarchical

    Best for
    Longer tasks where each main step has its own sub-steps.
    Example
    A changeover with set-up, first-off approval and run-up stages.
  • Checklist

    Best for
    Tasks where completing every item matters more than the order.
    Example
    A pre-start inspection; a shift handover.
  • Flowchart

    Best for
    Tasks with decisions and branches.
    Example
    What to do with a suspect part: hold, rework or scrap, depending on the defect.
Choose the format from the task: decisions call for a flowchart, main steps with sub-steps for a hierarchical SOP, and a list where order does not matter for a checklist. Illustrative examples. Many SOPs mix a hierarchical procedure with a checklist at the end.

Most plant SOPs are step-by-step or hierarchical. A checklist on its own is a record, not a procedure, so pair it with the SOP that says how each item is done. The post on what a standard operating procedure is goes through each format with manufacturing use cases.

How to write an SOP: the steps

Writing an SOP in six steps

  1. 1best shift

    Watch the work first

  2. 2

    Pick one task and one reader

  3. 3verb first

    Write each step as an instruction

  4. 4

    Put warnings before the step

  5. 5

    Test it with someone new to the job

  6. 6

    Approve, release and control it

Every question the new person asks at step 5 is a gap in the document: fix the steps and test again before it is approved.
  1. 1

    Watch the work first

    Observe or video the task as it is done on the best shift. Writing from memory or from the old document copies the gaps. LeanSuite's AI SOP creation works from a video of the task for this reason.

  2. 2

    Pick one task and one reader

    One SOP per task, written for a competent but new person. If the document has two different start conditions, it is two SOPs.

  3. 3

    Write each step as an instruction

    Start with a verb: Load, Press, Check, Record. One action per step. Put the reason or the limit in the same step if it matters, such as "Torque to the value on the drawing".

  4. 4

    Put warnings before the step they apply to

    A safety note placed after the step is read too late. Mark steps where the task can hurt someone or damage the product.

  5. 5

    Test it with someone who has not done the job

    Ask them to follow it as written. Every question they ask is a gap. Fix the document, not the person.

  6. 6

    Approve, release and control it

    Only the approved current revision is in circulation. Old copies are removed from the floor. Connect the SOP to training: see the SOP to training matrix.

SOP example: a filled SOP document

This SOP is made up for this page and is illustrative. It is a simple step-by-step SOP, condensed to one line per section.

  • Header: SOP-0042, Changing the label roll on the carton labeller, revision 2, owner Packaging Supervisor.
  • Purpose: replace the label roll without printing blank or misaligned labels.
  • Scope: labeller on the packing line. Does not cover the printer ribbon.
  • Safety: stop the conveyor and lock out the labeller before opening the guard.
  • Step 1: Stop the conveyor and press the labeller stop button.
  • Step 2: Open the guard and remove the empty roll.
  • Step 3: Load the new roll and thread the web along the guide marks.
  • Step 4: Close the guard and restart the conveyor.
  • Step 5: Apply the first three cartons and check the label is square and readable. Record the check on the line sheet.
  • Revision history: rev 2, step 5 added after a mislabel.

Review arithmetic: a plant with 120 SOPs that reviews each every 12 months must review 120 divided by 12, which is 10 SOPs a month. Plan the review calendar from that number. A shorter cycle for high-risk tasks raises it, so count the SOPs on each cycle separately and add them. Checked the other way: 10 reviews a month for 12 months is 120, so every SOP is seen once a year.

SOP examples from a plant

The list below is illustrative: tasks that commonly get an SOP in a manufacturing plant, grouped by the department that usually owns them. Each line would be one SOP.

Typical SOPs by area
AreaTypical SOPs
ProductionMachine start-up and shutdown; changeover between products; first-off inspection; filling in the hourly production sheet.
QualityReceiving inspection; calibrating a gauge; raising a non-conformance report; handling a customer complaint.
MaintenanceLockout tagout for each machine; the weekly lubrication round; responding to a breakdown call.
SafetyForklift pre-use check; reporting a near miss; issuing a permit for work at height.
WarehouseReceiving a delivery; picking and packing an order; cycle counting.
HousekeepingEnd-of-shift 5S clean-down; cleaning and sanitation of food contact surfaces.

Illustrative. Which tasks need an SOP is a decision for your own quality system.

Food, pharmaceutical and medical device plants usually have more SOPs, because their regulators expect documented procedures for cleaning, sanitation, training and record keeping. This page does not state what any regulation requires; read the current text that applies to you.

SOP vs work instruction, standard work, policy and process map

How the documents differ
DocumentWhat it isWhere it sits
PolicyA statement of what the company requires and why. No steps.Management system manual; referenced by the SOPs under it.
Process map or flowchartThe sequence of activities across several people or departments.Used to see the whole flow; each box may have its own SOP.
SOPThe approved procedure for a task: purpose, scope, responsibilities, steps, records.Document system; read in training and for audits.
Work instructionA short, often visual, set of steps for one operation at one station.At the workstation, in use.
Standard workThe best known sequence, with takt time, work in process and the time for each element.Posted at the process; used by the team to improve.

Plain-language summaries. Companies use the words differently.

The SOP sits in the middle. A policy says what must happen, an SOP says how one task is done and who is responsible, and a work instruction shows how at the station. The post standard work vs SOPs vs work instructions goes through the three plant documents in detail. See also standard work.

Who writes and approves an SOP

The person who knows the task best writes the first draft. That is usually the team leader or the most experienced operator, working with the supervisor or the process engineer. Quality reviews it against the requirements and the records it creates. Safety reviews the hazards and the protective equipment. The approver is the process owner named in the header, and in regulated plants quality signs as well. Writing an SOP at a desk, away from the job, is the commonest reason it turns out wrong.

Ownership continues after release. The owner reviews the SOP on a fixed cycle, whenever the process, the equipment or the material changes, and after an incident or an audit finding. LeanSuite's AI SOP creation drafts the procedure from a video of the task, with purpose, scope, PPE, warnings and a photo for each step, then versions it and collects each person's signature. The SOP to training matrix links each revision to who has been trained on it.

Common mistakes

  • Writing a policy, not a procedure. If there are no numbered steps, it is not an SOP.
  • Writing for the auditor instead of the operator. A long SOP that nobody reads helps nobody. Put the long text in the SOP and the short version at the station.
  • No owner. A document without an owner is out of date within a year.
  • Copies on the floor. Printed old revisions get used. Control where the current one lives.
  • Never testing it. An SOP that nobody has followed as written has hidden gaps.
  • No link to training. An SOP that people have not been trained on and signed off is only a document. Use a training matrix.

This guide does not state what any regulator, customer or standard requires of your SOPs. If your SOPs fall under a regulation or a customer requirement, read the current text of it.

SOP Software

Write and control SOPs in LeanSuite

LeanSuite is AI SOP software: film the task once and get a draft with purpose, scope, PPE, warnings and a photo for each step, then version it and collect each person's signature.

FAQ

Questions about sOP meaning and format

  1. SOP stands for standard operating procedure. It is a written, approved document that describes how to carry out a routine task the same way each time. It is also sometimes read as standard operating practice.

  2. A common format has a header with title, number, revision and owner, then purpose, scope, responsibilities, definitions, materials and safety notes, numbered steps, records, references and a revision history. No single format is required for every industry, so check any rule that applies to yours.

  3. As short as the task allows. Most SOPs run from one to a few pages. If one grows long because it covers several tasks, split it into one SOP per task and link them.

  4. An SOP is the approved procedure for a task, with purpose, scope, responsibilities and steps. A work instruction is a shorter, often visual, set of steps for one operation at one station. Many plants keep the SOP in the document system and the work instruction at the workstation.

  5. There is no single answer. Many plants review on a fixed cycle such as every year, and sooner after an incident, a process change or an audit finding. Your quality system or regulator may set the interval, so check the rule that applies to you.

  6. A plant SOP for changing the label roll on a carton labeller: a header with the document number and revision, the purpose, the scope, a safety note to stop and lock out the machine, five numbered steps from stopping the conveyor to checking the first three cartons, and a revision history. Other common examples are machine start-up, changeover, receiving inspection, gauge calibration and lockout tagout.

  7. To make a routine task give the same result every time, whoever does it. An SOP trains new people on the approved method, puts safety warnings and quality checks in the step where they apply, gives auditors something to check the work against, and gives the team a defined method to improve.

  8. Four formats are common: simple step-by-step for short tasks with no decisions, hierarchical for longer tasks whose main steps have sub-steps, checklist for tasks where every item must be completed, and flowchart for tasks with decisions and branches. Most plant SOPs are step-by-step or hierarchical.

  9. The person who knows the task best writes the first draft, usually the team leader or the most experienced operator with the supervisor or process engineer. Quality and safety review it, and the process owner named in the header approves it. In regulated plants quality signs as well. The owner then keeps it current.

  10. A policy states what the company requires and why, with no steps. An SOP says how one task is done, in numbered steps, and who is responsible. A policy on lockout, for example, says energy must be isolated before maintenance; the SOP for each machine says which isolators, in what order, and how to verify.

  11. The same as anywhere else: standard operating procedure, a written, approved method for a routine task. In an office the tasks differ, such as invoicing, onboarding or month-end close, but the document does the same job. In university applications SOP means statement of purpose, which is unrelated.

  12. Watch the task done well, write the steps in order as instructions with one action each, put warnings before the step they apply to, add the purpose, scope and materials and a header with a number and revision, and test it on someone who has not done the job. Fix every point where they hesitate, then approve and release it, and remove the old version from the floor.

Or browse the topics, the full library and the lean glossary.

Rather see it on your own problem?

Bring the problem you are stuck on, and we will show you on a call how LeanSuite handles it.

Pass it on

We want LeanSuite to be the best place on the internet for lean help. If this was useful, send it to someone on your team or in your network who needs it.