OCI is one of the quietest deal-killers in federal contracting. A firm can show up with the lowest price, the strongest past performance, and the smartest technical approach, and still get eliminated, or quietly barred from a follow-on worth far more than the bid in front of it, because of a conflict nobody flagged in time.
Organizational conflict of interest, governed by FAR Subpart 9.5, is not about an employee taking a gift or a manager hiring a relative. It is about whether your company's other work, relationships, or access give it an unfair advantage in a competition, or make it unable to be objective once the work starts. It is structural, it is easy to miss, and the penalties reach well beyond the single award in question.
This guide walks through what an OCI actually is, the three recognized types, how each one gets you disqualified, how mitigation works, and how to catch OCI during triage instead of after a competitor's protest.
What an OCI actually is
An organizational conflict of interest exists when a contractor's other activities or relationships could keep it from giving impartial advice, give it an unfair competitive advantage, or bias the ground rules of a competition. The government's concern is not your ethics. It is the integrity of the procurement and the work that follows it.
The distinction that trips people up is that OCI is about the organization, not the individual. A personal conflict of interest is one employee's financial or family entanglement. An OCI is your whole company being on two sides of a situation at once, because of what it does elsewhere. That difference is why OCI cannot be fixed by reassigning one person, and why it shows up as a company-level eligibility question, sometimes before you have written a single proposal page.
The three types of OCI
FAR 9.5 and decades of GAO and Court of Federal Claims decisions sort almost every real-world conflict into three buckets. Knowing which bucket you are in tells you whether the problem is fixable and how.
1. Unequal access to information
This arises when your firm, through other work, holds nonpublic information that competitors do not, and that information would give you an edge. The classic case is a support contractor who, while helping a program office, sees competitors' proprietary data, cost information, or source selection material, then wants to bid the next competition.
Why it matters: even the appearance that you could have used that information taints the competition. How it is usually handled: firewalls and nondisclosure controls that wall off the people with access from the people writing the proposal. Of the three types, this is the most often mitigable.
2. Biased ground rules
This is the most dangerous type. It arises when your firm helped set the rules of the very competition it now wants to win, by writing the statement of work, drafting specifications, or shaping the evaluation criteria. You effectively helped design the playing field, so you cannot then compete on it.
Why it matters: you may be barred entirely from bidding the resulting contract, and sometimes from related follow-on work, because no firewall can undo the fact that you wrote the requirement. This is the conflict behind the "we can't bid that because we helped scope it" conversation. Advisory and systems-engineering support work is valuable, but it can quietly forfeit your right to compete for the production or operational contract that comes after.
3. Impaired objectivity
This arises when your firm's work would require it to evaluate or oversee itself, an affiliate, or a competitor. If the task is to assess the performance of products or services your own division sells, you cannot be objective, and the government cannot trust the assessment.
Why it matters: it goes to the credibility of the work itself, not just the fairness of the competition. How it is handled: sometimes by recusal or subcontracting the conflicted portion to a neutral party, and sometimes only by declining the work. You see structured versions of this on large portfolios. The MDA MAPSS portfolio, for example, is built around an OCI regime that decides who can bid which tranches precisely to manage impaired objectivity across related work.
The consequences are bigger than one bid
An unmitigated OCI can cost you in four ways at once. You can be disqualified from the current competition. You can be barred from a follow-on or related contract, the future-work trap that often dwarfs the bid you were chasing. You can be knocked out by a protest, because a competitor who spots your conflict will absolutely raise it. And even where mitigation is allowed, it carries real cost: firewalls, recusals, sometimes divestiture of a business line.
The biased ground rules trap deserves special attention. Firms take on advisory, planning, or engineering support because it is steady revenue and builds agency relationships. But if that work shapes a requirement, it can lock you out of competing for the work it generates, sometimes across an entire line of future contracts with that customer. The advisory engagement that looked like a foot in the door can become the reason you are shut out of the room.
How OCI hides in a solicitation
OCI rarely announces itself with a banner. It shows up as a dedicated OCI section, agency-specific conflict clauses, representations that require you to disclose conflicts, language about prior or concurrent contracts, and a requirement to submit an OCI mitigation plan with your proposal. Sometimes it is a single sentence buried in Section H or the instructions in Section L. Because OCI clauses are often agency-crafted rather than a single standard FAR clause, they are easy to skim past. If you want a primer on reading clause language without drowning in it, see how to read FAR clauses without losing your mind.
Miss the OCI language and you face two bad outcomes: you pursue something your company is not actually eligible to win, or you fail to submit a required mitigation plan and get eliminated on a technicality. Both are avoidable with a careful first read.
Mitigation: firewall, recuse, or walk
When an OCI is identified, the question becomes whether it can be neutralized. Common mitigation approaches include information firewalls that separate conflicted staff from the pursuit, recusal from the specific tasks that create the conflict, subcontracting the conflicted scope to a neutral party, and in the hardest cases, divesting the business line that creates the conflict. The mitigation plan you submit has to be credible to the contracting officer, not just a paragraph promising good behavior. And some conflicts, especially biased ground rules, cannot be mitigated at all. The only fix is to not bid.
How to handle OCI in your pursuit process
Treat OCI as a triage step, not a post-award surprise. Before you commit real proposal hours:
- Map your current and recent contracts against the new opportunity. Ask where you have access, where you helped set rules, and where you would end up evaluating yourself or an affiliate.
- Decide early whether you can mitigate or whether the conflict is fatal. A firewall takes time to stand up and document.
- Surface OCI in your bid/no-bid decision, alongside price-to-win and capability fit, not after the team is emotionally committed to the pursuit.
- Watch your teaming arrangements. A subcontractor's conflict can taint the prime. The teaming guide covers how to vet partners before you bind them in.
A real-world pattern
Here is the kind of catch that pays for itself. A team is pursuing an opportunity and, buried in the solicitation, there is language indicating the awardee would be restricted from competing on future contracts with that agency, a biased-ground-rules outcome tied to the scope of the work. A team that spots that during the first read makes a clear-eyed decision about whether the single award is worth forfeiting a pipeline. A team that misses it can win the battle and lose the war. Surfacing that one requirement early is often the difference between a smart pursuit and an expensive mistake.
Bottom line
OCI is structural, it hides in plain sight, and its penalties extend far past a single award. The three types are unequal access to information, biased ground rules, and impaired objectivity, and they range from usually fixable to fatal. The firms that handle OCI well find it during the first read of a solicitation, weigh it deliberately in their go decision, and never let an advisory engagement quietly cost them a bid they wanted.
For how OCI fits into the rest of a solicitation review, see how to evaluate an RFP in under 10 minutes, build the requirement into your compliance matrix so the mitigation obligation does not get lost, and read Sources Sought vs RFI vs RFP to understand how early advisory work can create the conflict in the first place.
This guide is general information, not legal advice. OCI determinations are fact-specific and decided by the contracting officer, with review by GAO or the courts. Consult qualified government contracts counsel about your specific situation.