Organizational Conflicts of Interest (OCI) in Government Contracting
Organizational Conflicts of Interest can prevent you from winning contracts, get you disqualified after award, or even lead to contract termination. Understanding the three types of OCI and how to mitigate them is essential for any company doing business with the federal government.
FAR 9.5 requires agencies to identify, evaluate, and resolve potential OCIs before awarding contracts. This guide explains each type, common scenarios, mitigation strategies, and how to address OCIs proactively in your proposals.
100M+ government records · 300+ gov/news sources · Updated hourly
The Three Types of OCI
1. Unequal Access to Information
An unequal access OCI arises when a contractor gains access to non-public, competitively sensitive information through one contract that gives them an unfair advantage in competing for another contract. The concern is not that the contractor will act improperly, but that they have information competitors lack.
Common scenario: A contractor providing IT support to a government agency has access to the agency's budget data, cost estimates, and technical requirements for a new procurement. If that contractor competes for the new procurement, they have insider knowledge that other competitors cannot access.
Mitigation: Firewalls are the primary mitigation. Separate the personnel with access to sensitive information from the proposal team. Implement physical and electronic barriers. Have an OCI monitor verify compliance. Non-disclosure agreements add another layer of protection.
2. Biased Ground Rules
A biased ground rules OCI occurs when a contractor has helped to establish the specifications, evaluation criteria, or statements of work for a competition they later compete in. The contractor may have shaped the requirements — consciously or unconsciously — to favor their own solution.
Common scenario: A consulting firm helps an agency develop the requirements for a new IT system, including the technical specifications, NAICS code, and evaluation criteria. That firm then submits a proposal for the system implementation contract. They had the opportunity to write the rules in their favor.
Mitigation: This is the hardest OCI type to mitigate because the bias is baked into the process. Common approaches include having the government independently validate all requirements the contractor helped develop, making all contractor work products publicly available to all competitors, or excluding the contractor from the follow-on competition entirely.
3. Impaired Objectivity
An impaired objectivity OCI exists when a contractor is asked to evaluate or make recommendations regarding their own work, products, or services — or those of a competitor. The contractor's financial interest creates a risk that their judgment will be biased.
Common scenario: A contractor provides advisory and assistance (A&A) services to help an agency evaluate weapons systems. One of the systems being evaluated is manufactured by a division of that same contractor. The evaluator has a financial interest in recommending their own company's product.
Mitigation: Options include divesting the conflicting business unit, recusing specific personnel with ties to the conflicting interest, establishing firewalls between the advisory and product divisions, or having the government independently validate all recommendations. In severe cases, the contractor may need to choose between the advisory role and the product line.
FAR 9.5 Requirements
FAR Subpart 9.5 establishes the regulatory framework for identifying and resolving OCIs. It applies to all federal contracts and requires both the government and contractors to take affirmative steps to prevent conflicts.
Defines OCI as situations where a contractor's objectivity may be impaired or where a contractor may have an unfair competitive advantage due to its relationship with the government.
Requires the CO to analyze planned acquisitions for potential OCIs as early as possible, before issuing solicitations. The CO must evaluate whether conflicts can be avoided, neutralized, or mitigated.
Establishes specific rules for common OCI scenarios including systems engineering, advisory services, and contractors who prepare specifications. Contains the key principle that a contractor who prepares a SOW should not be allowed to compete for the resulting contract.
Requires solicitations to include OCI clauses, mandate contractor disclosure of potential conflicts, and establishes procedures for resolving identified conflicts including mitigation plans and waivers.
Provides illustrative examples of OCI situations across different contract types, including engineering and technical services, advisory services, and management support contracts.
Common OCI Scenarios
Systems Engineering & Technical Assistance (SETA)
SETA contractors who advise the government on technical decisions often face impaired objectivity OCI if their parent company manufactures products being evaluated. They may also face unequal access OCI from exposure to competitor proprietary data.
Requirements Development
Contractors who help develop requirements, specifications, or SOWs face biased ground rules OCI if they later compete for the implementation contract. This is common in consulting and architecture contracts.
IT Support & Infrastructure
IT support contractors with administrative access to government systems may have visibility into procurement-sensitive data (budgets, cost estimates, source selection information), creating unequal access OCI.
Testing & Evaluation
Contractors who test or evaluate systems may face impaired objectivity if they also developed or manufactured the system. Independent T&E requires organizational independence from the development contractor.
Mitigation Strategies
When an OCI is identified, the goal is to neutralize or mitigate it to a level acceptable to the Contracting Officer. The effectiveness of mitigation depends on the type of OCI:
Firewalls
Physical and organizational separation of conflicted personnel. Includes separate work spaces, separate IT systems, NDAs, OCI monitor, documented procedures, and training. Most effective for unequal access OCIs. Effectiveness rating: high for unequal access, moderate for impaired objectivity, low for biased ground rules.
Recusal
Removing specific individuals with conflicts from the affected work. The person with the conflict does not participate in the potentially biased activity. Works when the conflict is individual, not organizational.
Divestiture
Selling or spinning off the business unit that creates the conflict. This is the most drastic mitigation but the most effective. Companies sometimes choose between pursuing advisory work or product work when both create an irreconcilable OCI.
Government Oversight
Having the government independently validate all work products from the conflicted contractor. The government reviews recommendations, evaluations, and specifications to ensure they are unbiased. Adds cost and time but preserves competition.
An OCI mitigation plan should be specific, implementable, and verifiable. Generic statements like “we will avoid conflicts” are insufficient. Describe exactly what measures will be in place, who is responsible for enforcement, and how compliance will be monitored.
Related Guides
Proposal Writing
How to address OCI and other compliance requirements in your government proposals.
Teaming Agreements
How teaming relationships can create or mitigate organizational conflicts.
Compliance Certifications
Key compliance certifications that demonstrate your commitment to ethical contracting.
Frequently Asked Questions
What is an Organizational Conflict of Interest (OCI)?
An Organizational Conflict of Interest exists when a contractor's work on one government contract creates an unfair competitive advantage or biases their judgment on another contract. FAR 9.5 defines three types: unequal access to information (having insider knowledge that competitors lack), biased ground rules (setting the rules for a competition you later compete in), and impaired objectivity (being unable to provide unbiased advice because you have a financial stake in the outcome). OCIs can disqualify a contractor from competing for a contract or result in contract termination.
Can an OCI be waived?
Yes, but waivers are rare and require approval at a high level within the agency (typically the head of the contracting activity or above). FAR 9.503 allows waivers when it is in the government's interest and the conflict can be adequately mitigated. The contractor must demonstrate that their mitigation plan effectively neutralizes the conflict. Waivers are more likely for impaired objectivity situations where mitigation (like firewalls) can be effective, and less likely for biased ground rules where the conflict is inherent.
How should I address OCI in my proposal?
Many solicitations require offerors to identify potential OCIs and describe mitigation measures as part of their proposal. Even when not explicitly required, proactively addressing potential OCIs demonstrates awareness and responsibility. Your OCI response should: (1) identify all potential conflicts based on your current and recent contracts, (2) explain why each does or does not constitute a conflict, (3) describe specific mitigation measures for any identified conflicts, and (4) commit to notifying the Contracting Officer of any new conflicts that arise during performance.
What is an OCI firewall?
An OCI firewall is an organizational and physical separation between personnel working on potentially conflicting contracts. Firewalled personnel cannot share information, attend the same meetings, or access the same files related to the conflicting work. Firewalls typically include: separate physical work spaces, separate IT access and file systems, non-disclosure agreements for firewalled staff, an OCI monitor who verifies compliance, and documented procedures for handling inadvertent breaches. Firewalls are most effective for unequal access conflicts and less effective for impaired objectivity.
Can a subcontractor create an OCI for the prime?
Yes. OCIs flow up from subcontractors to the prime contractor. If your subcontractor has an OCI that would disqualify them from the work, that conflict can disqualify your entire team. This is why OCI analysis should include all team members — primes, subcontractors, consultants, and even affiliates. During proposal preparation, require all team members to certify their OCI status and disclose any current or recent contracts that could create conflicts. Address subcontractor OCIs in your mitigation plan.
Research Contract History with Bureauify
Identify potential OCI risks by researching historical contract awards, incumbent contractors, and advisory relationships. Make informed bid/no-bid decisions with complete contract intelligence.