Market intent
Commercial priorities, target users, jurisdictions, launch sequence and the claims needed for the product proposition.
Product definition · Pathway · Evidence · Timing
Make the regulatory decisions before they become expensive constraints
A useful regulatory strategy connects the product and its claims to the correct market route, evidence, quality-system work, responsibilities and lifecycle controls.
01Product-specific
02Market-specific
03Lifecycle-controlled
Decision architecture
One controlled rationale
-
01
Define
What is the product and what will be claimed?
-
02
Route
Where will it enter and which pathway applies?
-
03
Demonstrate
What evidence and controls must support it?
-
04
Sequence
Which decision unlocks the next investment?
Result
A defensible route with owners, dependencies and gates
What strategy means
A regulatory strategy is not a list of regulations
It is the documented logic that explains how the product will reach and remain in each target market, which uncertainties must be resolved first and what evidence supports each decision.
Regulatory strategy
Product qualification, classification, pathways, evidence, interactions, responsibilities, dependencies and decision gates.
Compliance system
The quality processes and records that implement the route and keep the released product under control.
Regulatory execution
Submissions, conformity assessment, registrations, authority or notified-body communication and lifecycle maintenance.
The strategy stack
Connect every regulatory layer to the same product definition
Product baseline
Intended purpose and claims
Define users, patients or specimens, use environment, indications, contraindications, operating principle, variants and claimed benefits.
- Controlled product and claim statement
- Configuration and accessory boundaries
Legal perimeter
Qualification and jurisdiction
Confirm whether the product is a medical device, IVD, accessory, combination product, software function or another regulated product.
- Applicable legislation and authority
- Borderline and combination questions
Market route
Classification and pathway
Apply the market-specific rules, establish the rationale and identify the conformity-assessment or premarket submission route.
- Classification rationale
- Notified-body or authority involvement
Proof
Evidence architecture
Map safety, performance and clinical or performance claims to risk controls, standards, testing and evaluation activities.
- Evidence gap register
- Integrated verification and validation plan
Operational control
Quality system and manufacturing
Align design and development, supplier control, production, risk management, records and release controls with the target routes.
- QMS scope and remediation
- Manufacturer and supplier responsibilities
External review
Assessment and interaction
Plan submissions, applications, consultation points and responses to the notified body, authority or other reviewing organisation.
- Submission or assessment package
- Questions, meetings and decision log
Lifecycle
Launch, surveillance and change
Establish registrations, economic-operator arrangements, post-market work, vigilance, renewals and rules for assessing product changes.
- Launch-readiness conditions
- Change and post-market feedback loop
Decision gates
Fund the next step only when its regulatory assumptions are controlled
A gate does not need every answer. It needs the right answer—or an explicit uncertainty, owner and action—for the decision being made.
-
Gate 01
Concept
Product, purpose, users, core technology and target markets are explicit.
Output · controlled product concept -
Gate 02
Pathway
Qualification, classification, routes and critical regulatory questions are documented.
Output · pathway rationale -
Gate 03
Evidence
Requirements, claims, risks and evidence activities form one traceable plan.
Output · evidence and gap plan -
Gate 04
Readiness
The design baseline, QMS, technical records and external-review package agree.
Output · submission-ready baseline -
Gate 05
Market entry
Assessment outcomes, registrations, labels, operators and release conditions are controlled.
Output · documented launch decision -
Gate 06
Lifecycle
Post-market data, changes and emerging requirements can update the product and strategy.
Output · maintained compliance
Where plans break
Late regulatory decisions turn into technical rework
The cost is rarely the classification memo itself. It is the testing, documentation, contracts or launch commitments built on the wrong assumption.
The completed studies may not support the intended purpose or promotional claim.
The rationale, special rules and route dependencies remain unresolved.
Evidence, labels, operator structure or submission formats may need rework.
Protocols can miss acceptance criteria, required variants or market-specific expectations.
Questions suited to early feedback surface only during formal review.
Data capture, responsibilities and budgets are not ready when obligations begin.
Market architecture
Use one controlled product core, then design each market route
A shared product definition, risk file and evidence base can create efficiency. It does not make classification, submissions, labels, registrations or change rules identical across jurisdictions.
European Union
MDR or IVDR qualification and classification, general safety and performance requirements, conformity assessment, CE marking, economic operators, registration and post-market obligations.
United States
FDA product classification and controls, the applicable exempt, 510(k), De Novo or PMA route, establishment and device requirements, QMSR and post-market controls.
Additional markets
Determine local reliance or recognition routes, licence holders or representatives, testing, language and format requirements, registrations, renewals and notification of changes.
Current US quality-system baseline
FDA’s Quality Management System Regulation became effective on 2 February 2026. US planning should therefore use the current QMSR framework rather than the former Quality System Regulation as the baseline.
Controlled deliverable
Make the strategy usable by the people who must execute it
The document should expose assumptions, dependencies and decisions. A concise, maintained map is more useful than a long report that cannot guide design, evidence or commercial planning.
Scope a strategy workshopScope and assumptions
Products, variants, markets, business constraints and unresolved questions.
Controlled product baseline
Intended purpose, users, use environment, claims, technologies and boundaries.
Route rationale
Qualification, classification, conformity assessment or submission pathways.
Evidence and gap register
Requirements, available evidence, gaps, activities, acceptance criteria and owners.
Operating model
QMS scope, legal manufacturer, suppliers, economic operators and review interfaces.
Integrated route map
Decision gates, external interactions, dependencies, timing and critical path.
Lifecycle rules
Registrations, surveillance, renewals and regulatory assessment of changes.
Decision log
Rationale, evidence, approvals, review dates and triggers for reassessment.
From decision to execution
Connect the strategy to the work packages it creates
01
Product qualification and classification
Define the regulatory perimeter and document the pathway rationale.
Explore service 02Technical documentation and evidence
Translate the route into a traceable dossier, testing plan and evidence structure.
Review the checklist 03Authority and notified-body interfaces
Prepare interactions, applications, submissions and responses for external review.
Explore service 04Economic-operator structure
Align manufacturer, authorised representative, importer and distributor roles.
Explore servicePrimary sources
Anchor decisions in current requirements and guidance
Standards, guidance and authority positions change. Confirm the current version and applicability for the product before fixing a route or protocol.
EU
EU
EU
US
US
Regulation (EU) 2017/745
Official consolidated access to the Medical Device Regulation
Regulation (EU) 2017/746
Official consolidated access to the In Vitro Diagnostic Medical Device Regulation
MDCG guidance
European Commission collection organised by regulatory topic
How to study and market your device
FDA route from classification and controls to submission and compliance
Quality Management System Regulation
FDA information on the QMSR and the current inspection framework
Frequently asked questions
Regulatory strategy in practice
What is a medical device regulatory strategy?
It is a controlled, product-specific rationale that connects intended purpose and claims with qualification, classification, market routes, evidence, quality-system activities, responsibilities, timing and lifecycle obligations.
When should regulatory strategy work begin?
Begin while the product, claims and target markets can still be changed without major rework. Review the strategy at defined development, evidence, submission, launch and change-control gates.
Is classification enough to define the regulatory strategy?
No. Classification helps determine the route and level of oversight, but the strategy must also address qualification, claims, applicable requirements, evidence, quality systems, economic operators, review interactions, registration and post-market duties.
Can one regulatory strategy cover the EU and the United States?
A single controlled product and evidence core can support both markets, but each jurisdiction needs its own qualification, classification, route, submission or conformity-assessment logic, labelling, registration and lifecycle requirements.
Does regulatory strategy end after CE marking or FDA clearance or approval?
No. Post-market surveillance, vigilance or medical device reporting, registration maintenance, quality-system controls and the regulatory assessment of changes continue throughout the product lifecycle.
What information is needed to start?
Useful inputs include the product concept, intended purpose, users and use environment, claims, technologies, variants, target markets, development status, existing evidence, manufacturing model, quality-system status and commercial timing.
Start with the decision
Build a route your development team can actually use
Bring the product concept, claims, markets, current evidence and open questions. MDRC will turn them into a controlled regulatory work plan.