Exception Management Playbooks for Consolidation Breaks
N.B. Use Cholesky to reflect correlated task durations where applicable. Validate calendar effects (non-working days). If milestones are externally fixed, compute required acceleration cost to achieve P80 confidence.
📄 Prompt Template
Create standard playbooks for when consolidation plans break due to late inventory, carrier fall-off, weather, or system outages. Define triggers from [ControlTowerTool] alerts and categorize by severity. For each scenario, prescribe actions: resequence stops, swap equipment, split shipments, mode switch, or reschedule appointments, while preserving [KeyAccountSLAs].
Output requirements: (1) A decision matrix (Scenario, Trigger, First Action, SLA Impact, Cost Delta, Approval Level). (2) Step-by-step playbooks (numbered lists) for the top 6 scenarios. (3) A communications template for customers and carriers.
Include data capture requirements to enable post-mortems and continuous improvement. Specify guardrails that prevent planners from de-optimizing the network.