engineering change request (ECR)

An engineering change request (ECR) is a formal, documented proposal to evaluate and potentially modify a product design, manufacturing process, specification, or controlled document. It is typically the first step in an engineering change process, capturing the need for change and requesting analysis and approval before any modification is implemented.

What an ECR includes

An ECR commonly includes:

• A description of the proposed change or the problem being addressed
• Reason or trigger for the change (for example, nonconformance, cost issue, safety concern, supplier change, customer request)
• Scope and affected items (such as part numbers, assemblies, BOMs, routings, work instructions, software versions, drawings)
• Preliminary impact considerations (on fit, form, function, quality, compliance, tooling, validation, inventory, and customers)
• Requested timing and priority
• Originator and date

The ECR is reviewed by engineering, quality, operations, supply chain, and other relevant functions to decide whether to proceed, modify, or reject the proposed change.

Role in configuration control and regulated manufacturing

In regulated and audited environments, ECRs are part of the configuration management and document control framework. They provide traceable evidence that:

• Changes to designs, specifications, and processes are not made ad hoc
• Impacts on safety, compliance, and quality are assessed before implementation
• There is a clear link between the request for change and the approved change record (often an engineering change order or ECO)
• Historic configurations can be reconstructed by tying ECRs, ECOs, and as-built / as-maintained records together

ECRs may reside in PLM, QMS, MES, or ERP systems, or in a dedicated change management tool, as part of an overall change control workflow.

How ECRs differ from other change records

• Engineering change request (ECR): The proposal and impact assessment stage. It records the idea, problem, or need and triggers cross-functional review.
• Engineering change order (ECO) or engineering change notice (ECN): The decision and implementation stage. It defines the approved change details, effective dates or serial/lot cut-ins, and implementation instructions.

Some organizations use combined forms or different names, but the conceptual separation between “request/analysis” (ECR) and “approval/implementation” (ECO/ECN) is common.

Operational context in manufacturing

On the shop floor and in supporting systems, an ECR can lead to:

• Revision updates to drawings, models, and specifications
• Changes to BOMs, routings, tooling, or test procedures
• Updates to work instructions, travelers, and training materials
• Adjustments to inspection plans, control plans, and FAI / AS9102 documentation
• Coordinated disposition of existing inventory and WIP affected by the change

Digital systems often link ECRs to nonconformance reports, CAPA records, and audit trails to provide evidence of closed-loop quality and change control.

Common confusion

• ECR vs ECO / ECN: ECR is the request and evaluation; ECO/ECN records the approved change and its controlled rollout.
• ECR vs CAPA or NCR: An NCR or CAPA may identify an issue that triggers an ECR, but the ECR specifically manages the engineering and configuration change, not the entire corrective action process.

Tie to audit and configuration-control context

In the context of demonstrating configuration control to auditors, ECRs help show that every change to a configuration item (such as drawings, BOMs, and routings) was requested, reviewed, and justified before release. When linked with ECOs and as-built records, ECRs support traceability of which configuration was applied to which parts, lots, or systems at specific points in time.