ISO 9001 clause 9.3.2: prepare management-review inputs
ISO 9001:2026 clause 9.3.2 identifies the inputs that management review must include. These inputs provide the evidence for leadership to evaluate the QMS, rather than merely listen to a status presentation. They should make relevant change, performance and unresolved needs understandable enough to support a decision.
What clause 9.3.2 requires in practice
Clause 9.3.2 lists what a management review has to take into account. The review begins with the status of actions from earlier reviews. It then considers changes in external and internal issues relevant to the system, and changes in what interested parties need and expect. Next comes information on system performance, including trends in nonconformities and corrective actions, results from monitoring and measurement, audit results, customer satisfaction and feedback from other relevant interested parties, how far quality objectives are met, how well processes perform and how far products and services conform, and how external providers perform. The review also looks at opportunities for improvement, whether resources are adequate, and how effective the actions on risks and on opportunities have been, which are considered separately. Trends are the important word: a single figure tells little, but its direction shows whether the system is getting stronger or weaker. The standard does not dictate the format of the inputs.
Show what changed and what remains open
Begin with the status of actions from previous management reviews. Explain whether decisions were implemented and what remains unresolved. A completed action may still need outcome evidence; an overdue action may require a new resource or priority decision. Simply copying the previous action list does not provide that understanding.
Include changes in relevant external and internal issues, and changes in the needs and expectations of interested parties relevant to the QMS. These are distinct considerations in the 2026 clause. A new delivery model, customer requirement or relevant external condition may affect the system even before it appears in a performance trend.
Bring performance trends into one useful view
The review needs information about nonconformities and corrective actions, monitoring and measurement results, audits, customer satisfaction and relevant interested-party feedback. It also considers achievement of quality objectives, process performance, product and service conformity, and external-provider performance. Present the information with enough context to reveal significance rather than treating every item as an isolated total.
Trends need consistent definitions and an appropriate comparison. Explain material changes in volume, work mix or measurement method. A rise in recorded nonconformities may reflect improved reporting; a falling complaint count may conceal lost customer engagement. The review should assess what the evidence supports and what remains uncertain.
Include improvement opportunities and resource adequacy. In the 2026 structure, review the effectiveness of risk actions under clause 6.1.2 and opportunity actions under clause 6.1.3 distinctly. Completion of the planned activity is not, by itself, proof that either purpose was achieved.
Why clause 9.3.2 matters to the business
Leadership decisions are only as good as the information in front of them. When inputs are complete, comparable over time and accurate about weaknesses, managers can see connections that individual reports hide, such as audit findings matching a provider's slipping delivery, or rising complaints following a change in staffing. When inputs are partial or flattering, review becomes a ritual. Preparing the inputs also forces process owners to think about their own performance before senior colleagues do. The business benefits from earlier warnings, fewer surprises in customer relationships and more convincing evidence of control when customers or assessors ask how leaders stay informed.
How to implement clause 9.3.2
Prepare the inputs as a single, short evidence pack that mirrors the clause. Resist the temptation to attach every report; a one-page summary per input with a link to detail is usually enough, and it leaves the meeting room to discuss what the trends imply.
- Turn the clause's list into a template with a heading for each input and a named owner who supplies it.
- Begin the pack with the status of actions from the last review, showing what was done and what remains open.
- For each performance input, show the direction over several periods and a short explanation of the cause.
- Summarise changes in internal and external issues and in interested party expectations, noting which could affect the system.
- Present risk actions and opportunity actions separately, each with a view of what they achieved.
- Mark where an input has not changed materially, rather than dropping it silently.
- Add the proposals that the owners want leaders to decide, so the review has something concrete to resolve.
Illustrative IT example: growth and support capacity
An IT provider prepares a review after expanding its managed-service customer base. The input pack connects growth in support demand, response performance, reopened cases, customer feedback and staff competence information. It also reports the status of a previous decision to improve escalation coverage.
The analysis shows that routine requests are handled well but complex cases wait for a small group of specialists. Management can therefore consider resource adequacy and the effectiveness of the earlier action. A page reporting only total tickets closed would hide the issue and provide a weaker basis for deciding how to support further growth.
Illustrative construction example: a supplier improvement initiative
A contractor introduced an opportunity action to standardise selected prefabricated components across projects. Review inputs compare delivery consistency, installation rework and provider performance before and after the initiative, while noting differences between projects. They also include customer feedback and changes in project requirements that affect the proposed wider use.
The evidence shows where standardisation helped and where additional coordination is needed. Management can evaluate the opportunity action separately from risk controls for unsuitable materials. The review does not assume that an initiative is beneficial simply because it was completed or described as innovative.
Prepare a clearer evidence base for leadership
Sterling can help improve management-review preparation, including scoped support from Effivity ISO & GRC automation software where agreed. The independent certification body retains its own assessment and decision.
The live KPIs, Objectives and Management Review course offers relevant learning for input owners and reviewers. Register interest in forthcoming QMS courses for wider system understanding.
Common nonconformities with clause 9.3.2
Typical findings show gaps or shallow treatment of the listed inputs. Weak preparation is usually visible in the pack itself.
- One or more inputs, such as provider performance or customer feedback from other interested parties, is not considered.
- Results are presented as single figures with no trend over time.
- The status of actions from previous reviews is not reported.
- The effectiveness of risk actions and opportunity actions is merged or not examined.
- Inputs describe activity, such as audits completed, but not what the results showed.
Frequently asked questions
Must every input have its own slide or report?
No. The organisation chooses a practical format. Related information can be combined where it remains clear that the required subjects were considered. A fixed template is less important than complete and useful review information.
How should an input with no significant change be handled?
A supported statement that the relevant area was reviewed and no significant change was identified can be appropriate. Avoid treating an empty field as evidence of consideration, especially where circumstances suggest that a change may matter.
Why separate risk actions from opportunity actions?
The 2026 clause identifies their effectiveness separately. Risk actions and opportunity actions can have different intended outcomes. Keeping the evaluation distinguishable helps management see whether each action achieved its purpose rather than merely being completed.
Prepare for decisions rather than presentation volume
Identify the significant conclusion for each relevant input and the decision it may require. Where evidence is incomplete, explain what is missing and why it matters. This is more useful than filling every agenda line with a reassuring statement that cannot be traced to current information.
Data owners can prepare their parts, but the combined review should reveal relationships across processes. Customer dissatisfaction, provider failures and repeated rework may share an underlying cause. Leadership needs that connection to assess the QMS as a system rather than approve separate departmental reports.
Common failures include omitting interested-party changes, reporting only average KPI results, ignoring previous actions and merging risk and opportunity actions into one completion percentage. Another is presenting raw audit findings without explaining repeated themes or their effect on the system. Keep the input factual, current and relevant.