ISO 22000 clause 9.1: measure food safety performance and use the results
ISO 22000 clause 9.1 requires the organisation to evaluate FSMS performance and effectiveness using appropriate monitoring, measurement, analysis and evaluation. It connects operational evidence with a wider system judgment. Knowing that checks were completed is useful; understanding whether the system meets its planned arrangements and needs improvement is the decision this clause supports.
What clause 9.1 requires in practice
Clause 9.1 requires the organisation to monitor, measure, analyse and evaluate so that it can judge how well the FSMS performs and how effective it is. The general part, 9.1.1, asks the organisation to decide what to monitor and measure, which methods will give valid results, when monitoring happens, when results are analysed, and who does the analysing. Appropriate documented information is kept as evidence.
The second part, 9.1.2, asks for analysis and evaluation of suitable data, including verification results for PRPs and the hazard control plan, internal audits and external audits. Its stated purposes are to confirm performance against planned arrangements, to spot where the system needs updating or improving, to find trends that point to more potentially unsafe product or process failures, to inform internal audit planning and to show that corrections and corrective actions are effective. Analysis results and the activities that follow are retained, reported to top management, and used in management review and system updating.
Decide what information is needed
The general requirements cover what to monitor and measure, suitable methods, timing of collection and evaluation, and who analyses and evaluates the results. Retain appropriate evidence of results.
Choose information linked to FSMS objectives, controls and significant concerns. Include enough context to interpret it. A count of complaints may mean something different after a major change in supply volume or product mix.
Separate measures of activity from measures of effectiveness. Training completion or audit completion can show that work occurred, but additional evidence may be needed to judge competence or effective implementation.
Analyse the system, not just individual events
Analysis and evaluation includes appropriate monitoring and measurement information, verification of PRPs and the hazard-control plan, and internal and external audit results. Bring related evidence together to examine patterns.
The analysis should confirm performance against planned arrangements, identify updating and improvement needs, reveal trends towards potentially unsafe product or process failure, inform audit planning and provide evidence about correction and corrective-action effectiveness.
Keep immediate action distinct from periodic analysis. A serious product concern must be handled promptly through the operational requirements; it should not wait for a quarterly performance report.
Make the conclusion useful to management
Report analysis results to top management and use them in management review and FSMS updating. Explain what the evidence supports, what remains uncertain and what decision is needed.
Retain results and resulting activities. A report should lead to action where the analysis identifies a need. Repeatedly showing the same adverse trend without a decision weakens the value of measurement.
Statistical techniques may be useful where appropriate, but the standard does not require sophisticated software for every analysis. Choose methods that improve the validity and clarity of the judgment.
Why measuring the right things pays off
Without deliberate measurement, a food business learns about its performance from complaints, rejected loads and inspector comments, all of which arrive late and at cost. Choosing and reading measures well lets management see problems while they are still small, and shows whether money spent on training, equipment or audits has changed anything. It also protects against false comfort. Many sites report a high rate of completed checks and few incidents, yet that can hide weak detection. Evaluation that links activity to outcome gives owners and buyers an accurate picture. It supports tender responses, customer scorecards and negotiations with insurers, because claims about food safety performance can be backed with explained evidence.
How to implement clause 9.1
Start from decisions management needs to make, then work back to the data that would inform them.
- List the questions leaders ask about food safety, such as whether failures are recurring or whether a new line is stable.
- Pick a small set of measures that answer them, mixing activity measures with outcome measures and noting what each cannot show.
- Write a one-line definition for each measure covering source, population and period, so every site counts the same way.
- Decide how often results are collected and how often they are analysed, keeping urgent product matters outside the periodic cycle.
- Give each measure an owner who has the competence to interpret it and the authority to propose action.
- Combine verification, audit and complaint information into a short periodic analysis with conclusions, not only charts.
- Send the analysis to top management with a clear request for decisions, and keep the record of what followed.
Illustrative food-manufacturing example
A manufacturer reports a high rate of completed monitoring records. The food safety team compares this with verification findings and discovers recurring uncertainty in how failures are evaluated. Management therefore considers the quality of evaluation alongside record completion.
The resulting action addresses competence and authority rather than setting a still higher completion target. The measure becomes useful because it is interpreted with other evidence.
Illustrative catering example
A caterer sees fewer complaints across several contracts. Analysis shows that one site supplied fewer meals while another changed its reporting route. The team separates those effects before concluding whether food safety performance improved.
It also examines verification and audit evidence to identify whether a favourable complaint trend is consistent with actual control performance.
Evidence and common mistakes
Useful evidence includes clear measure definitions, reliable data, analysis, conclusions and the resulting decisions or activities. Preserve the period and scope so comparisons remain meaningful.
Common mistakes include measuring only what is easy, averaging away important site differences and equating absence of reported incidents with an effective FSMS. Another is changing a measure's definition without explaining the effect on a trend.
Connect the evaluation with objectives and verification analysis. These links help keep information relevant to the system's purpose.
Explore each numbered part
9.1.1 · define measures people can interpret and use
A measure needs a clear purpose, method, timing and evaluator. This guide explains the planning decisions in clause 9.1.1 and the difference between collecting data and evaluating effectiveness. Food-production and logistics examples show how unclear definitions or late analysis can make a performance measure misleading even when the underlying records are complete.
9.1.2 · explain what the evidence says about the FSMS
Analysis should establish whether the FSMS works as planned and what needs to change. This guide explains the required purposes, evidence sources, retained results and management reporting. Manufacturing and catering examples show how to connect verification, audits and operational trends instead of reporting isolated figures that conceal recurring weaknesses or unsupported improvement claims.
Frequently asked questions
Does every requirement need its own KPI?
No. Determine suitable information to evaluate performance and effectiveness without creating unnecessary measures.
Can a dashboard replace analysis?
No. A dashboard presents information; people still need to interpret it and decide what it means for the FSMS.
Must all data use statistical techniques?
No. Use methods appropriate to the information and decision, ensuring results are valid and useful.
Make the next performance review lead to a decision
Discuss your FSMS measures and reporting with Sterling. Support can connect objectives, analysis, learning and suitable Effivity ISO & GRC automation software arrangements. Explore KPIs, Objectives & Management Review, the performance overview and the hub.