A notified body gets treated, early on, like a single hurdle — pass the audit, get the certificate, move on. Under EU MDR, the relationship doesn’t close when the certificate issues. The notified body that assesses a manufacturer’s technical documentation and quality management system keeps standing authority over both for as long as the certificate is valid, including the right to audit without warning.

Picking a notified body is picking a counterpart, not a vendor

Designation isn’t a blanket credential — a notified body is designated for specific device types and technologies, listed in the European Commission’s NANDO database, and working with one outside its actual scope doesn’t satisfy MDR regardless of its general reputation. Notified body capacity has been a persistent constraint since MDR’s rollout; whatever the current wait time is at a given body, it belongs in the regulatory strategy and submission timeline as a planning input, not something assumed away. None of this starts after a technical file is finished, either — the notified body is the eventual audience for documents like the clinical evaluation report this essay assumes a reader already knows how to build. It is one more place where the gap between the EU and FDA systems shows up in the mechanics, not just the paperwork: FDA reviews a device directly, while under MDR a private, member-state-designated body does, acting under the regulation’s authority rather than the agency’s own.

What changes once the certificate is live

The obligations that follow certification are where the relationship actually lives day to day. A manufacturer has to report changes that could affect conformity to its notified body, and for most changes that means getting them reviewed before implementation, not informing the body afterward as a courtesy. The notified body also decides, on its own authority, whether a vigilance signal or other trigger warrants an unannounced on-site audit rather than waiting for the next scheduled one. Managing that ongoing relationship — what gets flagged, when, and how the file is kept ready for a visit that isn’t on the calendar — is a larger and more continuous part of the job than the initial submission that gets most of the attention.

Where this goes wrong

Assuming any notified body covers any device

Designation is scoped by device type and technology in NANDO. A body in good standing generally isn’t automatically in scope for a specific product.

Reporting a change after implementing it

Most changes that could affect conformity need notified body review before they ship, not a notification once the change is already live.

Preparing only for the scheduled recertification audit

Unannounced audits are a standing right under MDR, not an exception — a file that’s only ready on a known date isn’t actually ready.

A notified body relationship that is managed only at certification and renewal is being managed for half the obligation. The other half is the standing duty to keep the body informed of what changes, and the file ready for the audit that wasn’t scheduled.

Sources & further reading

  1. EUR-Lex — Regulation (EU) 2017/745, Article 52 and Annex VII eur-lex.europa.eu
  2. European Commission — NANDO, notified body database ec.europa.eu
  3. Regulatory Academy — How to Read a Clinical Evaluation Report regulatoryacademy.com
  4. Regulatory Academy — What EU MDR Requires That FDA Doesn’t regulatoryacademy.com

This essay is provided for general educational purposes and reflects the regulatory landscape as of its publication date. It is not legal, regulatory, or career advice.