One month after the White House signed an executive order on April 30, 2026 making firm-fixed-price contracts the government's default, procurement attorneys and acquisition specialists are warning that the mandate's practical effect on complex federal programs may be the opposite of its intent, according to Federal News Network. Rather than cutting costs, forcing FFP terms onto requirements that are inherently unstable pushes contractors to price that uncertainty directly into their bids — and may cause some firms to decline to compete at all.
Why Requirement Stability Is the Key Variable
Firm-fixed-price contracting works when the government can define precisely what it wants before the contract is signed and when that definition is unlikely to change during performance. In those conditions — a commodity purchase, a well-specified construction project, a software product with frozen requirements — FFP puts appropriate risk on the party best positioned to manage it: the contractor who controls the means of production.
The challenge is that complex federal missions rarely produce stable requirements. Defense research and development work, by definition, involves discovering what is technically feasible — a scope that evolves as knowledge is gained. Large IT modernization programs frequently encounter legacy system incompatibilities, policy changes, and shifting user needs that require requirements adjustments during multi-year performance periods. Advisory and assistance services are shaped by the evolving priorities of agency leadership, which can change with little notice. In all of these contexts, a fixed price agreed to before performance begins is a price set in the absence of complete information.
When contractors are required to price that incomplete information under a fixed-price structure, the rational response is to include a risk premium — a buffer that compensates for the cost of absorbing scope changes that would otherwise be covered by equitable adjustments under a cost-type vehicle. Mayer Brown's analysis of the EO notes that historical precedent for forced FFP application to complex programs includes delays, renegotiations, and outright cancellations, outcomes that cost the government more in the long run than a well-managed cost-type contract would have.
Some contractors, particularly smaller firms with limited working capital, may find that the risk of absorbing cost overruns on a fixed-price complex program exceeds their tolerance entirely. Bid avoidance — declining to propose on a requirement — reduces competition, which is a direct driver of higher final prices. A mandate intended to impose discipline on government spending may paradoxically reduce the competitive pressure that keeps prices down.
Agency Implementation Deadlines
The EO establishes a tiered implementation timeline that agencies are now working against. For contracts above $10 million at civilian agencies and above $100 million at the Department of Defense, agency heads must personally authorize any departure from FFP. That approval requirement creates a bureaucratic gatekeeping layer that did not previously exist — program offices that previously selected cost-type structures based on their own contracting officers' judgment now need to escalate non-FFP decisions to the senior acquisition official level.
OMB guidance implementing the EO is due June 14, 2026, which will clarify how agencies should document exception justifications and what evidence is required to support an agency-head determination that a cost-type or time-and-materials vehicle is appropriate. The July 29 deadline applies to the largest existing cost-type contracts, which agencies are required to begin renegotiating toward fixed-price structures where feasible. A FAR amendment codifying the EO's requirements into the Federal Acquisition Regulation is scheduled for August 28, 2026, at which point the directive becomes embedded in the regulatory framework rather than existing solely as executive direction.
The renegotiation requirement is the most immediately disruptive element for contractors currently performing under cost-type awards. Agencies approaching contractors about converting existing contracts to FFP will face resistance where requirements have not stabilized — and contractors have every legal right to decline conversion if it would impose unreasonable risk. Contracting officers who push conversion without adequate justification expose their agencies to bid protests and contract disputes.
What It Means for Contractors
The most immediate action item for contractors is reviewing every active and pending proposal to assess whether their pricing reflects the risk environment under an FFP structure. Requirements that would have been priced under cost-plus terms assumed that unforeseeable scope growth would be recovered through equitable adjustments. Under FFP, that recovery mechanism is not available by default — it requires a formal contract modification and government agreement that the change was outside the original scope. Pricing submissions should be reviewed to ensure that contingency and risk reserves are explicitly included in the FFP rate structure.
For R&D and IT modernization contractors, the exception justification process is the critical pathway to preserving cost-type vehicles on genuinely complex work. Contractors should be prepared to support their agency customers in building the agency-head exception justification — documenting why the requirement cannot be adequately defined in advance, what the technical risks are, and why cost-type coverage is necessary to achieve the mission. A well-constructed justification package reduces the agency's burden and increases the probability that the exception is granted.
Equitable adjustment strategy deserves early attention. On contracts that do convert to FFP, establishing a clear baseline definition of scope at contract award is essential. Any government-directed change to that baseline creates the predicate for an equitable adjustment claim. Contractors who invest in rigorous scope documentation at award will be better positioned to recover costs when requirements evolve — as they inevitably do on complex programs.
Small businesses face disproportionate exposure. The financial reserves needed to absorb cost overruns on a fixed-price complex program are more readily available to large prime contractors than to small firms. Small business set-aside requirements do not exempt those awards from the FFP mandate, which means agencies and small business advocates will need to think carefully about which set-aside requirements can realistically be fulfilled under FFP terms and which need exception treatment.
One near-term action that any contractor can take regardless of company size is reviewing active and pipeline proposals for requirements that were scoped under cost-type assumptions and are now being re-evaluated under the FFP framework. Identifying those contracts early — before agency contracting officers initiate conversion discussions — allows companies to prepare their internal cost data, document baseline scope thoroughly, and consult legal counsel on their rights under the terms of their existing agreements. Preparation before the agency arrives at the table is far more effective than responding reactively once the pressure to convert has been applied.
