The Summer 2026 GovCon Shakeup: Fixed-Price by Default, FAR in Formal Rulemaking, and What Proposal Teams Need to Change Now

Something rare is happening in federal contracting this summer: four separate rule changes are landing inside the same ninety-day window, and each one moves the ground under a different part of your proposal shop. The Fixed-Price Executive Order signed April 30 changes how you price. The June 23 formal FAR rulemaking changes how you cite. The 2026 NDAA thresholds change what you have to certify. The Uniform Grants Regulation, comment window closing July 13, changes what your grants-side customers can even structure.

Treating these as four separate compliance updates, sequenced one at a time, is a mistake. They are one problem: the government is shifting pricing risk, compliance burden, and administrative discretion in ways that reward disciplined proposal workflows and punish ad hoc ones. If your capture and pricing teams are still operating under 2025 assumptions, update them before your next bid.

This piece walks through what actually changed, what it means for the numbers on your bid, and the concrete playbook for adapting your proposal system before your next Section L drop. Every threshold and date below is cited to the source document.

The four rule changes on one timeline

Before we get into any single change, look at them together. The pattern matters.

That is nine load-bearing dates in six months ^[1][2][3][4]. Every one of them touches something your proposal or pricing team relies on. Now let us dig into what each cluster of changes does to your bid workflow.

Fixed-Price by Default: What Executive Order 14402 Actually Requires

On April 30, 2026, the President signed Executive Order 14402, *Promoting Efficiency, Accountability, and Performance in Federal Contracting* ^[1], and its practical effect on pricing strategy is larger than any single line item in the text.

The order makes fixed-price contracting the default for executive branch procurement. Any non-fixed-price contract, including cost-reimbursement, time-and-materials, and labor-hour, "must be justified in writing by the contracting officer to the agency head," and the agency head must approve it in writing when its value, or the non-fixed-price portion of a hybrid, exceeds ^[1]:

• $100 million for Department of War contracts
• $35 million for NASA contracts
• $25 million for DHS contracts
• $10 million for all other agencies

Emergency, disaster, and contingency contracts, and research and development or pre-production development for major systems, are exempt from the approval thresholds ^[1]. The order also carries a retrospective element that many contractors missed. Within 90 days of signing (around July 29, 2026), each agency head must review its ten largest non-fixed-price contracts by dollar value and, to the maximum extent practicable, seek to modify, restructure, or renegotiate them to use fixed prices and performance-based incentives ^[1]. That is not a proposed rule. It is an existing-contract review that can produce modification requests on current awards.

For proposal teams, the immediate consequences are three. First, expect solicitations you would have bid as cost-plus-fixed-fee or T&M to arrive as fixed-price with the same technical scope but pricing risk shifted to your firm. Second, expect contract modifications on existing awards that restructure risk in ways your original bid did not assume. Third, because the contracting officer must justify any non-fixed-price choice in writing, a proposal that documents why fixed-price does not fit gives them the record they need.

That third point is the opening most contractors are missing.

The paradox: FFP-default makes contract-type evidence worth raising early

If you are bidding into a category where firm-fixed-price genuinely does not fit (high-uncertainty R&D, cost-share cooperatives, indefinite-quantity level-of-effort work), the contracting officer needs to build a written justification to their agency head. Your proposal is either the raw material that justification is built from, or it is not.

Raise it before proposals are due, not inside an unsolicited proposal section. Proposals are evaluated against the factors the solicitation states, so a contract-type argument the RFP did not ask for can simply be set aside. Use the channels the solicitation and the agency offer before the due date, such as the questions period, a draft RFP comment window, or industry engagement, to document scope volatility, requirement maturity, historical cost variance on similar work, and the specific technical risks that make fixed pricing a poor fit. That gives the contracting officer evidence while the contract type can still change. In the proposal itself, answer what Section L asks for, and address pricing risk only where the instructions invite it.

If your go/no-go process does not capture contract-type risk signals, such as scope maturity, historical cost variance, and technical risk, you will miss this opening.

The Pricing Math Actually Changes

Let us get concrete with an illustrative example; every rate below is an assumption, not a benchmark. Take a $28 million, five-year cybersecurity engineering task order that would previously have been bid as CPFF with award fee and now arrives as fixed-price with performance-based incentives.

Here is what happens to your pricing volume.

Under the old CPFF model:

• Direct labor: $14.2M
• Fringe: 32% = $4.5M
• Overhead: 42% on direct labor + fringe = $7.9M
• G&A: 8% on total costs = $2.1M
• Subtotal cost: $28.7M
• Fixed fee: 8% of costs = $2.3M
• Bid price: $31.0M
• Government absorbs cost overruns above bid; contractor keeps fee if performance milestones hit

Under the FFP model with the same scope:

• Same estimated cost baseline: $28.7M
• Fixed profit: 10% of costs = $2.9M (higher because there is no reimbursement floor)
• Scope contingency reserve: 6% of costs = $1.7M (covers estimating uncertainty)
• Cost escalation reserve: 3% of costs = $0.9M (labor market movement over 5 years)
• Change management reserve: 2% of costs = $0.6M (unforeseen requirement drift)
• Bid price: $34.8M

In this example, the price rises about 12% for the same scope, driven entirely by risk premiums the contractor now absorbs. That increase is only defensible if your BOE narrative ties each reserve to a documented risk factor. If your pricing team converts to fixed-price with only a profit uplift and no explicit risk reserves, it is either underbidding and taking on unmodeled loss exposure, or bidding a price the evaluator will find hard to justify.

Handle it with three practices: (1) build risk reserve pools that are named, documented, and mapped to specific technical or contractual risks, (2) write BOE narratives that walk the evaluator through each reserve rather than burying them in undifferentiated indirect rates, and (3) treat the reserve pool as a competitive dimension, not just a cost input.

The FAR Overhaul in Formal Rulemaking: What June 23 Changed

If you read my FAR Overhaul Compliance Gap piece from May, the story then was keeping proposal templates and compliance matrices in step with FAR Overhaul deviations that each agency adopts on its own schedule. June 23 was the next escalation. That day the Federal Register carried the FAR Council's first four FAR Overhaul proposed rules, which moved the rewrite into formal notice-and-comment rulemaking.

Comments on that batch were due July 23, 2026. OMB called it the first of three releases of proposed rules and said two more packages would follow.

Three practical consequences for proposal shops:

First, not every award is publicly announced. FAR 5.303 requires contracting officers to make same-day announcement information available for awards over $5.5 million, unless agency regulations set another amount ^[5]. It sets no such requirement for smaller awards, so they may not appear in announcements, and firms doing pipeline analysis off award announcements should lean harder on FPDS and USASpending data.

Second, contracting-officer discretion goes up. The RFO FAQ says the reduction of regulatory mandates "will, for the first time, give contracting officers actual power to determine when many Government-wide policies and practices are suitable" ^[6]. Expect more variation in how evaluation criteria and clauses are tailored. Templated proposals lose their edge; proposals that make their case for the specific requirement win more often.

Third, the sunset mechanism is real. OMB says the proposed rules include a new regulatory sunset process: a comprehensive review of rules, with public input, at least every four years. Together with agency deviations and the remaining rulemaking, that keeps the clause set moving. Treat your clause library as a live artifact with a named owner and a regular review, not an annual refresh.

Your compliance matrix from 2024 is not just stale, it is a submission risk, and formal rulemaking keeps the clause set moving. If you have not built a machine-readable clause mapping file yet, do it this week.

The FY 2026 NDAA: Higher Cost Data and CAS Thresholds

Section 1804 of the FY 2026 NDAA raised the threshold for certified cost or pricing data (the TINA threshold) "from $2.5 million to $10 million for defense contracts entered after June 30, 2026" ^[3]. Section 1806 raised the full CAS coverage threshold from $50 million to $100 million and the CAS applicability threshold for a contract from $2.5 million to $35 million, with CAS regulations to be implemented within 180 days ^[3]. Until the FAR and DFARS text catch up, check each solicitation and ask the contracting officer which thresholds they are applying; FAR 15.403-4 on acquisition.gov still shows $2.5 million.

What this means for pricing volume assembly:

For defense contracts entered after June 30, 2026 and valued below $10 million, the statute no longer requires certified cost or pricing data, once the contracting officer confirms that is the threshold being applied. That does not mean you skip pricing detail: the contracting officer will still expect a defensible cost buildup. Build pricing detail to the level the contracting officer needs without triggering the certification requirement.

What this means for TINA-triggering bids:

Above $10 million, and wherever the contracting officer is still applying the earlier threshold, TINA applies with full force. The defensive discipline (documented data currency, dated pricing records, complete sweep narratives) matters as much as it ever did. With fewer bids in the certified-data category, proposal teams can concentrate cost-volume rigor where it actually attaches.

The Grants Side: Uniform Grants Regulation

If your firm or your customers touch federal grants (universities, nonprofits, state and local passthroughs, prime contractors with grants exposure), OMB's proposed rule published May 29, 2026 is the counterpart to the procurement-side changes. Comments closed July 13, 2026, and OMB proposes a final rule effective by October 1, 2026 ^[4].

Key items:

• OMB would issue 2 CFR as the "Uniform Grants Regulation," an OMB regulation "with one government-wide effective date," rather than guidance adopted agency by agency ^[4].
• Senior appointees would review discretionary awards before issuance, checking that selected proposals are consistent with law, agency priorities, and the national interest ^[4]. Plan for added review time.
• OMB proposes to clarify agencies' ability to terminate discretionary awards for discretionary reasons, consistent with law ^[4].
• Fixed-amount awards and subawards would be eliminated unless authorized by statute ^[4], removing an award type the Uniform Guidance introduced in 2014. Note the contrast: procurement is moving toward fixed pricing, grants away from it.

For proposal shops with grants-facing customers, the practical impact is that grant-application workflows need review-time buffers, termination-risk narratives, and cost-allowability screens at intake.

What Actually Has to Change in Your Proposal Shop

Enough regulatory background. Here is the concrete adaptation list for a modern proposal operation working through the summer of 2026.

1. Contract-type risk analysis becomes a go/no-go input

Before you commit to bidding, your go/no-go framework should classify the solicitation on a two-axis grid:

• Solicitation contract type (FFP, CPFF, T&M, hybrid, IDIQ)
• Scope maturity (well-defined vs. exploratory)

The high-risk quadrant is FFP + exploratory scope. Bidding this quadrant without explicit risk premiums and BOE narratives is how contractors accumulate loss-making awards. If your automation platform does not surface this classification at intake, add it manually.

2. Review compliance matrices on a schedule, not once a year

FAR Overhaul deviations that each agency adopts on its own schedule, the formal rulemaking that began June 23, and the sunset mechanism together produce a rolling clause turnover cycle. Review your clause library on a set schedule and whenever a new deviation or proposed rule lands. Assign an owner. Version-control the mapping file. Test each new template pack against a known reference proposal before it goes live in production.

3. Risk reserves become an explicit BOE component

Under FFP-default, your reserves are the difference between a survivable bid and an underwater one. Break them out:

• Scope contingency reserve (estimating uncertainty)
• Cost escalation reserve (labor, materials, subs)
• Change management reserve (unforeseen requirement drift)
• Technical risk reserve (specific known unknowns)

Each reserve gets a documented rationale in the BOE. Evaluators can accept reserve pools when they understand what they cover. They cannot accept undifferentiated indirect rate padding.

4. Contract-type justification narrative gets built proactively

For any solicitation where FFP is a poor fit, your proposal should include a contract-type recommendation section that gives the contracting officer the raw material to justify a non-FFP structure to their agency head. Document scope volatility, requirement maturity, historical cost variance, and specific technical risks. This is a proposal deliverable now, not a post-award conversation.

5. Pricing pipeline widens below $10M and tightens above it

Below the new TINA threshold on defense work, once the contracting officer confirms it applies: build pricing detail sufficient for the CO's negotiation needs, without triggering certified data submission. Above $10M: run the full TINA discipline: data currency, sweeps, defensive-clause documentation.

6. Grants-adjacent workflows add review lead time

If any of your revenue touches federal grants, rebuild your grant-application timelines to include a review buffer, a termination-risk narrative, and cost-allowability screening. If the rule is finalized on OMB's proposed schedule, it takes effect October 1.

How Projectory Fits This Playbook

I run proposal strategy for a living. I would not spend the time to write this piece if I did not think our platform was well-positioned for this environment. Here is where Projectory actually helps:

Requirement extraction. Projectory's AI extracts the requirements from Section L, Section M, and the SOW into a structured list, so pricing and capture can read the scope and contract-type language before they commit resources.

Compliance matrix generation. The compliance matrix is built from those extracted requirements, so each clause and instruction in the solicitation, including amendments, has a row and an owner.

Go/no-go and P-Win scoring. The P-Win Predictor scores an opportunity on a weighted scorecard, and go/no-go workflows record the decision with stakeholder sign-off and an audit trail, which is where an FFP-versus-cost-type judgment belongs.

Content reuse. Approved past content, including pricing narrative and risk language your team has already defended, is searchable for the next bid instead of rewritten from scratch.

Projectory does not replace pricing judgment, compliance review, or capture strategy. It takes on the mechanical work, requirement extraction and matrix generation, so your senior proposal talent spends its time on the parts that decide the award: contract-type positioning, BOE narrative, risk-reserve defense, and evaluator-facing prose.

A 30-Day Playbook for the Next Bid Cycle

If you do nothing else after reading this, do this in the next 30 days.

Week 1: Reclassify your pipeline. Take every open opportunity in your capture pipeline. Reclassify each one on the two-axis grid: contract-type × scope maturity. Flag the FFP + high-uncertainty quadrant for pricing risk review. Bid/no-bid conversations on those get an extra look before commitment.

Week 2: Refresh the clause mapping. Pull the June 23 Federal Register batch. Cross-reference every affected clause against your active template library. Update the mapping file. If you do not have a mapping file, this is the week to build one.

Week 3: Rebuild pricing templates for FFP conversions. Take three of your most common CPFF or T&M pricing volume structures and rebuild them as FFP versions with explicit named reserve pools. Run them past a pricing peer. Compare the delta on a real historical bid where the outcome is known.

Week 4: Prepare the contract-type justification template. Build a reusable contract-type recommendation template your capture team can populate for solicitations where FFP is a poor fit. Include prompts for scope volatility, requirement maturity, historical cost variance, and technical risk. Deploy it into your next capture kickoff.

The rules are not going to slow down. More FAR rulemaking is on the way; a second set of proposed rules followed on September 18, 2026 ^[7]. OMB proposes an October 1 effective date for the Uniform Grants Regulation. The fixed-price contract reviews can produce modifications on current awards. Each of these can change a Section L, and each will land on a proposal team already loaded with active bids.

The teams that adapt their workflows now (clause libraries, requirement extraction, BOE structure, contract-type classification) will bid faster and price more defensibly than the ones still hand-checking the Federal Register in October.

Start with the pipeline reclassification this afternoon. It will tell you how much of your open pipeline now sits in the risky quadrant, and that number will decide how urgent the rest of this playbook is for your shop.

References

• [1]Executive Order 14402, Promoting Efficiency, Accountability, and Performance in Federal Contracting, 91 FR 24325 (May 5, 2026). https://www.federalregister.gov/documents/full_text/text/2026/05/05/2026-08900.txt
• [2]Federal Register, Revolutionary FAR Overhaul Parts 6, 7, 10, 18, 26, 37, and 41, proposed rule, 91 FR 37636 (June 23, 2026). https://www.federalregister.gov/documents/full_text/text/2026/06/23/2026-12560.txt
• [3]Crowell & Moring, The FY 2026 National Defense Authorization Act (December 23, 2025). https://www.crowell.com/en/insights/client-alerts/the-fy-2026-national-defense-authorization-act
• [4]Federal Register, OMB, Regulation for Federal Financial Assistance, proposed rule (May 29, 2026). https://www.federalregister.gov/documents/full_text/text/2026/05/29/2026-10817.txt
• [5]FAR 5.303 Announcement of contract awards. https://www.acquisition.gov/far/5.303
• [6]Acquisition.gov, FAR Overhaul FAQs. https://www.acquisition.gov/far-overhaul/faqs
• [7]Federal Register, Revolutionary FAR Overhaul Parts 8, 12, 13, 15, 38, 44, and 51, proposed rule, 91 FR 59406 (September 18, 2026). https://www.federalregister.gov/documents/full_text/text/2026/09/18/2026-19162.txt