The Conflict They Did Not Disclose. A $425,000 OCI Lesson.

Published 2026 | TIKC NewsWire

A government contractor agreed to pay $425,000 to resolve False Claims Act allegations that it failed to disclose organizational conflicts of interest, known as OCIs, while winning and performing federal task orders for the Army, the General Services Administration, and the Navy. The Justice Department alleged the company stayed silent about relationships that could have skewed its advice and its proposals, even though its contract required disclosure. The dollar figure is modest by enforcement standards. The lesson is not. An undisclosed conflict of interest is no longer treated as a clerical slip. It is treated as a false claim.

What the government said happened

According to the Department of Justice, a company officer held an ownership interest in a second firm that then received subcontracts for warehouse services under sole-source task orders from the Army and GSA. On a separate Navy contract, the company allegedly funded the labor of an outside employee who advised the Navy program office that set the scope and funding of the very work the company was bidding on. The conflict clause in the Navy contract required the company to tell the contracting officer. The government says it did not. These remain allegations, resolved by settlement without a determination of liability, but the theory is what matters for the rest of us.

Why an OCI becomes a false claim

An OCI exists when a contractor’s other interests or relationships could impair its objectivity, give it an unfair competitive advantage, or let it set the ground rules for its own work. The Federal Acquisition Regulation requires contracting officers to identify and address these conflicts, and many contracts carry a clause making disclosure an ongoing duty. When a company certifies compliance, invoices, and stays silent about a known conflict, the government’s position is that every payment request rests on a false implied certification. That is how a disclosure failure turns into False Claims Act exposure, often surfaced by an insider through a whistleblower suit.

The three flavors of conflict

OCIs usually fall into three buckets. Unequal access to information happens when work on one contract gives you nonpublic data that helps you compete for another. Biased ground rules happen when you help write a specification or statement of work and then bid on it. Impaired objectivity happens when your job is to evaluate or advise on something you or an affiliate have a financial stake in. The Navy allegation in this case is a textbook impaired-objectivity problem: paying the person who shapes the requirement you are chasing. The related unequal-access problem is the one small firms stumble into most often, usually without bad intent.

Appearance counts, not just intent

Contractors often assume that if they did not actually misuse an advantage, there is no conflict. Procurement law does not work that way. A conflict can exist on the appearance of a conflict alone, because the integrity of the competition depends on both fairness and the perception of fairness. Waiting until someone proves you gained something is the wrong posture. The duty is to flag the relationship early, let the contracting officer decide, and document a mitigation plan such as a firewall, a recusal, or a divestiture.

What to do now

• Map your relationships. List affiliates, owners, teaming partners, and consultants, and check them against every requirement you touch or advise on.
• Disclose early and in writing. Tell the contracting officer the moment a potential conflict appears, before award and again if facts change during performance.
• Build real mitigation. Firewalls, recusals, and nondisclosure agreements only work if they are documented and actually followed.
• Read your OCI clause. Know whether your contract makes disclosure an ongoing obligation, because many do.
• Treat it as a compliance item. An undisclosed OCI is a fraud risk, and it can reach the people involved, not just the company.

Set-asides and task orders are won on trust. The moment you hide a conflict, you are betting your company on nobody noticing, and in this enforcement climate somebody usually does. Disclose, mitigate, document, and keep winning the honest way. Brick by brick.

FAQ

What is an organizational conflict of interest?

It is a situation where a contractor’s relationships or other work could impair its objectivity, give it an unfair competitive advantage, or let it set the ground rules for its own work. The FAR requires contracting officers to identify and address them.

How does an OCI become a False Claims Act case?

When a contract requires disclosure and the company stays silent while billing, the government argues every payment request carried a false implied certification of compliance, which is what turns a disclosure gap into fraud exposure.

Do I have to prove I misused an advantage?

No. A conflict can exist on its appearance alone. The duty is to disclose the relationship and let the contracting officer decide, not to wait until harm is proven.

How do I mitigate an OCI?

Common tools are firewalls that separate teams and data, recusal from the affected work, nondisclosure agreements, or divestiture of the conflicting interest, all documented and actually enforced.

Sources

U.S. Department of Justice, Office of Public Affairs. (2026). Government contractor agrees to pay $425,000 to resolve alleged false claims related to conflicts of interest.

Federal Acquisition Regulation. (2026). Subpart 9.5, Organizational and Consultant Conflicts of Interest.

False Claims Act, 31 U.S.C. sections 3729 to 3733. (2026).

This article is general information, not legal advice.