ISO 9001 requires you to monitor customer satisfaction, but doesn't dictate the method. That flexibility is deliberate — the standard assumes you know your business better than the auditor does. The trap most companies fall into is either ignoring the requirement altogether or building something so elaborate it becomes pointless.
Where the requirement sits
Clause 9.1.2 requires you to monitor customer perceptions of the degree to which their needs and expectations have been fulfilled. That's the core obligation. You must also demonstrate that you're acting on what you find out. It's not a tick-box. The standard wants evidence that you're listening and changing behaviour as a result.
I've audited hundreds of companies. The ones that pass easily treat this as part of normal business — not as a compliance exercise bolted on for the auditor. They already know what customers think because they talk to them regularly. They just need to document that activity slightly more formally.
What actually works
The simplest approach is often the best. Customer feedback channels that already exist — complaints, returns, support calls, direct conversations — count. So do surveys, focus groups, and user testing. Post-delivery calls from a sales team member count. Net Promoter Score counts. Online reviews and social media feedback count, provided you're actively monitoring them.
The standard doesn't care whether your method is quantitative or qualitative. You can measure satisfaction on a 1-10 scale or collect written comments. You can do quarterly surveys or continuous feedback loops. What matters is that the approach reflects how your customers actually communicate with you and that the data informs business decisions.
In my experience, companies that track complaints and support interactions tend to spot issues faster than those relying on annual surveys alone. You get real-time signals that way. But if your customer base is largely B2B with long sales cycles, an annual structured feedback session might make more sense.
The documentation trap
Avoid creating a system for the auditor's benefit. I've seen organisations build elaborate survey matrices that nobody reads and data that never influences anything. That's worse than doing nothing. An auditor will ask: what did you do with these results? If the answer is "nothing," you've demonstrated non-conformance more clearly than if you'd kept it simple and genuinely acted on feedback.
What you need is a basic record of how you gathered information, what you found, and what you changed as a result. That might be notes from a customer call, a summary of feedback themes, a decision log showing action taken. Keep it brief. Keep it real.
Linking it to management review
This is where many companies stumble. You gather feedback, but does the leadership team actually see it and discuss it? Clause 9.3.2 requires that the organisation's performance, including customer satisfaction trends, goes to management review. If your managing director can't tell me what the satisfaction data shows, it's not embedded in your system. It's just data sitting in a spreadsheet.
That doesn't mean lengthy reports. It means whoever leads your business understands the trend and can explain what's being done about poor scores or emerging complaints.
If you don't have customer satisfaction monitoring in place yet, don't overcomplicate it. Pick one method that fits your business — a post-job survey for service companies, a customer advisory call for suppliers, a feedback form for retailers. Run it for a quarter, collate the findings, discuss them with your team, and make one change based on what you learn. Document it — that's your foundation. The auditor isn't looking for perfection or sophistication. They're looking for evidence that you care what customers think and that you do something about it when they tell you.
Ready to talk about your business?
Book a free, no-obligation call. We will tell you exactly what certification would involve for your size, sector, and starting point.