Internal audit checklist for medical device companies: FDA QMSR and ISO 13485
An internal audit checklist is the working list of requirements, procedures, and records an auditor moves through to confirm two things: that the quality management system does what its own documentation says it does, and that it satisfies the regulations the company is subject to. Nearly every medical device company has one. Most of them now cite a regulation that no longer exists.
On Feb. 2, 2026, 21 CFR Part 820 became the Quality Management System Regulation (QMSR), replacing the Quality System Regulation (QSR) that had governed US device manufacturers since 1978. The old section numbers are gone. Design controls are no longer at 820.30, purchasing controls are no longer at 820.50, and the quality audit requirement is no longer at 820.22. If your checklist still has a column of those citations next to the ISO clauses, every entry in that column points at a repealed section.
Two changes matter more than the renumbering. ISO 13485:2016 is now the substance of the FDA requirement rather than a parallel standard you also happened to meet. And the carve-out that kept internal audit reports out of FDA inspections was not carried over, so the audit report you write this quarter is a document an investigator can ask to read.
FREE RESOURCE: Click here to download our FDA QMSR and ISO 13485:2016 internal audit checklist.
What the QMSR changed
Part 820 is now much shorter than it was. Six operative sections remain: scope at 820.1, definitions at 820.3, incorporation by reference at 820.7, the core quality management system requirement at 820.10, control of records at 820.35, and device labeling and packaging controls at 820.45. Everything else was reserved or removed.
The substance moved into ISO 13485:2016, which 820.7 incorporates by reference along with Clause 3 of ISO 9000:2015. Both are readable at no cost through the ANSI incorporated-by-reference portal. Incorporation by reference is not a recommendation or a recognized-consensus-standard arrangement. The clauses of ISO 13485 carry the force of federal regulation, and § 820.10(e) states that failing to comply with any applicable requirement of Part 820 renders the device adulterated under section 501(h) of the Federal Food, Drug, and Cosmetic Act.
A few definitions are overridden. § 820.3 specifies that "organization," the term ISO 13485 uses throughout, means manufacturer as Part 820 defines it. Definitions from section 201 of the FD&C Act supersede the correlating ISO definitions, which is why the FD&C Act meanings of device and labeling control rather than ISO's medical device and labelling. For anyone reading the standard as a regulation for the first time, that substitution is worth making explicit in the audit procedure itself.
One point gets lost in the harmonization story. A certificate of conformance to ISO 13485 is not evidence of QMSR compliance, and the FDA neither requires nor issues one. The agency stated plainly in its QMSR frequently asked questions that a certificate does not exempt a manufacturer from inspection, and that FDA inspections do not follow the Medical Device Single Audit Program (MDSAP) audit plan or procedures. Your notified body audit and your FDA inspection remain different events with different evidence expectations, even though they now read from substantially the same requirements. For the full picture of what moved where, see our guide to the Quality Management System Regulation.
Why internal audits carry more weight now
Under the QSR, 820.180(c) kept management review reports, internal quality audit reports, and supplier audit reports outside the scope of an FDA inspection. Investigators could confirm that the audits had occurred and that procedures existed, but they could not read the findings. That exception was not maintained in the QMSR.
The FDA answered the question directly in its FAQ: the QMSR gives the agency authority to inspect management review, quality audit, and supplier audit reports, and the reasoning given in the final rule preamble is that manufacturers already provide these documents to other regulators. The agency also confirmed that investigators may review records created before Feb. 2, 2026, so there is no clean start. An audit report written in 2023 under the old exemption can be requested in an inspection next month.
The inspection method changed on the same date. The FDA withdrew the Quality System Inspection Technique (QSIT) and now inspects device manufacturers under the updated Inspection of Medical Device Manufacturers compliance program 7382.850. Firms that built their internal audit program around QSIT's four-subsystem structure, which is a large share of the industry, are auditing to a model the agency has retired.
What does that mean for how you write an audit report? Not softer findings. A thin report that records no observations in a system with open CAPAs and repeat nonconformances reads worse to an investigator than a detailed report with findings that were closed on time. The useful discipline is to write every finding so it stands on its own: what was examined, what the requirement is, what was observed, and what happened next. Where a record genuinely contains confidential information, § 820.35(d) allows a manufacturer to mark it to help the FDA decide what may be disclosed under the public information regulation in Part 20. Marking a record does not withhold it from the investigator.
Where the internal audit requirement lives now
The requirement sits in Clause 8.2.4 of ISO 13485, and through 820.7 it is the FDA requirement. The standard calls for internal audits at planned intervals to determine whether the quality management system conforms to planned and documented arrangements, to the requirements of the standard, to the company's own QMS requirements, and to applicable regulatory requirements, and whether it is effectively implemented and maintained.
Several specifics in that clause are where companies lose points. A documented procedure has to describe responsibilities and requirements for planning and conducting audits and for recording and reporting results. The audit program has to account for the status and importance of the processes and areas being audited and for the results of previous audits, which rules out an identical annual sweep that ignores where the problems have been. Criteria, scope, interval, and methods have to be defined and recorded. Auditors cannot audit their own work. And management responsible for the audited area has to ensure corrections and corrective actions happen without undue delay, with follow-up that verifies the actions and reports the verification results.
Clause 8.2.4 is also the only place the standard ties audits to the rest of the system. Audit results are a required input to management review under 5.6.2 and a named driver of improvement under 8.5.1, so an audit program that produces reports nobody acts on fails the clause even when every audit happened on schedule.
We worked with one company that included an annual internal audit in their SOPs but realized in month eleven that they hadn't followed their own requirement. They had to scramble and hire an external consultant who could only make judgments from afar. The company learned nothing and gained little more than a check mark from the audit. You can do better, and the checklist is where that starts.
How to reference requirements on a QMSR-era checklist
The old checklist convention, an ISO column beside an FDA column, made sense when the two were separate sets of requirements that happened to overlap. Under the QMSR that layout creates a false impression that there are two requirements to satisfy where there is now one.
The convention used below is simpler. Each line cites the ISO 13485:2016 clause, which is the FDA requirement. Where Part 820 adds something the standard does not cover, the line carries a second citation to the QMSR section. Nothing else needs a US-specific reference.
Write your checklist from the perspective of an external auditor, and be stricter than you expect the auditor to be. An external audit does not set out to tick individual requirements. The auditor is judging whether the QMS works as a system, which is worth keeping in view so that your internal audit does not drift into an exercise in confirming that documents exist.
The QMSR additions a pure ISO 13485 checklist will miss
If your checklist came from an ISO 13485 template or from a registrar, these are the lines it does not have. They are the US-specific supplements in Part 820, and they are the most likely gap in a company that certified to ISO 13485 and assumed the FDA work was done.
| What to verify | Reference |
|---|---|
| A system to assign unique device identification (UDI) is documented and meets Part 830. | ISO 13485: 7.5.8; QMSR 820.10(b)(1) |
| Traceability procedures account for Part 821 device tracking where it applies. | ISO 13485: 7.5.9.1; QMSR 820.10(b)(2) |
| Complaints meeting the reporting criteria of Part 803 are notified to the FDA. | ISO 13485: 8.2.3; QMSR 820.10(b)(3) |
| Advisory notices are handled in accordance with the corrections and removals requirements of Part 806. | ISO 13485: 7.2.3, 8.2.3, 8.3.3; QMSR 820.10(b)(4) |
| Design and development controls are applied to all class II and class III devices, to class I devices automated with computer software, and to the five class I device types listed in the regulation. | ISO 13485: 7.3; QMSR 820.10(c) |
| Devices that support or sustain life meet the implantable device traceability requirements, whether or not they are implantable. | ISO 13485: 7.5.9.2; QMSR 820.10(d) |
| Complaint records capture the device name, date received, UDI or UPC and other identifiers, complainant contact details, nature and details of the complaint, any correction or corrective action, and any reply sent. | QMSR 820.35(a) |
| Servicing records capture the device name, UDI or UPC and other identifiers, date of service, who performed it, what was performed, and any test and inspection data. | ISO 13485: 7.5.4; QMSR 820.35(b) |
| The UDI is recorded for each device or batch of devices. | ISO 13485: 7.5.1, 7.5.8, 7.5.9; QMSR 820.35(c) |
| Labeling and packaging are examined for accuracy before release or storage, covering the correct UDI or UPC, expiration date, storage instructions, handling instructions, and any additional processing instructions. | QMSR 820.45(a) |
| Release of labeling for use is documented, and labeling and packaging operations prevent mix-ups, with inspection results recorded. | ISO 13485: 4.2.5; QMSR 820.45(b), (c) |
| Records the company considers confidential are marked to aid the FDA in making disclosure determinations under Part 20. | QMSR 820.35(d) |
Management
The management section confirms that management reviews happen on a defined cadence, and that the quality system has an owner, a plan, and resources behind it.
| Management tasks | Reference |
|---|---|
| Internal auditors are trained and competent for the areas they audit. | ISO 13485: 6.2, 8.2.4 |
| Auditors do not audit their own work, and the selection of auditors supports objectivity and impartiality. | ISO 13485: 8.2.4 |
| The quality manual defines the scope of the QMS, justifies any exclusion or non-application, references the documented procedures, and describes how QMS processes interact. | ISO 13485: 4.2.2 |
| The roles the company holds under applicable regulatory requirements are documented and match what it actually does. | ISO 13485: 4.1.1 |
| Criteria and methods needed to control QMS processes are determined, and a risk-based approach is applied to the control of those processes. | ISO 13485: 4.1.2(b), 4.1.3(a) |
| Changes to QMS processes are evaluated for their effect on the QMS and on devices produced under it. | ISO 13485: 4.1.4 |
| Outsourced processes that affect product conformity are monitored and controlled, with written quality agreements in place. | ISO 13485: 4.1.5 |
| Computer software used in the quality management system is validated before initial use and after changes, proportionate to risk, with records retained. | ISO 13485: 4.1.6 |
| Management reviews are held at documented planned intervals under a documented procedure. | ISO 13485: 5.6.1 |
| Review inputs include feedback, complaint handling, reporting to regulatory authorities, audits, process and product monitoring, corrective and preventive action, follow-up from previous reviews, changes that could affect the QMS, improvement recommendations, and new or revised regulatory requirements. | ISO 13485: 5.6.2 |
| Review outputs record decisions and actions on QMS suitability and effectiveness, product improvement, changes needed to meet new or revised regulatory requirements, and resource needs. | ISO 13485: 5.6.3 |
| A quality policy and measurable quality objectives are established, communicated, and reviewed for continuing suitability. | ISO 13485: 5.3, 5.4.1 |
| QMS planning maintains the integrity of the system when changes are planned and implemented. | ISO 13485: 5.4.2 |
| Responsibilities and authorities are defined, documented, and communicated, and personnel who manage, perform, or verify work affecting quality have the independence and authority to do it. | ISO 13485: 5.5.1 |
| A member of management is appointed with responsibility for QMS processes, for reporting effectiveness to top management, and for promoting awareness of applicable regulatory requirements. | ISO 13485: 5.5.2 |
| Resources needed to implement and maintain the QMS are determined and provided. | ISO 13485: 6.1 |
| Competence requirements are determined, training or other action is provided, effectiveness of that action is evaluated, and records of education, training, skills, and experience are kept. | ISO 13485: 6.2 |
| Audit criteria, scope, interval, and methods are defined and recorded, and the audit program accounts for the status and importance of the areas audited and the results of previous audits. | ISO 13485: 8.2.4 |
| Audit records identify the processes and areas audited and the conclusions reached. | ISO 13485: 8.2.4, 4.2.5 |
| Management responsible for an audited area ensures corrections and corrective actions are taken without undue delay, and follow-up verifies the actions and reports the verification results. | ISO 13485: 8.2.4, 8.5.2 |
The second line above is where small companies struggle. Objectivity is straightforward in a company large enough to have people who were not involved in the work. In a five-person company with one person responsible for quality, it takes planning. Cross-training is the usual answer, since it both builds the pool of people who can audit and spreads knowledge of how the system works. Staff can pursue training through the American Society for Quality or a Regulatory Affairs Certification (RAC), and some companies contract an independent auditor for the areas their quality lead owns.
Design and Development
Here the aim is confirming that design and development is controlled well enough to produce devices meeting user needs, intended use, and the requirements the company specified. External auditors take a risk-based approach and focus on what is most likely to affect safe performance, so expect extra scrutiny and consider a dedicated audit of design control, validation, and risk management.
Check the applicability line first. The QMSR requires design and development controls for class II and class III devices, for class I devices automated with computer software, and for a short list of named class I device types. Companies with class I portfolios sometimes assume they are outside design controls entirely, and the software line catches more of them every year.
| Design and development tasks | Reference |
|---|---|
| Procedures for design and development are documented. | ISO 13485: 7.3.1 |
| Design and development controls apply to the devices the regulation names, and any exclusion is justified and recorded. | ISO 13485: 7.3; QMSR 820.10(c) |
| Planning documents the stages, the reviews needed at each stage, verification, validation, and transfer activities appropriate to each stage, responsibilities and authorities, methods for tracing outputs back to inputs, and the resources and competence required. | ISO 13485: 7.3.2 |
| Planning documents are maintained and updated as the work progresses. | ISO 13485: 7.3.2 |
| Design inputs cover functional, performance, usability, and safety requirements according to intended use, applicable regulatory requirements and standards, applicable risk management outputs, and information from previous similar designs. | ISO 13485: 7.3.3; ISO 14971:2019 |
| Inputs are reviewed for adequacy and approved, and they are complete, unambiguous, verifiable or validatable, and not in conflict with each other. | ISO 13485: 7.3.3 |
| Outputs meet the input requirements, provide information for purchasing, production, and service provision, contain or reference acceptance criteria, and specify the characteristics essential for safe and proper use. | ISO 13485: 7.3.4 |
| Outputs are in a form suitable for verification against inputs and are approved before release. | ISO 13485: 7.3.4 |
| Reviews are held at suitable stages with representatives of the functions concerned plus other specialist personnel, and records identify the design under review, the participants, and the date. | ISO 13485: 7.3.5 |
| Verification plans document methods, acceptance criteria, and where appropriate the statistical techniques with a rationale for sample size. | ISO 13485: 7.3.6 |
| Where the device connects to or interfaces with other devices, verification and validation confirm the design meets requirements in that connected configuration. | ISO 13485: 7.3.6, 7.3.7 |
| Validation is conducted on representative product, including initial production units, batches, or equivalents, with the rationale for the choice recorded. | ISO 13485: 7.3.7 |
| Clinical evaluation or performance evaluation is performed as applicable regulatory requirements require, and validation is complete before release for use to the customer. | ISO 13485: 7.3.7 |
| Design transfer procedures ensure outputs are verified as suitable for manufacturing before they become final production specifications, and that production capability can meet product requirements. | ISO 13485: 7.3.8 |
| Design changes are identified and, before implementation, reviewed, verified, validated as appropriate, and approved. | ISO 13485: 7.3.9 |
| Change review evaluates the effect on constituent parts, on product in process or already delivered, and on the inputs and outputs of risk management and product realization. | ISO 13485: 7.3.9 |
| A design and development file is maintained for each device type or device family. | ISO 13485: 7.3.10 |
Design and development links out to more of the system than any other area. Outputs become inputs to purchasing and production, risk management runs through all of it, and changes ripple into production records and post-market activity. Audit the links, not just the contents of each file, and document any gaps in the audit report.
Production and Process Controls
Production and process controls determine whether what leaves the line meets specification. The checks run across testing, infrastructure, equipment, and the supplier-facing controls at the point where purchased product enters the process.
| Production and process control tasks | Reference |
|---|---|
| Product realization is planned consistently with the rest of the QMS, and one or more risk management processes are documented with records retained. | ISO 13485: 7.1; ISO 14971:2019 |
| Production and service provision are planned, carried out, monitored, and controlled, including documented methods, qualification of infrastructure, monitoring of process parameters and product characteristics, and defined labeling and packaging operations. | ISO 13485: 7.5.1 |
| A record is established and maintained for each device or batch that provides traceability, identifies the amount manufactured and the amount approved for distribution, and is verified and approved. | ISO 13485: 7.5.1 |
| The UDI is recorded for each device or batch. | QMSR 820.35(c) |
| Labeling and packaging are examined for accuracy before release or storage, release of labeling is documented, and operations prevent mix-ups with inspection results recorded. | ISO 13485: 7.5.1, 4.2.5; QMSR 820.45 |
| Cleanliness of product and contamination control arrangements are documented where the conditions call for them. | ISO 13485: 6.4.2, 7.5.2 |
| Infrastructure and work environment requirements are documented and controlled, and maintenance activities and intervals are documented with records retained. | ISO 13485: 6.3, 6.4.1 |
| Processes whose output cannot be verified by later monitoring or measurement are validated, with criteria for review and approval, equipment and personnel qualification, revalidation criteria, and approval of process changes. | ISO 13485: 7.5.6 |
| Computer software used in production and service provision is validated before initial use and after changes, proportionate to the risk associated with its use. | ISO 13485: 7.5.6 |
| Sterilization processes and sterile barrier systems are validated before implementation and after product or process changes, and sterilization process parameters are recorded for each batch and traceable to production batches. | ISO 13485: 7.5.5, 7.5.7 |
| Product identification procedures are documented, product status with respect to monitoring and measurement is identified throughout production, storage, installation, and servicing, and returned devices are identified and distinguished from conforming product. | ISO 13485: 7.5.8 |
| Traceability procedures define the extent of traceability and the records to be maintained. | ISO 13485: 7.5.9.1; QMSR 820.10(b)(2) |
| For implantable devices and for devices that support or sustain life, traceability records include components, materials, and work environment conditions where these could cause the device to miss its safety and performance requirements, and distributor records allow traceability. | ISO 13485: 7.5.9.2; QMSR 820.10(d) |
| Customer property is identified, verified, protected, and safeguarded, with loss or damage reported to the customer and recorded. | ISO 13485: 7.5.10 |
| Preservation procedures protect product from alteration, contamination, and damage during processing, storage, handling, and distribution, including packaging design and any special conditions. | ISO 13485: 7.5.11 |
| Monitoring and measuring equipment is calibrated or verified against traceable standards at specified intervals, identified for calibration status, safeguarded from invalidating adjustment, and protected during handling and storage. | ISO 13485: 7.6 |
| When equipment is found out of tolerance, the validity of previous measuring results is assessed and recorded, and action is taken on the equipment and any affected product. | ISO 13485: 7.6 |
| Installation requirements and acceptance criteria for verification of installation are documented, with records of installation performed by the company or its supplier. | ISO 13485: 7.5.3 |
| Servicing procedures and records exist, and servicing records are analyzed to determine whether information should be handled as a complaint and as input to improvement. | ISO 13485: 7.5.4; QMSR 820.35(b) |
| Product characteristics are monitored and measured at applicable stages, the identity of the person authorizing release is recorded, and for implantable devices the identity of personnel performing inspection or testing is recorded. | ISO 13485: 8.2.6 |
| Methods for monitoring and measuring QMS processes demonstrate the ability of those processes to achieve planned results, with correction and corrective action when they do not. | ISO 13485: 8.2.5 |
Audit production early in the cycle. Walking the floor and the warehouse first lets you pull the samples you will use in other sections, and it gives you the lot numbers to trace in both directions, forward into distribution records and backward into purchasing and incoming inspection.
Purchasing
Companies that outsource design, manufacturing, or sterilization carry the most exposure here, because the controls over purchased product and outsourced services are doing work that would otherwise sit inside the building.
| Purchasing tasks | Reference |
|---|---|
| Purchasing procedures are documented and ensure purchased product conforms to specified purchasing information. | ISO 13485: 7.4.1 |
| Supplier evaluation and selection criteria are based on the supplier's ability to meet requirements, on supplier performance, on the effect of the purchased product on device quality, and are proportionate to the risk associated with the device. | ISO 13485: 7.4.1 |
| Monitoring and re-evaluation of suppliers is planned, performance is monitored, and results feed the re-evaluation process. | ISO 13485: 7.4.1 |
| Non-fulfilment of purchasing requirements is addressed with the supplier proportionate to risk and to regulatory compliance. | ISO 13485: 7.4.1 |
| Purchasing information describes the product and, as appropriate, specifications, acceptance requirements, procedures, processes and equipment, personnel qualification requirements, and QMS requirements. | ISO 13485: 7.4.2 |
| Purchasing information includes a written agreement that the supplier notifies the company of changes to purchased product before implementing them. | ISO 13485: 7.4.2 |
| Verification of purchased product is implemented with extent based on supplier evaluation results and proportionate to risk, and verification at a supplier's premises is stated in the purchasing information where it applies. | ISO 13485: 7.4.3 |
| Records of evaluation, selection, monitoring, and re-evaluation of suppliers are maintained, along with records of verification. | ISO 13485: 7.4.1, 7.4.3 |
| Outsourced processes are covered by written quality agreements, with controls proportionate to the risk and to the external party's ability to meet requirements. | ISO 13485: 4.1.5 |
Purchasing is the section where audit duration varies most. External auditors can spend a meaningful share of an audit here when a company outsources heavily, and the information has to come from partners who respond on their own schedule. Build that delay into your internal audit plan so your scrutiny matches or exceeds what an external auditor will apply. Supplier audit reports are among the records the QMSR opened to FDA review, which is reason enough to make sure yours are complete.
Corrective and preventive action, complaints, and nonconforming product
Everything in this area comes down to whether the system corrects itself. Information has to be collected and analyzed well enough that problems are identified and investigated, and that someone decides whether corrective and preventive action is warranted.
| CAPA and feedback tasks | Reference |
|---|---|
| Feedback procedures are documented, gather data from production and post-production activities, and feed risk management and the improvement processes. | ISO 13485: 8.2.1 |
| Complaint handling procedures cover receiving and recording information, evaluating whether feedback is a complaint, investigating, determining reportability, handling complaint-related product, and determining the need for correction or corrective action. | ISO 13485: 8.2.2 |
| Where a complaint is not investigated, the justification is documented. | ISO 13485: 8.2.2 |
| Complaint records capture the device name, date received, UDI or UPC and other identifiers, complainant contact information, nature and details, any correction or corrective action, and any reply sent. | QMSR 820.35(a) |
| Records of review, evaluation, and investigation are maintained for complaints involving possible failure of a device, labeling, or packaging to meet specifications. | QMSR 820.35(a) |
| Reportable complaints are notified to the FDA in accordance with Part 803. | ISO 13485: 8.2.3; QMSR 820.10(b)(3) |
| Advisory notice procedures exist, can be put into effect at any time, and align with the corrections and removals requirements of Part 806. | ISO 13485: 8.3.3; QMSR 820.10(b)(4) |
| Nonconforming product is identified and controlled to prevent unintended use or delivery, with documented controls for identification, documentation, segregation, evaluation, and disposition. | ISO 13485: 8.3.1 |
| Evaluation of nonconformity includes determining the need for investigation and for notifying any external party responsible. | ISO 13485: 8.3.1 |
| Use, release, or acceptance under concession happens only with documented justification, approval, and regulatory compliance, and the identity of the person authorizing the concession is recorded. | ISO 13485: 8.3.2 |
| Nonconforming product detected after delivery triggers action appropriate to the effects or potential effects, with records of the action taken. | ISO 13485: 8.3.3 |
| Rework procedures account for the potential adverse effect of rework, undergo the same review and approval as the original procedure, and reworked product is verified against acceptance criteria and regulatory requirements. | ISO 13485: 8.3.4 |
| Data analysis procedures determine the methods used, including statistical techniques and the extent of their use, with inputs from feedback, product conformity, process and product trends, suppliers, audits, and service reports. | ISO 13485: 8.1, 8.4 |
| Corrective action is taken without undue delay, is proportionate to the effects of the nonconformity, and is verified not to adversely affect regulatory compliance or device safety and performance. | ISO 13485: 8.5.2 |
| Effectiveness of corrective and preventive action is reviewed, and records of investigations and actions taken are maintained. | ISO 13485: 8.5.2, 8.5.3 |
| Preventive action addresses potential nonconformities proportionate to the effects of the potential problems. | ISO 13485: 8.5.3 |
| Improvement is driven through the quality policy, objectives, audit results, post-market surveillance, data analysis, corrective and preventive action, and management review. | ISO 13485: 8.5.1 |
One of the most common issues we see is companies logging every audit finding as a CAPA. A finding does not automatically require one. As we have written in our Ultimate Guide to CAPA for Medical Devices, CAPA is for systemic issues, and your complaint handling and nonconforming product procedures exist to handle the rest.
If an audit uncovers a nonconformance, you can request more records to determine its extent, record the severity in the audit report, and escalate to CAPA if it recurs or worsens. What you cannot do is leave the finding without a disposition. With audit reports now readable by an investigator, an open finding with no trail attached to it is the kind of thing that generates questions.
Documentation and records
Weak document control shows up faster in an inspection than almost anything else, usually as a record nobody can produce on request. The checks here cover both control of documents and retrievability of records.
| Documentation and records tasks | Reference |
|---|---|
| Documents are reviewed and approved before issue, reviewed and re-approved as necessary, with revision status and changes identified. | ISO 13485: 4.2.4 |
| Relevant versions are available at points of use, documents remain legible and identifiable, and obsolete documents are prevented from unintended use with suitable identification applied. | ISO 13485: 4.2.4 |
| Documents of external origin determined to be necessary are identified and their distribution controlled, and documents are protected from deterioration and loss. | ISO 13485: 4.2.4 |
| Changes to documents are reviewed and approved by the original approving function or another designated function with access to the pertinent background. | ISO 13485: 4.2.4 |
| The retention period for at least one copy of obsolete documents is defined and covers the device lifetime as the company defines it, and not less than the retention period of any resulting record. | ISO 13485: 4.2.4 |
| Record control procedures define identification, storage, security and integrity, retrieval, retention time, and disposition. | ISO 13485: 4.2.5 |
| Records remain legible, identifiable, and retrievable, and changes to a record remain identifiable. | ISO 13485: 4.2.5 |
| Records are retained for at least the lifetime of the device as the company defines it, or as applicable regulatory requirements specify, and not less than two years from release of the device. | ISO 13485: 4.2.5 |
| Methods for protecting confidential health information in records are defined and implemented. | ISO 13485: 4.2.5 |
| A medical device file exists for each device type or family, containing or referencing the device description and intended use, labeling and instructions for use, product specifications, specifications or procedures for manufacturing, packaging, storage, handling, and distribution, procedures for measuring and monitoring, and installation and servicing requirements as appropriate. | ISO 13485: 4.2.3 |
| QMS documentation includes the quality policy and objectives, the quality manual, the procedures and records the standard requires, documents the company determines it needs, and any documentation applicable regulatory requirements specify. | ISO 13485: 4.2.1 |
| Records of education, training, skills, and experience are maintained. | ISO 13485: 6.2 |
| Records the company deems confidential are marked to aid FDA disclosure determinations under Part 20. | QMSR 820.35(d) |
Document what you examined as you go. Record the specific files, lot numbers, and training records you pulled, since an audit report that names its evidence is far easier to defend than one that asserts a conclusion. Save this section for late in the audit, when you can follow up on questions raised in the other sections.
What happened to the DMR, DHR, and DHF
The QMSR does not use the terms device master record, device history record, or design history file. Those obligations did not disappear; they sit in ISO 13485 under different names. The medical device file in Clause 4.2.3 covers the ground the DMR covered, the design and development file in 7.3.10 covers the DHF, and the record required for each device or batch under 7.5.1 covers the DHR. Section 820.3 does reference the medical device file directly in its definition of rework.
Nothing requires you to rename your own documents. A company with a procedure titled Device Master Record Control is still compliant as long as the content satisfies 4.2.3 and the procedure makes the relationship clear. What an auditor will check is whether your internal terminology maps cleanly to the clauses, which is a short paragraph in a procedure and a line in your audit checklist. We cover the mapping in detail in our post on DMR, DHR, and DHF record keeping under the QMSR.
Customer-related processes
Complaint intake usually gets tested here, alongside how customer requirements, orders, and communications are handled.
| Customer-related process tasks | Reference |
|---|---|
| Requirements related to product are determined, including delivery and post-delivery requirements, requirements not stated by the customer but necessary for specified or intended use, applicable regulatory requirements, and any user training needed for specified performance and safe use. | ISO 13485: 7.2.1 |
| Requirements are reviewed before the company commits to supply, differing contract or order requirements are resolved, and records of the review and resulting actions are maintained. | ISO 13485: 7.2.2 |
| When product requirements change, relevant documents are amended and relevant personnel are made aware. | ISO 13485: 7.2.2 |
| Arrangements for communicating with customers cover product information, enquiries and order handling including amendments, customer feedback including complaints, and advisory notices. | ISO 13485: 7.2.3 |
| Communication with regulatory authorities happens in accordance with applicable regulatory requirements. | ISO 13485: 7.2.3 |
Audit this section carefully. An FDA investigator or a notified body auditor will almost certainly want to see how complaints are managed, and complaint handling has long been among the most common sources of warning letters and Form 483 observations.
FREE RESOURCE: Click here to download our FDA QMSR and ISO 13485:2016 internal audit checklist.
Pass your next audit with ease
If your behavior changes when an auditor arrives, your processes are not ready. The point of an internal audit program is that the system runs the same way whether or not anyone is watching, which matters more now that unannounced audits are a routine part of European oversight and FDA investigators can read findings that used to stay internal.
The QMSR transition gives most companies a concrete reason to rebuild the checklist rather than patch it. Replacing dead section numbers is the obvious task. The larger one is deciding what your audit reports should look like now that they have a second audience, and making sure the program covers the US-specific supplements that an ISO 13485 template leaves out.
A purpose-built QMS for medical device companies makes the mechanical part of this easier. Greenlight Guru includes audit workflows that let internal auditors build schedules, assign section owners, set due dates and reminders, and connect findings to the CAPA, complaint, and nonconformance records they relate to, so the evidence trail is assembled as the audit runs rather than reconstructed afterward.
Get a demo to see how it works.
Etienne Nichols is the Head of Industry Insights & Education at Greenlight Guru. As a Mechanical Engineer and Medical Device Guru, he specializes in simplifying complex ideas, teaching system integration, and connecting industry leaders. While hosting the Global Medical Device Podcast, Etienne has led over 200...
Related Posts
QMSR Mythbusters Episode
FDA Inspections Under QMSR: A Guide to Compliance Program 7382.850
QMSR: What's Left of the QSR in the New 21 CFR Part 820
Get your free eBook PDF
Internal Quality Audit Checklist




