Who Should Be on Your RFP Evaluation Committee (and Who Shouldn't)

Most RFP evaluation committees fail in one of two ways.

The first: one person decides. They circulate a summary, collect a few opinions, and call it a committee. The process is fast but the outcome is fragile. If that decision gets challenged, there is no defensible record of how the selection was made.

The second: ten people are invited to review submissions. Half of them have not read the RFP. Two of them want different vendors for reasons unrelated to the evaluation criteria. Nothing gets decided without a meeting, and the meeting produces more questions than answers.

The right structure is neither of these. Here is how to build an RFP scoring committee that moves fast, evaluates fairly, and produces decisions you can stand behind.

The right size: 3 to 5 people

Three to five evaluators is the functional range for most RFPs. Below three, you lose the diversity of perspective that makes committee scoring meaningful. Above five, decision friction increases faster than decision quality.

For straightforward vendor selections, three evaluators with clearly defined roles is often enough. For high-stakes, high-complexity procurements, four or five gives you more scoring redundancy and makes it easier to identify and investigate outlier scores.

The goal is not representation for its own sake. The goal is having the right perspectives in the room without creating a committee that cannot reach decisions.

The roles that must be represented

The end user. This is the person or team who will actually work with the vendor day to day. They know what good performance looks like in practice, and they know what the daily friction points will be if the vendor falls short. An evaluation committee without an end user produces selections that look good on paper but create problems within the first 90 days.

Finance. Someone needs to evaluate cost proposals with fluency: total cost of ownership, contract structure, payment terms, pricing escalation clauses. Finance also provides discipline on what the organization can actually sustain over the contract period.

IT or security (when applicable). For any procurement involving systems, data, or technical integration, IT and security need to evaluate vendor responses on those dimensions directly. They should score those sections, not just sign off at the end.

The procurement lead. This person owns the process. They manage the scoring rubric, facilitate evaluator calibration, track the timeline, and maintain the audit trail. They may also vote, but their primary role is process integrity.

These four roles cover the evaluation from four different angles: operational, financial, technical, and procedural. Missing any one of them creates a blind spot that shows up later.

The roles that kill objectivity

The person who already has a preferred vendor. They might not disclose it directly. The signal is subtler: they ask pointed questions about one vendor during the Q&A period, they consistently give low scores to competitors without documented rationale, they push the committee toward a decision before scoring is complete. If you know someone has a strong prior relationship with a vendor under evaluation, they should not score that vendor's submission.

Senior executives who have not read the RFP. Executive involvement in procurement decisions is legitimate. Executive involvement in evaluation committee scoring is usually not. A senior leader who joins the evaluation without reviewing the original requirements, without reading the vendor responses, and without scoring against the rubric will introduce authority bias. Their opinion carries disproportionate weight because of their role, not because of the quality of their evaluation. Keep executives in the approval chain, not the scoring committee.

Anyone with a financial relationship to a vendor under evaluation. This one is obvious but frequently unexamined. Conflict of interest disclosures should happen before the committee is finalized, not after scoring is complete.

How to manage conflict within the committee

Score variance is normal. Score variance without rationale is a problem.

Before evaluation begins, run a calibration session. Have every evaluator independently score the same sample response, then compare. Discuss where scores diverged and why. This surfaces different interpretations of the criteria before they become disagreements about vendor selections.

When final scores diverge significantly, require written rationale before the scores are debated. This prevents the loudest voice in the room from pulling scores toward their position. The rationale should reference the content of the vendor's response, not the evaluator's general impression of the vendor.

If evaluators cannot reconcile a significant variance after discussion, escalate to the procurement lead. In persistent cases, a fourth evaluator may be added to break ties, but this should be rare.

How to weight committee member scores

Not all evaluators have equal expertise across all sections. The end user should carry more weight on operational questions. IT carries more weight on security and integration questions. Finance carries more weight on pricing and contract structure.

The simplest approach: define which evaluators score which sections, and total the scores by section rather than by evaluator. This avoids the problem of an evaluator scoring heavily on a section outside their expertise.

An alternative: give each evaluator a scoring weight based on their role relevance, applied per section. More work to set up, but more precise for complex procurements.

Whatever weighting approach you use, document it before scoring begins. A weighting scheme you construct after you see the scores is not a weighting scheme. It is rationalization.

What an RFP scoring committee process looks like end to end

1. Define the committee roster and confirm conflict-of-interest disclosures before the RFP is issued.
2. Share the scoring rubric with evaluators before vendor responses arrive.
3. Run a calibration exercise with a sample response.
4. Score individually, asynchronously, with written rationale for each score.
5. Aggregate scores and identify significant variances.
6. Discuss variances with reference to vendor response content.
7. Finalize scores and document the outcome.

The documentation at step seven is not optional. If your procurement decision is ever challenged, the committee's scoring records are your defense. If those records do not exist, you are defending a decision with no paper trail.

Strutter AI manages the full evaluation process: scoring rubric design, committee score aggregation, variance flagging, and audit trail documentation. Start free at rfp.strutterai.com.