Management Review in ISO 9001: Why These Meetings Often Waste Time and How to Fix That

2026-10-04

Executive Summary

• Clause 9.3 of ISO 9001:2015 asks top management to review the quality management system to ensure it remains suitable, adequate, effective and aligned with the strategic direction of the organization. It’s a meeting to decide, not to hear reports.
• The output of the review is decisions and actions on improvement opportunities, any need for system change and resource needs. Minutes that say only “reviewed and noted” show a meeting with no output.
• Reviews become a formality when data is compiled by hand and arrives late, figures come with no interpretation, trends are missing, and nobody follows up the actions from last time.
• A simple fix: send a short pre-read, spend meeting time on three to five questions that need a decision, record decisions with owners and deadlines, and follow them up at the next review.
• An eQMS lets inputs be drawn directly from other components, but it won’t make decisions for leadership.

Ninety minutes and forty slides

The management review starts at nine. The CEO and department heads sit around the table. The quality manager presents a dense slide deck: internal audit figures, nonconformity counts, training results, supplier evaluations, one item after another.

After ninety minutes, the CEO nods. The minutes read: “Management has reviewed and noted the above.” The meeting ends. Next year the deck is updated with new figures and presented again.

The records show management review took place, at the right frequency. But one simple question remains unanswered: what did that meeting decide?

If the answer is “nothing specific,” the company has a ritual, not a management mechanism. This article is about that gap.

What clause 9.3 requires

The statements below are based on ISO 9001:2015, clause 9.3 (Management review), summarized in practical terms.

General (9.3.1). Top management reviews the organization’s quality management system at planned intervals to ensure its continuing suitability, adequacy, effectiveness and alignment with the strategic direction of the organization.

Two things to note right away.

First, the subject is top management. Not the quality manager presenting to a leader who happens to attend, but top management itself carrying out the review. This ties to the standard’s expectations of leadership across the whole system.

Second, the purpose includes strategic direction. The question isn’t only “does the system meet requirements” but “does the system still fit where the business is going.”

The standard sets no specific frequency, only “planned intervals.” The organization decides, based on its size, pace of change and decision-making needs.

Inputs and outputs: what they should really contain

The two lists in clause 9.3 show how the meeting is meant to work.

Inputs (9.3.2) must be planned and include consideration of:

• the status of actions from previous reviews;
• changes in external and internal issues relevant to the system;
• information on the performance and effectiveness of the system, including trends in: customer satisfaction and feedback from interested parties; the extent to which quality objectives are met; process performance and conformity of products and services; nonconformities and corrective actions; monitoring and measurement results; audit results; and performance of external providers;
• the adequacy of resources;
• the effectiveness of actions taken to address risks and opportunities;
• opportunities for improvement.

Outputs (9.3.3) are decisions and actions related to:

• opportunities for improvement;
• any need for change to the quality management system;
• resource needs.

The organization must retain documented information as evidence of the results of management reviews.

Read closely, three details deserve emphasis.

The status of last time’s actions is the first input. The meeting can’t start from a blank page; it picks up from the last one.

The standard speaks of trends, not just figures. A number for this quarter tells you little without knowing last quarter’s.

The output is decisions. “Reviewed and noted” is not a decision. Minutes with no decisions, actions or resources mean the meeting has not produced the output the standard describes.

These inputs, seen another way, are the results of the system components covered in earlier articles: internal audit, nonconformities and corrective action, suppliers, competence, risk. The quality of the review depends on the quality of the data from those places.

Why reviews become a formality

Across many manufacturing operations, these signs show up often. (A general observation, not measured figures.)

1. Figures compiled by hand and arriving late. Quality spends days gathering from scattered sources, and figures land just before the meeting, leaving no time for anyone to think about them.

2. Figures without interpretation. A slide lists “12 nonconformities, 8 closed” without saying what that means, whether it’s better or worse, or what to do.

3. No trends. Only the current period, no comparison with the last, so changes can’t be seen.

4. Only quality’s business. The standard mentions strategic direction, changes in context and resources. If the meeting only discusses quality figures, the larger questions never get asked.

5. Last time’s actions aren’t followed. Though it’s the first input under the standard, in practice it’s often skipped.

6. Top management absent or fully delegating. When the decision-maker isn’t there, the meeting can’t produce decisions.

7. Minutes copied from last year. Same structure, same wording, only the date changed.

Illustrative example (a composite scenario, not a real customer case): a company used to run management review with a deck of dozens of slides presented over more than an hour, ending in “noted” minutes. The following year the team changed approach: send a three-page summary in advance with the key trends and three questions needing a decision. The meeting spent most of its time on those three questions and ended with three decisions, each with an owner and a deadline. Next time, the meeting began by checking where those three decisions stood.

How to structure a review that produces decisions

Clause 9.3 doesn’t prescribe the meeting format. Below are common ways to make a review produce real output, not mandatory requirements.

Send a pre-read. A short summary of a few pages with key trends, anomalies and the questions needing a decision. The meeting isn’t for reading figures out; they’ve been read beforehand.

Prepare three to five decision questions. For example: which objectives are being missed and why? Which failures keep recurring and what resource is needed? Which risks have changed? Which suppliers need a second look? Does the system need to change to fit where the business is heading?

Have the right people in the room. Top management and those who can decide on resources, not just those who report.

Show trends. Each indicator displays the previous period and direction of change, with a one-line interpretation.

Look beyond quality. Ask whether the system still fits the business plan: new products, new markets, changes in scale, shifting customer requirements.

Record specific decisions. Each decision has an owner, a deadline and a completion criterion. Avoid phrases like “needs improvement.”

Follow up next time. The next meeting opens by checking last time’s decisions, as the standard makes that the first input.

Frequency in proportion. Some companies run one large session a year plus short quarterly ones focused on indicators and open actions. It depends on each company’s pace of change and decision needs.

A point for smaller companies: a review needn’t be long or formal. A short, focused meeting with clear decisions is worth more than a long one that merely presents.

Management review in eQMS

To be clear first: an eQMS won’t make decisions for leadership, and it won’t make leaders attend or pay attention. A prettier display of data doesn’t replace the conversation about what needs deciding.

What an eQMS changes is how much the inputs depend on manual compilation:

Inputs drawn directly from components. Audit results, nonconformities and corrective actions, supplier performance, training, risk status sit in one system and can be compiled without gathering from separate files.

Trends on hand. Versus the previous period and over time, rather than a snapshot of the current one.

Actions tracked across reviews. Last time’s decisions, owners, deadlines and status are there the moment the next meeting opens.

Decisions linked to action. A decision becomes an action with an owner and deadline instead of sitting in minutes.

History. Decisions and outcomes can be looked back on over several years.

A risk to watch: a handsome dashboard can create a feeling of “reviewed” without a discussion about what needs deciding. Data quality matters too: if data from the components isn’t reliable, neither are the review’s inputs.

When data from many sources flows into one stream, management review starts to have the conditions to become what the standard describes: where data turns into decisions. An approach that brings documents, processes and evidence into a single flow is covered in the next article in this series. And when operational data, such as data from an ERP, also has to feed management decisions, the broader question is what a company should do to use ERP data after implementation.

A practical checklist

Use these questions to review your current management review.

1. Does top management genuinely take part and decide, or just attend to hear reports?
2. Are inputs planned against the list in clause 9.3.2, or just whatever quality has to hand?
3. Are figures sent before the meeting, with time to read them, not compiled just before?
4. Does each indicator show a trend (versus previous period) and interpretation, not just a number?
5. Does the meeting discuss changes in context and strategic direction, not only quality figures?
6. Does the meeting begin by checking the status of last time’s actions?
7. Are three to five decision questions prepared in advance?
8. Do the minutes record specific decisions on improvement, system change and resources, or just “noted”?
9. Does each decision have an owner, deadline and completion criterion?
10. If you compare this year’s minutes with last year’s, are they actually different or only the date?

If three or more answers are “no” or “not sure,” the issue likely lies in how the meeting is designed and run, not in missing data.

A note on ISO 9001 editions

This article refers to ISO 9001:2015. According to certification bodies, a revised ISO 9001:2026 was scheduled for publication in September 2026, with a transition period expected to run about three years and 2015 certificates remaining valid during it. The revision is described as asking more of top management; clause structure and wording may change, so check against the edition your organization is certified to.

Is your management review producing decisions, or just minutes?

→ Take the Knowledge Management Maturity Assessment to identify your maturity level and the first improvement to make.

→ Read next: How OKELAS Organizes eQMS — Document, Evidence, Audit Trail to see an approach that brings documents, processes and evidence into one flow.

Further reading:

• ISO 9001 Clause 6 Risk Management: What’s Actually Required (previous)
• How OKELAS Organizes eQMS: Document, Evidence, Audit Trail (next)
• After ERP: What Should a Company Do to Use Its ERP Data? (related)
• eQMS for Manufacturing SMEs: A Practical Guide (pillar)

Sources:

• ISO 9001:2015, clause 9.3 (management review) and clause 5.1 (leadership): iso.org/standard/62085.html
• LRQA, ISO 9001 revision update: Publication date confirmed (certification body source; verify with ISO): lrqa.com

ISO 9001:2015 clauses are summarized in practical language and do not replace the text of the standard; compliance decisions should be checked against the official edition. The example is a composite illustrative scenario based on common patterns in manufacturing SMEs, not a specific customer case. The signs described are general observations, not measured figures. The ways of structuring a review described are common approaches, not mandatory requirements of the standard.