HACCP News
Every packaged food carries an allergen statement, and most food safety teams treat that label as the finish line. It isn’t. GFSI-recognized schemes expect a documented allergen management program behind that label – one that controls cross-contact on the line, validates that cleaning between runs actually works, and catches a labeling gap before a customer does. The label is the last step. Everything that makes it true happens earlier.
Cross-Contact Is Not Cross-Contamination
The two terms get used interchangeably and they shouldn’t be. Cross-contamination is the broad food safety term – any unwanted transfer of a hazard, biological, chemical, or physical, between foods, surfaces, or people. Cross-contact is narrower and allergen-specific: the unintended transfer of an allergenic protein from a food that contains it to a food that doesn’t declare it. A cook step can destroy the pathogen behind a cross-contamination event. Nothing destroys an allergen the same way – heat, time, and dilution don’t make peanut protein stop being peanut protein. That’s why cross-contact gets its own controls instead of riding along inside general sanitation.
The Major Allergen List Is Now Nine, Not Eight
Milk, eggs, fish, crustacean shellfish, tree nuts, peanuts, wheat, and soybeans made up the major food allergen list for years. Sesame joined them as the ninth major allergen effective January 1, 2023, under the FASTER Act. Any allergen program, label review process, or supplier questionnaire built before that date was built around eight allergens, not nine – and a program that was never formally revisited to add sesame is a program with a gap an auditor will find before you do, especially wherever sesame shows up in a dusting, coating, or seasoning blend rather than as an obvious headline ingredient.
Changeover Controls
A changeover control is the written procedure for what happens on shared equipment between an allergen-containing run and one that isn’t supposed to contain it: the scheduling rule that runs allergen-free products first where possible, the cleaning method required before the next product starts (dry clean, wet clean, or full teardown, depending on the allergen and the equipment), and a line clearance sign-off confirming the previous product and its packaging are actually cleared from the area before production resumes. Without a written, followed changeover procedure, “may contain” on the label isn’t a precaution – it’s an admission that nothing upstream of the label is actually controlling the risk.
Validating the Cleaning Between Allergen Runs
Validation and verification answer different questions, and auditors ask for both. Validation proves, with data – typically an allergen-specific test like ELISA or a lateral flow swab, since general-purpose ATP testing doesn’t reliably detect allergen residue – that a given cleaning procedure actually brings allergen residue on that equipment down to an acceptable level. It’s normally done once to establish that the method works, and again whenever the process, equipment, or allergen changes. Verification is the everyday check that the validated procedure was actually followed this time – a visual inspection, a swab, a sign-off. A program with verification records but no validation study has no proof the procedure it’s following was ever any good in the first place.
Where Allergen Programs Fail
- A changeover procedure exists on paper, but there’s no record it was actually followed for a specific batch on a specific date.
- The cleaning validation study is years old, done on an equipment configuration or product mix that no longer matches what actually runs on that line.
- Label review isn’t triggered by formulation or supplier changes, so a reformulated ingredient introduces an allergen the label never gets updated to declare.
- “May contain” precautionary labeling is used as the default answer instead of the last resort, after control measures have actually been tried and validated.
How HACCP Builder Helps
An Allergen Plan template ships as part of the Sub Plan library – covering cross-contact control, changeover, and label verification. It’s a structured starting document, not a blank form, and it stays with the rest of your program instead of living as a separate binder or file. It’s part of the same set of customizable checklists covering the programs that sit outside a traditional HACCP plan, described in more detail on the GFSI-recognized schemes page.
What This Is, and What It Is Not
This is a structured written program, not a testing service. HACCP Builder gives you a well-built starting document for changeover, cross-contact control, and label verification, and a place to keep it current – it does not run your allergen swabs or validate your cleaning procedure for you. The lab work and the judgment calls about your own lines are still yours; the blank page is not.
Contact HACCP Builder to see how an allergen management program fits into your own facility.
We can be reached at (866) 577-4030 ext. 800 or via email at [email protected]. Leave us a message or book a free demo today!
