OCI

An Organizational Conflict of Interest (OCI) exists when the other work, relationships or information access of a contractor produce one of three effects. The contractor would lose its objectivity, would gain an unfair competitive advantage, or would set the ground rules for a competition it intends to enter. FAR Subpart 9.5 governs the condition.

It is an organizational condition, not a personal ethics question. It can disqualify a company that did nothing wrong.

The three recognized types

The FAR does not label them with these names in a single list. Case law and practice settled on three categories drawn from FAR 9.505-1 through 9.505-4:

Biased ground rules — the contractor helped write the specification, statement of work, or evaluation criteria for the procurement it now wants to bid. FAR 9.505-1 (systems engineering and technical direction) and FAR 9.505-2 (preparing specifications or work statements) address this. The concern is not that the contractor cheated. The concern is that the requirement may take its shape, even unconsciously, from what that contractor offers.

Impaired objectivity — the government asks the contractor to evaluate, assess, or recommend on work that it or an affiliate or a competitor performed. FAR 9.505-3 addresses this. Advisory and assistance services, independent verification and validation, and test and evaluation support are the usual settings.

Unequal access to information — the contractor obtained non-public information through other work. The information includes competitor proprietary data, government source selection information and cost data, and it would give the contractor an advantage. FAR 9.505-4 addresses this. Contracting officers cure this type most often, because a properly implemented firewall can neutralize the advantage.

Who decides?

The contracting officer decides. Under FAR 9.504 the contracting officer must identify and evaluate potential conflicts as early as possible in the acquisition process. The contracting officer must then avoid, neutralize or mitigate them before contract award.

Under FAR 9.506 the contracting officer documents the analysis and may include a clause tailored to the situation. FAR 9.503 permits an agency head to waive the requirements for a compelling reason in the interest of the government. A waiver is exceptional, and you cannot assume one.

FAR 9.5 is distinct from FAR 3.11, which governs personal conflicts of interest of individual employees. They are separate regimes, and people frequently conflate them.

When does OCI appear in a bid?

Early. Many solicitations contain an OCI representation. The representation requires you to disclose potential conflicts and to submit a mitigation plan with your proposal.

Some solicitations contain an outright restriction. Such a restriction bars a support contractor on a program from the prime work, and it may extend to affiliates and subcontractors. OCI is also a standard protest ground. A conflict held by a competitor is a live issue, and so is yours.

Standard mitigation approaches

• Avoidance — decline the conflicting work. This is sometimes the only real answer, particularly for biased ground rules.
• Firewalls — physical, organizational and IT separation of the affected personnel and data, with signed non-disclosure acknowledgments and auditable access controls. Firewalls are effective mainly for unequal access.
• Divestiture — move the conflicting business unit outside the corporate family.
• Independent third-party review — insert an unaffiliated party where the contractor cannot preserve objectivity.

A mitigation plan is credible in proportion to how specific and verifiable it is. Name the individuals, the systems, the physical boundaries and the audit mechanism. That detail distinguishes a plan from a promise.

The mistake that makes this term matter

Almost every OCI grows out of work a company was proud to win. The advisory contract, the Systems Engineering and Technical Assistance (SETA) seat, the Independent Verification and Validation (IV&V) role. Those positions carry trust, and a firm earns them by being good at the job. Nobody signs one of them while thinking about the pursuit it forecloses years later.

The conflict then surfaces at the worst possible moment: after the pursuit has a budget, the team is in place and the proposal is half written. A contracting officer raises it, or a competitor raises it in a protest. The company then discovers that the answer is not a paragraph it can add to the proposal. It is a structural fact about which contracts it holds. That is why OCI belongs to the bid decision. By the time it reaches compliance review, the decision already made itself.

What goes wrong in practice

Nobody checks the affiliates and the subcontractors. OCI analysis follows the corporate family and the team. An advisory contract held by a parent company can disqualify a subsidiary. A conflict held by a teammate can taint the prime.

The company delays the disclosure. The instinct to stay quiet and hope is the worst option available. A disclosed and mitigated conflict is routine. An undisclosed conflict that surfaces later is a credibility problem and a potential misrepresentation.

Teams treat impaired objectivity as firewallable. It usually is not. If the government asks a company to grade its own homework, separation of the graders does not remove the corporate interest in the outcome. A generic firewall paragraph reused across bids will not survive scrutiny. It may itself become the protest exhibit.

What to do

1. Screen for OCI before you commit to a pursuit.
2. Treat the answer as a bid or no-bid decision, not a proposal task.
3. Maintain a current inventory of your advisory, SETA, evaluation and IV&V work.
4. Extend that inventory across the whole corporate family.
5. Check every new opportunity against the inventory, including the positions of your teammates.
6. When a conflict is real, disclose it.
7. Pair every disclosure with a specific mitigation plan.
8. Name the individuals, the systems, the boundaries and the audit mechanism in that plan.

What an OCI is not

An OCI is not an accusation. It is a structural condition, and the identification of one says nothing about the integrity of anyone.

An OCI is also not a permanent bar. A well-constructed mitigation that the contracting officer accepts resolves many conflicts. Some conflicts resolve simply with the passage of time, as the underlying information becomes stale or public.

Silas™ screens solicitations for conflict indicators and surfaces them at the pursuit-decision stage rather than at proposal review.