# Allergen changeovers: connect the previous run and the next release

A changeover record should identify the previous and next products, the approved changeover procedure and the verification required before the next run. A cleaning completion alone may not answer every question in the authorised release process.

> A changeover record should identify the previous and next products, the approved changeover procedure and the verification required before the next run. A cleaning completion alone may not answer every question in the authorised release process.

Kivloo editorial team · 2026-10-25

## Define the decision behind the record

Define what needs checked at that specific line or workstation. Link product identities, equipment and instructions. Do not invent a generic pass rule or imply that a photograph demonstrates the absence of an allergen.

## Connect the previous run, controls and next-run decision

Define the previous and next product identities and the approved changeover procedure. Identify equipment or areas in scope, the relevant ingredient information and who performs and reviews the required controls. An undated cleaning tick cannot show which product transition it covered.

Record the actual changeover activity and any required observations with time, method and responsible person. Preserve unsuccessful observations and repeated work rather than showing only the final acceptable state. If product or equipment scope changes, identify the change and reassess the record requirements under the approved procedure.

At review, follow the chain from the previous run through the performed controls to the decision for the next run. Test a satisfactory case, a repeated cleaning task and missing verification. The next production record should reference the reviewed changeover rather than merely infer approval from the presence of a signature.

## Worked example

A production line changes between two identified products. The team records the previous run, completes the approved work and captures the required verification. The authorised reviewer records the decision concerning the next run, with any unresolved condition still visible.

## 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.

- Previous and next product references

- Equipment and procedure version

- Completed work and operator

- Required verification result

- Release decision and authorisation

## Example record and review decision

Fictional record example: RUN-A: previous product and ingredient profile; CLEAN-02: approved changeover method; RUN-B: next product and release review.

Follow the connection between the previous run, performed controls and the documented decision for the next run.

A generic cleaning completion tick without the run identities may not explain which changeover was performed.

## Test the review, not just the form

Review the record starting from the next batch. The reviewer should find which changeover supported it and who made the decision. Test a failed verification; the system should retain it even after later work produces an acceptable result.

## Does a cleaning photograph prove allergen absence?

A photograph documents visible information. Use the verification and decision process appropriate to your operation.

## Does any cleaning record prove that the changeover was addressed?

The evidence needs to cover the actual transition and required method. Link previous and next products, performed controls and the review decision. A generic completion record may describe work without establishing which changeover it supports.

## Continue reading

- [HACCP guide: seven principles, food safety routines and practical records](https://kivloo.com/en/guides/haccp-guide-principles-records)

- [Allergen matrices: keep the ingredient evidence behind each version](https://kivloo.com/en/guides/allergen-matrix-version-control)

- [Ingredient substitutions: review the change before reusing a recipe record](https://kivloo.com/en/guides/ingredient-substitution-approval)

- [Ingredient label checks at receiving: preserve the actual product evidence](https://kivloo.com/en/guides/receiving-ingredient-label-check)

- [Digital HACCP records: build a temperature log your team can actually use](https://kivloo.com/en/guides/digital-haccp-temperature-records)

- [Food batch traceability: connect deliveries, ingredients and finished products](https://kivloo.com/en/guides/food-batch-traceability-records)

## Sources and further reading

- [Codex Alimentarius · CXC 1-1969 / General Principles of Food Hygiene](https://openknowledge.fao.org/3/cc6125en/cc6125en.pdf)

Operational guidance, not a certification or a legal assessment. Adapt examples to your site, approved procedures and local requirements. Product links lead to the English website; this guide does not imply a fully translated application or verified hardware compatibility.

Canonical: https://kivloo.com/en/guides/allergen-changeover-record