Learn how to write a food recall plan that meets the Food Standards Code: recall team, traceability, decision triggers, notifications and mock-recall testing.
A food recall plan is a written procedure that lets you quickly remove unsafe or non-compliant food from the supply chain. Under the Food Standards Code, food businesses that wholesale, manufacture or import food must have a documented recall system. A good plan names a recall coordinator, sets out how you trace and contact affected customers, and defines who you notify and how fast you act. Key takeaways: A documented recall plan is a Food Standards Code requirement for businesses that manufacture, wholesale or import food, and it must be ready to use before you ever need it.. The plan should name a recall coordinator and team, with contact details and clear authority to make a recall decision quickly.. Traceability is the backbone: you need one-step-back and one-step-forward records so you can identify affected batches and where they went.. Test the plan with a mock recall at least annually and after any major change to products, suppliers or systems.. Requirements and reporting contacts vary by state and territory, so confirm the notification steps with your local food regulator.. Why a written recall plan matters A recall is not the moment to work out who does what. When a supplier flags a contaminated ingredient, a customer reports illness, or a mislabelled allergen is discovered, you may have only hours to identify affected stock and stop it reaching consumers. A documented plan turns that pressure into a checklist you can follow. Under the Australia New Zealand Food Standards Code, food businesses that engage in wholesale supply, manufacture or importation are required to have a recall system and to be able to recall unsafe food. Standard 3.2.2 (Food Safety Practices and General Requirements) sets the recall obligation, and Standard 3.2.2A adds food safety management tools for certain businesses. Exact obligations vary by business type and location, so confirm what applies to you with your local council or regulator. Beyond compliance, a fast, well-run recall protects the people who eat your food and the reputation you have built. Regulators expect you to act decisively, and a clear plan is the evidence that you can. Build your recall team and define roles Every plan starts with people. Name a recall coordinator who has the authority to trigger a recall without waiting for a committee, plus a deputy in case the coordinator is unavailable. List their names, positions and direct contact numbers at the front of the plan so nobody has to search for them mid-crisis. Around the coordinator, define a small team and what each person owns. Typical roles include operations (locating and quarantining stock), quality or technical (assessing the hazard), communications (customer and media contact), and a records lead (pulling distribution data). In a small business one person may wear several hats, and that is fine as long as the plan says so. Recall coordinator with authority to act, plus a named deputy. 24-hour contact details for every team member. A single decision-maker for go or no-go on a recall. Assigned owners for stock control, hazard assessment, records and communications. Get your traceability records in order You cannot recall what you cannot trace. The plan should describe exactly how you achieve one-step-back and one-step-forward traceability: records that link each incoming ingredient to your suppliers, and each finished product batch to the customers you supplied. At a minimum you need batch or lot coding on finished product, records of raw material lots used in each batch, and distribution records showing who received which batch and how much. Store these so they can be retrieved quickly, including outside business hours. Keep records for the shelf life of the product plus a sensible margin. List where each record lives and who can access it. If your traceability depends on a supplier's paperwork or a third-party logistics provider, note how you obtain that information fast, because a gap in the chain is where a recall stalls. Set clear triggers and a decision process The plan should spell out what prompts you to consider a recall. Common triggers include a positive test for a pathogen or contaminant, an undeclared or mislabelled allergen, foreign matter, a supplier or regulator alert, or a credible consumer complaint about illness or injury. Define how the team assesses the hazard and decides. A short risk assessment should weigh the likelihood and severity of harm and how widely the product has been distributed. Undeclared allergens and microbial contamination generally point to urgent action because of the potential for serious harm. Distinguish a consumer-level recall (product has reached the public and must be retrieved from shops and homes) from a trade-level recall or withdrawal (product is still within the supply chain, or is removed for a quality issue that is not a safety risk). The plan should make clear who signs off on each and how quickly. Plan your notifications and communications When you decide to recall, several audiences need to hear from you quickly, and the plan should hold ready-to-use templates and contact lists for each. Internally, brief your team and freeze the affected stock. Externally, you will typically need to notify the relevant food regulator, your affected customers and distributors, and where product has reached the public, consumers. Reporting pathways and the lead agency differ across states and territories, and FSANZ coordinates recalls nationally through its recall protocol. Do not guess the contacts in a crisis: pre-fill the plan with the correct regulator details for your location and confirm them with your local food authority in advance. For consumer-level recalls, prepare draft recall notices, point-of-sale signage, and website and social media wording so they only need the specific product details filled in. Include how you handle media enquiries and customer refunds or replacements. Notify your food regulator using the correct state or territory pathway. Contact affected customers and distributors with batch details and instructions. For consumer recalls, issue notices, signage and online alerts. Have templates drafted in advance so you only add product-specific details. Document recovery, disposal and root-cause review A recall is not over when the notice goes out. The plan should describe how you retrieve or quarantine affected product, reconcile quantities (how much was made, distributed, recovered and unaccounted for), and dispose of or rework recovered stock so it cannot re-enter the food supply. Record every step as you go, including times, decisions and communications. This log demonstrates to regulators that the recall was effective and gives you the raw material for review. Once stock is controlled, run a root-cause investigation. Identify how the problem occurred, what corrective action prevents recurrence, and whether your food safety program, supplier controls or labelling need to change. Close the loop by updating procedures and, where relevant, your recall plan itself. Test the plan with mock recalls An untested plan is a guess. Run a mock recall at least once a year, and again after any significant change to products, suppliers, distribution or record systems. In a mock, pick a real batch and trace it forward to every customer and backward to every ingredient lot, timing how long the process takes. A useful mock measures whether you can account for the full quantity of a batch and reach affected customers within a target time. Note where information was slow or missing, then fix those gaps, whether that is tighter batch coding, better supplier records, or clearer contact lists. Keep the plan current. Review contact details, team roles and regulator pathways regularly, and store copies where the team can reach them even if your main systems are down. A recall plan is only as good as the day it was last verified. Checklist: Recall coordinator and deputy named with 24-hour contact details. Recall team roles and responsibilities documented. One-step-back and one-step-forward traceability records available quickly. Finished product carries batch or lot codes. Recall triggers and hazard assessment process defined. Consumer vs trade recall and withdrawal criteria set out. Regulator, customer and distributor contact lists pre-filled for your location. Draft recall notices, signage and online alerts ready to use. Stock recovery, reconciliation and safe disposal steps documented. Root-cause review and corrective action process included. Mock recall scheduled at least annually. Plan stored where the team can access it out of hours. Common mistakes: Writing the plan but never testing it with a mock recall, so nobody knows how long a trace actually takes.. Relying on a single person with no named deputy, leaving the plan stranded if they are on leave or unreachable.. Weak batch coding or distribution records that make it impossible to isolate affected stock.. Leaving regulator and customer contact details to be found in the moment instead of pre-filling them.. Treating an undeclared allergen as a minor labelling slip rather than a potential consumer-level recall.. Failing to reconcile quantities, so recovered stock is not matched against what was produced and distributed.. Skipping the root-cause review, so the same failure recurs and triggers another recall..
Steps to write your food recall plan
Name a coordinator with authority to act, a deputy, and role owners for stock, hazard assessment, records and communications. Record 24-hour contact details at the front of the plan.
Document how you achieve one-step-back and one-step-forward traceability, including batch coding, raw material records and distribution lists, and note where each record is stored and who can retrieve it.
List the situations that prompt a recall, set out a short hazard risk assessment, and state who decides between a consumer recall, a trade recall or a withdrawal.
Pre-fill contacts for your food regulator, customers and distributors for your state or territory, and draft recall notices, signage and online wording ready to use.
Describe how you quarantine and reconcile stock, dispose of or rework recovered product safely, log every action, and run a root-cause investigation with corrective actions.
Test the plan at least annually and after major changes, measure trace time and quantity reconciliation, and update the plan wherever the exercise finds gaps.
Frequently asked questions
Is a food recall plan legally required in Australia?
Yes, for many businesses. Under the Food Standards Code, food businesses that manufacture, wholesale or import food are required to have a recall system and be able to recall unsafe food, with Standard 3.2.2 setting the obligation. Exact requirements depend on your business type and location, so confirm what applies to you with your local council or state or territory food regulator.
What is the difference between a recall and a withdrawal?
A recall removes food from the supply chain because it is unsafe or unsuitable, and a consumer-level recall retrieves it from shops and consumers. A withdrawal removes food for a reason that is not a safety risk, such as a minor quality or labelling issue, and usually happens within the trade before product reaches the public. Your plan should state who decides which applies.
How often should I test my recall plan?
Run a mock recall at least once a year, and again after any significant change to your products, suppliers, distribution or record systems. A mock recall traces a real batch forward and backward and times how long it takes to account for the full quantity and reach affected customers, revealing gaps you can fix before a genuine recall tests them for you.
Who do I notify when I recall a food product?
You typically notify your food regulator, your affected customers and distributors, and, for consumer-level recalls, the public. FSANZ coordinates food recalls nationally, but the reporting pathway and lead agency vary by state and territory. Pre-fill the correct contacts for your location in the plan and confirm them with your local food authority before you need them.
What records do I need for traceability?
You need one-step-back and one-step-forward traceability: records linking incoming ingredient lots to suppliers, batch or lot codes on finished product, records of which raw material lots went into each batch, and distribution records showing which customers received which batches. Store them so they can be retrieved quickly, including outside business hours, for the product's shelf life plus a margin.
Does an undeclared allergen require a recall?
Often yes. An undeclared or mislabelled allergen can cause serious harm to allergic consumers, so it commonly triggers a consumer-level recall if affected product has reached the public. Plain English Allergen Labelling under Standard 1.2.3 aims to make allergen declarations clearer. Assess each case for likelihood and severity of harm and how widely the product was distributed, and act urgently where risk is high.