Engineering Change Notification ECN Procedure

The Engineering Change Notification (ECN) Procedure governs all changes to product design, manufacturing process specifications, tooling, materials, and documentation that may affect form, fit, function, safety, or regulatory compliance. This program establishes a single, auditable workflow — from initiation through implementation and post-change validation — that eliminates ad-hoc changes and ensures every modification is risk-assessed, approved, and communicated to all affected stakeholders before deployment.

Lean principles are embedded at every stage: only necessary changes are initiated, approvals are gated by impact severity, and implementation is time-boxed with clear close-out criteria. The ECN procedure is the single source of truth for change control in the manufacturing system and is mandatory for all production sites, contract manufacturers, and engineering partners.

This procedure applies to all engineering, quality, production, supply chain, and maintenance personnel who initiate, review, approve, or implement changes to any controlled element of the manufacturing system. Scope includes changes to:

• Product design specifications, BOMs, and CAD models
• Manufacturing process instructions, work standards, and routing
• Jigs, fixtures, tooling, and gaging
• Supplier-sourced components that affect fit, form, or function
• Packing, labelling, and regulatory documentation
• Software or firmware controlling production equipment

Excluded are routine maintenance tasks, consumable substitutions with no performance impact, and changes already covered under a separate valid deviation or waiver process. All ECNs must be logged in the official change register regardless of approval outcome.

• DIREvery ECN must be assigned a unique identifier in the format ECN-YYYY-NNNN and logged in the change register within 24 hours of initiation. No change may proceed without a valid ECN number.
• DIRAll ECNs must be classified by severity: Critical (safety/regulatory), Major (form/fit/function), or Minor (documentation/administrative). Approval routing and review timeline depend on classification.
• DIRThe originating engineer must complete the ECN form with a clear description of the current state, proposed change, reason, risk assessment, and impact analysis on cost, quality, and delivery within 5 business days of initiation.
• REQCross-functional review is mandatory for Critical and Major ECNs. Required sign-offs include: Engineering, Quality, Production, Supply Chain, and (if applicable) Safety and Regulatory. No single individual may approve their own change.
• REQImplementation must be time-boxed to a maximum of 30 calendar days for Major ECNs and 10 calendar days for Minor ECNs, unless an extension is formally approved by the ECN Board.
• REQPost-implementation validation must be completed within 5 business days of deployment. A closure report must be filed confirming that all affected drawings, BOMs, work instructions, training materials, and supplier documentation have been updated and version-controlled.

• ECN Originator (Engineer or Design Lead) — Initiates the ECN, completes the form and risk assessment, presents the change to the cross-functional team, and leads implementation and closure.
• ECN Coordinator (Program Manager or Change Board Administrator) — Assigns ECN numbers, maintains the change register, tracks review deadlines, schedules approval meetings, and archives closed ECNs.
• Cross-Functional Review Team — Participates in impact analysis, provides written sign-off or conditional approval, and ensures departmental readiness for the change.
• ECN Board (senior Engineering, Quality, and Operations leaders) — Reviews Critical ECNs, resolves escalated conflicts, approves timeline extensions, and authorizes emergency changes outside the standard cycle.
• Implementation Lead (Production Supervisor or Process Engineer) — Executes the change on the shop floor, updates controlled documents, trains affected operators, and coordinates validation testing.