1. Home
  2. |Insights
  3. |Watch for Conversion of Best-Value Evaluation to Lowest-Cost, Technically Acceptable

Watch for Conversion of Best-Value Evaluation to Lowest-Cost, Technically Acceptable

Client Alert | less than 1 min read | 12.04.13

With budgetary pressures increasing, agencies are more prone to make cost the determinative factor in their evaluations – regardless of the actual evaluation scheme – improperly converting a procurement into a lowest-cost, technically acceptable one. As demonstrated in GAO's recent decision in Logistics 2020, Inc. (Nov. 6, 2013), this may occur when a solicitation calls for a best-value award, but the agency uses evaluation criteria that merely measure whether proposals are technically acceptable, not whether any qualitative differences exist between proposals.


Insights

Client Alert | 5 min read | 08.21.26

FTC Proposes Enforcement Policy Statement on Personalized Pricing: What Businesses Need to Know

On August 19, 2026, the Federal Trade Commission (FTC) announced a proposed Enforcement Policy Statement on personalized pricing — the practice of companies using consumers’ personal data to set individualized prices, discounts, coupons, or other incentives. The proposed statement, which is open for public comment for 30 days following publication in the Federal Register, marks a major step up in the FTC’s focus on data-driven pricing strategies and puts businesses across industries on notice that undisclosed or inadequately disclosed personalized pricing will not be tolerated. Importantly, while the proposed statement is not a binding legal requirement and does not create new legal obligations, it serves as an enforcement warning that the FTC is prepared to use its existing enforcement authority under Section 5 of the FTC Act (Section 5) and is also a potential harbinger of rulemaking. Businesses that engage in — or are considering — personalized pricing should carefully assess their disclosure practices and data collection procedures against the standards articulated in this statement....

View All Insights