Retained vs. Transitioned Capabilities

Definitions

• Retained Capabilities – Activities the parent continues to perform for its remaining businesses and does not duplicate for the carve-out (e.g., group-level treasury, corporate strategy).
• Transitioned Capabilities – Activities the carve-out must own, either stood up internally or sourced from third parties (e.g., entity-specific accounting, IT user support).
• Bridging Services (TSA) – Temporary support the parent provides until the carve-out’s replacement solution is live.

Retained vs. Transitioned Capability Decision

Strategic Relevance
• Retain: Core to the parent’s long-term business model.
• Transition: Essential to the carve-out’s independent autonomy.

Volume and Economies of Scale
• Retain: Material scale benefits remain within the parent organization.
• Transition: Lower-volume activity can be outsourced or insourced cost-effectively by the carve-out.

Information Sensitivity
• Retain: Shared data poses compliance risk if transferred outside the parent.
• Transition: Dedicated data required for the carve-out’s standalone reporting and control.

Timing and Complexity
• Retain: High-complexity functions are better left with the parent on a temporary basis.
• Transition: Low-complexity tasks can realistically be re-platformed ahead of Day 1.

Step-by-Step Classification Process

• Capability Inventory
  List every process and sub-process across Finance, IT, HR, Supply Chain, Commercial, and Risk.
• Criticality Rating
  Score each capability for customer impact, regulatory requirement, and Day 1 necessity.
• Feasibility Assessment
  Evaluate cost, systems dependence, and talent availability to stand up the capability in time.
• Classification Workshop
  Assign each capability to one of three buckets: Retained, Transition Day 1, TSA.
• Exit-Strategy Definition
  For every TSA item, document replacement approach, build timeline, and exit date.

Capability Transition Tracker

• Payroll Processing (U.S.)
  • Day 1 status: Provided via TSA
  • Replacement plan: Outsource to ADP
  • Target TSA exit: Month 6
• Board Reporting
  • Day 1 status: Fully transitioned
  • Replacement plan: Handled by in-house FP&A team
  • Target TSA exit: Not applicable
• Insurance Placement
  • Day 1 status: Retained by parent
  • Replacement plan: Parent continues corporate policies
  • Target TSA exit: Permanent arrangement

Best-Practice Guidelines

• Limit TSA scope to non-strategic, high-complexity functions; avoid locking the carve-out into multi-year dependence.
• Where economies of scale justify permanent outsourcing (e.g., payroll, travel), transition directly to a third-party provider instead of taking a two-step TSA approach.
• Use service-level agreements and pricing schedules to create cost transparency and incentivize timely TSA exit.
• Align capability hand-offs with system cutover waves to prevent dual running costs.

Deliverables Checklist

• Capability inventory with criticality and feasibility scores
• Retained / Transitioned / TSA classification matrix signed by functional leads
• TSA term sheet including service scope, SLAs, pricing, and exit dates
• Replacement-solution implementation roadmap with budget and resource owners

Common Pitfalls

• Over-classifying functions as TSA because early planning underestimates build-out speed
• Forgetting to negotiate parent access to carve-out data once TSA ends (e.g., for consolidated reporting)
• Underfunding replacement solutions, leading to TSA extensions and cost escalation

A disciplined retained-vs-transitioned analysis anchors TSA design, clarifies Day 1 readiness requirements, and ensures both organizations focus resources where they matter most.