What are work instructions and how to create yours
A work instruction (WI) is the most detailed level of operational documentation. While a process describes the general flow and an SOP details the procedure, a work instruction goes granular: every click, every field, every verification.
If the SOP says "configure the system," the work instruction tells you exactly how — field by field, screen by screen.
Work instruction vs. SOP vs. Process
Many people confuse these three terms. The difference is in the level of detail:
| Level | Document | Example |
|---|---|---|
| Strategic | Process | "Customer service flow" |
| Tactical | SOP | "How to resolve a support ticket" |
| Operational | Work instruction | "How to log a ticket in Zendesk, step by step" |
The process answers "what" and "why." The SOP answers "how" in general terms. The work instruction answers "how" in detail, with each specific action in the system.
In practice, many companies use SOP and work instruction interchangeably. What matters is not the terminology — it's that the level of detail is sufficient for anyone to execute the task without help.
When to use work instructions
Work instructions are essential when:
- The process involves systems — ERPs, CRMs, internal tools that require specific navigation
- Errors have high impact — financial processes, compliance, security
- The task is complex — many steps with conditional decisions
- Turnover is high — new people need to learn quickly
- The process is regulated — ISO standards, audits require detailed documentation
Industries that use them most: manufacturing, pharmaceutical, food, healthcare, finance, and IT.
Structure of a work instruction
Header
| Field | Description |
|---|---|
| Title | Descriptive name of the task |
| Code | Unique identifier (e.g., WI-FIN-001) |
| Version | Version control (e.g., v2.1) |
| Owner | Who maintains the document |
| Review date | When it was last updated |
| Department | Team or area |
Objective
One sentence explaining what the instruction covers and the expected result:
"This instruction details how to record an incoming invoice in the ERP, ensuring the entry is correct for the monthly close."
Prerequisites
- Access to the ERP's Fiscal module
- Invoice in hand (physical or digital)
- "Fiscal Operator" permission
Detailed steps
Each step describes a specific action with a screenshot:
Step 1: Open the ERP and navigate to Fiscal > Incoming Invoices > New Invoice.
Step 2: In the "Supplier" field, type the company ID and select the business name from the list.
Step 3: In the "Invoice Number" field, enter the exact number from the document.
Step 4: Verify the total amount matches the original invoice. If there's a discrepancy, do not proceed — consult the finance team.
Step 5: Click "Save" and verify the status changed to "Recorded."
Notice how each step is granular — it describes the exact field, what to type, and what to verify. This level of detail is what differentiates a work instruction from an SOP.
Expected result
Describe what confirms the task was completed correctly:
"The invoice appears in the month's invoice list with status 'Recorded' and the values match the original document."
Error handling
List the most common problems and how to solve them:
| Problem | Solution |
|---|---|
| Supplier not found | Register in the Suppliers module first |
| Amount discrepancy | Check for withheld taxes not included |
| System froze | Clear browser cache and try again |
Examples by department
Finance
- How to record an incoming invoice in the ERP
- How to reconcile bank statements
- How to process expense reimbursements
HR
- How to register a new employee in the payroll system
- How to record vacation in the time-tracking system
- How to generate an overtime report
IT
- How to configure VPN for remote access
- How to create a user in Active Directory
- How to deploy to production
Operations
- How to process a sales order
- How to register a product return
- How to conduct a partial inventory
For all these cases, the format is the same: detailed steps with screenshots and verifications at each stage.
Best practices
One instruction per task
Don't mix multiple tasks in a single document. "How to record an incoming invoice" and "How to record an outgoing invoice" are separate instructions.
Screenshots at every step
Images eliminate ambiguity. If the step involves a system, capture the screen and highlight the relevant element. Tools like Instruo capture screenshots automatically while you execute the process.
Imperative language
Use imperative verbs: "Click on...", "Type...", "Select...". Avoid passive voice and long sentences.
Version control
Whenever you update, increment the version and record what changed. This is especially important in regulated environments.
Regular review
Set a review cycle — quarterly or semi-annually. Systems change, interfaces update, and the instruction needs to keep up.
How AI accelerates work instruction creation
The biggest obstacle to creating work instructions is time. Detailing every click with a screenshot manually takes hours. AI eliminates this work:
- Execute the process normally in the browser
- The tool records each action — clicks, filled fields, navigation
- AI generates the steps with clear text and annotated screenshots
- You review and publish — minimal adjustments, professional result
This transforms work instruction creation from a project that takes hours into a process that takes minutes.
Conclusion
Work instructions are the most detailed and practical level of operational documentation. They're essential for system-based processes, regulated tasks, and high-turnover environments. Keep each instruction focused on one task, use screenshots at every step, and review periodically.
To understand how work instructions fit into your company's documentation, read about how to document processes and how to create a knowledge base.
Want to create visual work instructions automatically? Start free on Instruo.