A technician finds a bait block gnawed on the north wall. He replaces it, notes it on the service report, and moves on. The finding is closed. Six weeks later the block on the same station is gnawed again, and the one next to it too. Now there is a pattern, a defensive email trail, and an auditor asking why a known issue was recorded three times and never actually solved. The problem was never the bait block. It was the gap in the cladding twelve metres away that let rodents into the wall void in the first place, and nobody looked for it because replacing the block felt like closing the finding.
This is the single most common weakness we see in otherwise well-run pest programmes across food and beverage sites: correction is mistaken for corrective action. This article sets out the difference, walks a 5 Whys analysis through a rodent breach and a fly spike, and shows what verification and close-out actually require. A blank corrective action log is on our free checklists and forms page.
Key takeaways
- Correction fixes the symptom (replace the block); corrective action removes the cause (seal the entry point). Auditors score the corrective action.
- Root cause analysis, done properly with a method such as 5 Whys, stops when it reaches a condition you can control, which is almost always a process or structural failure, not the pest.
- A finding is only closed when there is verification and objective close-out evidence, and the recurrence is trended so a repeat pattern triggers escalation.
Correction is not corrective action
The two words are used interchangeably on the floor, but they are different steps and an audit treats them differently. Correction is the immediate action that deals with the symptom in front of you: replacing the chewed block, sealing the gap under the door today, emptying the insect light trap that is full of catch. It is necessary and it happens first. Corrective action is what you do so the problem does not come back: identifying and eliminating the condition that produced the finding.
BRCGS, FSSC 22000 and every retailer scheme expect both, and they specifically require corrective action with root cause for recurring or significant issues. A file full of corrections and no corrective actions reads as a site that reacts but never learns, and that is exactly the finding an auditor writes.
Root cause analysis with 5 Whys
Root cause analysis is not a paperwork ritual. It is the discipline of not stopping at the first plausible explanation. The 5 Whys method is enough for most pest findings: you state the effect and ask why, then ask why of the answer, repeating until you reach a cause you can actually act on. You rarely need exactly five; the number is a reminder to go deeper than the first answer.
Worked example: a rodent breach
Effect: internal bait stations along the north wall show feeding over three consecutive services.
- Why is bait being taken internally? Rodents are active inside the wall void.
- Why are they in the void? They are entering from the external perimeter.
- Why can they enter? There is a 20 mm gap where a service pipe passes through the cladding, unsealed.
- Why is it unsealed? The penetration was cut during a plant upgrade and never proofed.
- Why was it missed? Proofing was not on the handover checklist for contractor work.
The root cause is not the rodent and not the bait block. It is a handover process that let an unsealed penetration stay open. The corrective action is to seal the penetration and add proofing to the contractor handover checklist so the next upgrade does not repeat it. That second half is what makes it corrective rather than merely a correction.
Worked example: a fly count spike
Effect: catch on the despatch insect light trap doubles between two services, mostly small flies (Drosophila species).
- Why has catch doubled? A breeding source has developed nearby.
- Why is there a breeding source? Organic residue is fermenting somewhere close to despatch.
- Why is residue accumulating? A floor drain near the dock is holding sludge.
- Why is the drain dirty? It was dropped from the deep-clean rotation when the schedule was revised.
The corrective action is to clean and treat the drain (correction) and to restore it to the cleaning schedule with a verification check (corrective action). Small flies breed in days, so a scheduling gap that would be trivial for rodents produces a visible spike within a fortnight.
Verification: proving the action worked
Taking the action is not the same as confirming it worked. Verification is the deliberate check, done after a suitable interval, that the corrective action achieved its purpose. For the rodent breach that means the internal stations return to no-feed status over the next services and the sealed penetration is re-inspected. For the fly spike it means the light trap catch returns toward baseline. Verification is often the missing step: the action is recorded, but nobody confirms the activity actually stopped, so a partial fix is filed as a full one.
Close-out evidence
A finding is closed when there is objective evidence that the corrective action was completed and effective. On a corrective action record that means:
| Field | What good looks like |
|---|---|
| Finding | What was observed, where, and when, with a photo |
| Root cause | The controllable condition, from a 5 Whys or similar analysis |
| Correction | The immediate action and when it was done |
| Corrective action | The action that removes the cause, with responsible person and deadline |
| Verification | The follow-up check and its result |
| Close-out evidence | Dated photo of the completed work, work-order reference, monitoring data at baseline |
A finding marked closed with only a tick and a date, and no supporting evidence, is treated by auditors as still open. The photograph and the return-to-baseline data are what turn a claim into evidence.
Trending recurrences
Individual corrective actions solve individual problems. Trending is what catches the pattern a single record cannot see: the same station flagged three times, fly counts creeping up every summer at the same line, a cluster of findings near one dock door. When a finding recurs despite corrective action, the trend is telling you the root cause analysis went to the wrong depth, and it should trigger escalation to structural or process change rather than another replacement block. This is why corrective action records and trend analysis in the documented file belong together, and why our myASConline portal links every finding to its station history automatically.
Get the corrective action log
The fastest way to move a team from correction to corrective action is to give them a record that forces the root cause and verification fields, so they cannot close a finding without them. Download our free corrective action log and checklists, or ask us to build the closed-loop process into your food and beverage pest programme. If you want to see how findings are read at the audit table, our food safety audit tips cover the auditor's view.
Frequently asked questions
What is the difference between correction and corrective action in pest control?
Correction is the immediate fix for the symptom, such as replacing a chewed block or sealing a gap today. Corrective action removes the cause so the problem does not recur, such as finding and closing the entry point rodents used. Audits score the corrective action.
How do you do root cause analysis on a fly count spike?
Use 5 Whys. Start with the doubled catch and ask why at each level until you reach a controllable condition, usually a missed cleaning or scheduling failure rather than the flies, then correct that and verify the catch returns to baseline.
What counts as acceptable close-out evidence?
Objective proof the action was done and worked: a dated photo of the completed repair, the work-order reference, a responsible signature, and follow-up monitoring showing activity back at baseline. A tick and a date alone is treated as still open.
