Incident Management Ireland & UK

What Is a Food Safety Incident — and What Should a Food Business Record?

A food safety incident is any safety or quality concern that may require action to protect consumers. This guide explains what to record from the first finding through containment, corrective action and review.

A food safety incident is a situation where the safety or quality of food may require action to protect consumers. It might involve contamination, an undeclared allergen, incorrect labelling, a supplier notice, a failed temperature control, pest activity, foreign material, or food that may be unsafe for another reason. The record should show what happened, what food or sites were affected, what immediate action was taken, who was responsible and how the business verified that the risk was controlled.

The answer in 30 seconds

When a food safety incident happens, record the time, location, person reporting it, affected product or area, batch/date information, hazard, immediate containment action, stock removed or held, authorities or suppliers contacted, corrective actions, evidence, manager verification and post-incident review. The goal is not just to prove that a form was completed. It is to prove that the business recognised the risk, protected consumers and learned from the failure.

TapTick helps food businesses turn incident handling into a controlled workflow: frontline recording, supporting evidence, corrective actions, manager verification and inspection-ready history. See the TapTick features.

Why food safety incidents matter

Food incidents are becoming more visible and more complex. The Food Standards Agency recorded 2,073 food and feed safety incidents in England, Wales and Northern Ireland during 2025/26, a 14% increase on the previous year. The FSA noted that increased reporting or changes in testing may explain part of the rise, but it also pointed to growing scale and complexity linked to global supply chains and cross-border distribution.

The same report shows why incident readiness cannot be limited to fridge temperatures. Pathogenic micro-organisms were the most commonly reported hazard type, with Salmonella, Listeria and E. coli/STEC prominent within that category. Allergen incidents were the second most commonly reported hazard type. That means a useful food safety system needs to handle microbiological risk, allergens, labelling, traceability, supplier issues, corrective action and evidence.

For a food business, the key question is practical: if something goes wrong today, can you prove what happened, what food was affected, what action was taken and who verified that the risk was controlled?

What counts as a food safety incident?

The FSA describes a food incident as a situation where concerns around the safety or quality of food or feed may require action to protect consumers. It gives examples including contamination during processing, distribution, retail or catering, as well as environmental pollution incidents that could affect food safety.

In day-to-day operations, a food business may need to treat any of the following as a potential incident:

  • a supplier recall or withdrawal notice;
  • food stored outside safe temperature limits;
  • possible Listeria, Salmonella or other microbiological contamination;
  • undeclared allergens or incorrect labels;
  • a product packed in the wrong packaging;
  • pest evidence in a food area;
  • foreign material found in food;
  • chemical contamination or cleaning-chemical misuse;
  • food from an unapproved or unknown supplier;
  • repeated failure of a control such as cleaning, chilling or hot holding.

Not every problem becomes a public recall. Some incidents are contained within the business. Others require supplier notification, local-authority advice, a withdrawal, a customer recall or a root-cause review. The record should be strong enough to explain the decision taken.

Do not wait until the incident is fully understood

The first record should capture what is known at the time. You can update the incident as more information arrives, but the original finding, time, action and decision trail should remain visible. Rewriting the past to make the final record look neat weakens the evidence.

What should you record first?

The first record should let a manager understand the situation quickly, even if they were not present. Start with the basics:

  • Date and time: when the issue was found and when it was reported.
  • Location: the site, department, storage area, display area, kitchen, delivery area or vehicle involved.
  • Reporter: the person who found or received the issue.
  • Incident type: allergen, microbiological, foreign body, temperature, pest, supplier, labelling, chemical, traceability or other.
  • Description: plain English explanation of what was found or reported.
  • Evidence: photographs, supplier notice, delivery document, batch label, customer complaint, temperature result or laboratory result where available.

If a product is involved, capture the product name, pack size, supplier, brand where relevant, batch or lot code, use-by or best-before date, quantity found and where the stock was located. For multi-site businesses, record which sites may be affected and which have confirmed zero stock.

Containment and immediate action

Containment is the first operational priority. It should happen before the business becomes absorbed in investigation or paperwork.

Common immediate actions include stopping use or sale, isolating stock, closing an affected area, removing food from display, increasing checks, notifying a manager, contacting the supplier or contractor, and seeking advice from the competent authority where required.

The record should describe the immediate action in enough detail to be useful. “Sorted” is not enough. A stronger entry might say: “Removed 14 units from chilled display and 6 units from back-up stockroom; placed in labelled quarantine crate in rear chiller; manager notified; supplier notice attached.”

For food that may have reached customers, the business may need to consider whether a recall is required. For food that remains within the supply chain, withdrawal may be enough. The distinction matters, but both require a clear action trail.

When withdrawal or recall may be needed

UK guidance explains that a withdrawal removes unsafe food from the supply chain before it reaches consumers, while a recall removes unsafe food from the supply chain and advises consumers to take action, such as returning or disposing of the food.

If a business believes food it has supplied is harmful to health, unfit to eat or not legally compliant, UK guidance says it should immediately withdraw or recall the food from the market and tell the competent authority, which may advise on further action. If unsafe food has reached consumers, the FSA incidents team may need to be told and a recall notice may be issued.

In Ireland, FSAI food incident reporting also asks for practical action details such as trade withdrawal, customer recall, point-of-sale notice and similar actions. That reflects the operational reality: regulators and businesses need to know not only what went wrong, but what was done about it.

Corrective action and root cause

After the immediate risk is controlled, the business should investigate why the incident happened and what will stop it happening again. The FSA advises root-cause analysis after a food safety incident and says the findings can be used to review food safety and hygiene management, including traceability, withdrawal and recall arrangements.

A useful corrective-action record should include:

  • the immediate cause and suspected root cause;
  • the named owner of each action;
  • a completion deadline;
  • evidence that the action was completed;
  • manager verification;
  • whether the issue should be reopened if the action is inadequate;
  • follow-up checks to prove the control is working.

Corrective action is especially important where the incident points to a system weakness: staff training, supplier checks, labelling controls, cleaning verification, temperature monitoring, building maintenance, pest prevention or stock rotation.

Food safety incident checklist

  • Record the date, time, site and exact location.
  • Record who found or reported the issue.
  • Classify the incident type and describe the hazard.
  • Capture the affected product, supplier, batch, date code and quantity where relevant.
  • Attach photographs, supplier notices, labels, temperature results or other evidence.
  • Stop sale, stop use or isolate affected food where needed.
  • Record stock removed, stock quarantined and confirmed-zero checks.
  • Notify the manager and relevant internal owner.
  • Contact the supplier, contractor, local authority or FSAI/FSA route where required.
  • Display point-of-sale or customer notices where instructed.
  • Assign corrective actions with owners and deadlines.
  • Verify completion before closing the incident.
  • Review the root cause and update controls where needed.
  • Keep the complete record for inspection and internal learning.

How TapTick helps

From incident to verified closure

TapTick helps food businesses move from a loose note or email chain to a controlled incident record. Staff can record the issue, product, batch, quantity and evidence. Managers can assign actions, verify completion and see which sites still need to respond.

This is especially useful for multi-site operators handling recalls, allergen issues, failed controls or supplier problems. It supports fast frontline recording, trustworthy evidence and closed-loop corrective action without turning the process into heavy software administration.

Start a free TapTick trial. No credit card required.

A good incident record should answer five questions: what happened, what was affected, what was done immediately, what was fixed permanently and who verified closure. If those answers are clear, the business is in a stronger position with managers, auditors and inspectors.

Official sources

Disclaimer: This article is general operational guidance, not legal advice. Requirements depend on the product, hazard, jurisdiction and facts of the incident. Follow official recall notices and seek advice from your competent authority, enforcement officer or food-safety adviser where required.

Put the guidance into practice

Make the daily record easier to complete—and easier to prove.

Start with one site, no credit card required.