"Should Have Known" Standard Applied to CDA Statute of Limitations
Client Alert | 1 min read | 02.28.13
In what seems likely to be a major landmark in the evolving interpretation of the CDA statute of limitations, the ASBCA has held that the statute began to run in 1999, when a DCMA price analyst had all the information the government needed to recognize that it had a claim for an alleged CAS violation, even though the responsible CO may not have been aware of the claim until an audit report was issued in 2006. The ASBCA held that, in the absence of any evidence of trickery or concealment, the government "should have known" that it had a claim based on the contractor's 1999 cost proposal that appeared to be inconsistent with its disclosed accounting practice and that the government could not unilaterally extend the statute of limitations by failing to perform an audit that put the CO on actual notice that there might be a claim.
Contacts
Insights
Client Alert | 4 min read | 10.30.26
Recent sustain decisions by the U.S. Government Accountability Office (GAO) in Fluor Federal Solutions, LLC and Reliance Test & Technology send a clear message: when an agency tries to fix a Procurement Integrity Act (PIA) violation by committing a second one, the cure can be just as fatal as the disease. The cases involved the U.S. Air Force’s $1.8 billion procurement for O&M services at Elgin Air Force Base. During discussions, the Air Force inadvertently released a pricing overview slide with all offerors’ bottom-line evaluated costs to Reliance Test & Technology, which immediately notified the agency of the error. In response, the Air Force decided to level the playing field by providing the same information to all the other offerors in the procurement, stating, “[o]fferors may consider this disclosure in their [final proposal revision].”
Client Alert | 3 min read | 10.29.26
What University Licensors Should Learn From TexasLDPC v. Broadcom
Client Alert | 2 min read | 10.28.26
Debriefing to Dead Briefing: How to Avoid Dismissal by Identifying “Required” Debriefings

