The contract sets the rules. The schedule lists the services.

Section 01

The contract and the schedule are different layers. Rules and inventory.

The Transition Services Agreement is the master legal document. It establishes the framework that applies to every service: how pricing works, how service levels are measured, how disputes are handled, how the buyer exits, what the liability caps are, and how governance operates. It is written once and governs the whole arrangement. What it does not contain is the actual list of services.

That list lives in the schedules, sometimes called transition service schedules or service exhibits. Each schedule describes one service or one functional area: what the seller provides, at what price, to what service level, with what dependencies, and until what date. The schedules are where the deal becomes concrete, because they are where the buyer can see exactly what it is buying and exactly what it will have to replace.

Reading the master contract without the schedules tells the buyer the rules of the game but not the game itself. A perfectly drafted master TSA attached to vague, incomplete, or seller favorable schedules still produces a bad outcome. The protection the buyer thinks it has in the contract is only as good as the detail captured in the schedules underneath it.

Section 02

What a good schedule contains. Specific, not summary.

A usable schedule names the service precisely, describes what is included and what is excluded, states the price and the pricing basis, sets the service level and measurement, lists the dependencies the service relies on, and gives a duration with an exit date. Each of those elements has to be specific. A schedule that says finance support with no scope boundary is an invitation to dispute everything that is not obviously in or out.

Exclusions matter as much as inclusions. A schedule that lists what the seller will do but not what it will not do leaves the boundary to interpretation, and interpretation favors whoever is less eager to perform. Clear exclusions prevent the seller from declining reasonable requests and prevent the buyer from assuming services that were never priced.

Dependencies deserve special attention. Many services in a carve-out depend on other services, on third-party vendors, or on access the buyer assumes it has. A schedule that names its dependencies lets the buyer sequence its exit correctly. A schedule that hides them produces the unpleasant discovery, mid migration, that exiting one service breaks three others.

Section 03

Where cost and risk actually concentrate. In the line items.

The schedules are where cost concentrates, because they hold the prices. A master TSA might say pricing is cost-plus with a defined mark-up, but the schedules say what the base cost is for each service, and that is where overcharging hides. Buyers who validate the master pricing rule but never test the line item costs in the schedules routinely overpay.

Risk concentrates in the schedules too. The service levels that protect daily operations live there, attached to each service. The exit dates that drive the migration plan live there. The dependencies that determine exit sequencing live there. Every operational variable the buyer has to manage during transition is captured, or omitted, at the schedule level.

This is why a buyer-side review spends as much time in the schedules as in the master contract. The contract is negotiated once and rarely revisited. The schedules are where the buyer will live for the entire transition, paying the prices, holding the service levels, and tracking the exits they define. Weak schedules are expensive in a way a strong master contract cannot fix.

There is also a volume trap worth naming. Many schedules price a service against an assumed level of usage, then leave the consequences of higher usage to a vague reference back to the master pricing rule. The buyer that does not test the assumed volumes can find the actual charges running well above the headline price once real demand lands. Each schedule should state its volume assumptions, its unit of measure, and what happens above the assumed level, so the price the buyer validated is the price the buyer pays.

Section 04

How schedules drive the exit. One line at a time.

A clean exit is executed schedule by schedule, not contract by contract. The buyer migrates off one service, terminates that schedule, stops paying for it, and moves to the next. The master contract continues to govern, but the buyer’s footprint shrinks as schedules are retired. For this to work, each schedule needs an independent exit date and termination mechanic so services can be exited individually rather than all at once.

Schedules that bundle many services under a single end date prevent this. If a buyer is ready to leave payroll but the schedule ties payroll to a dozen other services with a shared termination date, the buyer keeps paying for payroll until the slowest service in the bundle is done. Unbundling the schedules so each service can be exited on its own timeline is a core buyer-side ask.

The exit ramp the buyer negotiates is really a set of schedule level off ramps, each with its own date and its own dependencies. Managing the transition means tracking those off ramps against the migration plan and retiring schedules as the work completes. The structure of the schedules either enables that or fights it.

Section 05

What the buyer should require. Detail and independence.

The buyer should require schedules that are specific, complete, individually priced, individually service leveled, and individually exitable. Each service should stand on its own so the buyer can validate its cost, manage its performance, and exit it on its own schedule. Vague or bundled schedules should be sent back for detail before signing, while the buyer still has leverage.

The buyer should also require that the schedules reconcile with the service catalog and the migration plan. The same services should appear consistently across all three, with matching scope, price, and dates. Discrepancies between the catalog, the schedules, and the plan are where disputes and surprises originate, and they are far cheaper to fix on paper than in operation.

All of this is the work of reading the schedules as carefully as the contract, line by line, before signing. The master TSA sets the rules, but the schedules are where the buyer wins or loses. A disciplined review that pairs the two is what turns a transition into a managed exit rather than an open ended dependency. The cost of that review is small against the cost of a single mispriced or unexitable schedule discovered after close, when the buyer has already paid and the leverage to renegotiate is gone.

FAQ

TSA and schedule questions buyers ask.

Is a transition services schedule the same as the TSA?

No. The TSA is the master contract that sets the legal and commercial rules. The schedules are the attachments that list each actual service with its price, service level, dependencies, and exit date. The contract is the rulebook and the schedules are the inventory.

Why do the schedules matter more than buyers expect?

Because the schedules hold the prices, the service levels, the dependencies, and the exit dates for every individual service. That is where cost and operational risk concentrate. A strong master contract attached to weak schedules still produces a bad outcome.

Should each service have its own exit date?

Yes. Independent exit dates let the buyer migrate off and stop paying for one service at a time. Schedules that bundle services under a single shared end date force the buyer to keep paying for finished services until the slowest one in the bundle is done.

What makes a schedule weak?

Vague scope, missing exclusions, hidden dependencies, bundled pricing, and a single shared exit date. Any of these shifts interpretation and cost toward the seller. Buyers should require specific, complete, individually priced and individually exitable schedules before signing.

Related Reading

More on the TSA cluster.