EU Technical Documentation Requirements Guide: CE Marking Files

An EU technical documentation requirements guide is only useful when it helps you assemble a file that a notified body, market surveillance authority, or customs officer can follow. Under EU product law, technical documentation is the evidence that a product meets applicable essential requirements, harmonised standards, and the chosen conformity assessment procedure. The exact contents depend on the legal instrument. A medical device under Regulation (EU) 2017/745 follows Annex II, while machinery under Directive 2006/42/EC follows Annex VII. This guide maps the common structure, clause references, and maintenance duties. It also points to the official sources you should check before signing a declaration.

What EU Technical Documentation Must Contain

Most CE marking regimes require the same backbone: product identification, drawings, schematics, risk assessment, standards list, test reports, labels, instructions, and a declaration of conformity. The legal text may call it a technical file, technical documentation, or design dossier. The purpose is unchanged: demonstrate compliance and allow assessment.

Core elements across CE marking laws

• Product description and intended use, including variants and accessories.
• Design and manufacturing drawings, schematics, and component lists.
• Risk assessment and risk mitigation records, e.g. ISO 14971 for medical devices, ISO 12100 for machinery.
• List of harmonised standards applied, with full references and clauses.
• Test reports and calculations, including EMC, electrical safety, materials, and performance.
• Labels, markings, instructions for use, and translations.
• Declaration of conformity and, where used, notified body certificates.
• Post-market surveillance, vigilance, and corrective action records.

Use the EU CE Marking Technical File: A Practical Guide for a file structure that works across directives.

Sector-Specific Clause References You Should Know

Clause references matter because auditors check them directly. The following examples show how sector rules differ.

• Medical devices: Regulation (EU) 2017/745 Annex II sets technical documentation; Annex III covers post-market surveillance. Implantable devices have longer retention.
• Machinery: Directive 2006/42/EC Annex VII sets the technical file. Regulation (EU) 2023/1230 replaces it and uses Annex IV for technical documentation; transition ends 20 January 2027.
• Low Voltage: Directive 2014/35/EU Annex II.
• EMC: Directive 2014/30/EU Annex II.
• Radio Equipment: Directive 2014/53/EU Annex II.
• PPE: Regulation (EU) 2016/425 Annex II.

Always cite the consolidated version and the exact annex; older directive numbers can lead to the wrong evidence set. Where a conformity assessment module applies, choose it before writing the file. The Conformity Assessment Module Selection Guide for EU CE Marking explains module A, B+C, H, and others.

How to Build and Maintain the File

Build the file as a controlled document set, not a folder of loose PDFs. Assign an owner, version numbers, and a change log. Link each claim to evidence: a standard clause, a test report, or a risk control measure. Keep the language consistent with the declaration of conformity and the instructions.

Retention and updates

Most EU directives require the manufacturer or authorised representative to keep technical documentation for 10 years after the last product is placed on the market. Medical devices under Regulation (EU) 2017/745 generally require 10 years, or 15 years for implantable devices. Update the file when design, standards, suppliers, or legal requirements change. Do not overwrite old versions; retain them for traceability.

An EU technical documentation requirements guide should also flag language duties. Instructions and safety information must be in the language required by the member state where the product is sold. For machinery, the assembly instructions and declaration must be translated.

Common Gaps and Review Checklist

Market surveillance authorities often find the same weaknesses.

• Missing risk assessment or no link between risks and design changes.
• Standards list without editions, amendments, or clauses.
• Test reports from unaccredited labs or with expired samples.
• Declaration of conformity missing a directive, standard, or authorised representative.
• No post-market surveillance plan or complaint records.
• Incomplete translations or missing safety labels.

Keep a traceability matrix that maps each legal requirement to a document, test, or risk control. Run a gap review before a notified body audit. Use a checklist that mirrors the annex in your sector law. If the file includes personal data, such as user logs or clinical data, align it with GDPR duties. The GDPR Data Processing Agreement Clauses: A Practical Guide covers controller and processor terms.

Relationship to GDPR and Other Documentation

Technical documentation is not a GDPR record, but the two can overlap. A medical device file may contain clinical evaluation data, and a connected product may log user behaviour. Keep personal data minimised, documented, and lawful. Separate the product compliance file from the data protection file, but cross-reference where the same evidence is used.

An EU technical documentation requirements guide cannot replace legal advice. The applicable annex and conformity assessment module depend on the product, its risks, and the EU legal instrument. Confirm the current consolidated text on EUR-Lex before you finalise the file.

Practical Next Steps

1. Identify the exact EU law and annex. 2. Choose the conformity assessment module. 3. Build the file index. 4. Collect evidence and test reports. 5. Draft the declaration of conformity. 6. Set retention and review cycles. 7. Audit the file against the annex before signing.

Keep the file available to authorities for the required retention period. For most CE marking regimes, that means 10 years after the last unit is placed on the EU market. For high-risk medical devices, plan for longer. The goal is a file that is complete, current, and easy to assess. Review the file after every significant change and at least once a year.