ISO 22000 clause 9.1.2: explain what the evidence says about the FSMS

What clause 9.1.2 requires in practice

Clause 9.1.2 requires the organisation to analyse and evaluate suitable data and information from monitoring and measurement. That includes verification results for the PRPs and the hazard control plan, internal audit results and external audit results. The analysis serves five purposes: to confirm overall performance matches what was planned and what the organisation itself requires of its FSMS, to spot where updating or improvement is needed, to reveal trends pointing to more potentially unsafe product or process failures, to supply information for planning the internal audit programme, and to show whether corrections and corrective actions have worked.

Results and the resulting activities are retained as documented information. They are reported to top management and used as inputs to management review and to system updating under 10.3. A note in the standard mentions statistical techniques as one possible method. The clause is about drawing conclusions the organisation can act on, not about producing a particular type of report.

Use the required purposes to organise the analysis

Determine whether overall performance meets planned arrangements and the organisation's FSMS requirements. Identify where the system needs updating or improvement. Look for trends suggesting more potentially unsafe product or process failures.

The analysis also informs the internal audit programme by identifying the status and importance of areas to audit. It should provide evidence that corrections and corrective actions are effective. These purposes go beyond producing a general monthly score.

Use relevant information together. A favourable monitoring trend can be challenged by audit findings that reveal unreliable recording. Conversely, a temporary increase in reported issues may reflect improved detection rather than worsening control. Interpret the context.

Make comparisons meaningful

Check definitions, periods, coverage and the conditions represented. Where volume or product mix changes, consider whether a direct comparison remains valid. Preserve important differences between locations or processes instead of averaging them away.

Use suitable methods, including statistical techniques where they help. The standard does not require advanced analysis for every dataset. A well-explained pattern with clear supporting evidence can be more useful than an elaborate chart with uncertain inputs.

State limitations. Missing records, changed methods or restricted sampling may affect the conclusion. Reporting uncertainty accurately allows management to decide what further evidence or action is needed.

Report conclusions and retain resulting activities

Retain the analysis results and the activities that follow. Report the results to top management and use them in management review and FSMS updating.

A useful conclusion explains the issue, supporting evidence, implication and proposed decision. For example, repeated verification failures in one process may justify a focused audit or review of the control arrangement.

Check whether actions taken after previous analyses changed performance. Otherwise, the reporting process can repeatedly identify the same weakness without establishing improvement.

Why analysis turns data into management action

Most food businesses already collect large volumes of records. The gap is usually interpretation: nobody has time to ask what the records say together. Analysis closes that gap and delivers practical benefits. Hidden trends, such as a particular shift or product sequence producing repeated failures, become visible. Audit programmes can focus on areas that really need attention. Corrective actions can be judged on whether the problem stopped, not whether the form was signed. Management receives a short, reasoned message instead of a pile of sheets, which makes resource requests easier to approve. Where analysis is missing, leaders tend to learn about weaknesses from customers, so having it in place reduces surprises.

How to implement clause 9.1.2

Build a repeatable analysis routine that combines sources and ends with a conclusion someone owns. The routine should be light enough to repeat, because an analysis done only once cannot show a trend.

1. List the inputs: verification results, internal and external audit findings, complaints, inspection comments and corrective-action outcomes.
2. Set a fixed rhythm for the analysis and name the food safety team member who prepares it.
3. Check comparability before concluding anything, looking at coverage, volumes, product mix and any change in recording method.
4. Look for trends that suggest more failures or unsafe product, and for evidence that earlier corrective actions actually worked.
5. State limitations openly, such as missing records or reduced sampling, and say what further evidence would help.
6. Write each conclusion with its evidence, its implication and the decision proposed, and pass the audit-priority information to the audit planner.
7. Report to top management, and keep the record of what was decided so the next analysis can test it.

Illustrative food-manufacturing example

Illustrative catering example

A caterer compares site verification results with changes in service volume and staffing. One location's apparently improved result coincides with reduced observation coverage. The team identifies that limitation and obtains further evidence before claiming improvement.

The analysis also identifies a reliable practice at another location that may merit consideration elsewhere. Transfer requires local evaluation rather than assuming every site operates identically.

Evidence and common mistakes