MDRC logo
Explore
← MDRC knowledge centre

MDR planning · manufacturer readiness · notified-body review

How long does CE marking take?

The honest answer is not one number. It is one critical path.

CE marking has no universal statutory duration. The calendar is built from product development, evidence generation, QMS implementation, notified-body availability, assessment cycles and the time needed to close questions.

Updated 10 December 2024 Regulation (EU) 2017/745
Build a realistic timeline ↓

The short answer

Start by asking which clock dominates

A device that is technically finished but clinically under-supported is not “almost ready.” Neither is a polished dossier attached to an immature QMS.

Route AClass I

Standard class I, genuinely ready

No notified-body certificate is required. If development, verification, clinical evaluation, technical documentation and the QMS are already complete, final regulatory assembly may take weeks to a few months.

Dominant clockManufacturer readiness
Route BNB

A route requiring notified-body certification

Manufacturer preparation comes first. After the written agreement, the latest EU survey shows that most MDR certification routes still occupy a further 13–24 months, depending on certificate scope.

Dominant clockReadiness + external assessment
Route CDATA

A device that still needs pivotal evidence

Biocompatibility, electrical safety, software validation, usability work or a clinical investigation can become the critical path. Certification cannot compress evidence that has not yet been generated.

Dominant clockTesting or clinical evidence
The planning formula

Calendar time = manufacturer preparation + contracting + active assessment + pauses + final release

The critical path

Six clocks can run, but not all can run in parallel

A useful timeline is dependency-based. It shows what must finish before the next activity can start and which workstreams can proceed together.

01Define

Intended purpose and classification

The route cannot be priced or planned reliably until the device and its claims are stable.

02Generate

Verification, validation and clinical evidence

Testing lead times, sample availability and clinical follow-up often determine the real project duration.

03Control

QMS implementation and records

A procedure written yesterday is not automatically an implemented process with auditable evidence.

04Assemble

Technical documentation

The dossier should tell one consistent story across risk, clinical evidence, design controls and labelling.

05Assess

Notified-body contracting and review

Scope acceptance, audit, product review, questions and nonconformity closure create an external clock.

06Release

Declaration, CE mark and registrations

The manufacturer affixes the CE mark after the applicable conformity assessment and release controls are complete.

What the latest data say

The certificate clock is still measured in months, not sprints

The European Commission’s 20th notified-body survey reports the time from signed written agreement to issuance of a new MDR certificate, with data status 28 February 2026.

Reported duration from written agreement to certificate Share of notified bodies that had issued the relevant certificate
QMS certificates92%

of reporting notified bodies fell in the 6–18 month bands.

QMS + product certificates82%

fell in the 13–24 month bands.

Not includedPrep

Manufacturer preparation before the written agreement sits outside these figures.

These are observed bands reported by notified bodies, not legal deadlines and not a prediction for a particular device. View the Commission-published survey ↗

The 2027 rulebook

New maximum phases will make the active clock more predictable

Commission Implementing Regulation (EU) 2026/977 applies from 25 February 2027. It sets maximum phases for notified-body conformity assessment, but it does not create one universal deadline for CE marking.

Applicability checkpoint

The new quotation and timeline rules do not apply to conformity-assessment procedures covered by a written agreement signed before 25 February 2027.

Phase 0130days maximum

Complete application review and contract

The phase begins when the notified body receives a complete application and ends when the contract is signed.

Phase 02A120days maximum

QMS auditing

From the first audit-programme activity through completion of the notified body’s final review.

Phase 02B90days maximum

Product verification

From initiation of technical-documentation assessment through completion of the relevant final review.

Phase 0320days maximum

Decision and certification

From the day after the final relevant review to certificate issuance and entry in EUDAMED.

Under Annex IX, QMS auditing and product verification are performed in parallel where both apply, provided the required technical-documentation input informs the audit programme.
The tempting calculation30 + 120 + 20 = 170 active days

For a straightforward Annex IX path with parallel QMS and product activities, that arithmetic describes the maximum active phases. It still excludes pre-application work, manufacturer preparation and clock interruptions. It is not a 170-calendar-day promise.

The pause button

Why active assessment days become a longer calendar

The 2027 rules expressly allow interruption of the assessment clock. The most effective schedule control is therefore faster, better-quality closure of questions.

ⅡClock pausedcalendar still moving
01

Incomplete starting package

The 30-day application phase starts only after a complete application has been received.

02

Questions and nonconformities

The clock may pause while the manufacturer prepares evidence, corrections or a corrective-action plan.

03

External consultation

EMA, a regulatory authority, an expert panel or an EU reference laboratory can introduce an additional interruption.

04

Evidence or design change

A weak response can reveal a deeper gap, triggering new testing, clinical work or dossier realignment.

05

Sites and critical suppliers

Additional manufacturing sites, outsourced processes and audit logistics can expand assessment work and coordination.

06

Release-tail activities

Translations, UDI data, EUDAMED entries, authorised-representative coordination and controlled release still need owners.

The class I myth

No notified body does not mean no regulatory work

For standard class I devices, the manufacturer normally performs conformity assessment without notified-body certification. The shortcut is only the missing third-party assessment—not the disappearance of MDR obligations.

Class I devices supplied sterile, devices with a measuring function and reusable surgical instruments require notified-body involvement limited to the relevant special aspects.

Still required before releasemanufacturer-controlled
  • 01Intended purpose and justified classification
  • 02GSPR evidence and risk management
  • 03Clinical evaluation and applicable testing
  • 04Technical documentation and controlled labelling
  • 05Proportionate QMS, UDI and EUDAMED data
  • 06EU declaration of conformity and post-market system

Planning method

Shorten the route by removing rework, not controls

The fastest defensible programme is usually the one that finds contradictions before the notified body does.

01

Freeze the regulatory identity

Align intended purpose, claims, user, patient population, operating principle and classification before detailed dossier drafting.

02

Build an evidence map

Connect every relevant GSPR and risk control to a test, standard, clinical source or documented justification.

03

Run QMS and dossier work together

Use live development records to demonstrate implementation rather than writing procedures after the product is finished.

04

Approach suitable notified bodies early

Confirm designation scope, technology fit, sites, certificate needs and application expectations before the target submission date.

05

Conduct a consistency review

Challenge clinical claims, risk controls, specifications, test reports, IFU and marketing language as one connected evidence system.

06

Prepare the response room

Assign decision owners, evidence owners and response deadlines before the first question or nonconformity arrives.

A lean timeline model Build this before choosing a launch date
WorkstreamReady whenKey dependency
Device definitionClaims and classification are approvedBusiness and clinical strategy
EvidenceRequired reports support every claim and controlDesign maturity and test capacity
QMSProcesses are implemented and records existOperating history and internal audit
ApplicationScope, sites and documentation package are completeSuitable notified-body scope
ReleaseCertificate where required, declaration and registrations alignAssessment closure and controlled data

Practical questions

Four timeline traps to avoid

A date becomes useful only after its assumptions are visible.

Can we CE-mark a medical device in three months?+

Possibly for a standard class I device when development, testing, clinical evaluation, technical documentation and the QMS are already complete. It is generally not a realistic end-to-end assumption for a route requiring notified-body certification.

Does every class I device avoid notified-body assessment?+

No. Notified-body involvement is required for class I devices supplied sterile, devices with a measuring function and reusable surgical instruments. The assessment is limited to the applicable special aspects.

Does the 120-day QMS limit mean a certificate in 120 days?+

No. It is one active phase under the rules applying from 25 February 2027. Application review, product verification where required, decision and certification are separate, and assessment clocks may be interrupted.

When should we contact a notified body?+

Once the intended purpose, classification, technology, sites and conformity-assessment route are sufficiently stable to describe the scope accurately. Do not wait for a “perfect” dossier before checking scope and application expectations.

From target date to controlled plan

Need a CE-marking timeline that reflects your actual device?

We can turn the intended purpose, risk class, evidence gaps, QMS status and conformity-assessment route into a dependency-based programme.

Build the critical path ↗
↑

Discuss your regulatory pathway

Whether you are developing medical software, an AI-enabled healthcare solution, a digital health platform or a software-driven medical device, we can help define the regulatory strategy, evidence requirements and next steps.

→

Where companies need support

Regulatory strategy
Technical documentation
Clinical and performance evidence
Software lifecycle and cybersecurity
Notified Body readiness

Start a discussion

 

Regulatory support for software medical devices, AI health technologies and digital healthcare solutions.


©2026 MDRC - Medical Devices Regulatory Compliance

Useful information

CE-Certificate vs. EC-Certificate

Basic UDI-DI (bUDI)

EUDAMED registration - a brief guide

Authorised Representative Mandate

GSPR – General Safety and Performance Requirements

How to obtain CE marking for medical software under the EU MDR or IVDR?

Technical documentation for Medical Device Software in the EU

Read more >>


Cookie Policy

We only use essential cookies that enable core functionality and proper operation of the website. These cookies do not store any personally identifiable data. By continuing to use this website, you consent to the use of the essential cookies. You may disable these cookies by changing your browser settings, but this may affect how the website functions.
We do not use our own or third-party analytical, preferences, statistics, marketing, functional, advertisement, performance or any other non-essential cookies.

Send us an email:
info@mdrc-services.com

Or use the contact form below

 

Solutions

EU Authorised Representative (EC REP)

EU PRRC

Technical documentation

Risk management

Clinical evaluation

Notified Bodies

Quality management system

Post-market surveillance

Resources

Medical Device Regulation (MDR) - basics

CE-marking process for medical devices

CE-marking process for in vitro diagnostic medical devices

MDR technical documentation checklist

IVDR technical documentation checklist

Technical documentation checklist for medical device software (MDSW)

MDR-compliant quality system documentation checklist

MDR-compliant quality system documentation checklist for medical device software

Clinical Evaluation Plan checklist

Clinical Evaluation Report checklist

PRRC under MDR or IVDR

Articles

CE-Certificate vs. EC-Certificate

Basic UDI-DI (bUDI)

EUDAMED registration - a brief guide

Authorised Representative Mandate

GSPR – General Safety and Performance Requirements

More articles >>

Devices

General medical devices and equipment

In vitro diagnostics (IVD)

Medical software

Cookie Policy

We only use essential cookies that enable core functionality and proper operation of the website. These cookies do not store any personally identifiable data. By continuing to use this website, you consent to the use of the essential cookies. You may disable these cookies by changing your browser settings, but this may affect how the website functions.
We do not use our own or third-party analytical, preferences, statistics, marketing, functional, advertisement, performance or any other non-essential cookies.