An engineering change process that reaches production

No. The labels vary. What matters is distinguishing the proposal, the authorized implementation scope and communication of the effective change. If your company uses one document, its stages and decision responsibilities still need to make those distinctions clear.

Assign one coordinator to keep the change moving, but leave technical and functional decisions with the people qualified to make them. Purchasing can confirm supply and run-out; it should not become the default approver of engineering suitability.

Define the difference between release-critical work and follow-up that may legitimately continue afterward. For example, verifying a changed inspection method may be critical while reviewing longer-term supplier performance may not. Record the rationale rather than marking all actions optional to meet a date.

Contain the issue under the appropriate quality procedure and assess the released revision through a new, traceable change or approved reversal process. Do not erase the previous release evidence or silently restore an old revision number.

Start with one part or instruction change, a small review group and a clear handoff to production. Include a returned request or blocked implementation task, not only a smooth success. Expand after the team can explain which revision is current and why.