What Are Work Instructions? Definition, Examples and How to Write Them

A work instruction is a step-by-step document that tells a team member exactly how to complete one specific task, in order, with enough detail that they can do it consistently without asking anyone. Unlike an SOP, which covers a whole process and its context, a work instruction is purely operational: what to do, how to do it, right now.

If your team is doing the same task in five different ways, or a new hire made a costly mistake because the task was only ever shown verbally, work instructions are what fix that. Not more training. Not a longer onboarding programme. A clear, numbered instruction anyone can follow from day one.

Work instructions vs SOPs: what’s the difference?

This is the most common point of confusion in ops documentation, and it matters because mixing them up leads to documents that are too long to follow and too vague to be useful. The short version: an SOP defines a process (the what, why, and who). A work instruction defines a task (exactly how, step by step).

For the full treatment, including the documentation hierarchy and when to use each, read our full breakdown of work instructions vs SOPs. For how SOPs, policies, and procedures all fit together in one system, see our guide to SOPs, procedures, and policies explained. If you are evaluating SOP software, that page covers the broader process documentation layer.

What should a work instruction include?

The 6 core components

A good work instruction contains exactly what the person doing the task needs. Nothing more, nothing less:

1. Title: the task name, specific enough that there is no ambiguity about which task it covers (“Process a customer refund in Stripe”, not “Refunds”)

2. Purpose: one sentence on why this task matters and why consistency is important

3. Scope: who performs the task, when, and under what conditions

4. Step-by-step instructions: numbered, one action per step, written in plain language and active voice (“Click Save”, not “The Save button should be clicked”)

5. Supporting visuals: screenshots, diagrams, or photos for any step that could be misinterpreted from text alone

6. Version and owner: who owns it and when it was last reviewed, so everyone knows they are reading the current version

How to write work instructions, step by step

The most common mistake is writing from memory rather than observation. Here is how to write a work instruction that actually works.

Step 1: Identify the task (not the process)

A work instruction covers one task, not a whole process. “Handle a customer complaint” is a process. “Log a complaint ticket in Zendesk” is a task. Start with the smallest unit of work that needs to be done correctly and consistently by every person who performs it.

Step 2: Do the task yourself while documenting it

Do not write from memory. Open the system, perform the task, and write down each action as you take it. This is the only reliable way to catch the steps everyone forgets to mention because they have done it a thousand times.

Step 3: Write in plain language, active voice, present tense

Each step starts with a verb and describes one action: “Click the Settings tab”, “Enter the customer order number”, “Select Refund from the dropdown”. Avoid explaining why within the steps themselves; save context for the purpose field at the top.

Step 4: Add screenshots or visuals for complex steps

Any step that requires navigating an unfamiliar interface, making a judgment call, or locating something in a system benefits from a screenshot. For visual work instructions with annotated diagrams or image-led steps, build that format in from the start.

Step 5: Test it with someone unfamiliar with the task

Give the draft to a team member who has not done the task before and watch them follow it without help. Every time they pause, ask a question, or make a wrong assumption is a gap in the instruction. Fix it before you publish.

Step 6: Assign it to a role and set a review date

A work instruction that is not assigned to a role is just a document that might get read. Assign it to every role that performs the task and set a review date: quarterly for fast-changing tasks, annually for stable ones.

Work instruction examples

The format becomes clear when you see it applied to real tasks. Here are four examples across different industries, each with the actual steps shown rather than a description of them.

Example 1: How to process a customer refund (professional services)

Task: Process a refund request for a subscription client

1. Log in to the billing portal and navigate to the client account

2. Confirm the refund amount matches the client email request

3. Click “Issue Refund” and select the original payment method

4. Add a note to the client record: date, amount, and reason

5. Send the confirmation email using the refund template (Templates > Billing > Refund Confirmed)

6. Update the CRM ticket status to “Resolved”

Owner: Accounts team. Review: annually, or when the billing system changes.

Example 2: How to calibrate a measurement tool before inspection (engineering)

Task: Zero-calibrate a digital calliper before a quality inspection

1. Wipe both jaws with a lint-free cloth to remove debris

2. Close the jaws fully and confirm contact is flush, with no visible gap

3. Press and hold the Zero button until the display reads 0.00mm

4. Open and close the jaws twice to verify the reading returns to 0.00mm

5. Record the calibration check in the inspection log: date, tool ID, operator initials

6. If the reading does not return to 0.00mm, remove the tool from use and tag it for maintenance

Owner: QA team. Review: monthly, and whenever a tool is dropped or damaged.

Example 3: How to prepare a treatment room between patients (healthcare)

Task: Turn over a clinical treatment room to infection control standard

1. Don PPE (gloves and apron) before entering the room

2. Remove all disposable items from the previous patient (couch roll, tissue, used supplies)

3. Wipe the treatment couch with disinfectant wipes, head to foot, both sides

4. Wipe all contact surfaces: chair, sink taps, light handle, door handle

5. Replace couch roll and any paper items

6. Dispose of PPE in the clinical waste bin before leaving the room

7. Mark the room as ready on the scheduling system

Owner: Clinical staff. Review: annually, or when infection control protocols are updated.

Example 4: How to complete a job site sign-off checklist (field services)

Task: Complete end-of-job sign-off before leaving a customer site

1. Walk the entire work area and confirm all equipment and tools are removed

2. Check that all access panels and covers are reattached and secured

3. Test the installation or repair by running the system through one full cycle

4. Photograph the completed work and upload to the job record in the field app

5. Obtain the customer signature on the job completion form (digital or paper)

6. Mark the job as complete in the scheduling system before leaving the site

Owner: Field technicians. Review: annually, or when job management software changes.

Standard work instructions: what are they?

“Standard work instructions” is a Lean Manufacturing term, from the Toyota Production System, for the verified, approved sequence for a task. In quality management contexts these are sometimes called QWI (Quality Work Instructions), particularly in regulated industries where the instruction is tied to a quality standard. For most service and ops teams, “standard work instructions” and “work instructions” mean the same thing: the word “standard” signals this is the controlled version, not a draft.

Work instructions for manufacturing teams

Manufacturing teams formalise work instructions for assembly, machine setup, quality checks, and maintenance routines, procedures documented in production environments for decades. Here is a machine pre-start check example:

1. Check the guard is fitted and secured before powering on the machine

2. Confirm the previous operator’s sign-off is logged in the production record

3. Run one full cycle at low speed and observe for abnormal noise or vibration

4. Record the pre-start check in the shift log: date, machine ID, operator name

5. If any check fails, lock out the machine and notify the shift supervisor before continuing

Owner: Production operators. Review: quarterly, or when equipment is modified.

Waybook is used by engineering and production teams to document manufacturing work instructions alongside their SOPs and quality management docs. It is not an AR or connected-worker platform. For teams that need AR-assisted instructions tied to specific machines or IoT sensors, tools like Tulip or VKS are built for that. For teams that need step-by-step task instructions their people can access from any device, assign to roles, and track for completion, Waybook covers manufacturing, engineering, and field service operations.

Frequently asked questions

What is a work instruction in simple terms?

A work instruction is a short, numbered document that tells one person exactly how to do one specific task, step by step, in plain language. It does not explain why the task exists or who owns the process; it tells you what to do and in what order. Think of it as the operator-level “how to”: the document you hand to the person doing the work, not the manager overseeing the process.

What is the difference between a work instruction and a procedure?

A procedure is a broader sequence of activities within a process, often covering multiple tasks or roles. A work instruction is narrower: one task, one role, full step-by-step detail. In the documentation hierarchy, procedures sit between SOPs and work instructions: SOPs define the process, procedures describe the activities within it, work instructions give the operator the exact steps. In smaller businesses the terms are often used interchangeably; at scale, keeping them separate matters.

How long should a work instruction be?

As short as it needs to be. A good work instruction is typically 5–12 numbered steps. If you need more than 12 steps, the task is probably two tasks. Split it. Length is determined by task complexity, not word count. Add a screenshot wherever a step is ambiguous and plain text is not enough.

What is the difference between standard work instructions and regular work instructions?

“Standard work instructions” is a Lean Manufacturing term (Toyota Production System) for the verified, approved task sequence. In quality management contexts the term is common, sometimes called QWI (Quality Work Instructions), where the instruction may be tied to a quality standard or audit requirement. In most service and ops contexts the two terms mean the same thing: “standard” signals it is the approved version, not a draft.

What software do you use to create work instructions?

Teams use everything from Word documents and Notion pages to purpose-built work instruction software. The practical difference is accountability: a Word document gets emailed, saved somewhere, and forgotten. A work instruction in a platform like Waybook is assigned to a role, searchable, version-controlled, and tracked for completion, so you know who has read it and who has not. If your team is still emailing PDFs or pointing people at a shared drive, the problem is not the content of your instructions; it is the system they live in.

Start writing your work instructions in Waybook

When you are ready to build a system with instructions assigned to roles, tracked for completion, and linked to your SOPs and onboarding flows, work instruction software is what makes it stick. Try Waybook free.