November 7, 2026
Your recall plan is only as good as your last drill
Most food brands have a recall plan. It lives in a binder or a shared drive, it names a coordinator, and it lists who to call. Far fewer can say how long it took the last time they actually traced a lot from an ingredient to every customer, and what broke along the way.
That gap is the whole point of a mock recall. The plan describes what should happen. The drill tells you whether your records can make it happen.
What a drill finds that a plan cannot
The failures are rarely dramatic. They are small and boring, which is why nobody notices them until the clock is running:
- A production run that consumed two lots of an ingredient, with only one written on the batch sheet.
- A 3PL that confirms shipments by SKU but not by lot, so the forward trace stops at their dock.
- Samples and internal transfers that never made it into any system.
- One person who knows where everything is, and who is on vacation.
None of those show up when you read the plan. All of them show up the first time you try to reconcile how much of a lot was made, consumed, shipped, scrapped, and is still on the shelf.
Time it, every time
The single most useful habit is to put a clock on the drill and write down the time for each step. The total matters, but the breakdown matters more: if the backward trace takes ten minutes and the shipment list takes four hours, you know exactly where to invest. FDA's Food Traceability Rule expects covered firms to produce records within 24 hours of a request, which is a useful outer bound even if your products are not on the list.
Make the drill harder than you want to
Choose a lot that went into several production runs, through a sub-assembly, and out through more than one channel. A lot that was received and sold untouched will pass every time and teach you nothing. Alternate between scenarios that start from a supplier's ingredient and scenarios that start from a customer complaint about a finished product.
What changes when lots are in the ledger
When receipts, production, and shipments all carry lot numbers in the same system, the trace itself stops being the slow part. In Skygn, the recall screen takes any lot and returns every customer shipment it reached, including through finished goods built from it, plus the backward trace to source lots and suppliers, ready to export. That frees the drill to focus on the parts software cannot do: deciding, communicating, and fixing what you found.
We wrote a full step-by-step mock recall guide, including a mass-balance table you can copy. If you are working out how the traceability rule applies to you, start with our FSMA 204 overview.
Run your food brand on one system, without the contract
Every module is in the seat price, billed monthly with no annual contract. Start with a 14-day free trial, import your items and recipes yourself, and cancel anytime with a full export of your data.