ISO 9001 clause 9.1.1: plan valid monitoring and measurement

What clause 9.1.1 requires in practice

Clause 9.1.1 is the planning clause for performance evaluation. The organisation has to settle four questions: what needs to be monitored and measured; which methods will be used for monitoring, measurement, analysis and evaluation so that the results can be relied on; when monitoring and measurement take place; and when the results are analysed and evaluated. The standard then requires the organisation to evaluate how well the quality management system performs and how effective it is, and to hold documented evidence of the results. Two points are easy to miss. Collection and evaluation are separate decisions with their own timing, so a figure gathered daily may only be judged monthly. And the methods must produce results that can be trusted, which is a matter of validity rather than volume. The clause does not set the number of indicators, prescribe particular measures or require that everything be quantified.

Define the question before selecting the measure

Begin with a process outcome or quality concern. A question such as “Are accepted delivery commitments being met?” is more useful than a request to create five indicators. Decide what information would support a reliable answer and what level of detail is needed to identify meaningful differences.

Define the measure so different people would calculate or interpret it consistently. For a turnaround measure, specify its start and end points. For a defect rate, clarify the relevant population and what counts as a defect. These definitions are practical ways to support valid results, not a prescribed ISO formula.

Consider the method and the conditions affecting it. Information taken from incomplete records, inconsistent samples or an unsuitable measuring resource can mislead. Where measurement resources are involved, connect with clause 7.1.5. For service data, the reliability of the recording and classification process can be equally important.

Plan collection and evaluation separately

Determine when monitoring and measurement will occur and when results will be analysed and evaluated. These can be different intervals. A process may generate data every day but need a weekly trend review and an immediate response to certain results. The timing should fit the decision and consequences rather than an arbitrary calendar habit.

Assign practical responsibility for collecting, checking and interpreting the information. Clause 9.1.1 does not prescribe a named analyst role, but the planned method needs someone capable of carrying it out. Ensure the people receiving the results understand the definitions and limitations before they make decisions from them.

Why clause 9.1.1 matters to the business

A measure that is poorly defined can mislead a whole management team. If it counts the wrong thing, a team may work hard to improve a number while the customer experience stays the same or worsens. Planning monitoring and measurement properly means leaders see a true picture, can compare one period with another and can explain results to customers and assessors with confidence. It also avoids waste. Without a plan, people collect whatever is convenient and still lack what they need on the day a decision arrives. A clear plan keeps effort proportionate and ties information to the risks and objectives that actually matter to the business.

How to implement clause 9.1.1

Treat the plan as a short working agreement for each process, not a thick procedure. Remember that the plan can be as modest as a short table per process, provided it records the reasoning, because that reasoning is what you will need when results surprise you or someone challenges a figure.

1. For each significant process, state in a sentence what good looks like for customers and for the business.
2. Choose what to observe or measure to show that, including at least one view that could reveal a hidden problem.
3. Describe how each measure is taken, the source of the data and any known limits, so that results can be interpreted fairly.
4. Set collection frequency according to how quickly a problem would hurt, and set evaluation dates separately.
5. Name who collects, who evaluates and who receives the conclusions.
6. Try the plan on a recent period, and confirm that it would have caught a known past problem.
7. Review the plan whenever the process, customer demands or risks change, and note the reason for any change.

Evidence an auditor expects for clause 9.1.1

Common nonconformities with clause 9.1.1

Typical findings at this clause concern unclear planning or results that nobody evaluates.

• Monitoring takes place, but nothing shows what was decided about frequency or method.
• Measures are collected regularly with no record of when or by whom they are evaluated.
• Results from different periods cannot be compared because the method changed without being recorded.
• Process owners cannot explain why a measure was chosen or what decision it supports.
• The system's effectiveness is not evaluated, only the outputs of individual processes.

Illustrative construction example: inspection completion

Illustrative service example: response and resolution

A customer support operation reports the time to first response. Customers complain that their cases remain unresolved despite fast acknowledgements. The service owner retains the response measure for its original purpose but adds suitable information about resolution against the accepted service requirements.

The review distinguishes a holding message from a substantive response and checks whether complex cases are being classified consistently. Results are examined at a frequency that allows emerging backlogs to be addressed. The evidence shows how the measures support different questions rather than implying that one fast response proves an effective service.

Evaluate effectiveness and preserve the result

Performance describes what happened; effectiveness asks whether intended results were achieved. Use the information to reach a reasoned conclusion about the QMS, not just to report activity. A completed training schedule, for instance, is not by itself evidence that a competence-related process problem has improved.

Documented evidence of results must be available. Depending on the process, this can include a reliable system report, measurement record or recorded review conclusion. The format should make the result and its context understandable. Retain the relevant source or traceability where necessary, and control the information under the QMS arrangements.

Frequent weaknesses include changing a denominator without explaining the effect, reporting averages that conceal significant failures, and collecting measures with no agreed evaluation point. Another is using a target as proof that the measurement method is valid. A precisely stated target cannot repair unreliable data.