AI governance
GSA AI Clause: Five Decisions for AI Vendor Leaders
If you sell or resell AI tools to government buyers through GSA, the GSA AI clause now outranks your own terms. Your leaders need to settle five questions before the next order.
What is the GSA AI clause?
The clause is GSAR 552.239-7001, Basic Safeguarding of Data Within Large Language Model AI Systems. It took effect on October 19, 2026, as a class deviation.
GSA plans to add it to Schedule contracts through MAS Refresh 34, planned for November 2026. Current holders must accept that change within 90 days after it issues to keep selling on the schedule.
A formal rule will follow. The clause is in force now.
Does it apply to us?
It applies when the government buys an AI product where the language model is a key feature. Government data must also go into the model or come out of it.
Chatbots, assistants, agentic systems and AI document tools all count. So do commercial products.
Two cases drop out. One is AI you use only for your own back office.
The other is a minor AI feature in a product that is not AI. The feature must not be required, used by the government or fed government data.
Close calls are a judgment. Read the clause with your contracts counsel.
What happens to our terms of service?
They lose. If the clause conflicts with your terms of service, license, click wrap or other commercial terms, the clause wins.
The government owns its data and any custom work. You get a limited license to use that data to do the work, to support it, and for a few other narrow uses.
Decision one: who checks every customer contract, and every upstream vendor contract, against the clause?
Can we train our models on government data?
No. You may not use government data to train, fine tune or improve any language model. That includes third party models.
You also may not use it for marketing, sales or business strategy. You may not sell it, or keep it longer than the contract allows.
At contract end, you must delete it from all systems and backups. Model weights, embeddings, indexes and caches are included. Then you confirm the deletion in writing.
Decision two: does your data pipeline keep government data out of training and analytics by design?
What if our AI provider changes the model?
You still owe notice. Give the contracting officer 30 days of written notice before you add, replace or materially change a model or its provider.
You can skip that notice if the government gets access to the new model alongside the old one. That overlap must last at least 30 days for a major version and 15 days for a minor one.
Say your provider retires a model you do not control. Tell the contracting officer within 5 business days of the provider's notice.
A change that worsens bias, weakens safety guardrails or hurts accuracy must be reported within 7 days.
Decision three: do your upstream contracts make your provider warn you in time to meet these dates?
Who owns the two 72 hour clocks?
The clause has two.
One starts when you learn of a material violation of the clause. The other starts when you find a security incident in the model. It counts if it may touch government data.
The incident clock also needs daily updates until it is resolved. You must save logs for 90 days and complete the CISA incident form.
Decision four: name one owner for each clock, with a backup, before anything happens.
What else should leaders weigh?
The government may suspend use of your model at any time.
Say it ends the contract for cause after you fail to fix a problem. Then you may owe decommissioning costs. Those are capped at 25 percent of the affected order's value.
You must disclose which models process government data. The clause prefers models built and run in the United States.
Subcontractors doing AI work on government data get the clause too.
Decision five: which of your suppliers can show proof, not promises, that they meet it?
What is the next step?
Book a 30 minute call with the practice to put an owner on each of the five decisions.
Where are the sources?
GSA, RGO-2026-01 class deviation with GSAR 552.239-7001, Basic Safeguarding of Data Within Large Language Model AI Systems (Sept 2026): https://www.gsa.gov/system/files/RGO-2026-01-Signed_0.pdf
Wiley, GSA Releases Final Language of AI Contract Clause, October 13, 2026: https://www.wiley.law/alert-GSA-Releases-Final-Language-of-AI-Contract-Clause
Covington, Inside Government Contracts, GSA previews changes planned for the upcoming MAS Refresh, October 15, 2026: https://www.insidegovernmentcontracts.com/2026/10/gsa-previews-significant-changes-planned-for-upcoming-multiple-award-schedule-refresh/