HACCP verification activities: what a restaurant checks, how often and what to write down
HACCP verification activities are the checks you run to see that your own food safety system works. Verification is the step where you check that your own food safety system is working. Monitoring is the cook taking a temperature; verification is the manager asking whether the logs are filled in, the thermometers are right and the plan still matches the menu. In a restaurant that means reading logs weekly, testing thermometers monthly and reviewing the plan at least once a year.
This page is for the owner or kitchen manager who has a plan and logs and wants to know what "verification" means on the shop floor. If you do not have the plan and logs yet, see your plan, built from your menu. No card. If you do, read on for the schedule.
Verification, monitoring and validation: the difference
These three words get mixed up, and exams like to test them.
- Monitoring is the routine check at a control point: a cook probes the chicken, a closer logs the walk-in. Done by the person doing the work, every shift.
- Verification is a second look at the system: did the checks happen, were they right, do the corrective actions work? Done by a manager or someone outside the line.
- Validation is proof that a limit works at all: that cooking to 165°F really makes the food safe. For ordinary Food Code limits the validation is already done by the FDA, so a restaurant mostly cites it [1]. If you invent your own limit, for example for a long cure or a custom smoking time, you need evidence that it works.
Verification is the sixth of the seven HACCP principles in the standard Codex and NACMCF description [2]. The other principles are in how to write a HACCP plan for a restaurant.
HACCP verification activities: the five kinds
| Activity | What it is | Restaurant example | Record |
|---|---|---|---|
| Calibration | Checking measuring tools against a known standard | Probe thermometer in ice water reads 32°F | Calibration log |
| Record review | A manager reads and signs the logs | Friday: the week's cooler, cooling and receiving logs | Initial and date on each sheet |
| Direct observation | Watching a person do the check | Standing with a new cook while they cool a pot of beans | A short note: who, when, result |
| Product or surface checks | Testing the result, not just the step | A sanitizer test strip on a wiped table; a food probe on a plated item | Sanitizer log |
| Plan review | Rereading the plan against the real kitchen | New menu, new oven, a failed inspection item | Dated review note on the plan |
A schedule of HACCP verification activities for a restaurant
Every day
- The shift lead looks over the day's logs before leaving: blanks, round numbers like "40" in every box, readings above the limit with no note.
- One direct observation of a control point, rotating: cooling on Monday, receiving on Tuesday, hot holding on Wednesday.
Every week
- The manager reads all logs for the week and signs. Look for patterns (the same unit drifting up, the same person skipping the same log) not just single errors.
- Check that corrective actions were written when a limit was missed, and that the action matches the plan.
- Walk the line with the plan page in hand and check one control point end to end.
Every month
- Test every probe thermometer in ice water and record it; replace or recalibrate any that is off by more than 2°F. The Food Code asks for food thermometers accurate to within 2°F [3].
- Check the dish machine's final rinse and the sanitizer strips against the label.
- Check the pest control service record. See the pest control log.
At least once a year, and when things change
- Reread the whole plan against the current menu, equipment, suppliers and staff, and write the date and what changed.
- Retrain staff, and record who attended.
- Review the year's corrective actions: which control point failed most, and why?
The NACMCF guidelines say a plan should be reassessed when something changes and at least once a year [2]. The HACCP audit checklist gives a longer list for the annual review.
What a good verification note looks like
A verifier's note should say what was checked, what was found and what happened. Three examples:
- "Fri 11/13. Read the week's walk-in and cooling logs. Walk-in at 40 to 41°F all week. Tuesday cooling log has no 2-hour reading for the chili. Spoke to Dana; reading was taken but not written. Added a prompt to the sheet. M.K."
- "Mon 11/16. Tested 4 probes in ice water: 32, 32, 34, 32. Probe 3 is out by 2°F; recalibrated and retested, 32°F. M.K."
- "Wed 11/18. Watched Sam receive the fish order: probed two fish, 38°F and 39°F, logged both. Good. M.K."
Notes this short take less than five minutes and are what an inspector wants to see: someone looked, and acted.
What to do when verification finds a problem
The same loop applies to special processes. A sous vide plan, a chicken plan or a ground beef plan each have limits that verification should test: probe the thickest part, check the cook time, and read the cooling log.
- Fix the product first. If a log shows a unit was above 41°F for hours, the food in it may have to go. See what to do when a unit reads above 41°F.
- Find the cause. A skipped log is a training problem; a drifting cooler is a repair problem; a wrong limit is a plan problem.
- Fix the cause. Retrain, repair, or rewrite the step.
- Write it down. Date, finding, action, who.
- Check again. Verify the fix a week later.
Verification, inspections and audits
A health inspection is not your verification; it is an outside check on the result. The best use of your own verification is to find problems before the inspector does. Many violations cited in inspections, such as missing logs, a thermometer off the mark and no sanitizer test strips, are exactly what weekly and monthly checks catch. See the most cited restaurant violations. A third-party audit, which a large buyer may ask for, is a formal outside verification; most restaurants do not need one. For how long to keep these records see HACCP record keeping.
A one-page weekly sign-off sheet
You do not need software to verify. One sheet, kept at the front of the log binder, is enough. Make a row per week with these columns:
| Week of | Logs read (temps, cooling, receiving, sanitizer) | Gaps found | Corrective actions seen | Action taken | Initials |
|---|---|---|---|---|---|
| Nov 9 | All four | Cooling: 2 missing readings | 1 (cooler at 43°F, food moved) | Retrained closer; added a clock to the cooling sheet | M.K. |
| Nov 16 | All four | None | 0 | None. Probes tested: all 32°F | M.K. |
The two rows above are an example of the layout, not real data. A sheet like this shows an inspector that a person looked at the records every week, which is the point of verification. It also gives you a place to spot a trend: if "gaps found" is the same each week, the fix is not working.
Who does what in a small kitchen
- Line cooks monitor: probe, read, write the number.
- The shift lead checks the day's sheets before close and does one direct observation.
- The manager or owner does the weekly record review, the monthly thermometer test and the yearly plan review.
- An outside person (a consultant, a peer owner, a food safety class trainer) can walk through once a year with fresh eyes. This is optional, but it is the best way to catch what your own staff no longer see.
If you are the owner and the manager and the cook, split the roles by time instead: monitor during service, verify at close or on a quiet morning, and never sign a sheet in the same minute you fill it.
Common mistakes
- Signing logs without reading them.
- Calibrating once, at purchase, and never again.
- No verification record, only monitoring logs, so nothing shows that anyone reviewed them.
- Reviewing the plan only when something goes wrong.
- The same person monitors and verifies their own work.
- Treating verification as punishment, so cooks hide mistakes. It works only if finding a problem gets a fix, not a scolding.
Questions
What are HACCP verification activities?
Checks that your food safety system works: calibrating thermometers, reviewing records, watching staff do their checks, testing results and reviewing the plan.
What is the difference between verification and validation?
Validation shows a limit can control a hazard; verification shows you are following the plan and it is working in your kitchen.
How often should I verify?
Daily glance at logs, a weekly record review, monthly thermometer testing and at least an annual plan review, plus a review after any change.
Who should do it?
Someone other than the person who did the check: a manager, owner or trained lead.
Do I need a record of verification?
Yes. A signature and date on the logs, a calibration log and a dated plan review are the usual evidence.
Is verification required in a restaurant?
If your jurisdiction requires a written HACCP plan for a process, verification is part of it. For other restaurants it is good practice and part of active managerial control. Ask your health department.
If you want the plan, logs and a review date set up for your menu, see your plan.
Sources
- FDA Food Code 2022: cooking and holding limits. https://www.fda.gov/food/retail-food-protection/fda-food-code
- NACMCF, Hazard Analysis and Critical Control Point Principles and Application Guidelines (1997, revised). https://www.fsis.usda.gov/guidelines/1997-0006
- FDA Food Code 2022, 4-203.11: temperature measuring devices. https://www.fda.gov/food/retail-food-protection/fda-food-code
See also: HACCP monitoring procedures example.