Mock Recalls in Canada: How to Run an SFCR Recall Simulation

On 17 July 2026, the Canadian Food Inspection Agency updated a Class 1 recall (recall RA-82354) that grew to cover dozens of processed meat products because of possible Listeria monocytogenes contamination. No illnesses were reported, yet the recall still swept product off shelves and out of online orders across a province. Recalls like this are the moment your traceability, your records and your team are tested in public. The businesses that come through them well are almost always the ones that practised first.

A mock recall, also called a recall simulation, is that practice. It is a controlled exercise that walks your team through a realistic recall scenario so you can prove your recall procedure actually works before you ever need it. In Canada, testing your recall procedure is not optional for most licence holders under the Safe Food for Canadians Regulations. This guide explains what a mock recall is, what the regulations require, how to run one step by step, how to measure whether it passed, and the mistakes that quietly sink otherwise strong programs.

Executive summary

A mock recall is a simulated product recall used to verify that your traceability and recall procedures can remove an affected lot from the supply chain quickly and completely. Under the Safe Food for Canadians Regulations (SFCR), a licence holder must have a written recall procedure that enables the effective recall of a food, must test that procedure, and must keep the results for two years. The exercise mirrors the CFIA's own twelve-step recall process: assemble the team, identify affected product, build the distribution list, notify customers, and reconcile quantities. Success is measured, not assumed, using a reconciliation percentage and the time taken to reach each milestone.

The practical takeaway: schedule a mock recall at least once a year, base it on a plausible scenario, run it without warning your team, aim to trace one step back and one step forward within hours rather than days, and treat every gap as a corrective and preventive action (CAPA). Do this and a real recall becomes a procedure you have rehearsed, not a crisis you are improvising.

What is a mock recall?

What it is: A mock recall is a planned exercise that simulates a genuine recall from start to finish. You pick a product and lot, then work through the same actions you would take in a real event: identifying every affected unit, locating where it went, contacting the customers who received it, and accounting for all of it.

Why it matters: A recall procedure that has never been tested is an assumption, not a control. Mock recalls expose the weak points, a supplier lot code that was never recorded, a customer contact list that is out of date, a distribution record that lives only in one person's inbox, while the stakes are still zero. They also demonstrate to a CFIA inspector that your preventive control plan is real and functioning.

What to do: Treat the mock recall as a routine part of your quality system, not a once-and-done box tick. Run it on a schedule, vary the scenario each time, involve the real people who would act in an emergency, and document both the result and the fixes. The goal is a shorter, cleaner trace on every subsequent run.

Recall readiness is not unique to food. Cannabis licence holders, natural health product sites and drug establishments all carry recall obligations, and the discipline is the same. Our guide on how to avoid product recalls looks at the upstream controls that stop a recall from happening in the first place.

What the SFCR requires

What it is: The Safe Food for Canadians Regulations set out the recall obligations for licence holders. According to the CFIA's Recall procedure guide for food businesses, the recall procedure requirements sit in subsection 84(1) and section 85 of the SFCR. The written preventive control plan requirements sit in sections 86 to 89, and the traceability requirements sit in Part 5.

Why it matters: These sections are what a CFIA inspector checks against. A written recall procedure that enables the effective recall of a food is the standard, and a plan you cannot demonstrate is treated as a plan you do not have. Testing the procedure through a simulation is how you show it works, and the results must be documented and kept for two years after the simulation is completed.

What to do: Map your program to each requirement below, then confirm you can produce the record that proves it. Traceability is the foundation: if you cannot trace one step back to your immediate supplier and one step forward to your immediate customer, the recall procedure built on top of it cannot succeed.

SFCR area	Where it sits	What you must be able to show
Recall procedure	Subsection 84(1) and section 85	A written procedure that enables the effective recall of a food
Preventive control plan	Sections 86 to 89	A written PCP that identifies hazards and controls, with exceptions for some small businesses
Recall simulation	Testing the recall procedure	Documented results of the simulation, kept for two years
Traceability	Part 5	One step back to your supplier, one step forward to your customer, with records kept two years

How the CFIA classifies and handles a real recall

What it is: When a hazard is found in a food already in distribution, the CFIA runs a food safety investigation and decides whether a recall is needed. The agency explains how it decides to recall a food product in a five-step process, and it assigns each recall a class based on the health risk. Understanding the classes helps you build realistic mock scenarios.

Why it matters: The class drives the urgency, the level of CFIA oversight, and whether a public warning is issued. A Class 1 recall, like the Listeria example above, carries the highest risk and the tightest timelines. A mock recall built around a Class 1 scenario stress-tests your program the way a real emergency would.

What to do: Most recalls in Canada are voluntary, conducted by the business with CFIA oversight. If a company cannot or will not recall an unsafe food, the Minister of Health can order a mandatory recall. Build your procedure so a voluntary recall is fast and complete, because that is what keeps a mandatory order off the table.

Recall class	Level of risk	Typical example
Class 1	High: reasonable probability that eating the food will cause serious illness or death	Listeria, undeclared priority allergen, botulism risk
Class 2	Moderate: may cause short-term or non-life-threatening health problems	Some chemical or microbial contamination, certain labelling errors
Class 3	Low: unlikely to cause any adverse health effects, or a non-compliance with no health risk	Minor labelling or net-quantity errors

How to run a mock recall, step by step

What to do: A mock recall follows the same twelve steps the CFIA sets out for a real recall. You do not physically ship product back, but you generate every record, contact list and reconciliation you would produce in a live event. The sequence below adapts the CFIA's recall procedure into a simulation you can run in an afternoon.

1. Assemble the recall team. Bring together the real people who would act: quality assurance, operations, the recall coordinator, and whoever handles customer and CFIA communication. Confirm each role and each after-hours contact is current.

2. Set the trigger and notify the coordinator. State the scenario clearly, for example a supplier reports a contaminated ingredient lot, and note the point at which you would notify your CFIA recall coordinator in a real event.

3. Identify all affected product. Trace the affected ingredient or lot to every finished product, size, brand and code it touched. This is where poor ingredient-lot linkage shows up fast.

4. Hold and segregate. Determine how much affected product is still under your control, where it is, and confirm it would be quarantined so it cannot ship.

5. Build the distribution list. Produce a lot-specific list of every customer who received the product, with contact details, customer type and the quantity shipped to each. Flag customers serving vulnerable populations such as hospitals, care homes and daycares.

6. Prepare and issue the notice of recall. Draft the customer notice using your template. Time how long it takes to produce an accurate, complete notice ready to send.

7. Reconcile quantities. Add the product still in your control to the amount shipped to each customer. That total should equal the quantity produced for the lot. Any gap is a traceability failure to investigate.

8. Review, document and close out. Hold a post-exercise review with the team, record what worked and what did not, and open a CAPA for each gap. File the simulation record and keep it for two years.

Building a realistic scenario

The value of a mock recall depends on the scenario. Base it on something that could genuinely happen to your operation: an undeclared allergen from a supplier ingredient change, a positive environmental swab for Listeria in a ready-to-eat line, foreign material from a maintenance event, or a mislabelled lot. Rotate the trigger each year so you are not rehearsing the same easy path. To make the test honest, do not warn the team in advance and, where safe to do so, schedule it during a busy or inconvenient period. A recall that only works when everyone is ready and the plant is quiet is not a recall procedure you can rely on.

Measuring effectiveness

A mock recall only counts if you measure it. Two numbers matter most. The first is the reconciliation percentage: the quantity you can account for, whether held, shipped or confirmed with customers, divided by the quantity produced for the lot. Mature programs target close to 100 percent, and many quality systems set a pass threshold at 99 percent or better. The second is time to milestone: how long it took to identify affected product, produce a complete distribution list, and have a notice of recall ready to send. Record the actual times, compare them to your target, and track the trend across simulations. If reconciliation drifts below your threshold or the trace takes longer than a real Class 1 recall would allow, you have found your next corrective action.

Mock recall compliance checklist

Use this checklist to confirm your recall simulation is complete and defensible:

A written recall procedure exists that enables the effective recall of a food (SFCR subsection 84(1) and section 85).
The recall team, roles and after-hours contacts are documented and current.
Traceability records let you trace one step back and one step forward (SFCR Part 5).
Ingredient and packaging lot codes are linked to finished-product lot codes.
A lot-specific distribution list can be produced quickly, flagging vulnerable-population customers.
Notice-of-recall and CFIA-notification templates are ready to use.
Reconciliation reaches your pass threshold and timings meet your targets.
The simulation is documented, gaps are captured as CAPAs, and the record is kept for two years.

Common mistakes

Rehearsing the easy path. Running the same simple scenario each year, with advance notice, proves nothing about real readiness.
Weak ingredient-to-product linkage. If you cannot connect a supplier lot to the finished products it entered, you cannot scope the recall.
Stale contact lists. Customer and CFIA contact details that were never updated cost hours in a live event.
Not measuring. A simulation with no reconciliation percentage and no timings is a story, not a test.
No CAPA follow-through. Finding a gap and not fixing it turns your own record into evidence against you at the next inspection.
Discarding records early. Simulation records must be kept for two years; missing records are a finding even when the exercise went well.

Frequently asked questions

How often should we conduct a mock recall?

CFIA preventive control expectations and common industry guidance point to testing your recall procedure at least once every 12 months. Businesses with higher-risk products, complex distribution, or recent system changes should test more often. Regardless of frequency, document each simulation and keep the record for two years.

Is a recall simulation legally required in Canada?

Under the SFCR, licence holders must have a written recall procedure that enables the effective recall of a food (subsection 84(1) and section 85). Testing that procedure through a simulation, and keeping the documented results for two years, is how operators demonstrate the procedure works. A procedure you cannot show to be effective is treated as inadequate.

What is a good reconciliation target for a mock recall?

Mature programs aim to account for close to 100 percent of the lot, and many quality systems set a pass threshold at 99 percent or better. The exact figure matters less than being able to explain any shortfall and fix the traceability gap that caused it.

What is the difference between a mock recall and a traceability exercise?

A traceability exercise tests only whether you can trace product one step back and one step forward. A mock recall includes traceability but goes further: it tests the full recall procedure, including team activation, distribution lists, customer notification, reconciliation and post-recall review. Traceability is a component of the larger simulation.

Do cannabis and natural health product businesses need mock recalls too?

Yes. Cannabis licence holders, natural health product sites and drug establishments all carry recall obligations under their respective frameworks. The mechanics differ by sector, but the discipline of testing your procedure, measuring effectiveness and closing gaps is the same across regulated industries.

Who should lead the mock recall?

The person responsible for recalls in your business, often the quality assurance lead or recall coordinator, should run it, with the full recall team participating. Involving senior decision-makers and the staff who would actually communicate with customers and the CFIA makes the exercise realistic and surfaces the gaps that matter.

How MFLRC can help

MF License & Regulatory Consultants helps food, cannabis, natural health product and pharmaceutical businesses build recall programs that hold up under real pressure. We design and test recall procedures, run independent mock recalls and audits, and strengthen the traceability and quality systems that a recall depends on.

Our support typically includes gap assessments and internal audits, SOP development for recall and traceability, mock-recall facilitation with effectiveness scoring, CAPA design, and inspection-readiness reviews. For companies moving product across borders, we also advise on regulatory affairs and import and export obligations that shape recall scope.

If you are not sure your recall procedure would pass a surprise test, that is exactly the time to run one. We can facilitate your next mock recall, score it against CFIA expectations, and give you a prioritized action plan.

Book a Recall Readiness Consultation

Conclusion

A recall will always be stressful, but it does not have to be chaotic. The SFCR asks you to have a recall procedure that works, to test it, and to keep the proof. A well-run mock recall turns that requirement into a genuine capability: a team that knows its roles, traceability that closes without gaps, and metrics that improve every year. Run one before the CFIA gives you a reason to, and the next real recall becomes a procedure you have already rehearsed.