ISO 22000 clause 9: evaluate whether the food safety system works
Clause 9 of ISO 22000 evaluates the performance and effectiveness of the FSMS. It brings together monitoring and measurement, analysis, internal audit and management review. The purpose is to understand whether the system achieves its intended results and what needs attention, rather than simply producing a favourable dashboard for an external audit.
What clause 9 requires in practice
Clause 9 asks the organisation to find out, with evidence, whether its food safety management system is performing as planned. It has three parts. Clause 9.1 covers monitoring, measurement, analysis and evaluation of performance and effectiveness. Clause 9.2 requires internal audits at planned intervals to show whether the system conforms to the organisation's own requirements and to the standard, and whether it is effectively implemented and maintained. Clause 9.3 requires top management to review the system for continuing suitability, adequacy and effectiveness.
The parts depend on one another. Verification results for the prerequisite programmes and the hazard control plan (8.8) feed the analysis in 9.1.2; that analysis shapes the audit programme and goes to management review; and review outputs go on to system updating under 10.3. The outputs the standard expects include retained analysis results, audit programme and report records, and management review records. The format is left to the organisation.
9.1: define useful evaluation and analyse the results
Under 9.1.1, determine what needs monitoring and measurement, methods that produce valid results, timing and responsibility for analysis and evaluation. Retain appropriate evidence and evaluate FSMS performance and effectiveness. Clear definitions matter when different sites contribute data to a group report.
Analysis under 9.1.2 includes relevant monitoring, PRP and hazard-control verification, and internal and external audit information. Use it to assess whether planned arrangements and FSMS requirements are met, identify updating or improvement needs and recognise trends indicating more process failures or potentially unsafe product.
The analysis also informs the audit programme and provides evidence about corrections and corrective actions. Retain the results and resulting activities, report them to management and use them in review and system updating. A trend is useful only if someone can explain its significance and the action or decision it warrants.
9.2: audit the implemented system
Internal audits at planned intervals examine conformity with the organisation's own FSMS requirements and ISO 22000, together with effective implementation and maintenance. Audit should follow real operations and evidence. A completed document checklist cannot establish whether a control is used correctly on the night shift.
Plan the programme with attention to process importance, changes, monitoring and measurement results and previous audits. Define criteria and scope for each audit. Select competent auditors and organise work to support objectivity and impartiality. Report results to the food safety team and relevant management and retain programme and result evidence.
Necessary correction and corrective action should occur within agreed timeframes. Follow-up verifies the actions and reports the results. The audit process also considers whether the FSMS meets the intent of the policy and objectives. Closing a finding because a document was edited may be insufficient when the finding concerned ineffective practice.
9.3: use management review to make decisions
Top management reviews the FSMS at planned intervals for continuing suitability, adequacy and effectiveness. Inputs include previous actions and changes in context, as well as performance information. Relevant trends span system updating, monitoring, verification, nonconformities, audits, inspections, provider performance, planning actions and objectives.
Resources, emergencies, incidents, withdrawals or recalls, communications and improvement opportunities also matter. Present the information so that management can relate it to FSMS objectives. Large volumes of unanalysed data can obscure the issues requiring leadership attention.
Outputs include decisions and actions about improvement and necessary FSMS updates or changes, including resources and revisions to policy or objectives. Retain documented results. Useful records distinguish the issue discussed, the decision, responsibility and follow-up, rather than merely listing agenda headings.
Why evaluation decides whether the system is trusted
A food safety system can look complete and still fail on the night shift. Performance evaluation is how the business discovers that for itself rather than through a customer complaint or an adverse inspection. It tells owners where controls are drifting, whether resources match the risk and which sites or processes deserve attention. For buyers, evidence of accurate evaluation is as persuasive as the controls themselves, since it shows the organisation can detect and correct its own weakness. For an independent assessment, a system that has already examined itself through analysis, audit and review is far more likely to present consistent evidence. It also saves money by directing effort to the places where failures are actually concentrated.
How to implement clause 9
Treat clause 9 as one connected cycle with a clear owner, rather than three separate administrative tasks.
- Decide the questions the system should answer, such as whether controls are working, whether failures are repeating and whether resources are enough.
- Define the measures, data sources and owners for each question, and agree how verification results will be fed in.
- Schedule analysis so that results reach the audit planner before the programme is set, and reach top management before each review.
- Plan internal audits around process importance and recent change, using competent and impartial auditors.
- Prepare management review packs that tie evidence to the food safety objectives and highlight decisions needed.
- Track every action from audit and review to completion and to a check that it worked.
- Look back across the cycle at least once for gaps, such as measures nobody used or findings that never reached management.
- Adjust the programme as products, sites and customers change.
Illustrative example: repeated manufacturing record gaps
A hypothetical food manufacturer notices monitoring-record gaps concentrated during a particular handover. Analysis distinguishes missing evidence from confirmed process deviations and investigates both appropriately. The internal audit examines how responsibilities and actual practice align.
Management review considers whether the process needs staffing, training or a revised handover. It does not accept a lower count of reported gaps as improvement without checking whether recording became more reliable. The example illustrates evaluation of the system, not a conclusion about the safety of affected product.
Illustrative example: comparing catering locations
A hypothetical caterer compares verification findings across several workplace sites. One site reports fewer findings, but its checks cover fewer activities. The group first aligns the meaning and coverage of the data before judging relative performance.
The analysis identifies a common provider-communication weakness and informs the audit programme. Management assigns resources to address the interface and asks for evidence of effectiveness. This avoids rewarding a site merely for conducting fewer checks or reporting less information.
Evidence and frequent mistakes
Retained evidence includes monitoring and evaluation results, analysis and resulting activities, internal-audit programme implementation and results, and management-review results. The exact reporting format is a practical choice. An auditor may trace a recurring issue through analysis, decision and follow-up.
Frequent weaknesses include treating absence of complaints as proof of safety, mixing incomparable measures, repeating audit plans without considering changes and review minutes with no decisions. Another is treating operational verification under 8.8 as identical to a system audit. They contribute different evidence and need a clear relationship.
Explore each numbered part
9.1 · measure food safety performance and use the results
Performance evaluation connects monitoring data with a judgment about the FSMS. This guide explains what to measure, how and when to evaluate it, and how results support updating, audit planning and improvement. Manufacturing and catering examples show why activity counts, attractive dashboards and isolated pass rates need context before they can support a management decision.
9.2 · audit the food safety system for useful evidence
Internal audits should test how the FSMS works, including its own requirements and ISO 22000. This guide explains programme planning, scope, criteria, auditor competence, impartiality, reporting and follow-up. Manufacturing and catering examples show how to follow evidence through a process and use changes or previous findings to select meaningful audit priorities.
9.3 · make management review a food safety decision forum
Management review should help top management decide whether the FSMS remains suitable, adequate and effective. This guide connects review timing, required inputs, meaningful presentation and recorded outputs. Manufacturing and catering examples show how to turn trends, incidents and resource concerns into decisions rather than treating the review as an annual recital of completed activities.
Frequently asked questions
Must management review be a single annual meeting?
The requirement concerns planned intervals and complete consideration of the relevant inputs and outputs. The organisation can use suitable management arrangements if the review process and results remain demonstrable.
Can a general management-system auditor audit food safety?
Auditors need competence appropriate to the scope and criteria. General audit skills are useful but may need food safety and process knowledge to examine technical evidence meaningfully.
Does a successful internal audit certify the organisation?
No. It is an internal evaluation activity. Organisational certification is a separate decision by an independent certification body.
Make evaluation useful before the next external audit
Sterling can support performance-review methods, internal-audit preparation and management-review documentation. Agreed Effivity ISO & GRC automation software and employee learning can connect evidence with action. Request a free consultation about your evaluation gaps. Review ISO 19011 Auditing Management Systems and KPIs, Objectives and Management Review for the related skills, alongside the technical competence required for food safety work.
Return to clause 8 operation or the requirements hub; continue to clause 10 improvement.