SOP vs Work Instruction: What Is the Difference? (With Examples)

Using these terms interchangeably creates documentation hierarchies that confuse auditors and fail operators. Here is a precise definition of each, with real manufacturing examples and how ISO 9001 and AS9100 reference both.

SOP vs Work Instruction: What Is the Difference?

An SOP (Standard Operating Procedure) describes what to do and who is responsible at the process level. A work instruction describes exactly how to perform a specific task at the operator level — step by step, with every specification value, tool, and acceptance criterion included. ISO 9001 and AS9100 do not require you to use these specific terms, but they do require that your documented information hierarchy actually controls your processes. Using the two terms interchangeably creates the conditions for audit findings every time.

Ask twenty quality managers to define the difference between an SOP and a work instruction and you will get twenty different answers. Ask an ISO 9001 auditor, and they will tell you the distinction matters less than most people think — what matters is that your documentation hierarchy is logical, consistent, and actually controls your processes.

That said, using the terms interchangeably creates real problems: procedures at the wrong level of detail, documents with unclear ownership, and documentation structures where auditors cannot determine which document controls what.

The Documentation Hierarchy

Most quality management systems have four or five tiers:

Tier 1 — Quality Policy: A statement of organizational quality commitments. Written for leadership and external stakeholders. Reviewed annually.

Tier 2 — Quality Manual / Process Map: A description of QMS structure, how processes interact, and the organization's certification scope.

Tier 3 — Procedures and SOPs: Documents describing how a process is managed, who is responsible, and what inputs and outputs are required. SOPs operate at the process level.

Tier 4 — Work Instructions: Step-by-step directions for performing a specific task. They tell one person doing one task exactly how to do it correctly.

Tier 5 — Job Aids, Forms, Records: Supporting documents — templates, labels, checklists, inspection records.

Defining an SOP

A Standard Operating Procedure describes the what and who of a process. It answers: What is this process supposed to accomplish? Who is responsible for each part of it? What are the inputs and outputs? What other processes does it interface with?

An SOP for incoming inspection would describe: the purpose of incoming inspection, who is authorized to perform it, the general process flow from receipt to pass/fail disposition, records required, and how nonconforming material is escalated.

An SOP is appropriate when: the process involves multiple roles, the document needs to be understood across different functions, or the document describes a management or administrative process rather than a specific physical task.

SOPs are typically 2-6 pages. They use flowcharts and responsibility matrices. They reference work instructions for specific task execution but do not prescribe numbered steps themselves.

Defining a Work Instruction

A Work Instruction describes the how of a specific physical task. It tells one person, performing one task, exactly what to do in numbered sequential steps.

A work instruction for incoming inspection of fasteners would describe: which fasteners are covered, what tools are required, step-by-step inspection criteria for each characteristic, how to record results, and what to do with passing versus failing parts.

A work instruction is appropriate when: the task has specific physical steps, the task has critical parameters that must be controlled, variation in execution directly affects quality or safety, and the person performing it needs step-by-step guidance.

Work instructions are typically 1-4 pages per task. They use numbered imperative steps. They include images and embedded specification values.

How Auditors Distinguish Between Them

ISO 9001:2015 does not define "SOP" or "work instruction" as distinct document types — it uses the single term "documented information." But auditors evaluate whether documented information is at the right level of detail for the risk and complexity of the process it controls.

An auditor reviewing your incoming inspection process will look for: a procedure-level document describing the process and responsibilities (your SOP), and step-level instructions for each inspection type performed (your work instructions).

Finding only the SOP with no work instructions means operators must determine their own inspection methods — an unacceptable variation source. Finding only work instructions with no SOP means no one has documented who owns the process. Both are gaps.

The common audit finding: calling a work instruction an SOP, then writing it at SOP level when the process actually requires step-level control. The document exists. It does not control the process.

Real Manufacturing Examples

Documents that are correctly SOPs:

Documents that are correctly Work Instructions:

Documents people get wrong: Customer complaint handling. The response process is an SOP. The steps for writing the 8D report or conducting root cause analysis are work instructions.

ISO 9001 and AS9100 References

ISO 9001:2015 Clause 7.5 requires documented information for QMS operation (process level) and for process execution (task level). Both document types map directly to this requirement.

AS9100 Rev D Clause 8.5.1 explicitly requires work instructions for manufacturing processes and states they must be accessible at the point of use. This is not an SOP-level requirement — it requires task-specific step instructions.

IATF 16949 Clause 8.5.1.1 requires job instructions for all operators performing operations that affect product quality, accessible at the workstation, including acceptance criteria and reaction plans.

The Most Common Mistake

Calling everything an SOP and writing everything at the SOP level. This creates documentation that describes processes without controlling them — every auditor's least favorite outcome.

The fix is not creating more documents. It is assigning the right level of detail to the right document type and ensuring each type actually controls the process it is responsible for.

Coplain generates operator-ready work instructions at the right level of detail, distinct from your SOP library. Try free at coplain.com.

Frequently Asked Questions

Q: What is the difference between an SOP and a work instruction?

A: An SOP describes what to do and who is responsible at the process level — inputs, outputs, responsibilities, and major steps. A work instruction describes exactly how to perform a specific task at the operator level — every step numbered, every specification value included, images at critical points. The SOP provides the framework; the work instruction provides the detail operators need to execute without interpretation.

Q: Does ISO 9001 require work instructions?

A: ISO 9001 requires "documented information to the extent necessary to have confidence that processes are carried out as planned." Work instructions are not explicitly required by name, but they are required whenever a process has critical parameters where variation would affect product conformance. In practice, any manufacturing process with specifications that operators need to follow requires a work instruction or equivalent.

Q: Can a work instruction replace an SOP?

A: They serve different purposes and neither replaces the other. An SOP that tries to serve as a work instruction becomes too long and too operator-unfriendly. A work instruction that tries to serve as an SOP lacks the process-level context auditors need. Most quality systems need both: SOPs for process-level control and auditor review, work instructions for operator-level execution.

Q: What is the right length for an SOP?

A: An SOP should describe the process completely enough that a competent new person could understand the process flow, responsibilities, and key requirements — typically 2–8 pages. If it runs longer, it probably contains procedure detail that belongs in work instructions, or background information that belongs in training materials, not controlled documents.

Stop reading about better documentation. Start creating it.

Coplain turns any work instruction into a print-ready, audit-proof job aid in minutes.