TSA exit reports and snapshots

Two related things live here: the formal notifications you send the seller, and the reporting on where the exit programme stands.

Exit notifications

An exit notification is the document that formally tells the seller you are exiting a service. Each one carries an approval workflow, an AI-assisted draft, a legal review step and a record of delivery to the seller's TSA lead.

1. Create the notification against the service.
2. Review the draft. The AI produces the first version from the service record and the addendum's own terms; you are the one who signs it.
3. Route it for approval and legal review.
4. Record delivery. The notice date is what the tracker's arithmetic has been counting down to.

Reports and snapshots

TSA exit status is a report configuration in Report Centre like any other, so the pack is composed from live tracker data: services by status, exits achieved against plan, services at risk, and the notice dates coming up.

Snapshots preserve the position as at a date. That matters on a carve-out more than elsewhere, because disputes about what was in scope, and when, are settled by what the record said at the time rather than by what it says now.

A caution on timing

Compose the pack before the meeting. A composition takes a few minutes, and a steerco waiting on a deck is a poor use of eight expensive people.