18 September 2026 · 14 min read

Food Recall Checklist: What to Do in the First 24 Hours

A potential food safety incident can change quickly.

One moment, a food business is operating normally. The next, a customer complaint, laboratory result, supplier notification or internal quality issue may raise a question that requires urgent investigation.

The first 24 hours are critical because the team often has to make decisions before it has all the information.

This food recall checklist provides a practical framework for managing the early stages of a potential recall. It is designed for food and beverage companies and can be adapted to different products, markets and organisational structures.

Important: This checklist is an operational framework, not legal or regulatory advice. Recall notification requirements vary by jurisdiction, product, risk and circumstances. Companies should follow their applicable procedures and obtain appropriate professional or regulatory advice.

Quick answer: What should you do in the first 24 hours of a potential food recall?

In the first 24 hours, a food business should focus on:

Identify the issue
Open and document an incident
Secure potentially affected product
Assess the immediate risk
Establish what is known and unknown
Identify affected products, batches and suppliers
Assemble the incident team
Create clear actions and owners
Determine the distribution and potential scope
Document decisions and evidence
Escalate to the appropriate internal and external stakeholders
Determine the appropriate product withdrawal or recall response
Maintain a live timeline
Plan the next 24 hours

The exact sequence will depend on the nature of the incident.

Before the first 24 hours: have a recall plan

The best recall response starts before the recall.

Every food business should have a documented process covering:

Who leads a recall
Who can escalate an incident
Who makes key decisions
Who contacts suppliers
Who contacts customers and retailers
Who manages regulatory communications
Who manages communications
Where product and supplier information is stored
Where recall procedures are stored
How evidence is recorded
How decisions are documented
How actions are assigned
How the incident is closed

The procedure should also be tested.

A mock recall can reveal gaps that are difficult to see when reviewing a static SOP.

The first 24 hours: a practical timeline

0-1 hour: Capture the issue

The first priority is to establish a reliable record of what has been reported.

Create an incident record containing:

Date and time
Person reporting the issue
Source of the information
Product involved
Batch or lot information, if known
Supplier, if relevant
Manufacturing site, if relevant
Description of the issue
Initial evidence
Immediate actions already taken

Do not wait until you have all the information.

Record what is known and clearly identify what is still unknown.

Ask:

What exactly has been reported?
Who reported it?
When did it happen?
Which product is involved?
Is there evidence?
Is anyone potentially at risk?
Is product still being produced or distributed?

1-2 hours: Secure potentially affected product

If there is a credible concern about product safety, determine whether potentially affected stock can be identified and controlled.

Depending on the circumstances, this may involve:

Stopping production
Quarantining stock
Placing product on hold
Preventing further dispatch
Notifying relevant internal teams
Preserving samples
Securing relevant records

The appropriate action depends on the incident and applicable procedures.

The important operational principle is:

Do not allow uncertainty about the final scope to prevent sensible immediate controls.

Document what was placed on hold, when and by whom.

2-4 hours: Conduct an initial risk assessment

The team should establish an initial view of the potential risk.

Consider:

Hazard

What is the potential food safety or quality issue?

Examples might include:

Allergen
Microbiological contamination
Foreign body
Chemical contamination
Incorrect labelling
Undeclared ingredient
Packaging failure

Severity

What could happen if consumers are exposed?

Likelihood

How likely is the suspected issue to be present or cause harm?

Exposure

Could consumers have received the product?

Scope

Is this potentially limited to one batch, one product, one site or a wider group?

Evidence

What information supports the concern?

The initial assessment is not necessarily the final assessment.

As new information becomes available, the risk assessment may need to change.

4-6 hours: Establish the facts

At this point, the team should begin separating confirmed information from assumptions.

Create three lists:

What we know

For example:

Product X was manufactured on Tuesday
Supplier Y supplied ingredient Z
A complaint was received at 09:15
Batch 12345 is potentially affected

What we don't know

For example:

Whether other batches are affected
Whether the issue originated with the supplier
Whether affected product reached consumers
Whether the suspected hazard is actually present

What we need to find out

For example:

Confirm supplier batch
Review laboratory results
Check production records
Identify affected customers
Confirm distribution

This simple distinction can prevent speculation from becoming treated as fact.

6-8 hours: Identify the incident team

A potential recall can quickly become cross-functional.

Depending on the circumstances, the response team may include:

Technical / food safety
QA
Operations
Procurement
Supply chain
Manufacturing
Customer service
Legal
Communications
Senior management

Assign one clear incident lead.

Then assign owners to specific actions.

Avoid having five people "looking into it" without anyone owning the outcome.

Create a recall command structure

A simple structure might be:

Incident Lead

Owns the overall response.

Technical / Food Safety Lead

Owns risk assessment, investigation and technical decisions.

Operations Lead

Owns production, stock and site actions.

Supply Chain Lead

Owns distribution and product location.

Procurement / Supplier Lead

Owns supplier communication.

Communications Lead

Owns internal and external communications.

Management Lead

Provides senior-level decisions and escalation.

The exact structure will vary by organisation.

The important principle is clear ownership.

8-12 hours: Determine the scope

Now begin establishing exactly which products may be affected.

Look at:

Product codes
SKU numbers
Batch numbers
Lot numbers
Production dates
Best-before dates
Use-by dates
Manufacturing sites
Ingredients
Supplier batches
Packaging versions

Then determine the potential distribution.

Ask:

Which warehouses received the product?
Which retailers received it?
Which distributors received it?
Has any product reached consumers?
Is any stock still in the business?
Is product still in transit?
Has product crossed borders?

The objective is to create the clearest possible picture of the affected scope.

Build an affected product list

Create a live list containing, where relevant:

Product	SKU	Batch/Lot	Production date	Quantity	Location	Status
Product A	SKU001	B123	12 Sep	4,000	Warehouse A	On hold
Product B	SKU002	B124	13 Sep	2,500	Retailer	Potentially affected

Do not rely on a static document if the information is changing rapidly.

The list should have a clear owner and update process.

12-16 hours: Confirm distribution and customer exposure

Once potentially affected products have been identified, establish where they have gone.

Depending on your supply chain, this may include:

Warehouses
Distributors
Retailers
Foodservice customers
Online customers
Direct customers
International markets

Create a distribution map or list.

For each destination, record:

Customer
Product
Batch
Quantity
Date shipped
Current status
Contact
Action required
Action completed

This can become the basis for the recall execution plan.

16-20 hours: Determine the response

At this stage, the team should have a clearer understanding of:

What happened
Potential hazard
Risk
Affected products
Affected batches
Distribution
Available evidence
Current controls

The appropriate response will depend on the facts and applicable requirements.

Possible actions may include:

Continue investigation
Maintain product hold
Withdraw product from the supply chain
Recall product from consumers
Expand the affected scope
Reduce the affected scope
Contact relevant authorities
Notify customers or retailers
Issue appropriate communications

The decision and reasoning should be documented.

20-24 hours: Consolidate the incident record

By the end of the first day, make sure the incident record contains a coherent picture of the response.

It should include:

Incident

Original report
Date and time
Description
Source

Risk

Hazard
Initial assessment
Updated assessment
Evidence

Product

Affected products
Batches
Sites
Quantities

Supply chain

Suppliers
Warehouses
Retailers
Distributors
Customers

Actions

Action
Owner
Deadline
Status

Communications

Person / organisation contacted
Date and time
Method
Information provided
Response

Decisions

Decision
Date and time
Decision-maker
Reasoning
Supporting evidence

Timeline

A chronological record of important events.

The 24-hour recall checklist

Use this as a quick operational checklist.

Incident identification

Incident created
Time recorded
Reporter recorded
Product identified
Initial evidence attached
Known and unknown information separated

Immediate controls

Potentially affected stock identified
Product placed on hold where appropriate
Production reviewed
Dispatch reviewed
Samples / evidence secured
Immediate actions documented

Risk assessment

Hazard identified
Severity assessed
Likelihood considered
Consumer exposure considered
Initial scope assessed
Risk assessment documented

Team

Incident lead appointed
Technical lead appointed
Operations lead appointed
Supply chain lead appointed
Supplier lead appointed
Communications lead appointed
Senior management escalation completed where required

Investigation

Supplier contacted where relevant
Production records reviewed
Laboratory results reviewed
Product specifications reviewed
Relevant complaints reviewed
Root cause investigation started
Evidence collected

Scope

Affected products identified
Batches identified
Production dates identified
Sites identified
Supplier batches identified
Distribution identified
Customer exposure assessed

Recall / withdrawal

Appropriate response determined
Decision documented
Relevant stakeholders identified
Customer / retailer actions assigned
Regulatory requirements assessed
Communications prepared
Product status tracked

Documentation

Incident timeline maintained
Evidence organised
Decisions documented
Actions assigned
Communications recorded
Supporting documents stored
Next steps defined

What not to do during a food recall

Don't wait for perfect information

The initial picture will often be incomplete.

Record what is known, what is unknown and what needs to be investigated.

Don't rely entirely on email

Email can be useful for communications, but it is a poor substitute for a central incident record.

Important decisions and actions can easily become buried.

Don't let everyone own the incident

One person should own the overall response.

Individual actions should have individual owners.

Don't forget the timeline

Record important events as they happen.

Reconstructing a timeline from memory weeks later is much harder.

Don't treat every incident as a recall

A potential food safety issue requires assessment.

Do not assume that every complaint or quality problem automatically requires a recall.

Don't stop when the product is removed

The incident still needs investigation, documentation, corrective actions and review.

How to prepare for a recall before it happens

The best recall checklist is one your team has already practised.

Maintain current contact information

Make sure key internal, supplier, retailer and other relevant contacts are current.

Keep critical information accessible

People should know where to find:

Product information
Supplier information
Specifications
Procedures
Contact lists
Distribution records
Regulatory information

Run mock recalls

Test a realistic scenario.

For example:

"A supplier tells us at 9am that an ingredient used in three products may be contaminated."

Then measure:

Time to identify the product
Time to identify affected batches
Time to identify the supplier
Time to identify customers
Time to assemble the response team
Time to produce the required information

The objective is to identify weaknesses before a real incident.

Food recall software can make this process easier

A recall procedure is only useful if people can execute it.

When the process is managed through spreadsheets, documents and email, teams can lose time:

Finding the latest information
Identifying who owns an action
Locating evidence
Reconstructing decisions
Building timelines
Producing reports

Food recall management software can provide a central system for:

Incident intake
Risk assessment
Product identification
Supplier information
Tasks
Evidence
Timelines
Communications
Recall workflows
Corrective actions
Reporting
Readiness assessments

The objective is not simply to digitise a checklist.

It is to make the entire response process more visible and repeatable.

Friday4:30 and food recall readiness

Friday4:30 is built around the operational side of food safety incidents and recalls.

The platform provides a central workflow for managing an incident from initial identification through investigation, response and resolution.

It can help teams organise:

Incident information
Guided response workflows
Risk assessment
Tasks and ownership
Evidence
Supplier and product information
Incident timelines
Recall actions
Documentation
Corrective actions
Readiness assessments
Mock recall preparation

The goal is simple:

When an incident happens, your team should already know what to do.

Instead of relying on people to remember the process under pressure, the workflow provides structure around the response.

Frequently asked questions

What should I do in the first 24 hours of a food recall?

Start by documenting the incident, securing potentially affected product, conducting an initial risk assessment, assembling the response team, identifying affected products and batches, determining distribution, assigning actions and documenting decisions.

The exact response depends on the incident and applicable regulatory requirements.

What is the first step in a food recall?

The first step is usually to identify and document the potential issue and establish immediate controls appropriate to the circumstances.

Do not wait for every fact to be confirmed before creating an incident record.

How quickly should a food company respond to a potential recall?

Potentially serious food safety incidents should be escalated promptly according to the company's procedures and applicable requirements.

The appropriate response time depends on the nature and severity of the incident.

What information should be recorded during a food recall?

Record the incident, evidence, risk assessment, affected products, batches, suppliers, distribution, actions, decisions, communications and timeline.

Who should manage a food recall?

A recall should have a clearly designated incident or recall lead, supported by the relevant technical, quality, operations, supply chain, procurement, communications and management teams.

The exact structure depends on the organisation.

What is a mock recall?

A mock recall is a planned exercise in which a food company simulates a product recall to test its traceability, communication, decision-making and response processes.

It can reveal gaps before a real recall occurs.

What is the difference between a food withdrawal and a food recall?

The terminology and regulatory definitions can vary by jurisdiction.

Generally, a withdrawal involves removing product from the supply chain before it reaches consumers, while a recall involves action to retrieve product that may already have reached consumers.

Businesses should use the definitions and procedures applicable to their market.

Does every food safety incident require a recall?

No.

A food safety or quality incident should be assessed based on the available evidence, potential risk and applicable procedures and requirements.

Some incidents can be resolved without a consumer recall.

Downloadable food recall checklist

A practical recall checklist should be kept somewhere the team can access it quickly.

The checklist should cover:

Incident identification
Immediate controls
Risk assessment
Incident team
Investigation
Product scope
Distribution
Recall decision
Communications
Documentation
Corrective actions
Post-incident review

Review the checklist regularly and update it after incidents, exercises, organisational changes and changes to relevant requirements.

Conclusion

A food recall is not a single task.

It is a sequence of decisions, investigations, communications and actions that need to happen while the facts may still be developing.

The first 24 hours should therefore focus on creating control:

Capture the issue.

Secure the product.

Assess the risk.

Establish the facts.

Bring the right people together.

Identify the scope.

Assign actions.

Document decisions.

Coordinate the response.

Keep the timeline current.

Most importantly, do not wait for a real recall to discover whether the process works.

Run the mock recall first.

Friday4:30 helps food and beverage teams turn incident and recall response into a structured, repeatable process, while building readiness before something goes wrong.