A dual submission strategy runs an MDR CE marking track and an FDA clearance track in parallel, sharing a single QMS, a single risk file, a single intended purpose, and a single evidence base, while producing two separate submissions for two separate reviewers. It can shorten total time to two markets compared with sequential work, but it roughly doubles the near-term workload and budget, and it only pays off when both markets are already in the business plan with committed resources. Done well, it is a planning discipline. Done poorly, it is two rushed submissions that both fail.

By Tibor Zechmeister and Felix Lenhard. Last updated 10 April 2026.

TL;DR

  • A dual submission strategy is parallel execution of an MDR CE marking track and an FDA premarket track, anchored by shared upstream work (intended purpose, QMS, risk file, evidence base).
  • The efficiency gain is not on the submissions themselves — they remain two documents for two reviewers — but on the underlying work that feeds both.
  • MDR CE marking under Regulation (EU) 2017/745 requires a Notified Body conformity assessment under Article 52 for Class IIa and above, and clinical evidence under Article 61 for every device.
  • Dual submission is the right strategy when both markets are in the business plan with committed budget and headcount, and when a US regulatory specialist is already on the team.
  • It is the wrong strategy when one market is a "maybe later," when regulatory headcount is scarce, or when the founding team is still treating FDA framing as an afterthought.
  • MDSAP can anchor the QMS audit programme across both jurisdictions, reducing audit duplication.
  • The planning work happens once, at the start. The rework caused by planning the tracks in isolation is what kills dual-market budgets.

Why founders ask about dual submission

A founder pitches a seed round. The slide says "CE mark Year 1, FDA clearance Year 2." The investor asks why not both in Year 1. The founder has no good answer, so they promise both. Then the real work starts and the team discovers that "both in Year 1" is not a scheduling question — it is a structural decision about how the entire regulatory programme is built. Running two tracks is not running one track and then duplicating it. It is building one foundation that can carry two submissions at once.

This is the moment a dual submission strategy either becomes a real plan or becomes a commitment the team cannot keep. The difference is decided in the first month, not in the last quarter before filing.

A note on the boundary of our expertise, stated once and clearly. Tibor's authority is the EU MDR and the Notified Body system. He does not hold himself out as an FDA specialist. FDA-specific framing in this post stays at the general level on purpose. Predicate selection, CFR Part 820 implementation detail, review division interactions, and submission drafting belong to a US regulatory specialist who practices inside the FDA system daily.

When dual submission makes sense

Dual submission is not a default. It is a strategy that pays off in specific conditions and punishes the team when those conditions are not met.

It makes sense when the US market is already in the business plan with a target launch date, a named revenue assumption, and a US go-to-market plan that is not vague. It makes sense when the cap table can carry a regulatory programme roughly twice the size of a single-market programme for the duration of the build. It makes sense when the team has either hired or contracted a US regulatory specialist from the start, not as a line item for "later." It makes sense when the device's risk class is consistent enough across both jurisdictions that the same underlying evidence can serve both reviewers.

It does not make sense when the US plan is speculative. It does not make sense when the team is still solving MDR basics and quietly hoping the FDA side will "be similar." It does not make sense when regulatory headcount is one overworked person. In those cases, sequential planning is not slower — it is the only plan that finishes.

The honest test is this. If a founder cannot name the US classification pathway, the likely product code, and the specialist who will lead the US track, then dual submission is a wish on a slide, not a strategy. Sequential is the right answer.

For the broader comparative overview see MDR vs FDA: key differences for EU US medical device regulation and the planning companion regulatory strategy for startups targeting both EU and US markets.

The shared evidence base

The economic case for dual submission lives in one place — the upstream work that feeds both tracks. If that upstream work is designed once, from the start, to serve two reviewers, the parallel submissions become feasible. If it is built only for MDR and retrofitted for the FDA later, the parallel plan becomes two sequential plans with extra cost.

The shared base has six layers.

One intended purpose statement, drafted once, consistent across both submissions. This sounds trivial and is not. A sloppy intended purpose statement is the root cause of half the classification mismatches and clinical endpoint mismatches that blow up dual-market plans.

One risk management file built to EN ISO 14971:2019+A11:2021. The risk file is genuinely reusable across both tracks because the underlying standard is recognised on both sides.

One QMS foundation built to EN ISO 13485:2016+A11:2021 and gap-closed to US expectations from the start. The QMS is the most expensive thing to rebuild late. Building it once, to both standards, is the single highest-leverage decision in a dual plan.

One bench testing, biocompatibility, electrical safety, EMC, and software verification programme, designed with both reviewers in mind. Test plans written to serve only one side produce data that the other side cannot use without rework.

One clinical evidence plan, designed to satisfy MDR Article 61 and Annex XIV while also addressing what the US reviewer will want on the same device. This is the layer where a US specialist earns their fee early — the time to design a dual-purpose clinical investigation is before it starts, not after the data is in.

One technical argument about the device, expressed in two different document architectures. The MDR technical documentation and the FDA submission are structured differently, but the underlying engineering and clinical story is the same story, told twice, to two different audiences.

What is shared and what is duplicated

The discipline of dual submission is knowing which line items are shared and which are genuinely duplicated. Treating shared items as duplicated wastes money. Treating duplicated items as shared produces submissions that do not hold.

Shared, in most cases. The intended purpose statement. The risk management file. The bench, biocompatibility, electrical safety, EMC, and software verification data, provided the test plans were written for both. The underlying clinical evidence when the investigation was designed with both regulators in mind. The QMS, with the US gap close. The engineering and software architecture.

Duplicated, always. The CE marking conformity assessment itself, run by a Notified Body under Article 52 of Regulation (EU) 2017/745 for Class IIa and above. The US premarket submission, reviewed by the FDA. The clinical evaluation report in MDR format. The US submission narrative in its own format. The post-market obligations on each side. The labelling and IFU content that differs by jurisdiction. The economic operators on the EU side and the US Agent on the US side.

Partially shared. The clinical evidence — reusable where the study was designed for both, not reusable where endpoints were MDR-only. The QMS — shared foundation, with US-specific procedures bolted on. The cybersecurity work — shared technical substance, different documentation expectations.

The dual submission budget is the sum of two cost stacks minus the overlaps. The size of the overlaps is decided in the planning phase, not during execution.

Sequencing the dual work

Parallel does not mean "do everything at the same time." It means the two tracks share a single critical path for the shared work and then branch into two separate execution streams for the duplicated work.

The efficient pattern has three phases.

Phase one is the shared foundation. Intended purpose locked. Device description locked. Classification analysis completed on both sides. QMS designed to cover both. Risk management file started. Test plan library drafted to serve both reviewers. Clinical evidence strategy designed with both in mind. Both specialists — EU and US — are in the room for every decision in this phase. This is not where you save time by working in isolation. This is where you lose time by working in isolation.

Phase two is the parallel execution. The MDR technical documentation is built against the EN ISO 13485 QMS and prepared for Notified Body submission under Article 52. The US submission is built against the same evidence base in the document architecture the FDA expects. The two streams share the underlying data and diverge on the presentation. Status meetings for both tracks are held together so decisions in one track cannot accidentally break the other.

Phase three is the dual filing. MDR technical documentation goes to the Notified Body. The US submission goes to the FDA. Post-filing, each track follows its own review logic and its own response cadence. The shared infrastructure — QMS, risk file, evidence base — remains a single source of truth throughout.

This is not a shortcut. It is a more disciplined version of the work that would have happened anyway, with the discipline front-loaded instead of back-loaded.

MDSAP as the audit anchor

The Medical Device Single Audit Program, MDSAP, is run under the International Medical Device Regulators Forum and allows a single QMS audit by an authorised audit organisation to be recognised by multiple participating regulators including the United States. For a startup running a dual submission strategy, MDSAP is often the right QMS audit frame from the start because it reduces audit duplication and creates a single artefact that multiple jurisdictions accept.

MDSAP does not replace the Notified Body conformity assessment under MDR Article 52 for the EU side. The Notified Body remains the assessor for MDR technical documentation and issues the certificates that support the Declaration of Conformity. MDSAP sits alongside the QMS audit programme as a mechanism that reduces duplication of QMS audit effort across jurisdictions.

The practical point for founders: MDSAP is not free, and it is not instant, but it is usually cheaper than running entirely separate QMS audit programmes for each market over the life of the product. The decision to adopt MDSAP is a planning-phase decision, not something to bolt on after the first CE audit. The details of MDSAP scope, timing, and audit organisation selection are worth a dedicated conversation with a specialist.

The team and budget reality

A dual submission programme is not a single-headcount project dressed up in ambition. It has a minimum viable team shape that is different from a single-market programme.

On the EU side, the team needs a regulatory lead who owns the MDR technical documentation and the Notified Body relationship, a QMS owner, a clinical evaluation owner, and access to engineering and software leads who can produce the evidence. On the US side, the team needs a US regulatory specialist who owns the submission pathway, predicate analysis, and FDA interactions, and a QMS implementation role that closes the gap between the ISO 13485 base and US expectations.

The overlap between the two sides is the shared foundation: the intended purpose owner, the risk management owner, the evidence planning owner, and whichever single person is holding the two tracks together at the project management level. That last role is the one founders most often forget to resource, and it is the one that determines whether the plan holds together or fragments.

The budget shape is not "twice MDR." It is closer to "MDR plus US-specific work plus an integration layer." The MDR cost stack is roughly what a single-market MDR programme would cost. The US cost stack adds FDA user fees, US regulatory consulting, US-specific testing, a US Agent, and Part 820 implementation work. The integration layer is the cost of running two tracks without letting them drift apart — additional project management, joint status meetings, shared documentation discipline, and the specialist fees for decisions that touch both sides.

A founder who has budgeted only for the submissions themselves is budgeting for the visible half of the work. The integration layer is the invisible half, and it is where underfunded dual programmes fail.

Common mistakes

The dual submission mistakes repeat across startups. The pattern is almost always one of these.

Treating CE as a dress rehearsal for the FDA. CE is not a warm-up for an FDA submission. The two are different frameworks with different logic, and a CE mark is not credit toward anything on the US side.

Designing the clinical investigation only for MDR endpoints. This forecloses the option of using the same investigation to support the US submission, and the rework is expensive.

Postponing the US specialist. The single most common failure pattern is starting the MDR work and promising to bring in US expertise later. By the time "later" arrives, the upstream decisions that should have been made with both sides in the room have already been made with only one side present. The rework starts immediately.

Assuming ISO 13485 equals Part 820. The FDA's QMSR harmonisation initiative is moving Part 820 closer to ISO 13485, but there is still gap work at the implementation level and the FDA has its own inspection expectations. The gap analysis belongs in phase one, not in phase three.

Underfunding the integration layer. A dual programme with two competent track owners and no one owning the seam between them is a programme that produces two drifted submissions.

Writing one document and hoping it fits both. The MDR technical documentation and the US submission are different documents for different reviewers. Trying to write one document that "works for both" produces a document that satisfies neither.

For the pathway-level deep dives on the US side, see the 510(k) process for FDA clearance, substantial equivalence and 510(k) predicate strategy, FDA De Novo classification, and FDA 510(k) vs MDR CE marking. For QMS transition framing see FDA QSR to QMSR transition in 2026. For the primer see FDA regulation of medical devices: a primer for EU startups and the sibling post on FDA pre-submission meetings for EU MedTech startups.

The Subtract to Ship angle

The Subtract to Ship framework says: strip every activity that does not trace back to a specific regulatory obligation. In a dual submission context the test gets one extra clause. Strip every activity that does not trace back to a specific obligation on at least one of the two regulators, and for activities that remain, design them once to serve both where possible.

What subtraction looks like in practice on a dual programme. Remove the speculative predicate work done before the US specialist is in the room — it will be redone. Remove the MDR-only clinical investigation design when the same study could have served both sides with an early conversation. Remove the separate QMS builds for the two markets — one QMS, gap-closed. Remove the parallel risk files — one risk file. Remove the separate test campaigns when a single test plan could have served both — one campaign, two data packages.

What does not get subtracted. The two submissions themselves. The classification analysis on each side. The Notified Body conformity assessment under MDR Article 52. The FDA review. The post-market obligations. These are not bloat. They are the regulatory work the two systems actually require, and subtracting them produces two submissions that fail.

The Subtract to Ship discipline for dual submission is: one foundation, two submissions, zero rework caused by planning the tracks in isolation. See the Subtract to Ship framework for MDR for the foundational methodology this post extends.

Reality Check — Is your dual submission plan real?

  1. Is the United States in your business plan with a target launch date and a committed revenue assumption, or is it a "later" item that shifted onto the slide this quarter?
  2. Do you have a named US regulatory specialist on the team or on contract today, making decisions with you, not booked for "phase two"?
  3. Is your intended purpose statement drafted once, consistently, across both submissions?
  4. Have you completed classification analysis on both sides, or only the MDR side?
  5. Is your QMS designed from day one to cover EN ISO 13485 and US expectations, with a gap analysis against Part 820 on file?
  6. Is your clinical evidence plan designed to serve MDR Article 61 and Annex XIV and FDA expectations on the same study, or only the MDR side?
  7. Do you have a single person owning the seam between the two tracks — the project management layer that stops them drifting apart?
  8. Have you budgeted the integration layer, or only the two visible submission tracks?

Fewer than five clear answers means the plan is not yet a dual submission strategy. It is a single-market plan with FDA ambition attached. That is fine if you own it. It is dangerous if you are telling investors or your team otherwise.

Frequently Asked Questions

What is a dual submission strategy in MedTech? It is a regulatory plan that runs an MDR CE marking track and an FDA premarket track in parallel, sharing upstream work — intended purpose, QMS, risk management, and evidence — while producing two separate submissions for two separate reviewers. The goal is to reach both markets faster than sequential work allows, without paying for two fully duplicated programmes.

Can a CE mark and FDA clearance be obtained at the same time? Yes, but only when the programme is designed for it from the start. Running both in parallel is structurally different from running one and then the other. It requires a shared foundation built in phase one, both specialists engaged from day one, and a budget that carries the integration layer between the two tracks, not just the two submissions themselves.

Is dual submission cheaper than sequential? Not cheaper. Faster to the second market, usually, when done well, and more efficient in total work than sequential-with-rework, because the shared foundation is built once. The dual cost stack is the sum of the two programmes minus the overlaps, and the overlaps depend entirely on early planning.

When is dual submission the wrong choice? When the US market is speculative, when the team does not yet have a US specialist engaged, when regulatory headcount is scarce, or when the founding team is still treating FDA framing as an afterthought. In those cases sequential planning finishes. Parallel planning does not.

How does MDSAP fit into a dual submission strategy? MDSAP allows a single QMS audit by an authorised audit organisation to be recognised by multiple participating regulators including the US. In a dual programme it reduces QMS audit duplication across jurisdictions. It does not replace the Notified Body conformity assessment under MDR Article 52 — that remains the EU conformity route. Adopting MDSAP is a planning-phase decision, not a late add-on.

Do I need different clinical evidence for each submission? Sometimes, sometimes not. MDR Article 61 and Annex XIV require clinical evidence for every device. The US side may or may not require new clinical data depending on the pathway. A clinical investigation designed with both reviewers in mind can often serve both. A study designed only for MDR endpoints may leave gaps on the US side. The time to design for both is before the study starts.

Who should I hire first for a dual submission programme? The regulatory lead on each side, engaged from the start of phase one, plus the person who owns the seam between the two tracks at the project management level. Hiring one side and promising to bring in the other "later" is the single most common failure pattern in dual submission programmes.

Sources

  1. Regulation (EU) 2017/745 of the European Parliament and of the Council of 5 April 2017 on medical devices (MDR), in particular Article 52 (conformity assessment procedures) and Article 61 (clinical evaluation). Official Journal L 117, 5.5.2017, as amended, including Regulation (EU) 2023/607.
  2. EN ISO 13485:2016 + A11:2021 — Medical devices — Quality management systems — Requirements for regulatory purposes.
  3. EN ISO 14971:2019 + A11:2021 — Medical devices — Application of risk management to medical devices.
  4. U.S. Food and Drug Administration — Center for Devices and Radiological Health (CDRH), public guidance on the premarket submission framework, referenced at the general framework level, https://www.fda.gov/medical-devices
  5. Medical Device Single Audit Program (MDSAP) — programme documentation maintained by the International Medical Device Regulators Forum (IMDRF).

This post is part of the FDA and International Market Access series in the Subtract to Ship: MDR blog. Authored by Felix Lenhard and Tibor Zechmeister. A note on the limits of our expertise, stated once and clearly: Tibor's authority is in the EU MDR and the Notified Body system, and the FDA framing in this post stays deliberately at the general level. For specific US work — predicate selection, submission drafting, FDA review division interactions, 21 CFR Part 820 implementation detail, and the current state of the QMSR harmonisation timeline — work with a US regulatory specialist who practices inside the FDA system daily. The dual submission discipline is the plan. The two specialists are the execution.