GSA Has a Framework for Which FAR Clauses You Can Negotiate. Your Purchasing System Should Too. 

If you’ve ever sat across from a contracting officer and asked “can we adjust this clause,” you already know the honest answer is usually “it depends on which clause.” GSA has written that logic down, in an OEM engagement packet for its OneGov Strategy, the initiative aimed at large software and cloud OEMs like Microsoft, AWS, and Elastic. 

Buried in that packet is a small table that’s more useful to a defense manufacturer than anything else in the document. GSA sorted common contract terms into four buckets: Statutory, Regulation, Policy, and Negotiable. It’s the same discipline compliance officers apply to flowdown clauses every day, except here the government wrote its own answer key down and published it. 

The Four Buckets 

GSA defines the categories this way. Statutory terms come from an act of Congress and are codified in the U.S. Code. They cannot be waived, modified, or negotiated by anyone, on either side of the table. Regulation-based terms implement statutory requirements through the CFR. Waivers exist in theory, but GSA is direct about it: these are generally non-negotiable in practice. Policy terms come out of the FAR Council or an agency’s own FAR supplement, and deviations are permitted but need justification. Negotiable terms are the only category where a contracting officer and a contractor actually sit down and work something out. 

GSA’s own dashboard maps specific clauses to these buckets. Order of precedence and indemnification of the government both land as statutory. Small business subcontracting requirements and IP clauses are regulation. Reporting obligations and most-favored-customer terms are policy. Warranty terms and patent indemnification by the contractor are negotiable. 

Why This Matters If You’re Not Selling to GSA 

You may never touch a Multiple Award Schedule or bid on a OneGov agreement. That’s fine. The framework still applies to you, because the same four categories exist in every prime contract clause you’re flowing down to your subcontractors, and in every clause a prime is flowing down to you. 

The mistake we see most often at the subcontract level isn’t malicious. It’s a purchasing manager treating every clause as if it belongs in the same bucket, either flowing everything down to be safe or assuming everything is up for discussion because the prime seemed flexible on one item. Neither instinct holds up under a CPSR. A clause’s category isn’t a matter of how the conversation feels. It’s determined by the clause’s own prescription, and that prescription doesn’t move because you asked nicely. 

GSA can afford to publish this framework because a $500M-a-year OEM has leverage a Tier III subcontractor doesn’t. You won’t get the same room to negotiate warranty terms that Microsoft gets. But the underlying discipline, knowing which bucket a clause sits in before you walk into the conversation, applies exactly the same way down at your level. The stakes are arguably higher for you. GSA losing a negotiation on warranty language is a commercial disappointment. A subcontractor getting the statutory versus negotiable distinction wrong is a CPSR finding. 

Where GovComply.ai Fits 

This is the same three-state logic GovComply.ai applies to every clause in your prime contracts and flowdowns: mandatory, conditional, or not applicable, each with the regulatory basis documented. The platform doesn’t guess whether a clause is open for discussion. It tells you, before you’re in the room, whether you’re negotiating or complying. 

If your team is currently relying on instinct, or on whatever the last subcontract used, to sort clauses into negotiable and non-negotiable, that’s the exact gap GSA’s own framework just put a spotlight on. The free contract analysis will show you where those calls are being made without documentation behind them. 

GovComply.ai is compliance software built for defense and aerospace manufacturers holding government contracts. 

Source: GSA Office of Information Technology Category, Vendor Management Office, OneGov Strategy: IT Software Initiative — Industry Engagement Resources & Materials, available at itvmo.gsa.gov. The OneGov Strategy was announced in April 2025; this specific engagement packet is undated in the document itself. GSA’s OneGov Strategy targets direct-to-government software and cloud OEMs (Tier 1 threshold: $500M+ in annual federal spend across all 24 CFO Act agencies) and is not a program GovComply or its customers participate in. It’s cited here for its FAR clause negotiability framework, not as a GTM or partnership reference.