Bid protests: common grounds and how agencies reduce the risk

Reference article · 5 min read

A bid protest is a formal objection to how an agency ran a solicitation or made an award. It is filed by a party with an interest in the outcome, usually a firm that submitted or wanted to, and it asks the agency, or a body above it, to correct something before the contract is signed. Protests are an ordinary feature of public purchasing rather than proof that something went wrong.

Deadlines, forums, and remedies are set by state statute, local ordinance, and the agency's own purchasing policy, and they vary a great deal. Some jurisdictions require a protest within days of the event challenged, others measure from the notice of intent to award. Appeals may run to a purchasing director, a hearing officer, the governing body, a state administrative body, or a court. Confirm what applies to your solicitation with your purchasing office and counsel rather than relying on any general description, including this one.

Grounds that actually appear

• Ambiguous or restrictive specifications. The solicitation can be read two ways, or it names features only one product has without a functional justification.
• Unequal treatment of bidders. One firm received information, an extension, or a clarification opportunity that others did not.
• Scoring inconsistent with the stated criteria. The evaluation used factors or weights that were not published, or scores do not track the written comments.
• Responsiveness determinations. A submission was rejected or accepted over a material requirement, and the protester disputes whether the deviation was waivable.
• Responsibility determinations. The agency concluded a firm could or could not perform, and the protester challenges the basis, often references, financial capacity, or licensing.
• Late or incomplete submissions. A submission arrived after the deadline or omitted a required form, and the argument is about the clock, the portal, or waiver.

A protest arguing only that the protester's product is better rarely succeeds. What moves a decision is a documented departure from what the solicitation said the agency would do.

The usual stages

1. Pre-award protest. Filed against the terms of the solicitation, early enough that the agency can amend by addendum if the objection has merit.
2. Post-award protest. After the notice of intent to award is posted, interested parties have a defined window to challenge the selection.
3. Agency review and decision. The purchasing officer or a designee reviews the protest against the procurement record and issues a written determination.
4. Appeal. A protester who disagrees may have an internal appeal, an administrative hearing, or an outside forum, depending on the jurisdiction.
5. Resolution. Denial and award as planned, corrective action such as rescoring or reissuing an amended solicitation, cancellation, or a change in the award.

Effect on the award timeline

Most rules hold the award while a protest is pending, with an exception where the agency documents an urgent need and obtains approval. Expect the calendar to move. A first level decision can take weeks, and an appeal adds more. The costs are staff hours to assemble the record, legal review, and delay to the program the contract supports. Where a project has a fixed date set by a grant period, a failing legacy system, or a fiscal year, build protest time into the schedule rather than assuming the best case.

Habits that prevent protests

• Answer every question in a written addendum. Post questions and answers to all participants, and give no substantive answer to one firm by phone or email.
• Amend rather than explain. If an answer changes a requirement, issue it as an addendum and extend the due date when firms need it.
• Publish the evaluation method and follow it. State the factors, the weights, and how price is treated, then score on those and nothing else.
• Keep evaluation notes. Individual notes tied to criteria, dated and retained, plus consensus notes that say why a score changed.
• Clarify consistently. Give every firm in the same position the same opportunity, and record responsibility findings the same way.
• Offer debriefings. A short factual review of that firm's own proposal against the criteria settles many complaints before they become protests.

When a protest letter arrives

1. Log the date received and calculate the response deadline under your policy.
2. Route contact through one person and stop informal discussion of the procurement.
3. Preserve the record: solicitation, addenda, questions and answers, submissions, scoring sheets, evaluator notes, correspondence, and portal logs.
4. Read the protest ground by ground against that record, asking whether the agency did what the solicitation said it would do, and bring in counsel before anything is committed in writing.
5. Consider corrective action honestly, then issue a written decision that addresses each ground and states what happens next.

What to build into the solicitation

• The protest procedure. Where to file, the deadline, the required content, and who decides.
• The evaluation criteria and weights, stated plainly, with the role of price described.
• A single point of contact, and a prohibition on contacting other staff or elected officials.
• Addendum acknowledgment and the authoritative clock, so the record shows each firm received every change and which time stamp governs the deadline.
• A reservation to waive minor informalities, with material requirements identified where you can.

HQT works with state and local agencies on technology requirements and evaluation documentation that hold up on review.

Frequently asked questions