LPTA: Lowest Price Technically Acceptable Guide (Sept 2026)

When a solicitation runs under LPTA, the evaluation stops at 'acceptable' and price decides the rest. There's no adjectival scoring, no partial credit for a stronger technical approach, and no premium available for above-minimum performance. The strategic discipline is tighter than most teams expect: clear every criterion without ambiguity, then price as aggressively as cost realism allows. Understanding exactly where that line sits is where competitive positioning under LPTA actually starts.

TLDR:

• LPTA (FAR 15.101-2) awards to the lowest-priced offeror that clears a pass/fail technical bar; exceeding it earns nothing.
• Under DFARS 215.101-2-70, DoD contracting officers must confirm all eight statutory conditions before using LPTA, and the 2018 NDAA prohibited it entirely for major defense acquisition program development contracts.
• In LPTA, past performance earns no scoring credit; a strong delivery record clears the gate or it doesn't, then price decides.
• Compliance documentation is where pursuit teams most often miscalculate: a single vague Section L/M response can trigger an unacceptable finding regardless of your price.
• GovEagle parses Sections C, L, and M into an Excel-native compliance matrix and flags unaddressed requirements before submission, with IDS achieving 3-4x faster proposal preparation and Chevo seeing 30-40 percent time savings on RFIs.

What LPTA Means in Federal Contracting

LPTA, or lowest price technically acceptable, is a source selection methodology defined under FAR 15.101-2. Under this process, award goes to the lowest-priced offeror whose proposal meets stated acceptability standards. Meeting the bar is enough; exceeding it earns nothing. LPTA sits at one end of the best value continuum, opposite the tradeoff process, where agencies weigh quality factors against price. That positioning within federal source selection mechanics is what shapes how you write, price, and position a proposal against it.

How the LPTA Evaluation Process Works

Contracting officers running an LPTA evaluation follow a straightforward sequence. Proposals are reviewed against stated evaluation factors on a strict pass/fail basis. There are no adjectival ratings, no numerical scoring, no partial credit. A proposal either meets the acceptability threshold or it does not.

Once technical acceptability is confirmed, evaluators rank offers by price, and award goes to the lowest-priced acceptable proposal. A contractor who submits a technically superior solution gains nothing from that superiority as the evaluation stops at "acceptable" and lets price decide the rest.

Agencies typically review proposals in price order, starting with the lowest-priced offer and working up until they find one that clears the technical bar. Per guidance from the Army Judge Advocate General's Legal Center and School, identifying at least two acceptable offerors is considered a key discipline in LPTA procurements, though agencies often stop as soon as one acceptable offer is confirmed. The compliance pressure that structure creates is real: Chevo, a mid-sized federal contractor, saw 30-40 percent time savings on RFIs and 15-25 percent on RFPs by tightening its compliance review workflow, a direct result of the binary stakes the pass/fail gate imposes.

When Agencies Are Permitted to Use LPTA

FAR 15.101-2(a) states that LPTA is appropriate when best value is expected to result from selecting the technically acceptable proposal with the lowest assessed price. That standard applies when minimum requirements can be described clearly, performance risk is low, the work is not developmental or complex, and paying a premium for above-minimum performance would yield no meaningful benefit to the government.

For DoD acquisitions, DFARS 215.101-2-70 codifies six statutory factors (drawn from the Defense Federal Acquisition Regulation Supplement) contracting officers must confirm before using LPTA, later expanded to eight by the 2018 NDAA. Standard commodity purchases, straightforward services with well-defined scopes, and supply contracts with tight specifications tend to fit this model. Knowledge-based professional services and complex technical work generally do not.

DFARS Restrictions: Where LPTA Is Prohibited or Limited

Congress drew hard lines around DoD's use of LPTA through successive NDAAs. Section 813 of the 2017 NDAA introduced six conditions contracting officers must confirm before using LPTA. Section 822 of the 2018 NDAA added two additional conditions. Section 832 of the same NDAA outright prohibited LPTA for engineering and manufacturing development (EMD) contracts on major defense acquisition programs (MDAPs).

Under DFARS 215.101-2-70, all eight conditions must be satisfied:

• Minimum requirements can be described clearly and expressed as performance objectives
• Proposals will be scored against measurable acceptability standards
• No, or minimal, value would be gained from a higher-priced proposal
• Price is a material factor in the source selection decision
• The expected contract type is appropriate for LPTA
• Acquiring a commercial product or commercial service
• No meaningful performance risk exists
• Competitive market conditions support LPTA use

Note: the list above is a summary representation. Verify the exact conditions against the current CFR text at DFARS 215.101-2-70 before relying on it for a procurement decision.

The 2017 NDAA also cautioned against LPTA for knowledge-based professional services, personal protective equipment, and knowledge-based training in contingency operations outside the United States. For defense contractors, these restrictions narrow LPTA's footprint considerably on the DoD side of the market.

LPTA vs. Tradeoff: How the Two Source Selection Approaches Differ

The two source selection methods reflect fundamentally different philosophies about what the government is buying.

Under the tradeoff process (FAR 15.101-1), the government can pay more to get more. Evaluators score proposals on technical merit and weigh that score against price, so a higher-priced offer can win if the superiority warrants the premium. Under LPTA, once a proposal clears the acceptability bar, additional quality is irrelevant to award.

The practical effect on offerors is direct: in a tradeoff procurement, investing in a stronger technical approach can shift the award in your favor. In an LPTA competition, that same investment earns nothing beyond compliance.

Setting the Technical Acceptability Bar: Why Definition Precision Matters

The pass/fail structure only works if the pass threshold actually means something. When acceptability standards are vague or set too low, every offeror clears them and the competition becomes pure price. When they are set too high, the agency is functionally running a tradeoff without calling it one.

As Integrity Management Consulting has noted, the key is whether requirements are clearly definable and performance risk is minimal. When those conditions hold, LPTA can produce best value, but only if the acceptability criteria are specific enough to screen out genuinely insufficient proposals. Sections L and Section M evaluation factors carry that burden. Standards written in measurable, performance-based terms give evaluators a defensible line; standards written in ambiguous or aspirational language give protestors an opening and give low-quality offerors a pass they have not earned.

Past Performance Under LPTA

Under FAR 15.101-2(b)(1), past performance need not be an evaluation factor in LPTA source selections at all, provided the contracting officer documents the file per FAR 15.304(c)(3)(iii). When it is included, past performance receives the same pass/fail treatment as every other factor: rated acceptable or unacceptable, nothing in between.

The contractor implication is direct. An exceptional past performance record earns no additional credit under LPTA. Where a tradeoff procurement might reward a strong delivery history with higher adjectival ratings and a justifiable price premium, LPTA collapses that advantage into a binary gate. Clear it and move on; the award still goes to whoever priced lowest.

Bid Protest Considerations in LPTA Procurements

LPTA protest grounds narrow around three avenues: disputing a technical unacceptability finding, arguing the agency ran a comparative evaluation under an LPTA label, or pre-award challenges to whether LPTA was appropriate for the requirement. GAO's January 2025 ruling in Mission Essential Group, LLC, B-422698.2 (Jan. 8, 2025) confirmed that challenges to the evaluation scheme itself can prevail.

Proposal Strategy for LPTA Solicitations

Under LPTA, narrative sophistication and above-minimum technical investment carry no evaluation weight once the pass/fail gate is set. The strategic discipline moves entirely toward three priorities:

• Clear every acceptability criterion without ambiguity. A single unacceptable finding eliminates you regardless of price, so rigor against every Section L instructions and notices requirement is non-negotiable.
• Price as aggressively as cost realism allows (see the pricing and cost volumes guide for how to structure this). Award goes to the lowest acceptable offer, so your technical advantage caps at passing.
• Contain investment in proposal quality the evaluation cannot reward. Extensive differentiators and above-minimum solution design will not move the outcome.

The compliance side is where teams most often miscalculate. Cutting corners on technical narrative is rational; cutting corners on acceptability documentation is not. Evaluators are making a binary check, and a vague response to any stated subfactor gives them grounds to rate you unacceptable. Write to the standard explicitly.

On pricing, cost realism reviews still apply in a request for proposal evaluation, so artificially low numbers can themselves trigger an unacceptable finding. The target is the lowest defensible number, not simply the lowest possible one.

How GovEagle Supports LPTA Pursuits

In LPTA, compliance matrix accuracy is the single highest-impact variable in your pursuit. One missed Section L or M requirement triggers automatic elimination, regardless of where your price lands.

GovEagle parses Sections C, L, and M line by line into an Excel-native compliance matrix and generates a requirement-mapped annotated outline in Microsoft Word before drafting begins. Automated color team review reports then flag missing requirements before submission, so gaps surface internally instead of at evaluation. That is the exact friction point that eliminates teams before price is ever considered; Book a Demo to see how that gap-detection workflow runs across a live solicitation. For teams running multiple LPTA pursuits simultaneously, where margin compression often limits how much proposal investment is defensible, that throughput matters. Government proposal software is how leading teams manage it: IDS achieved 3-4x faster proposal preparation, and Chevo saw 30-40 percent time savings on RFIs.

More detail on how GovEagle structures the full pursuit workflow is available on the proposal automation solutions page.

Final Thoughts on How LPTA Works in Federal Source Selection

Put your proposal investment where it moves the outcome: airtight acceptability documentation and the lowest defensible number. GovEagle's proposal automation platform automates the compliance matrix before a single word of narrative gets written, so gaps surface internally, not at evaluation. Request a demo to see the workflow in action.

FAQ

What is lowest price technically acceptable (LPTA) and when can federal agencies use it?

LPTA is a source selection method under FAR 15.101-2 where award goes to the lowest-priced offeror whose proposal meets stated acceptability standards on a pass/fail basis; exceeding those standards earns nothing. Agencies may use it when minimum requirements can be described clearly, performance risk is low, and paying a premium for above-minimum performance would yield no meaningful benefit to the government.

LPTA vs. tradeoff: which source selection method should you prepare for?

LPTA and the tradeoff process reflect different acquisition philosophies: under tradeoff, a higher-priced proposal can win if the technical superiority warrants the premium; under LPTA, the evaluation stops at "acceptable" and price decides the rest. Before investing in a stronger technical approach, confirm which method the solicitation uses. Under LPTA, that investment caps at clearing the pass/fail gate.

What proposal strategy works best under an LPTA procurement?

Price as aggressively as cost realism allows and write explicitly to every stated acceptability criterion without ambiguity, since a single unacceptable finding eliminates you regardless of price. Above-minimum technical investment and elaborate differentiators carry no weight once the pass/fail gate is set, so contain proposal spend accordingly and direct rigor toward compliance documentation, not narrative sophistication.

Can a lean team run multiple LPTA pursuits without missing Section L or M requirements?

Yes, but compliance matrix accuracy becomes the single highest-impact variable across a simultaneous pipeline, since one missed requirement triggers automatic elimination regardless of price. GovEagle parses Sections C, L, and M line by line into an Excel-native compliance matrix and generates a requirement-mapped annotated outline in Microsoft Word before drafting begins. IDS achieved 3-4x faster proposal preparation and Chevo saw 30-40 percent time savings on RFIs running that workflow across concurrent pursuits.

How do DFARS restrictions on LPTA affect DoD proposals?

DFARS 215.101-2-70 codifies eight conditions contracting officers must confirm before using LPTA on DoD acquisitions, and the 2018 NDAA outright prohibits it for engineering and manufacturing development contracts on major defense acquisition programs. For defense contractors, this narrows LPTA's footprint considerably: knowledge-based professional services, personal protective equipment, and complex technical work generally do not qualify under those conditions.