Magazine article National Defense

Attorney-Client Privilege in Fraud Suits at Risk

Magazine article National Defense

Attorney-Client Privilege in Fraud Suits at Risk

Article excerpt

Government contractors typically maintain ethics compliance programs, which are mandated by the Federal Acquisition Regulation and are part of the industry's best practices. Central to these programs are internal investigations to detect and determine the extent of unlawful conduct, to include fraud relative to a government contract, which may, if appropriate, require timely disclosure of improper conduct.

Strict confidentiality is essential to any effective internal investigation, to include all interview notes, witness statements, investigation reports and other communications between a contractor and its legal counsel. Generally speaking, the attorney-client privilege--protecting an attorney's communications providing legal advice to its client--and the attorney-work product doctrine, which protects attorney-generated documents prepared in anticipation of litigation, will allow a contractor to keep such documents confidential.

However, in March a federal judge found that because a contractor's internal investigation was led by in-house counsel and involved the use of non-lawyer personnel to conduct interviews, the attorney-client privilege did not apply. The good news is that in June a U.S. Court of Appeals completely rejected that judge's conclusion, thereby preserving the privilege.

The trial and appellate decisions illustrate the importance of conducting internal investigations and taking the correct steps to protect communications between attorney and client from disclosure.

By way of background, in U.S. ex rel. Barko v. Halliburton, Case No. l:05-CV-1276 (March 6, 2014), the federal district court for the District of Columbia ordered Kellogg Brown & Root to produce whistleblower plaintiff documents that the company generated during its internal investigations of the alleged fraudulent activity complained of by the whistleblower, ruling that these materials were not protected under either the attorney-client privilege or attorney-work product doctrine.

The court explained that KBR's investigations, although following its code of business conduct's procedures, "were undertaken pursuant to regulatory law and corporate policy rather than for the purpose of obtaining legal advice." Thus the attorney-client privilege did not apply. The court also viewed the investigation reports as generated in the ordinary course of business rather than for anticipated litigation, thereby rendering the work product doctrine also inapplicable. Critical to this conclusion was that some investigation reports were generated by KBR's non-attorney ethics "director," although the investigation still fell under the auspices and at the direction of the Firm's in-house legal department.

The court also was swayed by the fact that no one told the employees interviewed that the investigation was being conducted in order to provide legal advice to the company.

The Court of Appeals flatly rejected these findings as valid bases to deny these privileges, holding that: In-house counsel is no less empowered than outside counsel to maintain the attorney-client and attorney-work product privileges; non-attorney investigators do not undermine the privilege so long as they act under the direction and supervision of attorneys; and employees interviewed need not be specifically informed that their interviews are subject to the attorney-client privilege, so long as they are informed that the investigation is confidential.

Most importantly, the Court of Appeals found the fact that KBR was required by law to maintain a compliance program and conduct internal investigations into potential wrongdoing did not eliminate the privilege so long as obtaining legal advice was at least one of the purposes for conducting the investigation. …

Search by... Author
Show... All Results Primary Sources Peer-reviewed

Oops!

An unknown error has occurred. Please click the button below to reload the page. If the problem persists, please try again in a little while.