|
Fifteen GAO Decisions, One Clear Message: Precision Wins Protests Over the last three weeks, the Government Accountability Office (“GAO”) issued fifteen bid protest decisions spanning agencies as varied as the Air Force, NASA, GSA, the VA, DHS, and even USASOC's live-goat training program. Taken individually, each decision resolves a narrow dispute over a specific solicitation. Taken together, they reveal a consistent pattern in how GAO evaluates protests and a clear roadmap for contractors who want to protest effectively, or avoid giving competitors grounds to protest against them. The throughline across all fifteen cases is deference to the record as written. GAO is not in the business of second-guessing agency judgment calls; it is in the business of checking whether agencies followed their own stated rules and whether protesters can back up their claims with specifics rather than inference. Below, organized by theme, are the key takeaways contractors should carry into their next proposal or their next protest. Additionally, a brief table below summarizes the outcome of the fifteen cases and highlights just how difficult it is to obtain a favorable outcome at the GAO. Of the fifteen cases decided, not a single one resulted in a sustain decision.
1. Read the Solicitation as a Whole, Not as You Wish It Read
The single most common reason protests failed over the last three weeks was that protesters read language into a solicitation that wasn't there, often by combining two separate requirements into one that sounded more favorable to their argument. In Indigo Ridge Farms (B-424156.2), the protester argued that because the solicitation required facilities capable of housing 500 animals, and separately required a USDA license, the awardee's license needed to authorize handling 500 animals. GAO rejected this, finding the RFP treated licensing and facility-capacity as two independent evaluation criteria, evaluated through entirely different means (a license copy versus diagrams and photos). Reading them together, GAO noted, would render the facility-capacity language superfluous, which is a classic red flag in interpretation disputes. Strategic Alliance Business Group (B-423306.19) hit a similar wall from a different angle: rather than misreading a requirement, the protester tried to satisfy a specific, mandatory item (a C-SCRM attestation form) by pointing to unrelated narrative elsewhere in its proposal. GAO wasn't persuaded, noting the protester never even explained how its narrative addressed the fifteen specific items the missing form required. Contractor takeaway: Before you protest, or before you submit, map every specific, standalone requirement to a specific, standalone response. If a requirement calls for a form, a certification, or a particular data point, generalized coverage elsewhere in the proposal will not save you. And if you're building a protest theory that depends on reading two provisions together to create a new combined requirement, expect GAO to ask why the agency would have bothered writing them separately. 2. Missing Mandatory Items Are Rarely Forgivable, and Clarifications Won't Bail You Out Two decisions in this set turned on the same blunt fact pattern: a proposal missing a required document. In Strategic Alliance, it was the C-SCRM attestation form. The protester's fallback argument, that the agency should have sought clarifications to fix what it called a "clerical error," also failed. GAO drew a sharp line between clarifications (limited exchanges that cannot cure deficiencies) and discussions (which can, but which agencies aren't obligated to conduct when award-without-discussions is contemplated). Because supplying the missing form would have materially changed the proposal's substance, it wasn't a clarification at all. Contractor takeaway: Treat "shall submit" and "shall provide" instructions as absolute, not aspirational. A missing certification, attestation, or form is not a paperwork technicality in GAO's eyes; it's a proposal deficiency that can end your bid before the technical merits are ever weighed. Build a submission checklist against the RFP's exact language, and don't count on an agency reaching out to let you fix it. 3. Standing and Timeliness Are Gatekeepers. Get There Before You Argue the Merits Several protests never even reached a substantive discussion because of threshold issues. FCN, Inc.—Reconsideration (B-424249.2) shows how narrowly GAO construes what a protester actually argued. FCN wanted reconsideration of a prior denial, contending it had timely raised an ambiguity theory about missing salient characteristics. GAO's review of the actual protest filing showed FCN's original argument was about undue restriction of competition and a de facto sole-source setup—not ambiguity. Referencing the same underlying provision in both arguments wasn't enough; the theories were legally distinct, and the ambiguity theory surfaced too late. BCCG JV (B-424377) presents an even more fundamental jurisdictional bar: because the task order was issued under a Department of Homeland Security waiver of procurement law authorized by the Illegal Immigration Reform and Immigrant Responsibility Act, Congress vested exclusive review authority in federal district courts, not GAO. No matter how strong BCCG's substantive arguments might have been, GAO simply lacked the power to hear them. The decision is also a good example of self-inflicted timeliness problems: the protester had accepted an IDIQ contract that expressly described the waiver's scope and expressly covered "waterborne" barriers, then waited months to argue the waiver didn't apply to waterborne barriers. Contractor takeaway: Before investing in the merits of a protest theory, confirm (a) that GAO actually has jurisdiction over the type of action being challenged, and (b) that your specific legal theory was raised clearly and distinctly within the applicable timeliness window. Challenges to a solicitation’s terms must be filed at the GAO before proposals are due. A protest that "gestures toward" an issue in its initial filing, then develops the real argument in later comments, risks being treated as an untimely new ground rather than a permissible elaboration. This is referred to as a “piecemeal presentation” of the protest. When in doubt, plead every distinct legal theory explicitly and early. 4. "Disagreement With the Judgment Call" Is Not a Protest Ground GAO's institutional posture is that it won't reevaluate proposals or substitute its judgment for the agency's. This fundamental principle showed up repeatedly, especially in tradeoff and technical-evaluation challenges. In InterImage, Inc. (B-424347), the protester argued the agency shouldn't have credited the awardee's experience developing a successor system (JPES) as advantageous for maintaining the current system (JOPES), especially given a 22% price premium. GAO found the agency had documented specific, concrete reasons, such as custom synchronization scripts and hands-on familiarity with underlying data structures, for treating that experience as valuable, and that the source selection authority had done a genuine qualitative comparison rather than a mechanical price-only analysis. The protester's disagreement with how much weight that experience deserved wasn't enough to overturn the decision. Contractor takeaway: If you plan to protest a technical or tradeoff decision, don't stop at "the agency should have valued this differently." You need to show the agency's stated rationale doesn't hold up on its own terms, e.g., that it's inconsistent with the solicitation's stated criteria, unsupported by anything in the awardee's actual proposal, or based on a misreading of the record. A well-documented, well-reasoned SSA narrative is very hard to unseat, even when the price gap is significant. 5. Conflict-of-Interest and Bias Claims Need Hard Facts, Not Suspicion BCCG JV also illustrates a now-familiar GAO standard: allegations of organizational conflicts of interest, bias, or "patterns of corruption" must be backed by specific, verifiable facts, not just inference from an employee's résumé or a generalized narrative of agency dysfunction. The protester's claim that a former agency official, three years removed from government service, gave the awardee a competitive edge failed for lack of any connection between that history and actual competitive advantage in a sole-source action where there was no competition to skew. Separately, GAO reiterated that alleged criminal post-employment violations under 18 U.S.C. § 207 are matters for agencies and the Department of Justice, not bid protest forums. Contractor takeaway: If you suspect an OCI or improper influence, build your case around specific, documentable facts, such as access to non-public information, a demonstrable timing or informational advantage, or a concrete role in the procurement, rather than job titles, family relationships, or general reputation. Absent hard facts, GAO will presume good faith on the part of government officials, and your protest ground will be dismissed rather than adjudicated on the merits. 6. Reconsideration Is Not a Second Bite at the Apple The FCN reconsideration decision is a useful reminder that GAO's reconsideration process exists to correct actual errors in a prior decision, not to let a protester reframe or expand arguments after losing. GAO's regulations require a detailed statement of errors made or information not previously considered, and simply arguing that an agency's response "should have" alerted GAO to a broader theory won't satisfy that standard. Contractor takeaway: If you intend to seek reconsideration, focus narrowly on demonstrable legal or factual errors in the decision itself. Don't use the reconsideration request as a vehicle to introduce a materially different argument that could have been, but wasn't, raised the first time around. The Bottom Line Across all fifteen decisions, GAO's message to contractors is remarkably consistent: precision beats persuasion. Protests succeed or fail based on whether the protester can point to specific solicitation language, specific record evidence, and specific procedural missteps. For contractors on the receiving end of an unfavorable evaluation, that means the real work happens well before a protest is filed: in reading solicitation language literally and completely, in submitting every required form and attestation without exception, in documenting technical advantages with concrete detail, and in identifying the exact legal theory that will support a challenge if one becomes necessary. The contractors who internalize these lessons will spend less time explaining to GAO what they meant to argue, and more time building the kind of record that actually wins. If you need assistance with assessing the viability of a potential protest, filing a protest at the GAO, or defending a protest, reach out to one of the expert government contracting attorneys at Reaves GovCon Group below:Think outside the beltway. Comments are closed.
|
