Technical FileEU

EU Machinery Regulation (EU) 2023/1230 Technical Documentation and Technical File

Annex IV turned into a practical evidence index.

Focus: risk assessment mapping, route-ready evidence, and exportable documentation packs.

Back to main artifact Review sources

Author

Sorena AI

Published

Feb 21, 2026

Updated

Feb 21, 2026

Sections

Structured answer sets in this page tree.

Primary sources

Cited legal and guidance references.

Publication metadata

Sorena AI

Published Feb 21, 2026

Updated Feb 21, 2026

Overview

Annex IV makes the technical file explicit: it must specify the means used to ensure conformity with essential health and safety requirements (Annex III) and include a minimum set of evidence. The fastest way to build a strong file is to treat it as an evidence system: a stable index that links each requirement and hazard to protective measures and verification reports.

Section 1

1) Pick the right Annex IV track first

The technical documentation structure depends on whether you ship machinery or related products, or partly completed machinery. State that track at the top of the file index.

This sounds basic, but it prevents declaration and instruction mistakes later.

Annex IV Part A applies to machinery and related products that will carry the CE mark and a DoC.
Annex IV Part B applies to partly completed machinery that ships with assembly instructions and a declaration of incorporation.
Use one shared evidence architecture with a clear branch for Part A vs Part B outputs.

Section 2

2) Part A minimum elements should read like an audit index

Annex IV Part A is the minimum content list, not an optional example. Treat each item as a section in the controlled index.

The highest-value item is still the risk-assessment package because it links the rest of the evidence together.

Complete description, intended use, drawings, schematics, and explanations of operation.
Risk-assessment documentation showing the applicable Annex III requirements, the protective measures used for each, and residual risks.
References to harmonised standards and common specifications with full or partial application clearly identified.
Test, inspection, and examination results plus production controls that keep series production conforming.
Instructions, information set, declarations for incorporated products under other EU acts where applicable, and the declarations or assembly instructions of incorporated partly completed machinery where relevant.

Section 3

3) Part B files need assembly logic, not a reduced Part A clone

Partly completed machinery files should show which essential health and safety requirements were applied, what risks remain for the integrator, and how assembly must be done safely.

Do not treat the declaration of incorporation as a lighter DoC. It serves a different legal function.

Describe intended function after incorporation or assembly.
Keep the relevant Annex III requirement set, risk-assessment outputs, drawings, standards references, and verification results.
Include assembly instructions and the declaration of incorporation as controlled outputs tied to the same version history.

Section 4

4) Add the software and sensor-system items explicitly required by the Regulation

Teams often miss the software-specific elements because they are not traditional mechanical-file artifacts. Build them into the index from day one.

Competent authorities may ask for source code or programming logic where necessary to verify compliance, so you need a retrieval process before anyone asks.

Keep safety-related software architecture, logic descriptions, versioning, and the basis for safe operation identification.
Where relevant, keep descriptions of system characteristics, capabilities, limitations, and development, testing, and validation processes for sensor-fed, remotely driven, or autonomous safety functions.
Link these items to the Annex III corruption-protection and logging controls rather than storing them as disconnected attachments.

Section 5

5) Digital instructions and declarations are part of the technical-file design

If you use digital delivery, the access conditions become part of the compliance architecture. That means retention, accessibility, and version traceability belong in the file design.

This is especially important when declarations are delivered via an internet address or machine-readable code.

Digital instructions for machinery or related products must be printable, downloadable, and savable, and users may request paper copies free of charge within one month.
For non-professional-use machinery, essential safety information must still be provided in paper form.
Digital assembly instructions and the declaration of incorporation for partly completed machinery must remain accessible online for 10 years.

Recommended next step

Keep EU Machinery Regulation (EU) 2023/1230 Technical Documentation and Technical File in one governed evidence system

SSOT can take EU Machinery Regulation (EU) 2023/1230 Technical Documentation and Technical File from reusing this material inside a governed evidence system to a reusable workflow inside Sorena. Teams working on EU Machinery Regulation (EU) 2023/1230 can keep owners, evidence, and next steps aligned without copying this guide into separate documents.

Evidence system

Open SSOT for EU Machinery Regulation (EU) 2023/1230 Technical Documentation and Technical File

Start from EU Machinery Regulation (EU) 2023/1230 Technical Documentation and Technical File and keep documents, evidence, and control records in one governed system.

Explore next step

Talk to Sorena

Talk through EU Machinery Regulation (EU) 2023/1230

Review your current process, evidence gaps, and next steps for EU Machinery Regulation (EU) 2023/1230 Technical Documentation and Technical File.

Explore next step

Section 6

6) Retrieval discipline is part of compliance

A technical file that exists but cannot be exported quickly is not operational. Design ownership, storage, and service levels up front.

The safest pattern is one stable folder structure and one response-pack export per family.

Assign a file owner and backup owner per product family.
Maintain a response pack with the current DoC or DoI, index, core reports, and instructions.
Track design changes, software updates, standards updates, route changes, and declaration revisions in a visible change log.

Primary sources

References and citations

Regulation (EU) 2019/1020 - market surveillance (EUR-Lex)

eur-lex.europa.eu

Referenced sections

Horizontal market-surveillance framework relevant to technical-file retrieval and authority response.

Regulation (EU) 2023/1230 corrigendum - Annex III general principles (EUR-Lex)

eur-lex.europa.eu

Referenced sections

Primary source for the risk-assessment and safety-integration principles that structure the technical file.

Regulation (EU) 2023/1230 corrigendum - Annex IV and digital-document provisions (EUR-Lex)

eur-lex.europa.eu

Referenced sections

Primary source for Part A and Part B technical documentation, source-code or programming-logic requests, and digital instruction or declaration conditions.

Related guides