Document control for medical devices
How document control works for medical device teams, the records an audit expects, and how to produce controlled, audit-ready documents without a separate manual chore.
Document control in a medical device quality system
Document control for medical devices is the part of an ISO 13485 quality system that governs how documents are approved, revised and retired. Controlled documents must be approved before use, identified by revision, changed under control, and protected against the use of obsolete versions, so you can always show which version was approved, by whom, and what changed.
In the United States, the FDA Quality Management System Regulation (QMSR) has incorporated ISO 13485:2016 by reference since 2 February 2026, so the same clauses apply in an FDA inspection.
The records an audit expects
- Approval evidence held with the document, not in email.
- Unambiguous revision status.
- An immutable record of exactly what was approved.
- A change history that makes every change attributable.
- Retention and quick retrieval when asked.
Producing it without the overhead
Manual document control is slow and fragile. A tool built for it makes the controls structural: a published, draft, and fix model for revision status, gated approval with e-signatures, a change log, and an immutable PDF snapshot on publish. The evidence is a by-product of the work. See document control software, the ISO 13485 document control guide, and the wider medical device solution.
Related guides
This guide is educational and does not certify any product or organisation.
Common questions
What is document control for a medical device team?
It is the controlled handling of the documents in a medical device quality system: approving them before use, identifying revisions, controlling changes, protecting against use of obsolete versions, and retaining records. ISO 13485 clauses 4.2.4 (documents) and 4.2.5 (records) set the expectations.
Which documents need to be controlled?
Quality system documents, design and development records, risk management records, verification and validation reports, and the design history file, among others. In practice, anything that provides evidence the device was developed correctly.
How does Traceable help?
A controlled version model, gated approval with e-signatures, a change log, and immutable snapshots produce the controlled documents an audit expects as a by-product of normal work. Traceable supports the process. Certification depends on your quality system and your auditor, not on any tool.
Produce controlled documents by construction
Publish a controlled document with e-signatures and an immutable snapshot in minutes.