Engineering Change Management (ECN/ECO) — From "Just Make the Change" to "Controlled Change"
In the process of product development and production, changes are inevitable. Customer requirements change, supplier materials are replaced, drawings are incorrect, and processes are modified... Every day, companies face various change requests.
However, the gap in change management often determines the maturity of the quality management system. Some companies simply make the change, only to later discover that upstream and downstream processes are out of sync, documents are not updated, and inventory is scrapped. In contrast, mature companies ensure that changes are controlled—each change has a closed loop, traceability, and verification.
1. What is Engineering Change Management?
Engineering Change Management (ECM) refers to the full-process control of changes in design, process, materials, and equipment throughout the product lifecycle, following the steps of proposing → reviewing → approving → implementing → verifying.
Common change carriers include:
- ECN (Engineering Change Notice): Engineering change notification
- ECO (Engineering Change Order): Engineering change instruction
- ECR (Engineering Change Request): Engineering change application
The relationship among these is: ECR → review → ECO → execution → ECN (notify relevant parties).
2. Types of Changes: Design Changes and Process Changes
1. Design Changes
These refer to changes at the product design level, including:
- Modifications to dimensions, tolerances, and material specifications
- Adjustments to functional or performance parameters
- Updates to drawings and BOM (Bill of Materials)
- Replacement or addition/removal of components
Design changes typically require cross-departmental review (R&D, Quality, Procurement, Manufacturing) to assess the impact on cost, delivery, quality, and reliability.
2. Process Changes
These refer to changes at the manufacturing process level, including:
- Adjustments to process flow or work sequence
- Replacement of equipment, tooling, or molds
- Modifications to process parameters (temperature, pressure, speed, etc.)
- Changes to inspection methods or frequency
Process changes are often overlooked—R&D modifies the design without informing production, or production changes the process without notifying quality, both of which can lead to batch issues.
3. Five Key Steps in Change Management
Step 1: Change Proposal and Recording
The source of the proposal can be any department. The key is to use a unified change application form to record: change cause, change content, impact scope, and urgency.
Step 2: Change Review (CCB)
Establish a Change Control Board (CCB) or designate a review leader to evaluate the change impact from the following dimensions:
- Technical feasibility
- Quality and reliability risks
- Cost impact (rework, scrap, mold changes)
- Delivery impact (inventory consumption, breakpoint switching)
- Regulatory compliance
Step 3: Change Approval and Planning
After the review is passed, develop a change implementation plan, including:
- Switching time point (breakpoint)
- Handling methods for old materials/products (consumption, rework, scrap)
- Document update arrangements (drawings, BOM, control plan, PFMEA)
- Training for relevant personnel
Step 4: Change Implementation and Verification
Execute the change according to the plan and perform first article verification—confirm that the changed product meets the requirements. Only after verification can the batch switch be made.
Step 5: Change Closure and Traceability
After the change is completed, update the documents, notify all relevant parties, and archive the change records. A good traceability system can ensure that: on a certain date, for a certain reason, who approved what change, and which batch numbers of products were affected—all can be traced.
4. Common Issues in Change Management
- Verbal Changes—Changes made based on a single word from a leader, without written records, making it difficult to hold parties accountable later
- Changes Made Without Review—Believing small changes do not require review, resulting in a chain of problems
- Lack of Breakpoint Control—Old and new materials coexist on the production line, leading to material mix-ups
- Delayed Document Updates—Changes have been in place for half a year, but drawings and BOMs are still outdated
- Failure to Notify Suppliers—Design changes are made, but suppliers continue to supply according to old drawings
5. Summary
Engineering change management is not about being strict, but about being correct. An effective change management system ensures that each change is traceable, accountable, and verifiable. For quality managers, change management is a crucial tool for preventive quality—rather than troubleshooting after a change, it is better to identify risks before the change.
Change management must be a closed-loop and traceable process
Knowledge code: 8.4.1
Version: v20260608
Author: Quality Think Tank