Lock escalation path above Steercopmo.dec.escalation_path_lock

P1 GCC

Summary

Lock the named escalation path. After lock, items that exceed Steerco authority have a defined next stop with an SLA.

Rationale prompt skeleton

Rationale should reference the escalation path question and the Steerco decision-authority thresholds. Confirm the SLA is realistic against sponsor calendar.

Default options (2)

sponsor_direct Escalate directly to named sponsor

Items above Steerco authority go straight to the sponsor with a 5-business-day SLA.

Pros

+ Fast; single named recipient
+ Sponsor stays informed without daily noise

Cons

− Sponsor capacity may not match escalation volume
− Risk of escalation-by-default for items that should resolve in Steerco

board_subcommittee Escalate to a board subcommittee (e.g., Transformation Committee)

Items go to a formal board subcommittee that meets monthly with a 30-day SLA.

Pros

+ Formal record of board engagement
+ Distributed accountability

Cons

− 30-day SLA is too slow for time-critical decisions
− Adds a governance layer that may not exist yet

Default approval chain

Admin
ExecutiveViewer

Linked evidence questions (1)

id	prompt	workstream
pmo.q.escalation_path	What is the escalation path above Steerco? Who/what body receives escalations, on what cadence, and what is the SLA for response?	pmo.governance_forums