Corrective Actions for NZ Food Manufacturers and Processors

Every food manufacturing site in New Zealand deals with things going wrong. Equipment fails. A temperature reading drifts outside limits. A cleaning procedure gets missed during a shift changeover. That’s not the problem. The problem is what happens next.

Corrective actions are where your food safety system proves it actually works. Not on paper in a HACCP plan nobody reads, but on the production floor when something deviates from the plan. MPI verifiers know this, which is why corrective action records are one of the first things they review during a verification visit.

This guide covers how to write, document, and close out corrective actions that hold up under scrutiny. It’s aimed at QC managers and operators running under a Risk Management Programme or custom Food Control Plan in New Zealand.

What Corrective Actions Actually Are

In a manufacturing compliance context, a corrective action is a documented response to any situation where your food safety system did not perform as intended. That includes CCP deviations, procedure non-conformances, failed verification checks, audit findings, and food safety complaints.

The key word is “documented.” Fixing a problem without recording it is just firefighting. A corrective action only exists if there’s a record of it.

Under the Animal Products Act 1999, RMP operators must provide for appropriate corrective actions where animal material or products may not be fit for intended purpose. The Food Act 2014 requires similar provisions for custom FCP operators. Both Acts expect the system to be proactive, not reactive.

Corrections vs Corrective Actions

This distinction trips up a lot of operators, and it’s one MPI verifiers pay attention to.

A correction is the immediate action you take to contain the problem. Product held. Line stopped. Affected batch segregated. The correction deals with the consequences of the deviation right now.

A corrective action goes deeper. It asks why the deviation happened in the first place and puts measures in place to stop it recurring. This is the part that requires root cause analysis and follow-up verification.

Both must be recorded. Here’s a practical example:

Deviation: Metal detector rejects a pack during routine screening. CCP critical limit breached.

Correction (immediate): Pack removed from line. Previous 30 minutes of production since last confirmed pass isolated for re-screening. Affected product held pending investigation.

Corrective action (prevent recurrence): Investigation found metal detector sensitivity had drifted due to vibration from adjacent equipment. Detector recalibrated. Mounting bracket reinforced. Test frequency increased from every 2 hours to every hour for the next 5 production days. Verified by QC manager on [date].

If your records only show “metal detector alarm, pack removed, line restarted” then you’ve done the correction but not the corrective action. MPI will flag that.

When Corrective Actions Are Required

Not every minor hiccup needs a full root cause investigation. But the following situations always require documented corrective actions:

CCP deviations. Any time a critical limit is breached. No exceptions. Your HACCP plan should already define the corrective action procedure for each CCP. If it doesn’t, that’s a finding in itself.

Non-conformances against your RMP or FCP. A procedure wasn’t followed. A specification wasn’t met. Incoming materials failed checks. These all trigger corrective actions, even if no product was directly affected.

Failed verification activities. Your internal audit found a gap. Your environmental swab came back positive. Your calibration check showed a thermometer was reading 2 degrees low. Each of these needs a documented response.

Audit findings from MPI or your recognised agency. When a verifier raises a non-conformance, you are expected to respond with a corrective action within the timeframe they set. Ignoring it or responding inadequately escalates the finding.

Customer complaints related to food safety. A foreign body complaint, an illness report, or an allergen issue all require investigation and documented corrective action regardless of whether you believe the complaint is valid.

How to Write Corrective Actions That Satisfy Verifiers

MPI verifiers are not looking for perfect English or a specific template. They are looking for evidence that you understood what went wrong, contained the risk, identified the root cause, and took meaningful steps to prevent it happening again.

A complete corrective action record should include:

1. Date and time of the deviation
2. What happened, described specifically (not “temperature issue” but “chiller 3 reading 7.2C at 0600, critical limit 5C”)
3. Immediate correction taken and by whom
4. Product disposition, what happened to affected product
5. Root cause, why it happened
6. Corrective action, what you changed to prevent recurrence
7. Verification of effectiveness, evidence the fix worked
8. Sign-off by a responsible person and date of close-out

Miss any of these and your corrective action is incomplete. The two most commonly missing elements are root cause and verification of effectiveness. Verifiers see this constantly.

Root Cause Analysis That Actually Works

You don’t need a PhD in quality management to find root causes. Two methods work well on a production floor.

The 5 Whys

Start with the deviation and ask “why” until you get to something you can actually fix. Usually takes 3 to 5 rounds.

Problem: Cooked product temperature below 75C at CCP check. Why? Oven was running 10 degrees below set point. Why? Heating element partially failed. Why? Element exceeded its service life. Why? No preventive maintenance schedule for oven elements. Root cause: Missing preventive maintenance programme for critical cooking equipment.

That last answer is something you can act on. “Oven was cold” is not a root cause. “No maintenance schedule” is.

Fishbone (Ishikawa) Diagram

For more complex issues where the cause isn’t obvious, map potential causes across six categories: People, Methods, Materials, Machines, Measurement, and Environment. In food manufacturing, the most common root cause categories are Methods (procedure not followed or inadequate) and Machines (equipment failure or lack of maintenance).

The fishbone approach is particularly useful when you have a recurring problem that simple 5 Whys analysis hasn’t resolved. It forces you to consider causes you might otherwise overlook.

Documentation Requirements

MPI’s verification topics include corrective actions as a mandatory check at every verification visit. What verifiers want to see:

• A complete log of all corrective actions raised since the last visit
• Evidence that each corrective action was investigated, not just patched
• Documented root cause for each non-conformance
• Evidence of follow-up to confirm the corrective action was effective
• Traceability of affected product through to final disposition
• Timely close-out relative to the severity of the finding

Records must be maintained in a way that supports review. Under the Animal Products Act, records relating to monitoring, corrective actions, and operator verification must be kept and available for inspection. If a verifier asks to see your corrective action log and you spend 20 minutes pulling papers from different folders, that tells them your system has gaps.

Common Corrective Action Failures

Having reviewed hundreds of corrective action records across manufacturing sites, these are the patterns that get flagged most often:

Vague descriptions. “Temperature high, adjusted.” This tells the verifier nothing. What temperature? Which unit? Adjusted how? What happened to the product?

No root cause analysis. Jumping straight from “what happened” to “what we did about it” without explaining why it happened. This is the single most common failure and the easiest to fix.

Copy-paste corrective actions. When the same corrective action text appears five times in three months for the same issue, it’s obvious the fix isn’t working. MPI will treat this as a systemic failure, not five separate incidents.

No follow-up verification. You changed the procedure. You retrained the operator. But you never checked whether it actually worked. Without verification of effectiveness, the corrective action isn’t closed.

Delayed close-out. Corrective actions that sit open for months without progress signal that nobody is managing the system. Set realistic deadlines and track them.

No product disposition recorded. When a CCP deviation affects product, the verifier needs to see what happened to that product. Held, reworked, downgraded, destroyed. Silence on product disposition is a red flag.

Tracking and Closing Out Corrective Actions

A corrective action isn’t done when you write it down. It’s done when you can prove the fix worked.

The close-out process should follow this sequence:

1. Raise the corrective action with full details of the deviation and immediate correction
2. Investigate the root cause using 5 Whys, fishbone, or your preferred method
3. Implement the corrective action, whether that’s a procedure change, equipment repair, retraining, or supplier action
4. Verify that the action was effective through monitoring data, repeat testing, or observation
5. Close out with sign-off from someone with authority (QC manager, operations manager)
6. Review at your next management review or internal audit to confirm the issue hasn’t recurred

Keep a register. Whether it’s a spreadsheet, a database, or a digital system, you need a central view of all open corrective actions, their status, and their due dates. If you’re managing this across handwritten forms in different folders, things will fall through the cracks. They always do.

When Corrective Actions Become Systemic Issues

If the same type of non-conformance keeps appearing despite corrective actions, you have a systemic issue. This is where MPI’s graduated compliance approach kicks in.

The first time, it’s a non-conformance with a corrective action. The second time, the verifier starts questioning your root cause analysis. The third time, expect a Corrective Action Request (CAR) with a fixed deadline and potentially increased verification frequency.

Under MPI’s VADE (Voluntary, Assisted, Directed, Enforced) compliance model, repeated failures move you from assisted compliance to directed compliance. At that stage, MPI can issue improvement notices requiring specific changes within set timeframes. Continued non-compliance can result in prosecution, with penalties under the Food Act 2014 reaching $100,000 for individuals and $500,000 for body corporates for serious offences.

Signs that your corrective actions have become systemic:

• Three or more corrective actions for the same root cause category within 12 months
• Corrective actions that address symptoms but not underlying causes
• The same equipment, process, or staff member appearing repeatedly
• Corrective actions that reference “retraining” as the sole fix every time

When this happens, step back from the individual incidents and look at the pattern. The root cause is almost certainly procedural or structural, not operator error.

How the Custom FCP / RMP App Helps

Managing corrective actions on paper creates exactly the problems MPI flags most often: incomplete records, missing follow-up, no central tracking, and poor traceability.

The Custom FCP / RMP App is built for NZ food manufacturers running under Risk Management Programmes and custom Food Control Plans. For corrective action management specifically, it provides:

• Structured corrective action forms that prompt for all required fields, so nothing gets missed
• Timestamped entries with automatic audit trails that verifiers trust more than handwritten logs
• Root cause analysis templates built into the workflow, so operators complete the investigation rather than skipping it
• Open action tracking with due dates and status visibility across the team
• Linked records connecting corrective actions to the CCP logs, monitoring data, and product batches involved
• Close-out verification that requires evidence of effectiveness before sign-off

When your verifier arrives and asks to see your corrective action history, you can pull it up in seconds, filtered by date, CCP, type, or status. That alone changes the dynamic of a verification visit.

Getting It Right

Corrective actions aren’t paperwork for the sake of paperwork. They’re the mechanism that keeps your food safety system improving rather than just existing. Every non-conformance is information. The question is whether you use that information to fix the underlying problem or just patch the symptom and wait for it to happen again.

MPI verifiers can tell the difference. So can your customers.

Get the basics right: document everything, find the real root cause, verify the fix, and close it out. That’s what separates a site that breezes through verification from one that dreads it.