An ECO That Fell Through Without a Log
The ECR goes in. The lead engineer acknowledges it. The Pulse ACR number gets assigned. And then, three weeks later, production is still building to the old revision because nobody sent the release email, the release folder number was never recorded, and the BoM revision detail lived only in a Slack message that scrolled into oblivion. The part ships. The field install team arrives. The kit list is wrong.
That sequence happens when ECO management lives in email threads and a shared spreadsheet that three engineers have edit access to simultaneously. The ECO Log template exists to close those gaps — one record per ECO, one place where the full lifecycle from initiation to QC sign-off is tracked, with checkboxes that cannot be quietly skipped.
The Checkboxes That Actually Matter
The three boolean fields at the bottom of this template — Released in Pulse, Release email sent, and Production dwgs & kit lists updated — look like administrative bookkeeping. They are not. They are the failure modes of the ECO process made explicit.
Released in Pulse tracks whether the ECO has been formally entered into the PLM system. Without this, the change exists in Memento and nowhere else. The Pulse ACR No. field records the specific ACR number assigned during release — cross-referencing Memento against Pulse during a discrepancy review becomes a one-second lookup instead of a fifteen-minute search through Pulse history.
Release email sent is a field that looks redundant until the day it isn't. The release email is the signal to production that the change is live. If it goes unsent because the engineer thought someone else handled it, production continues on the superseded drawing. Marking this field false on an ECO that is already showing "Released in Pulse" immediately flags an incomplete release cycle.
ECO QC'd and Complete is the final gate. A QC that signs off on completion before kit lists are updated can mark the ECO complete. This template makes that impossible to obscure — Production dwgs & kit lists updated must be checked before ECO QC'd and Complete makes sense to check. The sequence is visible in a single record.
What the Design Time Field Tells You After Sixty ECOs
Design time is tracked as a duration field in hours and minutes. At the individual ECO level, it is a labor cost input — paired with Extra parts costs in USD, it gives you total ECO cost per change order. At sixty entries, filtered by lead engineer or by reporting department, it becomes a workload analysis.
If your ECO log shows that project-specific ECOs consistently carry 8–12 hour design times while standard product ECOs average 2–3 hours, that spread informs resource allocation decisions for the next project cycle. If one department is generating 60% of the ECOs, that is a design review problem surfacing in the data before it surfaces as a schedule slip.
BoM Revision Detail and Production Action Req'd are free-text fields. Every structured process has exceptions, and those exceptions need a place to live that is attached to the specific ECO record — not in a separate email thread. When a BoM revision requires a partial retrofit of units already in production, that instruction belongs in Production Action Req'd, tied to the ECO number, visible to anyone pulling the record.
Install Action Req'd serves the field team. If an ECO affects units already shipped, the installation team needs clear direction. That direction, written once by the lead engineer and stored in the ECO record, survives the personnel change, the project handoff, and the six-month gap between the change order and the field retrofit.
The Project Specific or Standard lookup field splits the ECO population by type — an important split because project-specific changes carry customer impact and often require customer notification, while standard product changes flow through internal release only. Filtering by this field at any time gives you the subset of ECOs with external stakeholder implications.