Engineering change order (ECO)
An engineering change order is a formal document that authorizes and controls modifications to a product's design, components, specifications, or manufacturing processes. ECOs ensure that changes are reviewed, approved, and communicated to all affected parties, including suppliers. The ECO process maintains configuration control and creates an audit trail of product evolution.
Examples
Component substitution ECO: A preferred resistor goes end-of-life. Engineering issues an ECO to qualify and implement a replacement part, specifying the new part number, validating form/fit/function equivalence, and defining effectivity for the change.
Design improvement ECO: Field reliability data reveals a failure mode. An ECO documents the root cause, specifies the design change to address it, identifies affected documents and parts, and establishes implementation timing and disposition of existing inventory.
Cost reduction ECO: A supplier proposes a manufacturing process change that reduces cost. An ECO formally evaluates and approves the change, ensuring all requirements are still met and updating documentation accordingly.
Definition
ECOs provide configuration management discipline that prevents uncontrolled changes from creating quality problems, compliance issues, or confusion about what constitutes the current product definition. Regulated industries require documented change control as part of quality system compliance.
A typical ECO includes: description of the change and reason, affected items (drawings, BOMs, specifications), impact analysis, required approvals, effectivity definition, and implementation instructions. Complex changes may require engineering analysis, testing, or supplier requalification.
ECO implementation involves coordinating across functions: engineering updates designs and documentation, procurement communicates with suppliers and manages inventory transition, manufacturing updates processes and work instructions, quality updates inspection requirements.
Effectivity determines when a change takes effect, which might be a date, serial number, or event trigger. Managing effectivity is crucial when products are in production, requiring decisions about existing inventory, work in progress, and fielded products.
Frequently asked questions
What is an engineering change order?
An engineering change order (ECO) is a formal document that authorizes and controls modifications to a product's design, components, specifications, or manufacturing processes. ECOs ensure changes are reviewed, approved, and communicated to all affected parties, including suppliers, and they create an audit trail of how the product evolved.
What does an ECO contain?
A typical ECO includes a description of the change and its reason, the affected items (drawings, BOMs, specifications), an impact analysis, required approvals, an effectivity definition, and implementation instructions. Complex changes may additionally require engineering analysis, testing, or supplier requalification before approval.
What is effectivity in an ECO?
Effectivity defines when a change takes effect, which might be a date, a serial number, or an event trigger. Managing effectivity matters most when products are already in production, because it forces decisions about existing inventory, work in progress, and fielded products: what gets used up, what gets reworked, and what ships under the old configuration.
Why are ECOs required instead of informal changes?
ECOs provide the configuration control that prevents informal changes from creating quality problems, compliance issues, or confusion about what the current product definition actually is. Regulated industries require documented change control as part of quality system compliance, so the discipline is often mandatory rather than optional.
What triggers an ECO?
Common ECO triggers include a component going end-of-life, which requires qualifying a replacement and defining effectivity; field reliability data revealing a failure mode, where the ECO documents root cause and the design fix; and supplier-proposed process changes that reduce cost, where the ECO formally verifies that all requirements are still met before approval.
Which functions are involved in implementing an ECO?
ECO implementation is cross-functional: engineering updates designs and documentation, procurement communicates with suppliers and manages the inventory transition, manufacturing updates processes and work instructions, and quality updates inspection requirements. Missing any one of those handoffs leaves part of the organization building or buying to an obsolete definition.