FAR Overhaul 2026: What Federal Contractors Must Check
The FAR overhaul is changing how federal acquisition rules are written and, through agency class deviations, how some agencies already apply them.
The biggest contractor risk is not simply missing a new rule. It is confusing a model deviation, an agency-adopted deviation, a proposed rule, and the codified Federal Acquisition Regulation as if they had the same legal status.
They do not.
As of August 30, 2026, the codified FAR on Acquisition.gov remains FAC 2026-01, effective March 13, 2026. At the same time, the Revolutionary FAR Overhaul is active through agency deviations and formal Phase 2 rulemaking. See the current Federal Acquisition Regulation.
For a live pursuit, verify the rule that applies to the buying agency and solicitation—not merely the newest RFO text you find online.
What Is the FAR Overhaul?
The Revolutionary FAR Overhaul (RFO) is a governmentwide effort to streamline the Federal Acquisition Regulation.
Executive Order 14275, signed April 15, 2025, directed the administration to reduce the FAR to provisions required by statute or otherwise necessary for sound procurement. It also directed interim and deviation guidance while formal FAR revisions were developed. See Executive Order 14275.
Acquisition.gov says the initiative is led by the Office of Federal Procurement Policy and the FAR Council. Its stated approach is to rewrite retained requirements in plain language, remove unnecessary non-statutory mandates, and move useful but non-mandatory practices into separate guidance. See the RFO Frequently Asked Questions.
That creates two related changes:
- Regulatory text is being streamlined.
- Some former FAR detail is moving into non-regulatory guidance.
For contractors, this can change solicitation structure, terminology, agency discretion, and the places where a requirement must be verified.
For a broader explanation of how the FAR works, use the Federal Acquisition Regulation hub.
FAR Overhaul 2026: The Current Status
The FAR overhaul 2026 is now operating in two important layers.
Phase 1: Model Deviations and Agency Adoption
In Phase 1, the FAR Council issued model deviation text for FAR parts. Agencies use that model language to issue their own class deviations.
The distinction is critical.
Acquisition.gov states that model deviation text does not apply to an agency merely because the FAR Council published it. The agency must issue its own class deviation. Once adopted, the agency can use that streamlined text before formal FAR rulemaking is complete. See the RFO Frequently Asked Questions.
Agencies are expected to adopt the RFO model text, but adoption occurs through agency action. That means solicitation language can temporarily vary between agencies during the transition.
Phase 2: Formal FAR Rulemaking
Formal rulemaking is also underway.
Acquisition.gov’s current RFO tracker organizes Phase 2 into 12 FAR cases. As of August 30, 2026, proposed rules have been published for the first four of those 12 cases. The remaining eight are still shown as not yet published. See You Said, We Did.
The four published cases cover:
| FAR Case | Parts in current proposed-rule package |
|---|---|
| 2026-001 | 1, 2, 4, 33, 39, 40, 53 |
| 2026-002 | 6, 7, 10, 18, 26, 37, 41 |
| 2026-005 | 5, 24, 29 |
| 2026-007 | 3, 49 |
The first proposed rules were published June 23, 2026. These are proposed rules, not a signal that every provision has already replaced the codified FAR.
That difference should drive every contractor review.
Use This Five-Status FAR Overhaul Check
Before deciding that a FAR change affects your pursuit, classify what you found.
| Status | What it means | Does it automatically control your bid? | Contractor action |
|---|---|---|---|
| Codified FAR | Current FAR published in the official regulation | Baseline, subject to applicable deviations and supplements | Read current codified text |
| RFO model deviation | FAR Council’s streamlined model text | No | Check whether the buying agency adopted it |
| Agency class deviation | Agency has adopted deviation text for its acquisitions | Potentially yes for covered acquisitions | Read the agency deviation and effective terms |
| Proposed rule | Formal rulemaking text published for comment | Not yet final merely because proposed | Monitor; do not treat proposal as current rule |
| Non-regulatory guidance | FAR Companion, buying guide, Practitioner Album, training | Not mandatory by itself | Use for context and buying practice, not as a contract clause |
This status check is the core of the page.
Do not ask only, “What did the FAR overhaul change?” Ask, “What is the status of this change for this agency and this solicitation?”
Model Text and Agency Deviations Are Not the Same Thing
This is the most important RFO distinction for federal sellers.
Acquisition.gov explains that model deviation language is a FAR Council template. An agency adopts that language through a class deviation under its own procedures.
The official FAR Part Deviation Guide tracks individual FAR parts and links agency deviations.
For example, the guide currently shows agency deviations for Part 1 across DoD, GSA, DHS, VA, NASA, Commerce, Treasury, and many other organizations. It also shows agency adoption under other parts.
This matters because two solicitations issued by different agencies may not sit under the same transition state.
When reviewing a live opportunity:
- identify the buying agency;
- identify the relevant FAR part;
- open the RFO deviation guide;
- locate that agency’s class deviation;
- check its effective date and scope;
- compare it with the solicitation.
Do not assume that a model deviation alone changed your bid.
A Proposed Rule Is Not the Same as an Effective Rule
The Phase 2 proposed rules deserve close attention, but contractors should label them correctly.
The FAR Council received almost 1,600 comments during the earlier RFO process, with most coming from industry. The government says that feedback changed some positions between model deviations and the proposed rules. See You Said, We Did.
That is proof that the text can move.
For example, the government’s current tracker identifies several proposed changes:
| Area | Current Phase 2 proposal | Contractor implication |
|---|---|---|
| Part 1 | Proposed text removed automatic expiration of FAR requirements and instead relies on formal rulemaking for removal | Do not assume non-statutory rules automatically vanish after four years |
| Part 4 | Proposal would remove more than half the information required for SAM registration | Watch for actual SAM implementation before changing registration processes |
| Parts 7 & 10 | Proposed rule consolidates market research into acquisition planning | Early agency/industry engagement may be organized differently |
| Part 33 | Proposal expands disclosure in some agency-level protest situations | Could improve post-award information, but do not assume it is available today |
| Part 39 | Proposed text expressly recognizes new or emerging technologies | Relevant to technology acquisition strategy, not an automatic new contractor obligation |
These are examples of proposed Phase 2 changes. They should not be written into a compliance checklist as though they were final.
Some RFO Text Is Already Being Used Through Deviations
The opposite mistake is also risky.
A contractor may look at the codified FAR, see that the formal rule has not yet changed, and conclude that the RFO has no present effect.
That can also be wrong.
Agencies have issued class deviations adopting RFO text. Acquisition.gov’s deviation guide lists those agency actions part by part.
The official RFO FAQ describes the period between agency adoption and formal rulemaking as a testing period. Agencies can begin using adopted model text through their deviations while the codified FAR remains unchanged.
So the current operating model can look like this:
Codified FAR says A → FAR Council model says B → Agency deviation adopts B → Solicitation uses B
For that acquisition, reading only the codified FAR may leave the contractor with an incomplete picture.
What Changed Most Recently?
The current official Acquisition.gov news feed shows the latest broad RFO update on July 1, 2026.
On that date, the FAR Council updated RFO Parts 16 and 52 to implement Executive Order 14402, which addresses efficiency, accountability, and performance in federal contracting. See the July 1, 2026 Parts 16 and 52 update.
The official deviation guide now labels:
- Part 16 — Types of Contracts: updated July 1, 2026
- Part 52 — Solicitation Provisions and Contract Clauses: updated July 1, 2026
The guide also lists agency deviations beneath Part 16.
For contractors, that creates an immediate verification step.
If a solicitation relies heavily on contract type, pricing structure, or changed Part 52 language, check the buying agency’s applicable deviation before relying on an older internal FAR summary.
What Federal Acquisition Reform Means for Contractors
The wider federal acquisition reform effort is designed to give contracting officials more discretion and reduce mandatory process.
Acquisition.gov’s current FAQ says the RFO itself is not intended to change statutory requirements or create new regulatory burdens. It also warns that variation in solicitation language may occur while agencies adopt deviations over time.
That combination changes the contractor’s research job.
Expect Less Value From Old FAR Checklists
A checklist built around old section numbers may not match the current agency deviation structure.
Keep the underlying requirement, but verify the current source.
Expect Agency Context to Matter More
A generic FAR citation may no longer be enough.
The buying agency, supplement, class deviation, and solicitation can determine what text actually applies.
Separate Compliance From Guidance
The FAR Companion and Practitioner Albums may help explain acquisition approaches.
Acquisition.gov explicitly describes those buying guides as non-regulatory and non-mandatory.
They can explain buyer behavior.
They should not be treated as contract clauses.
Watch the Solicitation More Closely
During a transition, solicitation language is valuable evidence.
If a clause, instruction, or provision differs from your standard template, trace the source rather than assuming it is an error.
The Contractor RFO Verification Workflow
Use this workflow when a FAR issue could change the bid.
1. Start With the Live Acquisition
Capture:
- agency;
- solicitation number;
- FAR citation;
- clause or provision;
- clause date;
- amendment number.
2. Check the Codified FAR
Use the current FAR on Acquisition.gov.
As of this review, the published baseline remains FAC 2026-01, effective March 13, 2026.
3. Check the RFO Part
Use the FAR Part Deviation Guide.
Record the model text issuance or update date.
4. Check Agency Adoption
Find the buying agency under that part.
Open the actual deviation.
Do not infer adoption because another agency has already adopted it.
5. Check Phase 2 Status
If the part appears in a proposed FAR case, mark it proposed.
Do not silently replace the agency’s current rule with the proposed wording.
6. Return to the Solicitation
Ask whether the actual bid:
- uses the deviation;
- incorporates changed clauses;
- adds an agency-specific instruction;
- has an amendment that changes the baseline; or
- still follows older codified language.
7. Record the Contractor Impact
Write a short decision note:
| Field | Example |
|---|---|
| FAR part | Part 16 |
| Current status | Agency class deviation |
| Agency | Example agency |
| Effective date | Date from deviation |
| Solicitation impact | Contract-type language changed |
| Contractor implication | Recheck pricing/risk assumption |
| Owner | Pricing / Contracts |
| Status | Verified / unresolved |
That is much more useful than saving a link to the RFO page.
Four FAR Overhaul Mistakes to Avoid
Treating Every RFO Page as Effective Law
Model deviation text alone does not prove applicability.
Check the agency.
Treating Every Proposed Rule as Final
Phase 2 rulemaking is active.
A proposed rule shows direction, not necessarily today’s controlling requirement.
Reading Only the Codified FAR
Agency deviations can already govern covered acquisitions.
Check the transition layer.
Creating an “RFO Change Log” With No Contractor Action
A list of deleted paragraphs does not tell BD, capture, pricing, or proposal teams what to do.
For every material change, record:
status → agency → acquisition → impact → action
What Contractors Should Do Now
The FAR overhaul does not require every contractor to rewrite every compliance manual today.
It does require stronger source discipline.
For each live pursuit, identify the relevant FAR part. Then compare the codified FAR, RFO model language, agency deviation, Phase 2 rulemaking status, and the solicitation itself.
If the issue changes a must-meet proposal condition, move it into the RFP requirements workflow.
For the broad FAR framework, use the Federal Acquisition Regulation hub.
The operating rule is simple:
Do not ask whether the FAR changed. Ask which version applies to this agency, this acquisition, and this decision.
Sources & Official References
- Acquisition.gov — Revolutionary FAR Overhaul
- Acquisition.gov — RFO Frequently Asked Questions
- Acquisition.gov — FAR Parts and Agency Deviations
- Acquisition.gov — You Said, We Did
- Acquisition.gov — Current Federal Acquisition Regulation
- Acquisition.gov — FAR Rules Requesting Comments
- Acquisition.gov — July 1, 2026 Parts 16 and 52 Update
- White House — Executive Order 14275