Food safetyAllergen management
Allergen matrices: keep the ingredient evidence behind each version
An allergen matrix should link its entries to the recipe version and ingredient information used to make the assessment. A table without source references can become difficult to verify after a supplier, recipe or product changes.
At a glance
An allergen matrix should link its entries to the recipe version and ingredient information used to make the assessment. A table without source references can become difficult to verify after a supplier, recipe or product changes.
Define the decision behind the record
Treat the matrix as controlled information with an accountable reviewer. Record the scope and source documents. Do not allow a blank cell to mean both not assessed and an affirmative claim about absence; those meanings must be distinct.
Keep the evidence behind each matrix entry
Identify the recipe, current ingredient specifications and the products covered before assembling the matrix. Give the matrix a controlled version and define who reviews changes. A product name is not a substitute for the actual supplier evidence, especially when several specifications have been used over time.
For each ingredient relationship, retain the specification identity and version that supports the entry. When a supplier or recipe changes, identify the affected products and information that require review. Keep unresolved questions explicit rather than carrying forward an old answer because the ingredient name looks similar.
Test retrieval from both a current product and a historical batch. The reviewer should find the matrix version and the evidence applicable at that time. Preserve superseded versions with their effective dates instead of making old production records appear to have used the latest specification. Review completeness and outstanding questions before approving the new matrix.
Worked example
A supplier updates an ingredient specification. The reviewer identifies recipes using that ingredient, evaluates the change under the approved process and issues the next matrix version. The earlier version remains available to explain information used previously.
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.
- Recipe and ingredient identifiers
- Specification version and source
- Assessment status and reviewer
- Matrix effective date
- Change communication record
Example record and review decision
Fictional record example: MATRIX-v3 / RECIPE-02: ingredient links to SPEC-A-v2 and SPEC-B-v4; REVIEW-01: authorised comparison and effective date.
Retrieve the supplier evidence behind each ingredient entry and identify which matrix version informed current product information.
A matrix without source versions becomes difficult to review when a supplier later changes the ingredient specification.
Test the review, not just the form
Select one matrix entry and recover its supporting evidence. Then select a changed ingredient and identify the entries needing review. Test whether menus, printed references and staff instructions receive the appropriate update rather than assuming they synchronize automatically.
A few useful answers
Can a blank cell mean no allergen?
Do not rely on that ambiguity. Distinguish assessed information, unknown information and fields awaiting review.
Does a current matrix explain every historical batch?
Not by itself. A historical record needs the recipe, matrix and ingredient evidence that applied when the batch was made. The latest version can be available alongside that history, but should not silently replace it.
Sources and further reading
MarkdownExplore starter templates
Start with a useful checklist
English
