Skip to content

Menu

LexBlog, Inc. logo
NetworkSub-MenuBrowse by SubjectBrowse by PublisherJoin the NetworkGet StartedSubscribeSupport
Contact Us
Search
Close

May 2026 Bid Protest Sustain of the Month: In a Sustain-less Month, a Masterclass in How Not to Protest

By Cherie Owen on June 16, 2026
Email this postTweet this postLike this postShare this post on LinkedIn

The following is an installment in Crowell & Moring’s Bid Protest Sustain of the Month Series. In this series, Crowell’s Government Contracts Practice keeps you up to date with a summary of one of the most notable bid protest decisions each month. Below, Crowell Consultant (and former GAO Bid Protest Hearing Officer) Cherie Owen discusses GAO’s May 2026 decision in Mission Analytics, LLC—Recon., where a protest filing that missed GAO’s deadline by just 50 seconds set off a chain of procedural missteps that ultimately produced five dismissals across a single procurement, and offers some of the most practical filing guidance GAO has put to paper in recent memory.

May 2026 proved to be another sustain drought month – the second year in a row, as readers of the May 2025 Sustain of the Month post may recall.  For a blog dedicated to tracking contractor wins at GAO and the Court, that presents something of a content problem. As it turns out, however, one of GAO’s May 2026 decisions proved instructive in its own right: a single procurement that generated five adverse decisions, including a reconsideration of a reconsideration, and a procedural record that offers as much practical guidance as any sustained protest.

Mission Analytics, LLC—Recon., decided May 21, 2026, is a reminder that GAO’s bid protest framework is more nuanced and less forgiving than it might appear from the outside. Its rules on timeliness, standing, interested party status, and reconsideration are technical, precise, and rarely intuitive, and the consequences of misunderstanding them can compound quickly. This single procurement produced five adverse decisions, each one flowing from the last – a cautionary tale for any contractor that assumes the protest process is something it can navigate on its own.

The procurement at issue was straightforward. On September 11, 2025, the Air Force issued a request for quotations for CCTV system upgrades, with a closing time of 4:00 p.m. ET on September 17. Mission Analytics had concerns about certain solicitation requirements and raised them in an agency-level protest on September 17, including, in the final hours before the deadline, challenges to the camera zoom range specification, a Buy American clause, and the agency’s decision not to set aside the procurement for small businesses. The agency, rather than pausing or extending the solicitation, proceeded to receive and evaluate quotations.  Under GAO precedent, the agency’s decision to proceed constituted “initial adverse agency action” in response to Mission Analytics’ protest; its GAO protest clock then began running.  On September 23, the agency awarded the purchase order to another company.

September 29 was the tenth day after the initial adverse agency action (technically, the tenth day fell on a weekend, so the deadline rolled forward to the next business day), and therefore the last day to file a timely protest at GAO. At 5:07 p.m. (twelve days after the solicitation had closed), Mission Analytics submitted a quotation. At 5:31:49 p.m., it filed its protest with GAO.  However, GAO’s rules provide that a document is filed on a particular day when it is received in EPDS by 5:30 p.m. ET.  The agency later characterized this filing as late by “one minute and forty-nine seconds,” calculating from 5:30:00 p.m. to 5:31:49 p.m.

That framing, however, overstates the margin. Because GAO’s timeliness rules treat a filing as timely through 5:30:59 p.m., it is not until 5:31:00 p.m. that a filing is considered late.  Gov’t Acquisitions, Inc., B-408426 (“[f]or GAO filings, the time of filing will be viewed as 5:30 p.m., until the clock reaches 5:31 p.m.”).  This means the protest at 5:31:49 p.m. was actually only 50 seconds past the true deadline. The protest was accordingly treated as filed on September 30 and dismissed as untimely. As a further consequence of the untimely filing, Mission Analytics was also found not to be an interested party to challenge the award, because it had neither submitted a timely quotation nor filed a timely protest challenging the solicitation’s terms.

What followed was a sustained effort to reverse those conclusions. On January 26 and February 13, 2026 Mission Analytics filed two separate requests for reconsideration of the January 14 dismissal. In those requests, Mission Analytics argued, among other things, that its untimely filing should be excused because it had experienced technical difficulty when filing through EPDS, and that GAO should not penalize a protester for missing the deadline by such a slim margin. On February 2, it filed an entirely new protest, this one arguing that the Air Force had violated FAR 33.103(h) by failing to issue a well-reasoned written decision on the agency-level protests.

On April 1 GAO dismissed the new protest and denied the reconsideration requests in two separate decisions. As to the new protest, GAO explained that its regulations do not contemplate a challenge to an agency’s alleged failure to resolve an agency-level protest, and that GAO does not conduct appellate-style review of such decisions. GAO also confirmed that the Air Force had effectively denied the pre-award agency protest simply by proceeding to receive and evaluate quotations — no formal written decision was required. As to the reconsideration requests, GAO concluded that the technical difficulty argument had been raised too late, and that in any event minor technical difficulty with EPDS did not excuse an untimely filing.

On April 13, Mission Analytics requested reconsideration of both April 1 decisions. GAO dismissed the request, explaining that its Bid Protest Regulations simply do not contemplate requests for reconsideration of reconsideration decisions. Having already twice considered and rejected the timeliness, interested party, and technical difficulty arguments, GAO saw no reason to consider the matter for a third time.

As a masterclass in how not to protest, Mission Analytics offers several practical reminders that no protester can afford to overlook.  First, GAO’s bid protest regulations define “adverse agency action” broadly to include any action or inaction by an agency that is prejudicial to the position taken in a protest filed with the agency, including the opening of bids or the receipt of proposals. When the Air Force proceeded to receive and evaluate quotations notwithstanding Mission Analytics’ outstanding challenges, that conduct constituted adverse agency action and started the 10-day clock to file at GAO. Contractors should not wait for a formal written denial before heading to GAO — the clock may already be running. Second, GAO’s filing deadlines are strict and unforgiving. As this case illustrates, filing even 50 seconds late is fatal. Contractors should build a meaningful time buffer into the filing process and treat the 5:30 p.m. ET deadline as absolute. Finally, reconsideration at GAO is a one-time opportunity. GAO’s Bid Protest Regulations do not contemplate a request for reconsideration of a reconsideration decision — a procedural concept that, as far as GAO is concerned, simply does not exist. GAO will not revisit arguments it has already considered and rejected. Contractors who believe GAO has committed a legal error or overlooked material information must make that case fully and carefully the first time.

Photo of Cherie Owen Cherie Owen
Read more about Cherie OwenEmail
  • Posted in:
    Government Contracts
  • Blog:
    Government Contracts Legal Forum
  • Organization:
    Crowell & Moring LLP
  • Article: View Original Source

Call us at 1-800-913-0988 or email sales@lexblog.com.

Facebook LinkedIn Twitter RSS
  • About LexBlog
  • The Field We Built
  • Our Beliefs
  • Our Team
  • Contact LexBlog
  • Disclaimer
  • Editorial Policy
  • Terms of Service
  • Get Started
  • Publishing Solutions
  • Compass
  • Submit a Request
  • Support Center
  • System Status
Copyright © 2026, LexBlog, Inc. All Rights Reserved.
Law blog design & platform by LexBlog LexBlog Logo