Release an ECO
Releasing an ECO locks the phase-in dates, generates the action list, and notifies all affected departments. This is the point of no return — review everything before clicking Release.
Pre-release checklist
Section titled “Pre-release checklist”Before releasing, verify:
- All affected items have a phase-in date assigned
- Conflict flags have been reviewed and addressed (or overridden with a reason)
- The implementation strategy is correct
- BOM validation has passed (no unresolved violations)
Redline enforces the first check automatically — you cannot release an ECO if any affected item is missing a phase-in date.
What happens on release
Section titled “What happens on release”1
Phase-in dates are locked
Dates can no longer be changed without creating a new revision of the ECO.
2
Action list is generated
Redline’s rule engine determines which actions are needed based on affected items, ERP data, and conflict flags. Seven action types are evaluated: UPDATE_BOM, CANCEL_PO, AMEND_PO, UPDATE_PROD_ORDER_BOM, HOLD_PROD_ORDER, MBOM_REVIEW, and SERVICE_ACTION. AI writes the human-readable instruction text for each action.
3
N1 notifications are sent
Each department receives an email with only their action items. The email includes the action type, ERP reference, quantity, justification, and due date. Recipients can update action status directly from the email using one-click response buttons — no login required.
4
ECO status changes to Released
The released timestamp and user are recorded in the audit trail.
Action priority assignment
Section titled “Action priority assignment”Actions are automatically prioritised based on days until due date:
| Priority | Days to due | Urgency |
|---|---|---|
| 1 — Critical | ≤ 3 days | Immediate attention required |
| 2 — High | ≤ 7 days | Act this week |
| 3 — Medium | ≤ 14 days | Schedule in current sprint |
| 4 — Low | > 14 days | Plan ahead |
Regenerating the action list
Section titled “Regenerating the action list”If ERP data has changed since the initial generation, you can regenerate the action list. This deletes all current actions and rebuilds from fresh data. Use this if new POs were placed or production orders changed between preparation and release.