Engineering & Change Management template
Engineering Change Request (ECR) Template: Build & Export Free
Propose a change (the problem, the affected items and the justification) and route it for review, then export a print-ready ECR as a PDF, free to start.
Free to try · No credit card · Exports a clean PDF
A live Engineering Change Request 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 request?
An engineering change request (ECR) is the formal proposal that starts a change: it describes a problem or opportunity, the change being proposed, the items it would affect and why it's worth doing, so the change can be evaluated before anyone commits to it. It's the front end of the engineering change process.
A good ECR gives reviewers what they need to decide. It states the problem clearly, describes the proposed change, lists the affected parts, drawings and documents, and assesses the impact (cost, schedule, quality, inventory) with a priority. It's routed to the reviewers or a change board, and, if approved, it becomes the basis for an engineering change notice that actually implements the change.
ECRs are standard in manufacturing, hardware and regulated product development. They sit at the head of change management, ahead of the engineering change notice (ECN/ECO): the ECR proposes and evaluates; the ECN authorizes and communicates (more below).
The fields
What to include in an engineering change request
An ECR reviewers can act on is specific and impact-aware. These are the fields they expect, and all of them are in the template.
Request number, date and requester
A unique ECR number, the date and who's requesting, so the request is tracked and attributable.
Problem or reason for change
The problem, defect or opportunity driving the request, stated clearly enough to justify a change.
Proposed change
A description of the change being proposed: what would actually be different.
Affected items
The parts, assemblies, drawings and documents the change would touch.
Impact assessment
The impact on cost, schedule, quality, inventory and existing product: the basis for the decision.
Priority and urgency
How urgent the change is and why, so it can be triaged against other requests.
Disposition of current stock
What would happen to existing stock and work in progress if the change is approved.
Reviewers and approvers
The people or change board who review and decide on the request.
Decision
The outcome (approved, rejected or on hold) with any conditions.
Linked change notice
A reference to the engineering change notice (ECN/ECO) raised to implement an approved request.
Step by step
How to fill out an engineering change request
Four passes take you from a blank template to a routed, decision-ready ECR.
Describe the problem and proposed change
Add the ECR number, date and requester, state the problem or reason, and describe the change being proposed.
Identify affected items
List every part, drawing and document the change would affect. The more complete this is, the better the impact assessment.
Assess the impact
Assess the impact on cost, schedule, quality, inventory and existing stock, and set a priority so reviewers can triage it.
Route for review and export
Route it to the reviewers or change board for a decision, then export a print-ready PDF and link any resulting ECN.
Which one
ECR vs. ECO / ECN
They're the two halves of a change. One proposes and evaluates; the other authorizes and implements.
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.
Engineering Change Order (ECO / ECN)
The document that defines and authorizes an approved change and communicates it: affected items, before/after revisions and effectivity.
Use to implement and communicate a change that's been approved.
See the Engineering Change Order (ECO / ECN) template →Get it right
Common mistakes to avoid
- A vague problem statement that doesn't justify the change.
- Missing affected items, so the impact is underestimated.
- No impact assessment on cost, schedule, quality or inventory.
- No plan for the disposition of existing stock and WIP.
- Skipping review or approval before the change moves forward.
- No traceability from the ECR to the ECN that implements it.
Questions
Frequently asked
What is an engineering change request?
An engineering change request (ECR) is a formal proposal to make a change: it describes a problem or opportunity, the proposed change, the affected items and the impact, so the change can be evaluated and approved before it's implemented. It's the first step in the engineering change process.
What's the difference between an ECR and an ECN (or ECO)?
An ECR proposes and evaluates a change; an ECN (engineering change notice), also called an ECO (engineering change order), authorizes and communicates an approved change and defines how it's implemented. The ECR comes first; an approved ECR leads to an ECN.
What should an engineering change request include?
A request number, date and requester, the problem or reason, the proposed change, the affected items, an impact assessment, a priority, the disposition of current stock, the reviewers and the decision, plus a link to any resulting ECN. This template includes all of them.
Who approves an engineering change request?
Usually a change control board (CCB) or a defined set of reviewers spanning engineering, quality, manufacturing and sometimes purchasing: whoever the change would affect. The point is that the impact is assessed by the right people before the change is approved.
How does an ECR become an ECN?
Once an ECR is approved, an engineering change notice (ECN/ECO) is raised to implement it, defining the affected items and revisions, the effectivity, the disposition of existing stock and the actions needed. The ECN references the ECR so the change is traceable end to end.
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 Request
Engineering Change Notice (ECN)
Communicates an approved engineering change, affected items, before-and-after details, effectivity, implementation and release information.
Open template →Deviation / Waiver Request
Requests documented authorization to temporarily or specifically depart from a defined drawing, specification, process or other requirement.
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 →Build your Engineering Change Request 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 request. You remain responsible for the accuracy of the impact assessment and the completeness of the affected items, and for routing the request through your organization's change-control process before any change is made.