Legal Updates

When Good Business Sense Doesn’t Make Good Legal Sense

When Good Business Sense Doesn’t Make Good Legal Sense

In my role as a Senior E-Discovery Attorney, I often provide guidance to organizations in how to develop and implement policies governing data retention and disposition. When developing those policies, it is critical to consider both the business and legal implications of preserving or deleting data and, ideally, find a balance between the two even when the concerns and priorities may not be the same. A recent case highlights what often proves to be a fundamental tension between the perspective of business stakeholders and legal stakeholders with respect to the preservation of ESI for pending or reasonably anticipated litigation in large corporations.


In June 2015, Plaintiffs ILWU-PMA Welfare Plan and its Board of Trustees brought an ERISA action against Defendant Carewise Health, Inc. (“Carewise”) in U.S. District Court for the Northern District of California. For background, Carewise and its predecessor, CENTRA Cost Management Systems (“Centra”) provided plaintiffs with auditing and discount negotiation services for out-of-network medical claims costing more than $1,000.00. Plaintiffs allege that in 2009, Carewise began paying providers’ fees without auditing whether such providers accepted discounts causing plaintiffs to pay more than the usual rates for claims negotiated by Carewise. After several providers sued both Plaintiffs and Carewise in 2010, Plaintiffs and Carewise entered into a tolling agreement in March 2011 preserving and deferring any potential disputes between the parties during which time the statute of limitations for filing such claims would be tolled.

Carewise’s parent company, formerly named SHPS, Inc., owned three subsidiaries, two of which were relevant to the outcome of the case. The first, SHPS Health Management Solutions, Inc. (“HMS”), was formerly Carewise. The other, Human Resources Solutions, Inc. (“HRS”) was sold to ADP, Inc. in 2012. As part of the business decision to sell, ADP’s purchase of HRS included HRS servers containing ESI of Carewise, including employee emails. In conjunction with the sale of HRS, the parties entered into an agreement which included certain Electronically Stored Information (“ESI”) preservation related provisions. Pursuant to those provisions:

  1. The parties agreed to provide each other with reasonable access to business information reasonably required for litigation purposes;
  2. There was also a clause requiring the ESI to be retained for six years; and
  3. Each party was prohibited from destroying any of the information without first notifying the other party and giving it the opportunity to take possession of the information.

After suing Carewise, Plaintiffs propounded requests for production of documents to Carewise in February 2016. Even though ADP had agreed to retain the Carewise ESI for six years, ADP represented… guessed it......that it no longer possessed any of the data from before September 2009. Plaintiffs thus moved for spoliation sanctions against Carewise under Federal Rule of Civil Procedure 37(e).

Spoliation Sanctions

Rule 37(e) provides:

            If electronically stored information that should have been preserved in

            the anticipation or conduct of litigation is lost because a party failed to

            take reasonable steps to preserve it, and it cannot be restored or replaced

            through additional discovery, the court:

                        (1)  upon finding prejudice to another party from loss of the

                        information, may order measures no greater than necessary

                        to cure the prejudice; or

                        (2)  only upon finding that the party acted with the intent to deprive

                        another party of the information’s use in the litigation may:

                                   (A) presume that the lost information was unfavorable

                                    to the party;

                                   (B) instruct the jury that it may or must presume the information

                                    was unfavorable to the party; or

                                   (C) dismiss the action or enter a default judgement.

Fed. R. Civ. P. 37(e).[1]

Carewise argued mightily that spoliation sanctions were not in order because it had no duty to preserve the ESI. Specifically, Carewise argued:

  1. It owed no duty to preserve the ESI at the time of the 2012 sale to ADP since the litigation was not initiated until June 2015. The court disagreed, however, reminding Carewise that it had entered into the tolling agreement with Plaintiffs in March 2011 and thus reasonably anticipated the litigation at least that far back. Strike one.
  2. The tolling agreement contained no express promise to “maintain electronic records or any other form of evidence.” But as the court pointed out, at the very least, the tolling agreement “should have put Carewise on notice that it possessed information relevant to reasonably foreseeable litigation.” Strike two.
  3. Based on the tolling agreement, it could not discern the who, what, where and when of the forthcoming litigation. The court rejected “this hand-wringing over the minutiae” of the lawsuit as a “red herring.” Strike three.

Even though Carewise struck out on its arguments that it lacked a duty to preserve the ESI at issue, it argued that it nevertheless did “take reasonable steps to preserve” the ESI under Rule 37(e) “by including provisions in the sale agreement for access to and retention of business information.” For myriad reasons, the court did not agree, ultimately concluding that had it acted reasonably, Carewise would have “simply retain[ed] copies” of its ESI before HRS was sold to ADP.    


In the end, it’s difficult to attribute the court’s finding solely to the fact that Carewise failed to retain a copy of its data before its sale to ADP. It certainly did not help that Carewise’s ESI was housed on the servers of a completely different corporate entity in HRS or that there was “confusion” over which company even signed the sale agreement containing the ESI preservation related provisions. As if that was not enough, early on in the case when discovery was just underway and plaintiffs understandably expressed “serious concern” to Carewise about its access to the ESI, Carewise dismissively told them that it was “far too early to request a written explanation regarding the location of these servers....” (internal citations omitted).

While these factors collectively make this case somewhat unique, the case highlights the inherent tension between business and legal when it comes to the preservation of ESI. This is particularly true in the context of mergers, acquisitions and divestitures such as here where the parent company sells a subsidiary for which litigation is reasonably anticipated. With respect to the preservation of the divesting entities’ data, while legal stakeholders generally appreciate the significance of their client’s duty to preserve relevant ESI, business stakeholders naturally tend to focus on the bottom line - cost: “what is the most affordable, cost-effective means of preserving this data?” For Carewise, that decision effectively meant trying to contract away its preservation obligations from HRS to ADP. Organizations can better manage this conflict up front by requiring business stakeholders who are seeking to destroy data outside the ordinary, routine data destruction life-cycles to vet their requests through counsel who can ensure that all of the company’s best interests are accounted for, including its duty to the court to preserve ESI. 


DISCLAIMER: The information contained in this blog is not intended as legal advice or as an opinion on specific facts. For more information about these issues, please contact the author(s) of this blog or your existing LitSmart contact. The invitation to contact the author is not to be construed as a solicitation for legal work. Any new attorney/client relationship will be confirmed in writing.


[1] Interestingly, since Rule 37(e) was amended on December 1, 2015, after this litigation began, the parties also argued over which version of Rule 37(e) should have been applied. The old Rule 37(e) stated only that “absent exceptional circumstances, a court may not impose sanctions under these rules on a party for failing to provide electronically stored information lost as a result of the routine, good-faith operation of an electronic information system.” Plaintiffs fought for the application of the old version of the rule. However, Carewise “urg[ed] application” of the revised rule. (Emphasis in original).

Topics: Spoliation Data Preservation Data Retention Policy E-Discovery Best Practices Discovery Sanctions Sanctions

Subscribe to the E-Discovery Newsletter