Few clauses in ISO 9001 are misread as often as 9.1.2. It gets reduced to a single ritual: send customers a satisfaction survey once a year, file the responses, repeat. The survey goes out, the response rate is low, nobody acts on what comes back, and the whole exercise becomes a box to tick the month before the audit. That is not what the clause asks for, and an auditor can see straight through it.
What the clause actually requires
Clause 9.1.2 requires you to monitor customers’ perceptions of the degree to which their needs and expectations have been met. Two words in that sentence carry the weight. Perceptions, because this is about how the customer feels they have been treated, not your internal view of how the job went. And monitor, because it is meant to be an ongoing read, not a single annual snapshot.
The standard then leaves the method up to you. It explicitly does not mandate a survey. It lists a range of options as examples, and the list is broad: feedback on delivered products and services, meetings with customers, complaints, compliments, warranty or defect claims, repeat business, market-share analysis, dealer or partner reports. You choose the methods that suit your size, your work and the nature of your customer. A single phone call to a client after a job can be valid evidence. So can a pattern in your complaints log. The survey is one option among many, and for many businesses it is the weakest.
Your customer is the main contractor, not a consumer
Before picking methods, be clear about who your customer is. For a construction or engineering SME this is rarely an end consumer. It is the main contractor, the client, the principal designer, the framework you sit on. Their needs and expectations are concrete and contractual: programme, quality, safety, snagging, communication, whether you turn up when you said you would. Monitoring their perceptions means paying attention to signals that already exist in your business, most of which you are generating whether you record them or not.
The signals are already in front of you
A construction SME does not need to invent a measurement programme. It needs to notice and record what its customers are already telling it:
- Repeat business. A client who brings you back, or keeps you on their approved list or framework, is telling you something. A client who quietly stops calling is telling you something louder.
- Snagging and defect rates. The volume and nature of snags at the end of a job is one of the most honest readings of customer satisfaction you have, because it is what the client actually experiences.
- Complaints, and how fast you close them. Not just the count, but the pattern and the response time. A complaints log that is analysed is evidence. One that only accumulates is not.
- Payment behaviour and disputes. Slow payment and contested valuations are often satisfaction signals wearing a financial disguise.
- Project debriefs and end-of-job conversations. A short, recorded review with the client at the close of a contract captures perception while it is fresh, and costs nothing but the conversation.
Pick two or three of these that fit how you work. You do not need all of them. You need ones that genuinely tell you how your customers see you.
The failure auditors actually find
Here is the part that turns 9.1.2 from a tick-box into something useful, and it is also where the findings are raised. Collecting the data is not enough. The clause expects you to analyse it, draw conclusions, and act where the conclusions point to a problem. A survey returned and filed, a complaints log that grows but is never reviewed, a debrief nobody reads: these are the classic findings. The data exists, but it drives no decision, so it is not performance evaluation. It is just storage.
This connects directly to the broader pattern in what auditors actually look for. Across every clause, the gap that generates findings is the one between information a business holds and action it takes. Customer satisfaction is the clearest example. An auditor will not be impressed by a thick file of survey responses. They will ask what you learned from them and what you changed as a result.
A practical approach for an SME
Keep it light and make it real. Choose the two or three signals above that you already produce. Bring them to your management review, look at them honestly, and record the conclusion and any action in the minutes. If snagging on a particular type of job is creeping up, note it and decide what to do. If a long-standing client has gone quiet, ask why. That short loop, notice, conclude, act, record, is the whole of clause 9.1.2 done properly, and it is far more convincing to an auditor than a survey with a six per cent response rate.
It is also, not coincidentally, just good business. Competing on price alone is a race to the bottom. Knowing genuinely how your customers see you, and acting on it, is how you keep the clients you have and win the next ones. The clause is asking you to do something you should want to do anyway, and most of the raw material is already sitting in your business, much like the wider point we make in our guide to ISO 9001 for small businesses.
The point underneath it
Clause 9.1.2 is not a survey requirement. It is a requirement to pay structured attention to how your customers experience you, using whatever signals best reveal that, and to act on what you find. The businesses that struggle with it are usually the ones treating it as a once-a-year document exercise. The ones that find it easy are the ones already capturing these signals as they happen, ready to review rather than scrambling to assemble.
That, again, is the case for holding your evidence continuously rather than reconstructing it for the auditor. We set it out in full in why compliance is the entire product.