Free companion page
Free to print: The Reading Checklist: Forty Questions for Any Transition Services Agreement, from How to Read a Transition Services Agreement.
This page is free and needs no sign-up. It reproduces material from How to Read a Transition Services Agreement by Julian R. Sterling so you can print it or keep it open while you work.
To print it, use your browser's print button. Figures are as stated in the book; check the official source before relying on any of them.
Before you sign a TSA, before you price one into a deal, and before you plan the exit from one, read it once more against forty questions. They are the last thing on the desk, not the first: by the time you use them, you should know the deal, the services and the people. Their job is to catch the gap that eleven chapters of reading can still leave open.
Each question below comes with one sentence on why it matters and a pointer to the chapter that treats it. They apply to any TSA, whether you sit with the seller, like Cedarline Industries, or with the buyer, like Wexcombe Capital Partners and Orrin Controls Holdings. Where a question names Cedarline's TSA manager, Orrin's TSA manager or the TSA steering committee, read it as the roles in your own deal.
Does every service the business received before closing appear in a schedule? Anything missing will be discovered after closing, when it is hardest to add (Chapters 1 and 3).
Does the agreement separate the master terms from the service schedules, and say which prevails in a conflict? A schedule that contradicts the master terms without an order of precedence invites a dispute (Chapter 2).
Does each schedule describe the service in concrete terms: what is done, how often, by whom and for whom? Vague descriptions become arguments about scope the first time something goes wrong (Chapter 3).
Are informal help and shared resources that never had a cost center listed somewhere? Favors from the parent's staff are the services most often left out (Chapters 3 and 7).
Does each schedule name provider and recipient contacts by role? Named individuals leave; roles do not (Chapters 2 and 8).
Does each schedule state its dependencies, meaning what the recipient must supply for the provider to perform? A provider cannot be measured on a service the recipient starved of inputs (Chapter 3).
Is there a process for adding an omitted service after closing, with a price rule? Without one, every addition is a fresh negotiation under time pressure (Chapters 2 and 3).
Are there reverse services from the business sold back to its former parent, and are they in the same agreement or a separate one? Reverse services change the economics and the leverage on both sides (Chapters 1 and 10).
What standard of care does the provider promise: as before closing, a reasonable standard, or something higher? The standard decides what counts as a failure at all (Chapter 3).
Does the provider exclude professional advice, system changes and improvements? These exclusions are common and protect the provider from scope creep (Chapters 2 and 3).
Which services carry measurable service levels, and how is each measured? A service level that cannot be measured cannot trigger a credit (Chapter 3).
What service credit applies for a miss, and how is it calculated? In the case, a payroll pay-date miss earned a credit of a set share of the monthly fee, a model worth comparing against (Chapters 3 and 8).
Is a service credit the sole remedy for a service level failure, or can the recipient also claim damages? The answer can shut out a damages claim even below the cap (Chapters 3 and 9).
What must the provider do after a miss besides granting a credit? A root-cause report or a corrective plan is often worth more than the credit itself (Chapters 3 and 8).
Is each fee set at cost, cost plus a markup, or a scheduled amount? The method tells you what each side is trying to protect (Chapter 4).
What counts as cost: direct labor only, or also overhead, licences, space and allocated corporate charges? The definition of cost moves the fee more than the markup does (Chapter 4).
Can the recipient see the cost build-up behind each fee, and audit it? A cost-based fee without visibility is a scheduled fee in disguise (Chapter 4).
Can the provider pass through third-party costs, and does any charge above a threshold need the recipient's prior approval? Pass-through charges can arrive late and large (Chapters 4 and 10).
How often are invoices issued, when are they due, and what interest applies to late payment? Payment terms and late interest are the provider's protection against becoming the recipient's lender (Chapter 4).
Can fees change during the term, for example for cost increases or volume changes? A fixed fee and an adjustable fee carry different risks for each side (Chapter 4).
Is there a process for disputing an invoice without withholding payment on the undisputed part? Disputes over one line should not stop payment of the rest (Chapters 4 and 9).
What is the initial term of each service, and when does each end? A timeline of every end date is the backbone of the exit plan (Chapter 5).
Is there an outside date beyond which no service can run? The outside date is the one fixed point that every extension must respect (Chapter 5).
Can the recipient extend a service, on what notice and at what price? Extensions usually cost more, and step-ups are designed to discourage staying (Chapter 5).
Can the recipient end a service early, on what notice, and with what charge? Early exit saves fees, but notice periods and exit charges can erase the saving (Chapters 5 and 10).
Are there minimum service periods? A minimum period limits how early a recipient can leave (Chapters 5 and 10).
Does ending one service force the end of another that depends on it? Linked services can turn one exit into several (Chapters 2 and 5).
Does each schedule list concrete exit steps with owners and deadlines? An exit defined only by a date leaves the steps to be argued about at the worst moment (Chapters 5 and 7).
Which services depend on third-party licences or contracts that need consent to serve the recipient? A missing consent can stop a service on Day 1 (Chapter 6).
Who obtains each consent, who pays for it, and what happens if it is refused? A refused consent needs a fallback written before closing (Chapter 6).
Who owns the recipient's data while the provider holds it, and who may access it? Ownership is usually clear; access and use are where disputes start (Chapter 7).
Does every data extract have a format, a frequency, a validation step and a rerun deadline? A corrupted extract is an operational problem before it is a legal one (Chapter 7).
Are security and data processing duties written in both directions, with breach notice and return or deletion at the end? The recipient's users can be the provider's weakest point, and the reverse (Chapter 7).
Is it clear which people move, which stay, and which stay but serve under the TSA, and who directs their work? Blurred lines between employers create problems for both sides (Chapter 8).
How is the liability cap measured: which fees, over what period, and per claim or in aggregate? A cap on a look-back window can shrink late in the term, when failures are most likely (Chapter 9).
Does the agreement exclude consequential damages, and does it name lost profits expressly? The exclusion often does more work than the cap (Chapter 9).
What falls outside the cap and the exclusion, and how are those carve-outs defined? Definitions of willful misconduct and confidentiality decide how wide the carve-outs really are (Chapter 9).
Is there a TSA manager on each side, a steering committee and an escalation ladder with time limits? Governance that works on small problems is the only kind that works on large ones (Chapters 2 and 9).
What stranded costs will the provider carry when each service ends, and does any clause shift them to the recipient? The seller's tail shapes its behavior throughout the term (Chapter 10).
Has the recipient priced its exit costs against the fees each exit avoids, including the risks no price captures? The cheapest exit on paper is not always the safest (Chapters 10 and 11).
A checklist is only as useful as the reading behind it. The forty questions do not replace reading the agreement end to end; they test whether that reading was complete. The best use is to answer each one in writing, with a reference to the clause or schedule that answers it, and to mark every question the agreement leaves open.
Open questions are not always drafting failures. A TSA is negotiated quickly, often in the last weeks before closing, and some points are left to the TSA managers and the steering committee by design. What matters is that both sides know which points are open, and agree on how they will be settled, before the first service is tested.
In the case, the events that tested Cedarline and Orrin map to a handful of these questions: the payroll miss to questions 12 to 14, the data incident to questions 32 and 35 to 37, the ERP decision to questions 24, 25 and 40, and the stranded costs to question 39. A reader who had answered those questions in writing before Day 1 would have known, in each case, where the agreement stood.
Key Takeaway: Forty questions, grouped as scope, service levels, pricing, term and exit, consents and data and people, and liability, governance and stranded costs, are the last reading before signing, pricing or leaving a TSA. Answer each in writing with a clause reference and mark every open point. In the case, the payroll miss, the data incident, the ERP decision and the stranded costs each map to questions a careful reader could have answered before Day 1.