RNCS Free Assessment
Medical Device Registration in Europe · 4.3

Technical Documentation: The File That Makes or Breaks Your CE Mark

Next: Clinical Evaluation Under EU MDR →

When a Notified Body reviews your device, it never sees the device first. It sees your file. Everything you know about the design, the risks, the testing and the clinical evidence have to be on the page, in a form a reviewer who has never met you can follow.

That file is the technical documentation.

What is the technical documentation?

Technical documentation is the body of evidence showing that your device meets the General Safety and Performance Requirements (GSPRs) in Annex I of the MDR. Annex II defines what it must contain. Annex III covers the post-market surveillance documentation that sits alongside it.

The regulation asks for it to be presented in a clear, organised, searchable and unambiguous way. That sounds like a formatting point. In practice it is a quality test: a file that is hard to navigate usually has gaps behind the confusion.

Why it matters

The MDR is stricter than the directives it replaced. Evidence that was once accepted as a short summary now must be shown in full, with clear links between claims and data.

The file matters for three reasons. It is what the Notified Body assesses, so its quality drives how many questions you receive and how long the review takes. It is what authorities can ask your representative to produce at any time. And it is your own working record, the single source of truth when someone asks, years later, why the device was designed a certain way.

What goes inside

Annex II sets out six main areas.

SectionWhat it covers
Device description and specificationIntended purpose, users, patients, variants, accessories, UDI-DI, classification and reasoning, and links to earlier generations or similar devices
Information supplied by the manufacturerLabels, instructions for use and the translations needed for each market
Design and manufacturing informationDesign stages, manufacturing processes, sites and critical suppliers
General Safety and Performance RequirementsA checklist showing how each applicable requirement is met, and which evidence proves it
Benefit-risk analysis and risk managementYour ISO 14971 risk file and the conclusion that benefits outweigh residual risks
Product verification and validationPre-clinical and clinical evidence such as biocompatibility, electrical safety, software, stability and shelf life, performance testing and the clinical evaluation

Annex III adds the post-market surveillance plan and the reports it produces.

The GSPR checklist: the part reviewers read first

This checklist is the map to your whole file. For every requirement in Annex I, it should say whether it applies, why if it does not, and exactly which document and section proves compliance.

A checklist that says "see test report" without naming the report or section is one of the quickest ways to generate questions. Treat it as an index that someone else will actually use and check each reference before you submit.

Keep the story consistent

Reviewers do not read documents in isolation. They place the risk file next to the clinical evaluation, and both next to the instructions for use. If the intended purpose differs between them, or a risk appears in one but not another, expect a question.

A few habits help:

  • Write the basic details like intended purpose, indications for use, contraindications etc. once and reuse it everywhere else
  • Trace each hazard from the risk file to a control, a test and a line in the instructions for use
  • Align the clinical evaluation with the claims you make on labels and in marketing
  • Control versions tightly, so the file a reviewer sees matches what you sell

Special cases that need extra care

Some device types need more than the standard evidence.

  • Reusable devices. You must show that cleaning, disinfection and sterilisation instructions work, with validation data. Instructions you cannot back with evidence are a common source of questions.
  • Sterile devices. Packaging, sterilisation validation and shelf life all need evidence.
  • Software. Lifecycle records (often to IEC 62304), cybersecurity and usability evidence are expected.
  • Devices with a measuring function. Accuracy claims must be tested and documented.
  • Device families. If you group devices, justify why they belong together and show that the evidence covers the worst case.

Relevant standards such as ISO 14971, ISO 10993-1, IEC 62366-1 and ISO 17664 help here, but citing a standard is not the same as showing compliance. The reviewer wants your results.

How to organise it so a reviewer can follow

Good structure saves weeks.

  • Start with a master index that maps the file to Annex II and Annex III.
  • Keep one topic per document, with clear titles and version numbers.
  • Cross-reference precisely, with document, section and page.
  • Summarise before you detail. A short overview at the top of each section lets a reviewer see your argument before the data.
  • Run an internal mock review. Ask someone who did not write it to read it cold and mark everything that confuses them.

Keeping it alive after certification

The file is never finished. Under Article 10, you must keep technical documentation, the Declaration of Conformity and certificates available for at least ten years after the last device is placed on the market, or fifteen years for implantable devices.

In between, it must follow the device. Design changes, new test data, complaint trends, post-market findings and updated standards all feed back in. Set up change control so that nothing reaches the market without the file being updated and tell your Notified Body about significant changes before you make them.

Mistakes worth avoiding

  • Building the file only after choosing a Notified Body
  • Reusing evidence from an older device without justifying that it still applies
  • Test reports that lack a rationale for sample size or acceptance criteria
  • A risk file that was written once and never updated
  • Treating the file as paperwork to produce, instead of an argument to make

Last reviewed: October 2026

Contact us today

Tell us about your device and target market. Our regulatory specialist, not a salesperson, will reply within one business day.

Get Your Free Regulatory Assessment