Topic I-10 — Negotiated Acquisitions

Debriefing Unsuccessful Offerors

Transparency prevents protests. Your award decision should be so well documented that giving a full debriefing is easy. This training covers the FAR minimums, the KTHQ standard, and what a defensible debriefing looks like.

1 The Core Philosophy

Start here: A large share of the protests you will encounter trace back to a debriefing that did not give the contractor a clear picture of how the evaluation was conducted or why the award decision came out the way it did. Contractors file protests when they do not understand why they lost and suspect something was done wrong.

Debriefings exist to close that gap. FAR 15.506(d) sets the minimum content a debriefing must include. At KTHQ we aim well above that minimum. Full transparency about how the evaluation was conducted and why the award went where it did is the most effective protest-prevention tool available to you.

Many contracting officers get this backwards. They treat debriefings as a legal exposure to be minimized. They hedge, they stay vague, they disclose as little as possible. The theory is that less information means less ammunition for a protest. In practice, it works the other way around. Vague debriefings are what drive contractors to file protests, because the only way to force the government to show its work is through the GAO protest process.

Give contractors the information up front. If the evaluation was conducted properly and the award decision was sound, transparency costs you nothing and saves the government the cost and disruption of a protest.

The KTHQ Standard Your award decision document should be so well written that you could redact the proprietary information and offeror names, hand what is left to the public, and feel no shame. If you could not comfortably do that, the fix lives in the decision document itself, not in how much you withhold during the debriefing.

2 Pre-Award vs. Post-Award Debriefings

The FAR recognizes two types of debriefings for negotiated acquisitions conducted under FAR Part 15.

Pre-award debriefings (FAR 15.505) apply when an offeror is excluded from the competitive range before award, or otherwise excluded from the competition before award. The offeror has three calendar days from receipt of the exclusion notice to submit a written request for a pre-award debriefing. If the request is timely, the CO must provide a debriefing, typically before award.

Post-award debriefings (FAR 15.506) apply to offerors who received a proposal in the competitive range but were not awarded the contract. The offeror has three calendar days from receipt of notification of award (or from the unsuccessful offeror letter) to submit a written request. If the request is timely, the CO must provide a debriefing.

The content requirements differ. Pre-award debriefings are narrower because they happen before the source selection is complete. Post-award debriefings cover the full evaluation and award decision.

TypeFAR ReferenceWhenKey Limitation
Pre-award FAR 15.505 After exclusion from competitive range, before award Cannot reveal information about other offerors. Focused on the reasons this offeror was excluded.
Post-award FAR 15.506 After award, upon timely request May discuss the awardee's proposal at a higher level, but still protects proprietary and source selection information.
Timeliness matters. If the offeror's request is not received within three calendar days, the CO is not required to provide a debriefing under FAR 15.505 or 15.506. The CO may still choose to provide one as a matter of practice. At KTHQ, we generally will. The goal is transparency, not gatekeeping.

3 What a Post-Award Debriefing Must Include

FAR 15.506(d) lists the minimum content of a post-award debriefing. At a minimum, the debriefing must include:

Required ContentWhat It Means
Evaluation of significant weaknesses or deficiencies The government's evaluation of the debriefed offeror's proposal, including the significant weaknesses and deficiencies identified.
Overall evaluated cost or price and technical rating The overall evaluated cost or price and technical rating of the successful offeror and the debriefed offeror, and past performance information on the debriefed offeror.
Overall ranking of all offerors If a ranking was developed during the source selection, provide the overall ranking of all offerors.
Summary of the rationale for award A summary of the rationale for the award decision. This is the heart of the debriefing.
Make and model of the awarded commercial item For acquisitions of commercial items, the make and model of the item being delivered by the successful offeror.
Reasonable responses to relevant questions Reasonable responses to relevant questions about whether source selection procedures contained in the solicitation, applicable regulations, and other applicable authorities were followed.

Notice what is on this list. Your obligation is not just to recite ratings. You must explain the rationale for the award decision and answer questions about whether the source selection was conducted properly. That is a substantive obligation, not a procedural one.


4 What You Cannot Disclose

Transparency has limits, and those limits exist for good reasons. FAR 15.506(e) prohibits certain disclosures in a debriefing. The debriefing shall not include:

Point-by-point comparisons with other offerors. You do not walk through another offeror's evaluation side by side with the debriefed offeror's evaluation. You can discuss the relative standing and the award rationale, but not a line-by-line comparison.

Information exempt from release under the Freedom of Information Act. This includes another offeror's trade secrets, privileged or confidential manufacturing processes and techniques, and commercial and financial information that is privileged or confidential. It also includes the names of individuals providing reference information about an offeror's past performance.

If a contractor asks a question during the debriefing that would require you to disclose protected information, explain the specific restriction, point to FAR 15.506(e), and move on. Experienced contractors understand these limits and will not push further once the basis is clear.

The prohibited disclosures are narrow. The rule does not say "anything that might embarrass the government" or "anything that might expose a weakness in the evaluation." It protects proprietary information belonging to other offerors. Everything else is fair game if it illuminates the award decision, and most of the time you should share it.

5 Going Beyond the Minimum

The FAR lists what a debriefing must contain. It does not limit what a debriefing may contain, as long as the disclosures in section 4 above are respected. This is where the KTHQ standard differs from the minimum.

A minimum-compliant debriefing recites ratings and asserts a rationale. A good debriefing explains reasoning. The difference looks like this:

MinimumKTHQ Standard
"Your Technical Approach was rated Acceptable." "Your Technical Approach was rated Acceptable. The evaluators found your ticket intake and triage process met the PWS requirement, and no weaknesses were identified. The awardee received an Outstanding rating because their proposal included an automated routing system that reduced initial response time below the required threshold, which the evaluators determined exceeded the requirement in a manner beneficial to the government."
"Your price was higher than the awardee's." "Your total evaluated price was $4.8M. The awardee's total evaluated price was $4.2M. In the best value tradeoff analysis, the Source Selection Authority determined that the awardee's Outstanding technical rating combined with the lower price represented the best value, and that your Acceptable rating did not justify paying the price premium."
"The award decision was made in accordance with the solicitation." "The Source Selection Decision Document reflects that the SSA considered all three non-price factors and price, applied the adjectival rating scale defined in Section M, and determined that the awardee's proposal represented the best value in accordance with the Section M.4 tradeoff analysis. A specific finding was made that the technical superiority of the awardee's proposal in Factor 1 justified paying the price premium."

Every sentence in the KTHQ column refers to something that already exists in your source selection record. If the record is solid, you are not making anything up. You are quoting your own decision document in plain language.


6 Format: Written, Oral, or Both

FAR 15.506(b) says debriefings may be done orally, in writing, or by any other method acceptable to the CO. There is no required format. The CO decides.

In practice, most COs provide a written debriefing letter, and some offerors follow up with questions by phone or email. Some offerors prefer a phone call or teleconference because it allows them to ask follow-up questions in real time. Either approach works. Offer what serves the offeror's understanding.

If you do an oral debriefing, document it. Note the date, the attendees, the topics covered, and the questions asked. That documentation becomes part of the contract file and supports the record if a protest is later filed.

If you provide a written debriefing and the offeror asks follow-up questions, answer them in writing when possible. Written answers create a clear record and reduce the chance of misinterpretation.

Close the debriefing formally. Once you have delivered the debriefing and answered any follow-up questions within the window you specified, send a short closing note stating that the debriefing is concluded and no further questions will be entertained. Leaving the debriefing open-ended confuses contractors about whether they can keep asking, and it muddies the protest clock. A clear termination protects both sides. For DoD acquisitions subject to the enhanced debriefing process, the debriefing is not considered concluded until you have responded in writing to the two-day follow-up questions, so the protest clock is tied to that formal close.

7 When a Contractor Finds a Mistake

It happens. You give a thorough debriefing, the contractor reads it carefully, and they come back with a question that reveals an error in the evaluation. Maybe a weakness was assessed based on a misread of their proposal. Maybe a factor was scored against criteria that were not in Section M. Maybe the arithmetic in the tradeoff analysis was wrong.

Take it seriously, check the record, and if the contractor is right, correct it. That may mean re-opening the evaluation, reconsidering the award decision, or in some cases taking corrective action to cure the defect. The debriefing process exists in part to catch errors before they become sustained protest grounds, and a contractor who flags one during the debriefing is doing you a favor compared to a contractor who sits on the same information and files a protest three weeks later.

Document whatever you find, whatever you correct, and whatever you communicate back to the contractor. That record becomes part of the contract file.

A defensive posture during debriefings tends to be self-defeating. Contractors who sense that the CO is trying to protect the record from scrutiny often conclude that there is something to hide, which pushes them toward filing a protest so they can see the record anyway.

8 DoD Enhanced Debriefings

If you are a DoD contracting officer, you have an additional set of rules to follow. Section 818 of the FY2018 National Defense Authorization Act created the DoD enhanced debriefing process, implemented in DFARS 215.506-70. The key features:

Written responses to follow-up questions. For DoD acquisitions over certain thresholds, the offeror may submit additional written questions within two business days after receiving the post-award debriefing. The CO must respond in writing within five business days.

Extended timeline for protest filing. The protest clock is paused until the CO delivers the written responses. This means the debriefing is not considered complete, and the protest window does not start counting down, until the enhanced debriefing process is finished.

Redacted source selection decision document. For contracts above specific dollar thresholds, DoD offerors are entitled to request a redacted version of the source selection decision document. The redactions remove proprietary information but leave the substantive rationale intact.

If you work DoD acquisitions, know these rules. They effectively formalize the KTHQ standard at the department level. The enhanced debriefing process exists because Congress agreed that transparency reduces protests. Outside DoD, the enhanced process is not required, but the underlying principle applies just as well.

Always verify current thresholds and procedures in DFARS 215.506-70 before applying the enhanced debriefing process. The rules have been updated since they were first enacted, and specific dollar thresholds and procedural details may change.

1 The Context

You are the contracting officer on a competitive best-value tradeoff acquisition for IT Help Desk Support Services. Three offerors submitted proposals. The award went to Pinnacle IT Solutions. An unsuccessful offeror, Meridian Technical Services, submitted a timely written request for a post-award debriefing.

Here are the relevant facts from the source selection:

  • Factor 1 (Technical Approach): Pinnacle rated Outstanding. Meridian rated Acceptable. Third offeror rated Unacceptable.
  • Factor 2 (Staffing Plan): Pinnacle rated Acceptable. Meridian rated Acceptable with one weakness (incomplete coverage during shift transitions).
  • Factor 3 (Transition Plan): Pinnacle rated Acceptable. Meridian rated Acceptable.
  • Price: Pinnacle $4.21M. Meridian $4.78M. Third offeror $4.05M.
  • Award rationale: Pinnacle's Outstanding technical rating in Factor 1 (most important factor) combined with the mid-range price made it the best value. Third offeror's lowest price could not overcome the Unacceptable technical rating.

Below you will see two versions of the debriefing letter to Meridian. The first is a minimum-compliant version written by a CO who is afraid of a protest. The second is what the same debriefing looks like at the KTHQ standard.


2 The Bad Debriefing Letter

Read this one carefully. Everything in it is technically permitted by the FAR. Nothing in it is false. And it is almost certainly going to produce a protest.

Debriefing Letter: Minimum-Compliant Version
From: Contracting Officer To: Meridian Technical Services Date: April 9, 2026

Subject: Post-Award Debriefing, Solicitation FA4690-26-R-0042, IT Help Desk Support Services

This letter serves as your post-award debriefing in accordance with FAR 15.506.

Evaluation Results

Your proposal received the following ratings:

Factor 1 (Technical Approach): Acceptable
Factor 2 (Staffing Plan): Acceptable
Factor 3 (Transition Plan): Acceptable
Total Evaluated Price: $4,780,000

Award Information

The contract was awarded to Pinnacle IT Solutions at a total evaluated price of $4,210,000. Pinnacle received the following ratings:

Factor 1 (Technical Approach): Outstanding
Factor 2 (Staffing Plan): Acceptable
Factor 3 (Transition Plan): Acceptable

Rationale

The award was made in accordance with the evaluation criteria set forth in Section M of the solicitation. The Source Selection Authority determined that the awardee's proposal represented the best value to the Government.

This concludes your debriefing. Please direct any questions to the undersigned.

⚠️ No explanation of the weakness. Meridian's Staffing Plan received a weakness for incomplete coverage during shift transitions. The letter does not mention the weakness, does not explain what it was, and does not tie it to a PWS requirement. Meridian has no way to learn from this or understand how their proposal fell short.
⚠️ No explanation of why the awardee was Outstanding. Meridian sees that Pinnacle got Outstanding and they got Acceptable, but they do not know what the evaluators found. They do not know whether it was a better approach, a different tool, a specific process, or something else. This is the single biggest protest driver. Contractors will protest to force the government to explain the difference.
⚠️ The rationale is empty. "The award was made in accordance with the evaluation criteria" is not a rationale. It is a restatement that a decision was made. Meridian learns nothing about how the tradeoff was conducted, whether their Acceptable rating was weighed against the price difference, or why the price premium was justified.
⚠️ No overall ranking. FAR 15.506(d)(5) requires the overall ranking of all offerors, if a ranking was developed. This letter does not provide one. Meridian does not know where they finished relative to the third offeror.
⚠️ Closing without substance. Ending the debriefing is correct; you always want a clear termination. The problem here is that the letter concludes without having actually given the contractor anything to work with. There is no invitation to submit written follow-up questions within a defined window, so the contractor has no mechanism to clarify misunderstandings before being shut out. A good letter invites questions on a short clock and then formally closes.
Why this letter produces protests. Meridian reads this and learns that they lost. They do not learn why. They do not know what their weakness was. They do not know what made Pinnacle's approach Outstanding. They do not know how the tradeoff was conducted. The only way for them to find out is to file a protest and force the agency to produce the record. That is exactly what happens.

3 The Good Debriefing Letter

Here is the same debriefing, written at the KTHQ standard. Every fact comes directly from the source selection record. Nothing is made up. Nothing protected by FAR 15.506(e) is disclosed. And the contractor walks away understanding what happened.

Debriefing Letter: KTHQ Standard
From: Contracting Officer To: Meridian Technical Services Date: April 9, 2026

Subject: Post-Award Debriefing, Solicitation FA4690-26-R-0042, IT Help Desk Support Services

This letter provides your post-award debriefing in accordance with FAR 15.506. We appreciate the time and effort that went into preparing your proposal. The purpose of this debriefing is to give you a clear understanding of how your proposal was evaluated, how the award decision was made, and where your proposal stood relative to the other offerors.

Evaluation Summary

Your proposal received the following ratings under the Section M factors:

Factor 1 (Technical Approach): Acceptable. The evaluators found your tiered support model and escalation procedures met the PWS requirements. Your described approach to ticket intake and triage was assessed as aligned with the performance standards in PWS paragraph 3.2. No strengths or weaknesses were identified under Factor 1.

Factor 2 (Staffing Plan): Acceptable with one weakness. The evaluators identified a weakness related to coverage during shift transitions. Specifically, the proposed staffing schedule showed a 30-minute gap at the 1300 shift change where only one Tier I technician would be on duty, which the evaluators determined could impair the ability to meet the 15-minute initial response requirement in PWS paragraph 3.2 during that window. The rest of your staffing plan met the requirement, which is why the overall rating remained Acceptable.

Factor 3 (Transition Plan): Acceptable. Your 30-day transition plan met the requirement in Section L paragraph L.1(c). The knowledge transfer and system access portions were assessed as adequate.

Total Evaluated Price: $4,780,000. Your price was evaluated for reasonableness and completeness and was determined to be reasonable.

Awardee Information

The contract was awarded to Pinnacle IT Solutions at a total evaluated price of $4,210,000. Pinnacle's ratings were:

Factor 1 (Technical Approach): Outstanding
Factor 2 (Staffing Plan): Acceptable
Factor 3 (Transition Plan): Acceptable

Pinnacle's Outstanding rating in Factor 1 was based on specific proposal content that the evaluators determined exceeded the PWS requirements in a way beneficial to the government. Without disclosing Pinnacle's proprietary approach, we can share that the evaluators identified a strength related to proactive ticket categorization and response time performance that went beyond the 15-minute requirement in PWS paragraph 3.2. That finding was a primary basis for the Outstanding rating.

Overall Ranking

Three proposals were received. The overall ranking was:

1. Pinnacle IT Solutions (Outstanding, Acceptable, Acceptable)
2. Meridian Technical Services (Acceptable, Acceptable, Acceptable)
3. Third offeror (Unacceptable technical rating, lowest price, not eligible for award)

Award Decision Rationale

This was a best-value tradeoff acquisition under Section M.4. The Source Selection Authority considered the non-price factors and price and conducted a tradeoff analysis between your proposal and Pinnacle's. The relevant comparison was:

Pinnacle's technical advantage in Factor 1 (the most important factor) combined with a lower total evaluated price (a price advantage of approximately $570,000, or 12 percent). The SSA determined that Pinnacle's proposal was superior on the most important non-price factor while also being less expensive, which made it the clear best value. No price premium was being paid. The tradeoff was not close.

The third offeror's lower price could not overcome the Unacceptable rating under Factor 1, which per Section M.2 indicates a proposal that fails to meet one or more stated requirements. An Unacceptable proposal is not eligible for award under a best-value tradeoff.

Source Selection Procedures

The source selection was conducted in accordance with the procedures described in Section M of the solicitation, FAR Part 15, and applicable agency supplements. The evaluation team applied the adjectival rating scale defined in Section M.2, and findings were documented against the specific factors in Section M.1. We believe the procedures were followed, but we welcome your questions on this point.

Questions

If you have questions about the evaluation of your proposal or about the award decision, please submit them in writing to the undersigned within two business days of receipt of this letter. We will respond in writing. Our goal is to leave you with a complete understanding of how your proposal was evaluated and why the award went where it did.

Close of Debriefing

Once any timely follow-up questions have been answered in writing, this debriefing will be formally concluded. No additional questions regarding this source selection will be answered after that point. If no follow-up questions are received within the two-business-day window identified above, the debriefing will be considered concluded as of the close of that window.

The weakness is explained. Meridian now knows exactly what the weakness was (30-minute gap at 1300 shift change), why it was assessed as a weakness (tied to the 15-minute response requirement in a specific PWS paragraph), and why it did not drag the rating below Acceptable. They can learn from this on the next procurement.
The awardee's strength is explained at the right level. The letter identifies what the evaluators found in Pinnacle's proposal without disclosing Pinnacle's proprietary approach. "Proactive ticket categorization and response time performance that exceeded the requirement" tells Meridian what kind of content earned the Outstanding rating, without revealing Pinnacle's specific methodology or trade secrets.
The rationale is substantive. Meridian sees that the tradeoff was not a close call. Pinnacle was better technically AND cheaper. There was no price premium to debate. This removes the most common protest hypothesis (that the agency paid a premium for marginal technical gains).
The ranking is provided. FAR 15.506(d)(5) is satisfied. Meridian knows they finished second, and they know the third offeror was eliminated on technical grounds, not on price.
Questions are invited. The last paragraph opens the door for follow-up. If Meridian has lingering concerns, they can raise them directly with the CO instead of filing a protest to force the agency to respond.
Why this letter prevents protests. Meridian reads this and learns what they can improve on next time. They see that the tradeoff decision was straightforward and well documented. They understand the basis for every rating. There is no mystery left for a protest to resolve. If they still think something was done wrong, they can raise it directly. If they do not, they close the file and move on.

Final Note The good letter did not disclose anything the bad letter did not. Pinnacle's prices were already required to be disclosed. The rating comparison was already required. The weakness was already required. The only difference is that the good letter actually explained the information it disclosed. That is the work. That is what prevents protests. That is the KTHQ standard.

Test Your Understanding

For each situation, choose the action most consistent with FAR 15.506 and the philosophy of transparent debriefings.

Question 1 of 5
The Late Request

An unsuccessful offeror submits a written request for a post-award debriefing. The request arrives five calendar days after they received the unsuccessful offeror notification. FAR 15.506 requires the request to be submitted within three calendar days.

What is the correct approach?

Question 2 of 5
The Proprietary Question

During an oral debriefing, the unsuccessful offeror asks: "What software tools is the awardee using? We want to know what made their technical approach different from ours." The awardee's proposal identified a specific proprietary configuration management tool as part of their solution, and the evaluators relied on that tool in finding a strength.

How do you respond?

Question 3 of 5
The Mistake in the Record

During a written debriefing follow-up, the unsuccessful offeror points out that one of their weaknesses was based on a misread of their proposal. You go back to the evaluation and the contract file and confirm they are right. The weakness should not have been assessed. It was not the basis for the award decision (the award would still have gone to the same offeror even without that weakness), but it affected the narrative.

What do you do?

Question 4 of 5
The Rationale Section

You are drafting the rationale section of a debriefing letter. The award was a best-value tradeoff. Which version best reflects the KTHQ standard?

Question 5 of 5
The Point-by-Point Request

The unsuccessful offeror asks you to walk through each section of their technical proposal and explain, paragraph by paragraph, how it compared to the awardee's proposal at the same paragraph. They want a "direct comparison table."

What do you do?