LPTA vs Best Value Government Contracting: Choosing the Right Approach

A Tale of Two Solicitations

A small IT services firm in Northern Virginia receives two RFPs on the same day. The first is from a Defense Logistics Agency field office for desktop refresh support at a single installation: 500 workstations, standard image, 90-day period of performance. The second is from a civilian agency modernizing a legacy grants management system: custom development, data migration, and a five-year IDIQ with four option years. Both are competitive. Both require a proposal by Friday. But they are not the same type of competition, and submitting the same proposal strategy to both is a fast path to losing both.

The first solicitation will almost certainly be evaluated under Lowest Price Technically Acceptable (LPTA). The second will almost certainly use a best value tradeoff. Understanding which framework governs an acquisition, and why, is not academic. It determines how you price, how thick your technical volume needs to be, and whether your past performance section is a differentiator or a checkbox.

LPTA: What the FAR Actually Says

LPTA is defined at FAR 15.101-2. Under this method, proposals are evaluated for technical acceptability first. Any proposal that fails to meet the stated minimum requirements is eliminated. Among the technically acceptable proposals, award goes to the lowest price. Period. There is no tradeoff. A vendor with superior past performance, a more experienced team, or a more detailed quality control plan cannot use those attributes to justify a higher price.

The National Defense Authorization Act (NDAA) for FY2017 and subsequent NDAAs placed restrictions on DoD's use of LPTA, requiring contracting officers to document that LPTA is appropriate before using it. Specifically, DoD must determine that the requirement is well-defined, that the risk of unsuccessful performance is minimal, and that use of LPTA is consistent with market research. Civilian agencies face no identical statutory restriction, but FAR 15.101-2 still requires a determination that best value is expected to result from selection of the technically acceptable proposal with the lowest evaluated price.

When Agencies Actually Use LPTA

LPTA is appropriate for commoditized, well-specified requirements where performance variation is low. Common examples include:

• Janitorial and facilities maintenance services with defined square footage and frequency
• Hardware procurement (laptops, servers, peripherals) against a published spec sheet
• Courier and delivery services with defined routes and service levels
• Basic staffing augmentation where the labor category qualifications are tightly defined (e.g., "Secret-cleared Help Desk Technician, IAT Level II, minimum two years experience")

If you see an RFP where the technical evaluation factors are listed as "Acceptable/Unacceptable" with no adjectival ratings or point scores, and the award section says "lowest priced technically acceptable offeror," you are in an LPTA competition. Spending proposal budget on elaborate technical narratives beyond what is needed to clear the acceptability threshold is waste.

Best Value Tradeoff: The FAR 15.101-1 Framework

Best value tradeoff, governed by FAR 15.101-1, allows the government to select an offeror other than the lowest-priced one if the perceived benefits of the higher-priced proposal are worth the additional cost. The solicitation must identify all evaluation factors and subfactors, state their relative importance, and indicate whether technical factors are more or less important than price.

A typical best value RFP might list evaluation factors in descending order of importance: Technical Approach, Past Performance, Management Approach, and Price. The Source Selection Evaluation Board (SSEB) assigns adjectival ratings (Outstanding, Good, Acceptable, Marginal, Unacceptable) or confidence ratings to non-price factors. The Source Selection Authority (SSA) then makes a documented tradeoff decision.

What "Best Value" Looks Like in Practice

Consider a real scenario: a civilian agency issues an RFP for a five-year cybersecurity operations center (SOC) support contract. Three offerors respond. Offeror A prices at $4.2M with a Good technical rating and Satisfactory past performance. Offeror B prices at $3.8M with an Acceptable technical rating and Limited Confidence past performance. Offeror C prices at $4.6M with an Outstanding technical rating and Substantial Confidence past performance.

Under LPTA, Offeror B wins if they clear the acceptability threshold. Under best value tradeoff, the SSA might document that Offeror C's Outstanding technical approach and Substantial Confidence past performance justify the $400K premium over Offeror A, because the risk of performance failure on a security operations requirement outweighs the cost savings. That documented tradeoff is the core of the best value process.

Reading the RFP to Identify Which Framework Applies

You do not always have to guess. The solicitation will tell you, if you know where to look:

1. Section M (Evaluation Factors for Award): If it says "award will be made to the lowest priced technically acceptable offeror," you are in LPTA. If it describes a tradeoff process or says "technical factors are more important than price," you are in best value.
2. Adjectival rating scales: LPTA solicitations use binary ratings (Acceptable/Unacceptable). Best value solicitations use multi-tier scales.
3. Section L (Instructions to Offerors): LPTA solicitations often impose strict page limits on technical volumes because the government does not need extensive narrative to make an accept/reject determination. Best value solicitations typically allow more pages for technical approach.
4. FAR clause references: Look for FAR 52.215-1 (Instructions to Offerors, Competitive Acquisition). The fill-in at paragraph (f)(4) will reference either FAR 15.101-1 (best value) or FAR 15.101-2 (LPTA).

Proposal Strategy Differences: LPTA vs. Best Value

Pricing Under LPTA

In LPTA, price is the only discriminator among technically acceptable offerors. Your pricing strategy must be aggressive. Conduct a thorough cost analysis: strip out any labor categories or features that are not explicitly required by the PWS. Use the most cost-efficient labor mix that still meets stated qualifications. If the RFP specifies "three years of experience," do not propose five-year veterans at a premium rate. Review GSA wage determinations under the Service Contract Act (SCA) carefully, because undercutting SCA minimums will get your proposal rejected or create compliance liability post-award.

One common LPTA mistake: over-engineering the technical volume. If the threshold is Acceptable/Unacceptable, writing 40 pages when 12 pages would achieve Acceptable is a sunk cost with zero return. Use that proposal budget elsewhere.

Technical and Past Performance Under Best Value

In best value competitions, your technical volume is a revenue-generating document. Every adjectival rating step matters. The difference between an Acceptable and a Good rating on Technical Approach can be worth hundreds of thousands of dollars in award probability. Focus on:

• Discriminators: What does your approach offer that competitors cannot easily replicate? Proprietary tools, cleared personnel already on-site, an established subcontractor relationship with a relevant small business, or a documented methodology with verifiable outcomes.
• Risk mitigation: Evaluators are scored on identifying and mitigating risk. Show the government you have already thought through the failure modes and have specific, concrete plans to address them.
• Past performance relevance: CPARS ratings matter, but relevance matters more. A "Very Good" CPARS on a $500K help desk contract does not carry the same weight as a "Satisfactory" CPARS on a $5M program that is directly analogous to the requirement. Map your references explicitly to the current PWS tasks.

Pricing Under Best Value

Best value does not mean ignore price. Price realism and price reasonableness analyses still apply. Pricing too high eliminates you from consideration even with an Outstanding technical rating. Pricing too low triggers a realism concern that can downgrade your probability of successful performance. The target is a price that is competitive within the range of reasonable offers while supporting the technical approach you have proposed. If your technical approach requires senior staff, price senior staff. Inconsistency between your technical narrative and your cost volume is a red flag evaluators are trained to find.

Matching Your Pipeline to the Right Framework

Capture strategy starts before the RFP drops. If your market research shows an agency has historically used LPTA for a recurring requirement, your pre-RFP positioning should focus on cost structure efficiency, not relationship-building around technical superiority. Conversely, if an agency is issuing a sources sought for a complex IT modernization effort and asking for capability statements, that is a best value competition in formation. Invest in shaping the evaluation criteria during the pre-solicitation phase.

Tools like Winrove (a product of IT Custom Solution LLC, plans from $49/mo) can help you parse solicitation language quickly, flag evaluation framework indicators in Section M, and identify past performance gaps before you commit proposal resources. Knowing whether you are walking into an LPTA or best value competition on day one of the solicitation changes every downstream decision.

The Practical Takeaway

LPTA and best value are not interchangeable strategies. LPTA rewards cost discipline and operational efficiency. Best value rewards differentiation, demonstrated performance, and risk reduction. Read Section M before you read anything else in the RFP. Confirm the evaluation framework, then build your proposal strategy around it. Misreading the framework is one of the most preventable reasons small businesses lose bids they were otherwise qualified to win.