Last Updated on September 15, 2026 by Jorge Lynch
There is a persistent misconception in public procurement that awarding a contract on the basis of the lowest evaluated price means accepting the lowest quality.
It does not necessarily mean that at all.
The misconception usually arises because attention is placed on the final price comparison without considering what should have happened before price became decisive.
This is particularly relevant when procuring relatively standardized goods such as computers, vehicles, office equipment, furniture, and machinery.
Quality Begins with the Requirement
Good procurement starts by determining what the public entity actually needs.
This sounds obvious, but poor requirements are a common source of procurement failure. There is often a tendency to over-specify by requesting the best or most sophisticated product available rather than the product that adequately meets the operational need.
A government office that needs computers for routine word processing, spreadsheets, email, and internet access may not need machines designed for engineering or video production.
Paying for capability that will never be used is not necessarily good procurement. It may simply be unnecessary expenditure.
The objective should therefore be to obtain a product that meets the legitimate requirement at an appropriate cost.
That requirement must then be translated into clear technical specifications, performance standards, warranty provisions, delivery requirements, qualification requirements, and other relevant conditions.
In a properly designed procurement, the required level of quality is established before price becomes decisive.
Price Should Not Be the First Question
A lowest-price approach does not mean that evaluators simply identify the cheapest bid and award the contract.
The applicable procurement framework and the solicitation documents determine the evaluation process.
Depending on the procurement, the procuring entity may need to establish:
- whether the submission is responsive to the solicitation requirements;
- whether the bidder satisfies applicable eligibility and qualification requirements;
- whether the offered goods comply with the required technical specifications;
- whether warranties, delivery arrangements, and other mandatory conditions are satisfied; and
- whether the evaluated price or cost has been calculated according to the methodology stated in the solicitation documents.
A lower price cannot compensate for failure to meet a mandatory requirement.
The comparison should therefore be between offers that have already satisfied the applicable requirements, not between an acceptable product and an unacceptable cheaper one.
That distinction changes the meaning of “lowest price.”
Lowest Bid Price and Lowest Evaluated Cost Are Different
The lowest amount written on a bid form is not necessarily the lowest evaluated cost.
Where appropriate, evaluation may consider factors such as:
- delivery;
- operating and maintenance costs;
- energy consumption;
- spare parts;
- warranty;
- useful economic life; and
- other life-cycle costs.
Consider two pieces of equipment, evaluated over a five-year operating life:
Equipment A: purchase price $90,000
Equipment B: purchase price $100,000
Equipment A appears cheaper.
But if its energy and maintenance costs are substantially higher over that same five-year period, a properly defined life-cycle cost evaluation might show:
Equipment A: $145,000
Equipment B: $125,000
Equipment B has the higher purchase price but the lower evaluated cost.
The important point is that these factors, including the evaluation period itself, must be defined in advance and disclosed in the solicitation documents. They cannot be introduced after bids are received.
Why Pay More Than Necessary?
Now consider a simpler procurement where three bidders offer goods that have all been determined to meet the stated requirements:
Bidder A: $100,000
Bidder B: $112,000
Bidder C: $125,000
Assume there are no additional rated criteria or life-cycle cost differences that affect the result.
What would justify paying $125,000 when another qualified bidder is offering goods that meet the same requirement for $100,000?
Saying that the more expensive product is “better quality” is not enough.
If additional durability, functionality, performance, or service has value to the procuring entity, that value should have been reflected in the requirements or evaluation methodology.
If those additional characteristics were not needed, paying more for them may simply mean purchasing something the public entity did not require.
This is why selecting the lowest evaluated compliant offer can be entirely consistent with good public procurement.
It is not an instruction to buy poor quality. It is a control against paying more than necessary for the requirement the entity has decided it needs.
Price Should Not Always Determine the Award
There is an important qualification.
Not every procurement should be decided primarily on the basis of lowest evaluated cost.
For complex goods, works, information systems, specialized equipment, and other procurements where meaningful differences in quality or performance matter, additional criteria may be appropriate.
Public procurement frameworks may permit or require consideration of factors such as quality, sustainability, performance, risk, and life-cycle cost.
The World Bank, for example, has required Rated Criteria as the default approach for most international competitive procurement under Bank-financed projects since September 2023, replacing the earlier framework under which their use was merely encouraged. The requirement carries defined exceptions, including pharmaceuticals, vaccines, commodities, off-the-shelf goods, and educational materials. That exception matters for this discussion: many of the standardized goods used as examples throughout this article, such as computers, vehicles, and office equipment, will often qualify as off-the-shelf goods and can therefore remain properly evaluated on lowest evaluated cost even under the Bank’s current rules.
The broader principle is straightforward:
The award decision should follow the evaluation methodology appropriate to the procurement and disclosed to bidders in advance.
For straightforward goods that can be clearly specified and assessed largely on a pass/fail basis, lowest evaluated cost may be appropriate.
For more complex procurements, additional evaluated or rated criteria may be necessary.
When Low Price Produces Poor Quality, Look Upstream
When someone says that “lowest price produces low quality,” it is worth asking what actually went wrong.
Were the specifications inadequate?
Were minimum performance requirements too low?
Were warranty and after-sales service requirements weak?
Was durability ignored?
Were qualification requirements insufficient?
If an inferior product satisfies the specifications, the first question should be whether those specifications properly reflected the entity’s needs.
Selecting a more expensive offer after bids have been received cannot compensate for poorly defined requirements.
Quality must be built into the procurement before competition begins.
Quality Must Also Be Verified After Award
Defining quality before bidding is only part of the control.
After award, the procuring entity must verify that what is delivered actually meets the contract requirements.
That may involve inspection, testing, commissioning, review of deliverables, or other verification procedures.
Acceptance should be supported by evidence, and payment should follow verified acceptance.
If the contract requires a particular standard but the entity accepts something below that standard, the problem is not the lowest-price award criterion. It is a contract administration failure.
Prudent Use of Public Funds
Public procurement officials spend money on behalf of the public.
Buying the cheapest product regardless of whether it meets the requirement is poor procurement.
But paying more simply because a more expensive product is perceived to be “better” can also be poor procurement.
Good procurement lies between those two extremes:
Define the need carefully. Translate it into clear requirements. Tell the market how offers will be evaluated. Determine which offers satisfy those requirements. Consider life-cycle costs and other relevant factors where justified. Then apply the evaluation methodology as disclosed. And after award, verify that what was contracted is actually delivered.
Selecting the lowest evaluated price does not necessarily mean accepting low quality.
It means that once the required quality and other requirements have been properly established and satisfied, the public entity should have a defensible reason for paying more than necessary.
That is not “lowest price at any cost.”
It is prudent use of public funds.
Related Resource
The relationship between requirements, evaluation, award, acceptance, payment control, and contract administration is discussed in greater detail in Public Procurement and Contract Administration: A Brief Introduction, Third Edition.
The Third Edition also includes practical tools and checklists designed to help procurement practitioners translate these principles into working controls.