Medical Device Regulatory Strategy: A Step-by-Step Plan for US and EU Market Entry
Build a regulatory strategy: intended use, classification, pathway, evidence plan, Pre-Sub feedback, market sequencing, quality system readiness and timeline.

A regulatory strategy is the plan that connects your product idea to a legal market. Done early, it saves months and prevents expensive rework; done late, it turns into a series of surprises: a missing clinical study, the wrong pathway, or a quality system that is not ready for inspection. This guide sets out a practical approach to building a regulatory strategy for the United States and the European Union, including how to decide the sequence of markets, what to document, and how to keep the plan alive as the product evolves.
What a regulatory strategy contains
A good strategy is a short, living document that answers six questions:
- What exactly is the product, and what is it intended to do?
- How is it classified in each target market?
- Which pathway gets it to market, and what does each pathway require?
- What evidence is needed, and when will it be generated?
- What quality system and organisational capabilities are needed?
- What are the timeline, cost, risks and decision points?
Step 1: Lock down the intended use
Everything else hangs from the intended use and indications for use: the condition, the patient population, the user, the setting and the claims. Write them precisely and keep them consistent in labeling, marketing and the clinical evidence. A broad claim can raise the device class or require stronger evidence; a narrow claim may limit the market. Decide deliberately, because changing intended use later usually means new evidence and a new submission.
Step 2: Classify the device in each market
Classification determines the pathway. Work out the FDA class and product code, and the EU MDR class using the Annex VIII rules, as described in our article on medical device classification under FDA and the EU MDR. Record the reasoning and note anything uncertain, such as software functions that could attract a higher class.
Step 3: Choose the pathway
| Question | United States | European Union |
|---|---|---|
| Main route | 510(k), De Novo or PMA, depending on class and predicate availability | Conformity assessment under the MDR, with a notified body for most devices above basic Class I |
| Key evidence | Substantial equivalence to a predicate, or a risk-benefit case for De Novo and PMA | Clinical evaluation, technical documentation and QMS certificate |
| Quality system | QMSR (incorporating ISO 13485), establishment registration and device listing | MDR Article 10(9) QMS, usually certified to ISO 13485 through the notified body |
| Local roles | US agent for foreign establishments | EU authorised representative for non-EU manufacturers and a person responsible for regulatory compliance |
| Outcome | Clearance, grant or approval | CE mark under the MDR |
For US routes, read the 510(k) submission process, selecting a predicate and the De Novo guide. For the EU, see EU MDR and IVDR explained and technical documentation under the MDR.
Step 4: Plan the evidence
Evidence is usually the longest and most expensive part. Build an evidence plan that lists, for each regulatory claim, what supports it and when it will be ready:
- Bench and performance testing: verification against requirements, including standards such as electrical safety, biocompatibility and sterilization and packaging.
- Usability: formative and summative studies under IEC 62366-1.
- Software and cybersecurity: lifecycle documentation and security evidence for connected products.
- Clinical evidence: literature, equivalence, existing data, or a new investigation. In the EU, this feeds the clinical evaluation report; in the US, an IDE study may be required for significant-risk devices.
Whether a clinical study is needed is often the single biggest driver of timeline and cost, so decide it early and test the assumption with regulators.
Step 5: Use early regulator feedback
FDA’s Q-Submission program, including Pre-Submission meetings, lets you ask specific questions about classification, testing, clinical data and predicate selection before you invest in a study or a full submission. In the EU, early conversations with your notified body about classification, the conformity route and the clinical evidence strategy serve a similar purpose, though availability and timelines depend on the body. Prepare focused questions with a proposed approach for each, since regulators respond best to a concrete plan.
Step 6: Sequence the markets
There is no universal answer to “US first or EU first”. Weigh the factors:
- Evidence reuse: design, testing and quality system work serves both markets, so plan it once with both in mind.
- Clinical data: if a clinical study is needed, design it to satisfy both regions where possible.
- Capacity: notified body capacity and timelines for MDR certification can be long and variable, while FDA review has defined performance goals for most submission types.
- Commercial priorities: revenue potential, reimbursement and customer demand may favour one market.
- Risk: a first submission in one region often surfaces questions that improve the second.
Many companies choose the US first for a 510(k) device with a clear predicate, and the EU first for products where the MDR route is more straightforward. Make the choice deliberately, record it, and revisit it at each decision point.
Step 7: Make the quality system ready
Regulators approve a product made by a controlled system. For the US, the QMSR now incorporates ISO 13485; for the EU, notified bodies audit your QMS against the MDR. A single ISO 13485 system, extended with market-specific procedures, serves both. Consider whether MDSAP participation makes sense if you will also sell in countries that accept it. Our guide to ISO 13485 and MDSAP audit readiness explains how these fit together.
Step 8: Plan labeling, UDI and post-market obligations
Marketing authorisation is a milestone, not the finish line. Build into your plan labeling, UDI, post-market surveillance, complaint handling, vigilance and the recall process. Regulators expect these systems to be operating when the product launches.
Step 9: Build the timeline, budget and risk register
Turn the plan into a schedule with milestones such as design freeze, verification complete, submission, regulator response and launch, and add the dependencies between them. Budget for testing, clinical work, notified body and regulator fees, consultants, translations and the effort for responding to questions. Keep a regulatory risk register listing the main uncertainties, such as a possible reclassification, a predicate that may not hold, or a study that may not recruit, with an owner and a mitigation for each.
Keep the strategy alive
A strategy written once and filed is a liability. Review it at each design review and whenever you change intended use, add a software function, change a material or supplier, or learn something from a regulator. Treat significant changes as triggers to re-check classification, pathway and evidence.
Common mistakes
- Starting development before fixing the intended use and classification.
- Assuming a clinical study is unnecessary without regulator feedback.
- Designing evidence for one market and discovering it does not satisfy the other.
- Underestimating time for notified body review and for responding to questions.
- Leaving quality system readiness until after the submission.
- Letting marketing claims drift away from the cleared or certified intended use.
Frequently asked questions
When should I write a regulatory strategy?
As early as the concept stage, and certainly before design inputs are frozen. Early strategy work shapes requirements, testing and clinical plans, and it is much cheaper to adjust then than after verification is complete.
Should I go to the US or the EU first?
It depends on your device, evidence, predicate availability, notified body access and commercial priorities. Build a simple comparison of timeline, cost and risk for each sequence, and choose deliberately.
Do I need a consultant to prepare a regulatory strategy?
Not necessarily. Teams with regulatory experience can write one in-house, and many use outside experts for specific questions such as classification, clinical strategy or notified body selection. What matters is that someone owns the plan and keeps it current.
How often should the strategy be updated?
Review it at every design review and at each major decision point, and update it whenever intended use, technology, evidence or regulations change.
Regulations, guidance and timelines change. Confirm the current requirements with the regulators and your own regulatory advisers before committing to a strategy or a submission date.
Related reading
- Classification under FDA and the EU MDR: the first decision in any strategy.
- US FDA medical device regulations: pathways and QMSR.
- EU MDR and IVDR explained: roles, conformity assessment and deadlines.
- Landing your first regulatory affairs job: skills to build for strategy roles.
Talk to the AptSkill team
Want hands-on training in regulatory affairs for the US and EU? Send us your role and goal.
Ask about regulatory affairs training
Ready to take the next step?
Questions? Email aptskill6@gmail.com and the AptSkill team will respond promptly.