HACCP Monitoring & Records

HACCP Corrective Action Logs: How to Document Deviations

Documenting Corrective Actions When HACCP Controls Fail

Quick answer

Corrective actions are what happen when a critical limit is breached. They are HACCP Principle 5, and they are where many food businesses fall short - not because they do not take action, but because they do not document it properly. Under EC Regulation 852/2004, your HACCP plan must define what happens when monitoring indicates a CCP is not under control. The corrective action must address both the immediate food safety risk (what do you do with the affected food?) and the root cause (why did the deviation happen, and how do you prevent it recurring?). This article covers how to build a corrective action logging system that demonstrates control to EHOs and protects your business.

Every corrective action must address three things: the immediate food safety risk, the root cause, and prevention of recurrence.
Pre-define corrective actions for each CCP so staff can act immediately without waiting for manager input.
Trend analysis of corrective actions reveals systemic issues before they become serious.

Key takeaways

Every corrective action must address three things: the immediate food safety risk, the root cause, and prevention of recurrence.

Pre-define corrective actions for each CCP so staff can act immediately without waiting for manager input.

Trend analysis of corrective actions reveals systemic issues before they become serious.

Having documented corrective actions builds EHO confidence - perfect records with zero deviations look suspicious.

Close the loop on every corrective action by documenting the follow-up and resolution.

What a Corrective Action Log Must Capture

Every corrective action record should include seven elements: the date and time the deviation was detected, which CCP was affected, what the monitoring result was (e.g. "core cooking temp 68C" or "Fridge 3 reading 11C"), the critical limit that was breached, what immediate action was taken to address the food safety risk, what root cause investigation was carried out, and what preventive action was implemented to stop it happening again. The immediate action is about the food: was it discarded, recooked, moved to a compliant unit, or isolated for further assessment? The root cause investigation asks why: was the oven not calibrated? Did a staff member skip a step? Was the fridge overloaded? The preventive action addresses the system: recalibrate the oven, retrain the staff member, add a maximum-fill line to the fridge. Without all three elements, your corrective action is incomplete. An EHO reviewing your logs wants to see that you not only dealt with the immediate problem but also took steps to prevent recurrence.

HACCP Monitoring & Records

Monitoring records that write themselves

Every check in Paddl is timestamped and signed by the person who did it, with the reading, a photo where you ask for one, and the corrective action if it failed. The EHO audit pack for any date range is one click. Paddl is £69 per location per month with every feature and a 30-day free trial.

Start free trial HACCP software

Compare the best HACCP software Download the free temperature log sheets FoodDocs vs Paddl for HACCP

Pre-Defined Corrective Actions for Each CCP

Your HACCP plan should include pre-defined corrective actions for every CCP, so staff know exactly what to do without having to improvise during a busy service. For cooking CCP: if core temperature is below 75C, continue cooking until 75C is reached; if the food has been in the danger zone for more than 2 hours, discard it. For chilled storage CCP: if fridge temperature exceeds 8C, check food temperatures directly, move food to a compliant unit, investigate the cause (door left open, compressor failure, overloading), and call an engineer if needed. For hot holding CCP: if food drops below 63C, reheat to 75C within 2 hours or discard; do not simply turn up the heat and hope for the best. For cooling CCP: if food has not reached 8C within 90 minutes, transfer to a blast chiller or use ice baths to accelerate cooling; if food has been between 8C and 63C for more than 2 hours total, discard it. For delivery CCP: if chilled food arrives above 8C, reject the delivery and notify the supplier. These should be printed and posted near each CCP monitoring point.

Escalation and Trend Analysis

Not every corrective action is equal. A single fridge spike caused by a door being left open is different from a fridge that repeatedly exceeds 8C. Your corrective action system should include escalation triggers. For example: one deviation in a month - standard corrective action and logging. Two deviations on the same CCP in a month - supervisor review and documented root cause analysis. Three or more deviations on the same CCP in a month - management review, consider equipment replacement or process redesign, and retrain relevant staff. Trend analysis turns your corrective action logs from a reactive record into a proactive tool. Review your logs monthly (or at least quarterly) to spot patterns. Are most cooking deviations happening on the same section? That might indicate an equipment problem or a training gap. Are fridge deviations clustering at the same time of day? That might indicate overloading during prep or a delivery schedule issue. Document your trend reviews as part of your HACCP verification activities.

Common Documentation Failures

The most common failure is having no corrective action records at all, despite having occasional out-of-range monitoring results. If your temperature logs show nothing but perfect readings for six months, an experienced EHO will be sceptical. Real kitchens have occasional deviations, and documented corrective actions actually build confidence in your system. The second most common failure is recording the action but not the root cause or prevention. "Discarded food" is an immediate action, not a complete corrective action. What caused it? What did you change? The third failure is not closing the loop. If you identified that a fridge needed repair and noted "engineer called," there should be a follow-up record showing the engineer visited, what they found, and that the fridge was verified as working correctly afterwards. Keep corrective action logs together with or cross-referenced to your monitoring records so the full picture is available in one place.

What to do next

Write pre-defined corrective actions for each CCP

For every CCP in your HACCP plan, define the exact steps staff should take when a critical limit is breached. Print these and post them at each monitoring point.

Implement monthly trend reviews

At the end of each month, review all corrective action logs. Identify patterns by CCP, by time of day, and by staff member. Document findings and any system changes.

Create a corrective action form

Design a form with fields for: deviation details, immediate action, root cause, preventive action, follow-up required, and sign-off. Keep blank copies at each CCP station.

Common mistakes to avoid

Mistake

Recording only the immediate action without root cause analysis

Instead

Discarding food addresses the symptom, not the problem. Always document why the deviation occurred and what you changed to prevent it happening again.

Mistake

Treating corrective action logs as punishment rather than improvement

Instead

If staff fear blame, they will not report deviations. Foster a culture where documenting problems is valued because it makes the system stronger.

Frequently asked questions

How many corrective actions are too many?

There is no fixed threshold. What matters is the pattern. Occasional deviations with prompt corrective actions show a working system. Frequent deviations on the same CCP suggest a systemic problem that needs addressing at a deeper level - equipment, training, or process redesign.

Should I report corrective actions to my local authority?

Routine corrective actions (rejecting a delivery, discarding food that did not reach temperature) do not need to be reported. However, if a corrective action reveals a significant risk to public health (e.g. you discover you have served undercooked poultry to customers), you should contact your local authority Environmental Health team proactively.

Who should sign off on corrective actions?

The person who takes the immediate action should record it at the time. Root cause analysis and preventive actions should be reviewed and signed off by a manager or the HACCP team leader. For serious deviations, the business owner should be informed and their sign-off recorded.

HACCP Monitoring & Records