ISO 22000 clause 8.8.2: turn verification results into a system judgment
ISO 22000 clause 8.8.2 requires the food safety team to analyse verification results and use the analysis as an input to FSMS performance evaluation. The task is to understand what the results say about the system. A list of completed checks or a percentage of satisfactory results can be useful, but it is not automatically an analysis.
What clause 8.8.2 requires in practice
Individual verification results become useful only when someone looks across them. Clause 8.8.2 gives the food safety team the job of analysing the results of verification activities, and it requires the outcome of that analysis to feed into the evaluation of how well the food safety management system performs, which is dealt with under clause 9.1.2. The clause does not say which technique to use. It asks for a real interpretation: what the results say about how well PRPs and the hazard control plan are working, where there are patterns, and what needs updating or improving. The output is the team's analysis, in a form that management can use to decide what to change. In short, the clause requires judgement about the whole programme, not a tally of individual checks.
Bring results together with their context
Identify the verification activities, periods, products and processes represented. Results from different methods may answer different questions. Keep those differences visible before combining them into a headline measure.
Consider coverage and opportunity. A reduction in findings can reflect genuine improvement, fewer checks or a narrower sample. The team needs to know which explanation is supported before presenting a favourable conclusion.
Include adverse findings and the relevant actions, while ensuring immediate product and process responses have already been addressed. Analysis is not a reason to delay action on an individual result that requires prompt attention.
Why clause 8.8.2 matters to the business
A list of passed checks can look reassuring while hiding a trend, a coverage gap or a recurring weakness at one site. Analysis lets the business spot these early and put effort where it counts, rather than discovering them through a complaint or an inspection. It also gives senior managers a sound basis for decisions about resources and priorities, because the results are explained instead of just reported. Without this step, verification risks becoming a data collection exercise that costs time and changes nothing.
How to implement clause 8.8.2
Treat the analysis as a regular, structured review with conclusions and actions, not as a chart for the next meeting. Keep the presentation simple, with a short narrative of what the team concluded and why, and only the data needed to support that conclusion for the reader.
- Gather results from all verification activities for the period, with the products, processes and sites each one covered.
- Check coverage and opportunity: whether fewer findings reflect improvement or simply fewer or narrower checks.
- Look for patterns by shift, location, product, supplier or type of finding, and for links to recent changes.
- Ask whether any pattern challenges the assumptions behind the hazard analysis, the PRPs or the control plan.
- Write down the conclusions, the evidence, the uncertainties and the actions with owners.
- Send the analysis to performance evaluation and use it to decide on updates under the system updating process.
- Check later whether the actions that followed made a measurable difference.
Look for patterns and connected weaknesses
Examine recurring issues, differences across shifts or locations and relationships with changes in materials, equipment or work. A series of individually minor findings may indicate a broader weakness in the PRP or hazard-control arrangement.
Ask whether results challenge the assumptions behind the plan. Repeated monitoring or verification difficulties may indicate that instructions, competence, resources or the control arrangement need review. Avoid interpreting every finding as an isolated personnel error.
Consider whether the verification programme itself remains suitable. If known problems are discovered only through complaints while verification remains consistently satisfactory, the methods or coverage may need examination.
Use the analysis in performance evaluation
Connect the team's conclusions with clause 9.1.2, which addresses broader analysis, its purposes, retained results and reporting to management. The verification analysis should help identify needs for updating or improvement and support evaluation of corrective-action effectiveness.
Make conclusions actionable. Identify what the team believes, the supporting evidence and any uncertainty or further work needed. A chart without interpretation can leave management unable to decide what should change.
Keep the connection with FSMS updating. Where the evidence suggests that hazard analysis, a control plan or PRPs need review, assign that work rather than simply adding the issue to the next report.
Illustrative food-manufacturing example
A manufacturer sees repeated verification findings associated with one product-change sequence. Each event has been corrected, but the team combines the results and identifies a pattern linked to the same handover. It investigates the arrangement and checks whether the corrective action addresses the shared cause.
The useful conclusion goes beyond the count of closed findings. It asks whether the system now controls that sequence more reliably.
Illustrative catering example
A catering business reports fewer PRP verification findings across its sites. The food safety team discovers that the number of observed evening services also fell. It separates the change in coverage from the performance conclusion and plans appropriate additional review.
This prevents a favourable percentage from being presented as proof of improvement when the evidence does not yet support that interpretation.
Evidence and common mistakes
Useful analysis records identify the data considered, methods, conclusions and resulting activities. The linked performance-evaluation requirements specify retention and reporting. A spreadsheet, report or meeting record can work if it preserves the reasoning.
Common mistakes include averaging unlike results, ignoring missing data, reporting only favourable measures and repeatedly presenting the same trend without deciding what it means. Another is treating action closure as evidence of effectiveness without examining later performance.
Read this guide with verification planning. Good analysis needs results from activities designed to answer useful questions.
Frequently asked questions
Does analysis require statistical software?
No. Use suitable methods for the information and decision. More complex tools are useful only when they improve understanding.
Who performs this analysis?
The food safety team has the specific responsibility, drawing on relevant process and technical input.
Is a pass-rate chart enough?
Only if it supports a meaningful evaluation with appropriate context. Coverage, repeated failures and consequences may need additional examination.
Turn verification data into a useful management decision
Bring Sterling a set of verification results for a scoped analysis review. Support can connect interpretation, improvement actions and suitable Effivity ISO & GRC automation software arrangements. Review ISO 22000 Food Safety Awareness, the verification guide and the hub.