Standard Operating Instruction

A Standard Operating Instruction (SOI) is a documented procedure that is more specific than an SOP but broader than a single-task work instruction. The term is most common in pharma, aerospace, military, and parts of healthcare, where regulators expect a layered documentation system. ^[1] ^[2] In practice, SOI carries one of three meanings depending on the company: a direct synonym for SOP, a synonym for work instruction, or a middle layer that defines the procedure for a section within a larger process. The third reading is the most useful, because it gives you a real document to write rather than a duplicate of something else. SOPs define rules and intent. SOIs define how those rules play out for one section of the process. Work instructions show the operator how to perform individual tasks within an SOI. ^[3]

Key characteristics

Sits between the SOP and the work instruction in a layered quality system. ^[1]
Defines the procedure for one section of a larger process, not the whole process.
Owned by quality, operations management, or a process owner, not the line supervisor.
Written for supervisors and lead operators rather than the operator at the workstation.
Carries scope, references, owner, version, and review date, the same metadata as an SOP. ^[2]
Linked upward to the parent SOP and downward to one or more work instructions.

Example

Sanitation in a food production line

A food plant has an SOP titled 'Cleaning and Sanitation in Production Areas' that defines the rules: approved chemicals, training requirements, recordkeeping, and audit cadence. Underneath that SOP, the team writes an SOI titled 'Daily Sanitation of Line 3' that lists the stages, in order, with chemical concentrations and equipment needed. Underneath the SOI, three work instructions show the operator how to swab the filler nozzle, how to disassemble the conveyor for cleaning, and how to verify ATP test results. The SOP defines the rules. The SOI defines the procedure for one line. The work instructions show how to do each task on that line.

Comparison

SOI vs SOP

Aspect	SOI	SOP
Scope	One section of a process	Whole process or department
Audience	Supervisors, lead operators	Management, QA, auditors
Granularity	Mid-level procedural detail	High-level rules and intent
Common in	Pharma, aerospace, military, healthcare	All regulated industries
Where it links	Up to an SOP, down to work instructions	Down to SOIs and work instructions

How SOPX handles this

SOPX works as SOI software the same way it works as SOP software or work instruction software. The same recording can be framed as a high-level SOP, a section-level SOI, or a task-level work instruction. Teams that already use SOI in their quality system keep their naming and structure. SOPX handles versioning, translation into 50+ languages, and links between layers, so the SOP, the SOI, and the work instructions stay in sync when the process changes.

Frequently asked questions

Is an SOI the same as an SOP?

Sometimes. In some quality systems the two terms are direct synonyms, especially in older manuals. In others, an SOI is a more specific document that defines the procedure for one section of a process, with the SOP sitting above it as the rule layer. Check your quality manual before assuming.

Is an SOI the same as a work instruction?

Not quite. A work instruction is task-level: one operator, one workstation, one task. An SOI is procedure-level: it covers a section of a process and usually links down to several work instructions. Some military and aerospace organizations use SOI as a synonym for work instruction, but in most quality systems the SOI sits one layer above. ^[1] ^[3]

Which industries use the term SOI most?

Pharma (especially under FDA 21 CFR Part 211), aerospace (under AS9100), military quality systems, and parts of healthcare. ^[2] These industries tend to require layered documentation, so they need a name for the layer between the SOP and the work instruction. Industries with simpler quality systems often skip the SOI layer and go straight from SOP to work instruction.

Do I need an SOI if I already have SOPs and work instructions?

Probably not. The SOI layer is most useful when one SOP covers a large process and the work instructions feel too disconnected from it. If your SOPs are already process-specific and your work instructions link cleanly to them, you do not need a third layer. Add SOIs only if your industry requires the term or if your quality system already uses it.

Can SOPX generate an SOI from a process video?

Yes. The same upload can be framed as an SOP, an SOI, or a work instruction. The SOI version usually shows mid-level steps with descriptions and links to detailed work instructions for each task. Edits flow through the linked documents, so when the procedure on Line 3 changes, the SOI and the underlying work instructions update from the same source.

Sources

Statements above draw on the references below. Numbers in the text link to the matching entry.

[1]
Guidance for Preparing Standard Operating Procedures (SOPs)
U.S. FDA · Accessed 2026-05-06
[2]
ISO 9001 Processes, Procedures and Work Instructions
9000 Store · Accessed 2026-05-06
[3]
Standard Operating Procedure vs. Work Instruction: What's the Difference?
iSixSigma · Accessed 2026-05-06

Cite this definition

Copy the citation below for use in slide decks, training material, or research notes.

SOPX Glossary, "Standard Operating Instruction", https://sopx.io/glossary/standard-operating-instruction/, last reviewed 2026-05-06, accessed 2026-05-19.