Skip to content

Mock Recall Flow Chart: Twelve Steps, With the Clock On

A mock recall flow chart for a small food business: twelve steps from picking a lot to filing the gaps, what to do when a step fails, and a worked example.

By Koa Sterling. Product specialist at TaroStack and small business owner. Yes, I am a real human, and I actually sit in front of a computer and write these articles. Reviewed November 20, 2026 · 7 min read

A mock recall is a timed rehearsal. You pick one lot, pretend it's bad, and find out how long it takes to say where all of it is. It runs in twelve steps: pick a lot, start the clock, find every batch that used it, find what was made, find where every unit went, count what's still here, add it up, pull the contacts, draft the notice, stop the clock, score it, and write down the gaps. A flow chart helps because the steps have to be done in order and some of them will fail. When one does, the right move is to write the gap down and carry on with what you have. The gaps are the point of the exercise. Below are the steps, an example, and a file.

The short version

  • Pick the lot without warning. An ingredient lot one time, a finished lot the next.
  • Time it from the pick to the drafted notice.
  • Two scores: how long it took, and what share of the lot you accounted for.
  • A step you can't finish is a finding. Write it down; don't stop.
  • Every gap gets a fix, a name and a date.
  • TaroStack runs the trace as one report and saves the timed drill. More below.

The twelve steps

Step Do this Then
1 Pick a lot without warning Go to 2
2 Start the clock. Write the time Go to 3
3 Find every batch that used the lot All found: go to 4. Can't tell: write the gap, go on with what you have
4 For each batch, find how much was made and its lot codes Go to 5
5 Find where every unit went: customers, dates, quantities Go to 6
6 Count what's still in the building, and anything sampled or destroyed Go to 7
7 Add it up: shipped + on hand + samples + destroyed = made? Within tolerance: go to 8. Not: find the difference, write the gap
8 Pull a contact for every customer who got it Go to 9
9 Draft the notice you would send Go to 10
10 Stop the clock. Write the time Go to 11
11 Score it against your targets Go to 12
12 Write the gaps, who fixes each and by when. File it Done

If the lot you pick is a finished one, step 3 becomes "find every ingredient and packaging lot that went into it, and each one's supplier", and the rest is the same.

An example

A made-up granola maker. The lot picked: sliced almonds AL-0921, received September 21.

Step What they found
2 Started 9:05 AM
3 Three batches used it: MP-0928, MP-1012, HN-1015
4 96, 120 and 72 bags: 288 in all
5 4 shops, 2 markets, 61 online orders
6 31 bags on the shelf, 6 samples, 2 damaged
7 249 shipped + 31 + 6 + 2 = 288. 100%
8 4 shop buyers with phone numbers; 61 emails; market sales have no names
10 Stopped 10:20 AM: 1 hour 15 minutes
11 Time: under the 2-hour target. Accounted for: 100%. Contacts: two markets can't be reached by name
12 Gap: market sales. Fix: a sign-up sheet at the stall, and lot codes on the day's sales sheet, by December 15

A clean run that still found something. Seventy-odd bags went to people who can only be reached by a sign at the stall. That goes in the recall plan as the reason a public notice would be needed.

The two scores

Time. From the pick to the drafted notice. Set your own target, or take your customer's or your audit standard's. This maker uses two hours. FDA's food traceability rule, for the foods on its list, asks for records within 24 hours of a request. FDA has proposed moving that rule's compliance date to July 20, 2028, and Congress directed FDA not to enforce it before then. Buyers set shorter targets than that, and they're the ones asking now.

Share accounted for. What was shipped, plus what's on hand, plus samples and waste, over what was made. The target is 100%. A little over or under usually means a counting error. A lot under means product you can't find, and that's the finding that matters most.

When a step fails

It fails at What it means The fix is usually
3: can't tell which batches used the lot Batch records don't name ingredient lots Write the lot of every ingredient on every batch sheet
4: finished lot codes missing Packages aren't coded, or two batches share a code A code for each batch, on every package
5: don't know who got which lot Invoices don't carry lot codes Lot on the packing slip and the invoice
7: doesn't add up Samples, breakage or short fills aren't recorded A line for each on the batch record
8: no contact Cash and market sales A sign-up sheet; a public notice in the plan

None of these is fixed during the drill. They're fixed afterwards, and the next drill checks them.

How often, and what to pick

Once a year at least, and again after any big change: a new product line, a new sales channel, new software. Alternate the starting point. A finished lot tests whether you can go backward to suppliers. An ingredient lot tests whether you can go forward and sideways, which is harder, because one bag of almonds is in three batches. Pick a lot that has shipped and partly sold through, not last week's.

This is general information, not legal advice. A full worked run is in food mock recall example, the difference between a drill and the real thing in mock recall vs product recall, and the report the trace should produce in traceability report example.

Get the flow chart

Download the mock recall flow chart. The twelve steps, what to do at each, where to go next, and the example beside a place for your own run, with a read-me. It's an ordinary Excel file with no macros, and it works in Google Sheets, LibreOffice and Numbers. Print it and write on it during the drill.

Where this stops working

The steps are simple. Doing them from paper isn't. Step 3 means reading every batch sheet since September. Step 5 means every invoice since then. The example took an hour and a quarter because the maker is small and tidy. At four times the size, with batch sheets in a binder, it's a day, and a day is too long for the real thing.

How TaroStack does it

TaroStack does steps 3 to 8 as one report.

Step 3. Each batch notes the lots it consumed, automatically. Open the almond lot and every batch that used it is listed.

Steps 4 and 5. Each batch has its own lot code and quantity, and each order records the lot shipped.

Step 6. Stock on hand by lot, with holds, and adjustments with a reason for samples and damage.

Step 8. The recall report lists the customers and suppliers the lot reached, with where to find each one, and downloads as one file.

The clock. A traceability drill is timed and saved, to show a buyer or an inspector. Home warns you a month before a year passes without one.

Step From paper In TaroStack
Which batches used the lot Read every batch sheet The lot's trace
Where each unit went Every invoice Orders, by lot
Does it add up? A hand count and a sum Made, shipped and on hand, by lot
Date and result of the last drill A note in a binder The saved drill

Lots, batches and recalls, with timed drills, are on every plan, from $9.99 a month (5 recipes) or $39 a month (50 recipes). The first 14 days are free, with no credit card. If you'd like a hand setting up, ask, and we'll do it with you.

Questions people also ask

What are the steps of a mock recall?

Pick a lot, start the clock, trace it to every batch and every customer, count what's still on hand, check that it adds up, pull contacts, draft the notice, stop the clock, score it, and record the gaps.

How long should a mock recall take?

Use your customer's or auditor's target, or set your own. The example maker's target is two hours.

How often should you do a mock recall?

At least once a year, and after any major change to products, sales channels or record keeping.

Sources

  1. FDA, FSMA Final Rule on Requirements for Additional Traceability Records for Certain Foods: the compliance date and the proposed extension to July 20, 2028 (content current as of 11/04/2026) · read November 19, 2026
  2. 21 CFR 1.1455: records available within 24 hours, an electronic sortable spreadsheet on request · read November 19, 2026
  3. 21 CFR 117.139: recall plan (effectiveness checks; disposing of recalled food) · read November 20, 2026

We use AI to help with the research for these articles. Every one is read, checked against its sources and edited by Koa before it's published. Spot a mistake? Tell us and we'll fix it and say so. How we write these.

Let’s get your stack in order.

Get TaroStack

Sign up now for your free 14 day trial. No credit card required.