Why Your Medical Device File Fails Audits (ISO 13485 Clause 4.2.3 Breakdown)

ISO Cloud Consulting editorial team
Editorial illustration for the guide: Medical Device File Failures: ISO 13485 Clause 4.2.3 Guide

Medical device files usually fail audits because they are missing, unstructured, or not maintained. Clause 4.2.3 expects a defined file for each device or device family covering description and intended use, specifications, manufacturing, packaging and distribution, and monitoring and measurement. Fix it with a clear index, traceable links to procedures and records, and regular updates.

Most medical device files fail audits because they are incomplete, not structured, or not linked to actual processes. ISO 13485 requires a defined, maintained file that demonstrates how your device meets regulatory and quality requirements—not just a collection of documents.

This is one of the most overlooked certification risks in medical device companies.

What ISO 13485 Actually Requires (Clause 4.2.3)

ISO 13485 requires you to maintain a medical device file for each device or device family. This file must demonstrate conformity to both the standard and regulatory requirements.

At minimum, your file must include:

  • Device description and intended use
  • Product specifications
  • Manufacturing and process specifications
  • Packaging, storage, and distribution requirements
  • Monitoring and measurement procedures
  • Installation and servicing requirements (if applicable)

This is not optional. It is a core structural requirement of your QMS.

Why Medical Device Files Fail Audits

1. The File Doesn’t Exist (Or Isn’t Defined)

Many companies assume their Design History File or technical documentation covers this requirement.

Template for this step: the medical device file and IFU templates are in the ISO 13485 Medical Device File & Labelling Kit ($79).

It doesn’t.

Auditors expect a clearly defined medical device file structure. If you cannot show it immediately, you’ve already lost confidence.

2. It’s Just a Folder, Not a System

A common failure: dumping documents into a folder without structure.

What auditors actually look for:

  • Clear indexing
  • Traceability between sections
  • Alignment to QMS processes

If your file doesn’t tell a coherent story of how the device is controlled, it fails.

3. Missing Manufacturing and Process Controls

Clause 4.2.3 explicitly requires manufacturing, handling, and distribution specifications.

This is where most companies fall short:

  • No defined production specifications
  • No linkage to validated processes
  • No clear acceptance criteria

This directly links to failures in Clause 7.5 (production control).

4. No Monitoring and Measurement Defined

If your file does not clearly define:

  • How product is tested
  • What acceptance criteria are used
  • How conformity is verified

Then your device is not “controlled” under ISO 13485.

5. Not Maintained Over Time

The requirement is not just to create the file—but to maintain it.

Common audit findings:

  • Outdated specifications
  • Missing updates after design changes
  • Mismatch between procedures and actual practice

This signals a breakdown in your entire QMS.

What Auditors Actually Look For (But Don’t Say Directly)

Auditors are not just checking if documents exist.

They are assessing:

  • Do you understand your product?
  • Is your device controlled across its lifecycle?
  • Can you demonstrate consistency and traceability?

Your medical device file is one of the fastest ways for them to answer all three.

How to Fix Your Medical Device File (Practical Approach)

Step 1: Define the Structure

Create a standard structure aligned to Clause 4.2.3:

  • Section 1: Device description & intended use
  • Section 2: Specifications
  • Section 3: Manufacturing processes
  • Section 4: Quality control & testing
  • Section 5: Distribution & handling
  • Section 6: Post-market linkage

Step 2: Map Existing Documents

Do not start from scratch.

Map your existing:

  • Design documents
  • SOPs
  • Validation records
  • Test methods

Then identify gaps.

Step 3: Fix Traceability

Every section should link to:

  • Actual procedures
  • Records
  • Evidence of implementation

If you cannot trace it, it doesn’t exist in an audit.

Step 4: Align With Risk Management

Your medical device file should align with your risk management file under ISO 14971.

Risk controls, specifications, and verification activities must be consistent across both systems.

This is where advanced audits focus heavily.

Where Most Companies Go Wrong

The biggest mistake is treating the medical device file as:

  • A regulatory checkbox
  • A documentation exercise

It is neither.

It is the core evidence that your device is controlled, safe, and compliant.

How We Help Fix This Fast

If your medical device file is incomplete or failing audits, you don’t need more documents—you need the right structure and linkage.

We help companies:

  • Build audit-ready medical device files
  • Align documentation to ISO 13485 and ISO 14971
  • Fix traceability and structural gaps
  • Prepare for certification and surveillance audits

Final Takeaway

If your medical device file is not structured, traceable, and maintained, it will fail an audit.

Fixing it is not about adding documents—it’s about building a system that clearly demonstrates control.

Free sample

Get free sample pages from the Design Controls & DHF Kit

Design review pack pages and the DHF index. Real, unedited pages so you can judge the files before you buy.

You will also get occasional template updates and guidance. Unsubscribe any time. See our privacy policy.

Back to blog

Leave a comment

Frequently asked questions

What is a medical device file under ISO 13485?

A medical device file is a defined, maintained file kept for each device or device family that demonstrates conformity to ISO 13485 and applicable regulatory requirements. It is a core structural requirement of the QMS, not a loose collection of documents, and it should show clearly how the device is described, specified, made, checked, and distributed.

What should be included in an ISO 13485 medical device file?

At minimum, the file should include the device description and intended use, product specifications, manufacturing and process specifications, packaging, storage, and distribution requirements, and monitoring and measurement procedures. Installation and servicing requirements should also be included where they apply. Each section should link to actual procedures, records, and evidence of implementation.

Is a Design History File the same as a medical device file?

No, a Design History File or general technical documentation should not be assumed to cover the medical device file requirement. Auditors expect a clearly defined medical device file structure that can be shown immediately. Existing design documents, SOPs, validation records, and test methods can be mapped into that structure, with any gaps identified and closed.

Why do medical device files fail audits?

Medical device files usually fail because they are incomplete, unstructured, or not linked to real processes. Common problems include a file that is just a folder without indexing or traceability, missing manufacturing and acceptance criteria, undefined monitoring and measurement, and specifications that were not updated after design changes. The file should also stay consistent with the ISO 14971 risk management file.

Online course

ISO 13485:2016 Internal Auditor Course (Online, Certificate of Completion)

Learn this topic properly: short lessons, worksheets with model answers, a 100% pass mark on every lesson quiz and a certificate of completion. Unlimited access for $299.

Templates that do this job

Editable Word and Excel files. Instant download. Licensed for one organization.