Validation and verification are two of the most consistently confused terms in food safety management. I've seen non-conformance reports from BRC audits that cite the wrong clause because the auditor mixed them up. I've seen HACCP teams describe their monthly temperature record review as validation. I've seen validation plans that are actually just lists of verification activities. The confusion is widespread, it persists even among experienced practitioners, and it has real consequences for how HACCP systems are built and maintained.
The distinction matters because the two activities serve different purposes, happen at different stages, have different triggers, and require different types of evidence. If you're doing verification when you should be validating, your HACCP plan may be based on unproven assumptions. If you're doing validation when you should be verifying, you're creating unnecessary work and may be missing the ongoing evidence you actually need.
The Precise Definitions
The Codex Alimentarius CXC 1-1969 definition of validation is: obtaining evidence that a control measure or combination of control measures, if properly implemented, is capable of controlling a hazard to a specified outcome. Validation answers the question: will this work?
The Codex definition of verification under Principle 6 is: the application of methods, procedures, tests and other evaluations, in addition to monitoring, to determine whether a control measure is or has been operating as intended. Verification answers the question: is it working?
The critical difference is tense and orientation. Validation is prospective — you validate before you rely on the control measure, and when you validate you're proving capability. Verification is retrospective — you verify against an established system to confirm it's functioning as designed.
Why This Confusion Persists
There are a few reasons this distinction is consistently confused in practice. First, validation was a relatively informal concept in early HACCP guidance — it was implicitly included in establishing critical limits, not called out as a distinct activity. The 2020 revision of CXC 1-1969 significantly strengthened validation as an explicit, separate requirement, which has left many HACCP systems built under older guidance with validation gaps they don't recognise as gaps.
Second, the two activities can look superficially similar — both involve reviewing data and confirming that something is under control. The difference is in what data you're reviewing, what question you're answering, and what you do with the result. Reviewing CCP monitoring records to check they're being completed correctly is verification. Reviewing scientific literature to confirm your critical limit will kill the target pathogen is validation.
Third, BRC Issue 9 addresses them in separate clauses — clause 2.11 for validation and clause 2.12 for verification — but many sites treat them as a single activity, which means one or both are typically incomplete.
Examples Across Different Control Types
Thermal processing CCP — cooking temperature. You have a cooking CCP with a critical limit of 75°C core temperature for 30 seconds. Validation is the evidence that 75°C for 30 seconds, when achieved uniformly throughout the product, will reduce Salmonella to a level that doesn't present a consumer safety risk. This evidence might come from published D and z values for Salmonella in the product matrix, from regulatory guidance (FSA guidance on cooking temperatures, for example), or from thermal challenge testing. You validate this once — when you set up the CCP — and re-validate if the product formulation, product size, cooking equipment, or cook cycle changes in a way that could affect heat distribution. Verification is your ongoing review of cooking temperature records, your calibration of the temperature probe used for monitoring, your periodic internal audits of the cooking procedure, and your annual HACCP review that confirms the critical limit is still appropriate. Verification happens continuously; validation happened when you designed the CCP.
Metal detection CCP. Your critical limit is passage of a 2.0mm ferrous test piece at the start and end of each production run and every 30 minutes during production. Validation is the evidence that a metal detector set to detect 2.0mm ferrous (and equivalent sensitivity for non-ferrous and stainless steel) will reliably detect metal fragments of that size or larger in your specific product under your specific operating conditions (product density, moisture content, temperature, belt speed). This requires sensitivity testing using the detector in your specific product and operating conditions — it's not enough to rely on the manufacturer's specification for a detector in air. Verification is your completed test piece passage records, your calibration records, your review of rejected product logs, and your periodic audit that the test piece frequency and reject confirmation procedures are being followed.
Allergen changeover PRP/OPRP. Your allergen changeover procedure is an enhanced PRP controlling allergen cross-contact between products containing and not containing peanuts. Validation for this control is evidence that the changeover procedure — the specific cleaning method, the rinse-down sequence, the swab testing protocol — will reduce peanut protein below your action level. This might be demonstrated through ELISA testing following a simulated changeover, or through ATP swab data combined with protein test results showing progressive reduction through the cleaning steps. Verification is your completed changeover checklist records, your allergen swab results following changeovers, and your trend review confirming the procedure is consistently effective. If your testing finds residual peanut protein above the action level following a procedure-compliant changeover, that's a validation failure — the procedure doesn't work — not a verification failure.
Cleaning PRP. Cleaning is a PRP — it is never a CCP or OPRP in the CCP sense. Validation for a cleaning PRP is evidence that the cleaning procedure (chemical concentration, temperature, contact time, mechanical action) will achieve the specified hygiene standard on the food contact surfaces in question. This might be demonstrated through ATP monitoring data following a validated clean, microbiological surface swab results, or the use of cleaning chemicals validated by the supplier for the specific application. Verification is your routine ATP monitoring, your microbiological surface sampling programme, and your documented visual inspections. The key point: if your ATP swabs consistently fail on a particular surface, that's a verification-detected failure of your cleaning PRP, and your corrective action should investigate whether the PRP itself needs to be re-validated (different chemical, different concentration, different procedure) or whether an implementation failure is occurring (incorrect dilution, wrong procedure being followed).
When Validation Must Be Repeated
Validation is not a one-time exercise. BRC Issue 9 clause 2.11 requires that validation is repeated whenever there is a change that could affect the ability of the control measure to control the hazard. Common triggers include: change in product formulation (different composition affects heat distribution, water activity, or allergen risk profile); change in product size or geometry (affects thermal processing); new production equipment (different metal detector model, different oven, different packaging format); change in raw material supplier or ingredient specification; change in process parameters (different cook cycle, different cleaning chemical); new product type being produced on existing equipment (new allergen risk or different contamination profile); and emerging hazard intelligence suggesting the current critical limit may not be adequate.
The 2020 Codex revision explicitly requires validation to be reviewed when any of these changes occur. Sites that treat validation as a one-time activity at HACCP plan setup frequently fail clause 2.11 when process changes haven't been followed by validation review.
What Verification Records Should Look Like
A verification programme is a planned schedule of activities that confirm the HACCP system is operating as intended. Good verification records include: a documented verification schedule identifying all activities, their frequency, responsible person, and evidence required; completed records for each activity (calibration certificates, audit reports, sampling results, record review sign-offs); evidence that the results have been reviewed (not just filed); and records of any follow-up actions where verification activities identify deviations.
The verification schedule should cover as a minimum: review of CCP monitoring records (is every record complete, accurate, and reviewed?); review of corrective action records; calibration records for monitoring equipment; periodic internal audits of CCP implementation; microbiological or chemical verification testing; and the annual HACCP plan review under clause 2.14.
Common BRC Audit Findings
Against clause 2.11 (validation): critical limits without scientific basis — "we cook to 75°C""with no evidence for why 75°C is sufficient for your specific product and pathogen; metal detector sensitivity settings validated in air not in product; allergen changeover procedures with no verification that they actually remove allergen to the required level; failure to re-validate following a process or equipment change.
Against clause 2.12 (verification): monitoring records reviewed but sign-off dates don't match record dates; verification schedule not being followed at the specified frequency; verification activities that detect problems but no follow-up actions recorded; calibration of monitoring equipment overdue or using uncertified reference standards.
Validation proves your controls are capable. Verification proves they're being applied. Both are essential — but they're answering entirely different questions, and conflating them is how gaps get missed.
SafetyCore separates validation and verification clearly — your CCP records capture validation evidence at setup, while annual and triggered reviews give you the structured verification framework that auditors expect to see under BRC Issue 9 clauses 2.11 and 2.12.
Start Free Trial