ECR vs ECO vs ECN: What Every Quality Manager Needs to Know
The Three Documents of Engineering Change Management
Engineering change management uses three distinct documents, each serving a different purpose in the change workflow. Understanding the differences is essential for ISO 9001 compliance and for maintaining a clean audit trail.
| Document | Purpose | Who Creates It | When |
|---|---|---|---|
| ECR (Engineering Change Request) | Proposes a change and explains why it is needed | Anyone who identifies a need for change | At the start of the process |
| ECO (Engineering Change Order) | Authorises and instructs the implementation of an approved change | Quality manager or engineering lead, after CCB approval | After the ECR is reviewed and approved |
| ECN (Engineering Change Notice) | Communicates the approved change to all affected parties | Quality manager or document controller | After the ECO is issued |
Engineering Change Request (ECR)
The ECR is the starting point of every engineering change. It documents what needs to change, why, and the potential impact.
What an ECR Contains
- Change description — what specifically needs to change (drawing, BOM, process, specification, work instruction)
- Reason for change — the trigger (customer complaint, non-conformance, design improvement, supplier issue, regulatory update)
- Affected items — parts, assemblies, documents, and processes impacted by the proposed change
- Supporting evidence — test results, customer correspondence, NCR reference numbers, photographs
- Urgency — routine, urgent, or emergency classification
Who Can Raise an ECR?
In most manufacturing organisations, anyone can raise an ECR. Common initiators include:
- Quality managers (triggered by NCRs, audit findings, or CAPA outcomes)
- Design engineers (triggered by design improvements or error corrections)
- Production staff (triggered by process issues or producibility improvements)
- Purchasing (triggered by supplier changes or material availability issues)
- Customers (triggered by specification changes or complaints)
The key is that the process is open — restricting who can raise ECRs risks missing important changes.
ECR Example
A CNC machining company receives a customer complaint that a bracket mounting hole is consistently 0.2mm off-centre. The quality manager raises an ECR:
- Change: Revise drawing DWG-2045 to update hole position datum reference
- Reason: Customer complaint CR-2026-041; non-conformance NCR-2026-015
- Affected items: Drawing DWG-2045 Rev C, CNC programme PROG-2045, inspection plan IP-2045
- Evidence: CMM measurement report showing 0.18-0.22mm offset across 15 samples
Engineering Change Order (ECO)
The ECO is issued after the ECR has been reviewed by the Change Control Board (CCB) and approved. It is the formal authorisation to implement the change.
What an ECO Contains
- Approved change description — refined from the ECR, with implementation-specific detail
- Implementation instructions — step-by-step guidance for each affected area
- Affected documents — list of every document that must be revised, with current and new revision numbers
- Effectivity — when the change takes effect (immediate, from serial number X, from date Y, at next production run)
- Disposition of existing stock — what to do with work-in-progress and finished goods produced before the change (use as-is, rework, scrap)
- Approval signatures — timestamped signatures from the CCB members who approved the change
ECO vs ECR: Key Differences
The ECR asks "should we make this change?" The ECO says "here is exactly how to make this change."
| Aspect | ECR | ECO |
|---|---|---|
| Purpose | Request and justify | Authorise and instruct |
| Status | Proposed | Approved |
| Detail level | High-level impact | Implementation-specific |
| Signatures | Requester | CCB approvers |
| Triggers action? | No — triggers review | Yes — triggers implementation |
ECO Example
Following the bracket hole ECR above, the CCB approves the change. The ECO specifies:
- Drawing revision: DWG-2045 Rev C → Rev D, with updated datum reference for hole position
- CNC programme: PROG-2045 updated with corrected coordinates
- Inspection plan: IP-2045 updated with tightened tolerance check at first-off
- Effectivity: Immediate — next production run
- Existing stock: 45 brackets in stock to be 100% inspected; non-conforming units reworked
Engineering Change Notice (ECN)
The ECN communicates an approved change to everyone who needs to know about it. It ensures that no department continues working to the old specification.
What an ECN Contains
- Change summary — brief description of what changed and why
- ECO reference — link to the full ECO for detail
- Affected departments — who needs to take action
- Effective date — when the change is live
- Document revisions — which documents have been updated and where to find the current versions
- Acknowledgement — confirmation that each affected person has received and understood the change
ECN vs ECO: Key Differences
The ECO tells the implementation team exactly what to do. The ECN tells everyone else what has changed.
| Aspect | ECO | ECN |
|---|---|---|
| Audience | Implementation team (engineering, production, quality) | All affected parties (wider distribution) |
| Purpose | Instruct implementation | Communicate and confirm awareness |
| Detail level | Full implementation instructions | Summary with reference to ECO |
| Action required | Implement the change | Acknowledge receipt and update working practices |
ECN Example
After the bracket hole change is implemented, the ECN notifies:
- Production: new CNC programme PROG-2045 effective from lot 2026-048
- Goods inward inspection: updated inspection plan IP-2045 now includes first-off datum check
- Purchasing: no supplier impact — internal process change only
- Stores: remaining old-revision brackets marked as "rework required"
The Complete Workflow
The three documents form a sequence:
- ECR — "We think this needs to change, and here is why"
- ECO — "The change is approved. Here is exactly what to do"
- ECN — "The change is done. Here is what you need to know"
Each document builds on the previous one, creating a complete audit trail from initial request through implementation to confirmation.
ISO 9001 Audit Implications
ISO auditors do not require you to use the specific terms ECR, ECO, and ECN. What they require is evidence that:
- Changes are formally requested and justified (the ECR function)
- Changes are reviewed for impact and approved by authorised persons (the ECO function)
- Changes are communicated to affected parties and documents are updated (the ECN function)
Your change management process can use different terminology — change request, change authorisation, change notification — as long as the three functions are covered and documented.
Summary
ECR, ECO, and ECN are three distinct documents serving different purposes in the engineering change workflow. The ECR proposes and justifies a change, the ECO authorises and instructs its implementation, and the ECN communicates the completed change to all affected parties. Together, they provide the documented evidence trail that ISO 9001 requires for clauses 8.3.6 and 8.5.6.