Selling AI to the Government? A New GSA Clause Takes Effect October 19 — Here's What It Requires

If your company sells software, services or tools that use a large language model (LLM) to federal agencies, a new General Services Administration (GSA) contract clause goes into effect on October 19. It sets rules for how you handle government data inside AI systems, how fast you report problems, and which of your subcontractors must follow along. The good news for small firms: GSA narrowed it after industry pushback.

What Changed

GSA issued the clause as a class deviation from its acquisition regulation, in a memo dated October 1. The clause is numbered GSAR 552.239-7001 and titled "Basic Safeguarding of Data within Large Language Model Artificial Intelligence Systems." It takes effect October 19, but contracting officers can use it sooner in new solicitations and contracts, and they have discretion to apply it to open and already-awarded contracts.

It works as policy until GSA rescinds it or turns it into a formal rule, which would include a public comment period. No dates have been set for that. GSA took two rounds of public comment, including more than 75 comments this summer, and held a July listening session before finalizing the language.

Who It Applies To

The clause applies when the government is buying an AI product that receives or produces government data. It expressly covers AI-enabled document and productivity tools.

It generally does not apply when:

• You use an LLM only inside your own internal business or operational systems, and those systems are not delivered to or accessed by the government.
• The LLM function is incidental to a product whose main purpose is not AI.

A contracting officer can still decide otherwise, so read each solicitation. If you only use AI to draft your own proposals or manage your own back office, you are probably outside the clause. If your deliverable includes a chatbot, summarizer, search tool or analysis feature built on an LLM, you are probably inside it.

What Contractors Must Do

Protect government data

One summary of the clause reports that contractors are barred from using government data to train public or proprietary LLMs, to inform advertising campaigns, or to hand the data to third parties. The same summary describes required cybersecurity controls, including encrypted data transmission and detailed audit logging. Check the actual clause text in your contract for the exact wording, since summaries vary.

Access to government data by cloud hosting, technical support, security and maintenance providers is allowed, but only as necessary to perform the contract.

Stay accurate and objective

Contractors must use "reasonable efforts" to design, train and configure the LLM to prioritize accuracy and objectivity, and to acknowledge uncertainty when information is incomplete or contradictory. GSA largely removed the "unbiased AI principles" language and the ban on embedding "partisan or ideological judgments" that appeared in earlier drafts. The government may still run automated assessments for bias, truthfulness, safety and unsolicited ideological content.

Report incidents and changes

• Incidents: You must report incidents affecting an LLM used in contract performance that may affect government data. In certain cases, FedRAMP or CISA reports can satisfy this.
• Material changes: You must notify the government within seven calendar days of any material change that materially increases output bias, reduces safety guardrails or behavioral constraints, or degrades performance or truthfulness.

Accept a suspension right

The clause says the government "retains the right to suspend use of the LLM at any time." An earlier June draft allowed suspension only until performance issues were addressed, so the final language is broader. Build that risk into your revenue forecasts for any AI-dependent contract.

The Subcontractor Question

GSA narrowed the flowdown after comments. It now applies to subcontractors only if they handle government data or perform AI design, development, deployment or operation and monitoring tasks. Prime contractors must use "best efforts" to vet AI subcontractors and remain responsible for implementing the clause.

The clause also defines "fully open" models, which publish architecture, weights, code and data, and "open-weight" models, which publish only weights. Primes do not need to flow down foreign-control requirements to fully open models or to other open-source components, but open-weight-only models do not get that exception.

One Number Small Firms Should Know

If a contract is terminated for cause, your liability for decommissioning costs is capped at 25% of the affected task or delivery order. That limit matters if you are a small business whose entire cash position could be wiped out by one contract dispute.

Key Dates

• October 1: GSA issued the class deviation memo.
• Early October: A draft of MAS Solicitation Refresh #34 was posted.
• October 19: The clause takes effect.
• November 2026: GSA expects to release Refresh #34, which is slated to include the clause for Multiple Award Schedule (MAS) contractors.

A Practical Checklist Before October 19

1. Inventory your AI. List every product or service you deliver to the government that uses an LLM, and note whether government data passes through it.
2. Map your data flows. Know where government data is stored, who can access it and whether your model provider uses customer inputs for training.
3. Check your vendor terms. Confirm that your LLM provider's contract allows the restrictions the clause requires. If it does not, you may need a different provider or a different plan tier.
4. Identify subcontractors in scope. Flag the ones who design, run or monitor your AI, or who touch government data, and plan to add the clause to their agreements.
5. Write an incident and change-notice procedure. Decide who decides what counts as a "material change" and who makes the seven-day call.
6. Review your coverage. Ask your broker whether your business insurance addresses cyber incidents and errors in AI output.
7. Watch your solicitations. Read the clause list in every new MAS refresh, task order and renewal.

What We Don't Know Yet

GSA does not plan to publish a line-by-line list of changes from the earlier draft, so you will need to read the final clause. Rulemaking dates are not set. Contracting officers have discretion on existing contracts, so two companies could be treated differently. If you hold a GSA contract, ask your contracting officer in writing whether the clause will be added to yours and when.

The Bottom Line

The final clause is more targeted than the earlier drafts: it focuses on government data and AI products the agency actually buys, and leaves most internal back-office AI use alone. For a small contractor, the work is mostly documentation: know where government data goes, make sure your AI vendors and subcontractors can meet the terms, and be ready to report changes within a week. The firms that start now will be ready when Refresh #34 arrives in November.

Sources: GSA class deviation memo as reported by FedScoop; Winvale; Defense Signals; PilieroMazza weekly update, October 8, 2026. This article is general information, not legal advice. Consult a government contracts attorney about your specific contract.

Photo by Scott Graham on Unsplash