ISO 22000 verification: check that PRPs and hazard controls work
ISO 22000 clause 8.8 addresses verification related to PRPs and the hazard control plan. Verification checks that the arrangements are implemented and effective, that relevant hazard levels are acceptable and that the information supporting hazard analysis remains current. The food safety team analyses the results so that they inform evaluation of the wider FSMS.
What clause 8.8 requires in practice
Clause 8.8 asks the organisation to check that its prerequisite programmes and hazard control plan actually work. It has two parts. Clause 8.8.1 requires planned verification activities with a defined purpose, methods, frequency and responsibilities, confirming that PRPs and the plan are implemented and effective, that hazard levels are within the acceptable levels, that inputs to the hazard analysis are kept up to date, and that other actions the organisation decided on are carried out. The monitor of an activity does not verify it, results are kept and communicated, and adverse samples trigger handling of affected lots as potentially unsafe. Clause 8.8.2 asks the food safety team to analyse the results and feed that analysis into performance evaluation of the system.
Define what each verification activity will establish
Plan the purpose, method, frequency and responsibilities. Begin with the question the activity needs to answer. A review of records, observation of work and suitable testing can provide different evidence. Choose methods capable of supporting the intended conclusion rather than selecting checks simply because they are easy to complete.
The coverage includes PRP and hazard-control implementation and effectiveness, acceptable hazard levels, updated hazard-analysis inputs and other actions determined by the organisation. It should reflect the real products, processes and conditions. Repeatedly checking one convenient area leaves uncertainty elsewhere.
Distinguish validation, monitoring and verification
Validation establishes that a control or combination is capable of achieving the intended result. Monitoring provides information during operation to support timely action. Verification checks whether the specified arrangements are fulfilled and effective. Their evidence can interact, but their purposes remain distinct.
For example, checking that a monitoring record contains an entry can contribute to verification of implementation. It does not by itself establish that the chosen control is capable of achieving the required hazard reduction. Similarly, validation evidence does not show whether staff applied the control correctly during a particular run.
Assign appropriate responsibility
The person responsible for monitoring an activity must not carry out verification of that same activity. Organise responsibilities so that the verification provides a separate check. This requirement concerns the activity; it does not automatically demand that every verification task be outsourced.
Those conducting and evaluating verification need competence appropriate to the method and evidence. A general supervisor may be able to review some implementation evidence but require specialist support for a technical interpretation. Define how uncertain or adverse findings reach authorised decision-makers.
Retain, communicate and act on results
Keep documented verification results and communicate them. Where verification uses end-product or direct-process samples and results show a hazard level outside the identified acceptable level, the standard requires affected lots to be handled as potentially unsafe and corrective action to be applied. A result should not remain in a laboratory inbox while product decisions continue on old assumptions.
The food safety team analyses verification results under 8.8.2 and uses that analysis as an input to performance evaluation. Trends can reveal weaknesses that isolated checks obscure. Consider whether findings affect the hazard analysis, PRPs, control plan or wider resources and responsibilities.
Why clause 8.8 matters to the business
Verification is the system checking itself. Without it, an organisation relies on the same people who operate controls to tell it that the controls are fine. A genuine second look finds weak methods, missing coverage and drifting practice before they become incidents, and it supplies the evidence customers and certifiers want when they ask how you know the system works. The analysis step turns scattered checks into insight for management. Done well, verification also reduces the expense of finding problems in the market, where they cost far more than they do in your own plant.
How to implement clause 8.8
Approach verification as a planned programme of questions, each with a method and an owner. Remember that the programme itself needs review, so ask each year whether the checks still address the weaknesses that complaints, audits and incidents have exposed.
- List what needs to be verified: each PRP, each CCP and OPRP, the hazard levels, the currency of analysis inputs and any other determined actions.
- For each, state the question, choose a method such as observation, record review or testing, and set a frequency that fits the risk.
- Assign competent people who are not responsible for monitoring the same activity.
- Define how results are communicated and how an adverse sample result leads to the handling of affected lots and to corrective action.
- Carry out the activities, recording what was examined and what was found.
- Analyse the results across time, products and sites, and report the conclusions to performance evaluation and to the people who can act.
- Adjust the programme when it fails to reveal known weaknesses.
Illustrative manufacturing example: records completed, method inconsistent
A hypothetical manufacturer reviews a series of completed monitoring records and initially sees no omissions. A separate verification observation finds that staff apply an observation criterion differently between shifts. The team reviews the instruction and competence arrangements and assesses the implications of the inconsistency.
The response is not simply to demand more signatures. The organisation needs a dependable method and evidence that it is used consistently. The example does not decide product safety; that assessment belongs to competent authorised personnel using the relevant operational controls.
Illustrative catering example: a PRP across several locations
A hypothetical caterer verifies a cleaning programme at workplace service points. It checks implementation at different locations and times, then compares findings with the programme's intended conditions. One location repeatedly reports an access problem that prevents the method being followed.
The food safety team analyses the pattern and escalates the resource or layout issue. Repeating the instruction would not resolve the physical obstacle. After suitable changes, further verification examines whether the programme now operates effectively at that location.
What an auditor may examine
An auditor may ask why a method and frequency were selected, who performs monitoring and verification, and what happened after an adverse result. They may follow a verification trend into performance evaluation and management review. The evidence needs to support both the individual check and the learning process.
Common weaknesses include self-verification of the same monitored activity, records checked only for signatures, uncommunicated results and tests that do not address the intended question. Another is describing every favourable sample as proof that the entire system is effective.
Explore each numbered part
8.8.1 · verify that PRPs and hazard controls work
Verification checks implementation and effectiveness after controls are in place. This guide explains what verification must confirm, how to plan it, the separation from monitoring responsibility and the response to adverse sample results. Manufacturing and catering examples show how records, observations and suitable testing can answer different questions without being confused with validation.
8.8.2 · turn verification results into a system judgment
Individual verification results need interpretation across time, products and processes. This guide explains the food safety team's responsibility to analyse them for FSMS performance evaluation. Food-manufacturing and catering examples show how repeated small findings or apparently improving results can be misleading unless the team considers their context, coverage and consequences.
Common nonconformities with clause 8.8
Verification findings in food businesses tend to cluster around a few recurring weaknesses.
- The same person monitors and verifies an activity, so the check provides no independent view.
- Verification looks only at whether records are present and signed, and never at whether the control works in practice.
- Sample testing is carried out, but nobody has decided in advance how adverse results will be linked to product decisions.
- Results sit with the laboratory or quality department and are never communicated to the people who run the process.
- The programme never changes, even after complaints or incidents reveal problems it did not detect.
Frequently asked questions
Is verification identical to internal audit?
No. Operational verification concerns PRPs and the hazard control plan. Internal audit examines conformity and effective implementation of the FSMS against its criteria. Their results can inform one another.
Does every verification activity require laboratory testing?
No. Select suitable methods for the purpose. Testing may be important for particular questions, while other activities use observation, record review or different evidence.
Can the monitor also verify the same activity?
No. Clause 8.8.1 requires that verification of an activity is not carried out by the person responsible for its monitoring. Plan responsibilities accordingly.
Make verification findings lead to useful action
Sterling can support verification planning, documentation and connections with review and updating. Agreed Effivity ISO & GRC automation software can help organise evidence and actions alongside employee learning. Discuss your verification gaps. Review ISO 22000 Food Safety Awareness for the system context and, for relevant manufacturing teams, Prerequisite Programmes for Food Safety.
Revisit hazard control, return to clause 8 or the hub; continue to nonconforming processes and products.