ISO 22000 clause 9.3: make management review a food safety decision forum
ISO 22000 clause 9.3 requires top management to review the FSMS at planned intervals for continuing suitability, adequacy and effectiveness. The review brings together performance, changes and resource needs so management can decide what to improve or update. Its value is the quality of the resulting decisions, not the length of the presentation.
What clause 9.3 requires in practice
Clause 9.3 makes top management responsible for reviewing the FSMS at planned intervals, so as to confirm its continuing suitability, adequacy and effectiveness. It is divided into a general requirement (9.3.1), required inputs (9.3.2) and required outputs (9.3.3).
The inputs range widely: the status of earlier review actions, changes in internal and external issues, performance and effectiveness trends, resource adequacy, emergencies, incidents and withdrawals or recalls, relevant communication including complaints, and opportunities for improvement. The trends cover system updating, monitoring and measurement, verification analysis, nonconformities and corrective actions, audits, inspections, external provider performance, risks and opportunities, and objectives. The data should be presented so leaders can relate it to the FSMS objectives. Outputs include decisions and actions on improvement and any need to update or change the FSMS, including resources and revisions to policy and objectives. Documented information is retained as evidence of the results.
Plan a review that can influence the system
The general requirement establishes top management's role and planned intervals. Determine arrangements that provide timely oversight of the actual organisation. A single annual meeting is not prescribed as the only possible format.
Give management enough information to assess whether the system fits the operation, has sufficient arrangements and resources, and works in practice. These are related but different questions. A well-documented system can still be inadequately resourced.
Keep urgent operational decisions outside the waiting list for a future review. Management review complements immediate product and incident response rather than delaying it.
Bring the required inputs together
Review inputs include earlier actions, relevant context changes, performance and effectiveness trends, resource adequacy, emergencies and withdrawals or recalls, relevant communication and improvement opportunities.
Performance information includes updating, monitoring, verification analysis, nonconformities, audits, inspections, providers, risk-and-opportunity actions and objectives. Present it so management can relate the evidence to the FSMS objectives.
Explain the meaning and limitations of the information. A traffic-light dashboard without supporting context can conceal recurring failures or changes in measurement coverage.
Record decisions and follow them through
Outputs include decisions and actions on improvement opportunities and necessary FSMS updates or changes, including resources and possible policy or objective revisions. Retain documented evidence of the review results.
Make action ownership and intended completion clear as practical implementation choices. The record should distinguish a decision from a topic merely discussed. Follow up earlier actions at subsequent reviews and evaluate whether they achieved the intended result.
Connect outputs with FSMS updating. A management decision to change an arrangement needs to reach the people who maintain hazard analysis, PRPs and the control plan where relevant.
Why management review is where food safety gets resourced
Technical teams can see most food safety weaknesses but cannot always fix them. Fixing often needs a budget for equipment, a decision about staffing or a change to commercial arrangements, and these sit with top management. A review that brings the right evidence to the right people turns known problems into funded decisions. It also keeps leaders accountable for the system they say they stand behind. Businesses where this works spend less time firefighting, because causes are addressed at the level where they can be resolved. For customers, a record showing that top management examined food safety performance, asked questions and made decisions is some of the strongest reassurance a supplier can give.
How to implement clause 9.3
Plan management review as a decision session with a short, evidence-led pack and named owners for every outcome.
- Agree with top management how often reviews occur and who must attend, allowing earlier sessions when a major event or change requires it.
- Build a standard input list from 9.3.2 and assign someone to produce each item with an explanation, not just raw figures.
- Link the pack to the FSMS objectives so leaders can see which are on track and which are not.
- Keep the pack short by referencing detailed reports instead of reproducing them, while making sure the conclusions are visible.
- During the meeting, steer discussion towards decisions about resources, changes and priorities, and record each one clearly.
- Give each action an owner and a completion point, and communicate decisions to the teams that maintain the plan and PRPs.
- Open the next review by checking whether earlier actions achieved their intended effect.
Illustrative food-manufacturing example
A manufacturer presents recurring verification weaknesses alongside maintenance and staffing information. Management identifies a resource and scheduling issue that individual corrective actions had not resolved. It approves a defined change and requests evidence of its effect.
The review therefore changes the operating conditions behind the findings. It does not merely note that the food safety team has been busy closing actions.
Illustrative catering example
A catering group reviews a new contract model that adds remote service locations. Management considers whether competence, communication and oversight remain adequate as the business changes. It assigns the necessary review and resource decisions before expansion is treated as routine.
The review uses evidence from existing sites while recognising where the new arrangement differs. A standard group presentation does not replace local evaluation.
Evidence and common mistakes
Retain review results with a clear connection to the information considered and resulting decisions. Inputs may be held in linked reports rather than repeated in full within minutes, provided the record remains understandable.
Common mistakes include a review performed without top management, inputs copied from the prior year, actions with no follow-up and favourable totals that conceal important site differences. Another is recording “system effective” without showing the basis or addressing contradictory evidence.
Explore each numbered part
9.3.1 · give top management a real view of the FSMS
Top management needs to know whether the FSMS still fits the business, has enough support and works as intended. This guide explains the purpose and timing of management review. Food-manufacturing and catering examples show why growth, changed operations and recurring problems can challenge suitability or adequacy even when routine reports appear satisfactory.
9.3.2 · prepare management-review inputs that explain performance
Management-review inputs should give leaders an accurate basis for decisions. This guide explains the required topics and how to relate the information to FSMS objectives. Manufacturing and catering examples show how analysis, resource concerns and changed operating conditions can be presented clearly without burying important findings in an unfiltered collection of records.
9.3.3 · turn management review into owned changes
Review outputs should identify what management decided and what needs to happen next. This guide explains improvement decisions, FSMS updates, resource needs and possible policy or objective revisions. Food-manufacturing and catering examples show how to turn a discussion into a clear action and how to preserve evidence of both the decision and its eventual effect.
Frequently asked questions
Must management review be one annual meeting?
No. It must occur at planned intervals and address the required scope. Choose a suitable arrangement that produces coherent results.
Can the food safety team replace top management in the review?
The team provides important input, but the review responsibility belongs to top management.
Does every review require new objectives?
No. Consider whether revision is needed. The decision should follow the evidence and the system's needs.
Prepare a review that produces a useful decision
Discuss management-review preparation with Sterling, including input quality, decisions and follow-up. Suitable Effivity ISO & GRC automation software support can connect agreed evidence and actions. Explore KPIs, Objectives & Management Review, the performance guide and the hub.