Corrective Action

What is a Corrective Action?

A corrective action is the documented response a food business takes when monitoring shows that a Critical Control Point (CCP) has gone out of control — that is, when a critical limit has been exceeded and a food safety hazard may not have been adequately controlled. Under FSANZ Standard 3.2.1, every food safety program must specify the corrective actions to be taken for each CCP, including what happens to any product that was produced while the CCP was out of control.

The corrective action requirement has two parts: fixing the immediate problem (bringing the process back under control) and deciding the fate of the affected product (rework, destroy, or hold for further assessment).

Corrective Actions in Practice for Australian Food Manufacturers

What triggers the requirement? A corrective action is triggered whenever a CCP critical limit is breached. For example: the internal temperature of a cooked product does not reach the minimum required temperature; a metal detector fails its calibration check; the pH of an acidified product is above the safe level; chilled storage temperature exceeds the maximum limit.

Two common mistakes:

No documented corrective action procedure. Many small manufacturers have CCPs in their HACCP plan but no written corrective action for each one. "We'd throw it out" is not sufficient — Standard 3.2.1 requires the action to be documented in the food safety program in advance, not decided on the fly when something goes wrong.

Fixing the process but not recording it. Corrective actions must be recorded, not just taken. An auditor reviewing your food safety program will check that corrective action records exist and are linked to the specific CCP breach that triggered them.

Worked example: A Queensland bakery's HACCP plan identifies the baking oven as a CCP with a minimum core temperature critical limit of 75°C for its chicken pie filling. During a production run, the temperature probe shows 68°C for batch BB-2024-041. The operator's corrective action procedure states: (1) extend baking time by 5 minutes and re-check temperature; (2) if still below 75°C, remove product from production and label as "hold — food safety assessment required"; (3) record the deviation, the action taken, and the final disposition of the product. The operator follows the procedure, achieves 76°C on re-check, and documents the deviation in the batch record and the corrective action log.

Preventive vs corrective: Standard 3.2.1 uses "corrective action" to mean both fixing the immediate deviation and implementing measures to prevent recurrence. After a corrective action event, the food safety program should be reviewed to determine whether the CCP critical limit, monitoring procedure, or equipment needs adjustment.

How Batchbase Supports Corrective Action Records

Batchbase's food safety program module allows you to document the corrective action procedure for each CCP in advance — what to do, who is responsible, and what happens to affected product. During production, if an operator records a CCP result that falls outside the critical limit, Batchbase flags the deviation and prompts the operator to record the corrective action taken and the disposition of affected product.

These corrective action records are stored against the relevant batch record, creating a complete audit trail that links the CCP breach, the corrective action, and the product outcome. This is exactly what an approved auditor under Standard 3.2.1 will look for when reviewing your food safety program records.

Related Standards and References

• FSANZ Standard 3.2.1 — Food safety programs (corrective action requirements at clause 5)
• Codex Alimentarius CAC/RCP 1-1969 — General Principles of Food Hygiene (HACCP Principle 5: corrective actions)
• FSANZ food standards code