ISO 9001 Clause 9, Performance Evaluation, is the requirement to prove the quality management system actually works. It has three parts: 9.1 monitoring, measurement, analysis and evaluation; 9.2 internal audit; and 9.3 management review. Together they are the "Check" in Plan-Do-Check-Act.

Every other clause of ISO 9001 tells you to plan something, run something, or fix something. Clause 9 is where you find out whether any of it is landing. It is the difference between a binder full of procedures and a QMS that top management can honestly say is suitable, adequate, and effective. Auditors know this, which is why a weak Clause 9 is one of the most common reasons a certification audit turns up major findings.

What does ISO 9001 Clause 9 require?

Clause 9 requires you to gather evidence about QMS performance, audit yourself against the standard, and have leadership review the whole picture and decide what to do next. The clause of the standard (ISO 9001:2015) breaks into three sub-clauses, each answering a different question:

The three build on each other. Monitoring feeds audits with evidence; audits and monitoring both feed the management review; the management review produces decisions that reset objectives and resources for the next cycle. Skip one and the chain breaks: data with no review is noise, review with no data is opinion.

ISO 9001 Clause 9 anatomyClause 9: three layers, one conclusion9.1 MONITOR + MEASUREKPIs, product conformity, customer satisfaction, analysis9.2 INTERNAL AUDITindependent check vs. standard and vs. your own docs9.3 MANAGEMENT REVIEWtop management weighs it all and decides what changesEVIDENCE:suitable,adequate,effectiveEach layer feeds the next. Remove one and the conclusion stops being defensible.Data without review is noise. Review without data is opinion.
Clause 9 stacks three layers so the final claim, that the QMS works, rests on evidence rather than assertion.

What is Clause 9.1 monitoring, measurement, analysis and evaluation?

Clause 9.1 requires you to decide what to monitor and measure, how, and when, then actually analyze the results instead of just filing them. The standard deliberately does not hand you a KPI list; you determine what matters based on your processes, objectives, and risks. What it will not accept is measuring for the sake of a chart nobody reads.

Three obligations sit inside 9.1:

Good 9.1 evidence is where the plant floor and the standard meet. Statistical process control charts, first-pass yield, scrap rates, on-time delivery, and complaint trends are all 9.1 outputs. The failure mode is collecting numbers with no evaluation step, so the data never becomes a decision. That is exactly the gap 9.1.3 exists to close.

A concrete example: a plant tracks scrap by line every shift. Under 9.1.1 it decided scrap matters because a quality objective targets a scrap ceiling. Under 9.1.3 it does not just log the daily number; it evaluates the trend, notices line 3 has crept up for three straight weeks, links it to a material change, and flags it for corrective action. The measurement was step one. The evaluation is what the clause is actually asking for, and it is what an auditor will probe when they ask "what did you do with this data?"

What does Clause 9.2 internal audit require?

Clause 9.2 requires internal audits at planned intervals to check two things: that the QMS conforms to your own requirements and to ISO 9001, and that it is effectively implemented and maintained. It also requires an audit program that reflects the importance and past performance of each process, plus objective auditors who do not audit their own work.

In practice, 9.2 means a rolling audit schedule, checklists tied to clauses and processes, trained auditors, findings recorded honestly, and corrections that actually close. The independence rule matters: the person who runs a process cannot be the one who signs off that it conforms. If you want the working mechanics, our guide on how to run an ISO 9001 internal audit walks through building the program and closing findings, and the quality audit checklist gives you a starting structure.

What does Clause 9.3 management review require?

Clause 9.3 requires top management to review the QMS at planned intervals to confirm it is still suitable, adequate, effective, and aligned with the strategic direction of the business. The review has a defined set of inputs it must consider (9.3.2) and a defined set of decisions it must produce (9.3.3).

The inputs pull the whole clause together: status of actions from the last review, changes in internal and external issues, performance data (customer satisfaction, objectives, process and product conformity, nonconformities and corrective actions, monitoring results, audit results, external provider performance), adequacy of resources, effectiveness of risk and opportunity actions, and improvement opportunities. The outputs are decisions on improvement, changes to the QMS, and resource needs. We break the full agenda down in the ISO 9001 management review guide.

Clause 9 as the Check phase of PDCAClause 9 is the Check in Plan-Do-Check-ActPLANcl. 4-6DOcl. 7-8CHECKCLAUSE 9ACTcl. 10Check has no value unless it turns the wheel to Act. Findings must drive change.
Clause 9 is not the end of the loop. Its whole purpose is to feed Clause 10 improvement and start the next turn better informed.

How do you prove the QMS is working in 7 steps?

Clause 9 is easiest to pass when you treat it as one connected evidence chain, not three separate chores. Here is a working sequence:

  1. Define what you measure and why. Tie each metric to a quality objective or a known risk. If you cannot say what decision a number would change, stop measuring it. This is 9.1.1 done honestly.
  2. Capture the data at the source. Line checks, inspection results, complaints, and delivery performance recorded where the work happens, not reconstructed from memory at month-end. Clean capture is what makes 9.1.3 analysis trustworthy.
  3. Analyze and evaluate on a set cadence. Convert raw data into conclusions: is conformity trending up or down, are complaints clustering, is a supplier slipping? Record the conclusion, not just the chart.
  4. Audit against the standard and your own documents. Run the 9.2 program on a schedule weighted toward high-risk and recently-troubled processes. Write findings as evidence versus requirement, not as opinion.
  5. Close findings with real corrections. Every nonconformity gets containment, root cause, and corrective action through your CAPA process, then verification that it held.
  6. Feed it all into management review. Assemble the 9.3.2 inputs into one packet so leadership sees the full picture in one sitting, then record the decisions.
  7. Turn decisions into next cycle's plan. Improvement actions, QMS changes, and resource commitments from the review reset the objectives you will measure next. That closes the loop into Clause 10.

Clause 9 in numbers

A few facts worth anchoring on, straight from the standards bodies:

How does Clause 9 connect to the rest of ISO 9001?

Clause 9 sits between the doing (Clause 8, operations) and the improving (Clause 10). It is the hinge. Weak measurement means management review runs on anecdotes; weak auditing means nonconformities hide until a customer finds them; weak review means findings pile up with no one empowered to act. Strong Clause 9 is usually the clearest signal that a QMS is alive rather than shelfware.

It also connects outward to the business. The 9.3 requirement that top management confirm the QMS stays aligned with strategic direction is what stops quality from drifting into a compliance silo. When leadership reviews customer satisfaction, audit results, and objective performance in one sitting, quality stops being the quality manager's private problem and becomes a business input. That is the quiet ambition of Clause 9: make the health of the QMS visible enough that people with authority act on it.

The practical bottleneck is rarely willingness. It is that the evidence lives in a dozen places: inspection sheets on clipboards, complaints in email, audit findings in a spreadsheet, KPIs in a slide deck someone rebuilds every month. Harmony's role here is narrow and specific: it captures those quality checks and process data digitally at the station, keeps the records searchable, and surfaces the patterns so the 9.1 analysis and the 9.3 review packet mostly assemble themselves, working alongside your QMS rather than replacing it. No rip-and-replace. You can see how that plays out in a real plant on our customer story. However you assemble it, the standard's demand is constant: show, with evidence, that the system works, and act when it does not.