Technical File is the structured technical documentation a medical device manufacturer compiles to demonstrate that a device conforms to EU MDR 2017/745. Defined mainly by Annex II and Annex III, it covers device description, design and manufacturing information, risk management, and clinical evidence, and it forms the basis for CE marking and conformity assessment.
What is a Technical File?
A Technical File, also called technical documentation, is the evidence package that proves a medical device meets the General Safety and Performance Requirements (GSPR) in Annex I of EU MDR 2017/745. Its structure follows Annex II for technical documentation and Annex III for post-market surveillance documentation. Every device sold in the EU needs one, from a Class I bandage to a Class III implant, though the depth scales with risk class.
The file sits at the center of the device lifecycle. Design teams populate it during development, a notified body reviews it during conformity assessment for most devices above Class I, and the manufacturer keeps it current well beyond the last unit shipped.
Why the Technical File matters in medical device development
A weak Technical File is one of the most common reasons CE marking stalls. Notified bodies routinely return documentation that is incomplete, inconsistent, or hard to follow, and each round of questions can add months to a launch. Team-NB, the notified-body association, issued best-practice guidance for Annex II and III submissions because so many arrive poorly organized.
The stakes go past timelines. The file is the main object of scrutiny during audits and post-market investigations. If a field issue arises, regulators read the Technical File to judge whether the manufacturer identified the hazard, controlled it, and backed its claims with data. Gaps become nonconformities, sales holds, or removal from the market. MDR requires the documentation to stay available for at least 10 years after the last device is placed on the market, so it must be maintained throughout.
Key components of a Technical File
Annex II groups the required content into these areas:
- Device description and specification: intended purpose, variants, accessories, and the Basic UDI-DI.
- Information supplied by the manufacturer: labels, instructions for use, and packaging.
- Design and manufacturing information: design stages plus the production processes and sites.
- GSPR checklist: a mapping of each safety and performance requirement to the evidence and standards used.
- Benefit-risk analysis and risk management, documented per ISO 14971.
- Verification and validation: preclinical data, biocompatibility per ISO 10993-1, electrical safety per IEC 60601-1, usability per IEC 62366-1, and software lifecycle records per IEC 62304 where the device contains software.
- Clinical evaluation, with the clinical evaluation report and its supporting data.
Annex III then adds the post-market surveillance content: the PMS plan, the periodic safety update report (PSUR), and post-market clinical follow-up.
Harmonized standards do much of the work. Conforming to a standard listed in the Official Journal gives a presumption of conformity with the matching GSPR, which is why the file cites standards by number rather than describing methods from scratch. ISO 13485 provides the quality system backbone that keeps the set controlled and traceable.
Common challenges and best practices
The most frequent failure is structure, not science. Reviewers can usually find the data, but not quickly, so a clear index and consistent cross-referencing matter as much as the content. Build the file to Annex II order from day one rather than assembling it at the end.
Two problems recur. The GSPR checklist is often treated as a formality when strong files link every requirement to a document and standard with a clear rationale for anything marked not applicable. Teams also underestimate upkeep, since design changes, complaints, and revised standards feed back into the file. Change control has to reach the documentation as well as the product.
For US-facing programs, note the alignment shift. The FDA Quality Management System Regulation (QMSR) took effect on February 2, 2026, and incorporates ISO 13485:2016 by reference into 21 CFR Part 820. Legacy terms such as Design History File and Device Master Record are giving way to the ISO-aligned Medical Device File and Design and Development File. Because the EU Technical File and these US records draw on the same design and risk evidence, one well-controlled set can serve both markets with less duplication.
How SJML helps with the Technical File
SJML supports Technical File preparation as part of its Compliance-as-a-Service and regulatory sustenance work. The QARA team builds and remediates technical documentation and design history files, assembles GSPR checklists, and aligns risk management files to ISO 14971 and quality systems to ISO 13485 and MDSAP. Because SJML also handles device design, verification, and manufacturing under one roof, the engineering evidence that populates the file, from IEC 60601 testing to usability and software lifecycle records, is generated in-house and kept traceable. That single-source approach shortens review cycles and reduces the gaps notified bodies flag most often.
Frequently asked questions
No. A Technical File is the EU MDR documentation that demonstrates conformity for the whole device, while a Design History File (DHF) is the US design-controls record. They overlap heavily and draw on the same evidence, but the Technical File is broader and includes clinical evaluation and post-market surveillance content that the DHF does not.
Yes. Every medical device placed on the EU market needs technical documentation under EU MDR 2017/745, including Class I devices. The required content is the same in scope, but the depth and the level of external review differ. Most Class I manufacturers self-certify, while higher-risk classes undergo notified body assessment of the file.
Under EU MDR, the manufacturer must keep the Technical File available to authorities for at least 10 years after the last device covered by it is placed on the market. For implantable devices, the period is at least 15 years. The file must stay current throughout, reflecting design changes, complaints, and post-market data.
For most devices above Class I, a notified body reviews the Technical File during conformity assessment before CE marking. Competent authorities can also request it at any time, including during market surveillance or after an incident. Internally, QA and regulatory teams review it before submission and at each significant design or process change.
Related terms
- Design History File (DHF)
- General Safety and Performance Requirements (GSPR)
- Conformity Assessment
- Clinical Evaluation Report (CER)
- Medical Device File (MDF)
