How do I create a mock recall report?

01Direct answer

A mock recall report proves the trace worked.

To create a mock recall report, pick a finished product lot, define the scenario, trace ingredients backward, trace customers forward, calculate how much product is accounted for, record the time to complete, list gaps, assign corrective actions, and decide whether a retest is needed. The report should prove the recall plan works, not just that the team met for a drill.

FDA recall procedures and industry audit programs focus on fast, accurate product identification, notification, and disposition. HACCPlan connects mock recall evidence to lot records, supplier lots, shipping records, recall contacts, and corrective actions.

02Report fields

The report sections to include.

1. 01

   Scenario

   Product, lot, date range, reason for recall test, team members, and start time.

2. 02

   Backward trace

   Supplier lots, receiving records, CoAs, ingredient use, and production record.

3. 03

   Forward trace

   Customers, distributors, shipments, quantities, dates, and returned or destroyed product.

4. 04

   Reconciliation

   Quantity produced, quantity shipped, quantity on hand, quantity accounted for, and percent recovered.

5. 05

   Gaps and actions

   Missing records, slow steps, contact problems, corrective actions, owners, due dates, and retest plan.

Use the interactive version

Create a mock recall report in HACCPlan

Run lot tracing, record reconciliation, document gaps, assign corrective actions, and keep mock recall evidence beside the recall plan.

Use the recall plan generator first, then save mock recall reports in HACCPlan.

03Why it breaks

Mock recalls fail when they only test the phone list.

A contact list matters, but it is not the whole recall system. The hard part is finding records quickly and accounting for product accurately. If production records, receiving lots, and shipping records are disconnected, the mock recall becomes a manual search.

The report should show the time and the math. If 100 cases were produced, where are they now?

It should also show the communication path. If customers, distributors, stores, or internal teams would need to be notified, the mock recall should test whether those contacts are current and reachable.

04What HACCPlan does

Connect the report to live lot records.

HACCPlan keeps the mock recall report tied to traceability and corrective actions. That means the test can prove both the data and the response process.

1. 01

   Lot selection

   Choose a finished lot and pull linked ingredient, production, and shipping records.

2. 02

   Reconciliation

   Account for produced, shipped, on-hand, returned, destroyed, or missing product.

3. 03

   Gap tracking

   Turn weak records, slow steps, and contact issues into corrective actions.

4. 04

   Retest evidence

   Save the follow-up test if the first mock recall did not meet the goal.

05Proof

Show what improved after the test.

The best mock recall reports include the correction, not just the problem. If a customer list was stale, show the updated list. If supplier lots were missing, show the receiving-log change. If reconciliation was slow, show the new workflow and retest result.

That is what makes the mock recall useful for buyers and inspectors. It shows the business tested the system, found weak points, and improved the system before a real event.

06Timing

Record the clock.

Traceability requests can come with short deadlines. Your mock recall report should show when the test started, when records were pulled, when reconciliation was complete, and when gaps were assigned. Time is part of the proof.

07Next step

Test the lot most likely to create confusion.

Pick a product with multiple ingredients, multiple customers, or a recent supplier change. That test will expose record gaps faster than a simple lot with one customer.

Run the test

Build the mock recall evidence packet

Use HACCPlan to connect recall plans, lot records, reconciliation, corrective actions, contact lists, and retest evidence.

Useful for inspections, buyer audits, and internal recall readiness.

08Related

Pair the report with recall planning.

Use the recall plan generator, recall software, and lot-code tracking workflow.

Andrew Langevin·CFIA-licensed facility, Brantford ON· Published 2026-06-05· 8 min read· Wikidata Q139112497