We e-mail the editable toolkit files to the address you gave, usually within 2 to 3 business days.
ISO Standards

What Documents You Need for ISO 13485:2016 Implementation

What Documents You Need for ISO 13485:2016 Implementation
In short

Which documents does ISO 13485:2016 require? See the quality manual, procedures, medical device files and records you need, and how to plan them.

In this article
  1. The documentation structure ISO 13485:2016 expects
  2. Core QMS documents
  3. Documented procedures you will usually need
  4. Medical device files and product records
  5. Records auditors will ask to see
  6. How to plan your documentation without over-building it
  7. Frequently asked questions

ISO 13485:2016 asks for more documentation than most management system standards. That is deliberate. Medical device regulators and notified bodies expect you to show, with evidence, that your devices are designed, made and serviced in a controlled way.

This article sets out the documents you need, how they fit together, and how to avoid writing more paper than your organisation can maintain.

The documentation structure ISO 13485:2016 expects#

The standard's documentation requirements cover the following layers:

  • Quality policy and quality objectives, which set direction for the QMS.
  • A quality manual, which describes the scope of the QMS and justifies any requirement you treat as not applicable.
  • Documented procedures for the processes the standard names.
  • Work instructions and other documents your organisation needs to plan, operate and control its processes.
  • Medical device files for each device type or family.
  • Records that prove the system is working.
  • Documents required by applicable regulations in the markets where you sell.

The last point matters. ISO 13485 is not a regulation. Your target markets may add requirements, such as technical documentation, labelling, vigilance reporting or unique device identification, and those depend on your device class and role (manufacturer, importer, distributor and so on).

Core QMS documents#

Quality manual, policy and objectives#

The quality manual should state the scope of your QMS, the devices and activities it covers, and the reasons for any exclusions or non-applicable requirements. It should also reference the documented procedures and describe how the processes interact. Keep it short and accurate. A long manual that no one updates becomes an audit finding.

Document and record control#

You need a documented procedure for controlling documents (approval, review, versioning, availability at point of use, removal of obsolete copies) and another for controlling records (identification, storage, protection, retrieval, retention and disposal). Retention periods for records should reflect the device lifetime and regulatory requirements, so check them against the rules in your markets.

Roles and responsibilities#

Define who has authority over quality, who is the management representative, and who is responsible for regulatory affairs. Organisation charts and job descriptions are usually enough, as long as responsibilities are clear and current.

Documented procedures you will usually need#

The standard calls for documented procedures across the product lifecycle. The exact list depends on what your organisation does, but most manufacturers need procedures covering the areas below.

AreaWhat the procedure should cover
Management reviewInputs, outputs, frequency and records of decisions
Competence and trainingDefining competence, delivering training, evaluating effectiveness
Infrastructure and work environmentMaintenance, cleanliness and contamination control where relevant
Risk managementRisk management across the product lifecycle, aligned with your chosen risk standard
Customer communication and requirements reviewHandling enquiries, contracts, orders and feedback
Design and developmentPlanning, inputs, outputs, review, verification, validation, transfer and change control
Purchasing and supplier controlSupplier evaluation, selection, monitoring and re-evaluation
Production and service provisionControlled production, process validation, identification, traceability, preservation
Monitoring and measuring equipmentCalibration and control
Software validationValidating software used in the QMS, production or monitoring
Feedback and complaint handlingReceiving, evaluating, investigating and closing complaints
Regulatory reportingDeciding when and how to notify authorities of adverse events
Internal auditPlanning, independence, reporting and follow-up
Nonconforming productIdentification, segregation, disposition, rework and recall or advisory notices
Data analysisWhat data you collect and how you use it to evaluate the QMS
Corrective and preventive actionInvestigation, root cause, action, verification of effectiveness

Some items only apply in certain cases. Installation, servicing and sterilisation processes, for example, need procedures only if you carry them out. Record your reasoning in the quality manual rather than quietly skipping them.

Medical device files and product records#

For each medical device type or family, the standard expects a medical device file. It typically brings together:

  • A general description, intended use and labelling, including instructions for use.
  • Product specifications.
  • Manufacturing, packaging, storage, handling and distribution specifications or procedures.
  • Procedures for measuring and monitoring.
  • Installation and servicing requirements, where applicable.

This file is closely related to, but not always identical with, the technical documentation that regulators in your markets require. Decide early how the two will relate so you do not maintain duplicate sets that drift apart.

Design projects add their own records: design plan, inputs, outputs, review minutes, verification and validation reports, risk management file, transfer records and change history. Production adds batch or device history records, process validation reports and traceability records.

Records auditors will ask to see#

Records show that you do what your documents say. Certification auditors and regulators commonly look for:

  1. Management review minutes and the actions that followed.
  2. Training and competence records for each role.
  3. Internal audit programme, reports and closed findings.
  4. Supplier evaluation and re-evaluation records.
  5. Calibration records for measuring equipment.
  6. Complaint files, investigations and any regulatory reports.
  7. Nonconformity and CAPA records, including effectiveness checks.
  8. Design review, verification and validation evidence.
  9. Process and software validation reports.
  10. Traceability records linking components, batches and distribution.

How to plan your documentation without over-building it#

Start with a gap assessment against the standard and your regulatory obligations. Then work in this order:

  1. Define scope and role. Confirm which devices, sites, processes and regulatory roles the QMS covers.
  2. List the required documents and records. Map each requirement to an existing document, a document to revise, or a gap.
  3. Write procedures that match practice. Interview the people who do the work. A procedure that describes an idealised process fails the first audit.
  4. Build templates and forms. Standard formats for design reviews, CAPA, supplier evaluation and complaints save time and keep records consistent.
  5. Run the system before the audit. Collect real records, run an internal audit and hold a management review so you have evidence of operation.

Teams working across several standards may also find it useful to compare how documentation is structured elsewhere, for instance in our guide to IATF 16949:2016 documents, another standard with a strong process and records focus.

Frequently asked questions#

Is a quality manual mandatory under ISO 13485:2016?#

Yes. The standard requires a quality manual that covers the scope of the QMS, the documented procedures or references to them, and a description of how the processes interact. It should also explain any non-applicable requirements.

Can I use ISO 9001 documents as a starting point?#

Some of the structure carries over, such as document control, internal audit and management review. But ISO 13485 adds requirements around regulatory compliance, risk management, design controls, traceability, validation and complaint handling, so ISO 9001 documents will need substantial extension.

How much documentation is enough?#

Enough to meet the standard and your regulatory requirements, and to make sure your processes are performed consistently. The scale should reflect your organisation's size, device risk class and process complexity. Documents you cannot keep current are a liability, not an asset.

If you would rather start from a structured framework than a blank page, the ISO 13485:2016 Toolkit provides editable policies, procedures, checklists and worked examples, along with a gap assessment checklist, that you can adapt to your own devices and processes.

Share this guide

Ready to put this into practice?

Start with the ISO 13485:2016 Toolkit and adapt it to your organisation, or talk to us about implementation support.

Chat on WhatsApp