Engineering change orders, or ECOs, are written orders for changes in a product or process's components, specifications, or documentation. They're basically a way of documenting change so there's a record of it.
When an organization develops a process or product, changes are inevitable during engineering development, integration of elements, or implementation of the system. Engineering change orders allow organizations to compensate for design errors, implement debugging procedures, or otherwise make changes to make up for design, integration, or implementation flaws. An ECO is an important part of the audit trail that shows when changes are made during the process or product development. Why They're Used and What They Should Contain Suppose someone on a team identifies an issue with a process. Say, tolerance estimates were based on faulty calculations. Clearly changes are necessary, and an ECO can be created to summarize the changes needed, finalize the details of the change, and document all necessary approvals for the changes. Common reasons for ECOs include: • Corrections of design errors • Changes in customer requirements • Changes in materials or manufacturing methods Typically, an ECO contains the following types of information: • Identification of what needs changing, along with part numbers, component names, reference drawings, etc. • A statement of why the change needs to be made • A description of the change including modified drawings taking changes into account • A list of people, departments, and documents affected by the change • Instructions about when to implement the change • Documentation of approval by those authorized to sign off on changes Benefits of Using ECOs Maybe an ECO seems like overkill for a minor change, but it's actually essential for ensuring that product or process information is accurate at all times. It's also essential for ensuring that everyone affected by the change understands that it is being done and why. When an organization has a method for handling product or process changes, the chances for errors are diminished, and everyone has an easier time staying on the same page. And once a product or process is established, archived ECOs provide a full history of changes and when they occurred. In some industries, change histories are required by regulations, but even when they're not required, they're a good idea.
