12 October 2026 · 3 min read
How do you know an incident is actually closed?
Short answer: An incident is closed when you can show, with evidence, that the affected product is accounted for, the cause is understood, the corrective action is in place and verified, and everyone you told about it has been told it is over. Stopping the problem is not closure. Reconciliation is the hard part, how much product you made, how much was sold, how much came back or was destroyed, and what you believe happened to the gap. Most teams stop short of this because the pressure drops away once the retailer stops calling, and the file sits open for months. Then an auditor or insurer asks for the close out report and nobody can find a single version of what happened. Closure is a decision you make deliberately, on evidence, and record.
The rest of this covers what that evidence looks like and who needs it.
Stand down is not the same as close out
Stand down is operational. The duty line is quiet, product is on hold, the team can sleep. That can happen within a day.
Close out is evidential. It can take weeks, and it belongs to one named person. Confusing the two is how incidents quietly expire rather than end.
The reconciliation nobody enjoys
This is the number retailers and regulators go to first. You need:
- Quantity produced, in the affected batches, by code.
- Quantity dispatched, to whom, and when.
- Quantity recovered, returned, quarantined on site, held at depot, destroyed, with destruction evidence.
- The gap, and your reasoned account of it. Most of it is usually consumed, say so plainly rather than rounding the figure until it looks tidy.
An honest gap with an explanation reads better than a clean number nobody believes.
Effectiveness checks
Recovery figures alone do not prove the message landed. You check a sample of customers and depots and ask what they actually did, not what they confirmed by email. If a retailer says product was removed, you want the till block or the depot confirmation behind it.
Where a public notice went out, keep the notice itself, where it appeared, and how long it stayed up.
Telling people it is over
Everyone who received the alert needs the stand down, retailers, distributors, your own sales and customer service team, the duty line script, the regulator if they were notified. Consumer service in particular keeps repeating the holding line long after the position has changed, because nobody told them it moved.
The review, while it still stings
Hold it within a fortnight, not a blame session, a short written record of what was found, when, who decided what, what slowed you down, and what changes. Then put a date on each action and an owner, and check them at the next management review. If nothing in your procedure changed, you have not finished learning from it.
Frequently asked questions
What goes in a recall close out report?
Scope and product detail, the timeline, root cause, quantity reconciliation, effectiveness check results, corrective and preventive actions with owners, and confirmation that affected parties were stood down. Keep one version, not three.
Who signs off that an incident is closed?
Usually the Technical Director or Head of Quality, with sign off from whoever chaired the incident. Name the role in your procedure now, not during the event.
How long should we keep the records?
At least as long as your retailer and certification standards require, which is typically longer than product shelf life plus a margin. Confirm the specifics for your scheme and jurisdiction.
Can we close an incident without finding root cause?
You can close the response whilst an investigation continues, provided you say so explicitly, record the interim controls and set a review date. What you should not do is let it drift with neither cause nor controls.
Friday4:30 is the coordination layer for the food and drink business, from product incidents to business and industry issues, first alert to closed-out review.
This article is general guidance, not legal or regulatory advice. Always confirm your specific obligations with your regulatory authorities and legal advisors.