How to Request a Post-Award Debrief and Turn It Into Next-Bid Intelligence

What FAR 15.506 Actually Requires

FAR 15.506(a)(1) gives unsuccessful offerors the right to request a debriefing within three business days after the date on which the offeror receives notification of contract award. Miss that window and the agency can still debrief you, but it is no longer required to do so. Your written request should cite FAR 15.506 by name, state the solicitation number, and request the specific elements the regulation mandates: your evaluated unit and extended prices, your technical rating, the overall ranking of all offerors when it was disclosed, a summary of the rationale for award, and reasonable responses to relevant questions.

For task-order competitions under an IDIQ vehicle, the governing clause shifts. FAR 16.505(b)(6) covers task-order debriefs and applies a lighter disclosure standard. Know which clause governs before you draft the request letter, because the information you are entitled to differs materially.

How to Write the Debrief Request

Keep the request short and specific. Address it to the Contracting Officer of Record listed in the award notice. Include the solicitation number, the contract number if one was assigned, your firm's name and CAGE code (a five-character alphanumeric code assigned by the Defense Logistics Agency), and a clear statement that you are requesting a post-award debrief under FAR 15.506. Add a sentence requesting that the debrief be conducted in writing if you prefer a written format, which FAR 15.506(e) permits. Written debriefs are often more useful than oral ones because they produce a document you can analyze without relying on notes.

If you want to maximize the intelligence value, append a short list of specific questions. Permitted questions include: What was the evaluated price of the awardee? What weaknesses or deficiencies were identified in our technical volume? How did our past performance rating compare to the awardee's? Were any significant weaknesses noted in our management approach? Agencies are not required to answer every question, but asking precisely increases the probability of a useful response.

Turning the Debrief Response Into Bid Intelligence

When the debrief arrives, resist the urge to read it as a verdict. Read it as a data set. Structure your analysis around four categories.

1. Price Position

If the agency discloses the awardee's evaluated price, calculate the gap. Determine whether the gap was a function of labor categories, indirect rates, or fee. If your price was higher, identify which cost elements drove it. If your price was lower and you still lost, the issue was almost certainly technical or past performance, and price reduction on the next pursuit will not help you.

2. Technical Weaknesses

Every weakness cited in a debrief maps to a section of the PWS or SOW and to an evaluation factor. Create a simple table: weakness description in one column, the evaluation factor it affected in the second, the PWS paragraph it corresponds to in the third, and a proposed corrective action in the fourth. This table becomes a mandatory input to the next proposal kickoff for any requirement in the same NAICS code or functional area.

3. Past Performance Gaps

If the debrief identifies a past performance weakness, the fix is not in the proposal volume. It is in your CPARS record and your reference selection strategy. Review the CPARS ratings you have on file. If a rating is lower than expected, you have the right to comment on it in the CPARS system. Identify whether the weakness the agency cited was a relevance problem (the work was not close enough to the requirement) or a quality problem (the rating itself was marginal). Each has a different corrective path.

4. Evaluation Factor Weighting Signals

Agencies are not required to disclose the precise point scores, but the narrative often reveals which factors drove the award decision. If the debrief language concentrates on technical approach and says little about price, that agency weighted technical heavily. File that signal. When the next recompete or follow-on solicitation appears from the same contracting activity, you know where to invest proposal writing time.

Building a Debrief Log

A single debrief is useful. A log of debriefs across multiple pursuits over twelve to eighteen months is a competitive intelligence asset. For each debrief, record the agency, the NAICS code, the contract type (FFP, T&M, cost-plus), the evaluated price gap, the primary weakness categories, and the past performance rating received. Over time, patterns emerge. If the same weakness category appears across multiple agencies, it is a proposal writing problem, not a one-time miss. If past performance is consistently cited, the issue is reference selection or CPARS management.

Capture managers who maintain this log can walk into a bid/no-bid meeting with evidence rather than intuition. When a new solicitation drops from an agency where a prior debrief revealed a specific weakness, the team knows exactly which section of the proposal needs the most attention before the kickoff even starts.

What Debriefs Cannot Tell You

Debriefs have limits worth acknowledging. The agency will not disclose trade secrets or proprietary information from the awardee's proposal. It will not identify the names of the awardee's key personnel unless that information is already public. It will not explain source selection panel deliberations in detail. And in some cases, particularly for civilian agency procurements outside the FAR Part 15 framework, the disclosure obligations are narrower.

If the debrief response feels thin or evasive, you can ask follow-up questions in writing. If you believe the agency failed to provide the information required by FAR 15.506(e), you can note that in a follow-up letter and, in more serious cases, raise it in a Government Accountability Office (GAO) protest. Most offerors do not need to go that far. Most debriefs, even brief ones, contain at least one actionable data point.

Connecting Debrief Intelligence to the Next Pursuit

The debrief is not the end of the process. It is the input to the next capture plan. Before the next solicitation from the same agency or in the same functional area reaches the street, a capture team that has analyzed its debrief history can answer questions that most competitors cannot: What price range is competitive for this type of requirement? Which technical discriminators does this agency weight most heavily? What past performance profile do winning offerors typically present?

A government-contracting workspace where a team reviews opportunities, makes pursuit decisions, and prepares proposals benefits directly from this kind of structured intelligence. The debrief data informs the pursuit decision, the proposal outline, the price-to-win analysis, and the past performance reference selection, all before the RFP drops.

One Practical Takeaway

Set a calendar reminder for the day after every award notification: draft and send the FAR 15.506 debrief request before the three-day window closes. Treat the response as a structured data input, not a narrative to skim. Log it. Compare it to prior debriefs. Let the pattern tell you where to invest on the next bid. That discipline, applied consistently, compounds into a measurable improvement in proposal quality over time.