GSA’s Proposed AI Clause (GSAR 552.239-7001) Enters Formal Rulemaking: Re-Scoped with Four-Role Flowdown Framework and Under Heavy Industry Pushback

GSA’s Proposed AI Clause (GSAR 552.239-7001) Enters Formal Rulemaking: Re-Scoped with Four-Role Flowdown Framework and Under Heavy Industry Pushback

The General Services Administration (GSA) has officially advanced its highly anticipated AI procurement clause into formal rulemaking. Following intense industry criticism of its initial March 6, 2026 draft, which was introduced through MAS Refresh 31, GSA published a substantially revised proposed contract clause in the Federal Register on June 17, 2026.

The revised clause, now titled GSAR 552.239-7001, “Basic Safeguarding of Data within Large Language Model Artificial Intelligence Systems (LLMs),” represents a major shift in how the federal government purchases AI and LLM technologies. The public comment period for this revised rule officially closed on August 3, 2026, drawing sharp feedback from major industry groups.

Key Revisions in the June 17, 2026 Draft

In response to initial industry feedback, GSA made several significant concessions while simultaneously tightening compliance requirements in other areas:

1. Narrower Scope, Broader Contractual Reach: The March draft applied whenever AI capabilities were used "in performing" a GSA contract—a trigger broad enough to sweep in any contractor using AI tools in any context. The June version narrows this to apply only when government data—defined as "Data Inputs" (prompts, source data) and "Data Outputs" (responses, synthetic data, metadata)—is processed by an LLM. It explicitly excludes LLMs embedded in common commercial products (e.g., word processors, map-navigation systems) and those incidental to the contract's primary purpose. However, the clause now amends the GSAR generally, meaning it will apply across all GSA-administered contracts and solicitations, not just MAS contracts.
2. Removal of the "Any Lawful Purpose" License: The March draft granted the government an irrevocable, unlimited license to use the contractor's AI system "for any lawful Government purpose." The June version removes this provision, limiting the government's license to the specific purposes and scope of work defined in the contract and reaching only commercially available features.
3. Softened "American AI" Prohibitions: The initial draft flatly prohibited using foreign AI systems or components (including open-source model components). The June version replaces this with a "maximize the use of" standard, requiring contractors to maximize their use of LLMs that meet US jurisdiction-and-control criteria, with risk-based carve-outs for open-source components and published research.
4. The Four-Role Supply Chain Framework: To address the unworkable burden of making prime contractors responsible for every AI service provider in their supply chain, GSA replaced the single "Service Provider" definition with a four-role framework:
   • LLM Developer
   • LLM System Operator
   • LLM System Integrator
   • LLM Service Provider Each role has its own flowdown supplemental clause (552.239-7001-1 through -4) with calibrated obligations.
5. Strengthened "Unbiased AI" Obligations: The Unbiased AI provisions are the one area where GSA strengthened its requirements. The June version drops the "make commercial efforts to ensure" qualifier, creating a strict, unqualified obligation for contractors to "ensure" compliance with the Unbiased AI Principles (truthful, objective, ideologically neutral, and free from manipulation in favor of "ideological dogma"). The government retains the right to run unannounced automated assessments at any time using undisclosed benchmarks¹, and contractors remain liable for decommissioning costs if terminated for cause (with a cap set by the contracting officer).
6. Background Data Protections: The June version defines "Background Data" to include pre-existing proprietary content and IP owned by the contractor, explicitly letting the contractor retain ownership of that data in its original form.

Industry Feedback: The August 3, 2026 Comment Deadline

Industry groups, including the Professional Services Council (PSC), submitted formal comments on the revised draft on August 3, 2026. While welcoming several of GSA's revisions (such as the narrower license grant, preserved contractor IP ownership, and the shift toward risk-based foreign-ownership screening), the PSC and other stakeholders raised several critical concerns:

• Unworkable Flowdowns for Open-Weight Models: The PSC flagged that the four-role flowdown framework remains unworkable for developers of open-weight models, who have no direct relationship with the government and may not know their models are being deployed in federal contracts.
• Scope Clarification: Industry groups urged GSA to further clarify the boundaries of the clause's scope, particularly around what constitutes "Government usage context."
• Small Business Burdens: Commenters warned that the strict compliance, auditing, and "Unbiased AI" certification requirements would place a disproportionate and potentially exclusionary compliance burden on small businesses and startups.
• Phased Implementation: The PSC urged GSA to adopt a phased implementation timeline rather than forcing immediate compliance across all GSA contracts.

For commercial B2B founders selling to the federal government or to prime government contractors, GSAR 552.239-7001 is a critical regulatory development. Even in its revised form, the clause imposes strict data-handling, disclosure, and unbiased-output obligations that flow down the supply chain, requiring vendors to carefully evaluate their LLM integrations and data-handling policies.