The Race — Building Democracy in the Age of AI. People race toward a shared finish line.
The Race

Policy tool · See record

Contract exit rights

What the tool does

Agree in advance how an institution can stop using an AI supplier. Specify notice, transition assistance, data return and continuity so ending a contract does not also mean losing the ability to perform essential work.

Current status

An emerging procurement proposal in this record set. We have not verified a completed AI supplier exit under the proposed safeguards. Rights written into a contract and a successful transition are separate evidence.

Where it has been used

GSA’s contract exit protections

Added on

GSA adopted a standard contract clause on September 28 for government purchases in which a large language model is a material feature and directly receives or produces government data. Mandatory use in new covered purchases starts October 19; contracting officers may use it earlier. Incorporating it into an existing contract is a separate contracting decision. This is an adopted purchasing rule, not a single new supplier contract that every government can immediately order from.

The clause protects covered government inputs, outputs and custom developments; limits their reuse for training, sale and marketing; requires portable data and documented interfaces; and protects migration from obstructive charges. It includes reasonable human intervention and action traces, incident reporting within 72 hours, ordinarily 30 days' notice of material changes, and suspension and noncompliance remedies. Supplier ownership of pre-existing models and technology remains. Decommissioning liability after qualifying termination is capped at 25% of the affected order; replacement-system and reprocurement costs are excluded.

Eligible state, local and tribal governments and public educational institutions can use relevant GSA purchasing programmes within their statutory scope. If the underlying eligible contract contains this clause and the supplier accepts the non-federal order, its applicable terms carry into that separate purchase. Suppliers may reject those orders; eligibility, product category and incorporation must be checked for the particular purchase. The protection is therefore potentially reusable well beyond federal agencies, without assuming universal coverage or automatic amendment of all existing contracts.

Read more about this case →

The Right to Leave exit framework

Added by

The Race’s article, The Next AI Fight Is Over the Right to Leave, explains why a contract’s formal termination right is insufficient if data, permissions or workflows cannot move. It sets out the practical conditions for a usable alternative. The article is a proposed design framework, not evidence of a new customer right.

Read more about this case →

Britain’s review of cloud switching

Added on

A separate October 16 CMA report reviews actions AWS and Microsoft took between March and October. Its detailed account is more qualified than headlines suggesting that both companies have already connected all their clouds to rivals. AWS–Google interconnection is launched; Microsoft–Google remains a forthcoming preview, and UK AWS–Microsoft connections remain under development. The report also identifies updated switching-fee policies and operating channels through which customers and competitors can request interoperability.

The regulator finds limited uptake so far and continuing switching barriers. It will work next on translating identity/access permissions between clouds and moving applications packaged in Kubernetes, a common deployment system that can still depend on provider-specific services. These are future work areas. Voluntary engagement is not an enforceable order requiring every requested connection or a guarantee of seamless migration.

The Race mechanism is practical exit leverage. This concerns cloud switching, rather than designation of Microsoft’s business-software ecosystem. The report combines older launches, recent implementation and future promises; October 16 is the reporting date, not the start date of every customer right.

Read more about this case →

Source snapshot: 2026-10-17. Individual event and verification dates remain as recorded above. Inclusion alone does not assign a score.