Running an evaluation committee: conflicts, confidentiality, records

Reference article · 5 min read

The evaluation committee is where a solicitation either holds together or falls apart. Everything before it is written and reviewable: the requirements, the criteria, the weights. The panel itself is a group of people reading long documents under deadline, forming opinions, and then trying to reconcile them. The rules around that work exist because the record it produces may have to survive a protest, a public records request, and sometimes an audit. Those rules are simple, and easy to skip when the schedule slips.

Seating a panel that covers the work

Aim for a panel that collectively covers every scored dimension and individually has no stake in the outcome. Add a member to fill a real gap in expertise, not to spread political weight.

Cover these areas with practitioners:

The business owner. Program staff who will use the system daily and understand the workflows the requirements describe.
Technical review. Someone who can test architecture, integration, and hosting claims against your environment.
Security and privacy. Especially for systems holding criminal justice, health, tax, or student records, where separate compliance regimes may apply.
Operations and support. Whoever owns the system after go live and can judge maintenance, release practices, and support commitments.

The procurement officer usually facilitates rather than scores, which keeps the person enforcing the process from holding a stake in the result. Define that role before evaluations begin, and name alternates then as well, so a mid evaluation replacement does not leave you explaining what the new member read.

Conflicts of interest: disclose after the names are known

Conflict standards come from state ethics law, local ordinance, and your own procurement code. They differ by jurisdiction and change over time, so confirm the current standard with counsel or your ethics office rather than reusing a form from an older solicitation.

Collect a signed disclosure from every member after proposals are opened and the proposer and subcontractor names are known, since a disclosure asked in the abstract catches very little. Ask about current or former employment with a proposer or named subcontractor, financial interests including those of household members, family and close personal relationships with proposal teams, gifts or hospitality accepted, prior consulting or board service, and any contact from a proposer about this solicitation.

Not every disclosure is disqualifying. What matters is that the agency rather than the member makes the call, that the reasoning is written down, and that similar facts are treated the same way across members. When recusal is warranted, recuse the member from the entire evaluation rather than one proposal, because someone who cannot fairly score one submission cannot fairly rank the others against it.

Confidentiality and the panel's communications

Have each member sign a confidentiality acknowledgment covering the proposals, the scores, and the deliberations. Proposals routinely contain material a vendor has marked proprietary. Your state's public records law, not the marking, determines what is withheld, but the panel should treat such material as sensitive until the agency decides. Practical controls matter more than the signature:

Distribute proposals through a controlled system, not email attachments, and prohibit forwarding to anyone off the panel.
Keep deliberation off personal email and personal devices.
Avoid chat channels and calendar invitations others can read.
Collect working copies, or confirm destruction, when the evaluation closes.

Remind members that informal messages about official business are often records in their own right, whatever device they sit on.

Independent scores first, then consensus

Every member scores independently against the published criteria and weights before hearing anyone else's view. This is the most important structural rule. Panels that discuss first and score afterward converge on whoever spoke first or with the most seniority.

Collect and keep the individual scoresheets before the consensus session. Run the session criterion by criterion rather than proposal by proposal, and ask each member to point to the basis for a score in the proposal text. Consensus means a score the panel can explain, not an arithmetic mean. Averaging hides the fact that two people read the same page differently, which is usually the most useful thing in the room.

An outlier is a signal, not a problem to smooth over. Ask what that member saw. Often they found something the others missed, misread a requirement, or applied a criterion the solicitation did not include. Each is worth knowing, and only one calls for a changed score. A member is also entitled to keep a differing score: record it and move on rather than pressing for conformity.

Written comments and what becomes disclosable

Assume every comment will be read by the losing proposer, by counsel, and possibly by a judge. Tie each observation to the criterion and the document: which requirement, which section, what was missing or strong. Avoid comments about the vendor rather than the proposal, speculation about staffing or finances, reliance on information outside the submission, and anything resembling a joke.

Records practice varies by state, but scoresheets, consensus documentation, and the award recommendation memorandum are frequently disclosable after award. Draft accordingly from the first page rather than sanitizing later, since a scrubbed file invites the question of what was removed.

How to start

Draft criteria and weights before publication, and confirm the panel can apply them.
Seat the panel, name alternates, and put the facilitator's non scoring role in writing.
Hold a kickoff after opening: proposals out, disclosures and acknowledgments in, no contact rule restated.
Score independently, with a firm deadline for individual sheets.
Run consensus criterion by criterion and record the basis for each final score.
Retain scoresheets, notes, disclosures, and the award memorandum under your retention schedule.

HQT works with state and local agencies on the technical side of software procurements, including requirements and scoring criteria.

Frequently asked questions

Who should serve on a proposal evaluation committee?

Seat people who together cover every dimension you are scoring and who individually have no stake in which proposer wins. For a software or systems buy that usually means the program owner, a technical reviewer, someone responsible for security and privacy, and whoever will support the system after go live. The procurement officer typically facilitates the process rather than scoring, and that role should be written down before evaluations begin.

Does a conflict of interest automatically disqualify an evaluator?

Not always. Conflict standards come from state ethics law, local ordinance, and your own procurement code, and they vary by jurisdiction, so confirm the current rule with your counsel or ethics office. The important practice is that the agency, not the evaluator, decides whether a disclosed relationship is disqualifying, that the reasoning is documented, and that similar facts are handled consistently. When recusal is warranted, remove the member from the whole evaluation rather than from one proposal.

Are evaluator scoresheets and written comments public records?

In many states, individual scoresheets, consensus documentation, and the memorandum recommending award become disclosable after award, though timing and exemptions differ by jurisdiction. Confirm how your state's public records law and your retention schedule treat evaluation material before the panel starts writing. The safe practice is to write every comment as though the losing proposer and its counsel will read it, tying each observation to a criterion and to a specific part of the proposal.

Should evaluators score independently before the consensus meeting?

Yes. Independent scoring against the published criteria and weights, completed before anyone hears another member's view, is the structural rule that keeps a consensus session meaningful. Panels that discuss first and score afterward tend to converge on whoever spoke first or holds the most seniority. Collect and retain the individual scoresheets, then hold the consensus session criterion by criterion.

What should we do when one evaluator's score is far from the rest of the panel?

Treat the outlier as information rather than a problem to average away. Ask that member what they saw in the proposal: they may have found something the others missed, misread a requirement, or applied a factor the solicitation did not include. Only the second of those calls for a corrected score. If the member still disagrees after the discussion, record the difference in the consensus documentation instead of pressing for conformity.