Does your software have an AI assistant inside it? If you sell that software to the federal government, a new rule already applies to you, and it took effect before most small businesses even heard about it.
On October 19, 2026, the General Services Administration (GSA) put a new contract clause into force for systems built on large language models (LLMs), the technology behind chatbots and generative assistants. The clause is GSAR 552.239-7001, and it changes what you promise the moment government data touches your AI.
This guide covers what the GSA AI clause is, who it covers, what it asks of you, and the steps a small contractor should take now.
What the GSA AI Clause Is
The clause is titled “Basic Safeguarding of Data within Large Language Model Artificial Intelligence Systems.” GSA issued it through a class deviation known as RGO-2026-01.
A class deviation matters here. It means the clause works as GSA policy right now, while the formal rulemaking, including a public comment period, follows later. You do not get to wait for the final rule.
GSA did not spring this overnight. The agency released an early draft in March 2026, revised it for public comment in June, and announced the final text on September 28. Industry pushed back hard on the first version. The clause you have today is narrower than the one GSA started with.
Who the Clause Covers, and Who It Does Not
The clause does not touch every contractor who happens to use AI. Two things must both be true for it to apply.
First, LLM functionality has to be a material feature of what the government is buying. Second, government data has to be submitted to or produced by that LLM.
When both hold, the clause reaches a wide range of products: LLMs themselves, generative assistants, chatbots, agentic systems, and LLM-enabled productivity tools. It applies to commercial products, not only things marketed as “AI.”
The Carve-Outs
The clause steps back in two situations. Knowing them tells you whether you are even in scope.
- Internal, back-office use. If your LLM runs only inside your own business or performance-support systems, and the government neither buys it nor accesses it, the clause does not apply. That holds even if those systems incidentally process government data.
- Incidental or ancillary features. If LLM functionality is a minor part of a product whose main purpose is something else, the government does not require or access it, and it does not process government data, the clause steps back.
One caution. GSA has not clearly defined “incidental or ancillary,” so its reading of these carve-outs will decide close cases. Read the clause text against your actual product before you assume you are exempt.
Picture two small vendors. One sells a contract-writing assistant, where agency staff type sensitive data straight into the model. That sits squarely in scope. The other sells a scheduling app that uses an LLM only to suggest email subject lines, with no government data going into the model. That one likely falls outside it. Same technology, different answer, decided by the two-part test.
What the Clause Requires When It Applies
The obligations are real, and several reach into how you build and run your product. These are the ones small vendors should study first.
No training on government data. You cannot use government data to train, fine-tune, or improve any LLM. You also cannot use it to make business decisions or sell or license it.
The government keeps its data. The government retains full ownership of all government data. You keep your underlying model, your base models, and your background data, and you get only a limited, revocable license to use government data for performance and security.
Fast breach reporting. You must notify the contracting officer within 72 hours of learning of a material violation of the clause. Standard incident-response steps may not be enough, so build a workflow that meets this specific trigger.
Notice before model changes. You have to give 30 days’ notice before you replace or materially change a model, unless you give concurrent access to the successor. This applies whether the change is yours or an upstream provider’s.
Clean deletion at the end. When the contract ends, you delete the government’s data, including fine-tuned model weights and embeddings, unless the contracting officer directs otherwise in writing.
Your data export also has to work in open, standard, machine-readable formats, so the government can take its information and leave.
The Commercial Terms You Must Re-Read
Here is the provision that catches software sellers off guard. The clause takes precedence over conflicting commercial terms. Your standard terms of service do not override it.
For a small business that resells or builds on a third-party model, that order of precedence is the trap. Your vendor agreement, your license, and your privacy terms all sit below this clause when they conflict.
The enforcement side carries weight too. Noncompliance can expose you to the government restricting your use and to transition or wind-down costs. Read the exact consequence and cost language in the clause before you sign, since those terms drive your real risk.
| Obligation | What it means for you |
| No training on government data | You cannot improve your model with what the government feeds it |
| 72-hour reporting | Tell the contracting officer within 72 hours of a material violation |
| Model-change notice | 30 days’ notice, or concurrent access to the successor model |
| Data deletion | Remove government data, weights, and embeddings at contract end |
| Order of precedence | The clause beats your conflicting commercial terms |
When It Reaches Your Schedule: MAS Refresh 34
For Multiple Award Schedule (MAS) holders, the clause is set to arrive through MAS Refresh 34. GSA’s advance notice points to a release in November 2026, though the exact date has moved in reporting, so confirm the live date before you act.
Expect a mass modification to review and accept. Reporting indicates contractors get up to 90 days to accept it once the refresh is final. The practical window to prepare is short either way.
What Small Contractors Should Do Now
You do not need a legal team to get ahead of this. A few focused steps cover most of the risk.
First, inventory every product or service you sell that includes LLM functionality, and decide whether the clause applies or a carve-out fits.
Second, map your AI supply chain. Find which model providers or subcontractors touch government data, and check whether you can get the commitments the clause expects.
Third, compare your commercial terms of service against the order-of-precedence rule, so nothing conflicts by surprise.
Fourth, build an access log and a breach-reporting workflow now, tuned to the 72-hour material-violation trigger, not after an award.
Finally, watch for the formal rulemaking notice, because the language can still shift. None of this is legal advice, so confirm the final clause text before you rely on any single reading.
How CyberX Gov Solutions Can Help
A new clause like this lands on small teams that do not have a compliance department. That is where outside help earns its keep.
CyberX Gov Solutions supports small businesses through Get Fed Ready™, our GovCon readiness program. We help you read new contract terms, update your compliance and capability documentation, and get your registrations and representations in order.
When the change means a Schedule modification or a proposal update, our proposal development team helps you respond accurately and on time. The goal is simple: keep you compliant and competitive without losing weeks to guesswork.
Conclusion
The GSA AI clause is a signal of where federal AI buying is headed. Government data gets strict protection, and the contractor carries the duty to prove it.
For a small business, the move is not a panic. It is a careful read of your own product against the scope, a check of your supply chain and terms, and a workflow ready before your Schedule refreshes.
Not sure where your offering stands under the new clause? Talk to the CyberX Gov Solutions team or schedule a consultation at cyberxgovsolutions.com/schedule-a-meeting/.
Frequently Asked Questions
What is GSAR 552.239-7001?
It is GSA’s new contract clause on safeguarding government data inside large language model systems. GSA issued it as class deviation RGO-2026-01, and it took effect on October 19, 2026.
Does the clause apply if I only use AI inside my own company?
Generally no. If your LLM runs only in your internal or back-office systems, and the government neither buys nor accesses it, the clause steps back, even if those systems incidentally process government data.
Can I use government data to improve my AI model?
No. The clause bars you from using government data to train, fine-tune, or improve any LLM. You also cannot use it to inform business decisions or to sell or license it.
How fast do I have to report a problem?
You must notify the contracting officer within 72 hours of learning of a material violation of the clause. Ordinary incident-response procedures may not meet this standard on their own.
Is this a final federal rule?
Not yet. It is a class deviation, which works as GSA policy now, with formal rulemaking and a public comment period still to come. The language could change.
When will the clause appear on my Schedule?
GSA plans to add it through MAS Refresh 34, expected in November 2026. Confirm the current date, since it has shifted, and expect a mass modification to accept.
