How-To Guide

How to Do a Mock Recall in a Food Business

How to run a mock recall in a UK kitchen: pick a product, trace it one step back, find every pack on site, account for what was used, time it and fix the gaps.

Estimated time: 1 hour
The short version

Pick a product you received in the last few weeks, start a timer, and trace it: which supplier, which delivery, which batch code, how much is still on site and what happened to the rest. Stop the timer, write down how long it took and what you could not find, and fix those gaps.

  • Step 1: Pick a product and a batch
  • Step 2: Start the timer
  • Step 3: Trace it one step back

A mock recall is a practice run of what you would do if a supplier or the Food Standards Agency recalled a product you bought. It tests whether your records can answer the questions a real recall asks, while nothing is at stake.

The law asks every food business to know who supplied each food it uses (one step back, under Article 18 of Regulation 178/2002, kept in UK law) and to withdraw unsafe food. Manufacturers certified to standards such as BRCGS have to test their traceability at least once a year. For a restaurant, pub or cafe, once a year is a sensible minimum, and after any change to how you record deliveries.

The exercise takes under an hour.

8 steps to complete

1

Pick a product and a batch

Choose a product you received in the last few weeks, ideally a chilled one with a batch code, such as cream, chicken or smoked salmon. Take its batch code from a delivery note or a pack, or pretend the recall names a product and a use-by date only, which is what many FSA alerts look like.

2

Start the timer

Note the time. The question is how long it takes to answer: did we receive it, which batch, where is it now, and was any used. A common target is four hours; a small kitchen with good records can do it in minutes.

3

Trace it one step back

Find the delivery it came on: the supplier, the date, the batch code and use-by, the quantity, who received it and the temperature at the door. Find the paperwork for it too: the delivery note, and the invoice if you have it.

4

Find every pack on site

Check every place it could be: the walk-in, under-counter fridges, the freezer, the dry store and any second site. Count what is left. In a real recall, this stock would be set aside, labelled do not use, and kept until the supplier or the FSA says what to do with it.

5

Account for what has gone

For the rest, find out what happened to it: used up, binned, frozen or returned. Note anything that was used before the recall date. In a real recall, that food may have reached customers, and you would follow the supplier's or the FSA's advice on what to tell them.

6

Trace one step forward if you supply other businesses

If you sell food on to other businesses, such as a central kitchen supplying sites or catering for another company, find who you supplied, when and how much. Sales to the public do not need this, but you should still know which dishes the product went into.

7

Stop the timer and record it

Write down the date, the product, how long it took, what you found and what you could not find. Keep it with your food safety records. An EHO or an auditor may ask to see it.

8

Fix the gaps

The point of the exercise is the gaps. Typical ones: batch codes not written down at delivery, delivery notes thrown away, no record of what was binned, or nobody knowing who to call at the supplier. Change the delivery check or the daily routine so the gap closes, then test again next year.

How to Do a Mock Recall

Trace a product in seconds

With batch traceability on, each product of each delivery is a lot with its batch code, use-by and papers. Trace a product finds every lot at your sites by name or code, back to the delivery, who received it and the readings, and forward to what happened to it and any recall.

Free food recall log

Tips for success

Run the test on a different product each time, and sometimes on a product with no batch code on the paperwork
Have someone other than the head chef run it, so you test the records and not one person's memory
Keep supplier contact details, including out-of-hours numbers, where the person running a recall can find them
In Paddl, Trace a product finds every lot of a product or batch code at your sites with its delivery, who received it, its papers and what happened to it, and the lots export as a CSV for the record

Common mistakes to avoid

Only testing the paperwork
A mock recall should end at the shelf. Records that say you have six packs are only half the answer; somebody has to find them.
Picking an easy product
Choose something that comes often, from a busy supplier, in several batches. That is where records fall apart.
Not recording the result
Write down the time taken and the gaps found. Without it, nobody can show the test happened or that the gaps were fixed.

Frequently asked questions

How often should a restaurant do a mock recall?

There is no legal frequency for restaurants. Once a year is a sensible minimum, and again after any change to how deliveries are recorded. Certified manufacturers usually have to do it at least yearly.

How long should a mock recall take?

Four hours is a common target for finding all affected stock. A kitchen that records batch codes at delivery can usually do it in minutes.

Do I need batch codes for a mock recall?

Not by law. The law asks you to know the supplier, the product and the date. But a recall names batch codes, so recording them at delivery lets you find the exact stock instead of everything of that name.

Need hands-on help with this?

Our hospitality consultants work alongside your team to implement food safety systems, prepare for inspections, and improve compliance.

Explore compliance consulting

Ready to simplify compliance?

Paddl automates the processes described in this guide. Digital records, automatic alerts, and complete audit trails for your hospitality business.

Full access to all features · Dedicated onboarding support · Cancel anytime