The debriefing is a fifty minute call on a Thursday. Four people from the capture team dial in, the contracting officer works through a deck that never gets sent, and at minute thirty one an evaluator says the past performance reference was scored against the wrong contract.
Nobody catches the exact wording, because the two people who would have taken notes were the two people asking questions. Ten days later you decide whether to protest.
That is not a story about one badly run debriefing. It is the predictable result of how the rule is written.
The Rule Specifies the Content, Not the Medium
FAR 15.506(a)(1) is the entitlement. On a written request received within 3 days after notification of contract award, an offeror shall be debriefed and furnished the basis for the selection decision and contract award.
Section 15.506(d) is specific about what has to come out: the Government’s evaluation of the significant weaknesses or deficiencies in the offeror’s proposal, the overall evaluated cost or price and technical rating of the awardee and of you, the overall ranking of all offerors, a summary of the rationale for award, and reasonable responses to relevant questions about whether the stated procedures were followed.
Then 15.506(b) sets the format. Debriefings may be done orally, in writing, or by any other method acceptable to the contracting officer.
And 15.506(f) is the whole writing requirement: An official summary of the debriefing shall be included in the contract file.
Read those together. The disclosure is mandatory and detailed. The medium is the contracting officer’s choice. The only document the rule guarantees is a summary authored by the side that made the decision.
It is worth being precise about what that does and does not mean. Nothing here is misconduct, and nothing suggests contracting officers are hiding anything. An oral debriefing is fully compliant. The regulation simply does not pair its detailed disclosure obligation with any obligation to preserve the disclosure, and so the richest account of the evaluation — the one with the follow-up questions and the concessions in the answers — exists only as memory unless somebody decided in advance to keep it.
That Conversation Starts the Clock
Under 4 CFR 21.2(a)(2), where a debriefing is requested and required, the protest shall not be filed before the debriefing date offered to the protester, but shall be filed not later than 10 days after the date on which the debriefing is held.
The automatic stay runs tighter. FAR 33.104(c)(1) requires the contracting officer to suspend performance or terminate the award only when GAO notice arrives within 10 days after contract award or within 5 days after a debriefing date offered to the protester, whichever is later. Miss that and you may win a protest against a contract already half performed.
Those two deadlines are the reason the record problem is not merely an annoyance. Both clocks run from the date of the conversation, which means the debriefing is simultaneously the moment you learn the grounds for protest and the moment your window to act on them opens. The five day stay deadline in particular leaves almost no room to reconstruct anything. A capture team that spends the first week arguing about what an evaluator actually said has spent the part of the schedule that decides whether performance gets suspended.
Asking for more time does not move either date. Under 15.506(a)(4)(ii), accommodation of an untimely debriefing request does not automatically extend the deadlines for filing protests. The courtesy is real; the extension is not.
Why the Usual Workarounds Fail
- Assuming it arrives in writing. DoD had to legislate around this. DFARS 215.506(b) makes a written or oral debriefing mandatory on request at 15 million dollars and up, 215.506(d)(ii) adds the redacted source selection decision document above 150 million, and 215.506-70 keeps the debriefing open until the agency answers written follow ups. Civilian agencies owe none of it.
- Relying on the official summary. It goes in the contract file under 15.506(f). You typically see it in the agency report, weeks after the decision to protest was already due.
- Splitting note taking across the team. Your sharpest listeners are your questioners. Notes thin out at the exact moment an evaluator concedes something.
- Planning to sort it out in the record. The GAO record follows the filing. The 10 day judgment gets made on memory.
The first of those deserves emphasis, because it is where most of the confusion in this area comes from. Teams that work primarily on defense contracts build habits around a debriefing process that is genuinely more protective — enhanced content, written follow-up questions, a debriefing that stays open. Those habits do not transfer. The same team bidding a civilian agency procurement is operating under FAR Part 15 alone, where the enhanced debriefing simply does not exist, and the gap tends to be discovered on the call rather than before it.
What Actually Works
Put the format question in the request itself. The same letter that triggers 15.506(a)(1) can ask for the debriefing in writing and ask whether the session may be recorded. Contracting officers agree more often than capture teams assume, and a documented no is useful too — a written request that went unanswered is itself a dated document, which is a materially better position than a silence nobody can place in time.
Then capture your own side regardless. Hold the readout in the ten minutes after the call ends, while the phrasing is still exact, and record that instead of reconstructing it on day nine. Nobody needs permission to keep an accurate account of a conversation their own team just had, and this is the one part of the process that is never at the agency’s discretion.
Memory does not degrade evenly, which is why the timing matters more than the effort. What survives a week is the gist — the reference was scored wrong. What disappears first is exactly the detail that decides a protest: which reference, scored against which contract, in whose words, in answer to which question.
AmyNote captures it on the phone already on the table. Transcription runs on OpenAI’s latest Speech API, which handles the vocabulary that breaks consumer tools: significant weakness versus deficiency, technical acceptability, price realism, best value tradeoff, source selection authority, corrective action.
Analysis runs on Anthropic’s Claude Opus, so you can ask the transcript what the evaluator actually said about the past performance reference rather than replaying an hour of audio the night before a deadline. Speaker identification separates capture lead, proposal manager, and counsel, and cross session memory carries from the debriefing readout into the protest decision meeting.
On privacy: both OpenAI and Anthropic contractually guarantee zero training on user data. Audio is encrypted in transit and not retained after processing. Transcripts stay local on the device with end to end encryption. No proposal strategy and no source selection detail sitting on a third party server.
Getting Started
Write the debriefing request template this week, before an award notice starts a 3 day clock. Build the recording question and the written debriefing request into it. Then block fifteen minutes after every debriefing for a recorded readout, and make the protest call from a transcript instead of four sets of partial notes.
The regulation guarantees you the content and leaves the record to the agency. The part it cannot take away is the one you were always free to keep yourself. AmyNote runs on the phone already in your pocket.
Originally published as an X Article by @AmyNoteApp.
