5.1 Clause 9.1 — Monitoring, measurement, analysis & evaluation

Clause 9 begins the "Check" half of the PDCA cycle introduced in Chapter 1: after planning the QMS (Clauses 4-6) and operating it (Clauses 7-8), the organization must find out whether it actually works. Clause 9.1 -- Monitoring, measurement, analysis and evaluation -- is where that evidence is generated, and it is one of the richest sources of objective evidence a lead auditor will examine.

9.1.1 Determining What, How and When

Clause 9.1.1 requires the organization to determine:

• (a) what needs to be monitored and measured
• (b) the methods for monitoring, measurement, analysis and evaluation needed to ensure valid results
• (c) when the monitoring and measuring shall be performed
• (d) when the results from monitoring and measurement shall be analyzed and evaluated

Note the deliberate split between (c) and (d): an organization can collect data continuously (say, daily scrap-rate readings) while only analyzing and evaluating it monthly or quarterly. Both the collection cadence and the analysis cadence must be defined -- an auditor should ask for both, separately.

The clause also requires the organization to evaluate the performance and effectiveness of the QMS as a whole, and to retain appropriate documented information as evidence of the results. This is a step up from simply logging numbers: performance answers "are we meeting our targets?" while effectiveness answers "is the QMS actually achieving its intended outcomes?" A department can hit every individual KPI while the QMS as a system still fails to deliver conforming product on time -- effectiveness evaluation is meant to catch that gap.

9.1.2 Customer Satisfaction

Clause 9.1.2 singles out one measurement as mandatory in principle, if flexible in method: the organization shall monitor customers' perceptions of the degree to which their needs and expectations have been fulfilled, and must determine the methods for obtaining, monitoring and reviewing this information.

ISO 9001 deliberately does not prescribe a single method. Acceptable sources include:

• Customer satisfaction surveys
• Feedback on delivered products and services
• Meetings with customers
• Market-share analysis
• Compliments
• Warranty claims
• Dealer or distributor reports

A common misconception among candidates is that a survey is required -- it is not. An organization with low sales volume and close customer relationships might reasonably rely on direct feedback and warranty data rather than a formal survey instrument. What matters to an auditor is that the method chosen is actually applied, produces usable data, and that the data can be traced into clause 9.1.3 analysis.

9.1.3 Analysis and Evaluation

Collecting data is only half the requirement. Clause 9.1.3 requires the organization to analyze and evaluate appropriate data and information arising from monitoring and measurement, and specifies what the results must be used to evaluate:

1. Conformity of products and services
2. The degree of customer satisfaction
3. The performance and effectiveness of the QMS
4. Whether planning has been implemented effectively
5. The effectiveness of actions taken to address risks and opportunities
6. The performance of external providers
7. The need for improvements to the QMS

This list is a gift to an auditor because it is a checklist for tracing data to decisions. If a site tracks on-time delivery, scrap rate and complaint volume every month but nobody can point to a decision, trend chart, or improvement action that resulted from that data, clause 9.1.3 is not being met -- the organization is measuring but not evaluating.

Auditing Clause 9.1: What Good Evidence Looks Like

When gathering objective evidence against 9.1, look beyond the raw logs and ask to see the output of analysis:

• Trend charts or dashboards, not just raw data tables
• Minutes or records showing data was discussed and interpreted, not merely filed
• A traceable link from a metric to an action (e.g., rising scrap rate leading to an investigation and a process adjustment)
• Evidence that customer satisfaction data specifically fed into objectives or management review
• Statistical techniques appropriate to the data volume and criticality (control charts, Pareto analysis, simple trend lines)

A frequent finding at this clause is data that is collected diligently but never interpreted -- dashboards updated monthly with no narrative, no threshold, and no owner. That gap between "monitored" and "analyzed and evaluated" is exactly what separates a conforming clause 9.1 implementation from a nonconformity, and it is one of the highest-value places to probe during the conducting-the-audit phase you will study in Chapter 7.

A useful exam heuristic: whenever a scenario describes data being "collected" without describing any subsequent trend analysis, decision, or management discussion, suspect a gap in 9.1.1(d) -- analysis and evaluation -- rather than in 9.1.1(a) through (c), which only cover what, how and when to measure. The organization may have defined a perfectly valid monitoring schedule and still fail the clause because nobody closes the loop into analysis. Distinguishing these sub-clauses precisely, rather than citing "clause 9.1" generically in a nonconformity statement, is exactly the kind of specificity both the exam and a real audit report reward.