Food traceabilityRecall exercises
Backward traceability exercises: recover the inputs behind a finished batch
A backward exercise starts with a finished batch and recovers its actual input lots and receiving evidence. A recipe or standard bill of materials is useful context, but does not establish which supplier lots were used in that particular run.
At a glance
A backward exercise starts with a finished batch and recovers its actual input lots and receiving evidence. A recipe or standard bill of materials is useful context, but does not establish which supplier lots were used in that particular run.
Define the decision behind the record
Use the actual output identifier, then follow production and relevant handling events. Account for multiple lots of the same ingredient and any recorded rework. Keep unavailable references visible rather than replacing them with expected inputs.
Recover actual input lots instead of the intended recipe alone
Select the finished batch and define the production event and sites included. Prepare access to its actual input relationships, receipts and preceding transformations. Keep a recipe available as context, but do not use it as evidence that particular physical lots were consumed.
Retrieve each actual input and its source record. Where an ingredient was repacked or reworked, continue through the parent relationship rather than stopping at the latest internal label. Preserve unclear input identities and quantities as gaps; selecting a convenient receipt after the fact does not resolve them.
Review whether every input path reaches the intended source evidence and whether the returned references match the production record. Test multiple input lots and a reused intermediate product. Assign missing relationships for correction and repeat the retrieval from the same finished batch to verify that the repaired path is understandable to another reviewer.
Worked example
A reviewer selects a finished batch. The team recovers its actual ingredient lines, finds the associated receipts and identifies the source documents. One planned ingredient differs from the recorded input, so the difference is reviewed with the original records intact.
Build a usable record
Use the fields below to capture the facts needed for this particular decision. Keep the actual observation separate from any later correction or approval.
- Selected finished batch
- Actual production record
- Ingredient and rework lot references
- Receiving and supplier evidence
- Unresolved differences
Example record and review decision
Fictional record example: PREP-1 → ING-A / REC-01 and ING-B / REC-02; each receipt → supplier document and original lot.
Recover all input lots and their evidence, including repacked or reworked inputs where applicable.
Retrieving the recipe ingredient list is not the same as identifying the actual lots used in this production.
Test the review, not just the form
Ask an unfamiliar reviewer to follow the links without help from the original operator. Identify where the process depends on memory, naming conventions or free-text notes that cannot be searched reliably.
A few useful answers
Can the recipe substitute for actual ingredient-lot records?
No. It describes intended composition, while the exercise needs the inputs recorded for the selected batch.
Why does retrieving the recipe not complete the exercise?
A recipe identifies intended ingredients. A backward exercise needs the physical lots actually used and their source evidence, including relevant preceding transformations or repacking events.
Sources and further reading
MarkdownExplore starter templates
Start with a useful checklist
English
