16 November 2026 · 4 min read
When do you pick up the phone to the regulator?
Short answer - you notify when you have reason to believe product that is unsafe, or that does not meet food law, has left your control. Not when the investigation is finished, not when you have a root cause, and not when legal has reviewed the wording. In the UK and EU the duty under food law sits with the food business operator and the trigger is belief, not proof. In the US, the Reportable Food Registry and FDA notification rules work on a similar basis of reasonable probability of serious harm, with their own clocks. The practical test most Heads of Quality can apply at the desk: if you would want your own family warned, you are past the point of notifying, and the specifics of who you call and how fast depend on your jurisdiction and your approvals. This is general guidance, not legal advice; check the requirements that apply to your business and your approvals.
What follows is about the gap between knowing that and actually making the call.
The delay is rarely about the rules Almost nobody misses a notification because they misread the guidance. They miss it because the investigation is still moving, the lab result is due at 4pm, the co-packer has not come back, and every hour looks like it might resolve the question.
So the call slides. Then it slides again. By the time you phone, the first question you get is why you did not phone sooner, and you are answering that instead of describing the problem.
What you are allowed to not know The most common unspoken reason for waiting is the fear of ringing up with an incomplete picture. You do not need a complete picture.
A first notification that works sounds like this:
- What you believe is wrong. Allergen not declared, pathogen detected, foreign body with injury potential. What product and how much. Batch codes and date codes if you have them, your best current scope if you do not, clearly labelled as provisional. Where it has gone. Retail, foodservice, export, still in your warehouse. What you have already done. Stock on hold, line stopped, customers contacted. Who to ring back. A name and a mobile that will be answered tonight.
Say plainly which parts are still being confirmed. Regulators deal with moving information constantly. What they react badly to is finding out that you knew something and sat on it.
Decide who owns the call before you need it In a lot of businesses the answer to “who rings the authority” is genuinely unclear, and it surfaces at the worst moment. The Technical Director assumes the Head of Quality has done it. The founder wants a word first. Nobody wants to be the person who escalated something that turns out to be nothing.
Name one person and one deputy. Write down who they call, including the out of hours route, and check the number is current. A local authority main switchboard at seven on a Friday evening is not a plan.
Notifying is not the same as recalling Telling your authority what you have found does not commit you to a recall. It starts a conversation in which you will usually be asked what you intend to do, and your answer can be that you are assessing scope and will confirm within a stated time.
Keeping those two decisions separate in your own head removes most of the reluctance to call early. You are reporting a finding, not announcing an outcome.
Record the moment you decided Whatever you decide, log the time you became aware, what you knew then, what you decided and who agreed it. If you decide not to notify, that reasoning is the single most useful piece of paper you will own in an audit six months later.
Every one of these decisions is easier made on a quiet Tuesday than in the middle of an incident. Who calls, what they say and where it is recorded should already be settled before you need them.
Frequently asked questions Do I have to notify if the product is still inside my factory?
Generally no, if it is genuinely under your control and cannot be released. The obligation bites when unsafe product has left your control. The grey area is product sitting at a third party warehouse or a co-packer, where “control” is a question of fact rather than contract. If you cannot stop it with certainty, treat it as gone.
What if I notify and it turns out to be fine?
That outcome is normal and regulators expect it. You close the matter out with your evidence. A business that occasionally reports something that resolves to nothing looks like a business that is paying attention.
Who notifies when a retailer found the problem, not us?
You do, as the food business operator responsible for the product. Assume the retailer has already told their own contacts. Do not let that be your reason to wait.
Does it have to be in writing?
Phone first if it is urgent, then confirm in writing the same day with what you said and what you promised. The written version becomes the record both sides work from.
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.