ECR/ECN (Engineering Change Request/Notice)
Quick facts
| Category | Product design and specification change control |
|---|---|
| Used by | Manufacturing, medical devices, aerospace, automotive and other regulated industries |
| Also called | ECR, ECN, ECO (Engineering Change Order) |
| Related standards | ISO 9001, ISO 13485, AS9100, IATF 16949 |
| Related processes | Change control, document control, bill of materials, product design controls |
| Semantic match | engineering change request, engineering change notice, ECO process, design change control |
What is ECR/ECN (Engineering Change Request/Notice)?
An engineering change request, or ECR, is how a proposed change to a product's design, drawing, specification, or bill of materials is formally raised for evaluation. It typically describes what is being proposed, the reason for the change, and any known impact on cost, schedule, form, fit or function.
Once an ECR is reviewed and approved, often by a cross-functional change control board including engineering, quality, manufacturing and sometimes customer representatives, an engineering change notice, or ECN, is issued. The ECN documents exactly what changed, the approved effective date, and any related actions, such as updating drawings, notifying suppliers or customers, or adjusting inventory of superseded parts.
Some organizations use the related term ECO, or engineering change order, largely interchangeably with ECN, though usage varies by industry and company convention.
Why is ECR/ECN (Engineering Change Request/Notice) important?
Product designs and specifications change over the life of a product, whether to fix a defect, reduce cost, or respond to a new requirement. Without a formal ECR/ECN process, these changes can be implemented inconsistently, leaving some drawings, suppliers or inventory out of sync with the current approved design.
A disciplined ECR/ECN process ensures every design change is evaluated for its impact before approval and clearly communicated once approved, reducing the risk that a supplier builds to an outdated drawing or that inventory of a superseded part is used by mistake.
ECR/ECN records also create a traceable history of how a product's design evolved, which is valuable for troubleshooting field issues, supporting regulatory submissions, and answering customer questions about when and why a specific design change occurred.
How does ECR/ECN (Engineering Change Request/Notice) work?
A typical ECR/ECN process includes:
- Change request (ECR). Submit the proposed change with rationale and known impacts.
- Impact review. Evaluate effects on cost, schedule, form, fit, function and compliance.
- Cross-functional approval. Route the ECR to a change control board or designated approvers.
- Change notice (ECN). Issue the approved ECN documenting the change and its effective date.
- Implementation. Update drawings, specifications, bills of materials and related documents.
- Notification. Communicate the change to affected suppliers, customers or internal teams as required.
- Closure. Confirm all related updates and notifications are complete before closing the record.
ECR vs. ECN
| Comparison | ECR (Engineering Change Request) | ECN (Engineering Change Notice) |
|---|---|---|
| Stage | Before approval | After approval |
| Purpose | Propose and evaluate a design change | Communicate and implement the approved change |
| Typical content | Proposed change, rationale, impact assessment | Approved change details, effective date, affected documents |
Real-world examples of ECR/ECN (Engineering Change Request/Notice)
An electronics manufacturer submits an ECR to replace an obsolete component with an approved substitute. After engineering and quality approve the change, an ECN is issued specifying the new part number and the effective date for incorporating it into production.
A medical device company proposes a design change to improve manufacturability. The ECR triggers a design verification review, and the resulting ECN includes updated risk documentation as part of the device's design history file.
An automotive supplier issues an ECN for a dimensional tolerance change on a customer-supplied part. The supplier notifies the customer in advance, consistent with their quality agreement, before the change is implemented in production.
Regulations and standards related to ECR/ECN (Engineering Change Request/Notice)
ISO 9001, ISO 13485, AS9100 and IATF 16949 all require organizations to control changes affecting product conformity, which in practice includes formal engineering change processes for design and specification changes. ISO 13485 places particular emphasis on linking design changes to risk management and design history documentation.
Customer-specific requirements in automotive and aerospace industries frequently require advance notification or approval before a supplier implements an engineering change affecting form, fit, function or a part number the customer relies on.
Auditors typically expect ECR/ECN records to show a clear approval trail, documented impact assessment, and evidence that all affected documents, suppliers and inventory were updated consistently with the approved change.
Required by
How QT9 helps with ECR/ECN (Engineering Change Request/Notice)
QT9 QMS ECR/ECN capabilities
- Automate ECO/ECN approvals to reduce time-to-implementation.
- Log all design, part or document changes with complete history.
- Route change requests to a configurable change control board for approval.
- Collaborate across engineering, quality and manufacturing on one centralized platform.
- Stay audit-ready with ISO, FDA and GMP-aligned traceability.
- Provide compliant electronic signature approvals for internal teams, customers and suppliers.
Request an ECR/ECN Demo Explore Engineering Change Order Software →
See QT9 Software in Action
Discover how QT9 Software helps manufacturers improve efficiency, strengthen compliance and connect quality management and ERP processes within one integrated platform.
Common mistakes with ECR/ECN (Engineering Change Request/Notice)
Common mistakes include implementing a design change informally before the ECR has been fully evaluated and approved, and failing to notify all affected suppliers or customers before the change takes effect.
Other problems include not updating every document, drawing or bill of materials affected by a change, and allowing inventory of a superseded part to remain in use after a new revision has been released.
Frequently asked questions
Related quality management terms
Related content
Ready to Transform Your Business?
See how QT9 Software helps manufacturers simplify operations, improve traceability and drive continuous improvement with integrated quality management and ERP software.