The RFP Evaluation Committee: Roles, Size, Training and Ground Rules

When two evaluators score a proposal the same way

A committee chair opens the scoresheets the night before the consensus meeting. Two evaluators have scored the same proposal almost identically, down to the same ratings on six criteria. One of them sits next to the other in the office. Nobody has done anything wrong that the chair can point to, but she cannot say with confidence how those scores came about, and she has nothing in the file that would let her say so later.

Situations like this are rarely about bad faith. They come from committees that were assembled quickly, briefed informally and never given written ground rules. When a monitor, an auditor or an unsuccessful offeror asks how the selection was made, the committee's own record is the answer.

This guide explains who belongs on an RFP evaluation committee, how to think about its size, what orientation should cover, and what the chair should write down before anyone scores anything. After reading it, you will be able to show how your committee was formed and governed.

What the rules ask of an RFP evaluation committee

Federal procurement rules say little about committee structure. They say a good deal about what the file must show. Under 2 CFR 200.318(a), a recipient or subrecipient spending a federal award must have documented procurement procedures, consistent with state, local and tribal law and with 2 CFR 200.317 through 200.327. Your committee's ground rules should sit inside those procedures, not beside them.

For competitive proposals, 2 CFR 200.320(b)(2)(i) requires the solicitation to identify all evaluation factors and their relative importance. Section 200.320(b)(2)(ii) requires written procedures for conducting technical evaluations and making selections. The committee is the body that carries out those procedures, so its members need to know what they say.

Two other provisions bear directly on who may serve. Under 2 CFR 200.318(c)(1), no employee, officer, agent or board member with a real or apparent conflict of interest may take part in selecting, awarding or administering a contract supported by the federal award. The same section requires written standards of conduct covering conflicts of interest. This guide reflects the current text of 2 CFR Part 200, as revised effective October 1, 2024.

Finally, 2 CFR 200.318(i) requires records detailed enough to show the history of the procurement. That includes the rationale for the method, the contract type, the selection or rejection of contractors and the basis for the price. A committee roster, signed attestations and a written scoring plan are part of how that history gets reconstructed.

State and local codes may be stricter than the federal rules. When both apply, follow the stricter one, and confirm how a requirement applies to your award with the awarding agency or pass-through entity.

Roles on an RFP evaluation committee: scoring, advisory and chair

Most confusion about committees comes from blurred roles. A short written description of each role, approved before the solicitation closes, removes most of it. Here are the roles that small organizations commonly use.

Scoring evaluators

Scoring evaluators rate each proposal against the published criteria and submit their own scores independently. Their scores are the numbers that feed the ranking. Each one should be someone who understands the subject matter, has no conflict of interest and can commit the time to read every proposal in full.

Advisory members

Advisory members contribute expertise without scoring. A legal reviewer might answer questions about contract terms. A finance reviewer might check an offeror's cost build-up. An IT specialist might clarify a technical point. Keeping these people out of the scoring pool is a deliberate choice, and the file should say so. If an advisor's view influences the committee, record what was asked and what was answered.

The chair

The chair runs the process. The chair convenes orientation, enforces the ground rules, manages the schedule, facilitates the consensus meeting and makes sure rationales are written down. A chair may or may not score. If the chair scores, the file should show that the role does not give the chair's scores extra weight or let the chair see others' scores early. Many organizations separate the roles to keep the facilitation neutral.

The procurement contact

One person should handle all communication with offerors during the solicitation. Evaluators should not field questions from offerors, and offerors should not know who is on the committee until the organization decides to disclose it. Write this down as a rule, and record the contact's name.

Observers and support staff

Some organizations allow a note-taker, an observer from the pass-through entity or an intern. Decide in advance whether such people may attend the consensus meeting, whether they may speak and whether they sign the same confidentiality statement. An unexplained extra person in a consensus meeting is a question waiting to be asked later.

How many evaluators an RFP committee needs

There is no federal rule that fixes the number of evaluators on a committee, and this guide does not cite one. What follows are practice considerations, and your own written procedures and any state or local requirements come first.

Enough to cover the subject matter. A committee should collectively understand what is being bought. If the proposals address both program design and financial management, someone on the committee should be able to judge each.

Enough that one person's view does not dominate. A single evaluator is a single point of challenge. With very few scorers, one outlier can swing the ranking, and one conflict discovered late can undo the whole evaluation. Several scoring evaluators spread that risk.

Few enough to schedule and to discuss. Every added evaluator must read every proposal and attend the consensus meeting. Large committees tend to lose members mid-process, and a lost evaluator can leave the file with uneven scoring across proposals.

An odd number is convenient, not required. Odd numbers can make disagreements easier to resolve in discussion, but consensus scoring is not a vote. What matters is that your procedures say how final scores are reached. See the guide to consensus scoring for how that step is documented.

Plan for absence. Decide in advance what happens if an evaluator withdraws after reading some proposals. Options include removing that evaluator's scores for all proposals, or appointing a replacement who reads everything. Whichever you choose, record the decision and the reason before it happens, not after.

Whatever size you choose, write down why. A sentence such as "five scoring evaluators were appointed to cover program, finance and operations expertise, with two advisory members" is enough to show the choice was deliberate.

Conflict of interest and confidentiality before anyone scores

Under 2 CFR 200.318(c), a real or apparent conflict of interest bars participation in the selection of a contract supported by the federal award. The word "apparent" matters. A conflict does not have to result in a biased score to put the award at risk. A former employer, a family tie to an offeror's staff or a shared board seat can all raise the question.

The practical step is a written attestation, signed by each member before they see any proposal. A good form asks each person to disclose financial interests, family relationships, current or recent employment, board service and any other relationship with each offeror. It should also give a path for disclosing a conflict that surfaces later, once the offeror list is known. The evaluator conflict-of-interest form guide walks through what such a form should contain.

Treat the attestation as a gate. If the form is not on file, the person does not receive proposals. Where the offeror list is known only at the deadline, have members attest again, or confirm in writing, once names are available. The chair should review the forms and record any decision about a disclosed relationship, including a decision to excuse the member.

Confidentiality belongs in the same step. Members should agree in writing not to discuss proposals with anyone outside the committee, not to share scoring materials and not to contact offerors. Include a rule for what to do if an offeror contacts a member: do not respond, and report it to the procurement contact.

Orientation, training and a calibration round

Evaluators who have never seen the criteria used the way the committee will use them tend to score differently from one another. Orientation reduces that, and it creates a record that every member received the same instructions.

What orientation should cover

A short session before scoring begins can cover the following:

• the scope of the solicitation and the evaluation criteria, with their stated weights;
• the rating scale and what each rating point means;
• the schedule, including when scores are due and when consensus will meet;
• conflict-of-interest and confidentiality rules;
• the rule that scoring is independent and that members do not compare scores before everyone has finished;
• what to do with questions about the solicitation, which go to the procurement contact;
• how to write a useful comment, tied to the proposal's content rather than to a general impression.

Record who attended, the date and the materials distributed. If someone could not attend, record how they were briefed.

Why the rating scale matters

A criterion weighted at 25 percent means little if one evaluator treats "meets requirements" as a strong rating and another treats it as a middling one. Rating definitions should be written and fixed before scoring starts, so every evaluator reads the same scale. The article on rating scale definitions explains how to write anchors that evaluators can apply consistently.

A calibration round

A calibration round is a practice exercise. Each evaluator scores a sample, such as a short fictional proposal or a redacted excerpt from a past solicitation, using the actual criteria and scale. The group then compares results and discusses where interpretations differed. The aim is to find disagreements about the scale, not about the live proposals.

Keep the calibration material separate from the real evaluation. Do not use any actual offeror's content, and do not carry calibration scores into the ranking. Record that the exercise took place and what clarifications resulted, for example, "the group agreed that a rating of 3 requires the proposal to address every listed requirement." If the clarification changes the meaning of a rating, update the written definition before scoring opens rather than relying on memory.

What the chair should record before the first score

The chair's pre-scoring record is short, and it answers most questions that arise later. A practical list:

1. The committee roster. Names, titles, and whether each person is a scoring evaluator, an advisory member or the chair.
2. The reason for the composition. A sentence on expertise covered and why the number of scorers was chosen.
3. Signed conflict-of-interest attestations and any decision about a disclosed relationship.
4. Signed confidentiality statements.
5. The evaluation criteria, weights and rating definitions as published and as fixed for scoring. Under 2 CFR 200.320(b)(2)(i), the solicitation must identify all evaluation factors and their relative importance, so the committee's version should match the published one.
6. The written evaluation procedure, or a reference to it, as required by 2 CFR 200.320(b)(2)(ii).
7. The independence rule, stating that members score alone and do not see one another's scores until the round closes. See the discussion of scoring independence for why this protects the file.
8. The tie rule, chosen before any proposal is scored.
9. The schedule, including orientation, the calibration round, the scoring deadline and the consensus meeting.
10. The orientation record, with attendees, date and materials.

Date and sign this record. If something changes mid-process, such as a member stepping down or a criterion clarification, add a dated entry rather than editing the original.

The point of the list is reconstruction. A reviewer reading the file months later should be able to see who was on the committee, what each person had agreed to, what rules governed the scoring and in what order things happened. That is the history 2 CFR 200.318(i) asks the file to show.

If a protest or dispute arises, 2 CFR 200.318(k) leaves source evaluation, protests, disputes and claims with the recipient or subrecipient. Your committee records are then the material you have to work with. Local protest and debrief procedures are set by your own policy, so check yours.

Putting ground rules into practice

Start with a one-page committee charter. It should name the roles, state the independence and confidentiality rules, describe how absences and late conflicts will be handled and say who answers questions. Have each member sign it at orientation, and file it with the attestations.

Next, build the schedule backward from the proposal due date. Allow time for orientation, a calibration round, reading and independent scoring, and a consensus meeting that is long enough to discuss the criteria where scores diverged. Short schedules push committees to skip calibration and shorten discussion, which are the two steps that most improve consistency.

Finally, keep the record in one place. Rosters, attestations, orientation notes and the schedule are far easier to produce when they were filed together from the start than when they must be gathered from email threads.

For organizations that want a structured way to plan this, the Solicitation Timeline and Evaluation Committee Planner is designed to record committee roster and roles, key dates and the pre-scoring checklist in one workbook. It is available in the store now. For the broader sequence from solicitation to award file, see the RFP evaluation process guide. To hear when the evaluation workspace opens, join the waitlist. Plans are described on the pricing page.

Your state or local procurement rules, your pass-through entity's requirements and your own written procedures set the committee rules that apply to you. Confirm specifics with the awarding agency, the pass-through entity or your counsel.

RFPManagement records and computes. It does not give legal or procurement advice. The award decision stays with your organization.