Verification is the set of activities, other than monitoring, that determine whether the HACCP plan is valid and whether the system is actually operating according to the plan. HACCP Principle 6 covers validation, calibration of monitoring instruments, review of monitoring and corrective-action records, targeted testing, and periodic reassessment of the whole plan.

Monitoring proves the work happened; verification proves the monitoring is honest and the plan still holds. It is the principle that checks the checkers, and it is where a plan that looks perfect on paper either earns trust or falls apart. This post separates verification from validation, walks the four main verification activities (calibration, record review, testing, and reassessment), and shows how they fit into an annual rhythm. It closes the loop opened by Principle 4, monitoring and Principle 5, corrective actions whose records are the raw material verification reviews.

What is verification in HACCP?

Verification is any activity, other than monitoring, that confirms the HACCP plan is valid and being followed. NACMCF defines it as "those activities, other than monitoring, that determine the validity of the HACCP plan and that the HACCP system is operating according to the plan." Two questions sit inside that definition: is the plan scientifically capable of controlling the hazards (validity), and is the plan actually being executed as written (conformance). Verification answers both, using evidence separate from the day-to-day monitoring records.

The reason verification is its own principle is that monitoring can look flawless and still be wrong. Records can be complete but filled in from memory, instruments can drift, a critical limit can quietly become inadequate after a formulation change. None of that shows up in the monitoring record itself; it takes an independent check to surface it. That independence is why verification tasks are often assigned to someone other than the person who does the monitoring, and why it connects directly to the audits behind HACCP certification.

What is the difference between verification and validation?

Validation proves the plan can work before you rely on it; verification confirms, on an ongoing basis, that it is working. Validation is a subset of verification focused on the science: it gathers evidence that the critical limits and control measures will actually control the hazards. Verification is the broader, continuing discipline that includes validation but also record review, calibration, testing, and reassessment. Getting the two straight is the single most common source of confusion in Principle 6.

Monitoring, validation, and verification compared Three different questions, three different jobs VERIFICATION ongoing: is the plan working & being followed? VALIDATION up front & after change: can this plan work? MONITORING in control right now?
Monitoring asks about this moment, validation asks whether the plan can work at all, and verification asks whether it is working over time. Verification is the outer envelope that contains the other two.

A concrete split: obtaining USDA Appendix A data to justify a cook's critical limit is validation. Watching the operator take the cook temperature correctly, reviewing the week's cook records for gaps, calibrating the probe, and running a finished-product test are verification. Validation is done up front and repeated after any change; verification runs continuously for as long as the plan is in use. Both draw on the critical limits set in Principle 3 but they ask different questions of them.

The practical failure this distinction prevents is the plant that validates once, files the study, and never checks again. A validated plan that nobody verifies drifts: instruments fall out of calibration, operators develop shortcuts, records get thinner, and the paper still says everything is fine. Verification is the recurring reality check that catches that drift. It is also why a plan validated years ago is not automatically trustworthy today, the validation proved the plan could work then, but only ongoing verification and reassessment show it still does.

What are the main verification activities?

The main verification activities are calibration of monitoring instruments, review of records, targeted product and environmental testing, and periodic reassessment of the plan. Together they check the instruments, the paper, the product, and the plan itself, four different angles on the same question of whether the system can be trusted.

The four main verification activities Four angles on one question: can the system be trusted? Verify the system Calibration keep monitoring instruments accurate against a standard Record review check monitoring & corrective records, ideally by another Testing targeted finished-product & environmental testing Reassessment revisit the whole plan yearly and on any change
Calibration checks the instruments, record review checks the paper, testing checks the product, and reassessment checks the plan. Skip any one and a whole class of failure goes unseen.

Calibration keeps monitoring instruments accurate against a reference standard, so the data underlying every CCP decision is trustworthy; the details live in calibration for food safety. Record review examines monitoring and corrective-action records for completeness and compliance, ideally by someone who did not create them, and USDA's rule expects pre-shipment review of these records. Testing uses targeted finished-product and environmental sampling to confirm the system is delivering safe product; environmental testing ties into your environmental monitoring program. Reassessment revisits the whole plan on a schedule and on any change, so the plan does not go stale.

These four are not equal in frequency. Record review happens continuously, often before every shipment. Calibration runs on a set schedule tied to each instrument. Testing is periodic and risk-based, heavier where the hazard is more severe or the process less proven. Reassessment is the least frequent, at least annual, but the broadest in scope. NACMCF also notes that verification can be performed by company staff, third-party experts, and regulatory agencies, and that whoever does it needs the technical expertise to judge whether the system is genuinely sound rather than just complete on paper.

How often should a HACCP plan be reassessed?

A HACCP plan should be reassessed at least annually and whenever a change could affect the hazard analysis or alter the plan. USDA's rule is explicit: every establishment reassesses the adequacy of its HACCP plan at least once a year, and additionally whenever changes occur that could affect the analysis or the plan, such as new ingredients, formulations, processing methods, equipment, packaging, distribution, or intended use. A trained individual performs the reassessment and modifies the plan immediately if it is found deficient.

Reassessment is the safeguard against the most dangerous kind of failure: a plan that was correct when written and slowly stopped matching the plant. A new supplier changes the incoming hazard picture from Principle 1; a faster line changes what a monitoring frequency actually covers; a reformulation can move a critical limit. None of these announce themselves, which is why the reassessment is scheduled rather than triggered only by problems. The steps below turn the requirement into a repeatable review.

  1. Confirm the process still matches the flow diagram. Walk the floor and check that steps, equipment, and product flow match the documented diagram the plan is built on.
  2. Revisit the hazard analysis. Check whether new ingredients, suppliers, or process changes have introduced or changed any significant hazard.
  3. Re-examine CCPs and critical limits. Confirm the CCPs are still the right steps and the critical limits still reflect current science and current product.
  4. Review the record trail. Look across monitoring and corrective-action records for gaps, recurring deviations, and near-misses that hint at a weak point.
  5. Check calibration and validation status. Confirm instruments are in calibration and that validation evidence still covers the process as it runs today.
  6. Document the outcome and update the plan. Record what was reviewed and any changes made; correct the plan immediately if a deficiency is found.

Facts worth pinning

Where verification lives or dies

Verification is only as good as the records it has to work with, and that is the catch. If monitoring and corrective-action records are thin, late, or scattered across binders and inboxes, record review becomes an archaeology project and reassessment turns into guesswork. The plants that pass verification cleanly are the ones whose records were trustworthy the day they were made, complete, timestamped, and searchable, so a reviewer can scan a month of cook logs in minutes and spot the one recurring deviation that matters.

That is exactly the payoff of the digitize-the-paper move Harmony runs for production and quality records (see how CLS did it): when monitoring, corrective actions, and calibration all live in one searchable place, verification and the annual reassessment become a query instead of a binder hunt, and audit readiness is a byproduct rather than a fire drill. It ties the whole seven-principle framework together, from the HACCP plan down to daily execution and back up to HACCP certification.

Verification is the principle that makes the other six honest. Hazard analysis, CCPs, critical limits, monitoring, and corrective actions can each be done well and still add up to a plan that quietly stops working, unless something independent keeps checking. That is the job Principle 6 does, and it is why food-safety systems that treat verification as a genuine discipline rather than a filing exercise are the ones that hold up under inspection. See how a connected operation keeps this evidence live on the features overview.