Technical Documentation
Obodux Team
Under the EU Medical Device Regulation (EU) 2017/745 (MDR), every manufacturer must draw up technical documentation that shows the device meets the general safety and performance requirements, and keep it up to date. Annex II sets out what that documentation must contain. Annex III covers the technical documentation on post-market surveillance. For most devices a notified body reviews it before CE marking, and competent authorities can ask for it at any time.
This checklist walks through Annex II and III section by section: what each part must contain, what reviewers look for, and the gaps that most often send a file back.
At a glance
Section 1, device description and specification: intended purpose, users, classification, variants, accessories and Basic UDI-DI
Section 2, information supplied by the manufacturer: labels and instructions for use
Section 3, design and manufacturing information: design stages, manufacturing processes and validation, sites and suppliers
Section 4, general safety and performance requirements: the Annex I checklist with evidence for every requirement
Section 5, benefit-risk analysis and risk management
Section 6, product verification and validation: test results, biocompatibility, software, clinical evaluation and PMCF
Annex III: the PMS plan, plus the PMS report (Class I) or PSUR (Class IIa and above)
Section 1: Device description and specification
Product or trade name, and a general description including intended purpose and intended users
The Basic UDI-DI
Intended patient population, medical conditions, indications, contra-indications and warnings
Principles of operation and mode of action
Risk class and the Annex VIII classification rule applied, with the reasoning
Any novel features
Accessories, other devices and other products it is intended to be used with
All variants and configurations
Key functional elements, raw materials and materials in contact with the body
Previous generations of the device, and similar devices on the EU and international markets
What reviewers look for: an intended purpose used consistently across the whole file, and classification reasoning that names the rule and explains why it applies.
Section 2: Information supplied by the manufacturer
Labels on the device and its packaging (single unit, sales packaging and transport packaging)
Instructions for use, in the languages accepted in the member states where the device will be sold
What reviewers look for: labels and instructions that match the intended purpose, warnings and residual risks stated elsewhere in the file.
Section 3: Design and manufacturing information
Information to understand the design stages of the device
Complete information on the manufacturing processes and their validation, including continuous monitoring and final product testing
All sites, including suppliers and subcontractors, where design and manufacturing take place
Section 4: General safety and performance requirements
The file must show how the device meets each requirement in Annex I. In practice this is a checklist that states, for every requirement:
Whether it applies, and why not if it does not
The method used to show conformity
The harmonised standards, common specifications or other solutions applied
Exactly where the evidence sits in the file
What reviewers look for: every requirement that applies is backed by a precise reference to a document, not just a standard number.
Section 5: Benefit-risk analysis and risk management
The benefit-risk analysis referred to in Annex I, sections 1 and 8
The solutions adopted and the results of the risk management referred to in Annex I, section 3
Risk management is usually carried out to EN ISO 14971. Reviewers expect risk controls to trace through to the safety requirements, the labelling and the verification evidence.
Section 6: Product verification and validation
Results and critical analyses of all verification and validation tests and studies: engineering, laboratory, simulated use, animal tests and published literature
Biocompatibility of all materials in direct or indirect contact with the body
Physical, chemical and microbiological characterisation
Electrical safety and electromagnetic compatibility
Software verification and validation
Stability and shelf life
Performance and safety
The clinical evaluation plan and report, under Article 61 and Annex XIV
The post-market clinical follow-up (PMCF) plan and evaluation report, or a justification of why PMCF is not applicable
Additional information for specific cases, such as devices with a medicinal substance, sterile devices or devices with a measuring function
Annex III: Post-market surveillance
The post-market surveillance plan under Article 84
For Class IIa, IIb and III devices, the periodic safety update report (PSUR) under Article 86
For Class I devices, the post-market surveillance report under Article 85
The PMS plan should show how you collect and use information on quality, performance and safety, how you report serious incidents and field safety corrective actions, and how findings feed back into the risk management, clinical evaluation and technical documentation.
Mistakes that get technical files sent back
An intended purpose that changes between the device description, labelling and clinical evaluation
Classification reasoning that is missing or names the wrong rule
A safety requirements checklist ticked "complies" with no traceable evidence
Risk management that does not link to the safety requirements or the instructions for use
A clinical evaluation that does not support every claim and indication
Out-of-date versions, or documents that contradict each other between sections
A PMS plan that exists but is not connected to the rest of the file
Team-NB, the association of European notified bodies, publishes a best practice guide on MDR technical documentation, now in its fourth version (April 2026). It is worth reading alongside this checklist.
Frequently asked questions
What is the difference between a technical file and technical documentation?
"Technical file" was the usual term under the old Medical Device Directive. The MDR uses "technical documentation", but the terms are often used interchangeably for the documentation required by Annex II and III.
How long must MDR technical documentation be kept?
At least 10 years after the last device covered by the EU declaration of conformity has been placed on the market, and at least 15 years for implantable devices (Article 10(8)).
Who can ask to see it?
Your notified body reviews it as part of conformity assessment, and competent authorities can request it at any time.
Is the EU declaration of conformity part of the technical documentation?
The declaration of conformity is a separate document, set out in Annex IV. It is usually kept with the technical documentation and must be consistent with it.
Do Class I devices need technical documentation?
Yes. Class I manufacturers draw up the same Annex II and III documentation, even though most Class I devices do not need a notified body.
Can one technical file cover both EU MDR and UKCA?
Much of the content can be shared, but the UK and EU have separate legal requirements and declarations, so check that each market's requirements and references are covered.
How Obodux helps
Obodux builds your technical documentation section by section against MDR Annex II and III. It links every safety requirement to its evidence and keeps versions and approvals in one place. It supports EU MDR and UKCA, so you can see the gaps before your notified body does. Get a free gap analysis or see our EU MDR technical file software.
Related articles

Technical Documentation
Navigating the MDR Technical File Challenge: A Strategic Guide for Medical Device Manufacturers
A strategic guide to the MDR technical file challenge: notified body review, the three-strike system, the cost of non-compliance and how to get it right.

Technical Documentation
The Gaps You Can't See: Lessons on EU MDR Readiness
What two decades of building medical devices teaches about EU MDR readiness, from Obodux co-founder Simon Taylor.

Technical Documentation
EU MDR Technical Documentation: How to Identify Gaps and Maintain Readiness
A manufacturer can have hundreds of documents and still struggle to answer a simple question: are we ready for assessment? Here is how to find out.

