Organizational Conflicts of Interest: Understanding and Managing OCI in Government Contracts

An Organizational Conflict of Interest (OCI) exists when a contractor's other activities or relationships could impair its objectivity or give it an unfair competitive advantage in a government procurement.

Why OCIs matter:

• Can disqualify you from contract awards
• Can result in contract termination
• May lead to debarment
• Damage customer relationships and reputation

OCI regulatory basis:

FAR Subpart 9.5 governs OCIs. It requires contracting officers to:

• Identify potential OCIs early in acquisition planning
• Evaluate the significance of potential conflicts
• Avoid, neutralize, or mitigate conflicts
• Include appropriate clauses in contracts

The core principle:

Government contracting must be fair and objective. Any situation where a contractor's interests could compromise that fairness is an OCI — even if the contractor acts with complete integrity.

Perception matters:

OCIs are about potential for conflict, not just actual misconduct. Even the appearance of conflict can be disqualifying.

FAR recognizes three distinct OCI types. Understanding each is critical for identification and mitigation.

1. Biased Ground Rules

A contractor sets the "rules" for a competition in which it will compete.

Example: Company writes the SOW for a contract, then bids on that contract. They may have tilted requirements toward their capabilities.

Key question: Did you help define requirements you'll compete to fulfill?

2. Unequal Access to Information

A contractor has access to non-public information that gives competitive advantage.

Example: Contractor performing pre-award support sees competitor pricing or proprietary technical approaches, then competes against those competitors.

Key question: Do you have information competitors don't have that would affect the competition?

3. Impaired Objectivity

A contractor's judgment may be compromised by its financial or other interests.

Example: Contractor evaluates its own products/services or those of a competitor when the evaluation affects who wins work.

Key question: Would your recommendations affect your own business interests?

Multiple OCIs:

A situation can involve multiple OCI types simultaneously. Each requires separate analysis and potentially different mitigation approaches.

When to look for OCIs:

• During capture — before pursuing an opportunity
• At proposal time — before committing resources
• During contract performance — as situations change
• When acquiring companies or teaming

Questions to ask:

For Biased Ground Rules:

• Did we help write the SOW, specifications, or evaluation criteria?
• Did we provide systems engineering or technical direction?
• Did we conduct studies that influenced requirements?

For Unequal Access:

• Do we have non-public information about competitors?
• Did we see proposal or pricing information?
• Do we have access to source selection information?

For Impaired Objectivity:

• Would our evaluation affect our own products/services?
• Are we evaluating work we might perform or compete for?
• Could our advice steer business to ourselves?

Common OCI scenarios:

• SETA (Systems Engineering and Technical Assistance) work
• Advisory and assistance services
• Pre-award support followed by competition
• Acquisition of companies with government work
• Teaming with competitors on some contracts

When OCIs are identified, you must either avoid the conflict or mitigate it effectively.

Avoidance:

The cleanest solution — don't pursue the conflicting opportunity:

• Decline to compete on work you helped define
• Choose between SETA and implementation work
• Exclude certain business lines from competitions

Mitigation measures:

For Biased Ground Rules:

• Exclude personnel who wrote requirements from proposal team
• Document that requirements reflect government needs, not company capabilities
• Ensure government independently validated requirements

For Unequal Access:

• Implement firewalls — physical and electronic separation
• Restrict information access to need-to-know
• Non-disclosure agreements and training
• Independent verification of separation

For Impaired Objectivity:

• Use independent reviewers for assessments
• Recuse company from affected evaluations
• Structural separation between advisory and competitive work

Mitigation plan elements:

• Specific measures to address each identified OCI
• Personnel restrictions and firewalls
• Monitoring and enforcement procedures
• Training requirements
• Verification and audit provisions

Disclosure obligations:

You must disclose potential OCIs to the contracting officer. Failure to disclose can result in:

• Disqualification from award
• Contract termination
• False Claims Act liability (if you knowingly concealed)

When to disclose:

• With your proposal — before award
• When circumstances change during performance
• When you acquire companies or hire personnel with potential conflicts

What to disclose:

• Nature of the potential conflict
• Relevant work, contracts, or relationships
• Personnel involved
• Proposed mitigation measures

Proposal OCI language:

Many solicitations require OCI representations. Respond carefully:

• Certify no OCI if true
• Disclose and propose mitigation if potential exists
• Never misrepresent — it's worse than the OCI itself

OCI mitigation plans in proposals:

If you identify a potential OCI, include a detailed mitigation plan. Show the government you've thought through the issue and have credible solutions.

CO authority:

The contracting officer decides whether an OCI exists and whether mitigation is sufficient. This is a judgment call with significant discretion.

What COs consider:

• Nature and severity of potential conflict
• Likelihood conflict would affect objectivity
• Effectiveness of proposed mitigation
• Impact on the acquisition if contractor excluded
• Government's ability to independently verify work

Possible CO decisions:

• No OCI — Issue doesn't rise to the level of conflict
• OCI mitigated — Your mitigation plan is acceptable
• OCI not mitigable — You're excluded from competition
• Waiver — OCI exists but is waived in government's interest

OCI waivers:

Waivers are rare. They require:

• Head of contracting activity (or delegate) approval
• Determination that it's in government's interest
• Documentation of rationale

Don't count on waivers — build your strategy around avoiding or mitigating.

Challenging OCI decisions:

If you're excluded based on OCI, you can protest. GAO reviews whether the CO's determination was reasonable based on the facts.

Why SETA work is high-risk:

Systems Engineering and Technical Assistance (SETA) contractors often:

• Help define requirements (biased ground rules risk)
• See proprietary information (unequal access risk)
• Evaluate contractor performance (impaired objectivity risk)

SETA work frequently precludes competing on related implementation contracts.

Common restrictions:

• Can't compete for work you helped define
• Can't evaluate competitors' proposals
• Can't access source selection information
• May be barred from entire program competitions

Strategic considerations:

• SETA provides deep customer insight but limits future opportunities
• Implementation work has larger revenue but requires winning competitions
• Company structure may separate SETA and implementation units

Firewall approach:

Large companies often establish organizational firewalls:

• Separate business units for SETA vs. implementation
• Physical separation of personnel and systems
• Information flow restrictions
• Compliance monitoring

Firewalls don't always work — government may still find OCIs exist despite separation.

Establish an OCI program:

• Written policies and procedures
• Designated OCI officer/team
• Regular training for business development and contracts staff
• Database tracking potential conflicts

Early identification:

• Evaluate OCI risk at capture phase
• Include OCI review in bid/no-bid decisions
• Don't wait until proposal submission

Due diligence:

When acquiring companies or hiring key personnel:

• Assess their existing OCI obligations
• Review contracts for OCI restrictions
• Plan for inherited conflicts

Documentation:

• Document OCI analysis for every opportunity
• Keep records of disclosures and responses
• Maintain mitigation plan implementation evidence

Monitor and update:

• Circumstances change — revisit OCI assessments
• New wins can create new conflicts
• Personnel moves can trigger issues

Proactive communication:

When potential OCIs arise, proactively discuss with the contracting officer. Early engagement shows good faith and allows collaborative problem-solving.