ECO Implementation & Closure Checklist (Free)

0%

0 of 28 items complete

9 critical items still open - these are the highest-risk gaps.

Download checklist:

Data and documents

Affected BOMs updated and released with correct effectivityCRITICALDrawings and models revised, approved and releasedCRITICALRevision level on the item master matches the drawingCRITICALWhere-used list reviewed for all parents of the changed itemRoutings and operations updated if the process changedWork instructions and inspection plans revisedSuperseded documents marked obsolete and removed from the shop floor

Inventory and supply

Disposition decided for stock, WIP and open orders of the old revisionCRITICALOpen purchase orders amended or cancelled with suppliersCRITICALSupplier notified and drawings or specifications sentFirst deliveries of new revision identified and labelledOld-revision stock quarantined or tagged where neededStandard cost updated if the change affects costSafety stock and planning parameters reviewed

Quality and compliance

Verification or first article inspection completed where requiredCRITICALCustomer approval obtained where contract requires itCRITICALRegulatory or certification impact assessedGauges, test programs and fixtures updatedRisk assessment or FMEA reviewed for the changeTraceability recorded so affected lots and serials are identifiableTraining given to operators and inspectors

Service, sales and closure

Service parts and manuals reviewed for field impactSales and customer support informed of any visible differenceEffectivity date or serial cut-in confirmed in the ERPCRITICALFirst build under the new revision verified on the floorCRITICALActual cost and savings recorded against the estimateAll tasks on the ECO complete with sign-offECO closed with lessons learned noted

Every critical item should be complete before closure. Treat any incomplete critical item as a reason to keep the ECO open.

Automate closure checks from your ERP

Optional: we can build read-only checks that flag old revisions in stock or open orders before an ECO closes.

Optional. The tool and every export work without this. No spam.

How to use it

Go through the four groups at the point you intend to close the ECO, ideally with a representative from planning, quality and production. Mark the critical items first. If a critical item is open, do not close the ECO; log the task and the owner instead. Export the completed checklist and attach it to the change record.

Why closure needs a gate

Configuration management standards such as ISO 10007 treat verification of implementation as part of change control, not an optional extra. In practice, most repeat failures from a change come from one of three gaps: old stock used after the cutover date, a supplier still shipping the old revision, or documents on the floor not updated.

Adapting the list

Remove items that do not apply to your product and add your own regulatory items, for example customer notification rules, medical device design history updates or aerospace first article requirements. Keep the list short enough that people will actually use it for every change.

Common mistakes

Closing the ECO on engineering release alone is the biggest one. Another is skipping the first-build check, which is the only real proof that the shop floor is working to the new revision. Record the first build work order number on the ECO.

Frequently Asked Questions

Who should sign off the closure?

Typically the configuration manager or change owner, with confirmation from planning, quality and production for their items. The key is that closure is a deliberate check, not an automatic status change.

Which items are most often missed?

Open purchase orders and supplier notifications, floor-level documents and work instructions, and the effectivity date setting in the ERP. These are also the items that cause the most repeat problems.

Does every ECO need the full checklist?

Not necessarily. Scale it to the change class. A documentation-only correction might need only the first group, while a form-fit-function change needs all four.

How do I prove the first build used the new revision?

Record the work order and serial or lot, and keep the build record or inspection report showing the new revision. Include it in the ECO attachments.

Netray can check several of these items automatically from your ERP, such as old revisions still in open orders or stock, and flag them before an ECO is closed.

Talk to an Expert Explore More Free Tools

Related Tools

Engineering & PLM

More Engineering & PLM tools

See all

ECO Implementation and Closure Checklist