engineering change notice

An engineering change notice (ECN) is a formal, controlled document used to communicate, authorize, and record a specific change to the design, specification, or approved configuration of a product or manufacturing process.

What an engineering change notice includes

In industrial and regulated manufacturing environments, an ECN commonly:

• Identifies the item(s) affected, such as part numbers, assemblies, documents, or process steps
• Describes the change in clear, technical terms (what is changing and how)
• States the reason or justification for the change (for example reliability, cost, compliance, supplier change, or nonconformance)
• Defines effectivity, such as date, work order, lot, serial number range, or configuration baseline from which the change applies
• Lists impacted documents and systems, such as drawings, specifications, bills of material, work instructions, test procedures, or routings
• Captures required reviews and approvals (for example engineering, quality, manufacturing, supply chain, or customer when required)
• Records implementation and verification steps, including any required rework, retest, or validation

ECNs are typically generated and managed in PLM, PDM, or engineering systems but must align with ERP, MES, and QMS records so that released documentation and as-built / as-maintained configurations remain synchronized.

Role in configuration control and change management

An ECN is one of the core records within engineering change management. It documents a single change event that affects a controlled configuration baseline. While engineering change management refers to the overall workflow for proposing, assessing, approving, and implementing changes, the ECN is the specific notice that:

• Translates engineering decisions into actionable instructions for operations and supply chain
• Provides a traceable record linking design intent, released documents, and production execution
• Supports audits by showing who approved what change, when, and under which conditions

In long-lifecycle and regulated industries, ECNs help ensure that each product unit can be traced to the exact configuration and requirements that were in effect when it was built or serviced.

Operational use on the shop floor

On the shop floor and in supporting systems, ECNs commonly:

• Trigger updates to digital work instructions, travelers, routings, and inspection plans
• Drive part supersessions or bill of material changes in ERP
• Initiate updates to inspection criteria, FAI scope, or control plans for quality
• Define whether in-process or finished units must be reworked, used-as-is, or scrapped
• Provide reference identifiers that appear in MES transaction histories and traceability reports

Common confusion

• ECN vs. ECO (engineering change order): In some organizations these terms are used interchangeably. Elsewhere, an ECO is the broader change package or decision, and the ECN is the specific notice or implementation record communicating that change to affected parties.
• ECN vs. configuration control: Configuration control manages product and process baselines over time. The ECN is one type of record used within that control system to modify a baseline in a controlled, traceable way.
• ECN vs. deviation / concession: A deviation or concession allows temporary departure from a requirement for specific units or lots, without permanently changing the underlying design or process. An ECN typically results in a permanent or long-term change to the configuration or documentation.

Relation to the derived context

Within configuration control and engineering change management, the ECN is the formal notice that links proposed changes to actual updates across PLM, ERP, MES, and QMS. It helps prevent gaps between design intent, released documentation, and as-built or as-maintained records by providing a single, traceable reference for each approved change.