How to Write a Work Instruction That Operators Actually Follow

Most work instructions fail at the operator level, not the audit level. They pass the document review because the format is correct and the approvals are in place. Then the operator ignores them because the steps assume knowledge that was never written down. This guide covers the format that works, the writing approach that produces steps operators can follow without asking, and the common mistakes that make the document shelf decoration.

The difference between a work instruction and an SOP

A work instruction is operator-facing and task-level. It describes exactly how to perform a specific task at a specific station, written for the person doing the work. A standard operating procedure sits one level above it, covering a broader process and carrying QMS authority as a controlled procedure.

A work instruction references its parent SOP. It does not carry independent QMS authority. If the SOP defines the torque control process, the work instruction describes how to torque a specific joint on a specific assembly at a specific workstation. They are not interchangeable. For a full breakdown of the distinction, see the guide on SOP vs work instruction.

The practical consequence is that a work instruction can be revised more frequently than its parent SOP, often without triggering a full QMS document review. This makes it the right tool for process detail that changes as manufacturing matures.

Work instruction format (section by section)

Every work instruction requires a structured header that appears on every page of the document. The header contains the document number in your QMS numbering system, the document title, the revision number, the effective date, the department, the author name and role, the reviewer name and role, the approver name and role, and the page number out of total pages. If a page of the document is separated from the rest, the header alone must identify it and allow someone to verify they have the current revision.

The purpose section is one sentence. "This work instruction describes how to [specific task] at [specific station]." Nothing more. A purpose section that runs to two paragraphs is explaining the business context, not the purpose of the document. That context belongs somewhere else.

The scope section defines two things: what the instruction covers and what it does not cover. Specify which part numbers, which equipment, and which process step fall within scope. Then explicitly state the limitations of applicability. If the instruction applies only to aluminum variants of a part, say so. If it does not apply to rework, state that. Gaps in scope create operator confusion about when to follow the document.

The materials and tools section must be specific. "Torque wrench" is not a specification. "Torque wrench TW-003 (calibration due 2027-03-15, Cal-ID: CAL-TW-003)" is specific enough for an operator to verify they have the right tool in the right calibration state before starting. List part numbers for consumables, specification numbers for materials, and calibration IDs for all measuring instruments. If a tool is substitutable, name the primary tool and any approved alternates. If it is not substitutable, say so explicitly.

The safety section comes before the procedure steps. Operators need to prepare for safety requirements before they begin the task, not after reading through five steps. List all required PPE with specification where it matters (cut-resistant gloves rated to ANSI A4, not just "gloves"). Name any hazardous materials by proper chemical name. Identify all required energy isolation actions before the work begins, and reference the specific lockout/tagout procedure by document number.

The procedure steps section is the core of the document. See the next section for detailed guidance on how to write steps that are unambiguous.

The non-conformance section is the most frequently missing section in work instructions reviewed under ISO 9001:2015 QMS documentation requirements. It tells the operator what to do when a step cannot be completed as written or when the output of a step does not meet its acceptance criterion. Without this section, the operator faces a binary choice: ignore the problem or stop production without knowing the correct escalation path. Neither outcome is acceptable. The non-conformance section should identify the specific person or role to notify, the form or system used to record the nonconforming condition, and whether work can continue downstream or must stop.

The record keeping section identifies every record generated during the task. Name the form by its form number, describe what data is entered, and specify where the completed record is retained and for how long. If records are electronic, name the system and the data entry location within it.

The sign-off section captures the operator's initials and date confirming the task was completed per this instruction. This is not a quality inspection sign-off. It is the operator's confirmation that they performed the work using this document as their guide.

How to write procedure steps that are unambiguous

Each step contains one action verb. The operator reads the step, performs the action, and knows whether the output is acceptable before moving to the next step. If a step requires two decisions or two physical actions, it is two steps.

The difference between a bad step and a good step is measurability. "Tighten the bolt until snug" gives the operator three unknowns: which bolt, how tight is snug, and how do they verify it. A correct step reads: "Using torque wrench TW-003, tighten bolt M8x25 at position J4 to 22 Nm plus or minus 2 Nm. Record torque value in column 4 of form F-WI-022." The operator knows the tool, the part, the location, the target, the tolerance, and what to record. There is no judgment required.

Every measurement requires a value and a tolerance. The words "approximately" and "roughly" are not specifications. If the acceptable range is not known, the process has not been characterized well enough to write a work instruction for it. Get the process characterization data first.

When a step requires a calibrated instrument, name the instrument by its asset ID and state the calibration status check the operator must perform before using it. "Verify Cal-ID CAL-TW-003 tag on instrument shows calibration due date is in the future before use" is a verifiable step. Assuming the operator will check calibration without being told to is how calibrated instruments get used past their due date.

Acceptance criteria follow every step where the output can be verified. The format is: perform action, then verify result. "Verify the assembly is flush with the datum surface. Gap must not exceed 0.5 mm. If gap exceeds 0.5 mm, do not proceed. Follow non-conformance procedure NCR-WI-022." The operator knows the standard before they move on.

Images and diagrams belong in the step where they are relevant, not in an appendix. If an operator has to flip to the back of the document to understand a diagram while performing a step, the document design is working against the operator. Place the visual at the step that requires it.

How to validate a work instruction before releasing it

Document review by a subject matter expert is not validation. The SME already knows the process. They will read the steps and understand them because they are reading from their own mental model of the task, not from the text alone. The gaps in the document are invisible to them.

Validation requires an operator who did not write the instruction and has not performed this specific task recently. Give them the document and ask them to perform the task. Watch without helping. Every time they stop, hesitate, ask a question, or look at something other than the document, that is a gap.

The most common finding during operator walk-throughs: step 4 assumes the operator knows which side of the part faces up. This was communicated verbally during initial training two years ago. The current workforce includes operators hired since then. The document does not say which side faces up. Half the rejects from station 4 are traced to this missing orientation step.

Document every gap observed during the walk-through before revising the instruction. If you correct issues while watching, you lose the ability to distinguish which issues the operator encountered in sequence and which were related. A complete gap log from the walk-through is the validation evidence that supports releasing the instruction.

If the operator completes the task correctly on the first walk-through using only the document, and the output meets all acceptance criteria, the instruction is validated for that operator profile. A second walk-through with a different operator provides additional confidence, particularly for complex or safety-critical tasks.

When a work instruction needs photographs or diagrams

Any step where position, orientation, or surface condition matters and cannot be fully described in text requires a visual. "Install the gasket in the groove" is ambiguous when the groove has two possible orientations. A photograph showing the correct installed state eliminates the ambiguity.

Complex assembly sequences where the order of operations affects the result require a step sequence diagram. If installing component B before component A makes component A impossible to install without damage, a visual showing the correct sequence prevents the failure. Text alone creates ambiguity in complex spatial relationships.

Safety-critical torque sequences, particularly star patterns and cross patterns required for multi-bolt flanges and gasketed joints, must be diagrammed. A numbered bolt pattern diagram with the tightening sequence annotated is the only reliable way to communicate the pattern. Describing a 12-bolt pattern in text produces unacceptable interpretation risk.

When photographs are used, photograph the correct result, not the process of getting there. Show what the accepted output looks like. A photograph of someone's hands performing a step is less useful than a photograph of the correctly installed component from the operator's viewpoint. The operator is looking for confirmation that their output matches the standard, not a how-to demonstration.

All photographs should include a scale reference and be taken from the operator's natural viewpoint at that station. A photograph taken from above when the operator works from the side provides an angle the operator cannot use for comparison during production.

If your document system supports it, include a red-line version of the photograph that marks the specific feature being assessed in each step. A circle around the gap measurement location removes any ambiguity about which surface is being evaluated. Visual aids that require interpretation defeat their own purpose.

Review all photographs when the document is revised. A photograph taken two equipment generations ago showing legacy tooling that no longer exists in the facility undermines operator confidence in the entire document. Outdated visuals are often a stronger contributor to document non-use than outdated text, because the operator immediately recognizes the mismatch between the photograph and what they see in front of them.

For a sample SOP showing how these elements come together in a complete document, or to have your existing work instructions reviewed and rebuilt to this standard, see the Aptibot documentation service.