ISO 9001 clause 9.1.2: understand customer satisfaction

What clause 9.1.2 requires in practice

Clause 9.1.2 asks the organisation to monitor customer satisfaction and to decide how it will obtain, monitor and review the information that tells it how customers see the products and services. The clause leaves the method to the organisation. A note in the standard lists possible sources, including surveys, comments on what was delivered, meetings with customers, analysis of market share, compliments, complaints, warranty claims, dealer reports and social media. The requirement is therefore twofold: choose the sources and methods deliberately, and then actually monitor and review what they show. It does not demand a questionnaire, a score or an annual survey, and it does not treat a quiet period as proof of satisfaction. The output is a defined set of customer information channels together with evidence that the information is looked at, understood and fed into the wider evaluation under clause 9.1.3.

Choose information that reflects the customer relationship

Useful sources can include direct feedback, customer meetings, complaints, compliments, warranty information and other relevant channels. The standard offers examples of possible sources; it does not require all of them. Select methods that fit the customer base, the type of service or product, and the decisions the organisation needs to make.

Consider who provides the information. A purchasing contact, daily user and technical approver may experience different aspects of the same delivery. For a B2B service, feedback from one senior sponsor can be useful but incomplete if the people using the service face recurring difficulties that never reach that sponsor.

Decide how the information will be monitored and reviewed. A feedback channel with no review responsibility can become a collection point rather than a management method. Clarify how urgent issues are routed and how wider patterns are assessed alongside other performance information.

Why clause 9.1.2 matters to the business

Customers rarely announce dissatisfaction before they leave. By the time a complaint arrives, the relationship is often already strained, and many customers simply quietly move to another supplier. A deliberate approach to customer feedback gives the business earlier warnings, shows where service or products diverge from expectations, and reveals what customers value enough to recommend. It also supports sales, because buyers increasingly ask suppliers how they listen to customers. Relying on a single source, such as complaint counts, creates blind spots, whereas a mix of direct and indirect information produces a more accurate picture on which to base pricing, capacity and improvement decisions.

How to implement clause 9.1.2

Aim for a small set of feedback channels that suit your customers and are actually read. Pay particular attention to customers who say little, since silence is ambiguous, and make sure whoever speaks to customers daily has a route for passing on what they hear.

1. Identify the customer groups that matter most and what each cares about, such as speed, accuracy, responsiveness or price.
2. Select a mix of sources for each group, combining direct contact such as meetings or short surveys with indirect signals such as returns, repeat orders and complaints.
3. Decide how often each source is reviewed and who reads it.
4. Agree how feedback is recorded so that comments are not lost between sales, delivery and support teams.
5. Review the combined picture periodically and write down what it says, including mixed or contradictory signals.
6. Pass relevant conclusions to the people who can act, and agree what response customers will see.
7. Check from time to time that the chosen methods still reach the customers whose views matter most.

Evidence an auditor expects for clause 9.1.2

Common nonconformities with clause 9.1.2

Findings at this clause tend to be about method and follow-through rather than about the absence of a survey.

• No method is defined, and satisfaction is assumed because few complaints are received.
• Feedback is gathered but there is no evidence that anyone reviewed it.
• A single source, such as complaints alone, is used for every customer group, leaving important customers unrepresented.
• Comments from customers are held by individual account managers and never reach those who could act.
• Reported satisfaction results cannot be explained, because the way they were obtained was not stated.

Illustrative software example: satisfied sponsor, frustrated users

Illustrative manufacturing example: a low complaint count

A manufacturer receives few formal complaints and initially interprets this as strong satisfaction. Routine customer discussions reveal that one buyer has been ordering less because delivery updates are unreliable. The team considers order patterns and direct feedback alongside complaint records, recognising that some customers reduce business instead of submitting a complaint.

The manufacturer agrees a clearer update process and checks the customer's experience in later reviews. Evidence includes the feedback, the issue identified and the follow-up conclusion. An increase in sales would not by itself prove that communication improved, just as a decline could have unrelated commercial causes. The interpretation remains connected to the available facts.

Recognise the limits of the method

A survey result can be distorted by a low response rate, a narrow contact list or a question that combines several unrelated issues. A high average can conceal serious dissatisfaction in an important segment. Explain these limitations when reviewing results rather than presenting a single number as an unquestionable fact.

Complaint counts also need context. More complaints may follow easier reporting, increased volume or a genuine decline in performance. No complaints can mean satisfaction, reluctance to report or lack of an accessible route. Compare the information with relevant delivery and service evidence before reaching a conclusion.

Where practical, separate feedback about different aspects of the experience so the organisation can act. A broad “satisfied or dissatisfied” response may flag a concern but not explain whether the issue concerns timeliness, usability, technical conformity or communication. Follow-up should be respectful and proportionate, not designed to pressure the customer into changing a score.

Turn feedback into a reasoned response

Review relevant findings through analysis and evaluation and include customer satisfaction information in management review. Where feedback reveals a nonconformity, use the applicable response and corrective-action process. Where it identifies a preference or opportunity, assess the appropriate business response without automatically treating it as a failed requirement.

Useful evidence can include the chosen methods, feedback records, review conclusions and actions taken. Clause 9.1.2 does not mandate a named customer-satisfaction report. The broader QMS evidence should make it possible to understand how satisfaction is monitored and how significant information is reviewed.