Debriefing unsuccessful proposers after a technology award

Reference article · 5 min read

When a technology award is announced, the firms that did not win will want to know why. Some ask politely, some ask through counsel, and some file a protest first. A debrief is the agency's chance to answer on its own terms: in a controlled setting, from a prepared record, and within the limits public records law imposes.

Agencies sometimes treat debriefs as a hazard to be minimized, on the theory that saying less invites fewer challenges. Offices that run disciplined debriefs tend to find the opposite. A proposer given a specific account of how its own proposal was scored usually concludes the evaluation was rational. A proposer given a form letter and a closed door often concludes that something went wrong, and that a protest is the only way to find out what.

Know what your jurisdiction actually requires

Debriefing obligations are not uniform. They come from state procurement codes, local ordinances, administrative rules, and sometimes only from the solicitation's own terms. Some jurisdictions require a debrief on written request within a stated window after award. Others are silent and leave it to agency policy. Federal negotiated procurements follow their own rules, which do not automatically carry over to state and local buys. Requirements change, so confirm the current text with your procurement code and your counsel before setting expectations with a vendor.

Sort your obligations into three buckets before the first request arrives:

• Required. What statute, ordinance, or rule compels you to provide, to whom, and by when.
• Promised. What the solicitation committed to. A debrief clause in your RFP binds you even if the code is silent.
• Discretionary. What you offer as good practice. Offer it uniformly, because selective generosity is itself a protest ground.

Timing relative to the protest clock

Protest windows at the state and local level are often short, sometimes counted in business days from the notice of intent to award. The critical question, often answered only after a dispute begins, is whether requesting a debrief pauses that clock. In many jurisdictions it does not.

• State in the solicitation, and again in writing to each requester, how and when a debrief may be requested and whether it affects any protest deadline.
• Schedule promptly. A debrief delivered after the protest window closes looks like running out the clock, whatever the intent.
• Decide by policy whether you debrief after the notice of intent to award or after execution. Earlier surfaces evaluation errors before the agency is committed; later reduces the chance the session becomes a negotiation.

What you can tell a proposer about its own proposal

The organizing principle is that a proposer is entitled to understand its own result, not to audit everyone else's. Within that boundary, be specific. Vague feedback is what generates follow-up records requests.

• The published criteria and weights, restated exactly as the solicitation stated them.
• The firm's own scores or ratings by factor, including the consensus rating.
• The committee's written findings on that proposal: strengths, weaknesses, deficiencies, and unaddressed requirements, drawn from the consensus record.
• Where the response missed a stated requirement, citing the RFP section and the proposal section.
• How the firm's own price was evaluated: its own figures and the published price formula.
• Award facts that are public record, typically the awardee's name and contract value, as your records law defines them.
• Next steps: how to protest, where to file, and how to make a records request.

What stays out of the room

• Competitors' pricing detail. Build-ups, unit rates, and assumptions from other proposals stay out unless already public under your disclosure rules.
• Other firms' proprietary material. Methodology, architecture, staffing models, and anything marked and accepted as exempt.
• Evaluator identities and individual score sheets. Practice varies, and some jurisdictions treat these as public. Follow your records law, and never attribute a comment to a named evaluator.
• Deliberative material and legal advice. Internal debate, draft scores, and counsel's guidance are not debrief content.
• Comparisons beyond the record. Explain why the proposal scored as it did, not why a competitor was better.
• Anything forward-looking. No commitments about future solicitations and no coaching on the next bid.

Three rules keep a session inside these lines: read from the written record, do not re-evaluate, and do not argue.

Who speaks and how the session runs

Assign roles before the meeting. The procurement officer runs the session and is the only person who speaks about process, timelines, and legal questions. The evaluation chair or one designated evaluator explains technical findings, reading from the consensus narrative. Counsel attends or is available. Program staff may listen, but should not improvise explanations of scoring they did not write.

• Use a written agenda and a fixed time limit.
• Ask for questions in advance, in writing, so answers can be prepared and reviewed.
• When a question cannot be answered on the spot, say so and answer in writing later. Guessing is how improper disclosures happen.
• Keep a record of what was presented, and give every debriefed firm the same format and depth.
• Do not accept documents, revised pricing, or arguments about the award during the session.

Build the capability before you need it

• Put the debrief clause in the solicitation template so every procurement carries the same terms.
• Give clear marking instructions for confidential material so exemption claims are identified at submission, not argued after award.
• Write consensus narratives for an outside reader. Comments legible only to the committee force staff to improvise in the room.
• Build a standing debrief packet: criteria, scores, consensus findings, and protest instructions.

HQT provides software development, cloud, and technology advisory services for United States state and local government, including support for evaluation planning and solicitation documentation.

Frequently asked questions