9.2 Traceability Procedures, Mock Recalls & Staff Training
Key Takeaways
- Blueprint tasks E.1, E.2, E.6, and E.12 cover training staff on recall activities, conducting mock recalls, securing distribution lists, and developing traceability procedures.
- One-step-back and one-step-forward traceability is the baseline requirement under the Bioterrorism Act recordkeeping rule.
- FSMA Section 204 adds enhanced recordkeeping — Critical Tracking Events and Key Data Elements — for foods on the Food Traceability List, with a compliance date of July 20, 2028.
- Mock recalls should be run at least annually, exercise both directions of trace, and be measured on time to reconcile and percentage of product accounted for.
- A mock recall that reconciles 100% of product is only meaningful if the exercise was run against real records under time pressure rather than reconstructed afterward.
9.2 Traceability Procedures, Mock Recalls & Staff Training
Exam Tip: The traceability layers stack: one-up one-back applies broadly; FSMA 204 enhanced records apply only to foods on the Food Traceability List. Do not apply the enhanced requirements universally.
Layer 1: One-Step-Back, One-Step-Forward
The Bioterrorism Act recordkeeping rule requires persons who manufacture, process, pack, transport, distribute, receive, hold, or import food to keep records identifying the immediate previous source and the immediate subsequent recipient of food.
| Element | Record |
|---|---|
| One step back | Who supplied it, what it was, how much, when it was received, lot or code where available, and the transporter |
| One step forward | Who it went to, what, how much, when it shipped, and the transporter |
Retail food establishments and restaurants have reduced obligations under the rule — generally they must keep records of the immediate previous source but not of individual consumers. Retention periods vary by the perishability of the food, ranging from six months to two years.
This layer is what makes a traceback possible at all. It is also why shellstock tags retained for 90 days and invoices filed by date matter so much at retail: they are frequently the only one-step-back record that exists.
Layer 2: FSMA Section 204 Enhanced Traceability
The Food Traceability Rule (21 CFR Part 1, Subpart S) requires additional records for foods on the Food Traceability List (FTL) — a list that includes soft and semi-soft cheeses, shell eggs, nut butters, cucumbers, herbs, leafy greens, melons, peppers, sprouts, tomatoes, tropical tree fruits, ready-to-eat deli salads, and finfish and crustacean shellfish categories.
The framework has two vocabulary items the exam may test:
- Critical Tracking Events (CTEs) — the points in the supply chain where records must be created: harvesting, cooling, initial packing, first land-based receiving, shipping, receiving, and transformation.
- Key Data Elements (KDEs) — the specific data captured at each CTE, anchored by a Traceability Lot Code that follows the food through the chain.
Covered entities must also maintain a traceability plan describing their procedures, their lot code assignment method, and a point of contact.
Compliance date: July 20, 2028. FDA originally set January 20, 2026, then extended the date by 30 months; the extension was published in the Federal Register in August 2025 and reinforced by a congressional directive that FDA not enforce the rule before that date. The rule's substantive requirements were not changed by the extension.
Layer 3: Internal Lot Control
Regulatory minimums are not enough to execute a narrow recall. Internally, a facility needs:
- Lot codes assigned at receiving for every incoming ingredient, and recorded on the ingredient container
- Batch records listing every ingredient lot consumed in each production batch
- Finished-goods lot codes printed legibly on each package, with the coding scheme documented
- Shipping records linking finished lot codes to specific customers, quantities, and dates
- Rework tracking — reworked product carries the lot history of everything in it, and untracked rework is the classic cause of unbounded recall scope
Designing a Mock Recall
A mock recall is a rehearsal, and it should be uncomfortable.
Design principles
- Run it in both directions. A forward trace starts from an ingredient lot and asks where every unit of finished product went. A backward trace starts from a finished package and asks which ingredient lots are in it. Most programs only ever practice one.
- Use a real lot and real records. A drill against a hypothetical lot proves nothing.
- Do not warn the team. An announced drill measures preparation, not capability.
- Run it at a bad time — a shift change, an absent quality manager, a weekend. Real recalls do not wait for convenience.
- Include the phone calls. Actually locate and reach the consignee contacts, without sending the recall notice. Stale contact lists are the most common discovered defect.
- At least annually. GFSI-benchmarked schemes generally require the recall and withdrawal procedure to be tested at least once a year, and some — such as BRCGS — require that full traceability be demonstrated within four hours. Verify the requirement of the specific scheme the facility is certified to, since the numbers differ.
Scoring
| Metric | What it tells you |
|---|---|
| Time to complete the trace | The operational constraint that matters most in a real Class I event |
| Percentage of product reconciled | Produced minus shipped minus on-hand should balance; unexplained gaps are the finding |
| Contact list accuracy | Percentage of consignee contacts reachable at the number on file |
| Record retrieval time | How long it took to physically find each record |
| Gaps identified | Missing lot links, illegible codes, untracked rework, missing shipping records |
A drill in which everything worked perfectly usually means the drill was too easy. The purpose is to find the gaps before a regulator does.
After-action
Document the scenario, the timeline, the results, the gaps, the corrective actions, the owners, and the deadlines — and verify the corrective actions before the next drill. A mock recall report with no corrective actions is a compliance artifact, not an exercise.
Training Staff on Recall Activities
Blueprint task E.1 is "Train staff on recall activities." Training is role-specific.
| Role | Must know |
|---|---|
| Recall coordinator | The whole procedure; holds decision authority; the single point of external contact |
| Quality assurance | Health hazard evaluation inputs; sample retention; laboratory coordination |
| Production | How to stop production, segregate, and preserve records; where lot codes are applied |
| Warehouse / shipping | How to place a hold, physically segregate, pull distribution records, and stop outbound shipments |
| Purchasing | Supplier contacts; incoming lot records; how to notify a supplier of a defect |
| Customer service | The approved script; how to log consumer contacts; never to speculate about cause or liability |
| Senior management | Authority to initiate; resource commitment; the designated spokesperson |
| Retail store staff | How to remove product from shelves, where to place recalled stock, and how to respond to a customer holding the product |
The recall team roster must include names, roles, and after-hours contact numbers, and it must be reviewed on a schedule, because turnover silently degrades it. A recall plan listing a coordinator who left the company eighteen months ago is a plan that will fail on the first call.
What is the compliance date for the FSMA Section 204 Food Traceability Rule's enhanced recordkeeping requirements?
Which describes the baseline one-step-back, one-step-forward recordkeeping obligation?
A facility's mock recall program always starts from a finished product code and traces backward to ingredient lots. What is the principal weakness?
Untracked rework is repeatedly cited as a cause of unbounded recall scope. Why?