What Is an SOP? Standard Operating Procedures Explained

An SOP (standard operating procedure) is a documented set of step-by-step instructions that describes how to perform a routine task correctly, safely, and the same way every time. The purpose of an SOP is to remove guesswork: whoever does the job — first week or fifteenth year — follows the same procedure and gets the same result.

That's the two-sentence answer. The rest of this guide covers what SOP stands for, why organizations write them, the four standard formats, what goes inside an SOP document, real examples across six industries, and the uncomfortable truth about SOP compliance: most SOPs are written once and never read again. If you're here because you need to actually produce SOPs, the SOP template library has ready-made starting points for the most common procedures.

What does SOP mean?

SOP stands for standard operating procedure. Break the phrase apart and each word carries weight:

• Standard — there is one agreed way to do this task, not five tribal variations depending on who trained you.
• Operating — it covers work that actually happens in day-to-day operations: opening a restaurant, calibrating a scale, resetting a password, sanitizing a bioreactor.
• Procedure — it's a sequence. Steps in order, with a defined start and a defined end.

You'll hear the plural as "SOPs" ("our food-safety SOPs") and the informal usage "that's standard operating procedure," meaning the normal, expected way things are done here. The military popularized the term — in some contexts it originally meant "standing operating procedure," i.e., a procedure that stands until amended — and it migrated into manufacturing, pharma, aviation, and eventually every industry that needs repeatable work.

A useful distinction up front: an SOP is not a policy and not a work instruction. A policy says what the organization requires and why ("all food-contact surfaces must be sanitized between uses"). A work instruction is the most granular level — exact keystrokes, exact dial settings for one specific machine. The SOP sits between them: it turns policy into a repeatable procedure, and may reference several work instructions. Small organizations happily collapse all three into one document; regulated ones keep them separate.

Standard operating procedures: the working definition

If you need a citable standard operating procedures definition, use this one:

Every clause in that sentence is doing work:

• Formally documented — it exists in writing (or video), not in someone's head. If your best line cook quits tomorrow, the procedure survives.
• Approved — someone with authority reviewed it and signed off. In regulated industries this is literal: a signature and date on the document.
• Routine or repetitive — SOPs cover recurring work. You don't write an SOP for a one-time project; you write a plan.
• Qualified person — an SOP assumes baseline competence. It tells a trained phlebotomist the order of draw; it doesn't teach them to draw blood.
• Without direct supervision — this is the real test. If the task can only be done correctly when the supervisor is watching, you don't have an SOP, you have a supervisor.

What is the purpose of an SOP?

Organizations write SOPs for five reasons, and it's worth knowing which one is driving yours, because it changes how you write it.

1. Consistency

The core purpose of an SOP is that the output doesn't depend on who performed the task. A burger assembled at 11 p.m. Saturday looks like the one assembled at noon Tuesday. A batch record reviewed by analyst A gets the same scrutiny as one reviewed by analyst B. Consistency is what makes quality measurable — you can't improve a process that runs differently every time.

2. Safety

Many SOPs exist because someone got hurt, or nearly did. Lockout/tagout procedures, chemical handling, ladder safety, fryer cleaning — these SOPs encode the safe sequence so that shortcuts don't creep in. In safety-critical work the SOP often is the control: OSHA citations regularly hinge on whether a documented procedure existed and whether employees were trained on it.

3. Compliance

In regulated industries, SOPs aren't optional. FDA regulations for pharmaceutical manufacturing (21 CFR Part 211) require written procedures for production, cleaning, equipment maintenance, and laboratory controls — and require that deviations be recorded and justified. Food service operates under HACCP plans and local health codes that expect documented procedures. ISO 9001 certification requires documented process control. When an auditor arrives, "we all know how to do it" is a finding, not an answer.

4. Training and onboarding

An SOP is the raw material of onboarding. Instead of a new hire shadowing whoever happens to be on shift — and absorbing that person's habits, good and bad — they learn the standard directly. Companies with documented procedures consistently onboard faster because the knowledge transfer doesn't bottleneck on one busy veteran.

5. Institutional memory

People leave. The SOP is how the organization remembers what its best people knew. This is the least glamorous purpose and arguably the most valuable: a well-maintained SOP library is a company's operational knowledge in transferable form.

The four types of SOP formats

There's no single correct SOP format. The right one depends on how complex the task is and how many decisions it contains. Four formats cover nearly every case.

Step-by-step (simple list)

A numbered list of sequential steps. Best for short, linear tasks with fewer than ten steps and no branching decisions: replacing a fryer filter, clocking in a delivery, running a daily backup check.

Hierarchical

A numbered list where major steps contain sub-steps (1, 1.1, 1.2, 2, 2.1…). Best for longer procedures where operators need detail the first ten times but only the top-level steps afterward. Most pharma and manufacturing SOPs use this format because it lets one document serve both new and experienced staff.

Flowchart

A decision-tree diagram. Best when the procedure branches: if the temperature reads above 41°F, then… otherwise… IT incident response, deviation triage, and returns handling are natural flowchart SOPs. If you find yourself writing "if" more than twice in a list-format SOP, switch to a flowchart.

Checklist

A list of items to verify, in any order or a loose order, with a box to tick. Best for verification tasks rather than production tasks: opening/closing checklists, pre-flight inspections, room-turnover verification. The checklist's power is that it's used during the task, not read before it — which, as we'll see, is the failure mode of every other format.

Choosing between the four is a two-question test. First: does the task branch? If yes, flowchart. Second: is the document consulted during the task or learned before it? During means checklist; before means step-by-step for short tasks and hierarchical for long ones. Don't overthink it — a format mismatch is a minor sin compared to the real killers covered in the compliance section below.

A fifth format is emerging alongside these four: the short video SOP, a 15–30 second demonstration clip per procedure. It's not a replacement for the document (auditors still want the document) but it's rapidly becoming the preferred training format. More on that below.

What is an SOP document? The anatomy

So what is an SOP document, concretely — what sections does it contain? A minimal but complete SOP document has seven parts. (You can grab pre-structured versions of these from the SOP templates hub rather than building from a blank page.)

1. Header block — Title, unique document ID (e.g., SOP-KIT-007), version number, effective date, and the approver's name. The ID matters more than it looks: it's how training records, audit findings, and revisions point to the exact document.
2. Purpose — One or two sentences: what this procedure accomplishes and why it exists.
3. Scope — What the SOP covers and, just as important, what it doesn't. "Applies to all walk-in coolers at the downtown location; does not cover reach-in units."
4. Responsibilities — Who performs the procedure, who verifies it, who owns the document. Named roles, not named people — "Shift Lead," not "Marcus."
5. Materials and prerequisites — Equipment, tools, PPE, credentials, or system access required before starting.
6. Procedure — The steps themselves, in one of the four formats above. Number every step. One action per step. Include the acceptance criterion where it matters: not "chill the soup" but "chill from 135°F to 70°F within 2 hours."
7. Revision history — A table of version, date, author, and what changed. In regulated environments this is mandatory; everywhere else it's how you win the argument about when the procedure changed.

Regulated industries add more: definitions, references to governing regulations, attachments, and formal approval signatures. But if your SOP has these seven parts, it will survive contact with reality.

SOP examples by industry

The fastest way to understand SOPs is to look at what they cover in practice. Notice a pattern across all six industries below: the workhorse SOPs cluster around three themes — safety-critical sequences, contamination or error controls, and handover points where work passes between people. If you're deciding what to document first in your own operation, start where those three themes intersect with your highest-frequency tasks.

Restaurants and food service

• Handwashing procedure — the 20-second, soap-to-dry sequence required before food handling and after any contamination event. The highest-frequency SOP in the building.
• Color-coded cutting boards — raw meat on red, produce on green, ready-to-eat on white, with wash-and-sanitize between uses. The classic cross-contamination control.
• Cooling and cold-holding — the two-stage cooling rule (135°F→70°F in 2 hours, 70°F→41°F within 4 more) and cold-holding at 41°F or below.

Food service is also where the written-SOP failure mode is most visible — new hires simply don't read binders during a chaotic first week. We covered the video-first alternative in detail in our restaurant SOP videos guide.

Manufacturing

• Lockout/tagout (LOTO) — de-energizing and locking equipment before maintenance so it can't start while someone's hands are inside it.
• Machine startup and shutdown — the exact sequence for bringing a line up and down, including safety checks and warm-up parameters.
• First-article inspection — verifying the first unit off a changed-over line against spec before running the batch.

Pharmaceutical and GMP

• Cleaning validation — proving that equipment cleaning actually removes product residue and cleaning agents to defined limits, with sampling and testing.
• Deviation handling — what happens the moment something departs from a validated process: containment, documentation, investigation, CAPA.
• Batch record review — the second-person check of manufacturing records before a batch is released.

Pharma SOPs live under the strictest regime of any industry — FDA 21 CFR Part 211 and EU GMP both mandate written procedures, and auditors read SOPs against actual practice line by line. It's a big enough topic that we've written a dedicated guide to pharmaceutical SOPs.

Healthcare

• Hand hygiene (WHO five moments) — when and how clinical staff perform hand antisepsis around patient contact.
• Medication administration (the rights check) — verifying right patient, drug, dose, route, and time before administering.
• Sharps disposal — handling and disposing of needles to prevent needlestick injuries.

IT and software operations

• Employee onboarding/offboarding — account provisioning on day one and, more critically, access revocation on the last day.
• Incident response — severity classification, escalation paths, communication cadence, and post-incident review.
• Backup verification and restore testing — not just running backups, but periodically proving they restore.

Warehouse and logistics

• Forklift pre-shift inspection — the daily walk-around check OSHA expects before a powered industrial truck is used.
• Receiving and putaway — verifying inbound goods against the PO, damage inspection, and correct bin placement.
• Pallet stacking and racking limits — load limits, stacking patterns, and what never goes on a top rack.

Warehouses are a special case for one reason: turnover. Seasonal hiring can double a warehouse workforce in six weeks, which means SOP training has to work at speed and at scale. This is exactly the environment where a looping 20-second demonstration on a screen near the dock outperforms any document — the same clip trains the fiftieth hire as reliably as the first.

What is SOP in IT?

The question "what is an SOP in IT" deserves its own answer because IT usage differs slightly from the manufacturing tradition. In IT, an SOP is a documented procedure for a recurring operational task — provisioning a user account, rotating credentials, applying patches, responding to a sev-2 incident, restoring from backup. The term overlaps heavily with runbooks: a runbook is essentially an SOP for a specific operational scenario, often written to be executed under pressure at 3 a.m.

Two things distinguish IT SOPs:

• Automation pressure. In IT, a mature SOP is often a script waiting to happen. The document phase is still valuable — you can't automate a procedure you haven't defined — but the endpoint is frequently "this SOP is now a pipeline."
• Framework alignment. IT SOPs commonly map to ITIL processes (incident, change, problem management) or to control frameworks like SOC 2 and ISO 27001, where auditors ask for documented procedures exactly as an FDA inspector would in a pharma plant. If you're pursuing SOC 2, your access-review and offboarding SOPs are audit evidence.

The failure mode is the same as everywhere else, though: the runbook that was accurate two infrastructure migrations ago is worse than no runbook, because someone will follow it.

The SOP lifecycle: draft, approve, train, review

An SOP is not a document you finish; it's a document you operate. Mature organizations run every SOP through the same four-stage loop:

Draft. The task owner — the person who performs the work — supplies the steps, ideally by talking through the task while someone captures it, or by being observed doing it. Drafting from memory at a desk is how fictional procedures get written. A practical trick: have the drafter perform the task following only their own draft, and note every place they did something the draft doesn't say.

Approve. A supervisor or quality function reviews the draft for accuracy, safety, and regulatory fit, then formally approves it with a version number and effective date. From this moment the SOP is a controlled document: the approved version is the only version, old copies are withdrawn, and changes require a new revision. Uncontrolled copies — the printout taped inside a cabinet three revisions ago — are a classic audit finding.

Train. Everyone who performs the procedure is trained on it and the training is recorded: who, which SOP, which version, what date. This record is what connects the document to the workforce. When SOP-KIT-007 moves to version 4, the training matrix tells you exactly who needs retraining.

Review. On a fixed cycle — and immediately after any process, equipment, or regulatory change — the SOP is re-examined against actual practice. Either the document changes to match improved practice, or practice is corrected to match the document. The review that rubber-stamps without comparing is the review that lets drift accumulate.

The lifecycle is also where SOP programs get their return on investment. The draft stage captures expert knowledge; the training stage distributes it; the review stage keeps it true. Skip any stage and the document decays into shelfware.

SOP compliance: why SOPs fail

Writing the SOP is the easy half. SOP compliance — people actually following the procedure, and being able to prove it — is where most programs quietly collapse. The failure patterns are remarkably consistent across industries:

Written but never read. The SOP exists to satisfy an audit, lives in a binder or a SharePoint folder, and the people doing the task have never opened it. They learned the job from whoever trained them, drift and all. When auditors compare the SOP to observed practice, this is the most common finding: the document describes a fictional process.

Written by the wrong person. An office-based manager writes what they believe happens on the floor. Operators immediately spot the gaps, conclude the document is theater, and ignore it — along with every future SOP.

Too long to use. A 14-page SOP for a 90-second task. Length signals thoroughness to the author and unusability to the reader. If the procedure can't be consulted during the task, it won't be.

Never updated. The equipment changed, the software got upgraded, the recipe was reformulated — the SOP wasn't. Now the compliant employee is the one doing it wrong. Stale SOPs actively train people to disregard documentation.

Training was a signature, not a transfer. "Read and understood" sign-off sheets create compliance records, not competence. An employee who signed 40 SOPs on day one has read approximately zero of them.

Fixing compliance is mostly about lowering the cost of consumption: shorter documents, checklists at the point of work, procedures written by the people who do the task, scheduled review cycles (annual or biennial review is the norm in regulated industries), and training that demonstrates the task rather than describing it. Which brings us to the format shift.

From documents to short videos: the format shift

The biggest change in how SOPs get trained — not written, trained — is the move from documents to short demonstration videos. The logic is straightforward: the document remains the controlled source of truth for auditors and revision history, but the training artifact becomes a 15–30 second clip showing the procedure being performed. One SOP step, one video. Hands, equipment, environment — the actual task, watched instead of read.

Why now? Because the production cost collapsed. Filming a procedure used to mean scheduling a camera, a quiet shift, and an editor; re-filming after every revision meant it never happened. AI generation removed that constraint. With Pellucida, you paste the SOP text, the AI plans a segment-by-segment storyboard, and you review and edit every scene prompt before any video is rendered — so the demonstration matches your procedure, not a generic approximation. The output is a finished MP4 with AI narration and subtitles, in horizontal for the LMS or vertical for a break-room screen.

The operational pattern that works: keep the written SOP as the controlled document, generate one short clip per critical step, loop the clips where the work happens, and attach them to day-one onboarding. New hires watch the standard before anyone teaches them a shortcut. If you want to see the full pipeline from document to clip, the SOP-to-training-video walkthrough shows it end to end.

This isn't video replacing documents. It's video fixing the one thing documents demonstrably fail at: getting consumed.

Frequently asked questions

What does SOP stand for?

SOP stands for standard operating procedure — a documented, step-by-step set of instructions for performing a routine task consistently. The plural is SOPs, and "standard operating procedure" is also used informally to mean "the normal way things are done here."

What is the purpose of an SOP?

The purpose of an SOP is to make a task's outcome independent of who performs it. Specifically, SOPs deliver consistency (same result every time), safety (the safe sequence is documented), regulatory compliance (auditors require written procedures), faster training (new hires learn the standard, not one veteran's habits), and institutional memory (knowledge survives turnover).

What is an SOP in IT?

In IT, an SOP is a documented procedure for a recurring operational task — account provisioning, patching, incident response, backup restoration. The term is largely interchangeable with "runbook." IT SOPs frequently serve as audit evidence for SOC 2, ISO 27001, and ITIL-aligned processes, and mature ones often evolve into automation scripts.

What's the difference between an SOP and a work instruction?

An SOP describes a complete procedure at the level of what to do and in what order; a work instruction zooms into one step with machine- or system-specific detail — exact settings, exact screens, exact keystrokes. One SOP may reference several work instructions. Small teams merge the two into one document; regulated industries keep them as separate document types with separate control.

Who writes SOPs?

The person who actually performs the task should supply the content, typically paired with a supervisor or quality specialist who structures and formalizes it. In regulated industries a quality assurance function then reviews and approves the document. SOPs written by managers without input from operators are the single most common cause of SOPs that don't match reality.

How often should SOPs be updated?

Review every SOP on a fixed cycle — annually is the norm in pharma and healthcare, every two years is a reasonable floor elsewhere — and immediately whenever the process, equipment, software, or regulation changes. Every update gets a new version number and a revision-history entry, and anyone trained on the old version needs retraining on the new one.

---

If you're starting an SOP program from scratch: pick your three highest-risk procedures, write them with the people who do the work, and use a template from the SOP library so you're not inventing structure. And when the documents are written, turn the critical steps into short clips your team will actually watch — the Studio is free to explore.