Best Value Tradeoff vs LPTA, Plus the Third Approach the FAR Overhaul Named

A tradeoff lets the government award to other than the lowest priced or other than the highest technically rated offeror, and a higher priced proposal can win when its benefits merit the extra cost. LPTA awards to the lowest priced proposal that meets every acceptability standard, and no tradeoffs are allowed. Both are ways to reach best value; they differ in whether better than acceptable is worth paying for.

In a tradeoff, the evaluation assesses each offeror's ability to do the work and records relative strengths, deficiencies, significant weaknesses and risks (15.202(b)(2) in the deviation text). Proposals can be ranked. In LPTA, proposals are evaluated for technical acceptability only, and the RFP must say award goes to the lowest evaluated price among acceptable proposals (15.103-2(b)).

The codified FAR frames the choice the same way. FAR 15.101 calls it a "best value continuum": price "may play a dominant role" when the requirement is clearly definable and performance risk is minimal, and technical or past performance considerations may dominate as the requirement gets less definitive or riskier.

The model deviation text for Part 15 was issued September 30, 2025, according to acquisition.gov's deviation guide. It moves source selection approaches to 15.103 and adds two named options: highest technically rated with a fair and reasonable price (15.103-3) and phased acquisition (15.103-4), which splits a complex or high-risk buy into separate awards at distinct phases. The section also says agencies may use "any one or a combination" of approaches, "including but not limited to" the ones listed.

One familiar sentence moved rather than disappeared. Codified FAR 15.101-1(b)(2) requires a tradeoff solicitation to state whether all non-cost factors combined are "significantly more important than, approximately equal to, or significantly less important than cost or price." The deviation puts that requirement in 15.104(d), "Factor importance," citing 10 U.S.C. 3206(c)(1)(C) and 41 U.S.C. 3306(c)(1)(C), and applies it to competitive RFPs generally rather than only to tradeoffs. The one exception is the DoD, NASA and Coast Guard case in 15.104(b)(1)(ii), where a multiple-award RFP for the same or similar services, above the simplified acquisition threshold and intending awards to all qualifying offerors, may leave price out as an award factor and consider it at the order level instead.

The deviation applies at an agency only once that agency issues its own class deviation. The deviation guide lists Part 15 deviations from more than 30 agencies, including DoD, GSA, HHS, DHS, VA, HUD and Treasury; DoD readers should also check DoD's current DFARS and deviation text. Part 15 is among the parts in a proposed rule published September 18, 2026 (FAR Case 2026-003), whose comment period closed October 19. As of November 15, 2026, the Federal Register lists no final rule for it. Our post on where the FAR overhaul stands explains how the deviations and proposed rules fit together.

Outside DoD, only when six conditions are met and the contracting officer documents why. They come from section 880 of the John S. McCain National Defense Authorization Act for Fiscal Year 2019, and they appear in both the codified FAR 15.101-2(c) and the deviation's 15.103-2(c). DoD follows its own list in DFARS 215.101-2-70, drawn from section 813 of the FY2017 NDAA as amended.

Both texts then tell contracting officers to avoid LPTA "to the maximum extent practicable" for procurements predominantly for information technology services, cybersecurity services, systems engineering and technical assistance, advanced electronic testing and other knowledge-based professional services. Both also cover personal protective equipment and knowledge-based training or logistics services in contingency operations or other operations outside the United States. Only the civilian list names audit or audit readiness services, health care services and records, and telecommunications devices and services.

DFARS goes further with outright prohibitions: no LPTA for an auditing contract (10 U.S.C. 240f); for personal protective equipment or an aviation critical safety item when the requiring activity advises that the level of quality or failure could result in combat casualties; or for engineering and manufacturing development of a major defense acquisition program for which budgetary authority is requested beginning in fiscal year 2019.

The agency decides in advance that price tradeoffs would not be advantageous and that the requirement warrants paying any fair and reasonable price for the highest quality performance. Proposals are evaluated on the non-price factors, and the source selection authority identifies the highest rated one. Its price is then tested for fairness and reasonableness under subpart 15.4.

If the price passes, that proposal wins. If not, the authority moves to the next highest rated proposal and repeats the price test until award goes to the highest technically rated responsible offeror with a fair and reasonable price. The RFP must tell offerors up front that no tradeoffs will be made and that the highest technically rated proposal will be selected if its price is fair and reasonable (15.103-3(b)).

For offerors, this changes the pricing question. There is no credit for being cheaper than a stronger competitor, but a price the government finds unreasonable sends the evaluation down the list.

For most knowledge-based IT work, the regulations point away from LPTA, so in practice the choice is often between a tradeoff and the highest technically rated approach. A tradeoff fits when the agency wants to weigh how much better a proposal is against how much more it costs. Highest technically rated fits when the agency has already decided quality should drive the award and the remaining question is whether the price is fair.

LPTA can still fit a narrow, well-specified piece of a larger effort, such as a well-defined product buy, where every civilian condition holds and nothing above the minimum adds value. The market research file is where that case usually gets made or lost: it shows whether the requirement is stable, whether the market offers meaningful differences, and whether paying for more would buy anything.

Whichever approach is chosen, the file should let a reviewer trace the award back to the RFP. The deviation's 15.205 requires the source selection decision to reflect the source selection authority's independent judgment, compare proposals against all the criteria in the RFP, and document the rationale for business judgments and tradeoffs, "including benefits associated with additional costs." It adds that the documentation "does not need to quantify the tradeoffs."

For a tradeoff, that means naming the specific strengths that justify a higher price, not repeating adjectival ratings. For LPTA, good practice is a written finding on each of the six (or, at DoD, eight) conditions, plus the record that each acceptable proposal met every standard. For highest technically rated, it means the ranking, the price reasonableness analysis for the winner and, where it happened, for each proposal that was passed over on price.

From our delivery teams: Write the LPTA justification as one short paragraph per condition, each tied to evidence already in the file (the performance standards, the market research, the life-cycle cost analysis). A reviewer checking conditions one by one finds the answer where they expect it.

For offices rethinking how that record gets built, AIR-Quire drafts the FAR-required acquisition documents, checks every step against the agency's rules and compiles a complete, reviewable record, with a person in charge of every decision.