Generate & review

The action list is generated when you release an ECO. Redline’s rule engine determines which actions are needed, and AI writes the human-readable instruction text.

How generation works

For each affected item, the rule engine evaluates seven action types:

Action type	Condition	Department
UPDATE_BOM	Every affected item	Engineering
CANCEL_PO	Removed/revised item with open PO (no partial delivery)	Procurement
AMEND_PO	Removed/revised item with open PO (partial delivery exists)	Procurement
UPDATE_PROD_ORDER_BOM	Revised/qty_changed item with active production order	Production
HOLD_PROD_ORDER	Stop strategy with active production orders	Production
MBOM_REVIEW	MAKE item with active production orders	Production
SERVICE_ACTION	Proactive/Stop strategy with FCO_REQUIRED conflict flag	Service

Each action is auto-assigned a department, due date, and priority based on the phase-in timeline.

Reviewing the action list

Actions are displayed in a department-grouped accordion view:

Engineering → Procurement → Production → Service

Each department section shows a completion counter and expands to reveal individual action items. Each item displays:

• Sequence number — order within the list
• Action type — colour-coded badge
• Instruction text — AI-generated, plain-language instruction with ERP references
• Assignee — from default department assignees (configurable in Settings)
• Due date — calculated from phase-in date minus department offset
• Priority — 1 (critical) through 4 (low)
• Status — open by default

Editing before release

You can edit the action list before releasing the ECO:

• Edit instruction text — click any action line to modify the AI-generated text. Edited lines are marked with an edited badge
• Add manual actions — create custom action items for situations the rule engine does not cover
• Remove actions — delete actions that are not applicable to this change
• Change assignee — reassign an action to a different user or contact

All edits are tracked in the ECO’s History tab.

Review every justification

The justification sentence is what allows a department user to act without calling engineering. It must be readable in isolation. Review every generated justification before releasing — if a procurement manager cannot understand the action from the email alone, something is missing.

Regenerating

If ERP data has changed (new POs placed, production orders completed), you can regenerate the entire action list. This deletes all current actions — including manual edits — and rebuilds from fresh data.

After release

Once released, the action list is locked. Department users receive their actions by email (N1 notification) and can update status via:

• The Tasks page in Redline
• One-click response buttons in the email (no login required)

See Notifications & follow-up for the full notification and escalation flow.

Next steps

• Notifications & follow-up →
• Track & close an ECO →