Setting Up a Recall Team and Responsibilities

A recall team is a small, pre-named group with clearly assigned roles that activates the moment a food safety problem is identified. Before an incident, decide who coordinates the recall, who contacts your regulator and customers, who handles records and traceability, and who manages media and staff. Assigning these jobs in advance means no one hesitates, decisions happen fast, and affected product is located and withdrawn quickly. Key takeaways: Name your recall team before you ever need it — a recall is not the time to work out who does what.. Assign a single recall coordinator with the authority to make decisions and release product-hold instructions immediately.. Cover four core functions: coordination, regulator and customer notification, records and traceability, and communications with staff and media.. Keep a current contact list, including your local regulator or council, key suppliers, and distributors, and review it regularly.. Document roles in a written recall plan, test it, and make sure every team member knows their job and has a named backup.. Why a named recall team matters A food recall moves fast. Once a hazard is identified — a pathogen, an undeclared allergen, foreign matter, or a labelling error — every hour that product stays on shelves or in customers' hands increases the risk to public health and to your business. The single biggest cause of a slow, disorganised recall is confusion over who is responsible for what. A named recall team removes that confusion. Instead of scrambling to work out who calls the regulator or who pulls the distribution records, each person already knows their job and has the authority to act. This is a core part of the recall procedures expected under the Food Standards Code, which requires food businesses to be able to recall unsafe food. Think of the team as a standing capability, not a document that sits in a drawer. The people, their roles, and their contact details need to be current, understood, and rehearsed so activation is automatic rather than improvised. Speed: affected product is located and withdrawn before more of it is consumed.. Clarity: no duplicated effort and no critical task left undone.. Accountability: one person owns each decision and each communication.. Confidence: staff and customers see a controlled, professional response.. The core roles to assign Most recall teams are built around four functions. In a small business one person may hold several of these roles, and that is fine — what matters is that each function is explicitly assigned and someone owns it. In a larger operation each role may be a separate person with a named backup. The key is to write the roles down against real names and make sure each person understands the scope of their authority. A role no one has read is a role no one will perform under pressure. Recall coordinator: leads the response, makes the decision to recall, authorises product holds, and keeps the team on track. This person needs enough seniority to act without waiting for further sign-off.. Regulatory and customer liaison: notifies your local regulator or council and the relevant food authority, and contacts affected customers, distributors, and retailers. For consumer-level recalls, this role works with authorities on public notification.. Records and traceability officer: retrieves batch, production, supplier, and distribution records to identify exactly what product is affected and where it has gone — the one-step-back, one-step-forward trace.. Communications lead: manages internal staff briefings, handles media and public enquiries, and ensures a single consistent message. In smaller businesses the coordinator often covers this.. The recall coordinator: the decision-maker The coordinator is the hub of the whole response. This person receives the initial report of a problem, gathers enough information to assess it, and makes the call on whether to recall or withdraw product. That decision cannot wait for a committee, so the coordinator must have the delegated authority to act. Once a recall is triggered, the coordinator directs the other roles: instructing the traceability officer to pull records, the liaison to notify the regulator, and the communications lead to brief staff. They also keep a running log of decisions and actions, which becomes essential evidence that the recall was handled properly. Choose someone calm, organised, and available. Because incidents do not respect business hours, name a deputy coordinator who can step in if the primary person is unreachable, and make sure both have after-hours contact details for the whole team. Notification, traceability, and communications roles The regulatory and customer liaison is the team's outward voice to officialdom and trade customers. They need to know who to call — reporting and notification requirements vary by state and territory, so confirm the correct pathway with your local council or regulator in advance. For a consumer-level recall, national coordination generally runs through the food regulator system, and having the right contacts ready saves critical time. The records and traceability officer answers the question that drives everything else: what is affected, and where is it? They locate production and batch records, supplier lot numbers, and distribution lists so the recall targets only the product it needs to and captures all of it. Good day-to-day record-keeping is what makes this role possible under pressure. The communications lead protects trust. Staff need clear instructions so they give customers consistent, accurate information, and any external statement needs to be truthful and coordinated with the authorities. A single spokesperson and an agreed holding message prevent mixed messages that can make an incident worse. Build and maintain your contact list A recall plan is only as good as the phone numbers in it. Alongside the team roster, keep a current contact list covering everyone you may need to reach quickly. Store it somewhere accessible outside your main systems, in case those systems are unavailable during an incident. Stale contacts are a common failure point. People change jobs, suppliers change numbers, and after-hours lines get missed. Review the list on a set schedule and after any staffing change, and confirm the entries are still correct. Every recall team member and their named backup, with after-hours numbers.. Your local council or state and territory food regulator.. Key suppliers and the contacts who can confirm batch and lot details.. Distributors, wholesalers, and major retail customers who received product.. Any third-party logistics or storage providers holding your stock.. Document, train, and test the plan Roles that live only in someone's head disappear the moment that person is on leave. Capture the team structure, responsibilities, decision authority, and contact list in a written recall plan, and make it part of your food safety program under Standard 3.2.2 and 3.2.2A where they apply to your business. Training turns the document into a capability. Walk each team member through their role, the triggers for activating the plan, and how the roles hand off to one another. New staff in relevant positions should be briefed as part of induction, and refreshers keep the knowledge fresh. Finally, test the plan with a mock recall. A desktop exercise — tracing a hypothetical affected batch from supplier to customer against the clock — reveals gaps in records, contacts, and understanding while the stakes are low. Update the plan after every test and every real incident so it keeps improving. Checklist: Recall coordinator named, with delegated authority to trigger a recall. A named backup for every role, with after-hours contact details. Regulatory and customer liaison knows the correct notification pathway. Records and traceability officer can trace one step back and one step forward. Communications lead and a single agreed spokesperson identified. Current contact list for team, regulator/council, suppliers, distributors, and customers. Roles documented in the written recall plan under your food safety program. Team trained and the plan tested with a mock recall in the last review cycle. Common mistakes: Leaving roles unassigned or assuming 'everyone will pitch in' on the day.. Giving the coordinator no real authority, so decisions stall waiting for sign-off.. Naming a team but no backups, so one person's absence stops the response.. Letting the contact list go stale — wrong numbers and departed staff.. Storing the plan only in a system that may be unavailable during an incident.. Writing the plan but never training staff or testing it with a mock recall..