An engineering change sounds small on paper. Swap a material, update a tolerance, revise a drawing, move a step in the work instructions. Then the old revision ships anyway, purchasing orders the discontinued part, and the shop floor builds to two different versions of the same product. That is what happens when engineering change control is informal, and it is one of the most expensive avoidable problems in a small factory.
Engineering change control (ECO management) is the disciplined process of proposing, reviewing, approving, and releasing product and process changes, so that everyone works from the same current revision at the same time.
What is an engineering change order (ECO)? #
An engineering change order is the formal record of a proposed change. A good ECO answers five questions before anyone approves it:
- What exactly changes? The drawing, bill of materials, work instruction, or specification, with before and after revisions stated clearly.
- Why is it changing? A customer request, a defect fix, a cost reduction, a supplier change, or a regulatory requirement.
- What else does it affect? Inventory on hand, open orders, tooling, inspection criteria, training records, and supplier agreements.
- When does it take effect? Immediately, at a serial number, at a date, or when existing stock is used up.
- Who approved it? Engineering, quality, and production sign off, so no single person can push a change through alone.
If your ECO cannot answer all five, it is not ready for approval.
Why do ECOs break production? #
Most ECO failures are not engineering failures. They are communication failures:
- The old revision never dies. The new drawing is released, but the old one stays on the shop floor or in a shared folder. Two revisions in circulation means two versions of the product.
- Inventory is ignored. The change is approved while the warehouse still holds the old part, or purchasing has already ordered it.
- Open orders fall through the cracks. Work already in progress is built to the old revision because nobody checked which jobs the change applies to.
- Suppliers hear about it last. A supplier keeps shipping the old version because the updated specification never reached them, or reached them without an effective date.
- Training is skipped. Operators are expected to follow a new instruction they have never seen, and the audit trail shows no evidence they were trained.
How do you run an ECO process that actually works? #
You do not need a heavyweight bureaucracy. A small manufacturer needs a process simple enough to follow every time, and rigorous enough to catch the failure modes above. Here is a practical sequence:
1. Submit the change request with the full picture #
One form, one place, every time. The requester states the change, the reason, and the affected items, and attaches the marked-up drawing or revised document. If the affected items are not listed, send it back.
2. Assess impact before approving #
Route the request to engineering, quality, and production for an impact review. Cover inventory on hand, open purchase orders, work in progress, tooling, inspection plans, and customer notification requirements.
3. Approve with defined roles, not by whoever is available #
Set approval rules in advance. A minor documentation correction might need one approver. A change to a safety-critical dimension needs engineering and quality sign-off at minimum.
4. Set an effective date and a disposition for old stock #
Every approved ECO needs a clear cut-in point: a date, a serial number, or a “use up existing stock” rule, stated explicitly. Decide what happens to old inventory and old revisions, and record the decision on the ECO itself.
5. Release, notify, and remove the old revision #
Release the new revision to a single controlled location, notify everyone affected (including suppliers), and withdraw the old revision from circulation. If the old drawing is still accessible on the shop floor, the change has not actually happened. This step is where document control software earns its keep: one current version, controlled distribution, and a revision history auditors can follow.
6. Verify the change took hold #
Close the loop. Confirm the first production run under the new revision passed inspection, check that suppliers acknowledged the update, and confirm operators were trained where the work instructions changed. An ECO is complete only when production is actually running the new version.
What changes when ECOs run in one system? #
Spreadsheets and email can carry a small number of changes, but they cannot enforce a process. Nobody gets an automatic reminder when an approval is overdue, nothing stops an operator from opening last month’s drawing, and there is no single record linking the change to the affected inventory, orders, and training.
Purpose-built change control software changes that picture in concrete ways:
- One controlled revision. Only the current version is available to the shop floor, with older revisions archived, not deleted, so the history stays intact.
- Automatic impact visibility. The change record links to affected parts, documents, and open orders, so the impact review is based on data, not memory.
- Enforced approvals. The ECO cannot move forward until the required roles have signed off, and the approval trail is timestamped.
- Linked training and inspection updates. When a work instruction or inspection criterion changes, the related quality inspection criteria and training requirements update from the same record.
- A searchable change history. When a customer asks why a part changed six months ago, the answer is one search away, not a hunt through inboxes.
For manufacturers running several modules together, this is where an integrated system pays off: change control connected to document control, inventory, and production planning means one change propagates everywhere it needs to, instead of being re-entered in four places. That is the core promise of a cloud ERP for manufacturing.
An ECO checklist you can use this week #
Before your next change goes live, run through this list. If any box is unchecked, the change is not ready:
- The ECO states what changed, why, and what it affects
- Engineering, quality, and production have all reviewed the impact
- Inventory on hand and open orders were checked
- An effective date or serial number cut-in is recorded
- Suppliers were notified with the new specification
- The old revision was withdrawn from the shop floor
- Operators were trained on any changed work instructions
- The first run under the new revision was verified
The bottom line #
Engineering change control is not paperwork for its own sake. It is the mechanism that lets a small manufacturer improve products safely, without shipping the wrong version in the process. Start with the six-step process above, enforce it the same way every time, and move it into a controlled system as soon as email and folders start losing track.
Ready to bring your engineering changes under control? Explore how Artintech connects document control, quality, and production in one system, or start a free trial of Artintech to see how controlled revisions work in practice.
