A food mock recall is a controlled exercise that tests whether your plant can identify affected product, account for the quantities, contact the right people, and make the decisions a real recall would require.

The important distinction is that a traceability exercise tests the product records. A full mock recall tests the response around those records: escalation, product holds, communications, authority, disposition, and corrective action. A plant can complete the trace in time and still discover that nobody owns the next decision.

This guide explains what a complete mock recall should cover, how the requirements differ under BRCGS, SQF, FSSC 22000, and PrimusGFS, and how to test more than the spreadsheet.

Mock recall requirements at a glance

Program or requirement	Minimum testing frequency	Written time target	What to verify
BRCGS Food Safety Issue 9	Traceability: at least annually; incident-management and recall procedures: at least annually	Traceability should be achievable within 4 hours	Forward and backward traceability, document links, mass balance, recall procedure, and timings of key activities
SQF	Product traceability and the full withdrawal-and-recall system are tested at least annually	No universal four-hour limit in the code	Incoming materials, finished product, all recall-program components, records, and corrective actions
FSSC 22000	Traceability is tested at least annually; emergency preparedness and withdrawal/recall arrangements must also be tested	No universal scheme-wide time limit	Forward and backward traceability, mass balance where applicable, communications, and effectiveness of the response
PrimusGFS	At least every 6 months, with a short-season exception in applicable guidance	Guidance uses a 2-hour completion target	One step forward, one step back, quantity located, primary packaging in one annual exercise where applicable, and lessons learned
FSMA 204	Not an internal mock-recall schedule	Records must be provided to FDA within 24 hours after a qualifying request once requirements apply	Key data elements for critical tracking events in an electronic sortable spreadsheet
Customer requirements	Defined by the agreement	May be stricter than the certification scheme	Customer notification, stop-sale or hold confirmation, data format, and response timing

Always verify the edition, module, product scope, customer agreement, and local regulatory requirements that apply to your site. The table is a practical comparison, not a substitute for the standards themselves.

What should a mock recall include?

A defensible exercise should test four connected parts.

1. Backward traceability

Start with a finished-product lot and identify what went into it. The trace should include:

• Ingredient and raw-material lots
• Primary packaging and printed-label lots
• Rework or carryover product
• Suppliers and receiving records
• Production line, date, shift, and run records

Packaging is part of the trace. A plant that can identify every ingredient but cannot show which printed film or label was used may still be unable to define the affected scope.

2. Forward traceability

Start with an ingredient, packaging, or finished-product lot and determine every place it went. The trace should identify:

• Every production run that used the selected material
• Every finished-product lot created from those runs
• Product still in raw-material, work-in-process, finished-goods, or hold inventory
• Shipments, customers, distribution locations, and in-transit product
• Rework streams that may have carried the material into later runs

The purpose is not only to find one shipment. It is to define the complete exposure.

3. Mass balance

Mass balance reconciles the quantity received or produced against what was used, shipped, scrapped, reworked, returned, or remains on site.

A simple material mass balance is:

Quantity received = quantity used + quantity scrapped + quantity remaining + documented variance

A finished-product reconciliation is similar:

Quantity produced = quantity shipped + quantity on hand + quantity destroyed, reworked, sampled, or otherwise dispositioned

Traceability standards do not assume every process will reconcile to exactly 100 percent. Moisture loss, line waste, sampling, giveaway, yield variation, and measurement tolerances can create legitimate differences. What matters is that the plant can quantify and explain the variance with evidence. An unexplained gap is a traceability failure even when the correct lot numbers were found.

4. The recall response

The full mock recall should continue after the trace is complete. Test the decisions and communications that a real event would force:

• Who activates the recall or incident-management team?
• Who can stop production or place product on hold?
• How is the hold protected across shift changes?
• Who defines the affected-product perimeter?
• Who contacts regulators, customers, the certification body, insurers, and leadership?
• Who approves release, destruction, return, or rework?
• Which records capture the basis for each decision?
• What happens if the primary decision-maker is unavailable?

This is where a mock recall becomes more than a records exercise.

How long should a mock recall take?

There is no single food-industry time limit that applies to every plant.

BRCGS: four hours for traceability

BRCGS Food Safety Issue 9 states that traceability should be achievable within four hours. Its traceability requirements sit separately from the annual test of the broader incident-management procedures, including product recall and withdrawal.

That distinction matters. Completing the trace in four hours does not prove that the plant can manage the complete recall in four hours. The trace provides the affected-product list; the team still has to decide what to hold, what to communicate, and what happens next.

SQF: annual testing, no universal four-hour rule

The current SQF Food Safety Code for Food Manufacturing requires the product trace system and the withdrawal-and-recall system to be tested at least annually. The full recall test must include all components of the recall program.

SQF does not impose a universal four-hour traceability limit. Your documented procedure, customer commitments, and risk profile determine the internal target against which the exercise should be evaluated.

FSSC 22000: annual verification without a universal clock

FSSC 22000 requires organizations to verify the effectiveness of traceability and to test emergency and withdrawal/recall arrangements. The scheme does not establish one universal time target for every certified site.

The organization should define a realistic target that reflects its products, processes, distribution network, customer requirements, and regulatory exposure, then retain evidence that the target was met or corrected when it was not.

PrimusGFS: every six months and a two-hour target

PrimusGFS guidance requires recall procedures, including traceback, to be tested at least every six months, with an exception for qualifying short-season operations. The guidance uses a two-hour completion target and expects the selected product to be located and accounted for.

For produce operations, this makes the exercise both more frequent and more tightly timed than many teams assume.

FSMA 204: a 24-hour regulatory records deadline

The FDA Food Traceability Rule is not a mock-recall standard. It establishes additional recordkeeping requirements for foods on the Food Traceability List and requires covered records to be provided to FDA within 24 hours of a qualifying request, in an electronic sortable spreadsheet.

As of July 2026, FDA has proposed moving the compliance date to July 20, 2028, and Congress has directed FDA not to enforce the rule before that date.

The practical lesson is still immediate: records that technically exist but take a day to assemble are not recall-ready.

How to conduct a mock recall step by step

Step 1: Define the objective and scenario

Choose whether the exercise will begin with a finished-product complaint, a positive environmental or product result, a supplier notification, an allergen or labeling error, foreign material, or another credible hazard.

State the assumed facts clearly. Do not make the scenario so vague that each participant invents a different event.

Step 2: Select a difficult lot without warning the records team

Use a lot that crosses products, shifts, lines, customers, or rework streams. The person selecting the lot should not be the same person who maintains the traceability records.

A deliberately easy lot confirms that the easiest path works. It does not test the system.

Step 3: Start the clock and maintain an activity log

Record:

• Exercise start time
• Scenario and selected lot
• Participants and roles
• Time each major activity begins and ends
• Systems, reports, and documents used
• Conflicting or missing information
• Time the trace and complete exercise finish

The activity log shows where time was spent and which handoffs failed.

Step 4: Run backward and forward traces

Trace ingredients, packaging, rework, finished product, inventory, shipments, and customers. Keep the supporting records, not only the final lot list. The result should show the links between each record.

Step 5: Complete and explain the mass balance

Reconcile the selected quantities. Document normal process losses and investigate unexplained differences. Do not force the numbers to match by inserting an unsupported adjustment.

Step 6: Simulate containment and decision-making

Test the operational response:

• Stop or continue production
• Block affected inventory electronically and physically
• Define adjacent runs or shared equipment that may also be affected
• Protect the hold through shift change
• Confirm alternate decision-makers and out-of-hours contacts
• Draft internal, customer, regulatory, and certification-body communications
• Determine how product would be recovered and dispositioned

Do not send a real external recall notification during a drill unless the exercise has been specifically coordinated to prevent confusion.

Step 7: Document findings without softening them

Record what failed, not only what completed. Useful findings include:

• A packaging lot could not be tied to the finished product
• Rework extended the affected scope beyond the first lot list
• Two systems reported different quantities
• A customer contact list was outdated
• The second shift could not see the hold
• The person authorized to stop production was unavailable
• The reason behind a previous release decision could not be found

A mock recall with no findings may indicate that the test was too narrow.

Step 8: Assign corrective actions and verify effectiveness

Each finding needs an owner, due date, corrective action, and effectiveness check. Repeat the failed portion before the next annual or semiannual exercise when the risk warrants it.

A recurring finding is evidence that the corrective-action system did not work.

Mock recall checklist

Use this checklist to review whether the exercise tested the full response.

Preparation

• Current recall and withdrawal procedure
• Named recall team and alternates
• Current customer, supplier, regulator, certification-body, insurer, and leadership contacts
• Defined time targets by scheme and customer
• Credible scenario and independently selected lot

Traceability

• Backward trace to ingredients, packaging, rework, and suppliers
• Forward trace to all affected finished lots and customers
• Inventory in production, storage, hold, transit, and external warehouses
• Supporting documents and system links retained
• Mass balance completed and variance explained

Response

• Authority to stop production tested
• Physical and electronic holds simulated
• Shift-change communication tested
• Affected-product perimeter documented
• External communications drafted and reviewed
• Product recovery and disposition process tested
• Key decisions and their basis recorded

Follow-up

• Completion time measured against the applicable target
• Gaps and lessons learned documented
• Corrective actions assigned
• Effectiveness checks scheduled and completed
• Recall plan and contact lists updated

Test your plant's recall readiness

Knowing the requirements is different from knowing whether your current process would work under pressure. Answer these ten questions based on how your plant operates today, not how the recall plan says it should operate.

Why plants pass the trace and still fail recall readiness

The traceability system answers where the product came from and where it went. A real recall also demands answers that usually live outside the traceability record:

• Why was the lot released?
• Why was the hold boundary drawn around these runs but not the adjacent ones?
• Who decided that the previous sanitation cycle was sufficient?
• What did the plant do during the last similar event, and did it work?
• Who owns the next decision on the current shift?

Those answers are often spread across an ERP, LIMS, quality forms, email, group messages, shift notes, and individual memory. This is the same institutional knowledge problem found throughout manufacturing, compressed into a high-pressure event.

A mock recall that ends when the spreadsheet is complete tests the product trail but leaves the decision trail untouched. The first trail determines what must be recovered. The second determines whether the plant responds consistently and avoids repeating the same failure.

For a detailed view of how those decisions unfold during an actual event, see the food recall process hour by hour.