The best-value continuum
Every negotiated federal award sits somewhere on a single scale. FAR 15.101 calls it the best-value continuum, and it runs from lowest price technically acceptable at one end to a full tradeoff at the other. Where a solicitation lands on that scale decides almost everything about how the proposal should be written. The same technical story that carries a tradeoff is wasted effort under LPTA, and the low price that wins LPTA can lose a tradeoff outright.
The continuum is not two boxes. FAR 15.101 lets an agency use either process, or a combination, depending on how well the requirement is defined and how much risk the work carries. The further a requirement sits toward the tradeoff end, the more the government is willing to pay for a better answer. The further it sits toward LPTA, the more price alone governs among the proposals that clear the bar. Reading which model applies, and reading it correctly, is the first move in any capture.
Section M states the source-selection method and the relative importance of every evaluation factor. A firm that guesses the method from the work type, instead of reading Section M, routinely builds the wrong proposal for the buy in front of it.
What LPTA actually requires
Under FAR 15.101-2, award goes to the lowest evaluated price among proposals that meet or exceed the acceptability standards for the non-price factors. Two features define the process. First, the non-price factors are scored pass or fail. A proposal is acceptable or unacceptable on each standard, with no partial credit and no ranking above the line. Second, the rule is explicit that tradeoffs are not permitted. Once a proposal is rated acceptable, exceeding the requirement earns nothing.
That makes the acceptability standards the entire game. The solicitation has to describe the minimum requirements clearly and comprehensively, because an evaluator can only mark a proposal acceptable against a standard that is written down. When the standards are vague, LPTA gets fragile, and disappointed bidders protest that the line was drawn inconsistently.
Where the tradeoff process gives evaluators room
The tradeoff process, FAR 15.101-1, is the opposite posture. It applies when it may be in the government's interest to consider award to other than the lowest-priced or other than the highest technically rated offeror. Non-price factors are rated and ranked, not just passed or failed, and the source selection authority may pay a premium for a stronger proposal.
The rule sets two guardrails. All evaluation factors and significant subfactors that will affect contract award, and their relative importance, must be clearly stated in the solicitation. And the rationale for any tradeoff must be documented in the file, with the perceived benefits of the higher-priced proposal shown to merit the additional cost. That documentation duty is a small firm's opening. Because the evaluator has to write down why a higher-priced proposal is worth more, a proposal that hands the evaluator that language, in the form of concrete and verifiable strengths, is doing the source selection authority's work for them.
The DoD limits on LPTA for knowledge-based work
DoD has spent several years narrowing where LPTA can be used. DFARS 215.101-2-70 implements limits from the FY2017 National Defense Authorization Act, as amended by the FY2018 Act, and a final rule effective October 2019 wrote them into the supplement. LPTA is allowed only when a set of conditions all hold, among them that the minimum requirements can be described clearly and comprehensively, that little or no value would come from a proposal exceeding them, that the technical approaches need little subjective judgment, and that the contract file documents that the lowest price reflects full life-cycle cost.
The regulation then names work where contracting officers must avoid LPTA to the maximum extent practicable: information technology services, cybersecurity services, systems engineering and technical assistance, advanced electronic testing, and other knowledge-based professional services, along with certain training and logistics services. It bars LPTA outright for a short list that includes personal protective equipment and aviation critical safety items whose failure could cause combat casualties. For a small technical firm the practical read is direct. For software, data, and engineering services inside DoD, a tradeoff is the expected posture, and an LPTA solicitation for that kind of work is now the exception that has to justify itself.
The two models side by side
The differences are structural, not cosmetic, and they change the shape of a winning proposal.
| Dimension | LPTA | Best-value tradeoff |
|---|---|---|
| Governing FAR section | 15.101-2 | 15.101-1 |
| Award basis | Lowest evaluated price among acceptable proposals | Best overall value across price and non-price factors |
| Role of non-price factors | Pass or fail against acceptability standards | Rated and ranked; can justify a price premium |
| Evaluator discretion | Minimal, largely objective | Substantial, documented judgment |
| Credit for exceeding minimums | None | Can win the award |
| Where it fits best | Well-defined, commodity-like requirements | Complex, judgment-heavy work |
Reading Section M: factors and relative importance
Section M is where the method and the weights live. FAR 15.304 requires the solicitation to state whether the non-price factors, combined, are significantly more important than price, approximately equal to price, or significantly less important than price. That one sentence changes the math. When technical is significantly more important, a small firm with a genuinely stronger approach can win at a higher price. When price is significantly more important, the same firm has to get its price close before its technical edge matters at all.
Section M also lists the evaluation factors and subfactors in the order and structure the evaluators will use. If a subfactor appears there, it will be scored, and every subfactor deserves a dedicated, labeled response the evaluator can find quickly. Content that answers a Section M factor but hides under a heading that does not match reads, to a reviewer moving fast, as if it were never written.
Price realism is not price reasonableness
Two price analyses get confused, and the difference decides how aggressively to price.
Price reasonableness. The question is whether a price is too high. It protects the government from overpaying and is usually satisfied by adequate price competition or comparison to the market. It applies broadly, including to fixed-price work.
Price realism. The question is whether a price is too low to perform the work as proposed. Section M has to invoke it for a fixed-price competition. Where it applies, a price that undercuts the labor the work requires can be judged unrealistic and can cost technical confidence or the award.
Cost realism. On cost-reimbursement work, the government tests whether proposed costs match the proposed effort and may adjust them to a most-probable cost for evaluation purposes.
The trap for a small firm is bidding a rock-bottom price into a tradeoff that also invokes price realism. The low number does not buy the ranking that only quality earns, and it can read as a misunderstanding of scope. Price to a defensible basis of estimate, not to the floor.
How LPTA changes your proposal
Under LPTA the proposal has one job on the non-price side: clear every acceptability standard cleanly, with nothing left ambiguous, and then compete on price. Extra pages of technical excellence do not move the award, and time spent writing them is better spent sharpening price and removing any risk of an unacceptable rating. Map each stated standard to a short, direct, labeled response that leaves an evaluator no reason to mark it anything but acceptable. Then make the price as lean as the cost structure honestly allows.
How a tradeoff changes your proposal
A tradeoff rewards the opposite behavior. Here the proposal has to build discriminators: concrete strengths tied to the stated factors that an evaluator can quote in the decision document. Name the people, show the method, and give verifiable evidence rather than capability narrative. The goal is to make the higher-value case so plainly that the source selection authority can defend a premium in a sentence. In a tradeoff, the proposal that best arms the evaluator to justify paying more usually wins.
Where each model leaves leverage
The two ends of the continuum leave a small firm very different room to compete on quality. The relative leverage below is illustrative rather than a measured statistic, but it captures the pattern that decides where proposal effort belongs.
Common misreads of the two models
It is services, so it must be a tradeoff
Most knowledge-based DoD services do run as tradeoffs now, but civilian agencies still use LPTA for work that looks technical, and a commodity-like requirement can be LPTA anywhere. Read Section M. Do not infer the method from the type of work.
LPTA just means the cheapest bid wins
The cheapest among the acceptable bids wins. A low price attached to a proposal that misses even one acceptability standard loses to a higher, fully acceptable one. Acceptability comes before price, every time.
A stronger technical proposal always helps
Under a tradeoff it is the whole game. Under LPTA, above the acceptability line, it does nothing, and effort spent exceeding a pass or fail standard is effort that could have gone to price.
The relative-importance sentence is boilerplate
The significantly-more, approximately-equal, significantly-less statement under FAR 15.304 is the single most useful sentence in Section M. It tells a bidder where the evaluation weight actually sits, and therefore where to spend.
Questions to confirm before you bid
Which model does Section M name? LPTA or tradeoff, read directly from Section M rather than inferred from the work.
What is the relative importance of non-price factors to price? The significantly-more, equal, or significantly-less language decides where the effort goes.
Does Section M invoke price realism? If it does on a fixed-price buy, thin pricing carries risk beyond simply losing on price.
Are the acceptability standards and evaluation factors clearly written? Vague standards mean protest risk and inconsistent scoring, which changes how much margin to leave.
Does the work sit in a category where DoD restricts LPTA? If the requirement is knowledge-based and the solicitation still runs LPTA, understand the justification before committing.
Bottom line
Federal source selection is one continuum with two very different ends, and FAR Part 15 tells a bidder which end applies to anyone who reads it. LPTA rewards a clean, fully acceptable proposal at the leanest honest price. A tradeoff rewards discriminators that let an evaluator justify paying more. The firms that win read Section M first, weight their effort to the stated importance of each factor, price to a defensible basis rather than to the floor, and build the proposal the chosen model actually rewards. The method is not a detail. It is the strategy.
Frequently asked questions
LPTA (FAR 15.101-2) awards to the lowest evaluated price among proposals rated technically acceptable, with no credit for exceeding requirements and no tradeoffs permitted. A tradeoff (FAR 15.101-1) rates and ranks the non-price factors and lets the government pay a premium for a stronger proposal, with the rationale documented in the file.
In Section M of the solicitation, along with the evaluation factors and their relative importance under FAR 15.304. Read Section M before deciding how to build the proposal, because the method changes what a winning proposal looks like.
Yes, but DFARS 215.101-2-70 limits it. LPTA is allowed only when specific conditions all hold, must be avoided to the maximum extent practicable for information technology, cybersecurity, systems engineering, and other knowledge-based services, and is barred for a short list of safety-critical items.
Reasonableness asks whether a price is too high; realism asks whether it is too low to perform the work as proposed. Realism must be invoked in Section M for fixed-price competitions and can downgrade a proposal that prices below what the scope requires.
Under a tradeoff, yes, it is what wins. Under LPTA, above the acceptability line, no. Exceeding a pass or fail standard earns nothing, so once a proposal is acceptable the remaining effort belongs on price.