How should aerospace manufacturers manage in-process work when instructions change?

Aerospace manufacturers should manage in-process work under formal change control, not by silently replacing instructions at the point of use.

When an instruction changes, the first question is not “how fast can we push the update?” It is “what is the disposition of work already started?” In regulated, traceability-heavy environments, open work orders, partially completed assemblies, and serialized units may need different treatment depending on where they are in the routing, what characteristics are affected, and whether the change is editorial, process-critical, tooling-related, or product-impacting.

What the control approach usually looks like

• Freeze the prior revision for affected in-process units until a review determines whether they can continue, must be paused, or require rework.
• Assess effectivity explicitly by part number, serial number, lot, operation, date, and where relevant by tooling, machine program, or inspection method.
• Classify the change so minor clarifications are not handled the same way as changes to torque values, inspection points, material usage, sequencing, or acceptance criteria.
• Route the disposition through the right quality and engineering workflow, which may include review, deviation, concession, rework instructions, updated inspection requirements, or NCR handling.
• Record what revision was used at each completed step so the as-built record shows exactly which instruction governed the work actually performed.
• Release the new revision with controlled acknowledgements only after approvals, training impact review, and downstream system synchronization are complete enough to avoid conflicting directions.

In short, manufacturers should manage instruction changes with version control plus an in-process disposition workflow. The right answer is often mixed: some units continue on the old revision, some are reworked to the new revision, and some are placed on hold pending engineering or quality disposition.

What determines the disposition

The correct path depends on site-specific configuration and process maturity, but the main decision factors are usually:

• Whether the change affects form, fit, function, safety-critical features, or required inspection evidence
• Whether work has not started, is partially complete, or has already passed downstream verification
• Whether the product is serialized, lot-controlled, or otherwise subject to genealogy requirements
• Whether the change affects tooling, machine parameters, software, fixtures, or test methods
• Whether customer, program, or internal approval thresholds apply before use
• Whether operators have already been trained and whether updated training records are required before execution

A purely editorial update may allow rapid cutover. A process change that alters execution steps, acceptance criteria, or evidence requirements often does not.

Why simple replacement is risky

Simply publishing a new instruction and expecting all active work to follow it creates predictable failure modes:

• Operators complete a job with mixed revisions and no clear evidence trail
• Inspection records no longer match the governing instruction revision
• ERP, MES, PLM, and QMS hold conflicting versions or effectivity dates
• Training acknowledgements lag the released instruction
• Rework is performed informally without approved dispositions
• Auditors or internal reviewers cannot reconstruct what happened to each unit

That does not automatically mean a noncompliance finding, but it does create avoidable traceability and evidence problems.

System coexistence in brownfield environments

In many aerospace plants, instruction changes originate in PLM or document control, execution happens in MES or paper/digital travelers, and dispositions live in QMS workflows, with ERP carrying order and revision context. That split matters.

If those systems are not tightly integrated, manufacturers need explicit controls for:

• Which system is the source of truth for released instruction revisions
• How work orders inherit or lock an instruction revision at release
• How holds and disposition decisions are communicated to the shop floor
• How rework or deviation instructions are linked back to the original job and unit
• How training status is checked before the new instruction becomes executable

Full replacement of MES, ERP, PLM, and QMS just to solve revision handling is often unrealistic in aerospace-grade environments. It commonly fails because of validation cost, qualification burden, downtime risk, integration complexity, and the fact that long-lived assets and established evidence trails cannot be disrupted casually. In practice, most manufacturers improve revision governance through targeted integration, status controls, and better effectivity logic rather than wholesale system replacement.

Minimum operational controls worth having

• Versioned instructions with approval history and effective dates
• Work order or unit-level locking of the governing revision at job start
• Automated or manual hold rules for in-process work when critical revisions change
• Disposition workflow for continue as is, switch at next operation, rework, scrap, or deviation
• Electronic or procedural capture of who performed work, when, and to which revision
• Change impact review across quality, engineering, operations, and training
• Traceable linkage between instruction changes and resulting NCR, CAPA, or rework records where applicable

If those controls are missing, the organization is likely relying on tribal knowledge and supervisor intervention, which is fragile under shift changes, outsourcing, or high-mix conditions.

Bottom line

Manufacturers should manage in-process work instruction changes by controlling effectivity and disposition at the unit or lot level, not by forcing a blanket cutover. Some work can continue on the prior revision, some must stop, and some requires formal rework or deviation. The right answer depends on the nature of the change, the execution state of the product, and how well document control, MES, QMS, ERP, and training records stay aligned.