Engineering & Change Management template
Engineering Change Order (ECO / ECN) Template: Build & Export Free
Communicate an approved change (what changed, on which items and when it takes effect), then export a print-ready ECO/ECN as a PDF, free to start.
Free to try · No credit card · Exports a clean PDF
A live Engineering Change Order (ECO / ECN) rendered from this template, and yours opens the same way, in your brand, and exports to a clean PDF.
Overview
What is an engineering change order?
An engineering change order (ECO), also called an engineering change notice (ECN), is the document that defines, authorizes and communicates an approved engineering change. Where the change request proposes a change, the ECO/ECN is what actually implements it: it says exactly what is changing, on which items, and when the change takes effect.
A good ECO leaves nothing ambiguous. It references the approved request, lists every affected part, drawing and document with its before and after revision, sets the effectivity (a date, serial or lot from which the change applies), states the disposition of existing stock and work in progress, and assigns the implementation actions and approvals. Done well, everyone downstream knows precisely what to build from when.
ECOs/ECNs are core to configuration and change management in manufacturing and hardware. They follow an approved engineering change request and, for changes customers need to know about, often trigger a product change notification (more below).
The fields
What to include in an engineering change order
An ECO people can implement is complete and unambiguous. These are the fields they expect, and all of them are in the template.
ECO/ECN number and revision
A unique change-order number and its revision, so the change itself is identified and controlled.
Reference to the request
The engineering change request (ECR) this order implements, for end-to-end traceability.
Description of change
A clear description of what is changing, precise enough to act on without interpretation.
Reason for change
Why the change is being made, carried over from the approved request.
Affected items and revisions
Every affected part and assembly with its before and after revision level.
Affected documents
The drawings, specifications and other documents that change, and their new revisions.
Effectivity
When the change takes effect: a date, serial number or lot from which it applies.
Disposition of stock and WIP
What happens to existing finished stock and work in progress: use, rework, scrap.
Implementation actions
The actions required to implement the change, with owners and due dates.
Approvals
The sign-offs that authorize the change to be released.
Step by step
How to fill out an engineering change order
Four passes take you from a blank template to an approved, implementable ECO.
Reference the approved change
Add the ECO/ECN number and revision, reference the approved ECR, and describe the change and the reason for it.
List affected items and revisions
List every affected part and document with its before and after revision, so there's no doubt what changes.
Set effectivity and disposition
Set the effectivity (the date, serial or lot the change applies from) and the disposition of existing stock and work in progress.
Assign actions, approve and export
Assign the implementation actions with owners, capture the approvals, then export a print-ready PDF.
Which one
ECO / ECN vs. ECR
They're the two halves of a change. One authorizes and implements; the other proposed and evaluated it first.
Engineering Change Order (ECO / ECN)
The document that defines and authorizes an approved change and communicates it: affected items and revisions, effectivity and stock disposition.
Use to implement and communicate a change that's been approved.
Engineering Change Request
The proposal that starts a change (the problem, the proposed change and its impact), routed for evaluation before anything is committed.
Use to propose and evaluate a change before it's approved.
See the Engineering Change Request template →Get it right
Common mistakes to avoid
- No effectivity, so no one knows from when to build to the change.
- Missing before/after revisions on the affected items.
- No disposition for existing stock and work in progress.
- Not listing every affected drawing and document.
- Releasing without the required approvals.
- No link back to the ECR that authorized the change.
Questions
Frequently asked
What is an engineering change order?
An engineering change order (ECO), also called an engineering change notice (ECN), is the document that defines, authorizes and communicates an approved engineering change: the affected items and revisions, the effectivity, the disposition of existing stock and the implementation actions. It's how an approved change is actually put into effect.
What's the difference between an ECO and an ECN?
They're the same thing under two names, engineering change order and engineering change notice, used interchangeably across industries and PLM systems. Both define and authorize an approved change. Some organizations distinguish the "order" (the authorization) from the "notice" (the communication), but most treat them as one document.
What's the difference between an ECN and an ECR?
An ECR (engineering change request) proposes and evaluates a change; an ECN/ECO authorizes and implements the approved change. The request comes first and is about whether to change; the notice/order is about how and when the change happens.
What should an engineering change order include?
The ECO/ECN number and revision, a reference to the ECR, the description and reason for the change, the affected items and documents with before/after revisions, the effectivity, the disposition of stock and WIP, the implementation actions, and the approvals. This template includes all of them.
What is effectivity in an ECO?
Effectivity is the point from which a change applies, expressed as a date, a serial number or a lot/batch. It tells manufacturing exactly when to switch from the old configuration to the new one, so parts built before and after the change are unambiguous.
Related templates
Read the guideEngineering change: ECR, ECN and PCN explained
Change control keeps a product’s documentation honest as the product evolves. Here’s the difference between an ECR, an ECN and a PCN, what an engineering change notice contains, and how a controlled change flows from request to updated documents.
Read the guide →Documents that go with a Engineering Change Order (ECO / ECN)
Engineering Change Request (ECR)
Proposes and evaluates a potential engineering change before formal approval, including rationale, affected items, impact and requested action.
Open template →Product Change Notice (PCN)
Communicates an upcoming change to an existing product, material, process, specification, manufacturing location or other product characteristic.
Open template →Control Plan
Documents key process steps, product or process characteristics, controls, measurement methods, sampling and reaction plans used to manage manufacturing quality.
Open template →Build your Engineering Change Order (ECO / ECN) now
Fill in the fields, apply your brand, and export a clean PDF. Free to start.
Note: This template gives you a structured starting point for an engineering change order / notice. You remain responsible for the accuracy and completeness of the affected items, revisions, effectivity and dispositions, and for releasing the change through your organization's change-control process.