The Government owes you money. Now they want your data.

The government owes contractors money from this year’s shutdown. Now it wants to own their AI data.

DHS just came off the longest shutdown a single agency has faced: more than ten weeks, from mid-February to late April, on top of the 43-day shutdown that closed out 2025. Jim Carroll, CEO of the Professional Services Council, put it plainly: for every day of a shutdown, it takes three to five business days for the government to get back to normal operations. By his math, the ripple effects from this one won't fully settle until the end of the year.

Contractors felt that on the ground. Companies kept paying employees with no reimbursement coming in. Cash reserves got drained, credit lines got tapped, and cybersecurity, disaster response, and airport security contracts ran at reduced capacity because the money and the people weren't there. The government still owes back payments, interest, and penalties on a lot of that… and "owed" doesn't mean "paid."

While contractors are still waiting on that money, GSA has spent the year rewriting the rules on AI, and just revised them again. The GSAR 552.239-7001 clause, first published as a draft in March, was significantly revised in a June rewrite, narrowed to focus specifically on large language models, but expanded who it applies to: a new four-tier structure now pushes obligations down through developers, operators, integrators, and service providers, not just the prime holding the contract. Subcontractors are on the hook too. The clause requires "eyes off" technical controls on government data, tiered notice timelines, 30 days for material changes, seven days if performance or safety degrades, immediate notice for emergencies, and documented risk assessments anywhere the AI system touches foreign components.

Public comments on this latest version closed August 3. There's no final adoption date. GSA hasn't said whether this becomes a formal rule or a deviation, only that it's still gathering feedback. Which means the rules contractors will eventually be held to are still being written, and six months in, they already reach further than they did at the start.

This is the pattern I keep seeing in this industry: the disruption people brace for is rarely the only one that hits. Right now it's a shutdown recovery you're still owed money for, stacked on a compliance framework that keeps shifting under contractors who are expected to already understand how these AI systems work well enough to document, monitor, and disclose them. Most program managers and contract leads I talk to didn't have that training built into their career path.

That's not a knock on anyone. Most people in this ecosystem have been too busy delivering on contracts and extinguishing the daily fires in GovCon, that after a long day dedicated to the government and taking care of our families and other responsibilities, all we want to do is remove our shoes, and pass out in front of the TV, and not talk to anyone (although that might just be me). We feel we have no spare time, and no mental capability to do anything else, especially learning about AI.

But "too busy to learn it yet" and "can't learn it" are two very different problems, and only one of them is actually a problem.

The contractors who come out ahead here won't be the ones who panic about AI or the ones who wait until a contracting officer asks a question they can't answer. They'll be the ones who already understand what these systems do, how they touch the data the government is moving to claim, and how to talk about it credibly, before it's a compliance emergency instead of a knowledge gap.

If you're trying to make sense of where this clause is headed, or you just want to get ahead of it before the next revision lands, that's exactly the kind of thing I help contractors work through so don’t hesitate to reach out. We are all in this together.