01Direct answer
Build the checklist around the allergen risk between products.
To create an allergen changeover checklist, compare the product being made now to the product being made next. Record the allergens present, shared equipment, cleaning method, inspection points, verification result, label check, release decision, and corrective action if the changeover fails.
An allergen changeover is not just cleaning. It is a controlled switch from one product risk profile to another. HACCPlan connects the allergen matrix, sanitation steps, label review, verification checks, and batch release.
Reviewer question
The reviewer wants to know whether the line was cleaned and verified before the next product, and whether the right label was used after changeover.
02Checklist fields
The checklist should cover cleaning and labels.
- 01
Product sequence
Previous product, next product, allergens present, and whether the next product contains the same allergen.
- 02
Equipment
Shared hoppers, belts, fillers, utensils, rework bins, scales, and packaging areas.
- 03
Cleaning
Dry clean, wet clean, sanitation chemical, tools, disassembly, and pre-op points.
- 04
Verification
Visual check, ATP, protein swab, allergen swab, or QA release where used.
- 05
Label control
Correct label, allergen statement, lot code, packaging removal, and start-up check.
Use the interactive version
Create allergen changeover checklists in HACCPlan
Connect allergen matrices, cleaning steps, verification results, label checks, corrective actions, and batch release.
Free signup. Human review remains required for allergen and label decisions.
03Why it breaks
Changeovers fail when cleaning and label control are split.
One team may clean the line. Another may set packaging. QA may verify the line. Production may start the next run. If those records do not connect, the facility may prove cleaning but miss the label risk, or prove label review but miss the cleaning release.
Allergen errors can also happen when rework, utensils, scoops, totes, or partial packaging remain from the prior run. The checklist needs to match the real line, not a generic form.
04What HACCPlan does
Tie changeover to the product record.
HACCPlan makes the changeover part of product control.
- 01
Allergen matrix
Compare previous and next product allergens before the run.
- 02
Cleaning task
Create the right cleaning and verification checklist for the changeover.
- 03
Label check
Record the label version and allergen statement used for the next product.
- 04
Release decision
Keep failed verification, re-cleaning, and QA release tied to the lot.
05Proof
The best checklist protects the next product.
The record should show that the previous product risk was removed or controlled before the next product started. It should also prove that packaging matched the product being made.
That is the software-use-case lesson from larger brands: the page should not only explain the idea. It should show exactly how the user completes the workflow.
06Next step
Start with your worst-case sequence.
Pick the highest-risk changeover: allergen to non-allergen, tree nut to no tree nut, milk to dairy-free, sesame to no sesame, or a label-heavy packaging change. Build that checklist first.
Control allergen changeovers
Build the changeover workflow
Use HACCPlan to connect allergen risk, cleaning tasks, verification, labels, corrective actions, and batch release.
Useful for bakeries, co-packers, snack makers, and shared-line facilities.
07Related
Connect changeovers to allergen control.
Use the allergen statement calculator, allergen-control workflow, and label review workflow.
Andrew Langevin·CFIA-licensed facility, Brantford ON· Published 2026-06-06· 8 min read· Wikidata Q139112497