Your Notified Body audit is in 12 weeks. Your technical file isn't ready.

Your team has FDA 510(k) clearance for a Class II surgical instrument. The U.S. launch went well, and now the board wants European market access. Your VP of regulatory assumed you could reuse the FDA submission documentation—"it's basically the same device, same evidence." Then someone actually read EU MDR 2017/745 Annex II and Annex III. The technical file structure is completely different. The GSPR checklist has 200+ line items, each requiring specific conformance evidence mapped to harmonized standards. The clinical evaluation isn't a predicate comparison—it's a standalone document requiring systematic literature review, equivalence justification across three dimensions, and a benefit-risk analysis that follows MEDDEV 2.7/1 Rev 4 methodology. Your Notified Body audit is in 12 weeks.

You just discovered that having the engineering evidence and having the engineering evidence in the right structure are two entirely different problems.

What actually goes wrong

The GSPR mapping is the first wall. Each General Safety and Performance Requirement in Annex I needs a conformance rationale—either through a harmonized standard, a common specification, or alternative technical evidence. Your team starts the checklist and realizes that for half the items, the evidence exists somewhere in the FDA submission or DHF, but it's not organized in a way that maps to the GSPR structure. GSPR 10 through 22 cover specific engineering domains—chemical properties, infection control, software, electrical safety, biocompatibility—and each one requires tracing from the requirement through the applicable standard to the specific test report or design analysis that demonstrates conformance.

The clinical evaluation is the second wall. Your FDA submission relied on substantial equivalence to a predicate. EU MDR requires you to demonstrate equivalence across technical, biological, and clinical characteristics—and you need a contract or published data access agreement with the equivalent device manufacturer to use their clinical data. If you can't get that agreement, you're writing a clinical evaluation based on literature alone, which means a systematic review protocol, defined search strings, appraisal of every included study, and a synthesis that addresses each GSPR with clinical relevance. Your regulatory affairs team has never written one.

The post-market surveillance plan is the third wall. EU MDR requires a PMS plan, a PMCF plan, and—for your device classification—a periodic safety update report. These aren't boilerplate documents; they need to reference specific residual risks from your clinical evaluation and define surveillance activities that address them. The fourth wall: UDI registration in EUDAMED, the Declaration of Conformity format, and the labeling requirements that differ from FDA in ways that affect your packaging artwork timeline.

The same 12 weeks, with MANKAIND

The engineering evidence still needs to exist—MANKAIND doesn't fabricate test reports. But the platform transforms how that evidence is organized, mapped, and structured into the technical file. MANKAIND ingests your existing FDA submission documentation, DHF, and test reports, then maps them against the GSPR checklist. For each requirement, the platform identifies which existing evidence satisfies the conformance rationale, which harmonized standards apply, and where the gaps are—so your team knows on day one exactly what new work is required versus what can be restructured from existing outputs.

The clinical evaluation is generated from a structured framework. MANKAIND builds the equivalence analysis by systematically comparing your device's technical, biological, and clinical characteristics against the equivalent device—using the engineering specifications already captured in the design history. The literature review follows a defined protocol with reproducible search methodology. The benefit-risk analysis connects back to the risk management file, pulling the residual risk data that the clinical evaluation needs to reference.

The post-market surveillance plan and PMCF plan are generated from the clinical evaluation's identified gaps and the risk analysis's residual risk profile—not drafted as standalone documents. When the clinical evaluation identifies that a specific patient subpopulation was underrepresented in the evidence base, that gap becomes a defined PMCF objective with specific data collection requirements.

The outcome

The Notified Body receives a technical file where every GSPR entry traces to specific evidence, the clinical evaluation follows a defensible methodology, and the post-market surveillance plan reflects the actual risk profile of the device. Your team spent 12 weeks on engineering judgment—deciding which standards to claim, evaluating equivalence arguments, defining clinical evidence strategy—not on reformatting Word documents and hunting for test reports across shared drives. The audit findings are about engineering substance, not about missing cross-references. That is the difference between a technical file assembled under pressure and one structured from engineering intelligence.