Organizational Conflict of Interest (OCI)

An organizational conflict of interest (OCI) exists when a contractor's other activities or relationships leave it unable to give impartial assistance or advice, or hand it an unfair competitive advantage. FAR subpart 9.5 requires contracting officers to identify conflicts early and avoid, neutralize, or mitigate them before award.

FAR 9.505 rests on two principles: prevent conflicting roles that might bias a contractor's judgment, and prevent unfair competitive advantage, including advantage from access to proprietary or source selection information. Sections 9.505-1 through 9.505-4 apply those principles to the recurring fact patterns — systems engineering and technical direction, preparing specifications or work statements, providing evaluation services, and access to other companies' proprietary information.

The analysis belongs to the contracting officer. FAR 9.504 requires identifying potential conflicts as early as possible and resolving them before award, whether by restricting future work, accepting a mitigation plan, or excluding the offeror. An agency head or designee can waive the requirement in writing under 9.503 when applying it is not in the government's interest.

OCIs tend to surface as postaward protests: the winner helped write the specification, or will be grading its own work. A mitigation plan accepted without analysis is nearly as vulnerable as no plan, so document the OCI review even when the conclusion is that no conflict exists.

Regulatory Reference

FAR Subpart 9.5; FAR 9.503; FAR 9.504; FAR 9.505; Pub. L. 117-324

RFO Status

The Part 9 model deviation retains subpart 9.5 with plain-language edits, while a separate proposed rule under FAR case 2023-006, implementing Pub. L. 117-324, would move OCI coverage to a new subpart 3.12 with standard provisions and clauses; that rule remained unfinalized as of this entry's verification, so watch both tracks.

Category

Regulations & Policy

How AcqBot Helps

AcqBot flags OCI risk during acquisition planning — it checks whether a prospective offeror helped develop the specification or will be evaluating its own work, drafts the contracting officer's OCI analysis for the file, and generates solicitation restriction or mitigation language keyed to the FAR 9.505 fact patterns.