Deviations and corrective action

A deviation is simply a reading that falls outside the critical limit. The cook probes at 68 when the limit is 75. The fridge reads 9 when the limit is 5. In each case the control at that point has been lost, and the food may no longer be safe. It helps to hold a calm attitude to deviations. A deviation is not a disaster or a personal failure, it is a signal, and it is exactly what monitoring exists to catch. The whole system is built on the expectation that things sometimes go outside limits, which is why every critical control point has a corrective action ready in advance. Your job when you find a deviation is not to panic and not to hide it, but to recognise it for what it is and move to the planned response.

The flow in this lesson is the decision you run the instant you find a deviation. The first question is whether there is a planned corrective action that you are trained and able to carry out. If there is, you do it at once. For an undercooked joint that means putting it straight back on the heat and continuing to cook until the core passes the limit. If there is not, either because you are unsure what the right action is or because the decision is beyond your authority, you escalate, meaning you tell someone who can decide. And whichever path you take, the flow ends the same way: you record what happened. The single most important feature of this decision is speed. You take the planned action as soon as the deviation is found, because a problem caught and handled immediately can usually be contained, while the same problem left for later may spread to more food or reach a customer.

A deviation has three possible destinations, and knowing which applies is the skill. The first is to take the planned fix. If the HACCP plan has a corrective action for this situation and it is within your training, you carry it out at once, such as continuing to cook food that came up short. The second is to escalate. If you are unsure what to do, or the situation is beyond your authority, you tell a supervisor instead of guess, because a confident guess that turns out wrong is far more dangerous than admitting you need a decision from someone else. The third is to discard. Some food simply cannot be brought back to a safe state, and when that is the case it is thrown away, never served in the hope that it is probably fine. Serving on hope is how outbreaks happen. Which of the three applies depends on the situation and the plan, but the food handler always knows that guessing and serving-on-hope are never among the options.

The step that gets forgotten under pressure is the recording, and it matters as much as the action. Every deviation is written down: what went wrong, and what you did about it. The reason is straightforward but easy to underrate. A deviation that was handled perfectly but never recorded looks, to anyone checking later, exactly like a deviation that was ignored. The record is the only evidence that the problem was caught and dealt with properly. It protects the customer, because it forces the response to be real and complete, and it protects the business, because it is proof that the system worked. This connects directly to the next lesson on records and due diligence, but the habit to build now is simple: when you deal with a deviation, you are not finished until it is written down.

Three deviations, and for each one the same question the flow asks: is there a planned fix you are able to carry out. The first is a chicken at 68°C against a 75°C limit, with a planned action you are trained to do, so it stays with you and you keep cooking. The second is a warm delivery that nothing in the plan covers, so it goes to someone with the authority to decide. The third is the one that catches people out. A planned action does exist for a delayed cool, which makes it look like a yes, but you cannot tell how long the batch was out and you are not sure the action applies. Carrying it out anyway would be a guess, and guessing is never the right move, so the honest answer is no and it goes up. Notice where all three finish. Two left your hands and one did not, and every one of them ended at the same place, which is the record. An unrecorded deviation looks exactly like a deviation that was ignored.

Look back at the three cases you just routed. The first stayed with you, because the plan had an action you are trained to carry out. The second went up, because nothing in the plan covered it. The third went up as well, and that is the one worth sitting with, because a planned action did exist and what you could not tell was whether it applied. Carrying it out anyway would have been a guess, and guessing is never the right move. Now look at the right hand side of all three rows. Whichever way the food went, the deviation ended at the record. That is the step people forget under pressure, and it is the one that decides whether anybody can later show the problem was caught and handled. An unrecorded deviation looks exactly like a deviation that was ignored.

The scenario is deliberately an uncertain one, because uncertainty is where handlers most often go wrong. A chest freezer is too warm, you do not know for how long or whether the food is still safe, and there is no action you are trained to take. The right move is to escalate to a supervisor straight away and record what you found. The two wrong answers are the two classic failures. Deciding for yourself that it is probably fine is the guess the whole system exists to prevent, made worse here because you genuinely do not have the information to judge. Moving the food quietly and saying nothing is worse still, because hiding a food safety problem removes any chance for someone with authority to act, and concealment is one of the most serious things a food handler can do. When you are unsure and it is beyond you, escalation is not weakness, it is the correct, planned response.

The lesson in five lines. A deviation is a reading that falls outside the critical limit. Take the planned corrective action as soon as the deviation is found. Escalate when you are unsure or the issue is beyond your authority. Discard food that cannot be made safe, and never serve on hope. And record the deviation and the action taken, every single time, because an unrecorded deviation cannot be shown to have been handled at all.

This is the second of six lessons in Level 3, and every lesson is free to watch for as long as you need. When you are ready, the quiz proves what you know and earns a certificate recognised by TrustBite, an independent food safety recognition body. One payment covers the quiz and certificate for all three levels, so whichever level you buy first, the other two are included at no extra cost, and each certificate is valid for three years with renewal at 5 euros. No registration is needed to keep learning, and you only pay when you decide you are ready to be tested. If you are training a team, group options are available for both hospitality and production sites.

You now know what to do the moment a monitoring reading comes back out of limit. Recognise the deviation, take the planned fix if you can, escalate if you are unsure or it is beyond you, discard anything that cannot be made safe, and record all of it. You will have noticed how often recording came up in this lesson, at the end of every path. That is not an accident, and it leads straight into the next lesson, which is entirely about records: what they prove, why a missing one is treated as a control that never happened, and what due diligence really means. Every lesson stays free and you can rewatch any of them. When you are ready, the quiz earns a certificate recognised by TrustBite, and one payment covers all three levels.