Background

Documentation Standards for Industrial Automation: 82079-1 vs 26514

David Watson

Published:

When a compliance officer or documentation manager working with industrial automation documentation faces an audit, the question is rarely "did we follow a standard?" — it is "which standard actually applies, and how do we pass the audit successfully?". There's no single document that answers this. Two standards sit at the heart of it, and mixing them up is one of the most common reasons audits go badly for machinery documentation.

Machinery Documentation Standards vs Software Documentation Requirements

IEC/IEEE 82079-1:2019 is the horizontal standard for preparation of information for use (instructions for use) of products. It covers products of all kinds, "ranging from a tin of paint to large or highly complex products, such as large industrial machinery, turnkey based plants or buildings". This is the baseline for machinery documentation standards in the EU and US, and the reference point for technical writing for manufacturing across both markets.

ISO/IEC/IEEE 26514:2022 is the vertical standard for design and development of information for users of software, and it is one of the core software user documentation standards. It is explicitly a supplement to 82079-1, and it normatively refers only to the 82079 standard. The scope is software, not hardware.

This distinction is important because industrial automation products contain both: a physical machine and a software interface that controls them. One standard governs the machine. The other governs the interface — and with it, the software information architecture for industrial automation.

IEC/IEEE 82079-1 vs ISO/IEC/IEEE 26514: User Manual Compliance

Parameter IEC/IEEE 82079-1:2019 ISO/IEC/IEEE 26514:2022
Who it is for Manufacturers of all technical products Information architects and developers of software documentation
What it covers All types of instructions for use Information for users of software
Scope Horizontal: all products, from simple to complex systems Vertical: software documentation specifically
Relationship Baseline standard Supplement to 82079-1
Process coverage Complete information management lifecycle Design and development throughout software lifecycle
Regulatory trigger EU Machinery Regulation 2023/1230, product liability directives Software validation, usability engineering requirements

Find the standard that applies to your content

Pick the type of content you are documenting, and this widget tells you which standard governs it — IEC/IEEE 82079-1 for the machine, ISO/IEC/IEEE 26514 for the software interface — and why the distinction matters for audit and EU market access.

Choose an option above to see the applicable standard.


The most consequential difference is regulatory. IEC/IEEE 82079-1 is the standard referenced by EU Machinery Regulation 2023/1230, which mandates that instructions for use be provided in a language easily understood by users and be "clear, comprehensible and legible". This is not optional. It is a legal requirement for placing machinery on the EU market — the foundation of user manual compliance industrial machinery. ISO/IEC/IEEE 26514 has no equivalent regulatory mandate. It is a process standard, not a compliance trigger.

Technical Writing for Manufacturing: Two Failure Modes

Consider two failure modes that occur in industrial automation documentation in order to see how these standards diverge in practice.

Failure mode 1: The ambiguous safety instruction. A manual for a CNC machining center contains the instruction: "Before operation, verify that the spindle is in a safe condition." An auditor reviewing against IEC/IEEE 82079-1 finds a defect of completeness. The standard requires information for use to be verifiable — meaning the user must be able to determine objectively whether a condition is met. "Safe condition" has no measurable criteria. The corrected version might read: "Verify that the spindle speed indicator reads 0 RPM and that the emergency stop button is not engaged." This is a hardware safety issue, governed by 82079-1.

Failure mode 2: The orphaned interface element. A software control panel for a conveyor system includes a parameter labeled "Speed (m/min)" with no documented valid range. An engineer entering 500 m/min — far beyond the mechanical limit — causes a belt failure. Reviewing against ISO/IEC/IEEE 26514 reveals a defect of design: the standard requires that information for users of software be integrated with the user interface and that valid ranges be specified. This is a software documentation issue, governed by 26514.

Which standard is violated?

Read each instruction or documentation defect and pick the standard that governs it. Five cases, both standards, and the reasoning behind each answer.

Case 1
“Before operation, verify that the spindle is in a safe condition.”
Case 2
“Speed (m/min)” — parameter with no documented valid range.
Case 3
Maintenance manual omits the lockout/tagout procedure for servicing the hydraulic press.
Case 4
Diagnostic screen shows an error code with no description and no link to help content.
Case 5
Software help describes features by product version, not by user task, and mixes concepts with procedures in one topic.

The distinction is not academic. In the first case, the failure is in the machine documentation. In the second, it is in the software documentation. A single product may require both standards, applied to different parts of the information set — a daily reality for technical writing for manufacturing.

Functional Safety, Risk, and Industrial Automation Documentation

IEC/IEEE 82079-1 and ISO/IEC/IEEE 26514 deal with the information products themselves. But industrial automation documentation rarely sits on its own. Tech writers end up having to fit their instructions into broader functional safety frameworks — things like IEC 61508, which covers functional safety of electrical, electronic, and programmable electronic safety-related systems in general, or ISO 13849, which deals with control systems and machinery safety.

Then there's software safety and risk management. IEC 62304 covers software life cycle processes for medical devices, and it's often held up as the benchmark for rigorous software risk management. It reminds you that user documentation and safety-related software anomalies are tightly linked. Bring those hazard-analysis principles into your documentation workflow, and you get warnings, residual risks, and software limitations that are both accurate and defensible if someone challenges them.

How to Pass a Machinery Documentation Audit

1. Map your documentation to the appropriate standard. Instructions for installation, operation, maintenance, and service of the physical machine fall under IEC/IEEE 82079-1. Instructions for using the software interface — configuration screens, parameter settings, and diagnostic tools — fall under ISO/IEC/IEEE 26514. Do not apply one standard to both domains.

2. Use 82079-1 as baseline to ensure access to EU marketplaces. The EU Machinery Regulation 2023/1230 (Annex I, 1.5.2) requires that instructions for use be provided in the official language(s) of the member state where the machine is placed on the market. The same regulation further requires that digital instructions be available online for at least a period of ten years since market introduction. These are not best practices, but rather legal requirements.

3. Use 26514 to close the software documentation gap. Apply 26514 to bridge the software documentation gap. 82079-1 covers products generally, but it does not specifically address the challenges of software user documentation standards: modular information architecture, topic-oriented content, information typing (concept, task, reference), and integrating help into the user interface where 26514 is applied.

4. Prepare for the 26513 revision. ISO/IEC/IEEE 26513:2017, covering the principles of testing and reviewing of information for users, is currently being revised. The Draft International Standard (DIS) was registered in 2025 and is in the enquiry phase as of early 2026. If your documentation process relies on the 2017 edition of this standard for your review criteria, start preparing for the revision now.

Which standard covers this content?

Six items from a typical industrial automation documentation set. Assign each one to the correct standard. Your score appears at the end.

Installation instructions for the physical machine
Configuration screen with a parameter valid range
Residual risk statement for a hydraulic press
In-app tooltip explaining an error code
Lockout/tagout procedure for servicing
Topic-oriented help with concept, task, and reference types

Machinery Documentation Standards and Software Information Architecture

IEC/IEEE 82079-1 and ISO/IEC/IEEE 26514 are not competing machinery documentation standards. One governs the machine. The other governs the software. For industrial automation products, both apply — but to different parts of the documentation set.

Get the mapping wrong and the consequences are concrete. Under EU Machinery Regulation 2023/1230, an instruction that fails the verifiability requirement of 82079-1 is a defect in the machine documentation and a barrier to market access. A software parameter left undocumented under 26514 is a defect in the software information architecture for industrial automation — one that surfaces as an operational failure, not a paperwork gap.

The guidance for compliance officers and documentation managers is threefold. To start with, all content should be separated into the machine-facing and software-facing categories based on the assigned standard. Further, 82079-1 should be considered as the legal requirement for EU market introduction, while 26514 is the standard that covers the software documentation aspect. Third, monitor the 26513 revision, since review criteria for user manual compliance industrial machinery and software documentation alike are about to change.

Confusing the two standards is not just a technical error. In the EU, it is a compliance risk. In the field, it is a safety risk. In an audit, it is the finding that writes itself.


See also