We Fix Broken RFPS

23 September 2026

Your Evaluation Matrix Should Do More Than Add Numbers

Click on image for better resolution

An evaluation matrix should not be the place where good judgment goes to die.

Too often, procurement teams treat the matrix like a glorified calculator: plug in the scores, total the columns, and assume the highest number must equal the best decision. But a strong evaluation matrix does much more than math.

It creates structure, consistency, and—most importantly—a defensible record of how the team got from proposals to selection.

A well-built matrix helps procurement teams:

• Keep evaluators focused on the criteria that actually matter.
• Expose scoring inconsistencies before they become bigger problems.
• Support meaningful consensus discussions instead of “because I gave them a 9.”
• Make executive reporting easier by clearly showing how vendors compared.
• Give vendors better debriefings based on documented evaluation results.

The smartest time to build the matrix is before the RFP hits the street. Evaluation criteria and weighting should already be established, because changing the game after proposals arrive is exactly what a transparent process is designed to avoid.

Once evaluations are complete, scores can be compiled, weighted, and normalized according to the solicitation. The matrix then becomes a tool for identifying differences between evaluators and starting the conversations that matter.

And one more thing: don’t let price hijack the process. If cost dominates the scoring, all those carefully written qualitative criteria may not matter much in the end. Keeping cost below roughly 35% can help preserve the value of qualifications, approach, and performance.

The evaluation matrix is not the decision-maker.

It is a tool that helps your evaluators make—and defend—a better decision.

Because

‘The spreadsheet said so...’

is not a procurement strategy

Building Protest-Resistant Procurements Through Process Discipline

Click on image for better resolution

Bid protests are often treated like legal emergencies that appear after an award. But most protest problems start much earlier—when the procurement process is unclear, inconsistent, poorly documented, or simply not followed.

The strongest protest defense is not a brilliant legal argument. It is a disciplined procurement process.

That starts with one basic rule: say what you are going to do, then do exactly what you said.

If the RFP identifies evaluation criteria, weights, submission requirements, deadlines, or mandatory qualifications, those rules must guide the evaluation. Once proposals arrive is not the time to reinterpret the process, invent new considerations, or apply criteria differently between vendors.

A protest-resistant procurement should also include:

• A source selection plan developed before release
• An evaluation matrix tested with sample data
• Clear documentation connecting scores to proposal content
• Consistent treatment of every offeror
• Meaningful debriefings that explain the evaluation

Documentation matters because a reasonable decision is difficult to defend if the record does not show how the team reached it. Scores alone are not enough. Evaluator comments should connect published requirements, proposal responses, and specific findings.

Debriefings are another important risk-reduction tool. Vendors usually want to know where they performed well, where they fell short, and how the evaluation reached its conclusion. A substantive debriefing can reduce confusion, improve future proposals, and strengthen supplier trust.

The goal is not to eliminate every protest. That is unrealistic.

The goal is to build a procurement so transparent, consistent, and well documented that when someone asks, “Why did you make this decision?” the agency can clearly show the answer.

Say what you’ll do. Do what you said. Document all of it.

A defensible award begins with a defensible process.