Work Instruction Template: Examples and Formats
A work instruction is the most granular task-level document your team writes: the exact, ordered steps one person follows to perform one job correctly every time. This guide gives you a ready-to-use work instruction template in three formats (simple step-by-step, detailed with roles and safety, and checklist style), a filled-in example, and clear rules for writing them. If you also manage broader procedures, our SOP template and our walkthrough on how to write an SOP cover the level above this one.
The hard part is rarely the content. It is staring at a blank page and inventing structure. Seeing a finished work instruction next to its template removes that friction, so you can fill in your own steps in minutes. For more formats across doc types, see our process documentation examples.
Key Takeaways
- A work instruction documents how to do one task; an SOP documents what a process is and who owns it.
- A good work instruction has eight elements: title, purpose, scope, roles, materials, numbered steps, safety notes, and a review date.
- Three formats cover almost every case: simple step-by-step, detailed with roles and safety, and checklist style.
- 70% of employees say they lack mastery of the skills their job needs, often because instructions are missing or unclear (Gartner, 2024).
- Work instructions go stale fast. They belong on a searchable site, not in a buried file.
What Is a Work Instruction?
A work instruction (also called a job instruction or work instruction document) explains the precise way to complete a single task. It sits at the bottom of the documentation hierarchy: a policy says why, a process says what stages exist, an SOP says how a process runs end to end, and a work instruction says exactly how to perform one step inside that procedure.
Think of changing a printer toner cartridge, closing the books for one client, or running a daily database backup. Each is narrow, repeatable, and benefits from one correct sequence anyone can follow. That is the job of a work instruction.
SOP vs Work Instruction
People mix these up constantly. The difference comes down to altitude. An SOP describes a whole procedure, its purpose, owners, and timing. A work instruction zooms into one task within that procedure and spells out every action. Usually one SOP is supported by several work instructions.
| Work Instruction | Standard Operating Procedure (SOP) | |
|---|---|---|
| Question it answers | How do I do this one task? | What is this process and who runs it? |
| Scope | A single task or step | An entire procedure |
| Detail level | Very high, action by action | Moderate, stage by stage |
| Audience | The person doing the work | Anyone who owns or audits the process |
| Length | Often one page | Several pages |
| Example | "How to reset a customer password" | "Customer account management procedure" |
If you are deciding which to write first, start with the SOP to map the procedure, then break the precise tasks into work instructions. Our guide on how to write an SOP covers that upper layer in detail, and the instruction manual template post helps when you are bundling many instructions for end users.
Key Elements of a Good Work Instruction
Every effective work instruction document shares the same backbone. Skip an element and the reader either guesses or asks someone, which defeats the purpose.
- Title and ID. Name the exact task and give it a number so it is easy to reference and version.
- Purpose. One sentence on why the task matters and what done looks like.
- Scope. When this applies and when it does not.
- Roles. Who performs the task and any required qualification or access.
- Materials and tools. Everything needed before starting, listed up front.
- Steps. Numbered, one action per step, written in the active voice.
- Safety and quality notes. Warnings, checks, and acceptance criteria inline with the relevant step.
- Review info. Author, last reviewed date, and next review date so the document stays current.
A clear work instruction format keeps these in a fixed order so readers always know where to look. The three templates below all follow this backbone at different depths.
Work Instruction Template 1: Simple Step-by-Step
Use this when the task is short, low-risk, and the same every time. It is the most common work instruction format and works for office tasks, software steps, and routine admin.
WORK INSTRUCTION
Title: [Task name]
WI ID: [WI-001]
Purpose: [One sentence: what this task achieves]
Applies to: [Role or team]
Tools needed: [List anything required before starting]
Steps:
1. [First action - start with a verb]
2. [Second action]
3. [Third action]
4. [Continue, one action per step]
Done when: [The condition that confirms the task is complete]
Author: [Name] Last reviewed: [Date]
Keep each step to a single action. If a step has the word "and" twice, split it.
Work Instruction Template 2: Detailed With Roles and Safety
Use this for higher-stakes tasks: anything with safety risk, compliance requirements, equipment, or quality checks. It is the standard work instructions format common in manufacturing, lab, field, and ISO 9001 settings.
STANDARD WORK INSTRUCTION
Title: [Task name]
WI ID / Version: [WI-014 / v2]
Linked SOP: [Parent procedure]
Purpose: [Why this task is performed]
Scope: [When this applies / does not apply]
Roles & access:
- Performed by: [Role + required certification or training]
- Approved by: [Role]
Required materials, tools, PPE:
- [Item]
- [Item]
Safety warnings:
- ⚠ [Hazard and how to avoid it]
Procedure:
| Step | Action | Quality check | Notes |
| ---- | ------ | ------------- | ----- |
| 1 | [Action] | [What good looks like] | [Tip] |
| 2 | [Action] | [Check] | [Tip] |
| 3 | [Action] | [Check] | [Tip] |
Acceptance criteria: [How to confirm the task passed]
Author: [Name] Approved: [Name] Last reviewed: [Date] Next review: [Date]
The quality-check column is what separates a real work instruction from a loose list. It tells the reader not just what to do but how to know they did it right.
Work Instruction Template 3: Checklist Style
Use this when steps are linear, hard to skip safely, and benefit from being ticked off. Good for opening and closing routines, equipment startup, and pre-flight style checks.
WORK INSTRUCTION - CHECKLIST
Title: [Task name]
WI ID: [WI-027]
Purpose: [What this confirms or completes]
Frequency:[Daily / per shift / per job]
[ ] 1. [Check or action]
[ ] 2. [Check or action]
[ ] 3. [Check or action]
[ ] 4. [Final verification]
Completed by: ____________ Date/Time: ____________
Issues found: ____________
A checklist trades detail for speed. Pair it with a fuller instruction the first time someone learns the task, then let them use the checklist once trained.
Filled-In Work Instruction Example
Here is the simple template completed for a real software task, so you can see the level of detail to aim for. This is a typical work instruction example a support team would keep on hand.
WORK INSTRUCTION
Title: Reset a customer account password
WI ID: WI-009
Purpose: Restore login access for a verified customer safely.
Applies to: Tier 1 Support
Tools needed: Admin console access, customer's verified email
Steps:
1. Confirm the customer's identity using two account details on file.
2. Open the Admin Console and search the customer's email address.
3. Open the matching account record.
4. Click "Send password reset" (do not set a password manually).
5. Tell the customer the reset link expires in 30 minutes.
6. Log the reset in the ticket with the timestamp.
Done when: The customer confirms they can log in and the ticket is updated.
Author: J. Rivera Last reviewed: 2026-06-01
Notice how every step is one action, the risky shortcut is called out ("do not set a password manually"), and the "done when" line removes any doubt about completion.
How to Write Work Instructions That People Actually Follow
Templates give you structure. These rules give you clarity. Apply them as you write and edit.
- Start each step with a verb. "Open," "Confirm," "Press." Action-first steps are faster to scan.
- One action per step. If a reader can stop halfway through a step, it should be two steps.
- Write for the least experienced reader who will ever do this task, not the expert who wrote it.
- Cut jargon and acronyms, or define them once at the top.
- Put warnings before the step, not after, so nobody reads them too late.
- Add a visual where words struggle. A screenshot or photo beats a paragraph for spatial tasks.
- Test it on someone who has never done the task. Watch where they hesitate, then fix that line.
- Date every document and set a review interval. An unmaintained instruction is worse than none.
That last point is where most teams lose. A work instruction written in a Word file and emailed around is correct for a month, then quietly wrong. Tools like Docsio turn static work instruction docs into a searchable, always-current site, so the team always finds the latest version instead of an outdated copy in someone's downloads folder. Our runbook template post applies the same thinking to incident response.
Where Work Instructions Should Live
A work instruction only helps if the right person finds the right version at the moment they need it. Three failure modes are common: the doc is buried in a shared drive, the version people open is stale, or there are five copies and nobody knows which is real.
Keeping instructions on a single searchable site solves all three. Docsio lets you generate a branded documentation site from your existing files, edit with an AI agent, and publish updates in one click, so your work instructions stay findable and current. The AI generation feature can turn rough notes or an existing document into structured pages in minutes.
Frequently Asked Questions
What is a work instruction?
A work instruction is a document that explains the exact, ordered steps for completing one specific task correctly. It sits below an SOP in detail, focusing on how a single job is done rather than describing an entire process. Work instructions reduce errors, speed up training, and keep tasks consistent across a team.
What is the difference between an SOP and a work instruction?
An SOP describes a whole procedure: its purpose, owners, and stages. A work instruction zooms into one task inside that procedure and spells out every action step. One SOP is usually supported by several work instructions. Put simply, the SOP answers what and who, while the work instruction answers exactly how.
How do you write a work instruction?
Write the title and purpose, define the scope and who performs the task, then list the tools needed. Break the work into numbered steps, one action each, starting every step with a verb. Add safety or quality checks inline, then test the draft on someone unfamiliar with the task and revise where they hesitate.
What should a work instruction include?
A complete work instruction includes a title and ID, a one-line purpose, the scope, the role and access required, the materials or tools needed, numbered action steps, safety and quality notes, and review information with an author and last-reviewed date. The review date matters most, since it keeps the document trustworthy over time.
What is an example of a work instruction?
A common example is "Reset a customer account password": confirm identity, open the admin console, find the account, send the reset link, inform the customer of the expiry, and log the action in the ticket. Each step is a single action with a clear completion condition, which is the hallmark of a good work instruction.
Start with one task your team repeats most and fill in Template 1 today. Once you have a few, publish them somewhere searchable so they stay current. Try Docsio free to turn your work instructions into a living documentation site.