Skip to content
CHANGEROUTE

Engineering Change Request Template: Free ECR Form for UK Manufacturers

What an Engineering Change Request Is For

An engineering change request (ECR) is the formal document that initiates a proposed change to a product, process, or piece of documentation in a manufacturing organisation. It is not the approval to make the change — that comes later, via the Engineering Change Order (ECO). The ECR is the request: a structured record that documents what is being proposed, why it matters, and what impact it might have.

For UK manufacturers operating under ISO 9001:2015, the ECR is the starting point of the change control process that clauses 8.3.6 (design and development changes) and 8.5.6 (control of changes) require. Without a structured ECR, the downstream review, approval, and evidence trail that auditors check is difficult to reconstruct.

This page provides a free ECR form template with all required fields, a worked example, and the key points an ISO 9001 auditor will verify when reviewing your change records.

The ECR Form Template — All Required Fields

Section 1: Identification

ECR number A unique sequential reference. Format: ECR-[YEAR]-[SEQUENCE] (e.g. ECR-2026-023). This becomes the audit trail identifier — all related documents (impact assessments, ECO, ECN) reference back to this number.

Date raised The date the ECR was submitted, not the date the change was implemented.

Raised by Name and job title of the person raising the change request. Could be an engineer, a quality manager, a customer service representative, or a production supervisor — anyone can raise an ECR.

ECR title A short descriptive label for the change: "Update tensile strength specification — Grade 316 bolts" or "Revise process sequence for sub-assembly A12". Used in the ECR log and change meetings.

Section 2: Change Description

Change description A clear, specific description of what is being proposed. Not "improve the process" — that is a goal. The change description should describe the specific modification: which drawing, which procedure, which specification, which component, and exactly what will be different after the change.

Good: "Revise Drawing DWG-045 Rev B to change bolt grade specification from 4.6 to 8.8 property class throughout." Poor: "Update the bolt specification to use stronger bolts."

Change category Classify the type of change:

  • Design change (drawing, specification, material, component)
  • Process change (work instruction, manufacturing sequence, equipment, parameter)
  • Document change (procedure, form, work instruction revision not linked to a process change)
  • Supplier change (approved supplier substitution, new supplier qualification)

Category determines which departments must conduct an impact assessment and who must approve.

Change trigger What prompted this ECR? Common triggers:

  • Non-conformance report (NCR reference: ___) — change required to prevent recurrence
  • Customer request (customer reference: ___) — customer specification change
  • Design improvement — engineering decision to improve quality, cost, or performance
  • Regulatory update — new or revised regulatory requirement
  • Supplier change — supplier material substitution or component change
  • Cost reduction — value engineering initiative

Linking the ECR to its trigger (especially an NCR reference) creates the NCR-to-corrective action-to-ECO traceability chain that ISO 9001:2015 requires and that auditors look for specifically.

Section 3: Impact Assessment

The impact assessment section is completed by each affected department, not by the person raising the ECR. The ECR is routed to relevant functions, who assess the proposed change from their area's perspective.

Departments to assess (tick which apply to this change):

  • Engineering / Design
  • Production / Manufacturing
  • Quality
  • Purchasing / Supply Chain
  • Health & Safety
  • Finance (cost impact)
  • Customer Services (if customer-facing)

For each department completing an assessment:

Impact identified? Yes / No

Description of impact If yes: describe the impact specifically. "No impact" is a valid answer — but a function head must sign it. "Not assessed" is a pre-commit failure in an ISO 9001 audit.

Assessment completed by Name, role, and date.

Section 4: Classification

Change class After impact assessments are complete, classify the change:

  • Major — affects product form, fit, or function; affects safety; requires customer notification; requires re-qualification or re-testing. Requires Change Control Board (CCB) approval.
  • Minor — no effect on form, fit, or function; no safety implications; no customer notification required. May be approved by Quality Manager alone.

The boundary between major and minor must be documented in your change control procedure. Auditors specifically check for changes that were classified as minor but should have been major — it is the most common reclassification finding.

Customer notification required? Yes / No

If yes: customer notification must be documented before implementation proceeds.

Section 5: Approval

Approved by For major changes: signatures (or digital equivalents) from CCB members. Names and roles, not just signatures. For minor changes: Quality Manager name and date.

Approval date The date approval was granted. Implementation cannot begin before this date — retrospective approvals are a common audit finding.

Approved for implementation: Yes / No / Approved with conditions

Conditions (if any) If approved with conditions: document specifically what must happen before or during implementation.

Section 6: Implementation

Engineering Change Order (ECO) number Once approved, the ECR generates an ECO, which is the authorised instruction to implement. Record the ECO reference here to link the two documents.

Implementation target date When the change will be implemented. Must be after the approval date.

Documents to be revised (list) Every document affected by the change must be identified before implementation. Drawing numbers and revision levels, procedure references, work instruction numbers, form numbers. These get updated as part of ECO implementation.

Implementation confirmed by Named individual confirming the change has been implemented as approved.

Implementation date Actual date of implementation.

Section 7: Verification and Close-out

Post-implementation verification How the change will be confirmed as effective after implementation. May include: first article inspection, re-measurement, process audit, customer confirmation, batch pass/fail data.

Verification result Pass / Fail with evidence reference.

Verification completed by Named individual, with date.

ECR closed by Quality Manager or designated change control owner.

Closed date

Worked Example

A materials specification change following a goods-inwards rejection:

Field Example
ECR number ECR-2026-018
Date raised 8 July 2026
Raised by S. Kumar, Quality Manager
ECR title Revise bolt specification — Drawing DWG-045 Rev B
Change description Change bolt property class specification on Drawing DWG-045 from Grade 4.6 to Grade 8.8 throughout. Applies to all M8 hex head fasteners on sub-assembly A12.
Change category Design change (drawing specification)
Change trigger NCR-2026-031 — goods-inwards rejection of Grade 4.6 bolts supplied as Grade 8.8. Root cause: specification ambiguity on drawing led to supplier ordering error.
Engineering impact New drawing revision required (DWG-045 Rev C). Testing to confirm Grade 8.8 meets torque requirements at existing tightening specification. Completed by T. Chen, Design Engineer, 10 July 2026.
Production impact No process change required. Existing torque specification remains valid. Completed by R. Shah, Production Manager, 10 July 2026.
Quality impact Update approved supplier list to require Grade 8.8 certification with delivery. Update incoming inspection procedure to verify grade from certificates. Completed by S. Kumar, QM, 10 July 2026.
Purchasing impact Update purchase order template to specify Grade 8.8 property class explicitly. Completed by L. Martin, Procurement, 11 July 2026.
Change class Minor — no change to form, fit, or function. Grade upgrade only. No customer notification required.
Approved by S. Kumar, Quality Manager, 14 July 2026
ECO number ECO-2026-012
Documents to revise DWG-045 Rev B → Rev C; Approved Supplier List; Incoming Inspection Procedure IIP-003 Rev 4 → Rev 5; PO Template
Implementation target 28 July 2026

What Auditors Check in Your ECR Records

When a UKAS-accredited certification body auditor reviews your change management records, they typically:

Select recent changes at random. Not just the clean ones, and not just the ones you flag as "your best example." Random selection reveals how the process works day-to-day, not how it works when you are preparing for an audit.

Trace from trigger to close-out. For an NCR-triggered ECR, they will start at the NCR, verify the root cause identified a process or design issue, find the ECR, check that all affected departments assessed the impact, confirm approval preceded implementation, verify the documents listed were actually revised, and check that post-implementation verification was completed and documented.

Check classification decisions. They will look at how you classified changes — particularly if any minor-classified changes affect product form, fit, or function. A change that significantly affects a product's performance but was classified as minor (and therefore approved without CCB review) is a major nonconformance finding.

Verify that implementation dates follow approval dates. Changes implemented before they were approved are a procedural nonconformance. In paper systems, this often happens when someone "backtracks" to get a signature on something already implemented. Auditors know to look for date sequences that are improbably close.

Check document revision trails. If your ECR listed four documents to revise and your current document list shows only three revisions, they will ask about the missing one.

Connecting the ECR to Your Quality System

The ECR does not exist in isolation. A change management process that works as a system connects:

  • Non-conformance reports — recurring NCRs that indicate a systemic problem should trigger an ECR. The root cause analysis in a corrective action frequently identifies a design or process change required — that change becomes an ECR. The ECR reference goes in the corrective action record; the NCR reference goes in the ECR trigger.
  • Change control procedure — the ECR form works within the rules your change control procedure defines: what counts as a change, who assesses, who approves, what documents must be revised.
  • ECR template generator tool — our ECR Template Generator creates a structured ECR document with all required fields, formatted for your quality management system.
  • 8D problem solving — for complex or customer-reported issues, an 8D investigation may be running in parallel with the ECR. When D5 (corrective actions) and D6 (implementation) of the 8D produce a design or process change, that change needs an ECR. The 8D report references the ECR; the ECR references the 8D.

This guide describes the engineering change management requirements of ISO 9001:2015 clauses 8.3.6 and 8.5.6. The full standard is available from ISO. This guide is a practical reference — verify requirements with the standard and your UKAS-accredited certification body.

Sources

ChangeRoute is a quality management tool for ISO 9001-certified UK manufacturing SMEs. Join the waitlist to be notified when it launches.

Ready to automate your change management workflow?

ChangeRoute replaces paper ECRs with a structured digital workflow. Join the waitlist for early access.

No spam. Unsubscribe any time. Privacy policy.

Related guides

ECR vs ECO vs ECN: What Every Quality Manager Needs to Know

Clear explanation of the differences between Engineering Change Requests (ECR), Engineering Change Orders (ECO), and Engineering Change Notices (ECN). Includes practical examples and ISO 9001 context.

NCR Form Template: How to Write a Non-Conformance Report (with Free Template)

Free NCR form template for UK ISO 9001 manufacturers. All required fields, worked example, and how to write a non-conformance report that passes a UKAS audit.

ISO 9001 Internal Audit Checklist: A Practical Guide for UK Manufacturers

ISO 9001 clause 9.2 internal audit requirements, a practical checklist for UK manufacturing SMEs, and what auditors check when reviewing your audit programme.