HACCP Verification and Record Keeping for Restaurants

HACCP verification and record keeping are principles 6 and 7, and they are where many restaurant plans quietly fall apart. The plan says cooks probe chicken and record it. Verification asks whether they actually did, whether the thermometer was right, and whether the plan still matches the kitchen. Record keeping makes all of it visible to you and to the inspector. This guide explains what verification includes, what records to keep, how long to keep them, and a simple weekly routine that holds it together.

The definitions follow NACMCF's HACCP principles and application guidelines, and the restaurant rules come from the FDA Food Code 2022. Your state may differ. Any plan you build is a draft for your health department to review.

HACCP verification and record keeping: monitoring vs verification

These get confused all the time.

| | Monitoring (principle 4) | Verification (principle 6) | |---|---|---| | Question | Is this CCP in control right now? | Is the plan working and being followed? | | Who | The person at the station | A manager or someone not doing the monitoring | | When | Every batch, every 2 hours, etc. | Daily, weekly, monthly, yearly | | Example | Cook probes chicken: 168°F | Manager reviews the cooking log, checks the thermometer, watches a cook probe | | Output | Monitoring log entry | Signed log review, calibration log, reassessment record |

Monitoring without verification is common. Logs get filled in, but nobody looks at them until the inspector does.

What HACCP verification includes

NACMCF describes verification as activities, other than monitoring, that confirm the validity of the plan and that the system is operating according to the plan. In a restaurant this usually means five things.

1. Reviewing monitoring records

A manager reads the logs and signs them. The review checks:

• every required entry is there
• readings are within limits, or there is a corrective action
• entries look real, not copied
• the right person signed

A daily review catches problems while they can be fixed. A weekly review is the minimum many plans use.

2. Reviewing corrective action records

Every out-of-limit reading on a monitoring log should match an entry in the corrective action log. The reviewer checks that the action was appropriate and that the cause was addressed. Repeated corrective actions for the same problem are a signal to change something. See HACCP corrective actions examples.

3. Calibrating instruments

Thermometers, pH meters and other instruments used for monitoring are checked against a known reference on a schedule. See the thermometer calibration log.

4. Direct observation

A manager watches a cook take a temperature, check sanitizer, or label food. This catches technique problems that logs cannot show, such as probing the edge of a pan instead of the center.

5. Reassessing the plan

The plan is reviewed:

• when the menu changes
• when equipment changes, such as a new blast chiller or a different oven
• when the process changes, such as switching from shallow pans to an ice bath for cooling
• when a new supplier or ingredient changes the hazards
• after a foodborne illness complaint or other incident
• on a regular schedule, at least once a year as common practice

Record each reassessment, even if nothing changes. "Reviewed 3/1, no changes needed" shows the review happened.

Validation: does the plan actually work?

Validation is the part of verification that checks whether the critical limits and controls will actually control the hazard. For most restaurant CCPs, the Food Code limits are the validation, because they are based on scientific review. For special processes, validation may need more:

• a cooling method run several times with temperatures recorded every 30 minutes, to show it meets the 2 and 6 hour limits with full batches
• sous vide times and temperatures supported by published tables or a process authority
• sushi rice acidification supported by pH testing of each batch and a recipe that has been tested
• curing processes supported by a process authority or published guidance

See HACCP plan for sushi rice, the sous vide HACCP plan and HACCP plan for cured and smoked foods.

HACCP record keeping: what to keep

| Record | What it shows | Typical retention | |---|---|---| | HACCP plan with hazard analysis | The plan exists and its basis | Current version always; old versions as long as related records | | Flow diagrams | The process steps | With the plan | | Monitoring logs (cooking, cooling, reheating, holding) | CCPs were checked | Per plan; often 6 to 12 months | | Corrective action log | Deviations were handled | Same as monitoring | | Calibration log | Instruments were accurate | Same as monitoring | | Verification records (log reviews, observations, reassessments) | The plan was checked | Same as monitoring | | Training records | Staff were trained | Employment plus a set period | | Validation records | Limits work | As long as the process is used | | Supplier records, shellstock tags | Source of food | Shellstock tags 90 days after container emptied | | Parasite destruction records | Fish for raw service was treated | 90 days after sale or service | | Variance approval | Permission for the process | As long as the variance is in effect |

How long to keep HACCP records

The Food Code sets specific periods for some records:

• Reduced oxygen packaging under 3-502.12: records kept at least 6 months.
• Shellstock tags under 3-203.12: kept 90 days from the date the container is emptied.
• Parasite destruction records under 3-402.12: kept 90 days beyond the time of service or sale.

For other HACCP records, your plan and health department set the period. Many restaurants keep records 6 to 12 months. A plan approved as part of a variance may specify a period. When in doubt, keep them longer.

Federal HACCP rules for processors are more specific. For example, USDA's meat and poultry HACCP rule in 9 CFR part 417 sets retention periods, and FDA's preventive controls rule in 21 CFR part 117 requires review of monitoring and corrective action records within 7 working days. These apply to processors, not restaurants, but they show how regulators think about records. See HACCP vs FSMA.

What makes a good record

• Written at the time. Not filled in at the end of the shift from memory.
• In ink or a secure digital system. Pencil can be changed.
• Legible.
• Complete. Date, time, reading, initials.
• Corrections are visible. Cross out with one line and initial; do not use correction fluid. Digital systems should keep an edit history.
• Signed off. The reviewer signs and dates.

Paper vs digital records

Both are acceptable to most health departments if they meet the points above.

Paper is cheap and simple. Organize by month in a binder, one section per log. Keep the current month at the station and older months in the office.

Digital systems can timestamp entries, prevent missing fields, alert managers when a reading is out of limit, and store records securely. Wireless probes remove handwriting entirely. Make sure records can be shown or printed for an inspector on request, and back them up.

A weekly verification routine

A simple routine for a small restaurant manager, about 30 to 45 minutes a week:

Daily (5 minutes):

• glance at today's cooking, cooling and holding logs
• check any out-of-limit readings have corrective actions
• initial the logs

Weekly (20 minutes):

• review the full week of logs and sign each page
• review the corrective action log for patterns
• check the calibration log is complete
• observe one cook taking a temperature
• note anything to follow up

Monthly (15 minutes):

• file the month's logs
• check training records for new staff
• note any menu, equipment or supplier changes

Yearly (1 to 2 hours):

• reassess the full plan
• update flow diagrams and hazard analysis if needed
• record the review

Questions a reviewer should ask

When you sit down with a week of logs, these questions turn a signature into a real review:

• Did every scheduled check happen? Count the entries. If the plan says hot holding is checked every 2 hours from 11 to 9, there should be six entries a day.
• Do the readings make sense? A walk-in at 36°F on a busy Friday afternoon is plausible. A walk-in at exactly 36°F every reading for a month is not.
• Did anything go out of limits? If so, is there a corrective action, and was it the right one?
• Is there a pattern? The same unit running warm on Mondays, cooling failing on nights when one cook is on, or reheating readings close to the limit.
• Are the right people signing? If one person signs every entry for every station, ask how.
• Has anything changed in the kitchen? New items, equipment or suppliers that the plan does not cover yet.

Write a short note of what you found, even "no issues." That note is the verification record.

What to do when a review finds a problem

Treat a verification finding the same way you treat a monitoring failure: decide what happens to any food affected, fix the cause, and record it.

Examples:

• Missing entries. Find out why. If no one knows whether the food was checked, treat it as out of control. Hot-held food that was never checked may need to be discarded. Then fix the cause: a timer, a reminder, a clearer assignment.
• Readings that look copied. Talk to the staff member privately, retrain, and watch the next few readings yourself.
• Thermometer out of calibration. Review readings since the last good check. If any may have been below the limit by the error amount, evaluate the food involved.
• A process that keeps failing. If cooling keeps missing the 2 hour mark, the method needs to change: smaller batches, shallower pans, an ice bath, or a blast chiller. Update the plan.

Every one of these should leave a written trail: what was found, what was done, who did it and when.

Records the inspector may ask for

Inspectors vary, but common requests during a routine inspection of a restaurant with a HACCP plan include the plan itself, the last few weeks of monitoring logs for the processes in the plan, the corrective action log, the calibration log and any variance letter. Keep these together and easy to reach. Being able to hand over a neat binder in a minute makes a better impression than searching the office.

Verification log layout

| Date | Activity | Records reviewed | Findings | Action | Reviewed by | |---|---|---|---|---|---| | Mon | Weekly log review | Cooking, cooling, holding, CA log | Cooling log missing 6 hr check Tue | Retrained night cook | JM | | Mon | Observation | Line cook probing chicken | Correct technique | None | JM | | 1st of month | Calibration review | Calibration log | Complete | None | JM |

Signs your records are not believable

Inspectors and auditors look for patterns that suggest records are not real:

• the same reading every time, such as 38°F every day for months
• perfect handwriting with the same pen for a whole week, suggesting entries were written at once
• entries for times when the restaurant was closed
• no corrective actions over a long period
• readings exactly at the limit, such as 165°F every time

If you see these in your own logs, talk to the staff involved. The goal is real readings, including the occasional bad one with a corrective action.

Verification and the health inspection

Inspectors often check:

• that the HACCP plan is on site
• that monitoring logs are complete and current
• that corrective actions are recorded
• that thermometers are accurate
• that staff can explain their part of the plan

A signed weekly review is strong evidence that the plan is working. See the health inspection food safety checklist.

Verification for variances and specialized processes

When a HACCP plan is required for a variance or a specialized process such as reduced oxygen packaging, the health department may set specific verification requirements: more frequent reviews, lab testing, or submission of records. Follow those exactly. See HACCP variance requirements and the reduced oxygen packaging HACCP plan.

Training records

Training is not one of the seven principles, but it supports all of them. Keep a simple record for each staff member:

| Name | Date | Topic | Trainer | Signature | |---|---|---|---|---|

Include initial training, refreshers, and training after a corrective action. See HACCP training for restaurant staff.

Common mistakes

• No one reviews logs until the inspector does.
• Reviewer signs without reading.
• No calibration log.
• Plan never updated after menu changes.
• Records thrown out too soon.
• Records stored where staff cannot find them during an inspection.
• Corrective actions on monitoring logs but no separate corrective action record showing cause and follow-up.

A worked example: one month of verification

Week 1: Manager reviews logs daily, notices the cooling log has no 6 hour checks on two nights. The night cook says the 6 hour mark falls after closing. Corrective action: move cooling of large batches to earlier in the day. Record it.

Week 2: Weekly review shows all cooling checks complete. Observation of the grill cook shows correct probing.

Week 3: Calibration log shows probe 2 drifted 3°F. It was adjusted. Manager reviews cooking logs since the last good check and notes that the recorded temperatures had at least 3°F of margin. No food action needed. Record it.

Week 4: New menu item, braised short rib. Manager updates the flow diagram and adds cooling and reheating CCPs for it. Records the reassessment.

That month produces a handful of short records, and each one makes the plan stronger.

Verification on a food truck or in catering

Mobile and off-site operations make verification harder, because the person in charge may be at an event while the logs sit in the truck. Keep logs on a clipboard that travels with the food, photograph each completed page at the end of the day, and review them the next morning. For catering, attach the event's cooking, transport and holding readings to the event sheet so every job has its own record. See the food truck HACCP plan and HACCP plan for catering.

Who should do verification

Ideally, someone other than the person doing the monitoring. In a small kitchen that might be the owner reviewing the chef's logs, or the chef reviewing the line cooks' logs. When one person does everything, such as on a food truck run by the owner, self review is still useful if it is done at a different time, for example every Sunday evening with a fresh look at the week. Write down who verifies in your plan.

Keeping verification realistic

The biggest risk with verification is that it becomes paperwork nobody reads. Keep it small and focused:

• review the logs that matter most: cooling, hot holding and cooking
• look for patterns, not just individual readings
• act on what you find, and record the action
• keep the review short enough that it happens every week

A 20 minute weekly review that always happens is worth more than a detailed monthly audit that gets skipped.

Record storage tips

• Use one binder per year with tabs for each log type, or one folder per month.
• Label everything with the month and year on the spine.
• Store old records in a dry place away from the kitchen, where they will not get wet or greasy.
• Scan paper records monthly if you have the time; it protects against loss.
• Keep the current plan in a sheet protector at the front of the binder, with the date of the last review.
• Tell staff where records are, so the person on shift can show them to an inspector even if the manager is out.

Build verification into your plan

The HACCP builder adds a verification section to every plan with log reviews, calibration and reassessment schedules, and creates the logs you need. See the HACCP plan template and a complete HACCP plan example. Try one process free or get every process in the Plan Pack. The plan is a draft for your health department to review.

Frequently asked questions

What is the difference between monitoring and verification?

Monitoring is the routine check at a CCP, such as a cook probing chicken. Verification is checking that monitoring happened, was done correctly, and that the plan works, such as a manager reviewing the cooking log and calibrating the thermometer.

How long should I keep HACCP records?

As long as your plan and regulator require. Food Code 3-502.12 sets at least 6 months for certain reduced oxygen packaging records. Shellstock tags are kept 90 days. Many restaurants keep HACCP records 6 to 12 months.

Can HACCP records be digital?

Generally yes, if they are accurate, complete, secure and available to the inspector on request. Check with your health department.

How often should a HACCP plan be reviewed?

Whenever the menu, equipment, process or supplier changes in a way that affects safety, after any food safety incident, and at least once a year as a common practice.