Work Instruction Template: Structure, Example and Writing Rules

Search for a work instruction template and you usually find two things: safety forms from the employers' liability insurance associations, which are actually hazard notices, and QM templates with twelve header fields of which your company needs three. Neither helps much when all you really want is for the new colleague at goods receiving to know tomorrow morning what to do with a delivery that has no test certificate.

This guide gives you the template as a copyable outline right here in the text, a filled-in example from a metal fabrication shop, and the rules for writing work instructions that people actually open in daily work. It also explains why most work instructions fail not on their structure, but on their upkeep.

What is a work instruction?

A work instruction (WI) describes a single task at a single workstation precisely enough that a trained employee can perform it without asking anyone. It is the bottom level of documentation: above it sits the standard operating procedure, which governs a workflow across several roles, and above that the process as a whole. How those levels fit together, and where to start when building up your process documentation, is a topic of its own.

Typical work instructions in a mid-sized company: setting up a particular machine, the visual inspection of an assembly, creating a new customer in the ERP, approving an incoming invoice, packing a product for export. What they have in common is one workstation, one role, one clearly bounded result.

A work instruction is binding. It is not a recommendation and not a substitute for training; it is the definition of how the task is performed in this company. Anyone deviating from it needs a reason - and the instruction should say who decides on that reason.

Work instruction, SOP, safety instruction: the difference

Three terms that get mixed up constantly. The confusion is not harmless, because one of the three documents is required by law.

The SOP governs the workflow: that a delivery gets inspected, who decides in case of a deviation, and where blocked goods go. The work instruction governs the hands-on task: which gauge is used, which fields are filled in the ERP, and how you recognize that the inspection has passed. How to build the level above cleanly is shown in the guide on writing standard operating procedures.

The safety instruction is a different document from a different world. It comes out of occupational safety, is legally required for hazardous substances and dangerous machinery, follows a fixed structure (scope, hazards, protective measures, conduct in case of malfunction and accident, disposal) and is posted at the workstation in a color-coded format. If your search for a work instruction template turns up DGUV or trade association forms, you are usually looking at a safety instruction. The two can reference each other - the work instruction for setting up the press brake points to the safety instruction for the press brake - but they do not replace each other.

The template: structure of a work instruction

There is no prescribed structure. The following outline has proven itself equally well in production, administration and services. Copy it into your document and delete what you do not need - six filled-in fields beat twelve empty ones. If you find that your topic touches several roles and handovers, a process description template is the better format.

WORK INSTRUCTION

Header
  Document number:     WI-<area>-<sequential no.>
  Title:               <task in two to five words>
  Workstation/role:    <where and by whom it is performed>
  Version:             <no.>   As of: <date>
  Written by:          <role>   Approved by: <role>
  Next review:         <date>

1. Purpose
   What is meant to be achieved? One sentence.

2. Scope
   Which cases does this cover, and which does it explicitly not cover?

3. Prerequisites and equipment
   Tools, gauges, systems, access rights, forms, protective equipment.
   Reference to the safety instruction, if one exists.

4. Work steps
   No. | Step (one action per line) | Check (how do I know it is right?)

5. Special cases and deviations
   If <situation>, then <action>. Who decides when it is unclear?

6. Records and filing
   What gets documented where (test report, ERP posting, signature)?

7. Related documents
   SOP, inspection plan, drawing, safety instruction - with numbers.

Change history
   Version | Date | What changed | Who

A few fields cause trouble in practice. The purpose is not "description of the incoming goods inspection", it is "Every delivery is checked for identity, quantity and visible damage before storage and posted as inspected in the ERP." Phrase the purpose as a result and you immediately see whether the steps below actually deliver it.

The scope mainly needs the exclusion. "Does not apply to customer-supplied parts and returns" saves more questions than any list of inclusions. The equipment section is where the new colleague gets stuck before she even starts: if step 6 requires an ERP account with rights to post inspections, that belongs here - not in an onboarding email.

The check per step is the field most templates lack and the one that makes the difference. Without it, the person doing the work knows what to do but not whether she did it right. "Compare the delivery note against the order" is a step. "Part number, quantity and order number match; if they deviate, go to special case 5.2" is a step with a check.

Example: work instruction for incoming goods inspection in metal fabrication

Here is the template filled in. The company: a metal fabrication business with 60 employees, buying steel sections, sheet metal and bought-in parts for stairs, railings and structural steel assemblies. Goods receiving is staffed alternately by two warehouse operators. The instruction was written after the more experienced of the two, Mr. Aydin, was out for three weeks, and in that time two deliveries without a 3.1 mill certificate went into production.

Header: WI-WHS-03, incoming goods inspection for steel and bought-in parts. Workstation: goods receiving, hall 1; role: warehouse operator. Version 2, as of 2026-09-08. Written by: warehouse supervisor. Approved by: Head of QA. Next review: 2027-09-08.

Purpose: Every delivered item is checked for identity, quantity, visible damage and completeness of certificates before storage, posted as inspected in the ERP and given an inspection label.

Scope: All deliveries of steel sections, sheet metal, fasteners and bought-in parts to hall 1. Does not apply to customer-supplied parts (WI-WHS-05) or returns from the galvanizing plant (WI-WHS-07).

Prerequisites and equipment: ERP account with the "goods receiving" role, handheld scanner, tape measure, 150 mm caliper, green and red inspection labels, quarantine area (red-marked floor space next to gate 2), safety shoes and gloves per safety instruction SI-WHS-01 (handling steel sections).

Work steps:

Special cases: 5.1 No open order: refuse acceptance unless purchasing confirms by phone. 5.2 Deviation in quantity, dimension or measurement: red label on the item, move it to the quarantine area, report to purchasing and QA via the ERP transaction "goods receipt deviation", no partial posting. 5.3 Certificate missing: the material may be stored but not released to production. Set inspection status to "certificate pending", purchasing follows up. After five working days without a certificate, the Head of QA decides.

Records and filing: ERP posting with inspection status, certificate scanned onto the goods receipt document, damage photos in the transaction. Original delivery note to the purchasing file.

Related documents: SOP-QA-02 goods receipt and supplier evaluation, inspection plan IP-WHS-01, safety instruction SI-WHS-01.

What is notable about this example is less the structure than what version 1 was missing: special case 5.3. That material without a certificate may be stored but not produced with was something Mr. Aydin had handled that way for years - it was written down nowhere. His stand-in did not know the rule and posted the goods straight through.

Writing rules for work instructions that get read

The template is the easy part. Whether a work instruction works is decided when you write the steps.

One action per line. "Check the delivery note and post the goods" is two steps with two checks. Merge them and you lose the moment where the person pauses and verifies. Rule of thumb: if a step contains an "and", it is probably two.

Active voice with a clear subject. "The warehouse operator posts the goods receipt" instead of "The goods receipt is to be posted." The passive is widespread in QM documents because it sounds neutral - and that is exactly why it gets skimmed over. An instruction addresses the person carrying it out.

Images instead of prose. A photo of the red quarantine area says more than "in the designated area". A screenshot of the ERP screen with the field highlighted saves two sentences of click-by-click description that will be wrong after the next update. For machine setup, assembly and visual inspection, annotated photos are often the actual instruction; the text is the caption.

A check for every step. Each line answers the question: how do I know this step was done correctly? It is tedious to write and it is the only place where the instruction beats watching someone do the job.

Special cases visible, not in an appendix. The normal case needs little guidance; a skilled worker knows it after a week. The instruction gets opened when something is different. So the if-then cases belong prominently in the document, cross-referenced from the step they apply to.

Roles, not names. "The Head of QA decides", not "Ms. Lindner decides". Names change, roles stay - and a document with names in it becomes quietly wrong the first time someone moves on.

Short. One to three pages. If it grows beyond that, you have usually mixed two tasks together or let in questions of sequence and responsibility that belong at SOP level.

And one test that costs ten minutes: give the draft to someone who has never done the task and have them talk through it out loud. Wherever they hesitate, a check or a piece of equipment is missing.

Digital work instructions: what changes and what does not

"Digital work instructions" is the label for tools that show instructions as a step-by-step view on a tablet or terminal at the workstation, with photos, videos, sign-off per step and versioning in the background. For production and assembly with many variants, that is a genuine step forward: the assembler sees exactly the variant being built, confirms every step, and the company has the record without paper.

What does not change is the content. A digital work instruction with seven unclear steps is an unclear work instruction on a tablet. The outline above, the checks and the special cases stay the same whether the document lives as a PDF in a folder, a page in a wiki or a step sequence on a terminal. For most companies between 10 and 500 employees, a well-kept wiki or a document folder with clear versioning is the right starting point; the specialist software pays off once you need per-step sign-off and variant control.

What digital tools do reliably solve is a distribution problem: the current version is the one on screen. The printout taped to the machine, still showing the tolerance from two years ago, disappears.

The maintenance part: why work instructions go stale

Work instructions go stale faster than any other QM document because they sit closest to the work. An SOP survives an ERP migration with two edits; the work instruction with screenshots of the old screens is completely wrong on the day of the switch. A new gauge, a supplier who now sends certificates digitally, a replaced label printer - each of these small things makes a step unusable.

The real reason for going stale, though, is not the pace of change. It is the direction knowledge flows in. The instruction is written by the warehouse supervisor or by QM, from memory or after a walkthrough. The people doing the work read it once during onboarding and then develop their own, usually better practice: they know that the supplier Hübner always mails the certificates the following day, that sheets over 3,000 mm do not fit on the scale, that the scanner only reads the new labels from a distance. None of that flows back into the document, because nobody asks the people doing the work - and because those people never suspect their shortcuts are worth documenting.

Three measures help. A fixed trigger for review: every change to a system, gauge, supplier or workstation prompts a look at the document. A review date with a responsible role in the header block. And regular short conversations with the people who perform the task. Not "Is the instruction still current?" but "What did you do differently last time from what it says here?"

The third measure is where wissa.ai comes in. An AI interviews the employees who do the work - 15 to 20 minutes per person, by chat or voice, no workshop needed. When the warehouse operator names his stand-in or purchasing as being involved, they get invited next; the system works its way from one knowledge holder to the next. Out of that comes the raw draft of the work instruction: steps, equipment, special cases, every statement with a source reference. If one operator says material without a certificate gets blocked and the other says it gets stored, contradiction detection flags exactly that spot instead of smoothing it over. After each further conversation the documentation updates and shows the diff against the previous version. The editorial final version, the checks and the approval stay with you - but the question "How is it really done?" is answered before you start writing.

If you would rather write work instructions from what the people doing the job actually say than from memory: wissa.ai delivers the raw draft from AI interviews, GDPR-compliant with EU hosting, voluntary participation, no performance assessment. The first 3 interviews are free; after that, 12 interview credits cost 149 euros net, and interviewed employees remain free of charge. Register for free

Conclusion

A good work instruction has a purpose phrased as a result, a scope with exclusions, the equipment listed before the first step, one action per line with a check, and the special cases where they occur. The template above covers that; the example shows what it looks like filled in. Do not confuse it with the safety instruction, which comes from occupational safety law and is mandatory, or with the SOP, which governs a workflow across roles. And expect the instruction to go stale: the only protection is the people who do the task, and the question of what they do differently from what is written.

FAQ

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

The standard operating procedure describes a workflow across several roles: who does what in what order and who decides. The work instruction describes a single task at one workstation in detail: hand movements, system steps, checks. The SOP says that goods are inspected and blocked when they deviate; the work instruction says what they are inspected with and how the block is executed.

Is a work instruction required by law?

No. Work instructions are a company decision; ISO 9001 requires documented information only where it is necessary for the effectiveness of the system. Do not confuse them with the safety instruction from occupational safety law, which is mandatory for hazardous substances and dangerous work equipment under GefStoffV and BetrSichV and has to be posted at the workstation.

How long should a work instruction be?

One to three pages - more pages are fine if they carry images and less text. If the document gets substantially longer, you have usually mixed two tasks or let in questions of sequence and responsibility that belong in the SOP. An instruction that cannot be skimmed in five minutes never gets opened in daily work.

Who writes the work instruction?

Formally the area manager or QM, approved by the process owner. The content has to come from the people doing the work, because only they know the special cases and the actual practice. A proven division of roles: the practitioners supply the steps and exceptions, for example via interviews or tools like wissa.ai, QM structures the document and adds the checks, the area manager approves it.

How often does a work instruction need to be updated?

Event-driven on every change to a system, gauge, supplier or workstation, plus a fixed review date, usually annual, with a responsible role in the header block. Work instructions go stale faster than SOPs because they sit closer to the work. The most reliable early indicator is asking the people doing the job what they do differently from what is written.