Engineering change ECR / ECN management

1.Why change control — and when it starts

Change control starts at design release — the moment a drawing, BoM or firmware version is frozen and others begin to rely on it (purchasing orders parts, production builds, customers receive units). Before that point, iterate freely. After it, an uncontrolled change can mean obsolete stock built into product, a field failure, or a part that no longer mates.

A good process is proportional: a typo fix on a drawing note is not a new mold. The goal is traceability and impact control with the least friction that still prevents mistakes.

2.The ECR → ECN flow

A change moves through a short, auditable path. Keep the request and the notice as separate records — the ECR captures why, the ECN captures what was approved and released.

• Keep the request lightweight so people actually raise issues; put the rigor in the assessment and approval.
• One change = one ECN where possibleeasier to trace, roll back and audit than a bundle.
• A rejected ECR is still a recordit documents that the change was considered and why it was declined.

3.Classifying the change

Not every change needs the same scrutiny. Classify on fit, form, function and interchangeability, plus regulatory and customer impact, and route accordingly.

• Revision vs part number: a revision change means the new part replaces the old and is interchangeable. If the change breaks backward interchangeability, assign a new part number instead.
• Form-fit-function (FFF): changes that don't affect FFF are usually minor; anything touching the interface, performance or safety is major.

4.Effectivity and disposition of existing stock

This is where most change pain actually lands — deciding when the change applies and what happens to parts already made or on order.

For every approved change, set a disposition for finished stock, work-in-progress and on-order parts:

• Use-as-isexisting stock is acceptable; change applies going forward (typical for cost-down or minor improvements).
• Reworkbring existing stock up to the new revision (define the rework instruction).
• Scrapexisting stock is unsafe/unusable at the old revision.
• Return to supplierpush defective or wrong stock back up the chain.

Always reconcile on-order quantities and supplier tooling — an ECN that ignores the 5 000 parts already in transit just moves the problem.

5.Revision, BoM and documentation impact

A change is only "done" when every dependent record is updated — not just the drawing.

• Bump the revision on the changed item and record it in the title block and the BoM (see BoM & component sourcing, IDB-BOM-005).
• Run a where-used check: a changed component may sit in several assemblieseach parent BoM and drawing may need a revision too.
• Update all documentation: drawing, BoM, work instructions, test/inspection plan (DVP&R, IDB-DVP-052), labels, firmware version, and any customer-facing spec.
• Tooling and fixtures: molds, jigs, programs and gauges that embody the old geometry must be updated or flagged.
• Communicate effectivity to purchasing, production and (if relevant) the customer before the date hits.

6.Checklist

• Raise an ECR with the problem, the proposed change and the affected itemsnot just a solution.
• Assess impact across cost, schedule, risk, BoM, where-used, tooling, documentation and the field.
• Classify (major/minor; interchangeable or new part number) and route to the right approval level.
• Approve at the CCB with eng, quality, ops and purchasing represented; record the decision.
• Release an ECN that bumps the revision, sets the effectivity (date / serial / immediate) and the disposition of existing stock.
• Update every dependent recorddrawing, BoM, work instructions, test plan, tooling, firmware, labels.
• Verify and closeconfirm the change is effective in the build and archive the record.
• Log everything in the companion Excel ECR/ECN log so status, effectivity and history are one click away.