Organizational conflicts of interest sink awards more often than contractors expect, and the rules governing them sit in FAR Subpart 9.5, a section every proposal team should read before, not after, a protest lands. The subpart does not ban conflicts outright — it requires contracting officers to spot them early, document their analysis, and either mitigate, waive, or exclude the offending firm.
Background
FAR 9.505 lays out two guiding principles behind the entire subpart: preventing a contractor's judgment from being biased by a conflicting role, and preventing any competitor from holding an unfair, unauthorized information advantage over the rest of the field. Those two principles generate three canonical conflict types that recur across bid protests: unequal access to information, biased ground rules, and impaired objectivity.
Unequal access arises when a contractor has proprietary or source-selection information — through a prior contract, an incumbent role, or access to non-public data — that other offerors cannot get. Biased ground rules arise when a contractor writes or influences the specifications, statement of work, or evaluation criteria for a procurement it then competes for. Impaired objectivity arises when a contractor is asked to evaluate, test, or advise on work in which it has a financial or organizational stake, so its recommendations cannot be trusted as independent.
FAR 9.508 illustrates all three with nine lettered fact patterns, (a) through (i), that contracting officers still cite directly in source selection documentation. Two are especially instructive for IT and technical support contractors. Under 9.508(e), a contractor that develops specifications for a competitively acquired piece of IT hardware "should be excluded from the initial follow-on" acquisition of that same hardware — the firm that wrote the spec cannot then compete to fill it. Under 9.508(f), a contractor that defines the performance characteristics of a new rocket fuel cannot subsequently win the follow-on contract to develop or produce that fuel. Both examples describe biased ground rules, but the underlying logic — don't let a firm grade its own homework — applies just as directly to impaired-objectivity situations.
Key Details
FAR 9.504 puts the burden of identification on the government, not the contractor. The contracting officer must identify and evaluate potential organizational conflicts of interest "as early in the acquisition process as possible," obtain legal and technical advice as needed, and, before award, give any contractor with an unresolved conflict written notice of the conflict, the facts supporting it, and a chance to respond. Award can still proceed over an unresolved conflict, but only through a documented waiver issued under FAR 9.503 — a step that requires the agency to put its reasoning on the record, not simply assert that a conflict was "considered."
That documentation requirement is where agencies most often fail, and a recent Government Accountability Office decision shows exactly what thin documentation looks like. In Castro & Company, LLC, B-423689, decided in November 2025, GAO sustained a protest against the Federal Election Commission after the contracting officer stated only that she "considered whether prior contracts with CME created a conflict of interest" — without explaining what she actually examined, what mitigation measures she evaluated, or how a proposed firewall addressed the specific impaired-objectivity concern raised by the protester. GAO characterized that language as a bare conclusory statement rather than a meaningful investigation, and sustained on impaired-objectivity grounds.
The case matters beyond its facts because of what it says about firewalls generally. Firewalls — internal information barriers that wall off employees working on a conflicted matter from the rest of the firm — are the standard mitigation tool for unequal-access conflicts, where the problem is who has seen what data. They do not, by themselves, cure impaired objectivity. Impaired objectivity is a financial or organizational stake problem, not an information problem: restricting who sees which documents does nothing to remove the contractor's incentive to favor an outcome it has a stake in evaluating. Commentary on the decision from the bid protest bar, including SmallGovCon's analysis, makes the same point: GAO found the agency's OCI analysis had been reduced to a "bare statement" that the contracting officer "considered" the issue, without explaining what she analyzed or how her conclusion addressed the specific conflict raised.
What It Means for Contractors
For a contractor pursuing a follow-on contract, the practical lesson from FAR 9.508(e) and (f) is to flag your own OCI exposure before the agency does. If your firm wrote specifications, developed performance requirements, or advised on the acquisition strategy for a procurement, assume you are excluded from directly competing for the resulting work unless the agency documents a waiver, and raise the issue with the contracting officer rather than waiting to be protested off the award. Waiting invites exactly the kind of late-stage protest that delayed the FEC's contract in Castro & Company.
For a contractor structuring a mitigation plan around a potential impaired-objectivity conflict, an information firewall alone will not satisfy a contracting officer's FAR 9.504 obligations, and it will not survive a protest that challenges it on the merits. A credible mitigation plan for impaired objectivity has to remove or offset the financial stake itself — through subcontracting the conflicted piece of work to an unaffiliated firm, divesting the relevant business unit, or structuring the contract so the firm has no downstream interest in the outcome it is asked to evaluate. Contractors should also expect, and request, that the contracting officer's OCI analysis be documented in the file with specific reasoning, since a generic statement of "consideration" is now on record as insufficient to survive a GAO challenge.
Finally, for contracting officers and the contractors advising them informally, Castro & Company is a reminder that the FAR 9.504 notice-and-response obligation is not a formality to be satisfied with a form letter. A contractor facing an OCI exclusion is entitled to written notice of the specific facts and reasons behind it and a real opportunity to respond before award — and an agency that skips straight to a conclusory waiver risks losing the protest even when its underlying instinct about the conflict was correct.
