Action lists explained

An action list is a structured, department-specific set of instructions generated from your ECO and ERP data. It replaces the 90-minute Excel scramble and the informal email cascade.

Anatomy of an action item

Every action item contains five elements:

Element	Example
Action verb	Cancel / Amend / Update / Expedite / Notify / Hold
ERP reference	PO-8847 line 3 · Production Order WO-2025-0441
Quantity & date	200 units, delivery 3 April
Justification	”…delivers after phase-in date of 18 March”
Due date	Set automatically per department template (configurable in Settings)

Example action line

”Cancel PO-8847 line 3 for 200 units — arrives 3 April, after phase-in date of 18 March. New part AG-HYD-04221-02 ordered, arrives 24 April.”

The justification is what matters

The justification sentence is what allows a procurement manager to act without calling engineering. It must be readable in isolation — as if received with no other context. Review every generated justification before releasing the ECO.

Department grouping

Actions are grouped by department. When the ECO is released, each department receives only their own actions — not the full list. A procurement manager sees only procurement actions. An assembly lead sees only assembly actions.

Standard departments in Redline: Engineering, Procurement, Production, Assembly, Quality, Service. Your administrator can add custom departments in Settings → Departments.

AI-generated vs manually added

The action list is generated by the Claude API based on the ECO data, phase-in dates, and conflict flags. The structure (which actions are needed and in what sequence) is determined by Redline’s rule engine — AI is used only to write the human-readable instruction text.

You can:

• Edit any AI-generated action line — edited lines are marked with an edited badge
• Add manual action items that are not generated automatically
• Remove action items that are not applicable

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