What complex industries can learn from nuclear power plant documentation

Nuclear plants manage thousands of procedures across hundreds of people, under conditions where errors can be catastrophic. Over decades, they have developed a documentation discipline that works because it has to. Most manufacturers have no system behind their documentation, which means quality depends entirely on who happens to be writing it. When writers change, the dossier drifts. When an incident hits, the paper does not hold up.

The nuclear sector offers a template. Not because every company needs a safety case for a reactor, but because the principles nuclear operators use to keep documentation reliable apply directly to any industry with complex products, diverse user skill levels, and a high cost of error.

1. Write for the least experienced qualified user, not the author

Nuclear operating procedures are written on the assumption that the person using them may not be the person who wrote them, and may not have the same depth of knowledge. The IAEA's guidance on procedure development makes this explicit: procedures must be readable at the level of the qualified user who will apply them, not at the level of the specialist who drafted them.

The same principle runs through IEC/IEEE 82079-1, the international standard for instructions for use. Information must be designed for the target audience, whether unskilled consumer or trained professional, and the onus is on the writer to match that level.

Most industrial documentation fails this test. Authors write for themselves and for reviewers who share their knowledge. The operator on the floor is an afterthought.

2. Separate the "why" from the "what"

A well-written nuclear procedure does not mix technical justification with operational steps. Background, design intent, and regulatory context belong in one place; the instructions an operator follows belong in another. This distinction keeps the action steps short and unambiguous, and it allows the "why" content to be maintained independently of day-to-day procedural updates.

In most manuals, rationale is bolted into the steps themselves. This dilutes the action, increases cognitive load, and makes revisions harder than they need to be.

3. Not everything needs a procedure: know the difference

Nuclear operators classify tasks. Routine, high-consequence, skill-of-the-craft, and infrequent activities each get different documentation treatment. Some are procedure-controlled, some are guideline-controlled, some require only a checklist, and some are deliberately left to operator judgement.

Most manufacturers either over-document (every task becomes a twenty-step procedure) or under-document (everything is tribal knowledge). Both fail. The nuclear discipline is to decide, deliberately, what kind of document each task needs before anyone starts writing.

4. Classify how a document is to be used, not just what it contains

Nuclear plants distinguish administrative procedures, operating procedures, alarm response, abnormal and emergency procedures, and maintenance procedures. Each class has a defined purpose, format, and review cadence. A writer knows, before they start, which class they are working in and what rules apply.

In industry, the word "manual" often covers everything from marketing content to emergency response. Without classification, documents get written inconsistently, reviewed inconsistently, and filed inconsistently. The reader then has to guess how to use what they are holding.

5. Verification and validation are two distinct activities, and both are required

Verification asks whether the document is technically correct. Validation asks whether the document actually works when a real user tries to follow it. Nuclear operators treat these as separate steps. The IAEA technical report on verification and validation formalises this distinction for software and I&C systems, and the same logic is applied to procedures.

Most industrial review processes do verification only. An engineer signs off that the content matches the design. Nobody watches a user attempt the task. So the first validation happens in the field, which is the worst possible place to discover a defect.

6. Build a formal feedback and revision loop

A nuclear procedure is not finished when it is issued. It enters a defined loop of operator feedback, incident review, periodic revision, and reauthorisation. IAEA-TECDOC-1335 on configuration management ties this directly to the principle that documentation must match physical reality at all times.

Most manufacturers rely on ad-hoc updates triggered by complaints. There is no cadence, no ownership, and no record of why a change was made. So documents drift from the product, and the dossier loses its defence value when it matters.

7. Use a Writer's Guide to make quality independent of the individual author

The Writer's Guide is the single most underused document in industrial technical writing. A nuclear Writer's Guide defines vocabulary, sentence structure, formatting rules, step numbering conventions, and how to handle conditions, branching, and warnings. Two different writers, using the same guide, produce documents that look and read the same.

Without a guide, every writer reinvents the house style. Turnover causes quality collapse. New hires ramp up slowly. The organisation cannot scale its documentation function because every output depends on the individual sitting at the keyboard.

“We have turned INSTRKTIV’s Writer’s Guide into a guide specifically for the nuclear sector, taking IAEA requirements into account as well”

Ferry Vermeulen, founder at INSTRKTIV

8. Treat content management as a discipline, not an afterthought

Nuclear operators manage documentation as an asset class. Version control, access control, revision history, retention schedules, and traceability to requirements are all baseline expectations. The documentation function is not bolted onto engineering; it is a parallel discipline with its own tooling and its own competencies.

In most manufacturing businesses, documentation lives in shared drives, engineers maintain it part-time, and there is no single source of truth. That model worked when documentation was small and static. It does not work for current CE and sector-specific compliance regimes.

The structural basics they get right

On top of the principles above, nuclear operators get three structural things right. First, they use templates that are genuinely mandatory, not optional. Second, their creation, review, and authorisation process is documented and followed, not improvised. Third, and most importantly, the process is fast enough that people actually use it rather than work around it. A control system so onerous that writers bypass it is worse than no control at all. The IAEA guide on documentation for regulating nuclear facilities sets out this balance between rigour and usability.

Closing: Who owns THE documentation?

The structural lesson from nuclear is organisational, not technical. Documentation is not a shared part-time responsibility. It is a dedicated function with its own ownership, its own skills, and its own accountability. When every engineer writes when they have time, nobody owns quality. When documentation has an owner, quality becomes manageable.

You do not need a reactor to adopt this model. You need to decide that documentation is something you do on purpose, not by default.

Ready to bring this discipline to your own documentation? Contact INSTRKTIV to find out how we can help.

CONTACT US