Using the TSA Tracker

The tracker is the working surface for a carve-out. It answers the question a separation steerco actually asks: which services are still running, who owns getting off them, and which ones are going to be late.

What is in a row

The service, the workstream it belongs to, its exit date, its owner, its status and its programme risk. Status and risk are separate columns on purpose: a service can be on track and still be the riskiest thing in the programme.

The notice arithmetic

This is the part that catches people out. The date you have to act on is not the exit date; it is the exit date less the transition period less the contractual notice period. The tracker does that subtraction for you and shows how many days you have left before you must serve notice.

If you set a notice period shorter than the addendum specifies, you are warned but not blocked. You may still proceed, and the seller may accept or dispute it. That is a commercial call, not a system rule.

Status through the exit

TSA services carry their own status vocabulary rather than the work plan's: not started, on track, at risk, complete and exited. Exited is the one that matters; complete work is not the same as a service that has actually been switched off.

Keeping it current

The tracker is populated automatically from the import, then maintained by you as the exits proceed. Where you have built work plans from the addendum, the plan and the tracker are two views of the same programme rather than two lists to reconcile.