Skip to content

What is an ECR?

An Engineering Change Request (ECR) is the formal starting point for any change. It captures the reason, scope, and urgency of a proposed change before any engineering work begins.

Create an ECR when:

  • A supplier notifies you of a part discontinuation or revision
  • An engineer identifies a design improvement or correction
  • A customer requirement changes the specification
  • A field failure requires a component swap
  • A regulatory update mandates a material or process change
FieldRequiredPurpose
TitleYesShort description of the change
DescriptionYesDetailed explanation of what and why
Trigger sourceYesWhat initiated this change (supplier notification, engineering finding, customer requirement, field failure, regulatory, other)
ClassificationYesEmergency, major, or minor — determines review path
SeverityYesCritical, high, medium, or low — indicates business impact
Safety flagNoToggle on if safety-critical
Change typeNoHardware, software, mechanical, electrical, documentation, or process
Affected itemsNoParts or assemblies impacted by the change
AttachmentsNoSupporting documents (PDF, Word, Excel, images — max 25 MB each, up to 10 files)

An ECR moves through these states:

1
Draft
Created but not yet submitted. All fields are editable. Add affected items and attachments here.
2
Submitted
Awaiting initial review by the coordinator.
3
Under review
Coordinator is screening the request. They can approve directly (minor changes) or escalate to the CCB.
4
CCB review
The Change Control Board evaluates the request and records a formal decision.
5
Decision
Approved (creates an Engineering Change automatically), rejected (with rationale — can be resubmitted), or on hold (pending conditions).

Before submitting, use the Check for duplicates button. Redline uses AI to compare your title, description, and affected items against recent ECRs. If a similar request already exists, you will see a match with a one-sentence explanation of why it was flagged.

This prevents duplicate work — especially when multiple engineers independently discover the same issue.

When the CCB or coordinator approves an ECR:

  1. An Engineering Change (EC) is automatically created in draft status
  2. The EC inherits the ECR title, description, trigger source, severity, classification, and change type
  3. Affected items and preliminary actions are carried over
  4. The coordinator assigned during approval becomes the EC owner

From here, the coordinator uploads a BOM and continues with the ECO workflow.