Archive for the ‘Spoliation’ Category

Morning Links 7/21

Tuesday, July 21st, 2009

Bow Tie Law's Blog recently wrote that Telling the Judge ESI is "Expensive" is not an Excuse for Failing to Produce.

Case in Point provided a little humor on The "Dog Ate My Hard Drive" Defense.

e-discovery 2.0 continued its series on reducing e-discovery costs in How to Reduce Electronic Discovery Costs part III: Early Case Assessment.

e-Discovery Insights began analyzing the new California Electronic Discovery Act in a post entitled 1st Things 1st: The Litigation Hold Letter.

  • Share/Bookmark

Morning Links 7/15

Wednesday, July 15th, 2009

Bow Tie Law's Blog wrote Swimming in the Deep End: Treading Water in e-Discovery Cases which discussed the issues of cost shifting, metadata, and privilege logs arising in a recent case from Massachusetts. 

E-Discovery Bytes recently posted Coming Soon to A Wisconsin Courtroom Near You? which discusses the upcoming changings to the Wisconsin rules of civil procedure.

While on the topic of new rules, e-discovery 2.0 recently posted California Enacts Elecronic Discovery.

e-Lessons Learned recently posted Timber! Court Chops Down Government's Spoliation Case which discusses a recent decision finding that the unintentional spoliation of evidence did not warrant sanctions. 

Legal Holds and Trigger Events blog recently posted a link and information on a One Hour Podcast on Developing and Implementing Defensible Legal Holds.

  • Share/Bookmark

Morning Links 7/13

Monday, July 13th, 2009

Bow Tie Law's Blog wrote Keep on Trucking: Data Productions or Summaries, an analysis of a recent court decision finding that Rule 34 does not require a party to produce summaries upon request.

Electronic Discovery Law recently posted about a case in which "Inhibited Ability to Participate Meaningfully in Electronic Discovery" Results in Reduction of Rate of Recoverable Attorney's Fees.

Ride The Lightning recently posted Much Ado About Nothing? Computer Forensics and the Melendez-Diaz Case which found that allowing a forensics lab to present a certificate of its findings to the court without producing an analyst for cross examination violated a defendant's Sixth Amendment Right.

  • Share/Bookmark

No Specific Evidence of Spoliation, No Sanctions

Tuesday, March 17th, 2009

In Superior Production Partnership v. Gordon Auto Body Parts Co. (S.D. Ohio 2009) the Court ruled that sanctions were not appropriate absent evidence that any relevant information had been destroyed.  The case involved predatory pricing and Superior Production d/b/a PBSI brought a motion for sanctions based upon the defendants failure to institute a legal hold and failure to conduct a thorough search for relevant information.

The Defendants had not instituted a formal legal hold and their search for responsive documents was limited to one database.  The intial search did not include any emails or employee hard drives.  Despite requests from PBSI, the Defendant had not instructed any employees to preserve relevant information while the litigation was pending.   When this search resulted in a suspiciously small number of relevant documents, the Plaintiffs brought the motion for sanctions seeking the prodcution of employee hard-drives and to shift the costs of foresenically examining them to determine whether any relevant information was deleted.  In the alternative, PBSI sought an adverse inference instruction based upon the intentional or negligent destruction of relevant information.

The Defendant argued that its standard document retention policy was sufficient to preserve relevant documents. The Defendant also pointed out that after the initial production, and after one of its key employees was deposed because of the limited number of documents produced, the Defendant issued a formal litigation hold notice to all employees.  After a further search of email files and employee hard drives, some additional relevant documents were found and produced. 

The Court began by noting that the Defendant's duty to preserve and produce relevant evidence was triggered by the filing of the lawsuit.  Failure to meet that duty could result in sanctionable conduct.  However, the Plaintiff failed to produce any evidence that relevant information had actually been destroyed by the Defendant's actions or its failure to act.  Because of that lack of evidence, the Court declined to award either sanction the Plaintiff sought. 

However, the important lesson is that the Court noted direct evidence that relevant evidence has been destroyed is often not present in sanctionable cases and discussed two alternative methods a party seeking sanctions can meet its burden.  FIrst, "a certain group of relevant documents may exist only back to a particular point in time, and not beyond, creating an inference that the same documents did exist for earlier time periods but have simply been deleted."  And second, "a party suspecting document destruction may show that it is the routine practice either of the defendant or other companies engaged in a similar business to maintain certain types of documents, but that no such documents have been produced by this defendant."

Regardless of the outcome, the Defendant's actions in this case were questionable at best.  The Defendant clearly played with fire here by not instituting a legal hold.  The Court left the Plaintiff the option of bringing the motion again in the future should it find any direct evidence of spoliation.  The limited extent of the search also could have led to sanctions however this error was rectified by the subsequent steps to conduct a proper search of all potential sources of ESI. 

Another important point is the Defendant's standard document retention policy.  While the Defendant argued its document retention policy would prevent the destruction of relevant information, the opposite is more likely.  The duty to preserve is often breached through the routine destruction of relevant documents when a party fails to suspend its document retention programs.

  • Share/Bookmark