Management review is mandatory in every ISO management system standard — clause 9.3 in the High-Level Structure, with specific inputs and outputs the review must address. Most organisations hold management reviews because the clause requires it; far fewer use them to produce the decisions and improvements the clause was designed to drive. A management review that produces minutes but no decisions has satisfied the documentation requirement and failed the operational one. The reviews that move the management system look structurally different.
What the Standards Actually Require
The HLS clause 9.3 requires top management to review the management system at planned intervals to ensure its continuing suitability, adequacy, effectiveness, and alignment with strategic direction. The required inputs include status of previous review actions, changes in external and internal issues, performance and effectiveness information, audit results, customer satisfaction or stakeholder feedback, nonconformities and corrective actions, monitoring and measurement results, audit findings, performance of external providers, adequacy of resources, effectiveness of risk treatments, and opportunities for improvement. The required outputs include decisions and actions on continual improvement, changes to the management system, and resource needs.
Where Reviews Most Often Fail
Status-update meeting. The review covers what happened in the past period without producing decisions about what to do next. The standard's required outputs are absent because nothing in the meeting structure produces them. Wrong attendees. Top management does not attend; the review is led by middle management who report up later. The standard explicitly requires top management; without them, the decisions the clause demands cannot be made in the meeting. Too much, too little. Reviews trying to cover everything go three hours and produce no decisions; reviews going 30 minutes skip the substantive analysis. The discipline is calibrating the depth to the topics that warrant attention.
A test for management review effectiveness: when the next review opens, are participants reviewing the actions from the previous review? If "yes, and the actions were completed or have explicit reasons for not being completed" — the review process works. If the actions from the previous review have not been touched and nobody noticed — the review is a meeting, not a management process.
Designing for Decisions
Strong management reviews are designed around decisions. Each agenda item identifies a decision the meeting needs to make, the information required to make it, and who needs to be present for the decision to be valid. Items that do not require a decision are handled as pre-read briefings — distributed before the meeting, acknowledged in the meeting if needed, but not consuming meeting time. The meeting becomes a decision-making forum rather than a status-update broadcast.
Frequency and Scope
The standard requires reviews at planned intervals but does not specify frequency. Annual full reviews are the most common cadence and the most common failure mode — too infrequent for emerging issues, too compressed for genuine analysis. Stronger practice runs a full review annually with focused topical reviews quarterly. The topical reviews handle specific dimensions (audit results, risk treatment effectiveness, supplier performance) at depth; the full review synthesises across them. Both produce decisions; the cadence is matched to the topic.
Components of a Review That Drives Improvement
- Top management present and actively engaged; the meeting does not happen without them
- Pre-read materials covering required inputs distributed in advance, not presented in the meeting
- Agenda structured around decisions, with the meeting time used for decision-making
- Required outputs explicitly captured — decisions, actions, resource commitments, system changes
- Action tracking that survives between reviews and is verified at the next review
- Topical reviews complementing the full annual review at risk-proportionate cadence
- Minutes that record decisions and reasoning, not just what was discussed
When the Discipline Earns Its Operating Cost
A management review designed for decisions produces measurable improvement in the management system over time — audit findings decrease, performance metrics improve, the system continues to evolve with the organisation. A management review designed for the clause produces an annual paperwork exercise that satisfies the auditor and otherwise consumes top management time without proportional benefit. The investment is in the design and the discipline of running the meeting as a decision-making forum rather than as a documentation event.