FAR Overhaul Adoption Tracker

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.

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).

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 has not 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.

The table below is generated directly from ArcClause's adoption data, as of 2026-08-09 (the data file's own as-of date). It reflects 812 verified adoption records across 40 agencies and 30 FAR parts. A dated cell is an agency class deviation effective for new solicitations on that date; a blank cell means no RFO deviation is recorded for that agency and part, so ArcClause uses legacy FAR. Parts 12, 13, and 19 (the fully encoded commercial path) are shown first.

Source: ArcClause agency-adoptions.json (as-of 2026-08-09), generated by tools/gen-far-overhaul-tracker.mjs. Dates are agency class-deviation effective dates for new solicitations, drawn from agency memos and deviation documents posted to acquisition.gov and agency sites; hover any dated cell for the source note. Several dates were extracted from deviation PDFs, verify against the exact effective language before relying on edge dates. A blank cell means no RFO deviation is recorded for that agency and part as of this stamp, which ArcClause treats as legacy FAR; it is not a statement that the agency will never adopt RFO for that part. This is A-Frame's encoded data, not the government's official position, confirm against the current FAR, agency class deviations, and acquisition.gov before relying on it.

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.