Bid Protests for Software Companies: Agency, GAO and the Court of Federal Claims

#bid-protests#small-business#saas#federal-market

By — Founder of GovExpress; prior domain experience at Bloomberg Government and GovWin IQ.

Sooner or later a software company that bids on federal work loses a competition it thinks it should have taken. Usually the right response is a debriefing, a few lessons and the next bid. Sometimes the evaluation was flawed in a way that matters, and the company has a formal remedy: a bid protest.

This guide covers what a protest is, the three places you can file one, the deadlines that decide most cases, and how to think about whether filing is worth it.

What a bid protest is

A bid protest is a written objection to how the government ran a procurement. Under FAR 33.101 it can challenge:

  • The solicitation itself, for example requirements that unduly restrict competition, or evaluation criteria that are ambiguous or inconsistent.
  • The cancellation of a solicitation.
  • The award, or a proposed award, usually because the agency evaluated proposals in a way that departed from the solicitation or from procurement law.
  • The exclusion of your proposal from the competitive range.

Only an interested party can protest. In general that means an actual or prospective offeror whose direct economic interest would be affected by the award or by the failure to award. If you didn’t submit a proposal, you can usually protest the terms of a solicitation before it closes, but not the award that follows it.

A protest is not an appeal of the agency’s judgment. Evaluators have wide discretion. Protests succeed when the agency didn’t follow its own solicitation, treated offerors unequally, made an unreasonable or undocumented decision, or broke a rule. They rarely succeed because the protester simply believes its proposal was better.

The three forums

1. The agency

FAR 33.103 lets you protest directly to the contracting agency. Agency-level protests are informal, quick and inexpensive, and you don’t need a lawyer. They’re a reasonable choice when the problem is a clear error the agency is likely to fix once it is pointed out, such as an ambiguous instruction in a solicitation.

The drawback is that the agency is reviewing itself. If it denies your protest, you can still go to GAO, but only if you file there within the GAO deadline that runs from the agency’s adverse decision.

2. The Government Accountability Office (GAO)

GAO is the most common forum for federal bid protests. Its rules are in 4 CFR part 21, and FAR 33.104 covers how agencies handle GAO protests. Protests are filed electronically, and the process is built to move quickly:

  • The agency files a report responding to the protest, usually within 30 days, and you get a chance to comment on it.
  • GAO must decide within 100 days of filing, under the Competition in Contracting Act. Most protests are resolved sooner, often because the agency takes corrective action before a decision.
  • GAO issues a recommendation, not an order. If it sustains a protest, it may recommend that the agency re-evaluate proposals, amend the solicitation, re-compete or make a new award decision. Agencies almost always follow GAO recommendations.

3. The U.S. Court of Federal Claims

You can also file a protest at the Court of Federal Claims, which has jurisdiction under 28 U.S.C. 1491(b). Court protests are formal litigation. They need counsel, they usually cost more, and there is no automatic stay of performance: you have to ask the court for an injunction. Companies tend to use the Court when they want a binding judicial decision, when they have already lost at GAO, or when the issue falls outside GAO’s jurisdiction.

Deadlines decide most protests

Timeliness rules are strict, and a late protest is dismissed without anyone looking at the merits. At GAO:

  • Problems with the solicitation that are apparent before proposals are due must be protested before the closing time for proposals. You can’t wait to see whether you’re selected and then object to the terms.
  • Other protests must be filed within 10 days after you knew, or should have known, the basis for the protest.
  • If a debriefing is required and you request it on time, a protest based on what you learn must be filed no earlier than the debriefing and within 10 days after it.

“Days” here are calendar days, with a deadline that falls on a weekend or federal holiday moving to the next business day. Count carefully, and count from the earliest date the agency could argue you knew.

The automatic stay

The deadline that matters most commercially is the stay deadline. Under the Competition in Contracting Act, if the agency receives notice of a GAO protest within 10 days after award, or within 5 days after a required debriefing offered on the earliest date the agency proposed, whichever is later, it generally must suspend performance of the contract while the protest is pending (FAR 33.104(c)). The agency can override the stay only with a written finding, for example of urgent and compelling circumstances.

The stay is often the reason to file at GAO at all. Without it, the awardee starts work, and by the time a protest is decided the incumbent advantage may have shifted.

Task orders and small-business protests

Two special cases come up often for software companies.

Task orders. Protests of orders placed under an IDIQ contract are restricted by statute and FAR 16.505(a)(10). In general an order can be protested only if it increases the scope, period or maximum value of the underlying contract, or if its value exceeds a threshold set by statute. Civilian and Department of War orders have different thresholds, and the forum for qualifying order protests is GAO. Check the current threshold for the issuing agency before you assume you can protest an order.

Size and status protests. If you think the apparent awardee of a small-business set-aside isn’t actually small under the solicitation’s NAICS code, that challenge goes to the Small Business Administration, not GAO. Size protests have their own short deadline, generally 5 business days after you are notified of the apparent successful offeror, and are filed through the contracting officer under 13 CFR 121.1004.

Should you file?

A protest is a legal right, not a hostile act, and contracting officers deal with them routinely. It still has costs, and a first-time federal seller should weigh them honestly.

Reasons to file:

  • The debriefing showed a specific, documentable error: the agency applied a criterion that wasn’t in the solicitation, ignored part of your proposal, or evaluated competitors on different terms.
  • The contract is strategically important, for example a first federal reference or a foothold at a target agency.
  • The automatic stay would preserve your chance at the work while the protest is decided.

Reasons to hesitate:

  • Cost. Protest litigation needs counsel experienced in procurement law. Most of the substantive record is released only under a protective order, and generally only outside counsel can be admitted to see it. A company that files on its own usually can’t see the evaluation documents it is challenging.
  • Odds. GAO sustains a minority of the protests it decides. Its annual reports to Congress also publish an “effectiveness rate” that counts cases where the agency took corrective action, which runs much higher than the sustain rate. Corrective action is a real outcome, but it usually means a re-evaluation, not an award.
  • The record you have. If the debriefing didn’t reveal a concrete error, a protest becomes a request to see the documents in the hope of finding one. That is a weaker position.

A useful middle step is to ask questions in the debriefing, read the solicitation’s evaluation section against what the agency actually said, and get an opinion from procurement counsel before the 10-day window closes. Many good protest decisions are made in those few days.

What a protest doesn’t fix

A protest tests whether the government followed its rules on one procurement. It doesn’t change whether you were eligible to compete: that depends on your SAM.gov registration, your size status, the set-aside and any authorization the work requires, such as FedRAMP for cloud services or CMMC for Department of War contracts involving controlled information. It also doesn’t turn a self-attested compliance claim into a verified one. If an evaluator rated a capability as unproven, a protest that the rating was unfair is much harder to sustain than one showing the rating ignored evidence you submitted.

To see your registration record alongside the other categories federal buyers review, score your company’s federal readiness.

The CMMC brief

What the Phase 2 suspension changed and what it did not — the obligations that still bind, the assessment path a contract puts you on, the scoping decision that drives the cost, and the sequence that fits inside a pipeline. Sourced from the primary record.

The brief is not open for requests yet. Email us and we will send it the moment it is.