A corrective action is the predefined response taken when monitoring shows a critical limit has been breached at a critical control point. HACCP Principle 5 requires that response to do four things: identify and eliminate the cause, bring the CCP back under control, determine what happens to the affected product, and prevent the deviation from recurring, all documented.

A deviation is not an emergency if you planned for it, and that is the whole idea of Principle 5. The moment a cook comes in low or a metal detector is found not rejecting, two clocks start: one on the product already made, and one on the process that failed. This post covers what a deviation is, the four requirements every corrective action must meet, how affected product is controlled and dispositioned, and why documentation is what turns a one-off save into a permanent fix. It picks up where Principle 4, monitoring leaves off, because monitoring is what detects the deviation in the first place.

What is a corrective action in HACCP?

A corrective action is the set of steps taken when a critical limit is not met at a CCP, addressing both the product and the process. A deviation is any failure to meet a critical limit, and the corrective action is the planned answer to it. The distinction that trips people up: a corrective action is not just "re-cook it" or "throw it away." It has two halves, one aimed at the affected product and one aimed at the underlying cause, and a response that fixes only one half is incomplete.

Good HACCP plans write corrective actions in advance for the deviations they can foresee, so the floor knows exactly what to do without waiting for a decision. NACMCF and USDA both anticipate that some deviations will not be covered by a preplanned action, and they set a separate, more involved path for those. Corrective actions are close cousins of the broader corrective and preventive action (CAPA) discipline used across quality systems, but in HACCP they carry a specific food-safety and product-disposition weight.

It helps to picture two clocks starting the instant a deviation is found. The first runs on the product already made while the CCP was out of control; every minute it keeps moving toward shipping, the window to hold it narrows. The second runs on the process itself, which cannot make good product again until the cause is found and control is restored. Principle 5 is the discipline of running both clocks at once instead of fixing the line while an unsafe lot quietly ships, or holding product while the same failure keeps producing more of it.

What are the four requirements of a corrective action?

USDA's HACCP rule requires every corrective action to accomplish four things: identify and eliminate the cause of the deviation, bring the CCP back under control after the action, establish measures to prevent recurrence, and ensure no product that is injurious to health or otherwise adulterated enters commerce. All four, every time, or the corrective action is incomplete.

The four requirements of a corrective action Every corrective action does four things 1 · Cause identify and eliminate the cause of the deviation 2 · Control bring the CCP back under control after the action 3 · Prevent establish measures to prevent recurrence 4 · Product no adulterated product enters commerce The first three fix the process; the fourth protects the consumer, all from 9 CFR 417.3
Three of the four requirements are about the process; the fourth, in red, is about the product already made. Miss the product half and you have fixed the line while an unsafe lot ships.

The first three requirements are about the process: find why the cook ran low, get it back over the limit, and change something so it does not drift low again. The fourth is about the product already made while the CCP was out of control, and it is the one that protects the consumer. A corrective action that retunes the cooker but ignores the two pallets made during the deviation has done half the job. The cause step often pulls in a full root cause analysis when the reason is not obvious, because "prevent recurrence" is impossible until you actually know why it happened.

How do you handle the affected product?

You handle affected product by first segregating and holding it, then evaluating it, then dispositioning it based on that evaluation, keeping any adulterated product out of commerce. The product half of a corrective action is a decision tree, not a single answer, and the outcome depends entirely on what the evaluation finds.

Affected-product disposition decision tree What happens to the product made during a deviation deviation detected at the CCP segregate & HOLD all affected product evaluate for safety (qualified person) RELEASE evidence shows safe REWORK re-cook / reprocess DIVERT non-food / feed use DESTROY adulterated Every branch ends the same way: document the evaluation, the decision, and who made it
Hold first, evaluate second, disposition third. The evaluation must be done by someone qualified to judge safety, and release is only justified when there is real evidence the product is not adulterated.

The order is not negotiable: hold before you evaluate, because product that keeps moving cannot be recalled from the truck. Then a qualified person evaluates whether the deviation actually made the product unsafe. Depending on the finding, the product is released (evidence shows it is safe), reworked (re-cooked or reprocessed to meet the limit), diverted to a use where the hazard does not apply, or destroyed if it is adulterated and cannot be recovered. If the deviation is one your plan never anticipated, USDA's rule adds steps: hold the product, review it for acceptability, keep adulterated product out of commerce, and have a trained individual reassess whether the plan needs to change.

One worked example makes the tree concrete. Say a cook step's chart recorder shows the last two batches ran three degrees below the critical limit. The affected product is everything cooked since the previous verified-good reading, so it is segregated and held on a dedicated hold rack, not left mixed with released product. A qualified person reviews the recorder trace and the validation study and finds the delivered lethality was insufficient. Because the batches can be re-cooked to the validated limit without quality loss, the disposition is rework rather than destroy, and the recovered product is re-monitored on the way through. Change the facts, a metal detector found not rejecting, a pH drift in shelf-stable sauce, and the branch changes, but the sequence of hold, evaluate, disposition, document does not.

How do you execute a corrective action?

You execute a corrective action by working the product and the process in parallel, then closing the loop with documentation and, where needed, a plan reassessment. The sequence below covers both halves and ends where every corrective action must: a record that proves it was done.

  1. Stop and hold. The moment monitoring shows a breach, stop making affected product and segregate and hold everything produced since the CCP was last known to be in control.
  2. Bring the CCP back under control. Correct the process, a jammed valve, a low set point, a failed detector, so production can resume within the critical limit.
  3. Find and eliminate the cause. Investigate why the deviation happened; run a root cause analysis if the reason is not immediately clear.
  4. Evaluate and disposition the held product. Have a qualified person judge safety, then release, rework, divert, or destroy, keeping any adulterated product out of commerce.
  5. Establish prevention. Put a measure in place, a mechanical fix, a procedure change, retraining, so the same deviation does not recur.
  6. Document everything, then reassess if needed. Record the deviation, the actions, the disposition, and who did what; if the deviation was not covered by the plan, reassess whether the plan must change.

Facts worth pinning

Why documentation is the deliverable

The corrective-action record is not paperwork after the real work; it is the deliverable. A deviation handled perfectly but recorded poorly looks, to an auditor or an FSIS inspector, like a deviation handled poorly, and a pattern of the same deviation recurring is exactly what verification and reassessment are supposed to catch. The record has to capture the deviation, the product disposition, the cause, the prevention, and the names, made close to when it happened, not reconstructed from memory a week later.

This is where paper systems fail hardest, because corrective actions are the records most likely to live in someone's head or a scribbled note. Capturing them on tablets, tied to the monitoring event that triggered them and the product lot affected, makes the whole loop traceable, the same digitize-the-paper move Harmony runs for production and quality records (see how CLS did it). It feeds straight into Principle 6, verification where corrective-action records are reviewed for exactly these patterns, and into your broader HACCP certification evidence. See how a connected operation keeps this loop live on the features overview.