Skip to content

Menu

LexBlog, Inc. logo
NetworkSub-MenuBrowse by SubjectBrowse by PublisherJoin the NetworkGet StartedSubscribeSupportContact
Search
Close

Beware of Your Subcontractor’s Organizational Conflicts of Interest

By Richard Arnholt on February 5, 2015
Email this postTweet this postLike this postShare this post on LinkedIn

A recent Government Accountability Office (GAO) decision, International Business Machines Corporation, B-410639, et al., Jan. 15, 2015, highlights the need for contractors to ensure that both they and their subcontractors are free of or can sufficiently mitigate any organizational conflicts of interest (OCIs).

On January 15, 2015, the GAO denied IBM’s bid protest over an award of an indefinite-delivery/indefinite quantity contract to upgrade a Department of Defense payroll system.  IBM protested its elimination from the competition because key personnel from its proposed subcontractor, Booz Allen Hamilton, were involved in developing the statement of work, solicitation and other key acquisition documents and strategies, resulting in a “biased ground rules” OCI.

A biased ground rules OCI occurs when a company has a hand in setting the ground rules for a competition, and may therefore have an unfair competitive advantage in that competition.  The second type of OCI, “impaired objectivity,” occurs where a contractor is required to exercise judgment in the performance of a contract, but has an economic interest that could potentially influence the exercise of judgment.  The third type of OCI is “unequal or unfair access to nonpublic information,” which occurs where an offeror has access to nonpublic information in its performance of a government contract that could provide an unfair competitive advantage in a later competition for a government contract.

When IBM was first notified of the potential biased ground rules OCI it took the position that there was no  potential or actual OCI regarding itself or its subcontractor.  IBM later offered to have its subcontractor terminate a key employee to mitigate any potential OCI.  The contracting officer found the proposed mitigation was insufficient, determining the proposed action would not resolve the OCI because “the employee had already influenced the specifications, the harm has already been done,” and eliminated IBM from consideration for award.  The GAO found the contracting officer’s determination that an OCI existed and that IBM had failed to mitigate the OCI was reasonable.

This decision highlights the need for prime contractors to thoroughly vet their subcontractors for OCIs, particularly ones that involve biased ground rules.  It also serves as a reminder that the GAO affords contracting officers broad discretion with regard to determinations regarding the existence of an OCI and the adequacy of proposed mitigation plans.

Photo of Richard Arnholt Richard Arnholt

Richard Arnholt advises companies, large and small, on the complex rules and regulations applicable to grants and contracts from federal and state governmental entities. In an era of increased budgetary pressures for contractors, Richard focuses his practice on providing practical business and legal…

Richard Arnholt advises companies, large and small, on the complex rules and regulations applicable to grants and contracts from federal and state governmental entities. In an era of increased budgetary pressures for contractors, Richard focuses his practice on providing practical business and legal guidance to help clients efficiently navigate the minefield of government procurement and grant regulations.

Read more about Richard ArnholtEmailRichard's Linkedin Profile
Show more Show less
  • Posted in:
    Government Contracts
  • Blog:
    GovCon & Trade
  • Organization:
    Bass, Berry & Sims PLC
  • Article: View Original Source

Call us at 1-800-913-0988 or email sales@lexblog.com.

Facebook LinkedIn Twitter RSS
The Library at LexBlog
  • About LexBlog
  • The Field We Built
  • Library at LexBlog
  • Our Beliefs
  • Our Team
  • Contact LexBlog
  • Disclaimer
  • Editorial Policy
  • Terms of Service
  • Get Started
  • Publishing Solutions
  • Compass
  • Submit a Request
  • Support Center
  • System Status
Copyright © 2026, LexBlog, Inc. All Rights Reserved.
Law blog design & platform by LexBlog LexBlog Logo