If your business touches AI on a GSA contract, mark August 3, 2026. That’s the deadline to comment on GSA’s revised proposed clause 552.239-7001, “Basic Safeguarding of Data within Large Language Model Artificial Intelligence Systems (LLMs),” published June 17, 2026 in the Federal Register (Crowell & Moring, 2026; Wiley, 2026). It’s a significant rewrite of a March 2026 draft that drew heavy industry pushback for being too broad (Jenner & Block, 2026).
Who it reaches
The clause applies to GSA contracts where an LLM processes “Government Data.” It exempts LLMs embedded in common commercial products, or where the LLM functionality is incidental to the primary purpose of what’s being procured (Crowell & Moring, 2026). Crucially, the obligations flow down the entire LLM supply chain — developers, operators, integrators, and service providers who may never sign the prime contract (Holland & Knight, 2026).
What it requires
- Government data ownership and strict use restrictions, plus “eyes off” data handling.
- Storing or processing government data only when reasonably necessary to perform the contract.
- U.S. jurisdiction-and-control safeguards — the LLM can’t be controlled by, or compelled to disclose data to, an adversary foreign government.
- Incident reporting, plus an “Unbiased AI Principles” framework carrying potential termination-for-cause liability.
- Mandatory, role-based flow-down clauses to subcontractors — alongside liability caps and trade-secret protections (Holland & Knight, 2026; Crowell & Moring, 2026).
Why it matters beyond the GSA Schedule
When finalized, this clause is expected to apply across GSA’s governmentwide vehicles — the Multiple Award Schedule, GWACs, and OASIS+ (Holland & Knight, 2026). This is AI procurement moving into the language of contract clauses: data ownership, defined roles, flow-downs, and accountability. Even as a draft, it’s a preview of where governmentwide AI contracting is heading.
What to do now
If you develop, integrate, or resell AI: map where LLMs in your solution touch government data, check whether your subcontractors can actually meet the flow-down obligations, and — if the terms would hurt — submit a comment by August 3 at regulations.gov. The firms that engage now shape the rule they’ll live under later. Brick by brick.
FAQ
Does this apply if I just use an AI tool internally?
The clause targets LLMs that process government data under a GSA contract, and it exempts incidental or embedded commercial LLM functionality — but read the definitions carefully, because “government data” is broad (Crowell & Moring, 2026).
Is it final?
No — it’s a proposed clause. Comments close August 3 before GSA moves toward a deviation or formal rulemaking (Wiley, 2026).
Sources
Crowell & Moring LLP. (2026, June 17). GSA proposes revised AI contract clause for LLMs: Key changes federal contractors must understand.
Holland & Knight. (2026, June 29). GSA proposes sweeping AI data safeguarding rules for LLM contractors.
Jenner & Block LLP. (2026). GSA issues a revised proposed clause governing AI data-safeguarding requirements.
Wiley Rein LLP. (2026, June 29). GSA seeks comment on updated AI contract clause.
Need to translate this clause into a compliance checklist for your team? That’s what we do. Explore GovCon iSource.
