Escalation is a system. Not a temperament.

The five tier ladder. Each rung does a job.

A well drafted TSA escalation procedure operates as a five tier ladder. Tier one is the operational desk, where service tower leads on both sides resolve daily incidents. Tier two is the program management office, where the buyer side PMO and seller TSA office handle cross workstream issues and recurring exceptions. Tier three is the steering committee, where functional executives resolve contractual disputes and change requests. Tier four is the executive committee, where senior principals handle strategic exceptions and material disputes. Tier five is formal dispute resolution under the TSA's mediation, arbitration, or litigation clause.

Each tier has a defined remit. Tier one resolves anything inside the existing service catalog without contractual interpretation. Tier two resolves operational coordination issues and small change requests. Tier three resolves contractual disputes, financial variance, milestone risk, and change requests inside the contractual envelope. Tier four resolves strategic decisions and disputes that the lower tier could not close. Tier five binds the parties on items they could not resolve internally.

The escalation between tiers is structured. Each tier has a defined response window. If the tier does not resolve within the window, the issue moves to the next tier automatically. The buyer side advisor tracks the timer on every escalated item and triggers the next tier when the window closes. Without that timer, escalations stall at whichever tier has the least urgency. Sellers that benefit from delay rely on the absence of a timer.

The ladder structure is one of the items the pre signing review establishes in the TSA. Loose escalation language produces loose escalation behavior. Tight language with named tiers, defined windows, and explicit triggers produces predictable behavior. The work pairs with the governance committee structure framework.

Escalation criteria. Not subjective.

Escalation criteria need to be objective. Subjective criteria lead to discretion. Discretion leads to inconsistency. Inconsistency lets sellers exploit the variation. The buyer side advisor defines escalation criteria as binary tests. Either the test is met and the item escalates, or it is not and the item stays. Operational judgment guides the resolution at each tier. It does not control whether the item escalates.

Common tier two criteria include recurring exception count above threshold (typically three or more occurrences in 30 days), ticket aging beyond contractual resolution time, change request awaiting seller response beyond 10 days, and any issue affecting two or more service categories. Tier three criteria include any service credit claim, any invoice dispute above a dollar threshold, any milestone risk rated amber or red, any change request requiring contractual amendment, and any tier two item unresolved within the window.

Tier four criteria include any breach notice issued, any extension fee proposal, any termination decision, any dispute with cumulative exposure above a dollar threshold (typically $250K), any milestone slip affecting the contractual exit date, and any tier three item unresolved within the window. Tier five triggers when tier four fails to resolve within the contractual window for that specific type of dispute, typically 30 to 60 days.

The criteria live in a written escalation matrix maintained by the buyer side PMO. The matrix is reviewed quarterly and updated as the TSA evolves. Where the matrix is missing or vague, items stall at the operational tier and accumulate. Where the matrix is precise and enforced, items move predictably. The seller adapts to the predictability and resolves faster at the lower tiers to avoid the higher tier exposure.

Documentation discipline. The escalation log is the file.

Every escalated item lives in the escalation log. The log captures the item identifier, the originating tier, the date of first occurrence, the tier currently holding the item, the date entered each tier, the action history, the responsible owner on each side, and the current status. The log is maintained by the buyer side PMO. It is reviewed at the steering committee biweekly and at the executive committee monthly.

The discipline of the log produces three benefits. First, no item gets lost. The PMO has a single source of truth for every active escalation regardless of who on the buyer side originally raised it. Second, the seller cannot dispute the timeline. The dates of entry into each tier are recorded contemporaneously, not reconstructed after the fact. Third, the cumulative pattern becomes visible. Where the seller consistently fails to resolve at a specific tier, the pattern points to a structural issue that the executive tier needs to address.

The log also feeds the dispute file. Where any item ultimately reaches formal dispute resolution, the escalation log is exhibit one in the proceeding. It demonstrates that the buyer attempted to resolve through every contractual tier before invoking the formal mechanism. Arbitrators and judges reward parties that exhausted lower tier remedies. The log is the proof of exhaustion.

Documentation tone matters. The log is factual, not editorial. Entries describe what happened, when, and what action was taken. The log does not characterize seller intent, does not assign blame, and does not contain rhetoric. The buyer side advisor maintains tone discipline so that the log reads as an evidentiary record, not as a complaint letter. The work pairs with the dispute resolution process framework.

Timing the escalation. Fast is better than late.

The buyer side advisor coaches the Newco PMO to escalate quickly. Fast escalation produces three outcomes that slow escalation does not. The seller's senior executives engage earlier, reducing the time the issue sits with operational staff who lack authority to resolve. The cumulative cost of operational underperformance is shorter. The cure period clock starts earlier on any breach notice that follows.

The fear that fast escalation signals weakness or impatience is misplaced. Sellers calibrate their attention to the buyer's signal. A buyer that absorbs operational issues quietly for months tells the seller the issues do not matter. A buyer that escalates predictably and on schedule tells the seller the issues do matter. The seller routes more senior attention to the relationship and the operational performance improves. The early escalation discipline is one of the highest leverage moves a buyer can make.

The contractual timing also matters. Most TSAs require escalation within a defined window for the buyer to preserve remedies. A buyer that lets an issue sit at the operational tier for 90 days without escalation may have waived the right to claim damages, even if the issue is real. The buyer side advisor maintains the escalation calendar with contractual deadlines marked. Items approaching deadline escalate automatically, not at operational discretion.

The discipline includes the de escalation path. Where an item escalates and the seller engages substantively, the item may be resolved at the higher tier and removed from active escalation. The de escalation is documented in the log with the resolution date, the resolution terms, and any commitments the seller made for future operational improvement. De escalation discipline keeps the active escalation list manageable and the focus on the items that remain unresolved.

Interfaces with breach and dispute clauses. The escalation feeds the file.

Escalation interfaces tightly with the breach notification mechanism. Most TSAs require some attempt at lower tier resolution before formal breach notice. A buyer that issues breach notice without escalation history has a thinner factual case. A buyer that issues breach notice with a documented escalation history through tiers one through four has a thicker case. The escalation log is the substantive backbone of any breach notice. The work pairs with the breach notification strategy framework.

The dispute resolution clause similarly references the escalation procedure. Most TSAs require the parties to attempt informal resolution at the executive tier before invoking formal mediation or arbitration. The contractual sequence is usually: 30 days of executive negotiation, then mediation (where required), then arbitration or litigation. A buyer that did not run the executive tier negotiation has a procedural defect in any subsequent formal proceeding.

The advisor coordinates escalation with legal counsel. Where an item is escalating toward formal dispute resolution, the buyer's legal counsel is engaged before the executive tier negotiation. Counsel reviews the escalation log, advises on legal theories, and may participate in the executive tier discussion. Where the seller observes counsel engagement, settlement probability often rises. Where counsel engagement is delayed, settlement probability often falls.

The dollar value of the escalation determines counsel intensity. Small dollar items resolve through the buyer side advisor without external counsel. Mid sized items engage outside counsel for strategy. Large items engage outside counsel for full representation. The buyer side advisor scales counsel engagement to the dollar exposure and the strategic significance of the dispute.

Standing up the procedure. Day One through exit.

The escalation procedure must be operational on Day One. That means the matrix is drafted, the log infrastructure is built, the PMO owner is named, the tier windows are calibrated, and the first weeks of operating data are flowing through the log. Buyers that stand up the procedure on Day Two miss the first month of operating data and never recover the audit window for those weeks.

The pre signing review is where the contractual escalation procedure first appears. The buyer side advisor drafts the tier definitions, the response windows, the criteria for moving between tiers, and the interface with the breach and dispute clauses. The seller often pushes back on tight windows and explicit criteria. The buyer holds the line. The economics of tight escalation cost the seller very little and benefit the buyer enormously.

During the signing to Day One window, the operational infrastructure is built. The escalation matrix is loaded into the PMO tooling. The log template is created. The communication protocols are established. The first 30 days of operational meetings have escalation as a standing agenda item. The seller's TSA office is briefed on the escalation procedure during the joint kickoff. Both sides understand the procedure from week one.

Escalation programs are delivered under a Fixed Fee or Portfolio Retainer engagement model through TSA dispute resolution and Day One Readiness. The discipline pays back inside the first quarter through faster resolution, better seller engagement, and a documented operating record that holds up if any dispute escalates to formal proceeding. The work pairs with the monthly operating rhythm framework.

More on disputes and governance.