An engineering change notice (ECN) is issued and signed in the shop, yet machines still run old parameters. Incidents find execution never switched version: work orders, work instructions, first-piece cards still on the previous revision. Change stopped at notification—meaning no change. Quality incidents sprout here—not because nobody published, but because publication never entered the work-order state machine.
Notice is a legal act. Execution is a work-order act. Both must share one version number.
ECN Must Close Old Work-order Entry
After effective date, old process cannot be released. WIP either reworks to new revision or gets deviation approval to finish old. Work instructions push with the work order—wall paper is not authority. Training completion is a release gate; untrained staff cannot open new orders.
- Changes include effective batch or date—no "immediate" without boundary.
- QC samples to new revision—old revision is intercept.
- Supplier incoming standards change in sync—avoid changing only internally.
Execution Trusts Work Orders—not Posters
The XYN digital intelligence system locks process version on work orders; ECN effective cuts old entry. Notices can still be signed—but signature is no longer execution. Change protects quality only when it reaches execution; otherwise it only protects publication records.
Sample one work order this week—is process version equal to latest effective ECN? If not, fix release before wording the next notice.
