The need for strong security measures to protect sensitive government data from hackers has never been more intense. In November alone, the federal government suffered at least four breaches of government information systems, including cyber-attacks on the U.S. Postal Service, the State Department, NOAA, and the White House. What is not discussed in the news reports is the fact that the much of the burden of securing government data falls on government contractors.

The federal government has struggled to adopt a unified and mandatory approach to contractor data security. Each agency has taken a separate approach to adopting cybersecurity requirements, for example DoD recently adopted a new set of regulations governing unclassified “controlled technical information.” Many contractors find the current requirements confusing and at times conflicting between agencies.

In an effort to address this problem, the Department of Commerce National Institute of Standards and Technology has released a draft version of NIST Special Publication 800-171, Protecting Controlled Unclassified Information in Nonfederal Information Systems and Organizations [pdf].

The new NIST guidance is directed at contractors that already have information technology infrastructure and associated security policies and practices in place. The final version of Special Publication 800-171 will attempt to synthesize the federal government’s recommendations to ensure the confidentiality of sensitive federal information stored on contractor computers and information systems. Special Publication 800-171 is part of a three-part plan that will ultimately make these recommendations mandatory. The other parts include a rule proposed by the National Archives and Records Administration—currently under review by OMB—and the eventual adoption of a FAR clause that will apply the requirements of the NARA rule and Special Publication 800-171 to all federal contracts.

Six years from accrual. Three years from discovery. And never longer than ten years.

Despite the statutory language imposing time limits on the government’s pursuit of False Claims Act violations, courts continue to bend over backwards to give the government more time to assert them. The decision in United States ex rel. Sansbury v. LB&B Associates, Inc., No. 07-251 (D.D.C. July 16, 2014) [pdf] allowed the government a total of 14 years from the date of the first alleged false claim.

We hope that the Supreme Court will restore some sanity to the enforcement of the FCA limitations period in its decision in Kellogg Brown & Root Services, Inc. v. United States ex rel. Carter, No. 12-1497. We discuss the issues in that case in an earlier post. But we still have to wait a while for that. Argument in the Carter case is scheduled for January 13, 2015.

[UPDATE: On May 26, 2015, the Supreme Court reversed the Fourth Circuit’s decision in Carter and held that the Wartime Suspension of Limitations Act is limited to criminal offenses. Kellogg Brown & Root Services, Inc. v. Carter, No 12-1497 (U.S. May 26, 2015) [pdf]. Our discussion of the Carter decision is available here.]

The FCA limitations and tolling framework

Sansbury is an unusual case that is based on the intricacies of the FCA’s limitations and relation-back provisions. Before getting into the facts of the case and the holding, here’s a breakdown of those provisions.

According to the text of the False Claims Act (31 U.S.C. § 3731(b)), the limitations period applicable to civil FCA actions is the later of:  (1) 6 years after the date on which the violation is committed; or (2) 3 years after the date when the material facts giving rise to the cause of action are known or reasonably should have been known by the U.S. official responsible for acting on FCA violations (i.e. DOJ official), but in no event more than 10 years after the date on which the violation is committed.

But these may not be real deadlines. Even without the tolling that that may be available under the Wartime Suspension of Limitations Act, the government may get several additional years to make a decision on whether to intervene in a whistleblower’s qui tam suit. If the whistleblower’s original action is timely under § 3731(b), the government’s intervention complaint “relates back” to the date of the initial complaint. Even if the government takes three years to file its intervention complaint, it is deemed to have been filed on the date of the original suit. The relation back provision appears in 31 U.S.C. § 3731(c).


Cases at the Armed Services Board of Contract Appeals often require scientific or other technical evidence that is best explained by an expert witness. Though it conducts no jury trials and the rules do not expressly require it, the board generally considers itself the gatekeeper of junk scientific evidence. The board regularly considers motions challenging the admissibility of expert testimony. It also regularly grants them.

In the appropriate case, a pretrial motion to exclude an expert’s testimony can be an effective tool. Here we address the most common grounds for challenges to expert testimony at the ASBCA.

Expert testimony must be reliable.

The basic test for the admissibility of expert testimony in federal courts is set forth in Rule 702 of the Federal Rules of Evidence, which codifies the Supreme Court’s decisions in Daubert v. Merell Dow Pharmaceuticals, 509 U.S. 579 (1993), and Kumho Tire Co. v. Carmichael, 526 U.S. 137 (1999). Under Rule 702, expert testimony must not only be helpful, it must be based on sufficient facts or data, and be the product of reliable principles and methods.

Parties in litigation at the ASBCA are not exempt from the reliability requirement. The board frequently refers to the standards set forth in Rule 702 as a prerequisite to the consideration of expert testimony. Even without a jury, the board will exclude expert testimony that the board finds unreliable. Board rules are generally more flexible than the federal rules when it comes to the admissibility of evidence, but an expert’s opinion must be sufficiently reliable for the board to consider it. Universal Yacht Services, Inc., ASBCA No. 53951, 04-2 BCA ¶ 32648 (May 24, 2004) [pdf].


Contractors know that discovery is the most time-consuming and expensive part of litigation. Until now, the Federal Rules of Civil Procedure have done little to address the problem. Parties that preserve too much data are burdened with the cost of collecting and reviewing it. Parties that preserve too little risk not having access to key evidence or being penalized for spoliation.

While we’re not sure the problem can be fixed with a few changes to the procedural rules, reducing discovery costs appears to be a key goal of the recently-proposed amendments to the Federal Rules of Civil Procedure [pdf]. The revised rules were passed by the Judicial Conference of the United States in September 2014 and are now awaiting approval by the Supreme Court. Assuming they are approved, the amendments will become effective on December 1, 2015.

The proposed amendments have three primary objectives: (1) improve early and active judicial case management; (2) enhance the importance of proportionality in the discovery process; and (3) encourage greater cooperation among litigants. The amendments would also resolve an apparent circuit split over when sanctions may be imposed for failing to preserve electronically stored information. The changes aimed at accomplishing these objectives appear in the proposed amendments to Rules 1, 4, 16, 26, and 37.


Every Postal Service contractor should know the answer to certain fundamental questions: What procurement rules apply to the Postal Service and how do they differ from other agencies? What contract provisions are most likely to cause problems during performance? How do I identify and respond to changes and changed conditions? What recourse do I have when disputes arise?

That’s why our firm is presenting a full-day seminar on “Postal Service Contracting: What Every Contractor Should Know,” at the Westin Tysons Corner hotel on Thursday, November 6, 2014.

We start with the basics

We start with a primer on the creation, structure, and current management of the Postal Service. We provide vital background and statistical information that all postal contractors should know. We explore the pressing issues confronting the Postal Service today, its plans for the future, and how these issues will impact contractors. We conclude the session by setting out the 23 most important “culture pointers” encountered in the unique Postal Service contracting environment.


Controlling legal spend is a frequent and important topic of discussion, especially among in-house counsel and their litigation teams. Much of the discussion focuses on the problem of soaring discovery costs driven by the proliferation of electronic data. As an eDiscovery attorney, I employ early case assessment strategies and tools, technology-assisted review, and even low-cost outside staff attorneys to try and curtail the cost of discovery. In the end, the effectiveness of these cost-reduction alternatives hinges on whether clients have done their part to reduce the volume of data upstream.

Beyond implementing a formal records retention plan, there are a number of fairly simple steps that companies can take to help reduce litigation costs. Items 1-5 help reduce the volume of data that needs to be collected and reviewed. Items 6-8 will help ensure that your litigation budget is not exhausted on spoliation or sanctions motions.

1.   When implementing an email archive, be mindful of how it will impact litigation costs.

An email archive is not a cure to your litigation woes. Storing every company email that was sent or received in an email archive may make preservation easy, but it may also be contributing to your soaring discovery costs. Despite claims to the contrary, most archives have poor search and export features. It is also very difficult to pull out only responsive email from an archive.  Instead, you end up overspending on attorney review of irrelevant data or producing mounds of irrelevant data.

One way to control this issue is to tailor the archive for your own business and legal needs from the beginning. Do you really need every employee’s email messages for the last 10 years? Very few industries have regulatory requirements that require such broad retention. Even those that do usually only apply to a small subset of employees. Confirm any applicable regulatory requirements and consider your own business and legal needs. Consider creating email groups with different retention cycles.


Retaliating against an employee for reporting safety violations, the U.S. Postal Service asserted baseless terrorism charges against him. As a result, the employee was dismissed from his job, arrested, detained, harassed, criminally charged with committing acts of terrorism, and subjected to an extended campaign of public disparagement. That sounds like the exaggerated ranting of a would-be whistleblower seeking to cash in on a big pay day. But it’s not. These are the allegations made by the U.S. Department of Labor in a lawsuit it filed against its sister agency, the U.S. Postal Service, in an action filed in the U.S. District Court for the Eastern District of Missouri, Eastern Division, Case No. 4:14-cv-1233.