Medical Device made Easy Podcast podcast

September 10, 2026 Your Technical Documentation Has All the Documents… So Why Isn't It Ready?

A company says its Medical Device Technical Documentation is 90% or 95% ready.

The Risk Management File exists. The Clinical Evaluation is complete. Testing has been performed. The GSPR checklist and IFU are available.

But there's an important question:

95% of what?

Having all the expected documents doesn't necessarily mean your Technical Documentation is ready for assessment. Like a puzzle, you can have every piece on the table—but if some pieces are outdated, others belong to a different version of the product, and several don't fit together, the puzzle isn't complete.

1. Start With the Product, Not Annex II

Instead of immediately opening an Annex II template and looking for documents to fill each section, start with a more fundamental question:

What exactly are we trying to certify?

Your intended purpose, patient population, intended users, use environment, indications, contraindications, lifetime, claims, variants and accessories should provide a common source of truth across the Technical Documentation.

If Marketing makes a claim that isn't reflected in the intended purpose, Clinical Evaluation or Risk Management File, you may already have a significant consistency problem.

2. Challenge Your Regulatory Assumptions

“It's Class IIa because our competitor is Class IIa” isn't a classification rationale.

Early assumptions about qualification, classification and conformity assessment can influence testing, clinical strategy, budget and Notified Body involvement.

Those assumptions should therefore be challenged and properly documented before they become expensive to change.

3. Use the GSPR to Build the Dossier

The GSPR shouldn't simply appear at the end of the project as another checklist.

For every applicable requirement, ask:

How will we demonstrate conformity?

That means identifying the relevant standard, specification, analysis, test or report—and determining whether the required evidence actually exists.

Used this way, the GSPR becomes a tool for building Technical Documentation and identifying evidence gaps early.

4. Available Doesn't Mean Adequate

One of the biggest mistakes in Technical Documentation gap assessments is asking only:

“Do we have this document?”

A better question is:

“Is this evidence adequate for the device we're certifying?”

A biocompatibility report may exist—but does it cover the same materials, manufacturing process, patient-contacting components and contact duration?

Software verification may exist—but does it cover the current software version?

Clinical evidence may exist—but does it support the current intended purpose and claims?

That's why Available, Applicable and Adequate are three different things.

5. Make Sure the Puzzle Fits

Before submission, consistency and traceability become critical.

Imagine the IFU says the device can be used for seven days, while the Risk Management File and biological evaluation assume only 24 hours.

Every document exists—but together they don't tell a coherent story.

A reviewer should be able to trace important claims through intended purpose, design requirements, verification, clinical evidence, risk management, labeling and PMS.

Likewise, important risks should connect logically to risk controls, design implementation, verification, residual risk and post-market monitoring.

The 80/20 Approach to Technical Documentation

Instead of focusing first on the number of documents completed, focus on five questions:

Do we understand the product and its claims?
Is our regulatory strategy defensible?
Have requirements been translated into evidence needs?
Is our evidence adequate?
Does everything tell the same story?

Strong foundations make the rest of Technical Documentation much easier to structure.

EMD Technical Documentation Roadmap

To support this process, Easy Medical Device created the EMD Technical Documentation Roadmap.

The tool provides a structure for understanding the product, documenting regulatory strategy, mapping requirements, identifying standards and guidance, connecting risks with evidence, assessing gaps, assigning responsibilities, performing consistency checks, and ultimately mapping the documentation into Annex II and Annex III.

Final Takeaway

Stop thinking about Technical Documentation as a collection of folders that need to be filled.

Think about what the reviewer needs to understand:

Is there sufficient, coherent evidence demonstrating that this device conforms with the applicable requirements?

Your Technical Documentation isn't a filing cabinet.

Easy Medical Device Services

CE Marking • MDR • IVDR • Technical Documentation

Medical Device Market Access Services – Easy Medical Device

Back Office Services (BOSS Program)

SmartEye eQMS

SmartEye – eQMS – Easy Medical Device

EasyIFU