driftless
Search

Proposal Evaluation

Procurement technique · See it on the map

Runnable here

Scoring the proposals actually received against a set of criteria to compare them fairly.

When to use it

Whenever more than one vendor has submitted a real proposal and you need a defensible way to compare them — especially when a quality-and-cost-based selection method was chosen and more than price is on the table.

When to avoid it

Don't build formal weighted scoring for a purchase where lowest cost was already the chosen method, or where only one vendor responded — there is nothing to compare. And never let the criteria or their weights get set after proposals are already in hand: weights chosen after seeing the submissions aren't evaluation, they're justification for an answer already picked.

Steps

What it produces

Common pitfalls

Worked example

A small manufacturer requests proposals from three packaging vendors and sets weighted criteria in advance — 40% price, 40% sample quality, 20% lead time. After opening the proposals, the evaluator notices the incumbent vendor scores lowest on price but is the personal favourite of the buying committee, and floats reweighting toward relationship history. The evaluation lead rejects the change: the criteria were fixed before proposals were opened, and changing them now would be scoring backward from a preference, not forward from evidence.

Source

Where it comes from: this technique is named by the PMBOK Guide, 6th edition.