Quick Guide · Allergens
Allergen screening with Copilot: what AI cannot verify
When a supplier updates an ingredient formulation, Copilot Chat can rapidly highlight newly declared allergens between specification exports. However, physical cross-contact controls and factory validation under clause 5.3 remain the sole responsibility of the technical manager.
11 Nov 2026 · 42 sec · Copilot Chat (Copilot Chat, no licence needed)
The scenario
- Site
- Dessert and chilled bakery manufacturing site
- Who
- Raw Material Technical Manager
- Trigger
- An email notification from a long-standing supplier mentions an updated formulation for a biscuit crumb raw material, buried beneath routine supply-chain updates.
- Why it matters
- If a formulation change introducing a new allergen goes unnoticed, printed packaging becomes incorrect, site allergen management procedures fail, and mislabelled product risks consumer health and a critical audit non-conformance.
BRCGS context
| Clause | What the Standard expects | Sensible practice | Where technology helps |
|---|---|---|---|
| 5.3 Management of allergens | Allergens are risk-assessed and controlled to prevent cross-contact and ensure correct labelling. | Sensible industry practice involves maintaining a controlled change-management process whenever raw material formulations change, updating site cross-contact matrices, and reviewing manufacturing scheduling before accepting delivery. | Copilot Chat rapidly compares complex text in specification documents to flag added ingredients and allergen changes; the technical manager must independently evaluate factory cross-contact risks, cleaning validation, and final acceptance. |
| 5.2 Product labelling | Labels are accurate, legal and approved. | Sites routinely operate formal pack-copy sign-off workflows, checking declared ingredients and allergen emphasis against current raw material specifications prior to print runs. | Copilot Chat cross-references the amended raw material against exported site recipe lists to isolate affected finished SKUs; legal review, label verification, and final pack approval remain strictly human tasks. |
Clause intent in plain English, not the Standard's wording. Check requirements against your own licensed copy of BRCGS Food Safety Issue 9.
The approach, step by step
- 01
Upload and compare raw material specifications
Compare these two uploaded specifications for Biscuit Crumb (Old vs New). Provide a table showing differences in ingredient listing, compound ingredients, and declared allergens.You check: Verify every row against the original PDF specifications to confirm no compound ingredient details were overlooked or misparsed.
- 02
Map raw material changes to finished products
Review the attached Site Recipe Matrix. List every finished SKU that uses raw material RM-042 (Biscuit Crumb), showing current label allergens and the impact of the added Egg allergen.You check: Cross-check the SKU list against the live site recipe management database to ensure recipe versioning is current.
- 03
Draft an allergen risk assessment questionnaire
Draft an internal checklist for our technical team to assess factory impacts of introducing Egg via RM-042, covering storage, line segregation, utensil colour-coding, and cleaning verification.You check: Review the checklist against actual factory layout, current allergen profiles on that line, and validated cleaning regimes.
- 04
Draft supplier clarification and internal notification
Draft a formal technical notification to internal NPD and Labelling teams summarising the change to RM-042 and requesting a label update hold on affected SKUs.You check: Ensure the notification reflects agreed site approval workflows and correct internal stakeholders before sending.
Takeaways
- Use Copilot Chat to compare specification exports quickly, treating the output strictly as an initial screening draft.
- BRCGS clause 5.3 compliance rests on verified factory controls, such as cleaning validation and line segregation, which AI cannot assess.
- Cross-reference all AI-flagged formulation changes against master site databases before authorising factory trials or packaging sign-off.
Limitations and risks
- Copilot Chat does not connect directly to site ERP, recipe management software, or supplier specification portals; files must be manually exported and uploaded.
- Document parsing can omit text within complex nested tables, watermarked PDFs, or scanned specification sheets.
- Copilot Chat cannot evaluate whether site cleaning regimes effectively remove egg protein residues; validation requires physical testing and technical assessment.
- AI cannot determine regulatory transition rules for existing printed packaging stock or commercial run-out timelines.
- Over-reliance on automated document comparison, missing subtle compound ingredients or changes hidden in footnote disclaimers.
- Uploading confidential supplier formulations or proprietary customer recipes without ensuring enterprise data protection safeguards are active.
- Accepting a generated SKU impact list without verifying against the production master recipe database, risking unlabelled allergens entering retail distribution.
Sources
TFCD content is general guidance, not professional advice for your site. Always check requirements against your own licensed copy of the BRCGS Standard and your customers' codes of practice. Narrated with an AI voice clone of the presenter; Copilot screens are illustrative recreations with dummy data.

