Escalation works only when people are willing to use it.

Section 01

Why escalation needs a playbook

Escalation is the mechanism that resolves the issues a workstream cannot resolve alone. Without a defined path, escalation drifts: a blocker that should resolve in 48 hours sits for two weeks while emails circulate and nobody owns the decision. By the time it reaches someone with the authority to act, the issue has already consumed seller goodwill and threatened a milestone. The playbook exists to stop that drift.

A playbook turns escalation from a judgment call into a procedure. It states who hears an issue first, who decides at each tier, how long each tier has before the issue moves up, and what kinds of issue skip tiers and go straight to the top. With those rules written down, an issue moves on a clock rather than on the energy of whoever happens to be pushing it, which is what makes resolution reliable.

The playbook also protects the workstream lead. A lead who escalates without a playbook risks looking as though they could not handle their own work. A lead who escalates according to a written procedure is simply following the process, which removes the social cost of escalation. Removing that cost is essential, because the most common escalation failure is not escalating at all.

Section 02

The escalation tiers and time limits

A workable playbook has four tiers. Tier one is the workstream lead, who raises the issue within 24 hours of recognizing it cannot be resolved in the workstream. Tier two is the program director, who attempts resolution and reports back within 24 hours. Tier three is the steering committee, which convenes within 48 hours via a standing call if needed. Tier four is the sponsor or joint governance, within 96 hours for the matters that cross the contract.

The time limits are the spine of the playbook. Each tier has a fixed window to resolve or escalate, and an issue that is not resolved within the window moves up automatically. The automatic movement is what prevents an issue stalling at a tier where no one is willing to decide. Without time limits, escalation depends on someone choosing to push, and issues stall at exactly the points where the decision is hard.

Reserve standing call slots so escalations can land in real time rather than waiting for the next scheduled meeting. Holding a short slot twice a week for the program director and steering committee means an escalated issue meets a forum within days, not at the next monthly meeting. The slot is cancelled when no escalation arrives and used when one does, which costs little and saves the program weeks.

Section 03

Triggers that skip tiers

Some issues are too urgent or too significant to climb the tiers one step at a time. The playbook names the triggers that send an issue straight to the steering committee or sponsor. A risk to a critical path milestone, a service outage affecting customers, a dispute over the TSA terms, or a cost event above a defined threshold should escalate immediately rather than wait for the lower tiers to exhaust their windows.

Define the triggers precisely so the skip is a rule, not a judgment made under pressure. Anything that resets a milestone date on the critical path. Anything affecting an external party such as a customer or regulator. Anything that requires a change to the TSA itself. Anything above the cost threshold the committee owns. When the trigger is met, the issue jumps to the right tier automatically, which is exactly when speed matters most.

Match the trigger to the right forum. A customer affecting outage goes to the operational tier that can mobilize a response, not to the joint governance committee that meets to discuss contract matters. A dispute over TSA terms goes to the forum with the seller's leadership present. Routing each trigger to the forum that can actually act prevents the urgent issue arriving at a committee that can only refer it onward.

Section 04

The discipline of using escalation

The hardest part of escalation is the willingness to use it. Some programs avoid escalation because it creates discomfort, and that avoidance is precisely the failure the playbook is meant to prevent. The discomfort of escalation is the point: an issue that escalates gets resolved, and an issue that does not escalate gets worse. The buyer's program director should escalate without hesitation when a workstream cannot resolve.

Leadership sets the tone by responding to escalations well. When an escalated issue is met with a fast decision and support rather than blame, leads learn that escalation works and they use it early. When escalation is met with questions about why the lead could not handle it, they learn to hide problems until forced, and the program loses its early warning. How leadership receives the first escalation shapes whether the playbook lives or dies.

Track escalations as data. The pattern of what gets escalated, how fast it resolves, and which tier it stalls at tells the program office where the program is weak. A workstream that escalates often may be under resourced. A tier where issues stall may have an authority gap. The escalation record, fed into the lessons learned process, is one of the richest sources of insight into how the program actually runs.

Section 05

Connecting escalation to the governance system

The escalation playbook does not stand alone. It draws on the steering committee charter for the decision thresholds, on the RACI for who owns each issue, on the risk register for the risks that become issues, and on the status reporting that surfaces issues in the first place. Escalation is the action layer that sits on top of the rest of the governance system and makes it move.

Close the loop through the decision log. Every escalated issue resolves in a decision, the decision goes into the log with its rationale, and the resolution flows back to the workstream in the next status report. Closing the loop visibly is what sustains the willingness to escalate, because leads see that raising an issue produces a decision rather than disappearing into the committee.

At program close, an escalation playbook that was used well leaves a record of every hard issue the exit faced and how it was resolved. That record is the proof that the program stayed in control of its difficulties rather than being controlled by them, and it is the template the next carve-out inherits, pre loaded with the escalation patterns this exit actually encountered. A buyer-side program that escalates well is a buyer-side program that lands its exit on schedule.

FAQ

Escalation questions buyers ask.

What are the tiers in a TSA escalation playbook?

Four: the workstream lead raises within 24 hours, the program director attempts resolution within 24 hours, the steering committee convenes within 48 hours, and the sponsor or joint governance handles contract level matters within 96 hours. Each tier has a fixed window before the issue moves up automatically.

Which issues should skip the tiers?

Risks to a critical path milestone, customer affecting outages, disputes over TSA terms, and cost events above the committee's threshold. Define these triggers precisely so the skip is a rule applied automatically, not a judgment made under pressure.

Why do programs fail to escalate?

Because escalation creates discomfort and can feel like an admission a lead could not handle their work. A written playbook removes that social cost by making escalation a procedure, and leadership reinforces it by meeting escalations with fast decisions rather than blame.

How does escalation connect to the rest of governance?

It draws thresholds from the steering committee charter, ownership from the RACI, and inputs from the risk register and status reporting. Every escalation resolves in a logged decision that flows back to the workstream, which sustains the willingness to escalate.

Related Reading

More on TSA governance.