How to Write Work Instructions: Step-by-Step Guide & Examples
A work instruction is a document that describes the specific steps required to complete a single task. Unlike a Standard Operating Procedure (SOP), which manages the overall process and flow between people, a work instruction focuses entirely on the "how."
If you tell a new hire to "process the monthly payroll," that is a process. If you tell them "Log into Gusto, click 'Run Payroll,' select 'Salaried Employees,' and verify the total hours match the spreadsheet," that is a work instruction.
Most teams struggle with consistency because they stop at the SOP level. They define the rules but fail to document the mechanics. This guide covers how to write work instructions that remove ambiguity, with templates and examples for both digital and physical tasks.
What Are Work Instructions?
A work instruction (WI) is a granular, step-by-step guide designed to help an employee perform a specific task correctly and safely. In ISO 9001 and other quality management frameworks, work instructions sit at the bottom of the documentation hierarchy—they are the most detailed and specific documents you create.
Effective work instructions are:
- Visual: They rely heavily on screenshots, photos, or diagrams.
- Imperative: They use command-driven language ("Click," "Turn," "Enter").
- Linear: They follow a strict chronological order.
- Accessible: They are available right where the work happens.
If an SOP is the map of the building, the work instruction is the manual for operating the security keypad at the front door.
SOP vs. Work Instructions: What Is the Difference?
The terms are often used interchangeably, but in compliance and operations, they serve different functions. Mixing them up leads to bloated documentation that no one reads.
| Feature | Standard Operating Procedure (SOP) | Work Instruction (WI) |
|---|---|---|
| Focus | The Process (Who, What, When, Where) | The Task (How) |
| Level of Detail | High-level overview of workflow | Granular, click-by-click or motion-by-motion |
| Audience | Managers, Supervisors, Cross-functional teams | The specific operator or user performing the task |
| Length | Often covers multiple steps and handoffs | Covers one specific activity from start to finish |
| Example | "Customer Complaint Handling Process" | "How to Log a Ticket in Zendesk" |
How to Write Work Instructions in 6 Steps
Writing work instructions requires a different mindset than writing policy. You aren't explaining why something is done; you are explaining how to do it without error.
1. Define the Scope and Task
Don't try to document an entire role in one document. Pick one discrete task. A good rule of thumb: if the task takes more than 30 minutes or involves switching between completely different tools/stations, break it into two instructions.
Example title: "How to Generate the Weekly Sales Report in Salesforce" (Not "Sales Operations Guide").
2. List Prerequisites and Safety Warnings
Before the first step, list what the user needs.
- Tools: Software access levels, physical tools, logins.
- Inputs: Data sources, raw materials, specific files.
- Safety/Compliance: PPE requirements, data privacy warnings (e.g., "Do not export PII").
3. Write Steps in the Imperative Mood
Start every sentence with a verb. Be direct. Avoid passive voice.
- Bad: "The 'Submit' button should be clicked after the data is entered."
- Good: "Enter the data. Click Submit."
4. Add Visual Context
Text alone is rarely enough for a work instruction.
- Digital tasks: Use annotated screenshots. Circle the button they need to click.
- Physical tasks: Use photos of the machine setup or the correct hand position.
Visuals reduce interpretation error. If a user has to guess which "blue button" you mean, the instruction has failed.
5. Validate the Instruction
Hand the draft to someone who has never done the task. Watch them try to follow it without intervening. If they ask a question, your instruction has a gap. Mark that spot and revise it.
6. Assign Version Control
Work instructions change frequently—software updates move buttons, and machinery gets recalibrated. Every WI needs a version number, a "Last Updated" date, and an owner responsible for maintaining it.
Work Instruction Examples
Here are two examples showing how the format shifts between digital and physical workflows.
Example 1: Digital Work Instruction (Software)
Task: Adding a New User to Slack
Prerequisites: Admin access to Slack workspace.
- Navigate to Admin Panel: Click the workspace name in the top left corner. Select Settings & administration > Manage members.
- Invite Members: Click the green Invite People button on the right side of the screen.
- Enter Details: Type the email addresses of the new hires.
- Select Channel Access:
- For contractors: Select Guest and choose specific channels.
- For full-time employees: Select Full Member (gives access to default channels).
- Send: Click Send Invitations.
Example 2: Physical Work Instruction (Manufacturing/Logistics)
Task: Labeling Outbound Packages
Prerequisites: Zebra ZT410 Printer, 4x6 labels, scanner.
- Verify Order: Scan the pick ticket barcode. Ensure the screen displays "Order Verified."
- Print Label: Press the Print button on the touch screen. Wait for the label to fully eject.
- Inspect Label: Check that the address is legible and the barcode is not streaked.
- If streaked: Discard label, clean print head, and reprint.
- Apply Label: Peel the backing. Place the label on the top surface of the box, ensuring it does not overlap the seam tape.
- Final Scan: Scan the applied label to confirm the system updates to "Shipped."
What Should Be Included in a Work Instruction Template?
If you are building a library of instructions, standardization is key. A solid work instruction template includes:
- Header: Title, ID Number, Version, Effective Date.
- Purpose: One sentence explaining the output of this task.
- Responsibilities: Who is allowed to perform this task.
- Equipment/Tools: What is needed.
- The Procedure: Numbered list of steps with images.
- Troubleshooting: "If X happens, do Y."
- References: Links to the parent SOP or related policies.
Manual vs. Automated Documentation: The Screenshot Problem
The hardest part of creating work instructions isn't writing the text—it's capturing the visuals.
The Manual Method (Word/Docs)
Most teams start by taking screenshots using Snipping Tool (Windows) or Command-Shift-4 (Mac). They paste the image into a Word doc, draw a red box around the button, and type the instruction below it.
The problem: This is incredibly slow. Documenting a 20-step software process can take an hour. Updating it when the software interface changes takes just as long. As a result, work instructions are often outdated the moment they are published.
The Automated Method (Screen Recording)
Modern documentation tools solve this by recording your workflow. You simply perform the task once, and the software generates the work instruction for you.
Tools like Glyde run in your browser while you work. When you click a button, Glyde captures the screenshot, highlights the element you clicked, and writes the text instruction ("Click 'Save Changes'"). It captures the technical metadata (selectors, URLs) to ensure accuracy.
Instead of spending an afternoon formatting a Google Doc, you get a finished work instruction in the time it takes to do the task once.
Common Mistakes to Avoid
Even with good intentions, work instructions can fail if they aren't user-centric.
- Wall of Text: If your instruction looks like a novel, operators will skim it and miss details. Use whitespace and bold text.
- Dead Ends: Every instruction should end with a clear completion state. How does the user know they are done? (e.g., "A success banner will appear.")
- Assuming Knowledge: Don't say "Check the logs." Say "Open the 'Logs' folder on the desktop and open the file named 'error.txt'."
- Buried Files: If the work instruction is saved in a folder nobody can find, it doesn't exist. Link WIs directly inside the software (if possible) or pin them in your team's knowledge base.
Summary
Work instructions are the bridge between a process map and the actual execution of work. They are essential for training new hires, maintaining compliance, and ensuring quality control.
To create them effectively:
- Isolate the specific task.
- Use a consistent template.
- Write in clear, imperative commands.
- Use visuals for every major step.
- Keep them updated as tools change.
Learn More About Standard Operating Procedures
For a broader look at how work instructions fit into your overall process management, see our guide on the complete guide to standard operating procedures, including how to structure your documentation hierarchy.
