Introduction

One of the most underestimated costs in medical device regulatory projects is not testing.

It is not certification fees.

And it is not even timelines.

It is rework.

Under EU MDR and other global regulatory frameworks, rework has become one of the biggest reasons projects:

• Get delayed
• Exceed budgets
• Miss market timelines
• Create internal frustration

In many cases, the original issue is small.

But because it is discovered late, the impact becomes expensive.

A missing justification in the CER can trigger updates across:

• Risk management
• PMS documentation
• IFU claims
• Clinical strategy

And suddenly, one gap affects the entire submission.

The good news?

Most rework is preventable.

Why Rework Happens in Regulatory Projects

Rework usually does not happen because teams are careless.

It happens because:

• Regulatory strategy starts too late
• Documentation is developed in silos
• Teams focus on completion instead of alignment
• Assumptions replace structured planning

Under MDR, documentation is highly interconnected.

A change in one area often affects multiple others.

That means poor planning early on creates major problems later.

1. Start Regulatory Strategy Early

One of the biggest mistakes manufacturers make is treating regulatory as a final-stage activity.

In reality, regulatory strategy should begin during:

• Product development
• Design planning
• Clinical planning

Waiting until submission preparation creates avoidable gaps.

For example:

• Intended use may not align across documents
• Claims may lack supporting evidence
• Clinical data requirements may be underestimated

Early strategy reduces the risk of rebuilding documentation later.

2. Define Intended Use Clearly from the Beginning

A poorly defined intended use creates widespread rework.

Why?

Because intended use impacts:

• Device classification
• Clinical evaluation
• Risk management
• Labeling
• Testing requirements
• PMS strategy

Even small wording changes can affect the entire regulatory framework.

A common mistake is allowing marketing language to shape intended use without regulatory review.

Under EU MDR, claims must be:

• Scientifically supported
• Clinically justified
• Consistent across documentation

The clearer the intended use is early on, the less rework later.

3. Align Cross-Functional Teams

Regulatory projects involve multiple departments:

• R&D
• Quality
• Clinical
• Regulatory
• Manufacturing
• Marketing

One major cause of rework is poor communication between these functions.

Examples include:

• Marketing claims unsupported by clinical evidence
• Risk files not aligned with device design
• IFUs inconsistent with technical documentation

When teams work independently, inconsistencies appear.

And inconsistencies trigger regulatory questions.

Regular cross-functional reviews help identify gaps before submission.

4. Build Documentation Together — Not Separately

Many companies prepare documents as isolated tasks.

But under MDR, documents are interconnected.

For example:

• CER conclusions should align with risk management
• PMS plans should reflect identified clinical uncertainties
• Biological evaluation should support material-related risks

If documents are created independently, contradictions emerge.

This leads to:

• Notified Body findings
• Clarification requests
• Expensive revisions

A stronger approach is building documentation as one integrated system.

5. Do Gap Assessments Early

One of the simplest ways to reduce rework is conducting structured gap assessments early in the project.

Before submission, review:

• Clinical evidence gaps
• Testing gaps
• Labeling inconsistencies
• Risk management alignment
• PMS readiness

Finding gaps early is significantly cheaper than fixing them after review.

6. Avoid Copy-Paste Regulatory Documentation

Another common reason for rework is template overreliance.

Manufacturers sometimes:

• Reuse old CERs
• Copy previous risk analyses
• Duplicate justifications from unrelated devices

This creates:

• Inconsistencies
• Unsupported claims
• Weak scientific rationale

Regulators can quickly identify generic documentation.

Under MDR, device-specific justification is critical.

Templates should support structure—not replace critical thinking.

7. Treat Clinical Evaluation as a Core Activity

Clinical evaluation is often underestimated until late in the project.

That creates major problems because the CER influences:

• Safety claims
• Performance claims
• Benefit-risk conclusions
• PMCF planning

Weak clinical strategy often triggers:

• Additional literature searches
• Expanded justification requirements
• Requests for new data

Starting clinical planning early reduces last-minute corrections.

8. Integrate Risk Management Continuously

Risk management should not be treated as a standalone document.

It should evolve alongside:

• Device development
• Clinical evaluation
• PMS activities
• Biological evaluation

A common issue occurs when risk files:

• Are outdated
• Ignore clinical findings
• Lack linkage to PMS data

This creates inconsistencies regulators immediately notice.

Continuous integration minimizes rework later.

9. Prepare for Regulatory Review — Not Just Submission

Many teams focus on “completing the file.”

But submission is not the real goal.

The real goal is: surviving regulatory scrutiny.

Ask:

• Can every claim be defended?
• Are all conclusions traceable to evidence?
• Are gaps transparently addressed?

This mindset shift prevents reactive corrections after review.

10. Use PMCF and PMS Strategically

Under EU MDR, PMS and PMCF are not just post-market obligations.

They are part of the evidence strategy.

Weak PMS planning often leads to:

• Unsupported residual risks
• Incomplete clinical justification
• Additional requests from reviewers

A proactive PMS/PMCF strategy reduces future rework significantly.

11. Understand That Small Errors Become Large Delays

In regulatory projects, small inconsistencies can escalate quickly.

For example:

• One unsupported claim in IFU
• One mismatch in intended use
• One missing biological justification

…can trigger multiple document revisions.

This is why attention to detail early saves both:

• Time
• Cost

late

12. The Real Cost of Rework

Rework impacts more than documentation.

It affects:

• Submission timelines
• Market launch schedules
• Internal resources
• Regulatory credibility
• Team productivity

And under MDR, delays can become extremely expensive due to:

• Limited Notified Body capacity
• Long review cycles
• Increased scrutiny

Preventing rework is now a strategic advantage.

Final Thought

Most expensive regulatory problems are not caused by lack of effort.

They are caused by:

• Late planning
• Weak alignment
• Reactive strategy

Under EU MDR, successful regulatory projects require:

• Early thinking
• Cross-functional coordination
• Integrated documentation
• Strong scientific justification

Because in the end: Fixing problems early is always cheaper than rebuilding later.