What is an SOP (standard operating procedure)?

An SOP (standard operating procedure) is a written, step-by-step set of instructions for carrying out a routine task the same way every time. Organizations use SOPs to keep work consistent and safe, to meet quality or regulatory requirements, and to train employees on how a process is done.

Reviewed by Clark Quinn, Chief Learning Strategist Updated October 28, 2026

Example

A medical device manufacturer revises its SOP for cleaning a filling machine between production batches. The new version adds two steps and changes the order of a third. Under the company’s quality system, every operator who runs the machine must be trained on the new version before it takes effect.

The quality team publishes the revised SOP in its document control system. L&D creates a four-minute video that walks through each step on the actual machine and points out what changed. Operators watch it, complete a short quiz and then perform the cleaning once while a supervisor observes. The training record links each operator to version 4.0 of the SOP, which is what an inspector will ask to see.

How it works

An SOP has two lives: the document itself, and the training that gets people to follow it. Writing an SOP is also a form of knowledge transfer, because it turns what experienced staff know into instructions anyone can follow.

What an SOP contains

Most organizations write SOPs from a standard template. Common sections:

• Header: title, document number, version, effective date and owner.
• Purpose: why the procedure exists.
• Scope: which sites, teams, products or situations it covers.
• Responsibilities: who performs, checks and approves each part.
• Definitions: terms and abbreviations used in the document.
• Equipment and materials: what the person needs before starting.
• Procedure: numbered steps in order, with warnings where something can go wrong.
• References and revision history: related SOPs and forms, and a log of every change with its approval.

Common formats

• Simple steps: a numbered list for short, linear tasks.
• Hierarchical steps: main steps with sub-steps, for longer tasks that need more detail.
• Flowchart: for processes with decisions, where the next step depends on a result or a condition.

The SOP lifecycle

A process owner or subject matter expert drafts the SOP. It is reviewed, approved and published under document control, so that only the current version is in use. SOPs are reviewed on a schedule and whenever the process changes. Each revision gets a new version number, and everyone who performs the task is retrained on it.

How teams train people on SOPs

Publishing an SOP does not mean people follow it. Teams usually combine several methods:

• Read and acknowledge. The employee reads the SOP and signs to confirm. This is fast and creates a record, but it proves little about understanding.
• Demonstrate and practice. An experienced colleague shows the procedure, and the learner performs it under supervision until they can do it alone. This is the standard for hands-on tasks.
• Video walkthroughs. A short training video of each step gives every shift and site the same demonstration and can be rewatched at the point of work.
• Assessment. A knowledge check tests understanding of the rules and the order of steps. An observed performance tests the skill itself.

In regulated industries, the training record ties each employee to the specific SOP version they were trained on. When the SOP changes, the record shows who still needs retraining.

Common mistakes

• Writing for auditors instead of users. Dense SOPs full of regulatory language get ignored on the floor. Write steps the way the person doing the task would say them.
• Packing too much into one SOP. A procedure that covers five tasks is hard to follow and hard to update. Split it.
• Old versions in circulation. Printed copies taped to a machine often outlive the revision that replaced them.
• Treating a signature as training. A signed acknowledgment does not show that someone can perform the task correctly.

Why it matters for L&D teams

• Ready-made source material. SOPs are often the most accurate description of how work is done, which makes them a natural starting point for courses and videos.
• Version-linked records. Regulated industries expect training records that tie each person to the SOP version they learned.
• Constant retraining. Every revision triggers new training, so L&D needs a quick way to update content when a document changes.
• Consistency across sites. A shared SOP and shared training mean every shift and location does the task the same way.