GAO Bid Protest Roundup – June 1-12, 2026

In the last two weeks, GAO issued a series of bid protest decisions that—taken together—highlight how contractors can win (or lose) based on things like how strictly agencies apply stated thresholds, how persuasive the proposal record is against the solicitation’s evaluation criteria, and whether protests survive timeliness and “abandonment” rules. Below are the 10 most contractor-relevant takeaways, each tied to a specific GAO case, and distilled into practical guidance you can use to improve proposal strategy, reduce risk in submissions, and understand what GAO looks for when deciding whether an agency’s evaluation and award decision will stand.

1) Science Applications International Corporation — B-424255; B-424255.2

Key takeaway
GAO will not overturn a “Good vs. Excellent” technical rating where the evaluation was reasonable and the protest is largely disagreement with internal rating-language rather than inconsistency with the solicitation.

SAIC’s Allegations

SAIC protested the issuance of a task order to Accenture under GSA’s CASTLE-NET TOR. In essence, SAIC argued that:

• Its technical rating should have been higher (it received Good vs. Accenture’s Excellent under the most important technical approach/scenario response factor).
• The agency used unreasonable “qualifying language” (e.g., “mostly complete,” “mostly practical”) and disparately evaluated proposals.
• Accenture should not have received transition-in credit (SAIC argued it was the incumbent and therefore should have received a strength for transition-in).
• The agency conducted unequal/disparate treatment in multiple technical evaluation areas.
• The best-value tradeoff decision was insufficiently explained and unreasonable given SAIC’s arguments about underlying technical evaluation flaws.

GAO’s Response

GAO denied the protest. Key responses included:

• SAIC’s “Good vs. Excellent” arguments were largely disagreement with the agency’s evaluation judgments, not proof of unreasonableness.
• GAO explained that evaluation plan/rating definitions are internal guidance and do not by themselves create enforceable rights for offerors.
• GAO rejected the claim that “mostly/somewhat” wording meant the proposal had omissions, noting the record showed SAIC’s proposal met all solicitation requirements and the language reflected degree of compliance.
• On the transition-in credit issue, GAO held the solicitation did not require incumbent-favoring evaluation, and SAIC failed to show the agency was obligated to assign a transition-in strength based on incumbency alone.
• For disparate treatment, GAO reiterated that the protester must show the competitors’ proposals were substantively indistinguishable (or nearly identical) in the evaluated areas; SAIC did not.
• The best-value tradeoff was upheld because GAO found the SSA’s rationale was sufficient and consistent with the solicitation, particularly focusing on the technical approach/scenario response factor being more important and showing Accenture’s superior value justified the price premium.

2) Mustang Survival Manufacturing, Inc. — B-424336

Key Takeaway
In fixed-price/LPTA procurements, agencies generally are not required to perform “price realism,” unless the solicitation requires it—GAO focuses on fair and reasonable price , and the specific risk framework actually included (e.g., DFARS SPRS).

MSM’s Allegations

Mustang protested the Navy’s award of a contract to RFD Beaufort for SESSPE suits (submarine escape and surface survival equipment). Mustang’s main allegations were:

• Price evaluation was unreasonable: Mustang argued RFD Beaufort’s price was materially lower than historical pricing, and the agency should have analyzed/explained the basis for the reduction and whether the deviation created performance risk.
• SPRS (DFARS 252.204-7024) risk evaluation was flawed: Mustang challenged how the Navy used the Supplier Performance Risk System (SPRS) and argued that once the Navy found parts of the SPRS price information unreliable, it should have documented an adequate substitute evaluation addressing price and supplier risk.
• Award decision was unreasonable: Mustang contended the agency failed to reconcile the alleged “benchmarks deviation” and its implications.

GAO’s Response

GAO denied the protest, holding that the Navy’s evaluation was reasonable and consistent with the solicitation and applicable rules:

• Fixed-price vs. price realism
  • GAO explained that for a fixed-price contract, agencies are generally required to ensure prices are fair and reasonable, not to perform a price realism analysis—unless the solicitation specifically requires realism or rejection for “too low” pricing.
  • Because the solicitation did not require price realism, GAO would not require the kind of “justify the low price” analysis Mustang sought.
• SPRS/DFARS evaluation was satisfied
  • GAO found the Navy considered SPRS price risk information as DFARS 252.204-7024 requires, but reasonably determined that the SPRS price report contained faulty historical pricing information.
  • GAO accepted that the contracting officer therefore did not rely on the unreliable SPRS pricing outputs, and instead considered other allowed information (e.g., offerors’ proposed pricing and historical pricing that supported the fair/reasonable conclusion).
  • GAO also distinguished this from cases where agencies fail to generate or perform the required DFARS SPRS evaluation.
• Award decision challenge failed as a consequence of the evaluation
  • Since GAO found no basis to object to the price/risk evaluation, it also rejected Mustang’s argument that the award decision was unreasonable.

3) Economic Systems (EconSys) — B-424285.2

Key Takeaway
Competitive range exclusion is defensible when the agency reasonably finds your proposal is unacceptable as submitted under the stated factor criteria—and the protest doesn’t properly and specifically challenge the particular weaknesses/deficiencies.

EconSys’s Allegations

EconSys protested its exclusion from the competitive range under an OPM RFQ/RFP for federal HR IT modernization. Its main allegations were that:

• The agency applied unstated evaluation criteria.
• The agency unreasonably evaluated its proposal—especially under the step-two non-price factors (implementation approach, system testing, and virtual live demonstration).
• As a result, the competitive range determination (excluding EconSys) was improper.

GAO’s Response

GAO denied the protest, finding the agency’s evaluation and competitive range determination reasonable and consistent with the solicitation:

• No unstated criteria/evaluation tied to the stated RFQ scheme GAO held that the contested weaknesses/deficiencies were reasonably connected to the solicitation’s stated evaluation criteria and that agencies may consider matters logically encompassed by stated criteria.
• Example: “system of record” deficiency was reasonable GAO upheld a deficiency where EconSys’s approach was evaluated as inconsistent with the RFQ’s requirement that the Core HCM platform function as the system of record (rather than a front-end approach dependent on other systems).
• System testing weaknesses were tied to stated functional areas GAO found the agency’s testing critiques aligned with the RFQ’s functional areas (usability/accessibility, learning, reliability, real-time workflows, error handling, etc.), not hidden or unstated requirements.
• Competitive range exclusion was permissible GAO emphasized that agencies are not required to keep proposals that are technically unacceptable as submitted or have no realistic prospect of award.
• Procedural/pleading issues mattered GAO also dismissed challenges that EconSys failed to specifically and timely support, including arguments introduced or developed too late, which the GAO refers to as piecemeal presentation of protest issues. 

4) Spatial Front, Inc. — B-424251; B-424251.2; B-424251.3

Key Takeaway
Even if an agency evaluation has an error, GAO won’t sustain the protest without competitive prejudice—i.e., removing the error wouldn’t change the outcome given the other remaining evaluation findings.

SFI’s Allegations

SFI protested the award of a NOAA task order to GAMA-1 under an RFQ, alleging:

• Unreasonable technical/management evaluation of SFI’s quotation, including that the agency assigned decreased confidence findings for reasons not properly contemplated by the RFQ.
• The agency failed to evaluate the impact of a corporate transaction involving the awardee (GAMA-1’s acquisition).
• The agency made award to an ineligible vendor under the terms of the underlying BPA (because of recertification/size-status consequences after the transaction).
• Unequal discussions/exchanges: the agency allegedly communicated only with the awardee regarding the awardee’s situation.
• The agency’s best-value determination was flawed.

GAO’s Response

GAO denied most arguments and dismissed others, primarily on reasonableness and lack of prejudice:

• Evaluation challenges: denied
  • GAO found SFI’s decreased-confidence findings were largely reasonable and consistent with the RFQ’s broadly framed evaluation questions and required oral-briefing content.
• One evaluation misstep (Question 2) didn’t matter: denied
  • for lack of competitive prejudice GAO agreed the agency improperly tied one decreased-confidence finding to a requirement not contemplated by the RFQ’s question. But GAO held SFI failed to show competitive prejudice because multiple other decreased-confidence findings would remain and the SSA’s rationale relied mainly on other unresolved problems.
• Corporate transaction: denied
  • GAO held the acquisition (an equity sale) did not undermine the award because the agency reasonably determined it did not affect performance—GAMA-1 remained the same entity and represented that assets/capabilities/staffing would remain in place.
• BPA eligibility violation: dismissed as untimely
  • GAO found the supplemental challenge was raised too late because SFI had enough information earlier (during its initial protest) to raise the BPA eligibility ground.
• Unequal exchanges/discussions: denied
  • GAO held the communications with GAMA-1 did not amount to “discussions” requiring equal treatment across vendors; they were essentially about eligibility/size-status implications, not requests for information necessary to revise the quotation.
• Best value: denied
  • GAO found the SSA performed a rational price/technical tradeoff and reasonably concluded the awardee’s technical superiority justified the premium.

5) Servexo Protective Services, Inc. — B-424349; B-424349.2

Key Takeaway
When an RFQ includes a numeric CPARS threshold (like “>10% marginal/unsatisfactory”), GAO enforces it as written. Contractors can’t avoid the threshold by arguing the ratings come from one “program.”

SPS’s Allegations

Servexo protested that the USDA unreasonably evaluated its quotation as unacceptable under an RFQ for security guard services. Its primary argument was that:

• The agency’s CPARS evaluation math was irrational: Servexo argued the agency treated multiple related task orders as independent marginal performance events, even though they stemmed from one overarching program.
• Therefore, Servexo claimed the marginal ratings should have been treated more like a single issue rather than counted individually toward the RFQ’s threshold.

GAO’s Response

• GAO denied the protest, finding the evaluation reasonable and consistent with the RFQ:
• RFQ required a percentage test: GAO emphasized the solicitation’s clear rule: if more than 10% of CPARS ratings in a category (Quality/Management/Schedule) were marginal or unsatisfactory, the quotation would be rated Unacceptable.
• Agency followed the solicitation’s counting approach: The agency reviewed Servexo’s CPARS data and found Servexo’s schedule-category marginal ratings exceeded the 10% limit (about 22.97%).
• No RFQ prohibition on counting individual task orders: GAO found Servexo pointed to nothing in the solicitation requiring the agency to “aggregate” or qualitatively reinterpret ratings at a program level rather than count them as stated.
• Numerical method is explicitly allowed: GAO also rejected Servexo’s argument that the agency performed a “mathematical calculation” instead of a qualitative analysis—because the RFQ provided for that numeric/threshold method.

6) Oready, LLC — B-424508; B-424509; B-424510

Key Takeaway
Timeliness rules matter: sending a copy to the contracting officer doesn’t automatically make it an agency-level protest for GAO’s exception unless it meets the actual agency-level protest requirements.

Oready’s Allegations

Oready protested the terms of three RFQs issued by the Department of the Interior (Bureau of Indian Education) for therapy services at school sites. Its position was essentially that the RFQs included terms that unjustifiably limited competition.
However, the case was decided on a procedural basis.

GAO’s Response

GAO dismissed all protests as untimely, holding that:

• GAO filing cutoff mattered: Oready filed each protest after GAO’s 5:30 p.m. Eastern Time filing cutoff, even though the RFQs’ closing times were earlier. Because of the cutoff, the protests were treated as filed the next business day—after the submission deadline for each RFQ.
• Timeliness exception didn’t apply: Oready argued that it sent copies of each protest to the contracting officer before the RFQ quotation closing time, so it should be treated as a “subsequent protest” under GAO’s rules.
• The CO emails were not valid agency-level protests: GAO held the emails did not meet the requirements for an agency-level protest (FAR 33.103), because they were not addressed as requests for an agency ruling and instead explicitly identified the filings as copies of protests already intended for GAO.
• Result: Each RFQ-term challenge was dismissed under the timeliness rules (4 C.F.R. § 21.2(a)(1)).

7) The Gilchrist Law Firm, P.A. — B-424421; B-424421.2

Key Takeaway
If your quotation is submitted late or through the wrong method/portal when the RFQ requires strict compliance, GAO will defer to the agency’s rejection—and may dismiss as abandonment if you don’t meaningfully rebut the agency report.

TGLF’s Allegations

TGLF protested the VA’s rejection of its quotation under an RFQ for FOIA compliance services. GLF’s core contentions were that:

• The VA was required to assess TGLF’s quotation for compliance with submission instructions (even though VA said it was submitted late and outside the required eBuy process).
• TGLF argued the solicitation submission instructions were ambiguous or not enforced equally—specifically tied to how file naming and pricing template formats were handled.

GAO’s Response

GAO dismissed the protest. Its reasoning focused on abandonment and (in the alternative) the merits would not help TGLF:

• Abandonment: GAO found TGLF’s comments did not meaningfully rebut the VA’s detailed response—especially the agency’s position that the quotation was rejected because it was late and not submitted through the required portal/method. Because TGLF didn’t address the agency’s arguments, GAO treated the protest allegations as abandoned.
• Late/no evaluation (alternative merits discussion): GAO also noted that the RFQ was explicit that:
  • quotations had to be submitted electronically via GSA eBuy, and
  • late quotations would not be accepted or evaluated. Since TGLF did not submit before the deadline via the required method, VA properly set the quotation aside without evaluating it for the other technical/price criteria.

8) TechGlobal, Inc. — B-424287; B-424287.2

Key Takeaway
“Unstated evaluation criteria” arguments fail when the allegedly unstated factor (here, AI use) is logically encompassed by stated evaluation areas with a clear nexus to the required work.

TechGlobal’s Allegations

TechGlobal protested the issuance of a NOAA task order to Reston Consulting Group (RCG) under an RFQ for IT support services. TechGlobal’s main arguments were:

• Unstated evaluation criteria: NOAA allegedly treated RCG’s use of an AI tool (“Gemini AI”) as a key discriminator even though the RFQ did not mention AI.
• Unreasonable evaluation of TechGlobal: TechGlobal argued NOAA mis-evaluated its quotation, particularly that NOAA should have credited its staffing/management plan more favorably.
• Flawed best-value tradeoff: TechGlobal argued the SSA’s price/technical tradeoff was inconsistent with the RFQ, including that the “discriminators” relied on were not entitled to that weight.

GAO’s Response

GAO denied the protest, finding NOAA’s evaluation and selection reasonable:

• AI was not an unstated criterion (it had a nexus): GAO held that NOAA’s favorable evaluation of AI was logically encompassed within stated technical evaluation areas (help desk administration requirements), because the RFQ required development/maintenance of SOPs/documentation and the AI was evaluated as a tool to keep those SOPs current.
• No requirement to assign additional strengths: GAO found that TechGlobal failed to show the solicitation required a specific staffing/retention commitment to produce a higher confidence/strength. The record supported NOAA’s judgments about which proposal elements actually increased confidence.
• Best-value tradeoff was consistent and rational: GAO ruled the SSA reasonably concluded RCG’s technical superiority—particularly two technical discriminator elements—was worth the premium price, and TechGlobal’s challenge largely amounted to disagreement with the agency’s judgment.

9) Octave Technologies Corporation — B-424253; B-424253.4

Key Takeaway
In FAR 8.4/FSS RFQs, exchanging/discussing only with the “best-suited” vendor can be fair and proper if the record supports the best-suited determination and the RFQ authorizes that approach.

Octave’s Allegations

Octave protested CMS’s issuance of an FSS task order to C-HIT (doing business as C-HIT) under an RFQ for CMS’s API gateway support services. Octave’s principal allegations were:

• Misevaluation and disparate treatment: CMS allegedly evaluated Octave’s and C-HIT’s quotations unfairly and unreasonably.
• Improper “discussions” limited to C-HIT: Octave argued CMS held exchanges only with the awardee, without properly documenting a valid tradeoff/source selection basis using the other vendors’ initial quotations.
• Unreasonable source selection / best value: Octave contended that the exchanges and selection process were flawed and inconsistent with the RFQ.

GAO’s Response

GAO denied the protest, finding both the evaluations and the process consistent with the RFQ:

• Evaluation was reasonable and solicitation-consistent: GAO determined Octave failed to show the agency’s evaluation judgments were unreasonable. Differences in evaluation treatment were tied to material differences in the vendors’ quotations.
• Exchanges only with the best-suited vendor were permissible: GAO found the record supported the contracting officer’s “best suited” determination (essentially a competitive-range-of-one approach). Where the RFQ allows it—and evaluation supports it—CMS could conduct exchanges solely with that vendor.
• Tradeoff and documentation were sufficient: GAO concluded the award decision memorandum adequately reflected the contracting officer’s reasonable judgment that the superior quotation justified the higher price, and the exchanges were aimed at resolving issues that could be addressed through revision.

10) ID8Spark, LLC — B-424253.2; B-424253.3; B-424253.5

Key Takeaway
GAO upholds negative experience/evaluation outcomes when your quotation’s experience crediting doesn’t match what the RFQ allows or what verification sources/data show.

ID8Spark’s Allegations

ID8Spark protested the issuance of an FSS task order to C-HIT under a CMS RFQ for services supporting the CMS API gateway. ID8Spark’s principal allegations included:

• Misevaluation of quotations / disparate treatment: ID8Spark argued CMS evaluated its quotation unfairly and/or applied unequal evaluation treatment.
• Improper discussions/exchanges only with the awardee: ID8Spark challenged the process where CMS conducted exchanges with C-HIT rather than also with ID8Spark.
• Unreasonable best-value / best-suited determination: ID8Spark argued the agency’s choice of C-HIT as best-suited (and exchanges limited to C-HIT) was not properly supported.

GAO’s Response

GAO denied the protest, finding CMS’s actions reasonable and supported by the record:

• Corporate experience/negative finding was reasonable: GAO upheld a negative corporate experience finding where the RFQ limited how experience could be credited, and the submitted experience/attribution did not meet the rules the agency could verify.
• PWS/QASP evaluation was reasonable and tied to requirements: GAO rejected “unstated criteria” theories where the concerns (e.g., missing testing approach for the platform alternative task, and onboarding timeline specifics) were reasonably related to stated RFQ objectives and risk of disruption/minimized downtime.
• Key personnel evaluation/misrepresentation arguments failed: GAO found no basis that C-HIT misrepresented key personnel experience. It treated the evaluated quotation content as the relevant basis rather than relying on external/online resume materials.
• Exchanges with only the best-suited vendor were permissible: GAO held that limiting exchanges to the best-suited vendor was proper when the evaluation reasonably supported that determination. It characterized the exchanges process as consistent with the RFQ approach and the record showed C-HIT’s superiority justified the exchange focus.

​If you need help deciding whether to file a protest, or need help defending a protest that has been filed against you, reach out to one of our expert bid protest attorneys at Reaves GovCon Group: Email Brad Reaves or Jake Noe


Think outside the beltway.