How do you handle kit changes after production has started?

Why kit changes in-flight are risky

Changing a kit once production has started is inherently high risk because it disrupts a configuration that has already been planned, documented, and often partially built. At that point, bills of material, routings, travelers, and quality plans may already be instantiated, and operators may be following printed or cached instructions. Uncontrolled changes can create mixed configurations on the line, undocumented rework, and gaps in traceability. In regulated environments, this quickly turns into a documentation and audit exposure, not just an efficiency issue. For that reason, in-flight kit changes need to be treated as controlled configuration changes, not quick fixes.

Start with clear triggers and decision gates

You need defined triggers for when a kit change is even allowed after production start, such as formally logged nonconformances, customer-driven configuration changes, or safety-critical design updates. Each trigger should route through a decision gate involving at least engineering and quality, and often production planning. At that gate, the team decides whether to stop the order, scrap or rework parts, or proceed under controlled change with updated kits. In many brownfield plants this decision process is partly manual, but it still needs documented criteria and accountable approvers. Without clear gates, production staff will improvise, leading to uncontrolled divergence between the physical build and the documented configuration.

Perform a structured impact assessment first

Before changing any kits, perform an impact assessment covering technical, quality, and schedule implications. From a technical standpoint, identify which assemblies and serial numbers are already at which build step and whether the new kit content is forward- and backward-compatible. From a quality and regulatory angle, clarify whether this is a design change, a deviation, or a concession, and what level of documentation and validation evidence is required. Operationally, check capacity to rework affected units, material availability for revised kits, and any knock-on effects on downstream test or inspection. In older MES/ERP environments this analysis often relies on a mix of system queries and manual line walks; pretending it is fully automated when it is not is a source of errors.

Control work in progress and separate configurations

Once you commit to a kit change, you must prevent uncontrolled mixing of old and new configurations on the floor. A pragmatic pattern is to clearly separate work-in-progress into: units that will finish under the old kit, units that will be reworked to the new kit, and units not yet started that will begin with the new kit. Physical segregation, clear traveler markings, and line-side signage are often as important as system flags, especially in plants that still rely on paper travelers. If you attempt to drive everything purely through system statuses without physical controls, you increase the risk of operators following obsolete instructions or pulling the wrong components.

Update BOMs, routings, and travelers under change control

Any in-flight kit change should flow through your existing change control process, even if you need an expedited path. That typically means updating the BOM and relevant routings or work instructions, with clear effective dates or effectivity by serial/lot. Travelers or electronic work orders must reflect which configuration applies to which unit, and which additional steps (e.g., removal and replacement) are required. In brownfield stacks, aligning ERP BOMs, MES work instructions, and line documentation is often the hardest part and the main source of mismatch. If these systems cannot be synchronized quickly, you may need temporary controlled workarounds, like controlled rework sheets tied to specific serials, while formal master data updates catch up.

Handle physical material and kitting logistics explicitly

Changing a kit is not just a data change; it is a physical materials problem. Old components already issued to the order may need to be quarantined, returned to stock, or scrapped with proper disposition records. New components must be picked, verified, and staged, ideally with barcode or RFID checks where available, but often still supported by manual counts. Point-of-use storage labels and kanban bins may need to be updated to avoid operators grabbing superseded parts. If warehouse and production systems are weakly integrated, expect manual reconciliations between inventory records, kitting lists, and what operators actually have at the station, and plan for that overhead in the process.

Maintain full traceability and documentation of the change

For regulated work, traceability of what changed, when, for which units, and under whose approval is non-negotiable. Every affected serial or lot should be linked to the specific change record, deviation, or concession identifier. Inspection records, test results, and certificates of conformity must reflect the final as-built kit, not just the original plan. In older or fragmented IT environments, this often means supplemental documentation such as annotated travelers, controlled rework forms, or configuration summary sheets. The key is that an auditor can reconstruct, without guesswork, how the final configuration for each unit relates to the change and when the new kit content became effective.

Plan for validation, qualification, and re-verification where required

If the kit change alters form, fit, function, or process parameters in a regulated product, you may trigger the need for additional validation or qualification steps. That might include targeted re-qualification runs, additional first-article inspections, or temporary 100% inspection versus sampling. The burden depends heavily on your sector, customer contracts, and change classification, so the process must call this out explicitly. Attempting to shortcut these steps to avoid downtime can create bigger issues later when nonconformances surface in the field or during customer audits. Because full revalidation is costly, plants often use risk-based approaches, but those need to be documented and consistently applied, not improvised.

Brownfield coexistence: accept partial automation and manual controls

In most existing plants, the systems landscape cannot fully automate or perfectly synchronize in-flight kit changes. ERP, MES, PLM, and QMS often use different identifiers, update cycles, and ownership, making real-time effectivity control difficult. Effective handling usually combines: minimal but clear system changes (like status flags and revised BOMs), structured but manual communication (like focused line briefings), and simple physical controls (segregation, labels, and traveler annotations). Attempts to replace or heavily re-platform systems just to handle rare kit changes often fail under the weight of validation, integration complexity, and downtime risk. It is usually more realistic to strengthen procedures, training, and simple integration points than to chase a fully automated, zero-manual-touch solution.

Connecting this to your environment

If your current process for mid-build kit changes consists mainly of emails and verbal instructions, you likely already carry hidden risk in traceability and configuration control. A practical first step is to formalize triggers, decision gates, and minimum documentation requirements, even if your systems remain unchanged. From there, you can incrementally improve by tying change records to work orders in your existing MES/ERP, and by using simple physical controls on the line to separate configurations. Over time, you can target the highest-risk gaps—such as unsynchronized BOMs or poor serial-level tracking—rather than trying to redesign the entire stack around this one class of event.