The TSA exit timeline runs four windows, not one.

Window one. Pre-signing.

The pre-signing window opens when the TSA appears as part of the SPA package and closes the day the contract is signed. For most carve-outs that is a six to twelve week stretch, often compressed into the final three weeks before signature when the deal team is closing on multiple workstreams at once.

This is the highest leverage window in the entire TSA lifecycle. Every clause in the seller's first draft is negotiable because the seller is still competing for the deal. Once signed, every change is an amendment. The seller's counterparty leverage drops to near zero the moment the ink is dry.

The buyer-side deliverables at pre-signing are five. A service catalog audit. A pricing benchmark against cost-plus mark-ups and pass-through items. An exit clause review focused on the extension fee curve and service withdrawal rights. An SLA review that converts decorative service levels into enforceable credits. And a governance design that puts the buyer in the chair of the joint committee.

The output is not a deck. It is a redline package, a benchmark memo, and a negotiation playbook that the deal team carries into the redline session with specific positions on every clause that matters.

Window two. Day One and the first 90 days.

Day One is legal close. From that moment, the Newco is operating as an independent entity and the TSA is live. The first ninety days are stand-up work. The buyer is consuming TSA services while building the operating muscle to run an independent company.

The work in this window splits across the nine standard workstreams. Payroll has to run on the correct entity. Bank accounts have to settle on the right calendars. The Newco vendor master has to start receiving its own purchase orders. Customer invoices have to come from the Newco, not the parent. Each of these is operational, not contractual.

Around day sixty, the buyer has enough operating data to start scoping the formal exit ramp. Around day ninety, the exit plan is documented and the workstream cadence is running. The exit is not yet underway. The exit program is.

A common failure pattern in this window is treating the TSA as a finance problem. It is not. Finance signs the invoice. The workstream leads sign off on the service. A finance owned TSA at day ninety almost always means a missed exit at month eighteen.

Window three. Mid-TSA execution.

Mid-TSA runs from roughly month four through month fifteen on an 18 month agreement. It is the longest window and the one where most of the operating work sits. Services are running, the seller is invoicing, the Newco is building parallel capability.

This is also the window where renegotiation becomes possible. The pre-signing service catalog is the seller's best guess at what the buyer will need. By month four to month six, the buyer has consumption data. Some services were over scoped. Some pass-through items turn out to carry hidden mark-up. Some services the buyer never used at all.

Mid-TSA renegotiation addresses that gap. The work is not a wholesale reopening of the contract. It is a targeted set of amendments on specific services where the data supports a price reset, a scope reduction, or an earlier exit. Sophisticated sellers expect this conversation and price the original TSA assuming it will happen.

Mid-TSA is also when the exit ramp gets sequenced. Services with the longest replacement lead times start their migration first. Services with downstream dependencies are scheduled so the dependency chain unwinds in the correct order. The exit ramp is built service by service across this window.

Window four. The exit ramp and the tail.

The final three to six months of the TSA are the exit ramp itself. Each service in the catalog migrates off the TSA on its scheduled date. Replacement vendors go live. Internal capability operates without seller support. The invoice declines each month as services drop off.

A working ramp is one document, one row per service, with columns for current scope, target exit date, exit option, responsible workstream lead, dependencies, replacement vendor, and status. The buyer runs the ramp from this document. The seller is held to its commitments against the same view.

A small number of services almost always run past the original end date. The buyer negotiates an extension term for these before the contractual end date, ideally at a capped fee rather than the seller's standard extension fee curve. A working extension is a short post-close services agreement with a hard end date, not a rolling continuation of the full TSA.

The exit ends when the seller has nothing left to bill and the Newco has nothing left to migrate. The contractual end date is the legal endpoint. The operational end date is the one that matters to the value creation plan.

The milestones that decide the schedule.

A working TSA timeline has roughly fifteen milestones. Each one is a decision point with a date, an owner, and a deliverable. Miss a milestone and the downstream work shifts. Miss three and the exit moves into extension fee territory.

A short version of the milestone set. Pre-signing redline complete. Service catalog locked. SLA package locked. Governance charter signed. Day One stand up live. Workstream cadence operational. Day 60 consumption review. Day 90 exit plan documented. Month 6 mid-TSA renegotiation kickoff. Month 9 first wave of service exits live. Month 12 mid-term governance review. Month 15 long lead items exited. Month 18 contractual end. Tail services under extension. Final invoice reconciliation closed.

Each milestone is a public commitment between the buyer and the seller. Each one is logged in the governance minutes. Each one carries a consequence if missed. A milestone that has no consequence is not a milestone. It is a calendar entry.

Buyers who run the milestone set as a discipline land their exits on schedule across multiple carve-outs. Buyers who let the milestones drift end up paying extension fees they never planned for.

Where buyers most often lose the timeline.

The most common timeline failure is not at the end. It is at day ninety, when the exit program is supposed to be documented and running, and instead the Newco is still firefighting Day One issues that should have been resolved in window two.

The second most common failure is at month six, when mid-TSA renegotiation is supposed to start and the buyer has not yet built the consumption data that would support a position. Renegotiation without data is a request. Renegotiation with data is an argument.

The third is at month twelve, when the long lead items should be scheduled and the IT separation is still being scoped. IT is almost always the longest workstream. Starting late on IT means the entire exit ramp shifts right by months.

A working timeline catches each of these failures early. A passive timeline catches them at the end, when the only remedy is an extension fee. The difference is the discipline of the buyer-side cadence, not the wording of the contract.

More on TSA exit strategy.