Federal Bid Protests
A working overview for U.S. general contractors. Where to file, the filing windows, what a protest costs to run, and when protesting an award is the right move.
Last updated
This article is general guidance, not legal advice. Bid protest decisions involve case-specific facts, short timelines, and procedural rules that should be evaluated with counsel familiar with federal procurement protest practice.
What a bid protest is, and what it isn’t
A bid protest is a formal challenge to a federal procurement, filed by an interested party. The challenger argues that the agency conducted the procurement improperly, either in the terms of the solicitation itself or in the evaluation that led to award. Protests can challenge solicitation terms before bids are due (a pre-award protest), or they can challenge an award after the fact (a post-award protest). The forum and the filing rules differ.
A protest is not the appropriate response to losing a competitive procurement on price or on substantive evaluation grounds the agency was entitled to reach. A contractor whose proposal scored lower than the awardee’s on factors the agency was authorized to weigh does not have grounds to protest. A contractor whose proposal was misevaluated against the stated evaluation criteria, or whose proposal was rejected on grounds the FAR does not support, may have grounds.
The threshold for filing is that the protester is an “interested party,” which generally means an actual or prospective offeror whose direct economic interest would be affected by the award or the protest. A subcontractor on the losing team is not generally an interested party. A bidder that did not submit a proposal usually is not, with limited exceptions for pre-award protests of solicitation terms.
Where to file: agency, GAO, and the Court of Federal Claims
A bid protest can be filed in one of three forums. Each has its own procedural rules, its own typical timeline, and its own cost.
Agency-level protests
Agency-level protests are filed with the contracting officer or the agency’s designated protest authority and are governed by FAR 33.103. The procedure is faster and cheaper than the alternatives, and the agency typically issues a decision within 35 days. Agency-level protests work well when the issue is clear and the contractor wants a fast answer without committing to the cost of a GAO protest. The decision is sometimes less rigorous than a GAO decision, and the protester can pursue a subsequent GAO protest if the agency-level outcome is unsatisfactory, subject to the GAO timing rules.
GAO protests
The Government Accountability Office is the most common forum for federal-construction protests. GAO protests are governed by the Competition in Contracting Act and 4 CFR Part 21. GAO has 100 days to issue a decision after the protest is filed, with an expedited 65-day track available for some protests. The procedural rules are well-established and the decisions are reasoned and published, which means the GAO record is the body of precedent most procurement protest practice runs on.
Court of Federal Claims protests
The U.S. Court of Federal Claims has bid protest jurisdiction under 28 U.S.C. § 1491(b). COFC is the most formal and most expensive of the three forums and is generally used when the stakes are large enough to justify the cost, when the protester needs to pursue claims beyond what GAO is empowered to decide, or when the protester has run out of GAO options. COFC decisions are appealable to the Federal Circuit Court of Appeals.
Most contractors start at GAO
For a typical building-construction GC, the GAO is the default forum. Agency-level protests work for narrow, clear-cut issues. COFC is reserved for protests where the contractor is committed to the legal cost. The choice between forums is made with counsel and is sometimes shaped by the contractor’s appetite for the timeline and the appeal pathway each forum offers.
Filing windows and the CICA automatic stay
Bid protest deadlines are short and strict, and missing them is fatal to the protest regardless of how strong the underlying issue is. The deadlines run on calendar days, not business days, and the trigger is usually defined as the date the protester knew or should have known the basis for the protest.
Pre-award protests of solicitation terms
A protest of the solicitation terms (a pre-award protest, challenging something defective about the solicitation itself rather than the evaluation) generally has to be filed before bid opening on a sealed bid procurement, or before the proposal due date on a negotiated procurement. The rationale is that a contractor cannot wait until after losing the procurement to raise an issue with the solicitation that was apparent from the start. Filing a pre-award protest also requires the contractor to decide before bid submission whether to pursue the protest path or the bid-and-hope-for-the-award path.
Post-award protests
A post-award protest generally has to be filed within 10 days of the date the protester knew or should have known the basis for the protest. The trigger is typically the agency’s post-award notice or the contractor’s debriefing. The 10-day window is short. The contractor has to decide quickly whether the issue justifies a protest, retain counsel familiar with the relevant forum, gather the procurement record, and file before the window closes.
The CICA automatic stay
A timely GAO protest filed within the CICA stay window triggers an automatic stay of contract performance under 31 U.S.C. § 3553. For pre-award protests, the stay generally applies when the protest is filed before the agency issues an award. For post-award protests, the stay applies when the protest is filed within 10 days of award or within 5 days of a required debriefing, whichever is later. The stay holds contract performance until the GAO decision is issued.
The agency can override the stay in some circumstances by making a written determination that proceeding with performance is in the best interest of the government. Override is not routine; it requires the agency to formally justify the decision, and contractors with a strong protest position sometimes preserve the stay through the protest decision. For an awardee, the stay matters in the opposite direction: it pauses the work while the protest is decided, which carries cost and schedule consequences.
The deadlines run on calendar days, not business days, and missing them is fatal to the protest regardless of how strong the underlying issue is.
What a protest actually costs to run
A bid protest is not a free option. The cost includes counsel time at procurement-litigation rates, the contractor’s own time on the protest, the document collection and production effort, and the opportunity cost of resources committed to the protest rather than to the next bid. The cost varies widely with the forum and the complexity of the issue.
An agency-level protest is the cheapest of the three. The procedure is administrative, the timeline is short, and the contractor sometimes runs the protest with limited counsel involvement. A GAO protest is typically more expensive: the procedural rules require formal pleadings, the agency report has to be reviewed, supplemental protests sometimes follow, and the case can run to the full 100-day timeline. A COFC protest is the most expensive of the three, with full federal court litigation costs.
The contractor’s internal cost is also meaningful. Document collection, witness preparation if testimony is required, and the time the firm’s leadership spends on the protest add up. A protest the firm pursues over six weeks at GAO is six weeks of senior-team attention pulled away from the rest of the bid pipeline.
When a protest makes strategic sense
Most lost federal bids are not protested. The contractor reads the agency’s evaluation, attends the debriefing if one is offered, learns what can be learned, and moves on to the next opportunity. Protests fit a smaller set of situations.
There’s a real basis to believe the procurement was conducted improperly
The strongest protests are the ones where the contractor has identified a specific, articulable issue with how the agency ran the procurement: an evaluation factor was applied differently to different offerors, the awardee was non-responsive on a requirement the contractor met, the agency failed to follow its own stated evaluation criteria, or the solicitation itself was defective. Vague dissatisfaction with the outcome is not grounds. A protest filed without a strong basis damages the contractor’s relationship with the agency and rarely produces a useful outcome.
The award is large enough to justify the cost
Protest economics matter. A protest costing $40,000 to $150,000 in counsel fees on a $2 million construction award is harder to justify than the same protest cost on a $40 million award. The contractor weighs the protest cost against the probability of a successful outcome and the value of the award if the protest succeeds.
The contractor needs to preserve a position on future procurement
Sometimes the protest is about more than the immediate award. A solicitation defect that affects multiple upcoming procurements, an evaluation pattern that puts the contractor at structural disadvantage, or an issue that will affect subsequent task orders under an IDIQ vehicle can all justify a protest even when the immediate award is small. The protest is preserving the contractor’s position on future work.
Vague dissatisfaction with the outcome is not grounds. A protest filed without a strong basis damages the contractor’s relationship with the agency and rarely produces a useful outcome.
Building a protest position before the bid is filed
Most successful protests are not built from scratch in the 10 days after award. They are built on the documentation discipline the contractor maintained during the bid itself. The compliance matrix that mapped every solicitation requirement to a response location becomes evidence that the contractor met requirements the awardee may not have. The proposal narrative that addressed the agency’s evaluation factors becomes evidence that the contractor responded to the criteria the agency said it would weigh. The bid file that captured every amendment, every Q&A, and every clarification becomes the record the protest counsel works from.
Contractors who run a tight bid file rarely need to scramble for documentation when a protest situation arises. Contractors who run a loose bid file find themselves trying to reconstruct the procurement record from memory and from email archives during the same 10 days they should be deciding whether to protest at all. The bid documentation discipline is what converts a possible protest into a workable protest.
The ScalaBid Submission Package produces the four documentation components (proposal narrative, compliance matrix, indexed drawing set, action checklist) that survive the bid window as a structured record. On the rare procurement where the contractor needs to evaluate a protest after losing, that record is what counsel works from. Most protests never get filed, but the discipline that supports the option carries through to every other part of how the firm runs federal work.
For most contractors, the right operational posture is to treat protests as a low-frequency tool that is occasionally the right answer and almost never the first answer. The discipline that makes protests viable when they are the right answer is the same discipline that wins federal work in the first place.
Related field notes
- Federal construction bidding: a working guide · The broader procurement framework protests sit inside.
- Finding construction opportunities on SAM.gov · The discovery work that precedes any protest decision.
- MILCON, GSA, and DOE construction · How protest patterns differ across federal-construction programs.
- Compliance matrix · The bid-file discipline that supports protest decisions.