Skip to content

Free template

Updated

Mock recall template: traceability exercise worksheet

A mock recall is a practice run of your recall procedure. Someone names a finished lot, and the team traces it one step back to every ingredient and packaging lot and its supplier, and one step forward to every first customer, against the clock. SQF requires the test at least once a year (Food Manufacturing Code, Edition 9, element 2.6.3.2), and BRCGS asks for an annual traceability test with a quantity check. This worksheet has an exercise sheet (header, six timed milestones, where every unit of the finished lot went, the recall contacts tested and a scorecard), a trace-back table with a mass balance for each input lot, a trace-forward table and a gap log with owners, due dates and re-tests. The Excel version works out the elapsed time against your target and the unaccounted quantity and percent accounted for each lot, flags anything outside the tolerance your site sets, and gives an overall result. The PDF has the paper sheets, a worked example, and the rules paraphrased with their section numbers. It is an example to adapt, not legal advice.

Free to use: print it, copy it and edit it for your team. Enter your name and work email once to download.

Page 1 of the mock recall templateHeader fields for site, product, lot, scenario, time target and tolerance, a clock of six milestones, a finished lot reconciliation table, a scorecard and a recall contacts table.
Exercise header and scenarioSix timed milestonesTrace back to every input lotMass balance against a toleranceTrace forward to first customersFinished lot reconciliationRecall contacts testedScorecard and overall resultGap log with re-testsWorked example

When to use it

When to run a mock recall

  • For the yearly test your certification scheme or your customers require, on a different product, line and shift each time.
  • After a change to how lots are tracked: a new ERP or receiving process, a new warehouse, a new line or a new supplier of a bulk ingredient.
  • When a customer audit or questionnaire asks for your last mock recall and how long it took.
  • To train a new recall team or a new QA manager before they face a real recall.
  • If you make or use foods on the FDA Food Traceability List, to practise pulling the records that rule asks for.

How to fill it in

  1. 1

    Choose the lot and the scenario

    Pick a finished lot that has already shipped, so the forward trace is real. Change product, line, shift and supplier from one test to the next, and favour lots with many inputs, rework or a bulk material used across many products. Write the scenario in one line: a customer complaint, a supplier's notice, a positive test.

  2. 2

    Decide planned or no-notice

    A planned exercise trains people; a no-notice one shows what really happens on a night shift. In both, someone outside the team names the lot and starts the clock. Set the time target and the mass balance tolerance before you start, not after.

  3. 3

    Trace one step back

    From the batch and production records, list every lot used: ingredients, packaging that touches the food, processing aids and rework. For each one find the receiving record (supplier, supplier lot, date received, quantity, document number) and write down the time it was found.

  4. 4

    Trace one step forward

    From the shipping records, list every shipment of the lot to its first customer, the first place it went after it left your control, with the bill of lading or invoice number and the quantity. Check that each customer is on the recall contact list with current details.

  5. 5

    Reconcile the quantities

    For each input lot, received minus used in this lot, used in other lots, on hand and waste should come close to zero; the Excel flags anything outside your tolerance. For the finished lot, shipped plus on hand, samples and destroyed should equal what was produced.

  6. 6

    Test the people, not the customers

    Call the recall team at the hours a real recall could start and count who answers. Do not contact customers unless your procedure says so, and never in a way that could start publicity.

  7. 7

    Close out the same day

    Stop the clock and review with the team. Log every gap with a cause, an owner and a due date, re-test each fix on a later lot, and keep the records: auditors ask for the last test and what changed after it.

What auditors and the rules ask

What the codes and regulations ask for, in plain words

Paraphrased with section numbers so you can check the documents themselves. No US regulation sets a time limit for a mock recall: the time target is your site's or your customer's.

  • SQF Food Manufacturing Code, Edition 9, elements 2.6.2 and 2.6.3

    What it asks
    Trace at least one step back to the supplier and one step forward to the customer. Test the withdrawal and recall system at least once a year, on different products and shifts, and keep records of the tests and the corrective actions.
    Where the worksheet records it
    Trace back and trace forward tables, gap log, next test due
  • BRCGS Food Safety, Issue 9, clauses 3.9.3 and 3.11.3

    What it asks
    A traceability test across product groups at least once a year, with a quantity check or mass balance, and a yearly test of the incident and recall procedure. In earlier wording, as quoted by BRCGS, full traceability should take no more than 4 hours and the test records the timings of key steps.
    Where the worksheet records it
    Mass balance for each lot, the clock, the time target
  • 21 CFR 117.139 (FDA)

    What it asks
    A written recall plan for food with a hazard requiring a preventive control: who notifies direct consignees and, when needed, the public, how effectiveness is checked and how the food is disposed of.
    Where the worksheet records it
    Recall contacts tested, trace forward
  • 21 CFR 1.337 and 1.345 (FDA, Subpart J)

    What it asks
    Records of the immediate previous source and the immediate subsequent recipient of food, and for manufacturers the source of each ingredient in each finished lot. FDA can ask for them within 24 hours (1.361).
    Where the worksheet records it
    Supplier, lot, date, quantity and document columns
  • 21 CFR Part 1 Subpart S, the Food Traceability Rule (FSMA 204)

    What it asks
    For foods on the FDA Food Traceability List: a traceability plan, traceability lot codes and key data elements for receiving, transformation and shipping, and the records to FDA within 24 hours, as a sortable spreadsheet during an outbreak or recall.
    Where the worksheet records it
    Location and reference document columns, the Food Traceability List column, the Excel sheets

A filled-in example

Illustrative, not a benchmark

An example: a no-notice mock recall of lot TB-5281 of tomato basil pasta sauce, 2,000 cases of 680 g jars, with a 4-hour target and a 2% tolerance set by the site (illustrative numbers, not a real plant).

The example mock recall, by the clock

  1. 08:40Lot named
  2. 10:25 · 105 minTrace back
  3. 10:55 · 30 minTrace forward
  4. 11:40 · 45 minReconciled
  5. 12:00 · 20 minClosed
  1. Lot named to close-out3 h 20 minpass

Lot named at 08:40, records pulled at 09:05, trace back complete at 10:25, trace forward complete at 10:55, quantities reconciled at 11:40, exercise closed at 12:00: 3 hours 20 minutes against a 4-hour target.

Production records were pulled by 09:05. The trace back then took 80 of the 200 minutes, most of it spent finding one label roll lot on a paper receiving log.
  • 08:40: the plant manager names the lot. The production records are pulled by 09:05, and by 10:25 the trace back has found all 14 input lots; the last, a label roll, was only on the paper receiving log.
  • 10:55: the trace forward finds 5 first customers and 1,826 cases. With 150 cases on hand, 2 retained samples and 22 destroyed after a QA hold, all 2,000 cases are accounted for.
  • 11:40: the mass balance shows olive oil lot O1-5531 at 1,000 - 420 - 380 - 160 - 10 = 30 kg unaccounted, 3.0%, over the 2% tolerance: the tote heel went into the day tank with no record. Salt (0.5%) and dried basil (0.4%) are inside the tolerance.
  • 6 of the 7 people on the recall contact list are reached; one number is out of date.

Closed at 12:00: 3 h 20 min against the 4-hour target, with every lot and shipment found, so the result is Pass with gaps. Three corrective actions follow: a day-tank transfer record, packaging lots entered at receipt and an updated contact list, each with an owner, a due date and a re-test.

Common mistakes

  • Choosing an easy lot

    A lot with five inputs and one customer always passes. Pick lots with rework, bulk materials used across many products and many customers, and change product, line and shift each time.

  • Stopping once the records are found

    Finding every lot is half the test. Without the quantities you cannot tell whether product went somewhere you have no record of, which is exactly what a real recall needs to know.

  • Leaving out packaging and rework

    Packaging that touches the food, processing aids and rework are inputs too, and they are the ones most often kept on paper logs.

  • Running it from the office

    Use the records the shifts really keep. If the answer depends on one person who knows where things are, the test should show that; run the next one on the night shift.

  • Calling customers during a test

    A customer who thinks the recall is real can pull product or raise an alarm. Check the contact details instead; call only if your procedure says so, and say clearly that it is a test.

  • No re-test

    A corrective action is done when a later trace shows it worked, not when the form is signed. Log the re-test date and run it.

Download the template

Free to use: print it, copy it and edit it for your team. Enter your name and work email once to download.

Run this template in LeanSuite

LeanSuite lets food and beverage plants build their own GMP inspections and HACCP verification checks, complete them on a phone or tablet with photos, and turn failed items into corrective actions tracked to verified closure.

See it in a 45-minute demo

FAQ

Mock recall template: traceability exercise worksheet: common questions

More free templates

All templates
Browse all 189 templates

Can't find the template you need?

Tell us what you're looking for. We'll make it and send it to your inbox, free.

A shift handover sheet, a red tag log, a changeover checklist for one machine: if your team uses it on the floor, ask.

By sending this form you agree to our Terms of Service and Privacy Policy.

Pass it on

We want LeanSuite to be the best place on the internet for lean help. If this was useful, send it to someone on your team or in your network who needs it.