Mock Recall Playbook: From Days to Seconds

The mock recall is the only fire drill where the building actually burns someday. Here's how to run one, score one, and make the next one boring.

Written by George Munguia · Published Jul 19, 2026

Every certified food plant runs mock recalls because the schemes require it. Most treat it as a scheduled scramble: the quality team blocks a day, pulls binders, calls the warehouse, and assembles a trace that lands somewhere between four hours and three days. The exercise passes. The lesson, that a real 2 a.m. recall would look the same but with lawyers, gets filed with the binder.

Running the exercise honestly

Pick a lot nobody pre-staged, an ingredient received three weeks ago, or a finished lot mid-run. Start the clock. Require the team to produce: every batch the lot touched (one-up), every input in those batches (one-back), every customer shipment with quantities, and a mass balance, received versus used versus shipped versus on-hand, that reconciles. Stop the clock when evidence exists, not when someone says 'we found it.'

The three scores that matter

Time to scope: auditors' informal bar has fallen from 'same day' toward two-to-four hours; buyer expectations, shaped by FSMA 204's 24-hour records requirement, keep tightening (see our FSMA 204 guide).
Completeness: percent of the lot's quantity reconciled. 98% sounds fine until the missing 2% is a pallet in a customer's DC.
Evidence: can you hand over the records, batch documentation, shipping proof, or only assert them?

Why plants take days

The trace is a reconstruction: consumption lives on batch sheets in binders, receiving in a logbook, shipping in the ERP, and a human joins them under pressure. Every handwritten lot code that is ambiguous adds an hour. The scramble is the system working as designed, the design is just wrong.

Making the next one boring

The fix is upstream: capture the lot links as production runs, receiving, consumption, pack, so genealogy exists before any question does (mechanics in the genealogy guide). Then the mock recall is a query: scope in seconds, records attached, mass balance computed. Run the exercise anyway, it now tests the response process, holds, notifications, dispositions, instead of testing whether the plant can do archaeology under a stopwatch. Harmony deployments on dairy and bakery floors treat the sub-minute mock recall as a standard acceptance test of the trace layer.

Frequently Asked Questions

What is a mock recall?

A timed exercise proving the plant can identify everything a suspect lot touched, batches, inputs, customers, quantities reconciled, with records to show. GFSI schemes require them periodically; buyers increasingly ask for the results.

How fast should a mock recall be completed?

Certification schemes historically accepted same-day; expectations have tightened toward two to four hours, and FSMA 204's 24-hour records requirement is resetting the bar again. Plants with live genealogy finish the trace portion in minutes.

Why do mock recalls take so long?

Because the trace is reconstructed during the exercise from binders, batch sheets, and ERP exports. The time goes to archaeology, joining records that were never linked, and every ambiguous handwritten lot code adds delay.

How do you make mock recalls fast?

Build genealogy during production: capture lot links at receiving, consumption, and pack so the parent-child graph already exists. The recall becomes a query with records attached, and the exercise shifts to testing holds, notifications, and dispositions.

The Operations Brief

The best of what we publish, once a week.

Practical guides on high-production manufacturing, straight from the floor. No spam, unsubscribe anytime.

You're in. The next brief lands Monday morning.

See Harmony on your line

Harmony connects your machines, systems, and paperwork into one real-time operational layer — no rip-and-replace. See what it looks like in a plant like yours: read the CLS case study.

Book a Demo →

← Back to Resources