SOP vs Work Instruction: What is the Difference and When to Use Each

Using a work instruction when the procedure requires an SOP is one of those small errors that becomes a finding during an audit. The document hierarchy in a quality management system is not arbitrary. Each level serves a different purpose and carries different authority. Misclassifying a document is not just an organizational error. It is a signal to an auditor that the document control system is not well understood.

The distinction matters most in regulated environments: medical device manufacturing under ISO 13485 or FDA 21 CFR Part 820, pharmaceutical manufacturing under GMP, and automotive production under IATF 16949. In each of these frameworks, the document type determines what approval authority is required, what it can reference, and what authority it carries within the QMS.

What is a Standard Operating Procedure?

A standard operating procedure is a cross-functional, authority-bearing document. It defines a complete process from initiation to close, including every decision point, sign-off requirement, and deviation path within that process. An SOP does not describe a single task at a single workstation. It covers the entire process boundary, often spanning multiple functions and multiple people.

The scope of an SOP is process-level. Incoming inspection of metallic components is a process. Final assembly testing is a process. Batch release is a process. Each of these requires an SOP because each involves multiple steps, multiple roles, multiple acceptance decisions, and a defined outcome that must be documented.

An SOP requires multi-party approval. Typically this means engineering review, quality assurance approval, and sometimes regulatory affairs sign-off depending on the process risk class. The approval matrix confirms that the people with authority over the process have reviewed and accepted the procedure. A work instruction approved only by a production supervisor does not carry the same QMS authority as an SOP approved by quality assurance and engineering.

SOPs define the who, what, when, and what happens if it fails. They are written at a level that a trained supervisor or a quality engineer can follow and verify. They are owned by a process or quality function, not by a single workstation or a single operator. When the process changes, the SOP must be revised, reviewed, and re-approved through the full approval authority.

What is a Work Instruction?

A work instruction is a task-level, operator-facing document. It describes how to perform a single step, a single operation, or a single function at a specific workstation within a larger process. The key distinction is that a work instruction never stands alone. It exists inside the framework established by a parent SOP.

A work instruction references its parent SOP. An operator following a work instruction is performing one task within a process that is governed by an SOP. The work instruction inherits its authority from the SOP. It cannot override the SOP, cannot expand the scope of the process, and cannot change acceptance criteria that the SOP has established.

The level of detail in a work instruction is operator-level. This means step-by-step instructions that an operator can follow correctly without prior knowledge of the process or the product. Work instructions for orientation-sensitive operations often include photographs or diagrams showing correct and incorrect component placement. They specify exact tool names, exact measurement instruments, and exact forms for recording results.

Work instructions typically require less approval authority than SOPs. In many QMS frameworks, a work instruction is approved by a process engineer or production engineer without requiring quality assurance sign-off, because the QA authority is established in the parent SOP. Check your document control procedure to confirm what your QMS requires.

The key differences

Dimension	SOP	Work Instruction
Scope	Complete process	Single task or station
Primary reader	Supervisor, engineer, QA	Production operator
Level of detail	Process-level with defined parameters	Step-by-step for one specific task
QMS authority	Process-level control document	Task-level reference document
Stands alone	Yes	No. References parent SOP.
Approval authority	QA, engineering, sometimes regulatory	Typically process engineering
Revision trigger	Process changes	Task execution changes

Which document do you need?

Three questions determine the right document type. First: who is the primary reader? If the answer is a production operator who needs to know exactly what to do at a specific station, the document is probably a work instruction. If the answer is a quality engineer, a supervisor, or a compliance reviewer who needs to understand a complete process, the document is probably an SOP.

Second: is this a task or a complete process? A task is one operation within a process, with a defined start and end, performed by one operator in one location. A process spans multiple tasks, multiple operators, and multiple decision points. If you are describing a task, write a work instruction. If you are describing a process, write an SOP.

Third: does this document need to exist independently of any other document? SOPs are standalone. They can be read, reviewed, and audited without reference to any other procedure. Work instructions cannot. They exist within the structure of a parent SOP. If you are writing a document that cannot stand alone, you are writing a work instruction.

When you need both

Most regulated processes need both an SOP and one or more supporting work instructions. The SOP sets the rules for the process. The work instructions show specific operators how to perform specific tasks within those rules.

An example makes this concrete. Incoming inspection of metallic components requires an SOP and at least one work instruction.

The SOP covers: the complete inspection process, the sampling plan (how many parts are inspected per lot, per which standard), the acceptance criteria (what dimensions are checked and at what tolerances), the deviation routing (what happens when a part fails inspection), the QA sign-off requirements, how records are retained, and what disposition authority exists for non-conforming material. The SOP is written at the process level and approved by quality assurance.

The work instruction covers: how a specific operator uses a calibrated dial caliper to measure the outer diameter of part number XYZ-001 at inspection station 4. Which faces of the part to measure. How many readings to take. Which fields in the inspection record to complete. How to record a reading that is out of specification. The work instruction is written for the operator performing that one measurement task, and it references the parent inspection SOP for process authority.

Without the SOP, the work instruction has no defined context, no acceptance criteria authority, and no deviation path. Without the work instruction, the SOP relies on operator judgment for the measurement technique, which means the measurement may not be performed consistently across operators and shifts.

For a detailed guide on writing the SOP itself, including the section structure, step format, and audit requirements, see the guide on how to write a manufacturing SOP. For a complete example of a controlled document in this format, see the batch annealing SOP example. If you have a document set that needs to be assessed for correct classification and completeness before an audit, the Aptibot documentation service covers documentation gap analysis and procedure writing for regulated manufacturers.