Technical documentation remains one of the most critical elements in MDR conformity assessment. While Regulation (EU) 2017/745 defines what manufacturers must include under Annex II and Annex III, it does not prescribe one single format for how technical documentation should be structured and submitted.

In practice, this creates a recurring challenge: technical files may contain the required information, but still be difficult to assess if the documentation is incomplete, inconsistent, poorly structured, or hard to navigate. For manufacturers, this can lead to additional questions, longer review times, and avoidable delays in the conformity assessment process.

What the new Team-NB guidance means for MDR submissions

On 21 April 2026, Team-NB — the European Association of Medical devices Notified Bodies — adopted Version 4 of its Best Practice Guidance for the Submission of Technical Documentation under Annex II and III of the MDR. The document reflects a collaborative notified body approach and is intended to support a more consistent understanding of what manufacturers should provide when submitting technical documentation.

Compared with earlier versions, Version 4 provides updated and expanded guidance on recurring reasons for technical documentation delays, communication with notified bodies before submission, documentation structure, translations, file format, file naming, and the consistency of duplicated information across the technical file. Practical submission details are also relevant here: the guidance recommends keeping individual PDF files to a maximum of 100 MB, limiting the combined file path and file name to 160 characters (with spaces counting as “%20”, i.e. three characters), using bookmarks or a dedicated table of contents for documents of 10 pages or more, and agreeing the folder structure with the notified body in advance.

The update also incorporates recent regulatory and technical developments across several documentation areas, including e-IFU requirements, AI Act considerations, software and cybersecurity, biocompatibility, chemical characterization, CMR and endocrine-disrupting substances, sterilization, packaging, SSCP, and post-market surveillance. More specifically, the guidance does not treat the AI Act as a separate documentation chapter; AI/ML-related expectations are addressed within product verification and validation and software documentation, including training and test data sets, reference to the EU Ethics Guidelines for Trustworthy AI, and the Team-NB/German NB Alliance questionnaire for AI in medical devices.

The practical message for manufacturers

One of the key messages of the guidance is that technical documentation should not be treated as a collection of individual reports. It should function as a connected compliance system.

This means manufacturers should ensure that the technical file clearly links device description, intended purpose, classification, GSPR compliance, benefit-risk analysis, risk management, verification and validation evidence, clinical evaluation, PMCF, PMS, and PSUR documentation. When these elements are not aligned, notified bodies may need to raise additional questions to understand how the evidence supports conformity.

A practical way to reduce this risk is to maintain a clear documentation structure with a logical index or table of contents, searchable files, consistent terminology, complete reports, and explicit links between evidence and the relevant MDR requirements.

Key areas covered by the guidance

The guidance follows the structure of MDR Annex II and Annex III and provides practical recommendations across the main sections of the technical file. These include:

  • Device description, specification, variants, accessories, classification, and materials
  • Information supplied by the manufacturer, including labelling, IFU, implant card, promotional materials, and e-IFU information
  • Design and manufacturing information, including validated processes, critical suppliers, subcontractors, and manufacturing controls
  • General Safety and Performance Requirements, including how compliance is demonstrated and linked to supporting evidence
  • Benefit-risk analysis and risk management, including risk management planning, risk controls, and risk management reporting
  • Product verification and validation, including biocompatibility, software, cybersecurity, electrical safety, EMC, packaging, shelf-life, usability, sterilization, and other specific device cases
  • Clinical evaluation, including clinical evaluation strategy, CEP, CER, PMCF, and SSCP
  • Post-market surveillance, including PMS plans and PSUR expectations

Leveraging previous conformity assessment evidence

A particularly relevant part of the guidance concerns the use of evidence from previous conformity assessments, especially for manufacturers transitioning devices from the Directives to the MDR.

Team-NB explains that, in some cases, evidence previously assessed by a notified body may be leveraged to support MDR conformity assessment. However, manufacturers still need to provide full technical documentation under MDR Annex II and III. They should clearly indicate whether previously assessed evidence has changed, what the extent of any changes is, and where the evidence was previously reviewed.

This is especially important for legacy devices. Manufacturers should not assume that previous MDD evidence will automatically be accepted. Instead, they should make the connection transparent and provide references to previous assessment numbers, project IDs, or notified body reports where applicable.

For manufacturers, the value of the guidance is not only in understanding what must be submitted, but also how information should be presented so that notified body reviewers can efficiently follow the logic of compliance.

Practical takeaways for manufacturers

Based on the guidance, manufacturers should consider the following practical actions before submitting or updating MDR technical documentation:

1

Build the technical file around MDR Annex II and Annex III, not around internal document ownership.

2

Use a clear index, table of contents, and hyperlinks where appropriate.

3

Avoid fragmented or partial reports; provide complete and current evidence.

4

Ensure consistency across repeated information such as intended purpose, Basic UDI-DI, indications, contraindications, warnings, and device variants.

5

Link GSPR compliance to risk management, verification and validation evidence, clinical evaluation, and PMS outputs.

6

Clarify language and submission expectations with the notified body before submission. This early alignment can also be based on MDCG 2019-6 on structured dialogue and the IMDRF/RPS WG/N9 principles for pre-submission communication with the notified body.

7

For legacy devices, clearly identify what evidence was previously assessed and what has changed.

8

Keep the technical documentation searchable, logically organized, and easy to review.

Conclusion

Team-NB Version 4 provides manufacturers with a practical reference for improving the quality, structure, and reviewability of MDR technical documentation. The update reinforces a clear message: strong technical documentation is not only about having the right reports available, but about presenting a coherent, traceable, and well-maintained compliance story. The fact that Version 4 has grown to 92 pages, compared with approximately 80 pages in Version 3, also illustrates the increasing complexity of MDR technical documentation expectations. A practical example is risk management: the acceptability of risks should not be decided solely on the basis of an RPN value, but should be justified through the overall risk management process and benefit-risk rationale.

For manufacturers preparing MDR submissions, updating existing technical files, or transitioning legacy devices, the guidance can help reduce avoidable review questions and support a more efficient conformity assessment process.

EU MDR 2017/745 Zertifizierung jetzt mit DQS starten

Sparen Sie Zeit und internen Aufwand mit einem klar strukturierten Zertifizierungsprozess. Fordern Sie jetzt Ihr individuelles Angebot für die EU MDR 2017/745 Zertifizierung an.
 

Angebot an­fordern

The full Team-NB guidance can be accessed here

Author

Klaus Lindenberg

Klaus Linderberg graduated from Fachhochschule Lübeck as Diplom Ingenieur (FH) in Biomedical Technology. With extensive experience across various companies in Germany’s medical device sector, he has built a strong foundation in quality and regulatory compliance. He has been working as a Lead Auditor and Technical Expert for medical device Quality Management, specializing in regulatory standards and audits. His professional background is supported by certifications relevant to medical device quality assurance and auditing.

Loading...

You Might Also Enjoy These Reads

Discover more articles that dive deep into related themes and ideas.
Blog
Loading...

Akila Limited Achieves ISO 13485:2016 Certification for Medical Device PCBA Manufacturing in Hong Kong

Blog
Loading...

Updated MDR Harmonised Standards: Commission Implementing Decision (EU) 2026/760

Blog
Loading...

EU MDR Certification Process Explained: CE Marking Requirements for Medical Devices