How to Write Work Instructions (With an Example and a Free Template)

To write work instructions, pick one task with a clear finish line, watch or record your best operator doing it, and break it into steps, key points, and reasons. Write each step as one verb-first action with its expected result, put safety and quality checks exactly where they apply, add a visual per step, and test the draft on someone who has never done the task.

Below: each step in detail, a copy-paste work instruction template, and a filled-in example.

What a Work Instruction Is (and Is Not)

A work instruction tells one person how to complete one task, in order, to a defined standard. It sits below an SOP. The SOP says what a process is, who owns it, and when it runs. The work instruction says which button to press, which torque to set, and what the finished part should look like.

If you are unsure which document you need, our breakdown of SOP vs work instruction vs process doc covers the decision. The short version: if the reader is standing at the task right now, they need a work instruction.

Why Most Work Instructions Get Ignored

They rarely fail because the writer did not know the job. They fail for three reasons:

• They were written from memory. Experienced people skip steps they no longer notice doing. The check they make by feel, the part they always wipe first, the sound that tells them it is seated: none of it makes it onto the page.
• They explain instead of instruct. Paragraphs of background push the actual action out of sight. A reader holding a tool will not read a paragraph.
• They go stale silently. The line changes, the software updates, and nobody knows which documents are now wrong.

How to Write Work Instructions in 7 Steps

1. Scope one task with one finish line

A work instruction covers a single task that one person can finish in one session. "Operate the packing station" is too broad. "Seal and label an outbound carton" is right.

Write the finish line before anything else: the observable state that means the task is done. "Carton sealed, label scanned, placed on outbound conveyor" is a finish line. "Carton is ready" is not.

If the task has more than about 12 to 15 steps, split it into two instructions and link them.

2. Watch or record your best operator before anyone writes

This is the step most guides reduce to "consult experienced employees", and it is where most of the quality comes from.

Asking an expert to describe a task gets you their mental summary. Watching them do it gets you the task. The gap between the two is exactly the tacit knowledge a new hire needs: the extra check, the order that avoids rework, the moment they pause to look at something.

Record the expert doing the task at normal speed, and ask them to say out loud what they are checking as they go. A phone on a stand is enough for a physical task. For software, a screen recording with narration does the same job. The recording becomes your source of truth, so you write from what happened instead of from what anyone remembers.

3. Break it into steps, key points, and reasons

Use the job breakdown from the Training Within Industry (TWI) Job Instruction method, which manufacturers have used since the 1940s because it works. Replay the recording and fill three columns:

A key point is anything that makes or breaks the job, could injure the worker, or makes the work easier (the "knack"). If a step has no key point, it is probably obvious enough to merge with its neighbor.

The reason column is what most templates leave out, and it is what makes people follow the instruction when nobody is watching. An operator who knows why the tape extends up the sides stops cutting it short.

4. Write each step as one action with an expected result

Turn each row into a numbered step:

• Start with a verb. "Place", "Scan", "Tighten", "Click". Not "The carton should be placed".
• One action per step. If a step contains "and then", split it.
• Say where before what. "On the scanner screen, press Confirm" reads faster than "Press Confirm on the scanner screen" when the reader is looking for the location first.
• State the expected result. "The scanner beeps once and the screen turns green." This lets the reader self-check without asking anyone.
• Use exact names. Match the label on the machine or the button text in the software, character for character.

The craft rules here overlap with any instruction writing. Our guide on how to write step-by-step instructions people actually follow goes deeper on wording, including a before-and-after rewrite.

5. Put safety, quality checks, and stop conditions where they happen

Do not collect warnings in a box at the top where they are read once and forgotten. Place each one immediately before the step it applies to.

Three kinds of callout are worth distinguishing visually:

• Safety (risk to the person): "CAUTION: Keep fingers clear of the tape head blade."
• Quality check (risk to the output): "CHECK: Label barcode is flat and fully readable."
• Stop condition (when not to continue): "STOP if the carton weight differs from the order by more than 0.5 kg. Call the lead."

Stop conditions are the most underused of the three, and they turn an instruction from a script into a decision aid.

6. Add one visual per step that shows "right"

A photo or screenshot per step does more than any adjective. The best visual shows the finished state of that step, not the action in progress, because that is what the operator compares against.

Pull frames straight from your step 2 recording so the visuals match reality. Mark them up with arrows, circles, and numbered callouts. A free tool like Vidocu's image annotator handles this in the browser. Where a wrong state is common, show it next to the right one.

Visual-first instructions also reduce the translation burden on multilingual teams. It is the core idea behind standard work: make the correct method visible so it can be copied.

7. Test it on a first-timer, then put it under version control

Hand the draft to someone who has never done the task and watch them follow it without help. Every time they hesitate, ask a question, or do something unexpected, the document is wrong, not the person. Fix it and test again.

Then give the instruction a document number, a revision, an owner, and an approval date. If you work to ISO 9001 or a similar standard, work instructions are controlled documented information, so this is required, not optional. Even if you do not, a revision number is the only way an operator can tell whether the printout on the wall is current.

Work Instruction Template

Copy this into your document tool and fill it in. Every field earns its place; delete a section only if it genuinely does not apply.

WORK INSTRUCTION

Document no.:        WI-[AREA]-[###]
Title:               [Verb + object, e.g. "Seal and label an outbound carton"]
Revision:            [A / 1.0]        Effective date: [YYYY-MM-DD]
Owner:               [Role, not person]
Approved by:         [Role]           Related SOP: [SOP no.]

PURPOSE
[One sentence: what this task produces and why it matters.]

SCOPE
Applies to: [station / product / system]
Does not cover: [adjacent tasks, with links to their instructions]

BEFORE YOU START
Tools & materials:   [list]
PPE:                 [list, or "None"]
Prerequisites:       [training, system access, machine state]

STEPS
#  | Action (verb first)        | Key point               | Reason            | Visual
1  | [Action]                   | [How to do it right]    | [Why]             | [Img 1]
   | Expected result: [what the reader should see]
   | CAUTION / CHECK / STOP: [only if it applies to this step]
2  | ...

FINISH LINE
[Observable state that means the task is complete.]

IF SOMETHING GOES WRONG
[Symptom] -> [What to do] -> [Who to call]

REVISION HISTORY
Rev | Date | Change | By

Work Instruction Example: Seal and Label an Outbound Carton

Here is the template filled in for a simple packing-station task. The values are illustrative, so replace them with your own specs.

Document no.:  WI-PK-014          Revision: C     Effective: 2026-09-16
Title:         Seal and label an outbound carton
Owner:         Packing Team Lead  Related SOP: SOP-WH-003 Outbound Shipping

PURPOSE  Ship cartons that arrive intact with a scannable label.
SCOPE    Packing stations 1-6. Pallet wrapping is covered in WI-PK-015.
BEFORE YOU START  Tape gun (48 mm), label printer, handheld scanner, scale.
                  PPE: cut-resistant gloves.

1. Fold the bottom flaps: short flaps first, then long flaps.
   Key point: long flaps on top. Reason: keeps the tape seam flat.
   Expected result: flaps meet in the center with no gap.

2. Tape the bottom seam in one pass, extending 5 cm up each side.
   CAUTION: keep fingers clear of the tape head blade.
   Reason: short tabs peel off in transit.

3. Place the order items and void fill. Close the top flaps the same way.
   CHECK: nothing moves when you tilt the carton 45 degrees.

4. Weigh the carton on the station scale.
   STOP if the weight differs from the order by more than 0.5 kg.
   Call the Packing Team Lead.

5. Tape the top seam as in step 2.

6. On the label printer screen, select the order and press Print.
   Expected result: one label prints with the order number at the top.

7. Apply the label flat on the largest side, 5 cm from any edge or seam.
   CHECK: barcode is flat, unwrinkled, and not over tape.

8. Scan the label with the handheld scanner.
   Expected result: one beep and a green screen. A red screen means reprint.

FINISH LINE  Carton sealed, label scanned green, placed on outbound conveyor.

Note what it leaves out: background paragraphs, warnings grouped at the top, and steps that combine two actions.

Writing Work Instructions for Software Tasks

Everything above applies to on-screen work too, with two differences. The visual per step is a screenshot rather than a photo, and interfaces change far more often than physical stations do, so staleness is the bigger risk.

The fastest route for software tasks is to skip hand-capturing screenshots entirely. Record the task once, and generate the steps and screenshots from the recording. We cover the manual and automated versions of that workflow in how to turn a screen recording into a step-by-step guide with screenshots.

Draft Work Instructions From a Recording With Vidocu

Step 2 is the most valuable step and the most skipped, because turning a recording into a written instruction by hand is slow. Vidocu automates that conversion.

Upload a recording and Vidocu transcribes it, identifies the steps, and writes a step-by-step article with a screenshot pulled from the video at each major transition. You edit that draft into your template instead of starting from a blank page. For software workflows, Vidocu's AI Recorder goes one step further: you describe the task and an agent performs and records it, so nobody has to sit through the capture.

Be clear about where it fits. Vidocu is built around screen recordings, so software work instructions come out closest to finished. It will draft steps and extract frames from any video you upload, but on footage of a physical task expect to do more rewriting, especially of key points the camera cannot see. It is also an authoring tool, not a shop-floor execution system: there is no machine integration, no work-order routing, and no offline tablet mode. If you need those, our comparison of digital work instructions software covers the execution platforms honestly.

Two more pieces help once the instruction exists:

• Translation. Multilingual crews can get the same instruction, narration, and subtitles in 70+ languages through video translation, instead of maintaining a separate document per language.
• Proof of training. Vidocu's Training Center generates a knowledge check from the instruction, grades it, supports trainer sign-off, and can expire a qualification after a set number of days so people retrain on schedule. Training quizzes and scoring are included on Pro ($39/month).

Keep Work Instructions Current

An accurate instruction that goes stale is worse than none, because people trust it. Tie revisions to events, not to the calendar:

• Equipment, tooling, or material change on the station
• Software release that touches any screen in the instruction
• A defect or incident traced back to the task
• A first-timer test fails during onboarding
• An operator workaround you see repeated more than once (the instruction is wrong, or the workaround is better)

Assign one owner per instruction, by role, and review anything untouched for 12 months. If a task keeps changing, keep the recording as the master and regenerate the written steps from a fresh capture rather than patching the old text line by line.

FAQ

How long should a work instruction be?

Long enough to complete the task without asking anyone, and short enough to follow at the station. Most good work instructions have 5 to 15 steps and fit on one or two pages. If yours runs longer, it is usually covering more than one task and should be split.

Who should write work instructions?

The people who do the work should supply the content, and someone with writing and document-control skills should shape it. The most reliable approach is to record your best operator doing the task, draft from that recording, and have the operator review the draft for accuracy before a first-timer tests it.

What is the best format for work instructions?

A numbered sequence of verb-first steps, each with its key point, reason, expected result, and one visual, wrapped in a header with document number, revision, owner, and scope. Tables work well on paper and screens; video with written steps works best when the task involves motion or feel that a still image cannot show.

What is the difference between a work instruction and an SOP?

An SOP describes a whole process: its purpose, owners, and the sequence of activities. A work instruction zooms into one task inside that process and tells a single person exactly how to perform it. One SOP typically links to several work instructions.

Do work instructions need document control?

If you operate under ISO 9001, ISO 13485, or a similar quality system, yes: work instructions are controlled documented information and need a number, revision, approval, and change history. Even without a certification, revision control is the only way an operator can tell whether the instruction they are holding is current.

Write It From What Actually Happens

The difference between a work instruction people follow and one they ignore is almost always the source. Instructions written from memory miss the knacks; instructions written from a recording of the task capture them. Scope tightly, record first, write steps with key points and reasons, test on a first-timer, and revise on real events.

If you want to go from recording to draft in minutes instead of hours, try Vidocu for free.