How to choose a Notified Body for medical software certification

52 Notified Bodies were designated under EU MDR at the end of February 2026, according to the European Commission's Notified Body survey — and choosing the wrong one can cost you months before you realise the mistake. This guide covers what to evaluate, what questions to ask, and the selection errors we see most often in SaMD startups.

Lizaveta Dabrynskaya
Lizaveta Dabrynskaya
Founder & Regulatory Consultant · 13+ years

Short answer

Class IIa, IIb and III software cannot be CE marked without a Notified Body, so the choice shapes years of audits, reviews and recertification. Start with NANDO: filter by the MDR and check that the scope codes cover software. Then compare capacity and timelines: in the Commission’s 2026 survey, most Notified Bodies reported 13–18 months from a signed agreement to a new certificate. Ask about reviewers with IEC 62304 and IEC 62366 experience, the typical number of review cycles, how the published standard fees apply to you, and experience with AI/ML. There is no official ranking, and a smaller Notified Body with software expertise and capacity can be the better fit.

1. What a Notified Body actually does

A Notified Body (NB) is a conformity assessment organisation designated by an EU member state authority and notified to the European Commission. Under EU MDR, class IIa, IIb and III medical devices — which covers most medical device software under Rule 11 — cannot be CE marked without a Notified Body conformity assessment (Article 52). The NB assesses your technical documentation, audits your Quality Management System, and issues the certificate that underpins your CE mark; you, as manufacturer, remain responsible for the device.

This is not a rubber stamp. A thorough NB review generates questions and clarification requests across several rounds. Your relationship with your NB spans the initial certification and then continues through surveillance audits at least once every 12 months (Annex IX, section 3.3), unannounced audits at least once every five years (section 3.4), re-assessment before certificates are renewed — MDR certificates are valid for a maximum of five years (Article 56(2)) — and assessment of changes to your product. The Commission's December 2025 proposal to simplify the MDR would remove the five-year maximum validity, but it has not been adopted.

Why the choice is consequential

Once you have signed a contract with a Notified Body, switching is expensive and time-consuming — in our experience it often means repeating much of the technical review. Choosing carefully upfront is significantly cheaper than correcting a poor choice months into the process.

2. First filter: designated scope

Not every Notified Body is designated for every type of medical device. Before evaluating anything else, verify that the NB you are considering is designated under EU MDR for your specific device type and the conformity assessment procedures you need. The European Commission's NANDO database (now reached through the Commission's Single Market Compliance Space) lists every designated NB with its exact scope of designation.

For software specifically, look for NBs with explicit designation for:

  • The scope codes that cover software and devices incorporating or utilising software
  • Any further codes relevant to your device's clinical area or technology
  • The relevant MDR conformity assessment procedures for your class (typically Annex IX, or Annex XI)

Machine-learning experience is not something NANDO shows — ask about it directly (see the criteria below).

An NB whose scope does not cover software cannot certify your SaMD at all. Even within scope, software expertise varies: in our experience, reviewers less familiar with IEC 62304, IEC 62366 and software lifecycle concepts raise questions that reflect misunderstandings rather than genuine gaps in your documentation.

Check NANDO directly — do not rely on NB marketing

Marketing descriptions can be broader than the actual designated scope. The NANDO entry is the authoritative source. If the scope listed in NANDO does not cover your device type, the NB cannot certify it under the MDR, whatever its sales team tells you. In the Commission's Notified Body survey, applications outside the NB's designation scope were the most frequent reason for refusals (about 30% of refusal reasons).

3. Capacity and review times in 2026

Notified Body capacity was one of the main bottlenecks of the MDR transition, and the MDCG addressed it explicitly in MDCG 2022-14. The Commission's latest Notified Body survey (data as of 28 February 2026; 52 MDR-designated bodies, all of which responded) gives the best official picture of where things stand:

  • From application to signed written agreement: about 65% of MDR files took less than two months; a minority took more than six months.
  • From signed written agreement to certificate (MDR QMS-plus-product certificates): most often 13–18 months (51% of responding Notified Bodies), 19–24 months for 31%, more than 24 months for 10%, and 6–12 months for 8%. This is the duration of the review and certification work, not time spent waiting in a queue.
  • Completeness: only 14 of 52 MDR Notified Bodies said that more than half of the submissions they received were complete; incomplete applications were the second most frequent reason for refusals.

Two practical consequences for SaMD startups. First, the clock that matters starts when you sign the agreement — so the selection, pre-application contact and a complete submission all have to happen before that. Second, documentation quality is the variable you control: a complete, consistent file shortens the review more than any choice of Notified Body. For how this fits into an overall plan, see our guide to a realistic EU MDR timeline for software.

4. Five criteria that matter for SaMD

Criterion What to look for Red flag
SaMD experience Ask how many SaMD certifications they have completed under EU MDR. Look for NBs with dedicated software review teams and reviewers with IEC 62304 expertise. Cannot name SaMD volume or point to a dedicated software track
Current wait time Ask directly: what is your current timeline from signed contract to first technical review? Get this in writing if possible. Vague answer, or "it depends" without any indicative range
Reviewer continuity Ask whether the same reviewer team handles initial certification and annual surveillance. Continuity reduces rework and relationship friction. No dedicated account management; reviewers rotate without handover
AI/ML capability If your product uses ML, ask whether they have reviewed AI/ML SaMD under MDR, how they assess dataset and change-management evidence today, and how they plan to assess EU AI Act requirements once these apply to AI medical devices (2 August 2028, after Regulation (EU) 2026/1744). No current process for AI/ML documentation; no view on how AI Act requirements will be assessed
Communication quality During pre-submission, note response time and the precision of questions. Technically specific questions indicate competent reviewers. Generic checklist questions do not. Long delays; questions that suggest the reviewer has not read your documentation

5. Questions to ask before you sign

The pre-submission meeting is your opportunity to evaluate the NB as much as it is their opportunity to evaluate your device. These questions give you the information you need and simultaneously signal that you are a prepared applicant — which affects how the NB prioritises your file:

  • How many SaMD certifications have you completed under EU MDR? Can you share approximate numbers by risk class?
  • Do you have reviewers with specific IEC 62304 and IEC 62366 expertise on staff, or do you use external subject matter experts?
  • What is your current average timeline from signed contract to first technical questions on a Class IIa SaMD submission?
  • How do you handle AI/ML-based SaMD today, and how will you assess EU AI Act requirements alongside the MDR once they apply to AI medical devices (2 August 2028)?
  • What does your review process look like — sequential rounds of questions, or consolidated feedback at defined milestones?
  • Who will be our primary contact throughout the assessment, and what is your process if that person changes?
  • What are your surveillance audit frequency and format for a Class IIa SaMD after initial certification?
  • How does your published list of standard fees apply to our project — fixed or time-based, what triggers additional charges, and are there conditions for SMEs?
What good answers look like

A strong NB will answer the SaMD volume question with specific numbers, name their software-specific reviewers or team, give you an actual timeline range, and describe a structured review process with defined milestones. If the pre-submission meeting feels like a sales call rather than a technical conversation, treat that as meaningful signal.

Fees are public

Under Article 50 MDR, every Notified Body must establish a list of its standard fees for conformity assessment activities and make it publicly available. MDCG 2023-2 provides templates and says the list should be accessible on the NB's website without registration, and should explain how the NB takes the interests of SMEs into account. Read these lists before the first meeting. The Commission's December 2025 proposal would also allow the Commission to set the level and structure of Notified Body fees, with reductions for micro and small manufacturers — this is a proposal, not law.

6. The most common selection mistakes

Choosing on price alone

The cheapest NB is rarely the cheapest path to certification. A lower upfront fee from a body with long wait times, inexperienced SaMD reviewers, or poor communication will cost more in consultant time, delayed revenue, and extended timelines than the fee differential. Total cost of certification includes your team's time responding to questions — a high-quality NB that asks fewer, better-targeted questions is often more economical than a cheap one that asks many unfocused ones.

Not checking scope in NANDO

We have seen startups spend months in pre-submission discussions with a Notified Body before discovering the body's scope did not cover their specific device type. The NANDO check takes minutes and should be the first step, not an afterthought.

Contacting only one NB

Run pre-application conversations with two or three bodies in parallel. This takes more time upfront but gives you meaningful comparison data on timelines, communication quality, and fees. It also creates competitive pressure that occasionally produces better terms. We recommend parallel evaluations as a matter of course.

Underestimating the relationship component

Your NB is not a one-time vendor — it is a long-term regulatory partner. The person reviewing your initial submission will likely review your change notifications, conduct your surveillance audits, and handle your recertification five years from now. How they communicate, how quickly they respond, and how technically sophisticated their questions are matters well beyond the initial assessment. If you do change later, Article 58 MDR requires an agreement between you, the incoming and, where practicable, the outgoing NB covering when the old certificates become invalid and who is responsible from when.

Starting too late

In our experience, the most common mistake. Startups frequently begin NB outreach when their technical file is "almost ready" and expect a certificate within a few months. Given the review durations the Commission's survey reports — most often 13–18 months from signed agreement to certificate — and the realities of iterative document review, this rarely works. Start talking to your target NBs well before your documentation is complete, so that you understand their requirements and can sign the agreement as soon as your submission is genuinely complete.

7. How the selection process works in practice

A typical NB selection process for a SaMD startup:

  1. Scope verification — Check NANDO for all NBs designated for your device type and conformity assessment route. This removes a large part of the 52 MDR-designated bodies from consideration.
  2. Initial shortlist — Narrow to 3–5 based on reputation, geography, and visible SaMD track record (published case studies, contributions to SaMD technical guidance, presence at SaMD-specific conferences).
  3. Pre-application meetings — Request meetings with your top 2–3. Many NBs offer pre-application meetings or structured dialogue on process and requirements; terms and any costs vary, so ask. Use the question list above.
  4. Fee proposals — Request formal fee proposals from bodies that performed well, and check them against each NB's published list of standard fees. Compare total project fee, not just initial assessment cost — include estimated annual surveillance fees.
  5. Reference check — Ask each NB for references from SaMD clients with similar device types. Speak to those clients. Ask specifically about communication quality, turnaround time, and whether they would choose the same NB again.
  6. Decision and contract — Sign with your chosen NB and request a formal project plan with defined milestones and expected timelines.
One practical note on timing

Notified Bodies can and do refuse applications: the Commission's survey counted 989 refused MDR applications by the end of February 2026, mostly because the device was outside the NB's designated scope or the application was incomplete. Companies that engage early, communicate professionally, and submit complete documentation get faster turnarounds than those that submit late and incompletely. If you want help preparing that submission, see our EU MDR consulting — the Notified Body, not a consultant, decides on certification.

Official sources & references

Related guides

Frequently asked questions

Check NANDO, the Commission's database of notified bodies (the old address ec.europa.eu/growth/tools-databases/nando now redirects to the Commission's Single Market Compliance Space). Filter by Regulation (EU) 2017/745 (MDR) and look at the scope codes. Not all MDR-designated NBs cover software — look for the scope codes covering software and devices incorporating or utilising software. Then verify by contacting the NB directly and asking about their SaMD review team and IEC 62304 expertise. Self-reported designation is not sufficient — check the actual NANDO entry.
The best official reference is the Commission's Notified Body survey (data as of 28 February 2026). For MDR QMS-plus-product certificates, the time from signed written agreement to certificate was most often 13–18 months (51% of responding Notified Bodies), with 31% reporting 19–24 months and 10% more than 24 months. The survey does not break this down by class or for software, and the time before the agreement is signed comes on top. Ask each Notified Body for its current range for your type of device, and remember that the completeness of your submission is the factor you control.
Key questions: (1) Do you have reviewers with IEC 62304 and IEC 62366 expertise on staff, or do you use external SMEs? (2) What is your current timeline from signed agreement to first technical questions for Class IIa SaMD? (3) What is your typical number of review cycles before certificate issue? (4) How does your published list of standard fees apply to us, and what triggers additional charges? (5) Can your organisation also offer UKCA conformity assessment through a UK Approved Body using the same technical documentation? The answers reveal whether the NB has genuine SaMD depth or is handling it as a secondary competence.
We do not publish a ranking: capacity, reviewer teams and timelines change, and the right choice depends on your device class, technology, target markets and timeline. Start from the NANDO list of MDR-designated bodies whose scope covers software, then use the questions above to test their software and AI/ML experience. A smaller Notified Body with genuine software expertise and available capacity can be a better fit than a larger one. Always ask for current timelines directly — published figures go out of date quickly.
Yes, but it carries significant overhead. Article 58 MDR requires an agreement between the manufacturer, the incoming Notified Body and, where practicable, the outgoing one, setting out when the outgoing body's certificates become invalid, until when its identification number may be used, how documents are transferred, and from when the incoming body takes over responsibility. Certificates are not simply transferred: the incoming Notified Body has to carry out its own assessment before it issues certificates, and the outgoing body withdraws its certificates on the agreed date. Choose your initial NB carefully — switching is costly and disruptive.
Lizaveta Dabrynskaya
Lizaveta Dabrynskaya
Founder, TrustedTraceMed · Regulatory and quality consultant for medical device software

Regulatory and quality consultant for medical device software, with 13+ years in the healthcare domain. Built an ISO 13485 QMS from scratch for a Class IIa SaMD and worked on EU MDR, UKCA and Malaysia MDA submissions. Independent consultant, not a Notified Body.

Choosing a Notified Body?

In a free 30-minute call we look at your device class and scope, which Notified Bodies to approach, and how to prepare for the first meetings.

Request a free call →
No commitment · Fixed-fee proposals · Reply within 1 business day