A recall notice names a product, while the transportation file may name only a customer order. The immediate records problem is connecting those two descriptions without losing quantities or destinations.
Use these seven fields to support the recalling firm's and your food-safety team's instructions. They form a tracing worksheet for freight and warehouse teams, not a substitute for a recall plan. FSIS advises comparing product details with the information in the recall notice, including product names, dates, and lot codes. FSIS product-matching guidance.
1. Notice reference and the version you reviewed
Save the official notice link, its stated date or update, and the time your team reviewed it. Associate subsequent instructions with their sender and time. If the notice changes, preserve the earlier worksheet and document what must be rechecked. A forwarded screenshot can omit the context needed to identify the affected products.
2. Product identifiers from the notice and actual labels
Put the relevant notice criteria alongside the supplier's SKU, brand, package description, date codes, lot identifiers, and establishment information where specified. Preserve the original label evidence. Treat an unreadable or missing code as an unresolved match requiring the responsible team's review, not as proof that the product falls outside the notice.
3. The shipment references carrying those units
Map each potentially affected lot to inbound and outbound bills of lading, orders, and load references. Ask the warehouse for pallet or case-level records where needed. A shared order number alone may not identify which physical units moved on which truck. Record the document that supports each connection.
4. Quantity and a consistent unit of measure
Choose a working unit such as cases and record any conversion basis. Keep quantities received, currently held, transferred, and otherwise accounted for in distinct fields. Avoid adding pallets to cases or counting the same returned cases as both held and still outstanding at the receiver. Show unresolved balances explicitly.
5. Actual destination and present custodian
Capture where each shipment was delivered and who currently controls the relevant product, as far as records establish. A freight invoice's bill-to address may be different from the receiving location. FSIS's recall directive describes gathering distribution and consignee information during recall work. Use your records to support the responsible recall team; agency procedures are not themselves a checklist of duties for every broker. FSIS Directive 8080.1.
6. Instruction received and acknowledgement status
Track who was notified through the approved process, what action was requested, and whether receipt and action were confirmed. “Email sent” and “product held” are different statuses. Follow the responsible team's escalation process for an unanswered contact. Do not independently expand or narrow the recalled scope, or arrange disposition from an assumption.
7. Evidence closing each outstanding line
Attach the confirmation or document supporting a hold, return, authorized disposal, onward tracing, or other recorded outcome. Name the reviewer of unresolved items. Preserve cold-chain instructions during any authorized movement; recall tracing does not supply a new reefer setting or determine whether food is safe to release.
Copyable tracing worksheet
| Notice/version | Product/lot evidence | Load/BOL | Cases | Actual location/custodian | Instruction/acknowledgement | Evidence/open owner |
|---|---|---|---|---|---|---|
| ___ | ___ | ___ | ___ | ___ | ___ | ___ |
Worked example — hypothetical
In a mock recall exercise, the team's records identify 100 relevant cases: 40 remain at Warehouse A, 35 went to Receiver B, and 25 went to Receiver C. The quantity check is 40 + 35 + 25 = 100. That reconciles the initial distribution; it does not prove every case is controlled. If B has acknowledged the instruction but C has not responded, preserve C's 25 cases as an open action. If C reports a further transfer, add the supported destination and keep the history rather than counting another 25 cases as newly received inventory.
Next step: Review the lot-and-shipment identity section of 7 Details to Separate When Booking Fresh and Frozen Meat. Use it to strengthen the identifiers collected before the next shipment; it is background booking guidance, not a recall-management system.