Clear, time-boxed escalation paths prevent small problems from stalling the critical path, while a transparent decision-rights framework avoids duplicate approvals and “shadow steering.” Together they keep accountability unambiguous and resolution velocity high.
A. Four-Tier Escalation Ladder
- Tier 0 – Self-Help (Owner Level)
- Who: Task owner or work-stream lead
- Window: ≤ 4 business hours to diagnose and resolve
- Action: Log issue, apply available work-arounds, update issue log
- Tier 1 – Functional Manager
- Who: Direct manager or functional lead
- Trigger: Tier 0 unresolved, or impact > 2 days / $10 k
- Window: Additional 8 business hours
- Action: Re-assign resources, re-sequence internal tasks, notify PMO
- Tier 2 – PMO / Programme Director
- Trigger: Tier 1 unresolved, or risk to critical-path task / regulatory deadline
- Window: 24 hours
- Action: Convene cross-functional task force, approve contingency budget ≤ $50 k, update RAG dashboard
- Tier 3 – Steering Committee
- Trigger: Issue threatens Day 1, TSA exit, or budget variance > ±5 %
- Window: Escalate within 24 hours; ad-hoc SC call within 48 hours
- Action: Decide on scope trade-offs, budget reallocations, or timeline shifts; document decision in change-control register
(Any life-safety or legal-compliance breach bypasses directly to Tier 3.)
B. Decision-Rights Framework
- Task-Level Adjustments – Work-stream Lead may resequence or reallocate resources if no impact to critical path or budget.
- Budget Variance < ±5 % (work-stream) – PMO approves; informs Steering Committee in weekly summary.
- Scope Change Affecting ≥ 2 Work-streams – PMO escalates; Steering Committee approval required.
- TSA Extension (> 30 days or > 10 % cost) – Steering Committee approval; CFO co-signs amendment.
- Regulatory Deadline Shift – Steering Committee decides; Legal Lead must concur.
- Day 1 Date Change – Executive Sponsor (CEO or BU President) approval after Steering Committee recommendation.
C. Escalation & Decision Logs
- Issue Log – Captures timestamp, severity, owner, escalation tier, and resolution date.
- Decision Log – Records what was decided, by whom, date/time, rationale, and downstream actions. Both logs are part of the live PMO dashboard and archived weekly.
D. Communication Protocols
- Email subject line format: “ESCALATION Tier X – ‹Issue Summary› – ‹DD-MMM›”.
- Slack/Teams “#escalations” channel for rapid updates; PMO posts status changes in real time.
- After Tier 2 or Tier 3 resolution, PMO circulates a “Lessons Learned” note within 48 hours.
E. Common Failure Modes to Avoid
- Parallel escalations to multiple tiers—creates conflicting directives.
- Silent escalations—moving an issue upward without updating the log or alerting the current owner.
- Undefined authority—decision rights not documented, leading to decision paralysis.
- No post-mortem—recurring issues because root causes aren’t captured and fixed.
A tight escalation ladder and an explicit decision-rights matrix ensure every problem finds the right owner fast and every critical judgement call lands on the correct desk—keeping the carve-out’s execution rhythm unbroken.
