EU MDR Technical Documentation (Annex II & III): Structure, Contents, and Gap Assessment
Quick answer: EU MDR technical documentation is defined by Annex II (the core file: device description, labelling, design and manufacturing information, GSPR demonstration, benefit-risk and risk management, verification and validation including clinical evaluation) and Annex III (post-market surveillance documentation: PMS plan, PSUR or PMS report). It must be "clear, organised, readily searchable and unambiguous." Most notified body findings trace to three gaps: incomplete GSPR mapping, clinical evaluation that doesn't support the claims, and risk management files disconnected from design evidence.
What Annex II requires
1. Device description and specification. Intended purpose, patient population, principles of operation, classification rationale, variants and accessories, previous generations, and UDI-DI.
2. Information supplied by the manufacturer. Labels in the languages of intended member states, instructions for use, and promotional claims — auditors check consistency between IFU claims and clinical evidence.
3. Design and manufacturing information. Design stages, complete specifications, manufacturing processes and their validation, sites, suppliers and subcontractors.
4. General safety and performance requirements (GSPR). The Annex I requirements, which apply, the method of demonstrating conformity (harmonised standards, common specifications, or other solutions), and precise cross-references to evidence. A GSPR checklist that says "complies — see file" without pinpoint references is a standard finding.
5. Benefit-risk analysis and risk management. The ISO 14971 risk management file, aligned with the clinical evaluation and the IFU's residual risk disclosures.
6. Verification and validation. Test data, pre-clinical studies, biocompatibility, electrical safety and EMC, software lifecycle documentation (IEC 62304) where applicable, stability and shelf life, and the clinical evaluation report with its PMCF plan (Article 61 and Annex XIV).
What Annex III adds
The post-market surveillance documentation: the PMS plan (with its data sources, indicators, and threshold values per Article 84), and the PSUR (Class IIa and above, Article 86) or PMS report (Class I, Article 85). Under MDR this is part of technical documentation — a live document set, not an appendix written once.
How notified bodies actually review it
Reviewers work the file for coherence across documents: does the intended purpose match the classification, the clinical evaluation, and the claims in the IFU? Do risk controls trace to verification evidence? Does the PMS plan's threshold values connect back to the risk file? Documentation written by different contractors at different times, never reconciled, produces exactly the incoherence reviewers are trained to find.
The gap assessment approach
A structured gap assessment before notified body submission audits the file against Annex II/III line by line, grades gaps by certification risk, and produces a remediation plan with effort estimates. Typical high-severity findings in first-time files: equivalence claims without full data access; GSPR entries citing withdrawn standards; usability engineering (IEC 62366-1) missing entirely; software documentation not matching the released version; and PMCF plans that are plans in name only. Fixing these pre-submission costs weeks; fixing them inside a notified body review cycle costs quarters, because each response round re-enters the queue.
Frequently asked questions
How should the file be structured? Follow the Annex II heading structure directly — reviewers navigate by it. Keep one master GSPR matrix as the file's spine, with pinpoint references.
How often must technical documentation be updated? Continuously — Article 10(9) requires keeping it up to date, and the PSUR cycle forces the point (annually for IIb/III, at least every two years for IIa).
Do Class I devices need technical documentation? Yes — the same Annex II/III obligations apply; there is simply no notified body review. Competent authorities can request the file at any time.
Who verifies technical documentation internally? The PRRC (Article 15(3)(b)) — one reason a qualified external PRRC adds value beyond the signature.
About QLE Group
QLE Group performs technical documentation gap assessments, remediation, and full Annex II/III file builds from Brussels, applying the review criteria notified bodies use. Work is delivered by Radoslav Milkov — qualified PRRC, ISO 13485 / 21 CFR 820 Lead Auditor, LL.M. in EU Law, European Commission external expert. Complexity-indexed pricing at qle.be.
Need your file audit-ready? Book a scoping call or email info@qle.be.
