Campaign Changeover
Campaign changeover is the controlled transition between two campaigns on shared equipment — full cleaning, line clearance, recipe swap, equipment requalification verification, and the first-batch protocol on the next campaign. It is the most quality-sensitive period in a multi-product plant: cross-contamination, mix-up and labelling incidents disproportionately happen at changeover. Treating it with the same rigour as production blocks, not as 'down time', is what keeps multi-product manufacturing safe and auditable.
01What campaign changeover is
Campaign changeover is the bounded period between the last batch of one campaign and the first batch of the next, on the same equipment. It packages everything required to make the next campaign safe to start:
- Final clean of the previous campaign (often full CIP/SIP, depending on regime).
- Cleaning verification (swab, rinse, visual, microbial) against the campaign-end protocol.
- Line clearance — physical and electronic confirmation that nothing of the previous product remains.
- Recipe swap — control system loaded with the next campaign's recipe and parameters.
- Equipment status reset — clean status, calibration currency, PM gating re-verified.
- Material clearance — previous product BOMs and lots cleared from the work area; new product BOM staged.
- First-batch protocol activation for the next campaign.
02Why changeover is high-risk
- Cross-contamination — residual previous product in equipment can carry into the next product (potency or allergen consequences).
- Mix-up — wrong recipe, wrong BOM, wrong labels at the start of the next campaign.
- Mislabeling — left-over labels from previous product applied to new product.
- Documentation drift — changeover often spans shifts; handovers are common error sources.
- Time pressure — production loss during changeover incentivises shortcuts that compromise verification.
- Cleaning failure not detected until next batch fails identity or microbial limit testing.
03Cleaning verification
Verification follows the cleaning-validation programme:
- Swab sampling at hardest-to-clean locations (validated worst-case sites).
- Rinse sampling for soluble residues with TOC, conductivity or specific assay.
- Visual inspection by trained operator with documented criteria.
- Microbial sampling per validated frequency and locations.
- Acceptance criteria tied to health-based exposure limits (HBEL) and MAC calculations.
- Out-of-specification cleaning result triggers re-clean and investigation — never overridden silently.
04Line clearance at changeover
Line clearance at campaign changeover is more extensive than between-batch line clearance:
- All previous product material physically removed from the line and bordering staging areas.
- Loose product, dust, debris removed from equipment surroundings, conveyors and floors.
- All previous product labels, batch records, work instructions removed.
- Previous product BOM closed in MES; new product BOM staged but not yet released.
- Two-person check (operator + supervisor) with sign-off in eBR.
- Photo documentation in some industries to support audit defence.
05First-batch protocol
The first batch of a new campaign often has additional controls:
- Additional sampling at defined points (extra IPCs, extra microbial samples).
- Tighter acceptance criteria on selected attributes to confirm clean changeover.
- Quarantine or enhanced QA review before release — slower path to disposition.
- Engineering oversight present during the first batch for in-the-moment troubleshooting.
- First-batch material sometimes designated as 'training-out' and not commercial release if changeover risks are highest.
- Comparison with golden-batch profile to confirm process behaving as expected.
06Scheduling and time discipline
- Changeover window scheduled with the same rigour as production blocks — Gantt entry with start, end, owner.
- Critical path identified — cleaning verification is usually critical-path.
- Time-on-changeover tracked for SMED-style improvement (reducing changeover duration without compromising quality).
- Pressure to shorten changeover never compromises validated cleaning steps; improvement comes from parallelisation and prep.
07Cross-industry examples
- Pharma — full CIP/SIP between campaigns of different APIs, with HBEL-based MAC verification.
- Biopharma — extensive cleaning and re-validation for multi-product facilities, often with line-of-product or product-family segregation.
- Food — allergen changeover with documented procedures and verification (often with allergen-specific swab testing).
- Cosmetics — fragrance and colour changeover with ATP swabs and visual verification.
- Chemicals — solvent-flush sequences between product chemistries with composition verification.
- Confectionery — sugar/non-sugar or nut/non-nut changeover with rigorous allergen verification.
08Common mistakes
- Changeover treated as 'down time' rather than a controlled, documented operation.
- Cleaning verification swabs skipped when 'visual clean' looks OK — quality risk in undetectable residues.
- Line clearance signed off without true two-person check — most common deviation at audit.
- First-batch protocol skipped after a few successful campaigns — protocol designed for risk should not normalise away.
- Previous-product labels not cleared, used on new product — recall incident.
- Changeover scheduled too aggressively, pressure to skip verification.
- Cleaning OOS handled with re-clean but no investigation — missed signal of cleaning-procedure inadequacy.
09How V5 Ultimate handles changeovers
Frequently asked questions
Q.How long does a changeover take?+
Highly variable — minutes for allergen-free flavour swaps with minimal cleaning, days for full multi-product API train with extensive cleaning validation. The right number is whatever the cleaning and verification protocol requires, with parallelisable work moved off the critical path.
Q.Can two changeovers happen in parallel on shared equipment?+
No — equipment can only be in one state at a time. Different equipment trains can changeover in parallel if independent. Coordinating multiple changeovers on a shared train is sequential by definition.
Q.What if cleaning verification fails?+
Re-clean with full record of why first clean failed, re-verify, and investigate root cause. Repeated failures trigger a cleaning-procedure CAPA. Never proceed to next campaign with a failed verification — even with management override authorisation, the residual risk is unacceptable.
Q.Is changeover validation part of process validation?+
Cleaning validation is its own programme but is typically referenced from PPQ and CPV. Changeover effectiveness (whether the new campaign behaves as expected from batch 1) is a CPV observable that highlights cleaning or recipe-load issues.
Q.How are changeover deviations handled?+
Same as any deviation — captured at occurrence, investigated, dispositioned. Changeover deviations are particularly important because they typically affect the next campaign's quality risk, so QA review often includes a 'next-campaign-impact' assessment before approving the changeover record.
Primary sources
Further reading
V5 Ultimate ships with the Campaign Changeover controls already wired in — audit trail, e-signatures, validation evidence. Free trial, no credit card, onboard in days, not months.
