Most SDVOSB firms treat a lost award as final. It usually is — but not always, and the firms that never consider a protest leave a real remedy on the table when the award decision was genuinely flawed. A protest is not a way to relitigate a close technical score you disagree with. It is a formal challenge to a specific procurement error, and it only works when you can point to one. Organizational conflicts of interest are another area where an OCI that was not properly disclosed or mitigated by the awardee can be raised as a protest ground.
What a Bid Protest Actually Is
A protest is a formal objection to a solicitation, an evaluation, or an award decision, filed with a forum that has authority to review the procurement and, if it finds error, order a remedy — which can range from a corrective evaluation to a full re-compete. It is a legal process with strict deadlines, not an informal complaint to the contracting officer.
The Three Forums
Agency-level protests go to the contracting agency itself. They are the fastest and cheapest option, and many agencies take them seriously, but you are asking the same organization that made the decision to review its own work.
GAO protests go to the Government Accountability Office, which is independent of the procuring agency and is the most common forum for federal protests. GAO has a strong statutory framework, a predictable timeline, and issues written decisions that carry real weight even when they are not binding case law.
Court of Federal Claims (COFC) protests go to a federal court. This is the most formal, most expensive route, typically reserved for cases involving larger dollar values or where GAO relief was insufficient. Legal representation is effectively required.
Most SDVOSB firms that protest should be looking at GAO. It is independent, well-documented, faster than COFC, and does not require the same level of legal spend.
Grounds for Protest
You need an actual procurement error, not a disagreement with the outcome. Valid grounds typically include the agency failing to follow its own stated evaluation criteria, unequal treatment between offerors, a flawed or unreasonable technical evaluation not supported by the record, improper exclusion from the competitive range, or a solicitation that contains ambiguous or unduly restrictive requirements.
“We should have won” is not a ground for protest. “The agency scored us against a criterion that was not in the solicitation” is. The distinction is the entire game — a protest lives or dies on whether you can point to a specific procedural failure, documented against the actual solicitation language and the debrief the agency gave you.
Timeline and Deadlines
Protest deadlines are unforgiving and procedural, not discretionary. For GAO, a protest generally must be filed within 10 days of when you knew or should have known the basis for protest, and if you requested and are attending a required debriefing, the deadline is typically 10 days after the debriefing concludes — not 10 days after you received the initial notice.
This is why requesting a full debrief on every loss matters, independent of whether you plan to protest. A debrief starts the clock and, more importantly, is often where you first learn whether a protestable error actually occurred. See our guide on requesting a post-award debrief for how to structure that request.
The Automatic Stay
If you file a GAO protest within the required timeline — generally within 10 days of award, or within 5 days of a required debrief request if that is later — the agency is typically required to stay contract performance until the protest is resolved. This automatic stay is one of the most powerful features of the GAO forum: it forces the agency to actually engage with your protest rather than letting the awardee start work while the process plays out.
What a Protest Actually Costs You
Time is the first cost. A GAO protest typically takes up to 100 days to resolve, during which your team is spending hours on legal coordination and documentation instead of new business development. Legal fees are the second cost — agency-level protests can sometimes be handled without outside counsel, but GAO and COFC protests generally benefit from experienced government contracts counsel, and that is not inexpensive.
The relationship cost is the one firms underweight. Protesting an agency you plan to work with repeatedly is a real decision, not a free action. It is sometimes the right one — agencies generally respect a well-founded, professionally handled protest more than firms expect — but a pattern of weak or reflexive protests damages your standing with contracting officers who remember which firms protest every loss.
Realistic Odds
GAO sustains a minority of protests filed, but that statistic undersells the actual value of the process — a meaningful share of protests result in the agency taking voluntary corrective action once the protest is filed, without GAO needing to issue a sustained decision at all. Filing a well-documented protest sometimes gets you the remedy before the forum even rules, simply because the agency recognizes the exposure.
When It Is Worth Filing
File when the debrief reveals a specific, documentable procedural error — the agency applied an unstated evaluation factor, treated a materially similar aspect of two proposals inconsistently, or made a price realism determination unsupported by the record. File when the contract value justifies the time and legal cost. File when your documentation is strong enough that a third party reviewing the record would agree something went wrong.
When to Walk Away
Walk away when your actual objection is that you scored lower on a legitimately subjective technical factor and the agency followed its stated process. Walk away when you cannot point to a specific error, only a general sense the outcome was unfair. Walk away when the dollar value does not justify the time and legal spend relative to your firm’s size. Most losses fall into this category, and that is fine — the better long-term investment is almost always improving your next proposal, not fighting this one.
How to Protect Yourself Before You Ever Need to Protest
Request a full debrief on every meaningful loss, not just the ones you suspect were mishandled — you cannot evaluate protest grounds without seeing the evaluation record. Keep detailed records of every solicitation amendment, question-and-answer exchange, and evaluation criterion as it was actually published, not as you remember it. Track the actual language of the solicitation against what the debrief says was evaluated. This habit costs almost nothing and is the entire foundation of being able to recognize a protestable error when one occurs. Feed every loss — protested or not — back into your BD pipeline so you can track patterns across opportunities and calibrate future go/no-go decisions.