What leaves with you, in what format, and how long it takes

Either party gives written notice. The exit clock starts on receipt, not on the next renewal date, and the estate continues to run unchanged for the whole of the exit period.

Owner Chief Procurement Officer · can start on day one

Contractual. Ninety days on the master agreement.

The exiting party states where the work goes — a successor platform, a return to the prior systems, or a hold state where the workflows keep running under human execution. The extract format depends on this answer and nothing else can start until it is given.

Owner Chief Operating Officer · follows EXT-01

This is the step most exit plans skip and the one that decides how much of the rest is possible.

No new agents promoted, no new workflows published, no authority changes. Existing agents keep running at their current stage. The estate stops being a moving target so the extract can be reconciled.

Owner Head of Agent Platform · follows EXT-02

The freeze is a configuration state that exists in the product. It has never been exercised across the whole estate.

All fourteen asset classes on this page, in the open formats listed, written to storage the exiting party controls. Checksummed and accompanied by a manifest.

Owner Head of Data and Analytics · follows EXT-03

Two assets have an export route. The other twelve are produced by hand. The fourteen-day figure assumes the hand-produced ones go right first time.

Row counts, control totals and a sampled record-level comparison, signed by finance for the commercial assets and by audit for the evidence and decision records.

Owner Group Financial Controller · follows EXT-04

No reconciliation procedure has been written. This step is a placeholder with an owner, which is more than most exit plans have and less than a buyer should accept.

The operating run-book: what each of the 475 workflows does, which stations require a person, the escalation ceilings, the kill switches and what each one stops, and the standing exceptions with their owners.

Owner Head of Global Business Services · follows EXT-03

The run-book is generated from the same tables the product reads, so it cannot go stale. It has never been handed to anyone outside the team that wrote it.

Which model each workflow calls, the contractual position with each provider, and whether the receiving party can inherit the agreements or must contract fresh. Self-hosted weights transfer with the storage; provider agreements generally do not transfer at all.

Owner Chief Procurement Officer · follows EXT-02

Only the Helix weights move cleanly. Abraxas and Corvid agreements are non-assignable and the receiving party contracts from zero.

The receiving destination processes the same inbound work alongside the estate for a defined period, with outcomes compared station by station before anything is switched off.

Owner Chief Operating Officer · follows EXT-06

Thirty days is an assumption, not a measurement. No parallel run has ever been performed.

The receiving party loads the extract and demonstrates that the operating model, the authority grants and the evidence trail are all readable and complete in the destination.

Owner Head of Internal Audit · follows EXT-08

Two of fourteen assets have ever been read back outside the product. This is the weakest link in the whole plan and it is the one the plan depends on.

Production data deleted, backups aged out on their existing cycle rather than deleted early, sub-processor instructions issued, and a signed deletion certificate produced listing every store and its completion date.

Owner Chief Information Security Officer · follows EXT-09

Backups age out over 35 days. Deletion is not instant and the certificate says so rather than pretending otherwise.