ISO 22000 clause 9.3.2: prepare management-review inputs that explain performance
ISO 22000 clause 9.3.2 defines the information management review must consider. It includes earlier actions, relevant changes, performance and effectiveness, resources, incidents, communication and improvement opportunities. The data must be presented so top management can relate it to the FSMS objectives. A complete agenda is useful only when the information under it supports a real judgment.
What clause 9.3.2 requires in practice
Clause 9.3.2 lists what the management review has to consider. It begins with the status of actions from previous reviews and with shifts in the internal and external issues that bear on the FSMS, among them changes to the organisation and its context under 4.1.
It then lists performance and effectiveness information, including trends in system updating, monitoring and measurement, analysis of verification results for PRPs and the hazard control plan, nonconformities and corrective actions, internal and external audit results, inspections by regulators and customers, external provider performance, the review of risks and opportunities with the effectiveness of actions taken, and the extent to which objectives are met. Further inputs are the adequacy of resources, any emergency, incident or withdrawal or recall, relevant external and internal communication including requests and complaints, and opportunities for continual improvement. The data has to be presented so that top management can relate it to the stated objectives of the FSMS. How the pack is laid out is the organisation's choice.
Start with earlier commitments and changed circumstances
Report the status of actions from previous reviews. Distinguish completed work from demonstrated results and identify overdue or ineffective actions. Management needs to know whether its earlier decisions produced the intended outcome.
Explain relevant external and internal changes, including changes in the organisation and its context. Consider new products, sites, service arrangements, requirements or other relevant developments. Link the information to the FSMS implications rather than presenting a general business update.
Where climate change has been determined relevant under context evaluation, relevant changes can form part of this review input. The amendment does not create a universal environmental programme within every FSMS.
Present the required performance picture
Include trends in system updating, monitoring and measurement, verification-result analysis, nonconformities and corrective actions, internal and external audits, inspections and external-provider performance.
Also review risks and opportunities and the effectiveness of actions taken to address them, together with the extent to which FSMS objectives have been met. Keep organisational risk planning distinct from technical hazard analysis while explaining their relevant connections.
Use analysis and evaluation to interpret the evidence. Counts without context can conceal recurring failures or make changed reporting appear to be changed performance.
Include resources, events and communication
Assess resource adequacy, including relevant competence and operational support. Report emergencies, incidents and withdrawals or recalls that occurred. Explain what they reveal about both the event's cause and the organisation's response capability.
Bring relevant internal and external communication, including interested-party requests and complaints. Commercial or supplier information can signal an FSMS change even when it arrives outside the food safety team's usual reporting system.
Identify opportunities for continual improvement. These can arise from successful practice as well as failures, but proposed changes still need a suitable basis and evaluation.
Why the quality of review inputs shapes the decision
A review can only be as good as what it is shown. Packs padded with raw inspection sheets hide the issues leaders need to see, while packs with only good news produce confident decisions on a false picture. Well-prepared inputs make the meeting short and productive: leaders see how earlier decisions turned out, what has changed in the business, where failures cluster and where resources are stretched. Including provider performance, complaints and recalls also surfaces issues that originate outside the food safety team, such as a supplier change or a commercial promise. Because the pack ties evidence to objectives, leaders can judge whether the system is delivering what the business promised its customers, and decide where to act.
How to implement clause 9.3.2
Prepare the review pack as a structured explanation of performance, built from the same sources every time and tailored to current events.
- Create an input checklist taken from the clause so that no required topic is forgotten, and give each topic an owner.
- Start the pack with earlier actions, marking which finished, which show the intended effect and which are overdue or ineffective.
- Describe relevant changes in products, sites, customers, suppliers and requirements and say what each means for the FSMS.
- Present trends for each performance topic with a sentence of interpretation, noting any change in how data was collected.
- Cover resources, incidents, recalls and communication candidly, including complaints that came through commercial channels.
- Keep detail in referenced reports and show the objectives alongside the evidence, so leaders can see the link.
- Finish with a list of opportunities and decisions requested, so the meeting knows what it is expected to settle.
Illustrative food-manufacturing example
A manufacturer prepares a review pack showing repeated verification findings, the status of related actions and the resource conditions contributing to delay. It explains how those findings affect a stated food safety objective.
Management can then consider a specific resource or process decision. A large appendix of unanalysed inspection sheets would have made the same issue harder to assess.
Illustrative catering example
A catering group reports a changed contract pattern, site-level complaints, audit results and competence needs together. It identifies where the new service arrangement creates additional oversight demands.
The presentation preserves differences between sites instead of combining every result into one favourable average. This supports a decision targeted to the actual weakness.
Evidence and common mistakes
Use a clear relationship between the required topics, supporting analysis and objectives. A checklist can help confirm coverage, but avoid duplicating every source record in the review pack. Retain the review results under the output requirement.
Common mistakes include omitting provider performance, reporting action closure without effectiveness, hiding adverse trends and presenting resource requests without explaining the food safety need. Another is repeating last year's inputs despite material changes.
Record limitations and unresolved questions where they affect the decision. Clear uncertainty is more useful than unsupported reassurance.
Frequently asked questions
Must every input be discussed in equal detail?
No. All required topics need appropriate consideration, with depth suited to significance and the evidence.
Are complaints relevant if they came through sales?
Yes, where they are relevant to the FSMS. The original reporting channel does not determine their importance.
Should raw data be included?
Provide enough supporting evidence, but present analysis and meaning so management can relate results to objectives and decisions.
Prepare an input pack management can act on
Discuss management-review inputs with Sterling, including gaps, trends and objective alignment. Suitable Effivity ISO & GRC automation software support can accompany the agreed evidence arrangement. Review KPIs, Objectives & Management Review, the review guide and the hub.