Management review

In plain words

The management review is the moment when top management puts the whole QMS on the table at planned intervals and answers three questions: does it work? Does it still fit us? What do we change? It is not a formality but the steering moment of the system.

The standard makes it concrete. It gives a fixed list of inputs (9.3.2) — everything that reports on the state of the system: status of previous actions, changes in the environment, customer satisfaction, extent to which objectives are met, process and product performance, nonconformities and corrective actions, audit results, supplier performance, adequacy of resources, effectiveness of actions on risks and opportunities, opportunities for improvement. And it demands defined outputs (9.3.3): decisions on improvements, changes to the system, resource needs.

The decisive thing stands between the lines: it is the task of top management. The management must be in the room — that is the thread to leadership (5.1), not the optional flourish of the QM person.

Why this requirement exists

This clause makes the QMS a management tool rather than a certificate on the wall. Everything else generates information; 9.3 is the place where information becomes decisions. Without it, audits, objectives and complaints pile up unseen, and nobody steers.

The fixed input list exists against selective attention: it forces even the uncomfortable points onto the table — the missed objective, the cluster of complaints — that one would pass over on one’s own. And the top-management duty exists because only they can decide on resources and direction: a review delegated to the QM person alone loses exactly the authority that makes it effective.

What good looks like

At least once a year (more often when much is in motion) top management — in a small company literally the managing director plus the two process owners — sits down for two, three hours with a prepared input package covering the 9.3.2 list. One walks through the points; the uncomfortable ones get the most time. The result is a short report with decisions: the objectives for next year, changes to the system, committed resources — each decision a task with an owner and a date. Not a thirty-page report nobody reads, but a focused session with real resolutions.

What changes as you grow: From around 50 people, short quarterly interim reviews feed the annual full review. From 100–250 people, a structured input package per area, metric overviews and formal action tracking arrive. The core stays the same at every size: leadership in the room, the full input list, real decisions at the end.

The minimum to pass

• A management review has taken place within the intended rhythm, with top management present.
• The inputs per 9.3.2 are covered — demonstrably, not selectively.
• The report shows outputs (9.3.3): decisions on improvement, system changes, resources.
• The actions from it are tracked — and reappear next time as an input.

What an auditor asks for

• The last review report — and the one before it, as evidence of continuity: were the actions from back then followed up?
• The coverage of the inputs: can it be shown for each 9.3.2 point that it was addressed?
• The presence of top management — the management was in the room, not only on the distribution list.
• A decision that really changed something — a committed resource, an adjusted objective.
• The hand-off: are the resolutions travelling as trackable actions, or did it stay at good intentions?

Common traps

• The formality. A template filled in an hour before the audit, no real walkthrough. Auditors recognise it by the pattern — and by the date.
• Inputs left out. The comfortable points addressed, the uncomfortable ones (missed objectives, complaints) skipped. The list is meant to be complete.
• The QM person’s solo show. Leadership is absent, so no decisions with weight are made. A review without top management is a summary, not a review.
• Outputs without teeth. “We should improve X” without an owner, without a date. A resolution without a task fizzles out by next year.
• Once and never again. The annual ritual with no follow-up on last year’s actions — then the most important input point is missing: what became of what we decided?

Worked example

The management review of Berger Präzisionsteile GmbH is a June morning: Frau Berger, Marco and Lea, three hours. From the year, Lea prepares the input package: the audit results (the setup-sheet finding and its closed chain — 9.2), the objective scorecard (scrap 1.8% met, new-customer share 17% missed — 6.2), the metric trends (9.1), the complaint log, the hardening shop’s supplier performance (the batch error and the crisis that kept the customer — 8.4/7.4) and the updated risk overview (6.1). They walk each 9.3.2 input; the uncomfortable ones get the most time: why 17%, what now?

The outputs (9.3.3): the objectives for next year (the growth objective stays, a new action mix), a resource decision (the second hardening shop confirmed, an additional measuring instrument for the tightened tolerances approved) and the setup-sheet change service made permanent. Each output a task with an owner and a date. The report is two pages, signed. When the certification auditor read it, the setup-sheet chain closed across audit → review → lesson was the strongest single piece of evidence that Berger’s system is alive — not paper, but a decision that had effect.

← All ISO 9001 topics · To the knowledge hub