Short answer
In the European Commission’s 2026 Notified Body survey (data as of 28 February 2026), 52 Notified Bodies were designated under the MDR. From signing the written agreement to a new QMS and product certificate, 51% of the Notified Bodies that had issued them reported 13–18 months, 31% reported 19–24 months and 10% more than 24 months; reaching the signed agreement takes extra time. Class IIa, IIb and III software needs a Notified Body whose NANDO designation covers the device type. The most effective way to protect your timeline is to submit a complete technical file that has been reviewed for gaps beforehand.
What the official numbers show
According to the European Commission's Notified Body survey (data as of 28 February 2026, published July 2026), 52 Notified Bodies were designated under the MDR. Every manufacturer of Class IIa, IIb or III software, and every legacy MDD device moving to the MDR, needs one of them — and not every NB is designated for every device type.
The same survey asked NBs how long it takes to reach a new MDR certificate, measured from signing the written agreement to issuing the certificate. For QMS + product certificates, 51% of the NBs that had issued such certificates reported 13–18 months, 31% reported 19–24 months and 10% more than 24 months. QMS-only certificates were quicker: 62% of NBs reported 13–18 months and 30% reported 6–12 months.
Two points matter when you use these figures. First, they describe the duration of the certification process itself, reported as the share of NBs in each time band — they are not waiting-list figures and not an average. Second, the time before the written agreement comes on top: in the same survey, about 65% of MDR applications reached a signed written agreement within two months of being lodged. Your own timeline will depend on your device, the NB's workload, the quality of your documentation and how quickly you answer questions, so treat the survey as a planning range, not a promise. For a phase-by-phase view, see our guide to a realistic EU MDR certification timeline for software.
What drives the pressure on NB capacity
MDR technical documentation is extensive. Annexes II and III set out detailed requirements for the technical documentation and the post-market surveillance documentation, and the NB assesses them against the general safety and performance requirements of Annex I. For software, that includes the software lifecycle, risk management, clinical evaluation and cybersecurity evidence. More content means more review effort per file.
Designation is demanding. NBs must meet the organisational and competence requirements of MDR Annex VII and pass a joint assessment before they are designated, and each designation covers a defined scope of device types. Capacity for software therefore depends not only on how many NBs exist but on how many have software in scope and reviewers with the right expertise.
Legacy transitions are still running. Legacy devices that qualified for the extension under Regulation (EU) 2023/607 must be certified under the MDR before 31 December 2027 or 31 December 2028. NBs are completing these assessments in parallel with applications for new devices.
Poor application quality creates rework cycles. In practice, incomplete documentation or documentation that does not address the MDR requirements leads to additional rounds of questions and non-conformities, and every round adds time to the assessment.
How to choose a Notified Body that can actually deliver
Not all NBs are equal — and choosing one that does not fit your device can add significant delay. Here is what to evaluate (our guide on how to choose a Notified Body goes into more detail):
- Designated scope for your device type: Verify that the NB is actually designated to certify your specific device class and type under EU MDR. Not all NBs hold authorisation for all software categories. Check the Commission's NANDO database (New Approach Notified and Designated Organisations, now part of the Single Market Compliance Space).
- Current availability: Ask directly — "When could we sign a written agreement, and how long are your current reviews for a device like ours?" The honest answer tells you more than any marketing material.
- SaMD-specific experience: Ask how many SaMD and AI medical device certificates the NB has issued under EU MDR. Software applications require reviewers with specific IEC 62304 and clinical evaluation expertise. A hardware-focused NB may have the scope but lack the right reviewers.
- Language and location: Confirm which languages the NB accepts for your documentation and audits, and where its software reviewers are based. Working in a language that is not your team's working language creates avoidable friction.
- Communication responsiveness: Test this during the selection process. How quickly do they respond to pre-submission enquiries? Slow pre-submission communication is often an early sign of slow review communication.
Six strategies to protect your certification timeline
- Engage NBs early. Contact candidate NBs as soon as your intended purpose and classification are stable, not when the technical file is finished. Many NBs offer pre-application meetings, and MDCG 2022-14 encourages structured dialogue between NBs and manufacturers before and during conformity assessment. These meetings do not guarantee a faster review, but they clarify scope, expectations and the NB's availability.
- Submit a complete, polished technical file on day one. In our experience, incomplete or poorly organised documentation is one of the most common causes of extra review rounds. A complete, well-organised, well-written technical file is easier to review and tends to generate fewer non-conformities.
- Conduct an independent pre-submission audit. Before submitting to an NB, have your technical file reviewed by someone who knows what NBs look for under EU MDR — for example through an independent technical documentation gap analysis. Finding gaps before submission is usually cheaper and faster than resolving major non-conformities afterwards.
- Respond to NB questions quickly. Each day a question sits unanswered extends your timeline. Agree internally who owns NB responses and how quickly technical, clinical and software input must be turned around.
- Consider less congested NBs. NBs differ in workload, and a smaller or more recently designated NB may be able to start sooner than the best-known names. All NBs designated under the MDR must meet the same Annex VII requirements, and a certificate from any of them is valid throughout the EU — provided the NB's designation covers your device.
- Watch the December 2025 simplification proposal — but do not plan around it. The Commission's proposal would, among other things, remove the five-year maximum validity of NB certificates in favour of periodic reviews. It has not been adopted, and its final content and timing are unknown. Base your 2026–2028 applications on the MDR as it applies today.
What good pre-NB preparation looks like
The companies that move through NB review fastest are the ones that treat NB submission as the final step in a well-executed process — not the beginning of the documentation work. A complete, submission-ready technical file under EU MDR includes:
- A clear, specific intended use statement and device description (this is the anchor of everything — vague intended use generates cascading queries)
- Complete Rule 11 classification justification with written rationale
- Technical Documentation per Annex II with all required sections complete, including software documentation per IEC 62304
- Clinical Evaluation Report following MDCG 2020-1 (guidance on clinical evaluation of medical device software) — including a systematic literature search, not just a summary
- ISO 14971:2019-compliant risk management file — not the 2007 version
- Post-market surveillance plan that is specific to your device, not generic
- Declaration of Conformity aligned to your classification and conformity assessment route
Preparing all of this — including a solid Clinical Evaluation Report, ISO 14971:2019 risk management file, and IEC 62304 documentation — before engaging an NB is not just best practice — it is the most reliable way to avoid extra review rounds once the NB clock is running.
- ↗ NANDO database — EU MDR designated NBs — European Commission NANDO (Single Market Compliance Space)
- ↗ Notified Body survey on certifications and applications (MDR/IVDR), data as of 28 February 2026 — European Commission
- ↗ Regulation (EU) 2023/607 — extension of the MDR transitional period — EUR-Lex
- ↗ MDCG 2022-14 — Notified body capacity and availability of medical devices — Medical Device Coordination Group
- ↗ Procedure 2025/0404(COD) — proposal to simplify the MDR/IVDR — European Parliament Legislative Observatory
- ↗ EU MDR 2017/745 — EUR-Lex