13.1 Bid Protests (FAR Part 33)

13.1 Bid Protests (FAR Part 33)

Quick Answer: Manage Disagreements (FAI 3.1.4, about 10 questions) includes bid protests under FAR Part 33. Know the conceptual forums (agency, GAO, Court of Federal Claims), timely filing and stay themes, CO duties when a protest is filed, corrective action, independent judgment, and pre-award vs post-award differences. Document everything; do not “win” by hiding the file or ignoring legal process.

Award is not finished when the SSA signs a selection decision. Disappointed offerors may protest alleged violations of procurement law or the solicitation’s ground rules. Part 33 is the FAR home for protests (Subpart 33.1) and for disputes after award (Subpart 33.2—previewed in Section 13.3 and expanded in Post-Award chapters). On CON 3990V, protest items test whether you protect competition integrity and the record, not whether you can litigate like a protest counsel.

Why protests matter to contracting professionals

Protests are not personal attacks on the CO—they are a public accountability mechanism. They force agencies to:

Exam stance: Treating a protest as “nuisance to ignore” or “automatically suspend the mission forever without process” are both wrong. The professional response is timely notice, complete documentation, legal coordination, and independent judgment on remedies and overrides.

Conceptual protest forums

CON 3990V expects a map of forums, not a case-law treatise.

1. Agency-level protests

An agency protest is filed with the agency (often with the Contracting Officer or a designated agency protest official, per agency procedures). Themes:

• Can be faster and less formal than external forums.
• May allow the agency to fix issues before external litigation heat.
• Still requires impartial consideration—do not treat it as a rubber stamp for the original decision.
• Filing at agency level does not always prevent later GAO/COFC action; rules on timeliness, dismissal, and forum choice are technical—know that procedure matters and coordinate with counsel.

CO role: Receive, acknowledge, assemble facts, avoid ex parte freelancing that undercuts the official response, and implement decisions of the deciding official.

2. GAO protests

The Government Accountability Office (GAO) is a primary external forum for bid protests under the Competition in Contracting Act (CICA) framework. Conceptual points:

• Protesters allege the agency violated statute or regulation in the competition or award.
• GAO issues recommendations (agencies nearly always follow them as a practical matter; CICA stay rules create strong compliance incentives).
• Focus is typically procurement law compliance and evaluation fairness—not a full trial of every business grievance.
• Agencies must produce an agency report / administrative record themes: evaluation documents, solicitation, communications, source selection decision, and relevant correspondence.

Exam cue: GAO is not “just another email complaint.” It triggers formal process, documentation obligations, and often stay analysis.

3. Court of Federal Claims (COFC)

The U.S. Court of Federal Claims can hear bid protest actions under federal jurisdiction concepts. Compared with GAO at the conceptual level:

You need awareness of multiple forums, not a preference ranking for every scenario. When in doubt on real cases: notify counsel and leadership early.

Timely filing themes (structure without fake day counts)

Exact calendar rules can be detailed and are easy to misstate under closed-book pressure. CON 3990V-level mastery emphasizes structure:

1. Timeliness is jurisdictional-feeling in practice — late protests are often dismissed without reaching the merits.
2. Solicitation defects should generally be protested before proposals are due (or as early as practicable once the defect is apparent)—waiting until after losing to attack a known RFP flaw is a classic untimely pattern.
3. Award challenges must be filed within the applicable post-debriefing / post-knowledge windows under the governing forum’s rules.
4. Debriefings matter: they educate unsuccessful offerors and can affect when the protest clock runs; mishandled debriefs can increase protest risk and confusion.
5. Stay concepts depend on timely filing at the right forum under CICA-type rules—untimely or wrong-forum filings may not trigger the automatic stay the protester hopes for.

Teach the principle: File early when the defect is known; document debrief content carefully; never invent exact day counts on the exam if you are unsure—apply the “timely / untimely / stay” logic.

Scenario — Known solicitation ambiguity. Offerors ask about conflicting evaluation language; agency ignores it. After award, the loser protests the ambiguity. Forum may ask: should this have been protested pre-award when apparent? Lesson: fix solicitations early; protest counsel (and examiners) care about when the issue became apparent.

Stay of award / performance concepts

A stay can prevent award or stop performance while a protest is pending, protecting the competitive status quo.

Exam trap: “A protest always permanently cancels the requirement.” False—protests address process legality; the mission may continue after resolution, corrective action, or lawful override.

Exam trap: “Override is automatic whenever the general wants it.” False—override is a documented legal decision, not a preference.

Contracting Officer responsibilities when a protest is filed

When notice of protest arrives, the CO’s professional checklist (conceptual) is:

1. Acknowledge and calendar — capture filing date/forum; start the process clock for responses and stays.
2. Notify — program office, legal counsel, small business (if size/socioeconomic issues), SSA/source selection team as needed, and higher review per agency policy.
3. Preserve the record — freeze spoliation risk: evaluation worksheets, emails, consensus reports, PNM, competitive range memos, debrief scripts. Do not “clean up” the file after protest notice.
4. Suspend or proceed lawfully — apply stay rules; if override is considered, build the justification with counsel.
5. Support the agency report / response — factual accuracy, complete exhibits, honest description of what happened (including mistakes).
6. Consider corrective action early if the file shows clear error—defending a broken process wastes time and credibility.
7. Maintain integrity of communications — no informal side deals with the protester or awardee that contradict the official process; no leaking protected source selection information.
8. Independent judgment — recommendations from program or counsel inform the CO; the CO still owns contracting decisions within authority and must not sign false or unsupported positions.

Independent judgment is a recurring CON 3990V Guiding Principles echo: you are not a stenographer for the PM’s anger at the protester, nor a rubber stamp for “just re-award to the same firm without reevaluation” when the record is flawed.

Corrective action

Corrective action means the agency voluntarily (or after recommendation) fixes the procurement problem. Examples:

• Amend the solicitation and allow revised proposals.
• Reopen discussions with competitive-range offerors.
• Reevaluate proposals under stated factors with a clean team or corrected standards.
• Conduct a new competitive range determination.
• Terminate or rescind an improper award and re-compete or re-select lawfully.
• Provide a required debriefing that was withheld improperly (as part of a broader fix).

Exam cue: Corrective action is a strength when the file is weak—not an admission of personal failure. Defending the indefensible is the failure mode.

Pre-award vs post-award protest differences

Scenario A — Pre-award. A brand-name-or-equal specification effectively sole-sources without justification. Competitor protests before proposals due. CO focus: Can the requirement be opened up? Is the restriction justified and documented?

Scenario B — Post-award. Unsuccessful offeror learns at debrief that evaluators used an unstated “incumbent knowledge” factor. CO focus: Is the allegation true? Does the record support reevaluation/corrective action?

Scenario C — Responsibility challenge style issues. Protest alleges awardee is nonresponsible or that nonresponsibility of the protester was unfair. Link to Part 9 themes (Chapter 12.3): process and evidence still matter.

Documentation and the administrative record

Protest defense (and corrective action design) lives or dies on the file created before the protest:

• Solicitation and amendments
• Evaluation plans / standards applied
• Individual and consensus evaluation reports
• Competitive range determination
• Discussion letters and offeror responses / FPRs
• Price/cost analysis and PNM themes
• Source selection decision document
• Responsibility determination
• Debriefing content
• Contemporaneous emails that show actual decision rationale (dangerous if they contradict the official decision)

Guiding principle: Write the award as if a stranger will read it under protest pressure—because that is exactly what happens.

Connecting protests to the Award phase flywheel

Protests often allege failures earlier in Award and Pre-Award:

• Unstated evaluation criteria (12.2)
• Unequal discussions (12.2)
• Missing fair-and-reasonable price support (11.x)
• Weak responsibility file (12.3)
• Restrictive specifications or poor competition planning (6.x–8.x)
• Small business / set-aside process errors (9.x; Section 13.2)

Prevention beats litigation: clear solicitations, stated factors only, equal treatment, complete documentation, and honest debriefs reduce protest vulnerability.

CON 3990V closed-book anchors

• Part 33 Subpart 33.1 = protests; forums include agency, GAO, COFC.
• Timeliness + stay structure > memorizing every day count under uncertainty.
• CO duties: notify, preserve record, support response, consider corrective action, independent judgment.
• Override of stay requires documented legal basis—not raw schedule panic.
• Pre-award attacks ground rules; post-award attacks evaluation/award outcomes.
• Corrective action restores lawful competition; cosmetic papering fails.

---

Bottom line: Bid protests test whether the acquisition was fair and documented. Master forum awareness, timeliness/stay concepts, CO process duties, corrective action courage, and pre- vs post-award differences. On CON 3990V, the winning mindset is integrity under pressure—defend sound awards with a complete record, and fix broken ones without ego.