ConformoBook a demo

Guide · MDR

Common MDR Documentation Gaps That Delay Technical Assessment

Learn how incomplete, inconsistent or difficult-to-trace documentation can slow technical assessment workflows.

By Conformo Editorial Team · Published · Updated

A gap is more than a missing file

Some gaps are obvious: a document is absent. Others are harder to detect because the file exists but the evidence is inconsistent, out of date, difficult to navigate or disconnected from the claim it is supposed to support.

1. Unclear document status and version history

Reviewers lose time when the index, file name, cover page and internal references point to different revisions. The problem compounds when replacement files arrive without a clear statement of what changed.

  • Use stable document identifiers.
  • Include version and effective date in the index.
  • Mark superseded documents clearly.
  • Provide a change summary for revised submissions.

2. Device scope and intended purpose do not stay consistent

Differences in model names, variants, intended users, indications or patient populations can ripple across classification, risk management, clinical evaluation, labeling and verification evidence.

CompareLook for
Device description vs labelingSame models, purpose, users and claims
Clinical evaluation vs risk fileAligned device scope and residual-risk statements
Verification vs marketed configurationCorrect software, accessories and variants
PMS plan vs intended useRelevant data sources and risk signals

3. Cross-references do not resolve to evidence

A checklist may say that a requirement is covered, but the cited section may be missing, too broad or unrelated to the conclusion. Reviewers then reconstruct the link manually.

  • Reference a controlled document and precise location.
  • Keep requirement, method and evidence in the same traceability view.
  • Explain partial application, deviations and alternative methods.
  • Test links and bookmarks before submission.

4. Risk, clinical, labeling and PMS files tell different stories

These records should behave as a connected evidence system. Delays appear when clinical claims are absent from risk controls, labeling omits residual risks, or post-market activities do not address uncertainties identified in the clinical evaluation.

5. Verification evidence lacks context

  • The tested article or software version is not identified.
  • Acceptance criteria were not defined before results were interpreted.
  • Deviations and failed runs are omitted or unexplained.
  • The report does not connect results to the device claim.
  • Shelf-life, packaging, sterilization or transport assumptions conflict.

A test report should let a reviewer understand what was tested, why it was representative, which method was used, what acceptance meant and how deviations affected the conclusion.

6. Post-market surveillance is generic

A generic plan lists data sources but does not explain how information will be collected, analyzed, trended and fed back into risk management, clinical evaluation or corrective action for the specific device.

  • Name device-relevant data sources.
  • Define responsibilities, frequency and methods.
  • Set indicators and threshold values where appropriate.
  • Show the link to vigilance, PMCF and risk updates.

A readiness review that prevents avoidable delay

  1. Lock the submission scope and document index.
  2. Run an automated and human version check.
  3. Reconcile intended purpose, device identifiers and claims.
  4. Validate every critical cross-reference.
  5. Review risk, clinical, labeling and PMS consistency together.
  6. Separate administrative completeness from technical adequacy.
  7. Record open issues, owners and resolution status before submission.

Frequently asked questions

What is the most common cause of MDR documentation delay?

There is no universal single cause. Operational delays often arise from incomplete document sets, inconsistent scope or claims, weak cross-references, unclear version control, unresolved risk-clinical-labeling inconsistencies and repeated clarification cycles.

How can teams find gaps before submission?

Use a controlled readiness review that checks the document index, versions, cross-references, device scope, claims and traceability before technical adequacy is assessed by qualified specialists.

Sources and further reading