Last reviewed on May 12, 2026.
What OCI is
An Organizational Conflict of Interest (OCI) exists when a contractor's other activities, relationships, or contracts could compromise its objectivity, give it an unfair competitive advantage, or impair its ability to provide impartial advice to the government. OCI is distinct from personal conflicts of interest (which involve individual employees) and from procurement integrity violations (which involve disclosure of source selection information). OCI is about the contractor entity's structural position.
The framework is in FAR Subpart 9.5. Contracting officers have substantial discretion to identify, evaluate, and require mitigation of OCIs. Successful OCI challenges are a common basis for bid protests, particularly when an incumbent's other contracts arguably positioned it advantageously for a follow-on competition.
The three OCI types
1. Unequal access to information
A contractor performing one contract gains access to non-public information that gives it an advantage when competing for another contract. Common scenarios:
- An incumbent on a support services contract sees agency budget data not available to other bidders
- A contractor developing a requirement sees draft solicitation language
- A contractor providing systems engineering sees architecture decisions before they're public
2. Biased ground rules
A contractor helps the government draft the requirement, specification, or evaluation criteria for a procurement and then bids on that same procurement. The risk is that the contractor shaped the rules to favor itself. Common scenarios:
- A contractor writes the statement of work for a follow-on contract
- A contractor drafts evaluation criteria that match its own capabilities
- A contractor develops technical specifications during an advisory engagement
3. Impaired objectivity
A contractor is asked to evaluate or oversee work performed by an affiliate, customer, or its own prior work. The contractor's objectivity is structurally compromised. Common scenarios:
- A contractor evaluates proposals from competitors that are also subcontractors on the contractor's other work
- A contractor provides oversight on a system it previously developed
- A contractor performs independent verification of work done by an affiliate
How OCI is identified
OCI identification happens in two places: the contractor's own internal review and the contracting officer's evaluation.
- Solicitation disclosure. Many solicitations require offerors to disclose potential OCIs in their proposals. The disclosure should describe other contracts the offeror holds that touch on the same scope, agency, or subject matter.
- Contracting officer review. The CO evaluates disclosures, looks at the offeror's broader contract portfolio, and determines whether a significant OCI exists.
- Competitor allegations. Disappointed bidders frequently allege OCI as a basis for protest. The CO must respond to allegations even when the offeror did not self-disclose.
- GAO and court review. When OCI is contested, the forum reviewing the protest evaluates whether the CO's OCI determination was reasonable and documented.
Mitigation plans
When OCI is identified, the contractor can propose a mitigation plan. The plan describes specific measures to address the conflict. Mitigation effectiveness depends on the OCI type:
- Unequal access mitigations. Firewalls between teams, restricted information access, employee non-disclosure protections, and personnel screening. Reasonably effective when properly implemented.
- Biased ground rules mitigations. Disqualification from competing on work the contractor helped shape. This is the most common mitigation because alternatives are weak — once the contractor has shaped the rules, no firewall undoes the effect. Some agencies allow narrow exceptions when the shaping work was years earlier and the government has substantially modified the resulting solicitation.
- Impaired objectivity mitigations. Genuinely difficult. Mitigation usually requires the contractor to decline the oversight or evaluation work, or to have the conflicting affiliate excluded from the work being evaluated.
A common contracting officer outcome: accept a mitigation plan for unequal access OCIs, require disqualification for biased ground rules OCIs, and require restructuring for impaired objectivity OCIs.
What an OCI mitigation plan should contain
- Clear description of the OCI risk — which type, which contract(s), which scope
- Identification of the specific information, decisions, or evaluations creating the conflict
- Personnel firewall measures — who is restricted from working on which contracts, with documented procedures
- Information access controls — system permissions, document handling, briefing exclusions
- Reporting and audit provisions — how the contractor will demonstrate ongoing compliance
- Escalation procedures when new conflicts emerge during performance
- Senior management certification of the plan
The mitigation plan is a contractual commitment. Failure to implement it during performance can result in contract termination and protest risk.
OCI in protests
OCI allegations are among the most common protest grounds. A typical OCI protest argues:
- The awardee had a significant OCI that the agency failed to identify or evaluate
- The agency identified an OCI but accepted an inadequate mitigation plan
- The protester would have won absent the OCI advantage
GAO sustains OCI protests when the record shows the agency did not meaningfully evaluate the conflict or where the mitigation plan is plainly inadequate. Reasonable, documented agency analysis generally survives protest review even when the protester disagrees with the conclusion. For broader protest mechanics, see GAO bid protests.
How to manage OCI risk proactively
- Maintain a current contract portfolio map. Know what work the firm holds, with which agency, and what subject matter. Without this map, OCI disclosure is guesswork.
- Screen new pursuits against the portfolio. Before investing capture resources, evaluate whether the firm's other work creates a non-mitigable conflict.
- Maintain documented firewalls. If the firm holds multiple potentially conflicting contracts, documented separation procedures make later mitigation plans credible.
- Plan around biased-ground-rules work. Accepting a requirements-shaping contract typically means giving up the eventual performance contract. Decide whether that trade is worth it before signing.
- Disclose proactively. Late OCI disclosures are worse than early ones. If a potential conflict exists, surface it in the proposal rather than hoping it goes unnoticed.
- Read flow-down clauses in subcontracts. OCI obligations flow to subs in many contracts. Subcontractors' other work can create OCI risk for the prime.
Common mistakes
- Treating OCI as personal conflict. Personal conflicts (employee financial interests) are separate. OCI is about the contractor entity's position.
- Filing thin mitigation plans. A boilerplate firewall plan without specifics rarely satisfies a careful contracting officer or survives protest review.
- Ignoring affiliate conflicts. Conflicts created by parent companies, sister entities, or majority-owned subsidiaries count. Corporate structure does not insulate.
- Underestimating biased-ground-rules implications. Helping draft a requirement usually disqualifies the firm from the follow-on. Plan accordingly.
- Late disclosure. Disclosing an OCI in your protest response after losing the contract is worse than disclosing it in the proposal.
- Skipping internal OCI review on pursuits. A 15-minute conflicts check before authorizing capture investment saves substantial later cost.