How to Conduct a Mock Food Recall

To conduct a mock food recall in a small food business, you pick a product and batch, then trace it one step back to your supplier and one step forward to where it went, using your records to work out how much you received, used, sold and still hold. The exercise is timed, any gaps in traceability are noted, the quantities are reconciled, and corrective actions are raised for anything that did not add up. A mock recall proves your traceability works before you ever need it for real. Even small cafes and takeaways benefit from practising this. A real recall is stressful and fast-moving; rehearsing it calmly shows whether you could actually locate an affected product in time. This guide walks through how to run one. Why run a mock recall at all? Recalls happen regularly across Australia for reasons ranging from undeclared allergens to microbial contamination. The Food Standards Australia New Zealand (FSANZ) food recall statistics show that recalls are a routine part of the food system, and businesses of every size can be caught up in one when a supplier's ingredient is affected. If a supplier recalls a batch you received, you need to know instantly whether you have it, where it went and what to do. Traceability underpins all of this. The principle is simple: one step back to know where every ingredient came from, and one step forward to know where your product went. A mock recall tests whether your records actually deliver that in practice. Step one: choose a product and scenario Start by picking a realistic scenario. Choose an ingredient or menu item and imagine your supplier has notified you of a contamination or allergen issue with a specific batch or delivery date. Something you use often, like a dairy product, a sauce, or packaged smallgoods, makes a good test because it touches many dishes. Write down the trigger clearly: for example, "supplier advises batch received on a given delivery date may be contaminated." From that starting point, your job is to trace it in both directions and reconcile the numbers. Step two: trace one step back Tracing back means proving where the product came from. Find the supplier record: the invoice or delivery docket, the date received, the quantity, and any batch or lot code. This shows you can identify the exact source of the ingredient. If you cannot find which delivery a product came from, that is a traceability gap worth noting immediately. Good receiving records are the foundation here. Keeping delivery and receiving records that capture supplier, date, quantity and batch details means the one-step-back trace takes minutes rather than hours. Without them, a real recall becomes guesswork. Step three: trace one step forward Tracing forward means working out where the product went. In a small business this usually means which dishes it went into, which days it was served, and whether any was sold wholesale or is still in storage. Use your prep records, production notes and stock records to follow the trail from delivery to plate. For products with a shelf life, your waste and expiry records help show what was discarded and when. The aim is to account for the entire quantity you received: what was used, what was sold, what was wasted, and what remains on the shelf right now. Step four: time the exercise Timing matters because a real recall is urgent. Note when you start and when you can confidently say where the whole batch went. A business that can trace a product in a short, calm window is far better prepared than one that takes hours of digging. Record the elapsed time so you can measure improvement next time you run the drill. A simple mock recall record Step What to record Trigger Product, batch or delivery date, reason for the mock recall One step back Supplier, invoice or docket, date received, quantity, batch code One step forward Dishes made, dates served, any wholesale, quantity remaining Reconciliation Received versus used, sold, wasted and in stock Timing Start time, completion time, total elapsed Gaps and actions Missing records found and corrective actions raised Step five: reconcile the quantities Reconciliation is the heart of the exercise. Add up everything you can account for: the amount used in dishes, the amount sold, the amount wasted, and the amount still in stock. That total should roughly match the quantity you received. A large unexplained gap means product went somewhere your records cannot see, which is exactly the weakness a mock recall is designed to expose. Received quantity from the supplier docket. Used quantity from prep and production records. Sold quantity, including any wholesale. Wasted quantity from waste and expiry records. Remaining stock physically on hand. Step six: note the gaps and raise corrective actions Almost every first mock recall reveals something: a missing batch code, a delivery with no docket, or stock that cannot be fully traced. These gaps are the whole point. For each one, raise a corrective action describing what was missing and how you will fix it, such as recording batch codes at receiving or tightening your prep notes. Then run another drill later to confirm the gap is closed. Document the entire exercise so you can show an Environmental Health Officer (EHO) that you test your traceability, not just claim it works. The state health department, such as the Victorian health department , and your local council both expect food businesses to be able to trace product. You can find step-by-step templates in the FoodSafety HQ food safety guides . How often should a small business run a mock recall? Running a mock recall periodically, and after any major change to suppliers or menu, keeps your traceability sharp. Treat it like a fire drill: an occasional practice that feels unnecessary until the day something goes wrong, when it suddenly becomes the difference between a quick, controlled response and a scramble. Regular staff training and induction ensures more than one person can run the drill. Frequently asked questions What is the goal of a mock food recall? The goal is to test whether you can quickly trace an affected product one step back to its supplier and one step forward to where it went, reconcile the quantities, and identify any gaps in your records before a real recall ever happens. What does one step back, one step forward mean? One step back means being able to identify the supplier and batch of every ingredient you receive. One step forward means knowing where your product went, whether into dishes served, sold wholesale, wasted or still in stock. How long should a mock recall take? There is no fixed rule, but faster is better. Aim to trace and reconcile the product in a short, calm window. Record your time so you can improve with each drill and prove readiness to an inspector. Do small cafes really need to practise recalls? Yes. Even small venues can be affected when a supplier recalls an ingredient. Practising means you can act quickly and confidently, protecting your customers and demonstrating good management to regulators. FoodSafety HQ keeps your recall and traceability records connected, from receiving and batch codes to waste and corrective actions, so a mock recall or a real one is fast and fully documented. Explore the delivery and traceability feature or start a free trial on our pricing page to make your next drill effortless.