GMP work instructions — Arbeitsanweisungen in German, istruzioni di lavoro in Italian — are the documents that turn a procedure into concrete actions: how to clean that machine, how to load that line, how to prepare that reagent. They are often the most-read documents on the shop floor and, at the same time, the most neglected by the documentation system: written in a hurry, photocopied next to the machine, not always aligned with the governing SOP. In this article we look at what EU GMP expects for work instructions, how they differ from SOPs, how to structure a reusable Word template, and which errors show up most often in audits.
GMP work instructions: what EU GMP Chapter 4 says
Chapter 4 of the EU GMP guide (EudraLex Volume 4, "Documentation") distinguishes two primary types of documentation: instruction documents (directions or requirements) and record/report documents. Among instruction documents the chapter lists specifications, manufacturing formulae and processing, packaging and testing instructions, procedures — defined as documents that "give directions for performing certain operations", otherwise known as SOPs — protocols and technical agreements.
A detail that surprises many: Chapter 4 does not define "work instructions" as a standalone document category. The term appears in section 4.4, where the text requires that "Standard Operating Procedures, Work Instructions and Methods" be written in an imperative mandatory style. In other words: the guideline acknowledges that work instructions exist and subjects them to the same style and control rules as SOPs, but leaves the company the freedom — and the responsibility — to define their role and hierarchy within its own quality system. It is the Site Master File, or the "master" SOP on document management, that must state which document levels exist and how they connect.
The same framework applies in the PIC/S PE 009 guide (Part I, Chapter 4), which mirrors the European text, while in the United States 21 CFR 211.100 requires written procedures for production and process control, drafted, reviewed and approved by the appropriate organizational units and approved by the quality control unit, with the obligation to record and justify any deviation.
Work instruction vs SOP: the differences that matter
In day-to-day practice the most useful distinction is one of hierarchy and granularity: the SOP describes the process and the responsibilities, the work instruction describes the execution of a specific task, often tied to a single piece of equipment, workstation or activity. A cleaning SOP defines policy, frequencies, responsibilities and records; the work instruction says, step by step, how to clean granulator GR-01.
| Aspect | SOP | Work instruction |
|---|---|---|
| Subject | Process or system (what, who, when) | Specific task (how, in sequence) |
| Scope | Cross-functional: department or site | Local: machine, workstation, activity |
| Level of detail | Responsibilities, flow, references | Operational steps, parameters, images |
| Audience | All functions involved | The operator performing the task |
| Typical number | Limited and stable | More numerous, updated more often |
| Control requirements | Approval, signature, date, periodic review | Identical: same Chapter 4 rules |
Beware of the most common misconception: "simpler document" does not mean "less controlled document". Section 4.3 of Chapter 4 requires every instruction document to be approved, signed and dated by authorised persons, to have unambiguous contents, to be uniquely identifiable and to have a defined effective date. A work instruction taped to the machine without a revision number is, for all practical purposes, an uncontrolled document.
Topics like this one — documentation, data integrity, audit readiness — are the bread and butter of The Pragmatic GMP, GuideGxP's free weekly newsletter: one GMP topic every week, explained in operational terms, straight to your inbox. Subscribe here.
How to write an effective work instruction
Section 4.4 sets the golden rule of style: imperative and prescriptive. Not "the operator should verify the pressure", but "verify that the pressure is between 2.0 and 2.5 bar". A few practical criteria that hold up well in audits:
- One step, one action. Each numbered step contains a single verifiable action; if you need two verbs, you need two steps.
- Explicit parameters. Values, ranges and units of measure in the text of the step, not deferred "to the specification": the operator must not need to open a second document to execute.
- The operator's language. Section 4.4 requires style and language to fit the intended use: short sentences, no unexplained acronyms, photos or diagrams wherever a verbal description would be ambiguous.
- Clear recording points. Where the operator must sign or record a value, the instruction says so explicitly and names the form or system to use.
- Consistency with the parent SOP. Every instruction cites the SOP it derives from; when the SOP changes, the impact assessment must reach the child instructions too.
Remember section 4.5 as well: documents must be regularly reviewed and kept up to date. A sound system gives work instructions the same periodic review cycle as SOPs, with extra attention to the copies distributed on the shop floor: reproducing working documents from the master must not introduce errors (section 4.2), and obsolete copies must be withdrawn in a traceable way.
Word template: the structure
A well-built Word template makes every instruction on site consistent and cuts drafting time in half. The sections that should not be missing:
- Controlled header: logo, title, unique identification code, revision number, effective date, page X of Y.
- Purpose and scope: which activity, equipment or area it applies to, and what stays out.
- References: parent SOP, specifications, equipment manuals.
- Materials and prerequisites: PPE, tools, required equipment status, preliminary checks (e.g. line clearance).
- Numbered operating sequence: the steps in imperative style, with parameters, tolerances and recording points highlighted.
- Handling of anomalies: what to do when a step fails (who to notify, when to open a deviation).
- Signature block: prepared by, reviewed by, approved by — with dates.
- Revision history: number, date and reason for every change.
A note on context: Chapter 4 is under revision. In July 2025 the European Commission, EMA and PIC/S opened a joint targeted consultation on the draft of the new Chapter 4 (together with Annex 11), with a much more explicit focus on electronic documentation and data governance. Anyone building a work instruction system today does well to design it digital-first: electronic masters, controlled distribution, compliant electronic signatures.
The most frequent audit findings
- "Ghost" instructions on the shop floor: versions printed years earlier, never withdrawn, different from the current master.
- Instructions that contradict the parent SOP because they were updated at different times, without a cross-impact assessment.
- Descriptive instead of imperative style: section 4.4 is among the most cited references in documentation findings.
- Steps the operator cannot execute as written — and therefore performs "from memory", opening a gap between the written and the done that every inspector knows how to spot.
- No documented training on the latest revision: the instruction changes, the training record does not.
GuideGxP recommendation
Treat work instructions as first-class citizens of the documentation system: same approval, same periodic review, same copy control as SOPs. Before writing a new one, watch the operator perform the task and write the steps as they are actually performed (when correct): an instruction born at a desk is immediately recognisable, on the shop floor as in an audit. And measure the quality of the result with a simple test: a trained person who is new to that workstation must be able to perform the task without asking anyone anything.
If you want to start from documents that are already structured and defensible in audits, browse our catalogue of ready-to-use GxP manuals, templates and checklists: operational tools built for QA, QC and manufacturing.
