Monitoring, measurement, analysis and evaluation

In plain words

This clause asks three questions: what do you monitor and measure, when — and, the step most skip, what do the numbers mean? Measuring is easy; evaluating is the point. A number without a conclusion is paper.

Two things belong to it explicitly. First, customer satisfaction (9.1.2): you must look at how the customer perceives you — not only at your internal metrics. You can meet every tolerance and still lose the customer, because delivery date, reachability and flexibility matter and stand in no drawing. Second, analysis and evaluation (9.1.3): draw conclusions from the data that leadership can actually use.

Two boundaries save misunderstandings. 9.1 does not measure the single part — release does that (8.6). And 9.1 does not mean the measuring equipment — that is 7.1.5. Here it is about the performance of the system: how are we doing across all orders and processes, and what does it tell us?

Why this requirement exists

A QMS that generates data but never looks at it is a filing cabinet, not a management system. 9.1 forces the loop to close: measure → evaluate → decide. Without it, leadership steers by gut feeling, and metrics are collected because collecting is what one does.

Customer satisfaction (9.1.2) stands as a point of its own on purpose, because it is the most easily forgotten: the inward look (scrap, inspection results) feels complete and conceals what the customer experiences. And the emphasis on evaluation (9.1.3) exists because measuring tends toward reassurance — a full data sheet looks like control without containing a single consequence.

What good looks like

A handful of real metrics that mean something — scrap rate, on-time delivery, complaints, customer feedback — captured at a sensible rhythm (usually monthly) and actually looked at: a trend, a conclusion, a consequence. Customer satisfaction feeds on real signals: complaints, returns, repeat orders, the annual conversation with the customer — a formal survey is one option, not a duty. The evaluation (9.1.3) answers the questions that count: are the products conforming? Is the customer satisfied? Are the objectives being met? Are the actions on risks and opportunities working? Where must we get better? The result flows into the management review.

What changes as you grow: From around 50 people, each process owner gets a small metrics picture of their area. From 100–250 people, where it carries, systematic satisfaction surveys, statistical trend and spread analysis and a deliberate mix of leading and lagging metrics arrive. The core stays the same at every size: few real numbers, honestly evaluated — not many numbers, filed unseen.

The minimum to pass

• It is defined what is monitored and measured, with method and rhythm.
• Customer satisfaction is tracked from at least one real source — complaints, feedback, on-time delivery.
• The data is analysed and evaluated — conclusions drawn, not just collected.
• The results reach the management review.

What an auditor asks for

• The metrics themselves — with a trend over time, not a snapshot.
• How customer satisfaction is captured — and a concrete conclusion drawn from it.
• A case where analysis led to a decision — the closed loop.
• The link to the objectives (6.2): does the metric trend say whether an objective is being met?
• In conversation: does leadership know its most important numbers and their direction, without looking them up?

Common traps

• Measuring without evaluating. The daily scrap tally that never becomes a trend. The most common gap in the clause: much raw material, no conclusion.
• Only the inward look. Internal metrics shine while the customer quietly walks away — because nobody measured their perception. 9.1.2 is exactly this point.
• Vanity numbers. What is easy to measure gets measured, not what counts. A pretty number with no link to objectives or risks is decoration.
• The survey as an alibi. A questionnaire nobody evaluates — or the survey as the only source, while complaints and on-time delivery speak louder.
• 9.1 confused. With part release (8.6) or with monitoring of measuring equipment (7.1.5). Here it is about the performance of the system, not the part and not the caliper.

Worked example

Berger Präzisionsteile GmbH keeps a handful of metrics on a monthly one-pager that Lea maintains: scrap rate (the 6.2 objective, at 1.8%), on-time delivery from the customer’s view, complaints (the sum of the 8.7 cases that reached customers) and new-customer share (the 6.2 growth objective, at 17%). The actual evaluation (9.1.3) is the quarterly look: the scrap trend is flat and good, on-time slipped in the second quarter (the 5-axis breakdown), complaints are falling. Customer satisfaction (9.1.2) Berger reads from complaints, on-time delivery and the annual conversation — where the main customer said the call during the hardening-shop crisis had kept them (7.4). No formal survey; for twelve people the real signals are richer than a questionnaire. The honestly missed 17% figure is analysis material, not a hiding game — and moves openly into the management review (9.3).

The teaching sentence came from the neighbouring shop: it measured the same scrap rate daily and never drew a trend from it — a drawer full of numbers, not one consequence. Berger’s one page with a quarterly conclusion beats it. Measuring is not evaluating.

← All ISO 9001 topics · To the knowledge hub