Reference  ·  Regulatory Status Tracker

FAR Overhaul Adoption Tracker

Where the Revolutionary FAR Overhaul (RFO) stands — official rulemaking status by FAR part (final / proposed / legacy) and verified agency adoption, in one scannable view. Built by former Contracting Officers; grounded in official sources.

As of June 25, 2026. Regulatory status changes frequently — always verify current status at acquisition.gov/far-overhaul and the Federal Register before relying on it.

The RFO, directed by Executive Order 14275 ("Restoring Common Sense to Federal Procurement"), is rolling out on two tracks. First, agencies issued class deviations on the commercial-buying path (FAR Parts 12, 13, 19) ahead of formal rulemaking. Second, the FAR Council has now opened formal notice-and-comment rulemaking — the first batch of proposed rules published June 23, 2026, with comments due July 23, 2026.

Read this in two layers. The first table is the government's official rulemaking status (what the Federal Register and acquisition.gov say). The second is ArcClause coverage — what A-Frame's clause engine has independently encoded and verified. The two are not the same thing: ArcClause coverage is our data, not the regulation's status, and is necessarily narrower than the full overhaul.

1 · Official rulemaking status, by FAR part

Source: Federal Register (June 23, 2026) and acquisition.gov/far-overhaul. The FAR Council has stated it intends to issue a total of 12 proposed rules that will collectively revise the entire FAR; the batch below is the first four (covering ~20 parts). Parts not listed below are not yet in a published proposed rule and remain legacy FAR unless an agency has issued a class deviation (see Layer 2).

Final rule in effect Proposed rule — open for comment Legacy FAR (no RFO rule yet) / deviation-led Not confirmed here
FAR part(s) Official status (as of Jun 25, 2026) Comment deadline Source
1, 2, 4, 33, 39, 40, 53 Proposed rule (open)
FAR Case 2026-001
July 23, 2026 Fed. Reg. 2026-12559
6, 7, 10, 18, 26, 37, 41 Proposed rule (open)
FAR Case 2026-002
July 23, 2026 Fed. Reg. 2026-12560
5, 24, 29 Proposed rule (open)
FAR Case 2026-005
July 23, 2026 Fed. Reg. 2026-12561
3, 49 Proposed rule (open)
FAR Case 2026-007
July 23, 2026 Fed. Reg. 2026-12562
12, 13, 19 Deviation-led
Commercial path — agency class deviations ahead of rulemaking
acquisition.gov/far-overhaul · see Layer 2
52 Conforming changes
Solicitation provisions & contract clauses, amended across the cases above
July 23, 2026 acquisition.gov/far-overhaul
All other parts Not yet in a published proposed rule
More rules forthcoming — Council plans 12 total
acquisition.gov/far-overhaul

FAR Case 2026-005 covers Parts 5, 24, 29 (and conforming Part 52 changes). We confirmed the four published rules and the July 23, 2026 deadline against the Federal Register and an industry summary; we did not independently re-read the full text of every rule, so treat the per-part groupings as the published case scope, not a clause-level mapping. Final rules had not been issued for any RFO part as of this stamp. Verify the live list at acquisition.gov/far-overhaul.

2 · ArcClause coverage & verified agency adoption

This is A-Frame's own data, not the government's status. ArcClause is a deterministic clause-selection engine that resolves a "regime" (legacy vs. RFO deviation) per FAR part, per agency, per solicitation date.

ArcClause has encoded and CO-verified RFO deviation clause text for the commercial path — FAR Parts 12, 13, and 19 (plus one Part 22 clause). For every other part it carries the legacy FAR text and, where an agency is on RFO for a part it hasn't yet encoded, the engine resolves to legacy and raises a review flag rather than asserting a clause is correct. That is a deliberate integrity choice, not full RFO coverage.

ArcClause tracks adoption only for agencies whose posture it has researched ("verified agencies"). An agency not on this list triggers an unverified-posture banner instead of a possibly-wrong legacy assumption. The table below reflects exactly what is encoded in ArcClause's adoption data as of June 14, 2026 (the data file's own as-of date) for the three commercial-path parts.

RFO deviation adopted (date = effective for new solicitations) No RFO record encoded → ArcClause uses legacy
Verified agency Part 12
(Commercial)
Part 13
(Simplified)
Part 19
(Small Bus.)
DoD2026-02-012026-02-012026-02-01
GSA2025-11-032025-11-032025-11-03
HHSlegacy*2025-11-212025-11-21
NASA2025-09-222025-12-192026-02-20
NSF2025-09-182025-12-022025-12-02
OPM2026-04-132026-04-202026-04-29
Treasury2025-09-232025-09-232025-11-25
USDA2025-08-212025-10-022025-10-02
VA2025-10-142025-10-082025-11-19

Source: ArcClause agency-adoptions.json (as-of 2026-06-14). Dates are the agency class-deviation effective dates for new solicitations, drawn from agency memos posted to acquisition.gov; several were extracted from the deviation PDFs and the data notes flag them to verify against the exact effective language before relying on edge dates. The DoD dates (RFO Phase 1, eff. 2026-02-01) are corroborated across industry summaries; the data notes that the primary OSD memo was not machine-fetchable when recorded, so re-confirm at the source.
*HHS Part 12 shows legacy because the HHS class deviation on file did not cover Part 12; an HHSAR deviation implies alignment but ArcClause has not recorded a Part-12 RFO date for HHS.
Agencies not listed (e.g., DHS, DOI, DOJ, State, DOT, Education, EPA, HUD, Energy, Labor) have deviations whose effective dates ArcClause could not reliably confirm; the engine shows an unverified-posture banner for them rather than guessing. Absence here is not evidence an agency has not adopted RFO.

How ArcClause uses this. For a given solicitation, the engine takes your agency, FAR part, and solicitation date, finds the latest adoption record effective on or before that date, and selects the matching clause regime — defaulting to legacy with a review flag when it can't verify RFO. Same inputs always yield the same output; AI never picks clauses.

What this means for your next solicitation

If you contract for one of the verified agencies above and your solicitation is dated after that agency's adoption date for Parts 12, 13, or 19, you are likely on the RFO deviation regime for that part — different provisions and clauses than legacy FAR. For the parts now in proposed rulemaking (1, 2, 3, 4, 5, 6, 7, 10, 18, 24, 26, 29, 33, 37, 39, 40, 41, 49, 53), nothing is final yet; legacy FAR still governs unless your agency has a separate deviation. When in doubt, the cognizant Contracting Officer determines what applies.

Companion reading: our blog covers what the FAR Overhaul under EO 14275 means for COs, and we are publishing a piece on the July 23, 2026 comment deadline — find it on the A-Frame blog.

Build your clause matrix with the right regime

ArcClause picks the legacy or RFO-deviation provisions and clauses for your solicitation — by agency, part, and date — with the prescription behind every row. Free, no login.

Open ArcClause →

DISCLAIMER: This page is a decision-support reference for informational purposes only. It is not legal advice and creates no attorney-client relationship. Regulatory status changes frequently; "official status" reflects published Federal Register documents and acquisition.gov as of June 25, 2026, and "ArcClause coverage" reflects A-Frame's own encoded data (as-of June 14, 2026) — the latter is not the government's position. The determination of which provisions and clauses apply to any given acquisition, and which regime governs, remains the responsibility of the cognizant Contracting Officer. Verify everything against the current FAR, Federal Acquisition Circulars, class deviations, and applicable agency supplements before use in any official capacity. A-Frame Solutions LLC assumes no liability for decisions made based on this reference.