1. Home
  2. |Insights
  3. |Debriefing to Dead Briefing: How to Avoid Dismissal by Identifying “Required” Debriefings

Debriefing to Dead Briefing: How to Avoid Dismissal by Identifying “Required” Debriefings

Client Alert | 2 min read | 10.28.26

A recent GAO decision,  Encon Desbuild JV4, LLC, highlights a critical pitfall for contractors: GAO dismissed as untimely a protest filed within 10 days of a “debriefing” because the debriefing was not “required” under GAO’s precedent and the applicable regulations.  This was true even though the contracting officer incorrectly told the contractor that the debriefing was required and provided under FAR part 15. 

Under 4 C.F.R. § 21.2(a)(2), a protester must file a protest based on grounds other than alleged solicitation improprieties no later than 10 calendar days after the protester knew or should have known the basis for protest.  An exception applies when the protest challenges a competitive procurement under which a debriefing is “requested and, when requested, is required”—a standard that largely governs procurements under FAR part 15.  In those instances, a protester may wait until after receiving its required debriefing to file. 

In Encon, the protester attempted to invoke the “required debriefing” rule to delay filing—even though GAO has previously held that debriefings provided in connection with phase one of design-build procurements under FAR subpart 36.3 are not “required.”  GAO concluded that Encon’s debriefing did not toll the 10-day protest deadline for two reasons: 

  1. Phase one of a design-build selection issued under FAR subpart 36.3 does not trigger “required” debriefings.  GAO emphasized that it has “repeatedly” declined to import FAR part 15 requirements into phase one of a design-build procurement, citing its earlier decision in Venergy Grp., LLC, B‑422708, Sep. 10, 2024, which involved nearly identical facts.  Because the first phase merely identifies the candidate pool for phase two without considering price- or cost-related factors, it is not a “procurement conducted on the basis of competitive proposals under which a debriefing is required.”  4 C.F.R. § 21.2(a)(2). 

  2. Neither designating a solicitation as a request for proposals, nor incorporating selected FAR part 15 procedures necessarily changes the nature of the procurement or the governing acquisition procedures.  Citing several prior decisions, GAO stressed that the solicitation’s references to FAR part 15 did not alter the nature of the procurement.  Moreover, while the solicitation referenced FAR part 15 procedures—on which Encon relied to argue that the procurement was conducted using competitive proposals—those procedures applied only to the second phase of the design-build process.  GAO also rejected Encon’s argument that the debriefing exception applied because the contracting officer mischaracterized the debriefing as a FAR part 15 “required” debriefing.  Noting that it addressed the same situation in Venergy, GAO concluded that “the contracting officer’s mischaracterization of a debriefing is not determinative as to whether a debriefing is required.”   

Because Encon waited more than ten days after learning its basis for protest, GAO dismissed the protest as untimely. 

As we have previously noted, determining whether a procurement qualifies for the debriefing exception is a nuanced question requiring analysis of multiple factors.  Crowell’s interactive roadmap of GAO bid protest timelines provides a helpful overview, but if you are unsure whether your procurement falls under the debriefing exception, contact experienced protest counsel who can guide you through this analysis.

Insights

Client Alert | 8 min read | 11.16.26

OCC’s AI Examiner Framework: How Banks’ AI Use Can Trigger Legal Liability and Supervisory Exposure

On November 4, 2026, the Office of the Comptroller of the Currency (OCC) issued Bulletin 2026-54 and a Supervisory Framework on Bank Use of Super Intelligence (the “Framework”), an examiner resource addressing banks’ use of artificial intelligence (AI), particularly generative AI and AI agents that can act on their own. The Framework creates no new legal requirements or supervisory expectations, and the OCC states that banks are not expected to use it to assess their own AI use or risk management. Importantly, it identifies as higher risk several AI uses common for banks that are already governed by binding law, such as moving money, making credit decisions, and communicating with customers. A failure in any of those uses could trigger legal liability. Institutions that rely on AI for these tasks should consider the following: ...