Practical guide · Solenor editorial · October 7, 2026
What to Include in a Carve-Out TSA Schedule
A practical checklist for transition service agreement schedules: scope, price, duration, service ownership, dependencies and exit assumptions.
What should a TSA schedule contain?
A transition service agreement (TSA) schedule should identify each service, provider and recipient, scope, pricing basis, duration, extension and exit conditions, responsibilities and dependencies. Link contractual terms to the agreement and distinguish them from management estimates and unresolved assumptions.
AI can help extract candidate terms and compare documents. Financial validation and legal interpretation must remain with the relevant professionals; generated schedules are drafts.
Service-level checklist
Start from the signed agreement or clearly identified draft version. Record whether each value is contractual, estimated or outstanding. A short label such as IT support is insufficient if the service includes ERP access, infrastructure, licenses and migration assistance.
- Service scope and responsible parties
- Price, currency, tax and billing basis
- Duration, extensions and termination
- Dependencies and migration milestones
- Service levels and escalation process
- Source reference and open questions
Keep cost categories separate
Distinguish recurring TSA fees, replacement standalone costs, one-off separation expenditure and seller-retained stranded costs. Identify overlaps with the EBITDA bridge and implementation budget to avoid double counting.
Model the timing of service exit rather than assuming every service ends at closing or at the same date. Record renewal provisions and the cost consequences of delays.
Illustrative example: ERP access
A fictional shared ERP service costs €45k per month for 12 months. Its simple base fee is €540k. That amount excludes taxes, scope changes, extensions, migration expenditure and replacement operating costs unless the source agreement expressly includes them.
Verify licensing rights, user scope, hosting dependencies, migration milestones and exit assistance. Link each assumption to its source and ask management or legal counsel to resolve unsupported terms. This is an illustrative calculation, not a customer case study.
Validate the draft before relying on it
Have the operational owner confirm service scope and dependencies, finance reconcile pricing and cost categories, and legal counsel review contractual rights and obligations. Retain disagreements and incomplete evidence in the schedule.
Agree source access, confidentiality and deployment boundaries before using an AI tool with transaction contracts. The reference below provides general AI governance guidance, not a legal TSA template.
References and scope
Solenor editorial methodology. These sources provide AI governance context and describe our practices; they do not certify the product or financial conclusions. Published October 7, 2026.
Founding team
Discuss your review workflow
Review your scope and requirements with the team before sharing sensitive data.