Best value award: defining it before you have to defend it

Reference article · 5 min read

Low bid is a comfortable default because it removes discretion. For technology, that same absence of discretion is often the problem. The cheapest proposal can carry integration work the agency absorbs in staff time, a license model that reprices at renewal, or a support arrangement that pushes cost into the next budget cycle. Most state and local procurement codes allow award on a basis other than price alone, on one condition: the agency has to say in advance how it will decide, and then decide that way.

That condition is the whole game. A best value award is defended with the solicitation written before proposals arrived and the evaluation record built while scoring them. If the basis of award is vague, every explanation offered afterward reads as a rationalization, however sound the decision was.

Sealed bids and sealed proposals are different instruments

Most codes distinguish competitive sealed bidding from competitive sealed proposals. Sealed bidding assumes the agency can describe exactly what it wants, so the only open question is price, and award goes to the lowest responsive bid from a responsible bidder. Responsiveness is conformance to the invitation; responsibility is capacity to perform. Neither is a quality comparison.

Competitive sealed proposals exist for what sealed bidding handles badly, including most software and services buys, where the how matters as much as the what. Award goes to the proposal most advantageous to the agency under the criteria stated in the request. Terminology varies by jurisdiction, so confirm what your code authorizes.

The award methods and what each one commits you to

• Low bid. You buy whatever meets the specification at the lowest price. Every quality judgment has to live in the specification, written as pass or fail.
• Lowest priced technically acceptable. You set a floor, rate each proposal acceptable or not, and award to the lowest priced acceptable proposal. This commits you to ignoring superiority above the floor: if a proposal is far better than acceptable, you cannot pay more for it. Use it only when acceptable can be defined precisely.
• Points plus price. You publish weighted factors, score proposals, convert price to points by a stated formula, and add. This commits you to arithmetic: the weights and the price formula decide the outcome, and an unexamined formula can let a small price difference swamp a large capability difference. Model it against plausible price spreads before publishing.
• Trade-off. You rate qualitative factors, then judge whether the advantages of a higher rated proposal are worth the premium. The most room for professional discretion, and the most documentation required.
• Qualifications based selection. Selection on qualifications, with price negotiated after. Many states limit this to design and engineering services, so check whether your code allows it here.

Stating the basis of award so it holds

Write the award section as though a hearing officer will read only that page. State:

• The evaluation factors and subfactors, in the words your scoring sheets will use.
• Their relative importance, and whether all non price factors combined are more important than, equal to, or less important than price.
• Whether the agency may award to other than the lowest priced proposal, said plainly.
• How price will be evaluated: total value over a defined term, option years, implementation and transition, and the assumptions offerors must use so prices are comparable.
• For a scoring method, the formula and points available. For an acceptability method, what makes a proposal unacceptable.
• Whether the agency may award without discussions.

Then hold the line. Evaluators cannot introduce a factor that is not in the solicitation, and cannot quietly reweight one that is.

Documenting why the higher price was the better value

A defensible trade-off record is comparative, not descriptive. Summaries of each proposal are not a decision. The record should name the specific advantages of the selected proposal over the next lower priced one, tie each to solicitation language, and say why they justify the difference in concrete terms: fewer interfaces to build, a migration path that avoids a parallel run, accessibility conformance already demonstrated.

Address the delta directly. Say what the premium buys, and what the cheaper path would likely cost in staff time, extended timelines, or deferred work. Avoid invented figures: a clear qualitative comparison signed by the award authority is stronger than a fabricated savings estimate. Retain evaluator notes, consensus documentation, and any changed scores with the reasons they changed.

Briefing a council or board on a decision that was not the cheapest

Elected officials are approving a contract, not re evaluating proposals. Give them the decision structure rather than a defense:

1. What the agency is buying and why the requirement exists.
2. The method of award, and that it was published before proposals were received.
3. Who responded and how the evaluation was run.
4. The two or three concrete differences that drove the selection.
5. The cost picture over the full term, including what the price does not include.

Say the price difference out loud early; officials react badly to a number that first surfaces during public comment. Expect the question of whether the low proposer could have done the job, and answer it against the stated criteria, not with opinions about the vendor.

Before you release the solicitation

• Run the scoring formula against sample prices and confirm the result matches your intent.
• Confirm each factor can be evaluated from the material you are requesting.
• Decide who the award authority is and who signs the determination.
• Review the disclosure and retention rules for evaluation material with counsel, and give evaluators written instructions on what is and is not a permissible consideration.

HQT works with state and local agencies on technology requirements, evaluation criteria, and the technical documentation that supports procurement decisions of this kind.

Frequently asked questions