Shannon McGarry
Learn what engineering change management is, how ECRs, ECOs, and ECNs work, and how manufacturers improve traceability, compliance, and collaboration across the product lifecycle with Autodesk Vault and Fusion Manage.
What is engineering change management?
Engineering Change Management (ECM) is the formal process used to propose, evaluate, approve, implement, and document changes to a product design, bill of materials (BOM), manufacturing process, or related engineering data. The goal of ECM is to ensure every product change is reviewed, communicated, and executed in a controlled manner before it reaches manufacturing, suppliers, or customers.
A well-managed engineering change process helps organizations reduce errors, improve product quality, maintain regulatory compliance, and make sure that everyone is working from the most current and approved information. ECM creates a clear record of what changed, why it changed, who approved it, and when it was implemented.
As products grow more complex and teams become increasingly distributed, formal change management becomes essential for maintaining accuracy, traceability, and alignment across engineering, manufacturing, procurement, quality, and supply chain teams.
Engineering change management vs. enterprise change management
Although they share similar terminology, engineering change management and enterprise change management address very different types of change.
| Engineering Change Management (ECM) | Enterprise Change Management |
|---|---|
| Governs changes to physical products and related engineering data | Governs organizational, process, and business changes |
| Focuses on CAD files, BOMs, drawings, specifications, and manufacturing processes | Focuses on people, policies, software rollouts, training, and organizational adoption |
| Requires design reviews, approvals, and technical validation | Requires stakeholder alignment, communication planning, and change adoption strategies |
| Often subject to regulatory and quality requirements | Generally driven by business transformation initiatives |
| Uses ECRs, ECOs, and ECNs to control product changes | Uses project management and organizational change frameworks |
Confusing the two can create unnecessary risk. Product changes often require formal documentation, traceability, and regulatory evidence that organizational change management processes are not designed to provide.
Why engineering change management matters
Every product eventually changes. A component becomes obsolete. A design flaw is discovered. A supplier changes materials. Regulatory requirements evolve. Manufacturing identifies a more efficient production method.
Without a formal change process, teams often rely on spreadsheets, email threads, shared drives, and verbal communication to coordinate updates. This creates opportunities for:
- Version mismatches between engineering and manufacturing
- Outdated drawings reaching the shop floor
- Incorrect BOMs being released
- Missed supplier notifications
- Compliance documentation gaps
- Costly rework and scrap
Engineering change management creates a controlled system for managing these updates so that every stakeholder works from approved, accurate information.
Understanding the ECR, ECO, and ECN lifecycle
Most engineering organizations manage changes through three core artifacts:
- Engineering Change Request (ECR): A request proposing a change
- Engineering Change Order (ECO): The approved authorization to implement the change
- Engineering Change Notice (ECN): The communication that informs affected stakeholders that the change is now in effect
While terminology varies between organizations, the overall lifecycle follows a similar pattern.
1. Request initiation
The process begins when an Engineering Change Request (ECR) is submitted. The request identifies:
- The problem or improvement opportunity
- Affected products or assemblies
- Supporting documentation
- Business justification
- Change urgency and priority
This step establishes a formal record that initiates evaluation and ensures the request is visible to relevant stakeholders.
2. Impact analysis
Engineering teams assess the potential impact of the proposed change before any approval occurs. Impact analysis typically includes reviewing:
- Assemblies and subassemblies
- CAD models and drawings
- Engineering and manufacturing BOMs
- Inventory and work-in-progress
- Supplier dependencies
- Production processes
- Regulatory implications
The goal is to understand both technical and business consequences before moving forward.
3. Review and approval
Once impact analysis is complete, stakeholders review the proposed ECO through a structured approval workflow. Participants often include:
- Engineering
- Manufacturing
- Quality
- Procurement
- Supply chain
- Program management
This stage ensures all affected functions understand the change and approve implementation before release.
4. Implementation
After approval, the change is executed across affected products, documents, and manufacturing records. Inventory disposition decisions are documented, and revised deliverables are released.
Optimize Data Management with Autodesk Vault
Secure, organize, and manage your engineering data efficiently.
Organizations using Autodesk Vault can manage ECO workflows through lifecycle stages such as:
- Create
- Review
- Approve
- Release
- Audit
Autodesk Fusion Manage: Connect People, Processes, and Data
Streamline workflows, enhance collaboration, and gain real-time visibility with PLM.
For organizations operating across multiple locations, Autodesk Fusion Manage extends change management through cloud-based approval workflows, configurable routing, and cross-site collaboration, helping ensure all stakeholders receive the appropriate change information at the appropriate time.
5. Documentation and traceability
The final stage creates a permanent record of the approved change. Complete traceability includes:
- Original request
- Approval history
- Revision information
- Affected items
- BOM updates
- Supporting documents
- Implementation records
A full audit trail allows organizations to demonstrate compliance, investigate quality issues, and understand how products evolved over time.
The critical EBOM-to-MBOM handoff
Many change management discussions end when an ECO is approved.
In reality, approval is only part of the process. Manufacturing cannot execute a change until the engineering bill of materials (EBOM) has been translated into an accurate manufacturing bill of materials (MBOM).
When an ECO is approved:
- Engineering releases updated designs
- Manufacturing receives updated production requirements
- Procurement evaluates material impacts
- Production planning updates manufacturing records
A disconnected handoff between engineering and manufacturing creates significant risk. Approved engineering changes may never reach the shop floor, suppliers may continue ordering outdated components, and production may operate from obsolete instructions.
Organizations using Fusion Manage can connect product structures, BOM management, and change workflows so that approved changes become the authorizing record for downstream manufacturing activities, helping maintain alignment between engineering and production.
Engineering change management in regulated industries
Medical devices
Medical device manufacturers must maintain rigorous change-control practices and demonstrate that design changes are reviewed, validated, and documented as part of their quality management system.
FDA Quality Management System Regulation requirements under 21 CFR Part 820 require manufacturers to establish and maintain documented quality processes and records.
For medical device organizations, change records often need to show:
- What changed
- Why the change occurred
- Validation results
- Approval history
- Implementation evidence
Vault’s revision control and audit history capabilities, combined with Fusion Manage’s workflow and change history records, help support these traceability requirements.
Aerospace
AS9100 places significant emphasis on configuration management, document control, and change control throughout the product lifecycle.
Aerospace manufacturers must demonstrate that released designs, drawings, and product configurations are controlled and traceable throughout development and production.
Revision-controlled drawings, BOM snapshots, released records, and documented approval histories help organizations establish evidence for configuration management activities.
Vault supports controlled revision management while maintaining historical records of released product data.
Defense
Defense manufacturers frequently operate under strict controls surrounding export-controlled technical data and product records.
Changes affecting controlled assemblies or components must be managed through documented approval processes with appropriate access controls and authorization procedures.
Fusion Manage provides configurable role-based permissions, controlled routing workflows, and centralized change records that can support organizations managing controlled engineering information.
Connecting engineering change management across the product lifecycle
Engineering change management is most effective when change records, engineering data, and business processes are connected.
Many organizations begin by controlling CAD files and revisions in a PDM system. As products become more complex, they often expand to broader PLM capabilities that connect approvals, BOMs, quality processes, supplier collaboration, and manufacturing operations.
Vault provides engineering data control, revision management, and product data management, while Fusion Manage extends those capabilities with workflow automation, approvals, lifecycle management, and cross-functional collaboration. Together they help create a connected process spanning engineering, manufacturing, quality, procurement, and product management.
Frequently asked questions
An ECR initiates the change. It documents a problem, corrective action, or proposed improvement and triggers review. An ECO is the approved authorization to implement that change, defining affected items, timelines, responsibilities, and disposition requirements. An ECN is the communication that notifies affected stakeholders that the approved change is now in effect. Keeping these records separate improves traceability and auditability throughout the change process.
Without a formal engineering change management process, changes often spread through email, spreadsheets, and informal conversations. This increases the likelihood of version conflicts, manufacturing errors, missed approvals, and incomplete compliance records. ECM provides a controlled process that documents what changed, why it changed, who approved it, and when implementation occurred.
Common artifacts include Engineering Change Requests (ECRs), Engineering Change Orders (ECOs), Engineering Change Notices (ECNs), redlined drawings, affected-item lists, updated BOMs, inventory disposition instructions, approval records, and audit logs. Together these artifacts create a complete history of product changes.
ECM provides the framework for executing sustainability-related product changes in a controlled manner. Organizations can use formal change workflows to manage material substitutions, eliminate restricted substances, qualify alternative suppliers, update packaging, and document compliance activities. The result is a traceable record demonstrating both implementation and regulatory compliance.
PLM helps organizations define who can change product data, when changes can occur, and what approvals are required. Configurable workflows, lifecycle states, role-based permissions, and audit trails create governance controls that improve accountability and consistency across the product lifecycle.
ECM manages changes to products, designs, BOMs, specifications, and manufacturing processes. Enterprise change management manages organizational transformation, software adoption, training, business process improvements, and cultural change. They serve different objectives and require different controls.
ECM creates a documented record of every approved change, including affected items, revision histories, approvals, implementation activities, and supporting documentation. This allows organizations to determine which design version, BOM, and approved change history correspond to a particular product release.
Uncontrolled changes create gaps in product records and increase the risk of manufacturing errors, supplier confusion, and compliance issues. Teams may work from different versions of product data, and there may be no reliable record showing who authorized the change or when it occurred. In regulated industries, this can result in nonconformances and audit findings.