Debriefing Unsuccessful Offerors After an RFP: What to Share and What to Record

When the second-ranked offeror asks for a full explanation

A program director at a grant-funded nonprofit opens an email on a Tuesday morning. The offeror ranked second has read the notice of intent to award and wants "a full explanation of how our proposal was scored and why it was not selected." The notice went out four days ago. The director has the committee's consensus minutes in one folder, the individual scoresheets in another, and a general memory of a long meeting.

Several questions arrive at once. How much should the director say, and to whom? Should the answer be a letter or a call? Does the file hold enough to explain the result without improvising? A careless answer can look like favoritism, and an overly guarded one can invite a protest that a plain explanation would have settled.

This guide shows how to prepare a debrief from the evaluation record, decide what to share, and document the conversation so the file shows what was said.

What an RFP debrief for unsuccessful offerors is, and what your rules require

A debrief is a structured explanation of how a proposal was evaluated against the published criteria. It is not a chance to renegotiate scores, accept new information or reconsider the award. Treat it as a description of a decision already made and already recorded.

Federal grant rules do not supply a debrief procedure for recipients. The procurement standards in 2 CFR 200.317 through 200.327 set requirements for procedures, methods and records, but they do not mention debriefs or prescribe a format for one. A debrief is good practice, and it may be required by your own policy or by state or local law. Your awarding agency's award terms can also add expectations, so check them. Your own written procurement policy, any state or local procurement code, and your public-records law usually govern whether a debrief is offered, when, and in what form.

The federal rules do put the burden on the issuer. Under 2 CFR 200.318(k), the recipient or subrecipient "is responsible for the settlement of all contractual and administrative issues arising out of its procurement transactions." The text continues:

"These issues include, but are not limited to, source evaluation, protests, disputes, and claims."

The section does not say how protests must be handled or require written protest procedures. That is left to your own policy and to state or local law.

A debrief often comes before any formal protest, so it is a practical place to show that the evaluation followed a consistent method. For more on how the protest side works, see our overview of 2 CFR 200.318(k) and protests for grant recipients.

Prepare from the consensus record, not from memory

Debriefs go wrong when the person speaking reconstructs the evaluation from recollection. The better source is the consensus record, which should already hold the final score on each criterion and the reason for it. If the record has only totals, the debrief will be thin, and the gap is worth fixing for the next solicitation. Our guide to consensus scoring in an RFP covers how to capture that rationale at the time.

Before any letter or meeting, assemble a short preparation file:

• the solicitation as issued, including the evaluation factors and their stated relative importance, which 2 CFR 200.320(b)(2)(i) requires the RFP to identify;
• the rating definitions or anchors the committee used;
• the unsuccessful offeror's final consensus score and rationale for each criterion;
• the responsiveness determination for that proposal;
• the award memo or selection memo, and the date of the notice of intent to award;
• your written debrief and protest procedures, if you have them.

Read the offeror's proposal against its own consensus rationale. A debrief should be able to say, criterion by criterion, "the committee rated this section at this level because of these features of the proposal." If you cannot say that from the record, do not fill the gap with opinion. Note the gap and decide with your counsel or procurement lead how to respond.

RFPManagement is designed to hold the final score and a required written rationale for each criterion in one consensus record. That puts the material a debrief draws on in a single place. Whatever you use, the principle is the same: the explanation comes from what the committee recorded, not from what someone remembers afterward.

What to share and what to hold back

Policies and public-records laws differ, so treat the lists below as a starting frame for a conversation with your counsel, not as a rule. The aim is to explain the offeror's own evaluation fully, and to avoid disclosing other offerors' protected information or inviting a point-by-point rebuttal.

Usually appropriate to share

• the published criteria, weights and rating definitions, which were already in the solicitation;
• the offeror's own score and consensus rationale on each criterion, in plain language;
• the strengths and weaknesses the committee identified in the offeror's proposal, tied to those criteria;
• the offeror's overall ranking, if your policy allows it;
• the selected offeror's name and the award amount, where your policy or public-records law makes them public.

Usually handled with care

• other offerors' proposals, pricing details and proprietary content, which are generally not shared in a debrief;
• individual evaluator scoresheets and evaluator identities, where your policy or public-records law may call for a specific approach;
• side-by-side comparisons that disclose another offeror's proposal content;
• any statement that suggests the award is open to change.

If a request goes beyond what your policy covers, you can say that you will confirm what can be released and respond in writing. That is a complete answer, and it is better than an improvised one. Public-records requests are a separate track from debriefs, so confirm with counsel how your jurisdiction treats scoresheets and proposals after award.

Keep the tone factual. Describe how the committee applied the criteria, and avoid language about the offeror's quality that the record does not support.

Writing the letter or running the meeting

Many issuers use a written notice first, then offer a meeting or call on request. Your policy may fix this sequence. The notice of intent to award, or the unsuccessful bidder letter that accompanies it, commonly states the outcome, the selected offeror, how to request a debrief, and any protest procedure and deadline set by your local policy. Do not copy deadlines from another entity's template. State only the ones your own policy sets.

For a written response, a workable structure is:

1. State the outcome and the date of the decision.
2. Restate the criteria and weights from the solicitation.
3. Summarize the offeror's consensus ratings with the main reasons, criterion by criterion.
4. Point to the procedure and contact for any further questions or formal protest.

For a meeting, a short agenda keeps it on track. Open by stating its purpose and that the award decision is not being reconsidered. Have one person speak, with a second person taking notes. Walk through the criteria in the order of the solicitation, listen to questions, and answer from the record. If a question calls for information you do not have in front of you, say you will follow up in writing rather than guess.

Watch for a moment when a debrief turns into a protest. If an offeror says the evaluation was biased, that a criterion was misapplied, or that a conflict existed, stop and acknowledge the concern. Then refer the offeror to your written protest procedure and note the exchange. Our guide to bid protest procedure for local governments explains how to think about that handoff, and local procedure governs.

For context on where evaluation records get challenged, GAO's FY2025 bid protest report names the most prevalent reasons for sustaining protests that year: unreasonable technical evaluation, unreasonable cost or price evaluation, and unreasonable rejection of a proposal. Those are federal agency procurements only, not grant-recipient or local procurements. They still show why a debrief should track the criteria in the solicitation. Source: GAO Bid Protest Annual Report to Congress for Fiscal Year 2025, GAO-26-900695, December 12, 2025.

What to record about the debrief

The debrief itself becomes part of the procurement file. Under 2 CFR 200.318(i), records must be detailed enough to show the history of the procurement, including the rationale for the method, the contract type, the selection or rejection of the contractor, and the basis for the price. A debrief is not one of those four elements, but a note of it sits naturally beside them and helps show that the explanation matched the record.

A short debrief entry usually includes:

• who requested the debrief, on what date, and by what means;
• the date, format and attendees on both sides;
• the materials shared, such as the criteria, the offeror's consensus ratings and any letter sent;
• the questions the offeror asked and a summary of the answers;
• any commitment to follow up, and the date it was fulfilled;
• any statement that sounded like a protest, and the referral made;
• confirmation that scores and award documents were not changed afterward.

The last item matters. If a debrief prompts a real error to surface, the correction should come through your documented process, with its own entry and reason, never through a quiet edit to earlier records. Our guide to RFP evaluation documentation describes how the full file fits together, and the RFP award memo is the record the debrief most often refers back to.

Keep the entry with the rest of the file. Under 2 CFR 200.334, federal-award records are generally kept three years from the final financial report, unless an exception applies, and local public-records rules may require longer. Confirm the current text at eCFR, and confirm with your awarding agency or pass-through entity how it applies to your award.

Setting up the next debrief before it is requested

The easiest debrief is the one the file was built for. Before your next solicitation, decide a few things in advance: whether you offer debriefs, who conducts them, what the notice of intent to award will say, and where the debrief entry will live. Write those into your procurement procedures, which 2 CFR 200.318(a) requires you to document in any case. Then ask each evaluation committee to write a rationale for every final score at the time of consensus, so the debrief has something to draw on.

The Award Documentation Kit is a store kit designed to track conflict-of-interest attestations, assemble the inputs for the selection memo, and score debrief and protest-file checklists for completeness. It includes Word forms for the attestation, the selection memo and a debrief letter. It is available in the store now. See the Award Documentation Kit page for what it is designed to record.

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