Legacy FAR vs. the FAR Overhaul: What Changes for Clause Selection

Two contracting officers can buy the identical service this quarter and owe a different set of clauses. Not because one of them is wrong — because they're working under two different versions of the Federal Acquisition Regulation at the same time. The Revolutionary FAR Overhaul is rolling out part by part and agency by agency, and until it finishes, the clause matrix is no longer a fixed checklist you can pull from a template. It's a determination — one that depends on who your agency is and when your solicitation goes out.

If you build clause matrices, this is the part of the overhaul that lands on your desk first. Here's what actually changes, and how to keep your selection defensible while both regimes are live.

Why there are two FARs right now

Executive Order 14275, "Restoring Common Sense to Federal Procurement," signed April 15, 2025, directed the FAR Council to strip the FAR back to its statutory roots — removing rules not required by statute or executive order and rewriting what remains in plain language. That effort is the Revolutionary FAR Overhaul, or RFO.

The mechanism matters for clause selection. The FAR Council isn't flipping a switch on a single effective date. It rewrites the FAR one part at a time and publishes model deviation text for each. Agencies then issue class deviations adopting that text, and those deviations stay in effect until the revised FAR is formally codified. GSA's class deviations took effect November 3, 2025; the Department of Defense is moving through the DFARS; civilian agencies are adopting parts on their own schedules well into 2026.

One requirement. Two possible clause matrices.

Agency+ FAR part+ Solicitation date

Has your agency adopted the RFO deviation for this part, effective on or before your solicitation date?

Legacy FAR

No — not adopted, or adopted after you issued

• Full legacy prescriptions apply
• Non-statutory clauses still incorporated
• 52.212-5 with the long checked sub-clause list

FAR Overhaul (RFO)

Yes — deviation in effect for this part

• Non-statutory provisions & clauses removed
• Statutory clauses (52.212-4/-5) rewritten
• Prescriptions reworded & renumbered

Same requirement — the regime is decided by agency + timing, not the work.

What actually changes in the matrix

When a part is rewritten, the model deviation text reflects the removal of non-statutory content and the plain-language rewrite of what's kept. For the provisions and clauses you incorporate, that shows up in four ways:

• Non-statutory provisions and clauses come out. Requirements that weren't grounded in statute or an executive order are the overhaul's main target. Clauses you've incorporated by habit for years may simply no longer be prescribed under the deviated part.
• Statutory clauses stay — but get restructured. The clauses that implement statutes and executive orders don't disappear. The commercial terms family at 52.212-4 and 52.212-5, for example, is required by statute and survives, but it's being rewritten, and the long list of checked sub-clauses inside 52.212-5 is pruned to what statute and EOs still require.
• Prescriptions move and get reworded. The prescription is the rule that tells you why a clause applies and under what conditions. The overhaul rewrites prescriptions in plain language and renumbers them, so the trigger you memorized under the legacy FAR may read differently — or live somewhere else — under the deviation.
• There's a new source of truth to reconcile. For each revised part, acquisition.gov publishes a "Practitioner Album" and a "line-out" version showing exactly which provisions and clauses were struck. It's genuinely useful — and it's one more document you have to check against your template instead of trusting muscle memory.

Timing decides which regime applies

Because adoption is rolling, the date attached to your action is what places you in one regime or the other. The questions that resolve it:

• Has your agency adopted the deviation for this part? If it hasn't, you're still on the legacy FAR for that part — even if a neighboring agency has already moved.
• What's the effective date of that class deviation relative to your solicitation date? A deviation that takes effect after you issue doesn't retroactively change the solicitation you already put on the street.
• Which date controls the clause — solicitation or award? Some requirements resolve as of the solicitation date and some as of the anticipated award date, and the overhaul doesn't erase that distinction.

None of this is exotic — COs have always had to apply the FAR in effect at the right point in time. What's new is that the "FAR in effect" is now a moving, agency-specific target, and getting it wrong doesn't just mean an extra clause. Incorporating a deviated-out clause, or missing one a statute still requires, is exactly the kind of thing that surfaces in a protest or an audit.

Keeping the matrix defensible during the transition

The discipline that holds up is the same one that always has — it just has more inputs now:

• Pin the regime before you build. Confirm, for each relevant part, whether your agency has adopted the RFO deviation and as of what date. Don't assume the answer is the same across parts.
• Work from the current prescription, not the template. For every provision and clause, trace it back to the prescription that's actually in force for your regime — and capture that citation.
• Document the basis for each call. A matrix that records why each clause is in or out — the prescription, the regime, the date basis — is what lets a reviewer (or a protester) follow your reasoning instead of second-guessing it.

Done by hand across both regimes, that's real work: checking adoption status, finding the right prescription under the right version of the part, resolving the threshold by the right date, and writing it all down. It's precisely the kind of structured, rules-driven task worth automating.

That's why we built ArcClause — a free FAR provision and clause matrix builder. You answer a short wizard about the acquisition, and it returns the provisions and clauses your solicitation needs. It's aware of both regimes — legacy FAR and the Revolutionary FAR Overhaul — and resolves which one applies from the agency and the timing you give it. Selection runs on a deterministic rules engine, so the AI never picks a clause; every row comes back with the prescription cited behind it, and you can export a Basis of Selection that shows your reasoning. No login, no credit card. You can read the authoritative source for any of this on the FAR Council's Revolutionary FAR Overhaul site, and ArcClause links the prescription on every clause it returns.

---

The overhaul will eventually settle into a single, simpler FAR — and that's the point of it. But "eventually" is doing a lot of work. For the months it takes every agency to adopt every part, clause selection is a determination, not a lookup, and the teams that treat it that way — pinning the regime, working from the live prescription, and documenting the basis — are the ones whose solicitations hold up.