Customer Satisfaction vs Customer Feedback: Meeting ISO 9001 and ISO 13485 in One Procedure
Updated: 4 days ago
Companies that hold ISO 9001 and ISO 13485 together often run two separate processes for what customers think: a satisfaction survey for the ISO 9001 auditor and a feedback and complaint system for the medical device auditor. The two standards ask for related but different things, and treating them as one requirement, or as two unrelated ones, is a common source of audit findings. This article explains what each standard asks for and how to meet both with one controlled procedure.
What ISO 9001:2026 asks for
ISO 9001:2026, published 16 September 2026, keeps customer satisfaction in clause 9.1.2. The organization monitors customers' perception of the degree to which their needs and expectations have been fulfilled, and determines the methods for obtaining, monitoring and reviewing that information. The results then feed the analysis and evaluation required by clause 9.1.3 and, through it, management review and improvement.
Two points matter in practice:
Methods are your choice. Surveys, customer meetings, delivery and quality ratings, warranty data, lost-business analysis and dealer reports can all count, as long as the method is defined and used.
Perception, not just complaints. A low complaint count does not show that customers are satisfied. Auditors look for an active method that asks for or captures customer views.
What ISO 13485:2016 asks for
ISO 13485 is written for regulatory purposes. It does not follow the Annex SL structure used by ISO 9001, and its emphasis is on meeting customer and regulatory requirements and keeping the quality system effective, so that devices on the market stay safe and perform as intended. The customer topics sit in clause 8.2:
Clause 8.2.1 Feedback. The organization gathers feedback that includes data from production as well as post-production activities. That information is an input to risk management, so it can be used to monitor and maintain product requirements and the product realization or improvement processes.
Clause 8.2.2 Complaint handling. Documented procedures cover receiving and recording information, evaluating whether feedback is a complaint, deciding whether information must be reported to regulatory authorities, handling the product involved, and keeping complaint records.
Clause 8.2.3 Reporting to regulatory authorities. Where applicable regulations require notification of complaints that meet specified criteria, the organization needs a documented procedure for it.
For companies selling in the United States, FDA's Quality Management System Regulation (QMSR), in effect since 2 February 2026, incorporates ISO 13485:2016 by reference. 21 CFR 820.35(a) adds to clause 8.2.2 a list of what complaint records must contain: the device name, the date received, any UDI or UPC and other device identification, the complainant's name, address and phone number, the nature and details of the complaint, any correction or corrective action, and any reply to the complainant.
Where the two requirements differ
The difference is one of purpose. ISO 9001 asks how satisfied customers are so the business can improve. ISO 13485 asks what the field is telling you about whether the device meets its requirements, so risk can be controlled and regulatory duties met. The list below is the short version.
Trigger: ISO 9001 expects you to go and ask. ISO 13485 expects you to capture and assess what comes in, from production through post-production.
Main destination of the data: ISO 9001 sends it to analysis, management review and improvement. ISO 13485 also sends it to risk management, complaint handling and, where required, regulatory reporting.
Records: ISO 9001 needs evidence of the method and results. ISO 13485 and the QMSR need complaint records with specific content and evaluation decisions.
Common audit findings
These are the patterns that tend to show up when one process is stretched to cover both standards, or when the two run side by side without a link:
A survey with no follow-through. Results are collected but never trended, reviewed or acted on, so the 9.1.2 and 9.1.3 evidence stops at the spreadsheet.
Survey comments that are really complaints. A customer writes that a device failed in use, and the comment stays in the survey file instead of being evaluated under the complaint procedure.
No link to risk management. Feedback and complaint trends are reviewed, but the risk management file is never checked against them.
Feedback limited to customers. ISO 13485 feedback includes production and post-production data, not only what customers volunteer.
Incomplete US complaint records. Records miss one or more of the 820.35(a) items, often the UDI or the reply to the complainant.
How to cover both in one procedure
A single customer satisfaction and feedback procedure can satisfy both standards if it is built around one intake and two clear outputs.
1. Define every source
List the sources you will use: surveys or interviews for perception, plus service reports, returns, sales and distributor reports, production data, literature and any other post-production information. Name the owner and frequency for each.
2. Screen everything for complaints
Add a required step: every piece of feedback, including free-text survey comments, is screened against your complaint definition. Anything that alleges a deficiency in identity, quality, durability, reliability, usability, safety or performance moves into the complaint process and its records.
3. Analyze with defined methods
Set the measures and the analysis method in advance, including any statistical techniques and alert or action levels for trends. Keep satisfaction scores and complaint trends separate so one does not hide the other.
4. Route the outputs
Send results to management review, to the corrective action process when thresholds are exceeded, and to risk management for review against existing risk estimates. Record each decision so the auditor can follow the path.
5. Reference it in the quality manual
Show in the manual's process interaction table how customer satisfaction, feedback, complaint handling and analysis of data connect. This gives an auditor from either standard one place to start.
Documents that support this approach
The A.P. Lyon Dual-Standard QMS family is written to ISO 9001:2026 and ISO 13485:2016 together. These documents cover the process described above:
Customer Satisfaction Monitoring Procedure | ISO 9001:2026 + ISO 13485:2016 (SOP 8-015-C) for obtaining, monitoring and analyzing customer perception and using the results to improve.
Complaint Handling Procedure | ISO 9001:2026 + ISO 13485:2016 (SOP 8-001-C) for receiving, investigating, assessing reportability, trending and closing complaints, with feedback to risk management.
Complaint Trending Procedure | ISO 9001:2026 + ISO 13485:2016 (SOP 8-002-C) for statistical methods and risk-based alert, action and escalation criteria.
Dual-Standard Quality Management System Manual (QMSM-C), updated October 2026 with process interaction tables and a reference to SOP 8-015-C.
The documents are editable Word and Excel files that work in a paper-based system or can be imported into an eQMS; see Using A.P. Lyon Procedures in an eQMS. If you are still deciding whether you need both standards, start with ISO 9001 vs ISO 13485: Which Do You Need?
Next steps
Browse the full Dual-Standard QMS category, or use Build Your QMS to price a set: 20% off 5–9 procedures, 35% off 10–19, 50% off 20–39 and 60% off 40 or more. If you want help adapting the process to your devices and markets, see A.P. Lyon consulting. Founder Aaron Lyon is a former Director of Quality Assurance and International Regulatory with more than 30 years in product design, development and global manufacturing.



Comments