Nuclear documentation: one industry, no single rulebook

Suppliers moving into the nuclear sector usually start with one question: where is the list of documentation requirements. They expect a single rulebook. There is no single rulebook.

Requirements for nuclear documentation are not harmonised. They vary by country, by regulator, by licensee, by project, and in some cases by reactor design. A supplier qualified for one new build can win work on the next and find that the document control rules, the procedure formats and the records expectations have all shifted. The body of requirements that matters most is rarely the legislation. It sits in licence conditions, in quality programmes, in technical documentation obligations, in IAEA guidance, in ASME codes, and in customer requirements that arrive with the contract.

I have watched teams assume that a national nuclear act would tell them how to write an operating procedure. It does not. It tells the licensee to demonstrate safety and to keep its documentation under control, then leaves the detail to other documents. If a client asked you today which standard governs the format of your procedures, could you name it without checking the contract? 

There is no single nuclear documentation rulebook

Picture the requirements as layers, not a list. At the top sits the EU Nuclear Safety Directive. Below it, national legislation. Below that, the national regulator's requirements. Alongside these run the IAEA safety standards, NRC requirements, ASME codes, and ISO 19443 for the supply chain. Then come the project-specific requirements and, finally, the licence conditions for the individual installation. Every one of these layers feeds into a single thing: the documentation package the licensee has to maintain and defend. The difficulty is that each layer adds or sharpens requirements, and the lowest layers, the project requirements and the licence conditions, are usually the most detailed and the least public.

What the EU Nuclear Safety Directive actually requires

The EU Nuclear Safety Directive (2009/71/Euratom, amended by 2014/87/Euratom) says very little about manuals or technical documentation directly. Its focus is demonstrating nuclear safety, maintaining a safety management system, conducting a periodic safety review at least every ten years, and preserving nuclear competence.

The documentation-related duties that do appear are these:

• Safety demonstration: licence holders must submit documented evidence of the installation's safety when applying for a licence.

• Management systems: licence holders must maintain a management system that gives due priority to safety, which in practice means document control, procedures, work instructions and configuration management.

• Periodic safety reviews: a comprehensive reassessment at least every ten years, supported by extensive documentation of design, modifications, operating experience, incidents and safety analyses.

• Emergency procedures: develop, maintain, test and update emergency procedures and severe accident management guidelines.

• Operating experience: safety-significant events must be recorded, evaluated and documented.

• Training and competence: documented training programmes, competency records and qualification management for personnel involved in safety.

For anyone producing documentation, the concrete requirements are usually found not in the Euratom directive but in national licensing expectations, IAEA GSR Part 2 and GSR Part 7, IAEA Safety Guides and TECDOCs, ASME NQA-1, NRC guidance, ISO 19443, and the WENRA Safety Reference Levels. These contain far more specific rules for procedures, records, document control and configuration management than the directive itself.

One directive, implemented several ways

The Netherlands and Finland both implemented the same directive, and they did it differently. In the Netherlands the hierarchy runs from the Kernenergiewet to the Besluit kerninstallaties, splijtstoffen en ertsen (Bkse), to ministerial regulations such as the Regeling nucleaire veiligheid kerninstallaties, and finally to the licence conditions set by the ANVS. The Bkse contains no detailed requirements for operating manuals, maintenance manuals or work instructions. The detail is imposed through licence conditions and ANVS guidance, which for an installation such as Borssele are often far more specific than the law itself.

Finland pushed the detail into the regulator's guidance. The Nuclear Energy Act sets the fundamental safety principles, and the STUK YVL Guides carry the concrete requirements: management systems, document control, procedures and work instructions, safety analyses, configuration management, operating experience feedback, training and maintenance documentation, quality records, traceability, and verification and validation documentation. Same directive, two countries, two very different sets of practical rules. Requirements are not fully harmonised. They vary by country, project and vendor.

The same country, different projects

Harmonisation does not even exist fully within a single country. COVRA, the Dutch organisation responsible for radioactive waste management, demonstrates safety through a licensing basis under the supervision of ANVS, with further detail specified through licence conditions and supporting guidance, including references to IAEA publications such as TECDOC-1058 and GSR Part 2. The new-build PALLAS reactor applies a broader combination of requirements, including Dutch nuclear legislation, ANVS licensing requirements, IAEA safety standards, and industry codes such as ASME for specific systems and components. PALLAS has also developed a project-specific safety framework, the VOBK, built upon the Dutch regulatory framework, which itself is strongly influenced by IAEA safety standards. 

This is where suppliers get caught. There is a real distinction between ASME codes and NRC regulations. ASME Section III, ASME NQA-1 and the ASME OM Code are used worldwide, including in countries with no connection to the United States regulator, and can be contractually or technically mandatory for a project. NRC regulations only bind a European project if the reactor is NRC-licensed, if the ANVS writes specific NRC requirements into the licensing basis, or if the owner adopts NRC guidance voluntarily. In practice, many European projects still use NRC documents, the Regulatory Guides, NUREGs and the human factors review model NUREG-0711, as recognised good practice. Recognised good practice and legally applicable requirement are not the same thing, and the documentation team needs to know which is which before it writes anything.

Where the concrete requirements actually live

Two IAEA documents show how far apart these layers sit. IAEA GSR Part 2 works at management level. It requires a documented management system, controlled documentation, records management, competence management, leadership and safety culture, supplier management and continuous improvement. It does not tell you how to write a procedure. It tells management that procedures and documents must exist, be controlled, be maintained, and be used effectively.

IAEA TECDOC-1058 works at the other end. It is specifically about nuclear plant procedures and covers procedure writer qualifications and training, writing standards, format and structure, the use of action verbs, warnings, cautions and notes, verification and validation, review and approval, human factors and revision control. It even recommends that an organisation establish a Procedure Writer's Guide, defines what one is, and lists the topics it should cover, while making clear that the exact contents are for the organisation to set, not a fixed requirement.

Around these sit ASME NQA-1, which drives document control and long record retention for nuclear quality, and ISO 19443, which applies ISO 9001 to suppliers of items and services important to nuclear safety (ITNS) and is steadily becoming a contractual expectation across the supply chain. None of these tells the supplier the single answer. Together, they define the space the supplier has to map.

The gap the sector has not closed

The nuclear sector is very good at controlling documentation. It is much less harmonised on how information is structured, written and presented to the people who actually use it. The industry has, in effect, mastered the control of documents and left the usability of their content to vary widely. That is the gap.

This is why IEC/IEEE 82079-1, the standard for the preparation of information for use, belongs in every nuclear documentation programme. The nuclear standards govern how a document is controlled, traced, reviewed and retained. 82079-1 governs whether the content inside it can be understood and acted on: matching the language and structure to the competence of the least experienced qualified user, structuring warnings so the hazard, consequence and required action are clear, and making information findable at the point of need rather than buried in sequence. TECDOC-1058 already points the same way when it ties reading level to the least experienced qualified user and treats human factors as part of procedure quality. Bringing in the international information-for-use standard makes that principle explicit and consistent across the whole documentation set, complementing NQA-1, ISO 19443 and the IAEA framework rather than competing with them.

How to start documentation on a nuclear project

The order of work matters more than the volume of it. A workable starting sequence:

1. Determine the requirements that actually apply to this project. Look at the country, the regulator, the licensee, any project-specific safety requirements such as a VOBK set, the chosen codes and standards, and the customer requirements in the contract. Do not assume the last project's rules carry over.

2. Translate those requirements into concrete documentation obligations: which procedures, records, work instructions, training and maintenance documentation are needed, and what document control, review and traceability rules apply to each.

3. Decide what is controlled where, so the same knowledge is created once and reused across the project rather than rewritten, and paid for, several times.

4. Put a team in place that takes ownership, staffed with people trained to produce compliant documentation. Finance buys a reactor. It does not buy the skill to document it.

5. Apply IEC/IEEE 82079-1 alongside the nuclear standards, so the documentation is usable and not only controlled.

Nuclear projects have mastered control of documentation. The work that remains is making that documentation usable, and treating both as one discipline rather than two. If you are entering the nuclear supply chain, the first deliverable is not a manual. It is a clear map of what this specific project actually requires.

CONTACT US