Organizational Conflict of Interest (OCI): What Federal Contractors Must Know
OCI can disqualify you from federal contracts you've worked years to win. Learn the three types of OCI, FAR mitigation requirements, and how to avoid common OCI traps.
You have invested months in capture activities, built agency relationships, and submitted a strong proposal. Then the contracting officer issues a show cause notice — or simply excludes your firm — because of an Organizational Conflict of Interest.
OCI is one of the most misunderstood and underestimated risks in federal contracting. Getting it wrong can mean losing a contract you've won, being excluded from future competitions, or facing a sustained bid protest that puts your program work on hold.
This guide explains what OCI is, the three types that matter, and how to identify and manage OCI risks before they derail your business development.
What Is an Organizational Conflict of Interest?
An Organizational Conflict of Interest exists when, because of other activities or relationships, a contractor's ability to give impartial advice, perform fairly, or compete fairly may be impaired — or when the contractor has an unfair competitive advantage because of access to non-public information.
FAR Subpart 9.5 is the primary regulatory framework. Contracting officers are required to identify and mitigate actual or potential OCIs before award.
The core concern: Government procurement should be fair, and advisors who help the government make decisions should not benefit from those decisions. OCI rules prevent the government from inadvertently giving one contractor an unfair edge.
The Three Types of OCI
1. Biased Ground Rules
What it is: A contractor helps develop the requirements, specifications, statement of work, or evaluation criteria for a subsequent procurement — then competes for that procurement.
The problem: The contractor who wrote the SOW may have unconsciously (or consciously) written it in a way that favors their own capabilities, making it harder for competitors to win.
Example: A systems engineering firm helps the government develop the technical requirements for a major software system. When the government then competes the software development contract, the systems engineering firm is excluded from bidding because it helped write the requirements.
Common trigger: Advisory and Assistance Services (A&AS) contracts. If you provide technical advisory services that result in specifications for a future acquisition, you may be OCI-precluded from competing for the resulting contract.
FAR reference: FAR 9.505-1.
2. Impaired Objectivity
What it is: A contractor evaluating or providing advice on a government decision also has a financial interest in the outcome of that evaluation.
The problem: You cannot be expected to objectively evaluate your own products, services, or work — or those of a company you have a financial relationship with.
Example: A contractor performs post-award evaluation of software systems delivered by a prime contractor. If the evaluating contractor has a teaming relationship with that prime, or is a subcontractor on a related program, their evaluation objectivity is impaired.
Common trigger: Independent Verification and Validation (IV&V) contracts. If you win an IV&V role, you are typically excluded from competing as a prime or sub on the program you are evaluating.
FAR reference: FAR 9.505-3.
3. Unequal Access to Information
What it is: A contractor has access to non-public, competitively useful information about a procurement — information their competitors do not have — as a result of performing a prior or concurrent contract.
The problem: Access to source selection information, cost estimates, or proprietary competitor data creates an unfair advantage in a subsequent competition.
Example: A contractor manages the government's contracting support functions and sees all price proposals submitted by competing firms. If that firm later competes for a contract in the same area, they have seen competitor pricing that others have not.
FAR reference: FAR 9.505-4.
OCI Mitigation Plans
When OCI exists but can be managed, the contracting officer may accept an OCI Mitigation Plan — a contractor's documented commitment to firewalls, disclosure policies, and restrictions that neutralize the conflict.
Effective mitigation measures include:
Firewall procedures: Physical and organizational separation between the team performing the conflicted work and the team pursuing the related competition. Different program managers, separate physical locations, restricted information sharing.
Non-disclosure agreements: Personnel with access to sensitive government information sign NDAs restricting use of that information.
Exclusion from specific task: In some cases, a contractor can carve out specific employees or teams from conflicted work while retaining the rest of the contract.
Notification procedures: Prompt disclosure to the CO when an OCI risk is identified.
A mitigation plan must be approved by the contracting officer. Not all OCIs can be mitigated — biased ground rules OCI in particular often results in exclusion regardless of proposed mitigation.
When OCI Cannot Be Mitigated
Some OCI situations result in mandatory exclusion:
- You wrote the SOW for a competition — you are excluded from competing, period.
- You are evaluating the performance of a company you are teaming with on another program.
- You have access to all competitor pricing in a follow-on competition.
Contracting officers have discretion to award to an OCI-affected contractor only when the agency head grants a waiver upon finding that it is in the best interest of the government — this is rare and requires written justification.
How OCI Gets Identified
Solicitation OCI Clauses
Many RFPs include OCI representation requirements. Section H or L of the RFP may include specific questions: "Has your firm or any affiliate performed work for this agency in the past 12 months in an advisory capacity for this program?" Failing to disclose a known OCI in your proposal is a compliance violation.
Agency OCI Screening
Contracting officers are supposed to conduct OCI screening before source selection. They compare offerors against their own contracts database.
Competitor Protests
The most common way OCI surfaces post-award. A losing competitor discovers that the awardee had an advisory role, access to non-public information, or a financial relationship with a government evaluator — and files a protest with the GAO or Court of Federal Claims.
GAO has sustained OCI-based protests in numerous cases, resulting in contract terminations, re-competitions, and awardee exclusion.
Identifying Your Own OCI Risk
Before pursuing any federal opportunity, run an OCI screen:
Questions to ask:
- Has our firm performed any advisory, design, or A&AS work for this agency related to this requirement in the past 2 years?
- Does our firm have access to any non-public information about this competition (draft SOWs, budget estimates, evaluation criteria)?
- Is our firm currently performing any work that requires objective evaluation of parties who might be our competitors in this competition?
- Does any team member have a personal financial interest in the outcome of this award?
If the answer to any of these is yes, involve your legal counsel before submitting a proposal.
OCI in Teaming Relationships
OCI applies not just to your firm but to your entire team — primes, subcontractors, and consultants.
A common trap: A prime contractor brings on a subcontractor late in proposal development without realizing that subcontractor performed advisory services for the government on this exact program. The prime's proposal is now OCI-tainted even though the prime itself had no conflict.
Due diligence on teammates:
- Ask every proposed sub and major consultant: have you performed any work for this agency related to this requirement?
- Get written representations from all team members.
- Review your teammates' GSA and federal contract records for relevant advisory work.
OCI and Large IDIQ Vehicles
OCI is particularly complex on IDIQ vehicles:
- A contractor holding a seat on an IDIQ vehicle for advisory services may be OCI-precluded from competing for task orders under a different IDIQ vehicle covering related execution work.
- Some IDIQ vehicles explicitly state in their ordering procedures that holders with certain advisory relationships are excluded from specific task orders.
- Review the IDIQ contract's OCI provisions before pursuing task orders.
Key Takeaways
- Three OCI types: Biased ground rules (you wrote the requirements), impaired objectivity (you evaluate your own interests), unequal access (you saw non-public information competitors didn't).
- FAR Subpart 9.5 is the controlling authority — contracting officers are required to identify and mitigate OCIs before award.
- Biased ground rules OCI is the most common and the hardest to mitigate — writing a SOW typically means you cannot compete for the resulting contract.
- OCI screening is mandatory before proposing — check your own work history, your teammates' history, and any non-public information access.
- Post-award OCI protests are a real risk — a competitor can protest your award based on an OCI you didn't disclose; sustained protests mean losing the contract.
- Get legal counsel whenever an OCI risk is identified — the cost of early consultation is far less than the cost of an OCI disqualification or protest.
Find federal opportunities that match your capabilities without OCI conflicts →
Find opportunities like this one
RFxNerd monitors federal procurement and surfaces the best-fit opportunities for your business — scored and ranked automatically.
Get started →