Washington’s AI Contract Clause Arrives on 19 October
From 19 October, GSA contracts for chatbots, agents and other large language model tools must carry clause 552.239-7001. What it demands of vendors, and why state and local buyers on GSA schedules should read it too.
The main entrance to the General Services Administration headquarters at 1800 F Street NW, Washington DC.
America’s central buying agency has finished writing its rules for purchased AI. The General Services Administration’s (GSA) class-deviation memo RGO-2026-01, signed by Senior Procurement Executive Jeffrey A. Koses, now carries GSAR clause 552.239-7001, “Basic Safeguarding of Data within Large Language Model Artificial Intelligence Systems”. The memo’s Attachment A lists Part 552, which holds the clause, as effective on 19 October 2026; contracting officers may use it now and must from that date. FedScoop reported that GSA updated the memo on Monday; Attachment A’s latest signatures are dated 28 September. Through GSA’s schedules, the clause can reach beyond federal agencies.
Which Purchases the Clause Covers, and Which It Skips
Under section 539.71, the clause goes into GSA solicitations and contracts, commercial ones included, for an LLM, chatbot, generative assistant, agentic system or LLM-enabled productivity tool where the model is a material feature and government data is fed into or generated by it. It self-deletes where a contractor uses AI only for back-office work the government never touches, or where AI is incidental to a product bought for another purpose. For awarded contracts, adoption is the contracting officer’s call.
What Vendors Must Do: the Obligations in One Table
The table below, built from the clause text, reads each obligation for vendors and for state or local buyers ordering through GSA.
| Obligation (clause paragraph) | What it means for a vendor | What it means for a state/local buyer |
|---|---|---|
| Disclose LLMs (f)(1) | List the models processing government data, within 120 days unless the contract sets a date | An inventory of the models behind the tool |
| Flow-down and vetting (a)(2), (d) | Pass requirements to subcontractors handling government data in AI design, development, deployment or monitoring (NIST AI RMF 1.0, Appendix A), and vet them with best-efforts due diligence | Duties reach the model developer, not just the reseller |
| Data ownership and training (e) | Government owns inputs, outputs and custom work; no training, fine-tuning, marketing use or resale | Prompts and documents cannot improve a commercial model |
| Deletion at end (e)(4)(vii) | Erase government data, fine-tuned weights, embeddings and backups unless the contracting officer directs otherwise, and confirm in writing | A documented exit |
| US-controlled models (f)(2) | Maximise use of LLMs developed and operated in the US; no core components controlled by adversary governments | A preference, though adversary-controlled core components are “prohibited” |
| Incidents and changes (f)(5), (i) | Report incidents within 72 hours, with daily updates; give 30 days’ notice of model or provider changes; flag safety or bias degradation within seven days | Early warning before the model underneath changes |
| Government rights (j) | Accept automated testing for bias, truthfulness and “unsolicited ideological content”, suspension “at any time”, and decommissioning liability capped at 25 per cent of the order | Testing and suspension rights sit with “the Government” |
Why State and County Buyers Inherit It
The clause defines “Government” as any entity authorised to buy through GSA under 40 U.S.C. 501 and 502. Section 502(c), implemented as GSA’s Cooperative Purchasing programme, lets state and local governments order from its Information Technology category. Under the schedule terms in the same deviation package (Part 538, effective 30 November), such an order incorporates the schedule contract’s terms by reference, with limited exceptions, and vendors may turn it down within five business days. In this desk’s reading, a county that buys an LLM tool where the clause sits in the underlying schedule contract receives its data protections and its evaluation and suspension rights.
Where the “Ideological Content” Language Comes From
The clause takes its LLM definition from Executive Order 14319, Preventing Woke AI in the Federal Government (23 July 2025), whose “truth-seeking” principle its accuracy duty echoes and which charges decommissioning costs to vendors. FedScoop reported that most “unbiased AI principles” wording was cut, and that Palantir called for the rule’s withdrawal. Corynne McSherry of the Electronic Frontier Foundation told FedScoop some language remained “somewhat alarming”. America.gov’s opinionated chatbot shows why neutrality tests matter.
The text has moved since GSA’s Federal Register notice of 17 June 2026, which followed a 12 January draft and preceded a 14 July listening session. Tested against the National Defense Industrial Association’s comment letter of 3 April 2026, the final text concedes two asks, a back-office exclusion and relief for open-source components, but keeps the clause’s precedence over commercial licence terms, which NDIA wanted removed or revised. NDIA had also sought a delay of at least 90 days after final schedule terms.
What Decision-Makers Should Watch
Procurement chiefs should map existing AI orders against the clause before 19 October; state CIOs should ask vendors whether schedule offerings carry it. Defence buyers face parallel pressures, as Guardrails for Hire described; this week’s cover on incident-notification rules and Ghana’s central review show other governments converging on similar controls. The memo promises formal rulemaking with full notice and comment.
Sources
- RGO-2026-01: GSA Acquisition Regulation (GSAR) Class Deviations in Response to Executive Order 14275, incl. Attachment A and clause 552.239-7001 — U.S. General Services Administration, Office of Acquisition Policy — memo dated 15 January 2026; clause dated “(GSAR Deviation)(Sept 2026)”; Part 552 effective 19 October 2026 per Attachment A; (PDF)
- GSA issued an AI acquisition policy for new contracts. Here’s what it says. — FedScoop — 1 October 2026
- ‘Hallelujah’: Stakeholders react with praise and concern to GSA AI acquisitions clause — FedScoop — 6 October 2026
- Preventing Woke AI in the Federal Government (Executive Order 14319) — The White House — 23 July 2025
- General Services Acquisition Regulation; Acquisition of Information and Communication Technology; Notice of Listening Sessions and Request for Comments — Federal Register (GSA) — 17 June 2026
- Re: GSA General Services Acquisition Regulation Deviation 552.239-7001 — National Defense Industrial Association — 3 April 2026; (PDF); industry association position
Discussion
No comments yet. Start the conversation.
