Close
Enter your
text here

Preservation

For Successful Discovery, Think Backwards – eDiscovery Best Practices

The Electronic Discovery Reference Model (EDRM) has become the standard model for the workflow of the process for handling electronically stored information (ESI) in discovery.  But, to succeed in discovery, regardless whether you’re the producing party or the receiving party, it might be helpful to think about the EDRM model backwards.

Why think backwards?

You can’t have a successful outcome without envisioning the successful outcome that you want to achieve.  The end of the discovery process includes the production and presentation stages, so it’s important to determine what you want to get out of those stages.  Let’s look at them.

Presentation

As a receiving party, it’s important to think about what types of evidence you need to support your case when presenting at depositions and at trial – this is the type of information that needs to be included in your production requests at the beginning of the case.

Production

The format of the ESI produced is important to both sides in the case.  For the receiving party, it’s important to get as much useful information included in the production as possible.  This includes metadata and searchable text for the produced documents, typically with an index or load file to facilitate loading into a review application.  The most useful form of production is native format files with all metadata preserved as used in the normal course of business.

For the producing party, it’s important to save costs, so it’s important to agree to a production format that minimizes production costs.  Converting files to an image based format (such as TIFF) adds costs, so producing in native format can be cost effective for the producing party as well.  It’s also important to determine how to handle issues such as privilege logs and redaction of privileged or confidential information.

Addressing production format issues up front will maximize cost savings and enable each party to get what they want out of the production of ESI.

Processing-Review-Analysis

It also pays to determine early in the process about decisions that affect processing, review and analysis.  How should exception files be handled?  What do you do about files that are infected with malware?  These are examples of issues that need to be decided up front to determine how processing will be handled.

As for review, the review tool being used may impact production specs in terms of how files are viewed and production of load files that are compatible with the review tool, among other considerations.  As for analysis, surely you test search terms to determine their effectiveness before you agree on those terms with opposing counsel, right?

Preservation-Collection-Identification

Long before you have to conduct preservation and collection for a case, you need to establish procedures for implementing and monitoring litigation holds, as well as prepare a data map to identify where corporate information is stored for identification, preservation and collection purposes.

As you can see, at the beginning of a case (and even before), it’s important to think backwards within the EDRM model to ensure a successful discovery process.  Decisions made at the beginning of the case affect the success of those latter stages, so don’t forget to think backwards!

So, what do you think?  What do you do at the beginning of a case to ensure success at the end?   Please share any comments you might have or if you’d like to know more about a particular topic.

P.S. — Notice anything different about the EDRM graphic?

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

Leaving Your Hard Drives in a Rental House is Negligent, Court Rules – eDiscovery Best Practices

In Net-Com Services, Inc. v. Eupen Cable USA, Inc., No. CV 11-2553 JGB (SSx) (C.D. Cal. Aug. 5, 2013), the plaintiff’s destruction of evidence was negligent where its principal failed to take steps to preserve evidence he had stored in a home he rented to nonaffiliated lessees.

A principal of the plaintiff, Steve Moffatt, had custody and control over the company’s documents, which included its financial information. The company was using one accounting system but switched to another when it moved into a new location. When the employee looked for this data and could not find it, he assumed it had been “lost or stolen.” However, he did not report the loss to the company’s insurer or to the police.

Over the previous three years that the company was in operation, it was based in Moffatt’s home office. The company went out of business in October 2011, and as the company wound down, Moffatt stored all of the company’s computer hardware and software in his garage. Around that same time, in September or October 2011, Moffatt rented his home. The only precaution he took was to instruct his lessees not to throw any equipment or software away. Despite this instruction, he drove by the home either in September or October and noticed that the renters “had put a ‘big pile of office equipment and everything else in the front yard’” and were throwing them in dumpsters. As associate retrieved the computers’ hard drives from the renters’ trash in September 2011. The hard drives stored the company’s most recent accounting system; another back-up drive stored the same information, but it was most likely thrown out as well.

In 2012, during discovery, the court granted Eupen’s motion to compel “production of ‘missing accounting information,’ including financial data believed to be stored on purportedly ‘dead’ hard drives. Net-Com responded that the data “may no longer exist” and that its principals had had “no luck” accessing the information on the drives. The court ordered Net-Com to produce the missing information, aside from the company’s federal and state tax returns. It also required Net-Com “to produce ‘the computer hard drives containing potentially relevant ESI that Net-Com has been unable to restore’ to allow Eupen USA ‘to test Net-Com’s assertion that the information is inaccessible.’”

In July 2013, Eupen filed a motion for sanctions based on the loss of data and suggested that Net-Com “be precluded from offering evidence of its damages because its production of financial data was incomplete and insufficient due to the loss of information ‘allegedly contained on a computer hard drive that was apparently no longer functional.’” In response, Net-Com argued that no evidence existed that he hard drives had been “‘irreparably damaged’ such that their contents [were] irretrievable.’” The court declined to preclude the evidence but ordered Net-Com to send the hard drives to a vendor for forensic analysis.

Net-Com complied and submitted the drives to a vendor, Ai Networks. The vendor found “‘recoverable data on at least one of the hard drives,’” said it could retrieve it within three weeks, and estimated the cost to recover it would be between $2,000 and $3,000.

The court found that Net-Com’s duty to preserve arose at least by February 8, 2011, when it filed the lawsuit. The complaint alleged that Net-Com’s damages amounted to “millions of dollars”; therefore, the complaint placed the company’s financial and accounting data at issue. But “seven months after filing suit, Moffatt effectively abandoned the hardware and software containing Net-Com’s financial records by leaving the equipment and data in a garage in a house he rented out to third parties. Even if the eventual loss and destruction of evidence was not intentional, it was definitely negligent.”

The court found sanctions appropriate, noting that an adverse inference instruction is “‘adverse to the destroyer not because of any finding of moral culpability, but because the risk that the evidence would have been detrimental rather than favorable should fall on the party responsible for its loss.’” Although the court could not yet determine whether Eupen had been prejudiced, it ruled that Net-Com had to “bear the full cost of restoring and producing data on the hard drives” and ordered the company “to restore and produce any relevant data from the subject hard drives within fourteen days of the date of this Order.”

So, what do you think?  Were the sanctions severe enough?   Please share any comments you might have or if you’d like to know more about a particular topic.

Case Summary Source: Applied Discovery (free subscription required).  For eDiscovery news and best practices, check out the Applied Discovery Blog here.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

Despite Missing and Scrambled Hard Drives, Court Denies Plaintiff’s Request for Sanctions – eDiscovery Case Law

In Anderson v. Sullivan, No. 1:07-cv-00111-SJM (W.D. Pa. 08/16/2013), a Pennsylvania court found “that no sanctions are warranted” despite the disappearance of one hard drive, “scrambling” of another hard drive and failure to produce several e-mails because the evidence was not relevant to the underlying claims and because there was no showing the defendants intentionally destroyed evidence.

In the underlying lawsuit, the plaintiff alleged that she was retaliated against by officials employed by, or associated with, the Millcreek Township School District (“MTSD”) because she made several whistleblower reports against the District and its top administrators, including Dean Maynard (MTSD’s former Superintendent) for violation of her First Amendment rights and the Pennsylvania Whistleblower Act.  In January of 2007, Maynard inadvertently sent an email to an MTSD teacher, instead of to the intended recipient.  The email allegedly revealed previously undisclosed personal relationships that Maynard had with two people he had recommended for employment with the District.  Maynard disclosed this letter to the School Board and an investigation ensued, where several computers were examined, including those of Maynard and the plaintiff.

As part of this examination, MTSD’s IT department removed the original hard drives from the targeted employees’ computers and replaced them with a new hard drive onto which the employee’s active files would be copied so that the laptop would function without interruption; however, the original hard drive from Maynard’s computer was lost.

When the new hard drive that was installed in Maynard’s computer was examined by Anderson’s expert in approximately June 2011, the expert discovered the hard drive was “scrambled” possibly by some type of wiping software.

At summary judgment, the court concluded that the plaintiff’s claims did not qualify as whistleblower reports under the PWA because they did not disclose any non-technical violation of law.  After her claims were dismissed on summary judgment, the plaintiff filed a motion for sanctions due to the disappearance of one hard drive, “scrambling” of a second hard drive, and withholding 44 pages of e-mails from a 10,000-page production to conceal that one of the hard drives was missing.  Although this court entered summary judgment in favor of all defendants, they retained jurisdiction to adjudicate the motion for sanctions.

Because the plaintiff’s claims were dismissed as a matter of law, the court found that sanctions were not warranted on either hard drive because they could not have contained relevant evidence.  The court also determined that there was a lack of evidence suggesting that evidence was intentionally destroyed.  With regard to the 44 pages of e-mails that were not produced, the court found there was nothing in the record to suggest they were intentionally withheld or even were relevant to the plaintiff’s claims.  So, the court denied the motion for sanctions.

So, what do you think?  Should the motion for sanctions have been granted?   Please share any comments you might have or if you’d like to know more about a particular topic.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

A Model for Reducing Private Data – eDiscovery Best Practices

Since the Electronic Discovery Reference Model (EDRM) annual meeting just four short months ago in May, several EDRM projects (Metrics, Jobs, Data Set and the new Native Files project) have already announced new deliverables and/or requested feedback.  Now, the Data Set project has announced another new deliverable – a new Privacy Risk Reduction Model.

Announced in yesterday’s press release, the new model “is a process for reducing the volume of private, protected and risky data by using a series of steps applied in sequence as part of the information management, identification, preservation and collection phases” of the EDRM.  It “is used prior to producing or exporting data containing risky information such as privileged or proprietary information.”

The model uses a series of six steps applied in sequence with the middle four steps being performed as an iterative process until the amount of private information is reduced to a desirable level.  Here are the steps as described on the EDRM site:

  • Define Risk: Risk is initially identified by an organization by stakeholders who can quantify the specific risks a particular class or type of data may pose. For example, risky data may include personally identifiable information (PII) such as credit card numbers, attorney-client privileged communications or trade secrets.
  • Identify Available Data: Locations and types of risky data should be identified. Possible locations may include email repositories, backups, email and data archives, file shares, individual workstations and laptops, and portable storage devices. The quantity and type should also be specified.
  • Create Filters: Search methods and filters are created to ‘catch’ risky data. They may include keyword, data range, file type, subject line etc.
  • Run Filters: The filters are executed and the results evaluated for accuracy.
  • Verify Output: The data identified or captured by the filters is compared against the anticipated output. If the filters did not catch all the expected risky data, additional filters can be created or existing filters can be refined and the process run again. Additionally, the output from the filters may identify additional risky data or data sources in which case this new data should be subjected the risk reduction process.
  • Quarantine: After an acceptable amount of risky data has been identified through the process, it should be quarantined from the original data sets. This may be done through migration of non-risky data, or through extraction or deletion of the risky data from the original data set.

No EDRM model would be complete without a handy graphic to illustrate the process so, as you can see above, this model includes one that illustrates the steps as well as the risk-time continuum (not to be confused with the space-time continuum, relatively speaking)… 😉

Looks like a sound process, it will be interesting to see it in use.  Hopefully, it will enable the Data Set team to avoid some of the “controversy” experienced during the process of removing private data from the Enron data set.  Kudos to the Data Set team, including project co-leaders Michael Lappin, director of archiving strategy at Nuix, and Eric Robi, president of Elluma Discovery!

So, what do you think?  What do you think of the process?   Please share any comments you might have or if you’d like to know more about a particular topic.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

eDiscovery Daily is Three Years Old!

We’ve always been free, now we are three!

It’s hard to believe that it has been three years ago today since we launched the eDiscoveryDaily blog.  We’re past the “terrible twos” and heading towards pre-school.  Before you know it, we’ll be ready to take our driver’s test!

We have seen traffic on our site (from our first three months of existence to our most recent three months) grow an amazing 575%!  Our subscriber base has grown over 50% in the last year alone!  Back in June, we hit over 200,000 visits on the site and now we have over 236,000!

We continue to appreciate the interest you’ve shown in the topics and will do our best to continue to provide interesting and useful posts about eDiscovery trends, best practices and case law.  That’s what this blog is all about.  And, in each post, we like to ask for you to “please share any comments you might have or if you’d like to know more about a particular topic”, so we encourage you to do so to make this blog even more useful.

We also want to thank the blogs and publications that have linked to our posts and raised our public awareness, including Pinhawk, Ride the Lightning, Litigation Support Guru, Complex Discovery, Bryan College, The Electronic Discovery Reading Room, Litigation Support Today, Alltop, ABA Journal, Litigation Support Blog.com, Litigation Support Technology & News, InfoGovernance Engagement Area, EDD Blog Online, eDiscovery Journal, Learn About E-Discovery, e-Discovery Team ® and any other publication that has picked up at least one of our posts for reference (sorry if I missed any!).  We really appreciate it!

As many of you know by now, we like to take a look back every six months at some of the important stories and topics during that time.  So, here are some posts over the last six months you may have missed.  Enjoy!

Rodney Dangerfield might put it this way – “I Tell Ya, Information Governance Gets No Respect”

Is it Time to Ditch the Per Hour Model for Document Review?  Here’s some food for thought.

Is it Possible for a File to be Modified Before it is Created?  Maybe, but here are some mechanisms for avoiding that scenario (here, here, here, here, here and here).  Best of all, they’re free.

Did you know changes to the Federal eDiscovery Rules are coming?  Here’s some more information.

Count Minnesota and Kansas among the states that are also making changes to support eDiscovery.

By the way, since the Electronic Discovery Reference Model (EDRM) annual meeting back in May, several EDRM projects (Metrics, Jobs, Data Set and the new Native Files project) have already announced new deliverables and/or requested feedback.

When it comes to electronically stored information (ESI), ensuring proper chain of custody tracking is an important part of handling that ESI through the eDiscovery process.

Do you self-collect?  Don’t Forget to Check for Image Only Files!

The Files are Already Electronic, How Hard Can They Be to Load?  A sound process makes it easier.

When you remove a virus from your collection, does it violate your discovery agreement?

Do you think that you’ve read everything there is to read on Technology Assisted Review?  If you missed anything, it’s probably here.

Consider using a “SWOT” analysis or Decision Tree for better eDiscovery planning.

If you’re an eDiscovery professional, here is what you need to know about litigation.

BTW, eDiscovery Daily has had 242 posts related to eDiscovery Case Law since the blog began!  Forty-four of them have been in the last six months.

Our battle cry for next September?  “Four more years!”  🙂

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

Court Awards Sanctions, But Declines to Order Defendants to Retain an eDiscovery Vendor – Yet – eDiscovery Case Law

In Logtale, Ltd. v. IKOR, Inc., No. C-11-05452 CW (DMR) (N.D. Cal. July 31, 2013), California Magistrate Judge Donna M. Ryu granted the plaintiff’s motion to compel responses to discovery and awarded partial attorney’s fees as a result of defendants’ conduct.  The judge did not grant the plaintiff’s request to order Defendants to retain an eDiscovery vendor to conduct a thorough and adequate search for responsive electronic documents, but did note that the court would do so “if there are continuing problems with their document productions”.

Case Background

The plaintiff, a shareholder in pharmaceutical company IKOR, Inc. (“IKOR”), a filed suit against the defendant and two of its officers, Dr. James Canton and Dr. Ross W. Tye, accusing the defendant of misrepresentations to induce the plaintiff to invest, breach of fiduciary duties, breach of contract, and breach of the implied covenant of good faith and fair dealing. The defendant brought counterclaims for breach of a licensing agreement, theft of intellectual property, and interference with prospective economic advantage.

In the motion to compel, the plaintiff sought to compel the defendants’ compliance with a prior court order to compel the production of all responsive documents as well as to compel production from Dr. Canton, who objected to several of Plaintiff’s discovery requests.  The plaintiff contended that Defendants’ document productions were incomplete and that they “failed to adequately search for all responsive electronic documents”, asserting that all three defendants had produced a total of only 121 emails, 109 of which were communications with the plaintiff (including only three pages in response to a request seeking all documents relating to the defendant’s communications with a company run by three of IKOR’s principals. The “dearth of responsive documents, as well as the lack of emails from at least one key individual”, caused the plaintiff to “raise concerns about the quality of Defendants’ document preservation and collection efforts” and express concerns about possible “evidence spoliation through the deletion of emails”. The plaintiff also contended that Dr. Canton waived his objections by failing to serve a timely response.

Judge’s Ruling

Judge Nyu agreed with the plaintiff’s, noting that “Given the paucity of documents produced by Defendants to date, as well as counsel’s own acknowledgment that Defendants’ productions have been incomplete, the court shares Plaintiff’s concerns about the inadequacy of Defendants’ search for responsive documents. Defense counsel has not been sufficiently proactive in ensuring that his clients are conducting thorough and appropriate document searches, especially in light of obvious gaps and underproduction. Under such circumstances, it is not enough for counsel to simply give instructions to his clients and count on them to fulfill their discovery obligations. The Federal Rules of Civil Procedure place an affirmative obligation on an attorney to ensure that a client’s search for responsive documents and information is complete.”  She also agreed with the plaintiff regarding Dr. Canton’s objections, since he “offered no reason for his late responses”.

Judge Nyu ordered the defendants to “produce all remaining responsive documents by no later than August 26, 2013”, noting that “if there are continuing problems with their document productions, the court will order them to retain the services of an e-discovery vendor”.  Judge Nyu also granted attorney’s fees for the plaintiff’s activities “as a result of Defendants’ conduct”, albeit at a reduced amount of $5,200.

So, what do you think?  Was the sanction warranted?   Should the judge have ordered the defendants to retain an eDiscovery vendor?  Please share any comments you might have or if you’d like to know more about a particular topic.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

Imagine if the Zubulake Case Turned Out Like This – eDiscovery Case Law

You’ve got an employee suing her ex-employer for discrimination, hostile work environment and being forced to resign.  During discovery, it was determined that a key email was deleted due to the employer’s routine auto-delete policy, so the plaintiff filed a motion for sanctions.  Sound familiar?  Yep. Was her motion granted?  Nope.

In Hixson v. City of Las Vegas, No. 2:12-cv-00871-RCJ-PAL (D. Nev. July 11, 2013), Nevada Magistrate Judge Peggy A. Leen ruled that the duty to preserve had not yet arisen when the plaintiff sent an internal email complaining she was being subjected to a hostile work environment and discrimination and that the failure to suspend its then-existing practice of automatically purging emails after 45 days did not warrant sanctions.

Here’s the timeline:

  • In March 2010, the plaintiff sent an email to a City of Las Vegas Personnel Analyst in the Employee Relations Division complaining she was being subjected to a hostile work environment and discrimination.
  • A chain of correspondence took place between April 6 and 7 of 2010 between the union representative assisting the plaintiff and a city employee.
  • In July 2010, the plaintiff alleged that the defendant constructively terminated her by forcing her to submit her resignation.
  • In September 2010, the plaintiff filed a complaint with the Nevada Equal Rights Commission.

The plaintiff and the defendant both produced the chain of correspondence from April 6 and 7 of 2010, but the defendant’s production omitted an email from the city employee (Dan Tarwater) to the union representative (Michael Weyland) commenting that “perhaps Weyland will have the good sense to have the Plaintiff retract her hostile work environment claim”.  Thus, the plaintiff filed a motion for sanctions.

The defendant indicated that their email system permanently deleted all messages after 45 days unless a sender or a recipient affirmatively saved the document to a folder, which didn’t happen with this particular email and also argued that “because Plaintiff has a copy of the email, any failure to disclose it is harmless”.

Judge Leen ruled that the “record in this case is insufficient to support a finding that the City was on notice Ms. Hixson contemplated litigation sufficient to trigger a duty to preserve electronically stored information by suspending its then-existing practice of automatically purging emails after 45 days.”  She also stated that “Plaintiff resigned July 15, 2010, and asserts she was constructively discharged. Nothing in the record suggests that on or before the date of her resignation, the Plaintiff threatened litigation, or informed the City that she had retained counsel about her employment disputes…By July 15, 2010, when Plaintiff resigned, the email system the City used as the time would have already purged Mr. Tarwater’s April 7, 2010, email unless it was saved to a folder.”

As a result, the court denied the plaintiff’s motion for sanctions.

So, what do you think?  Did the defendant have a duty to preserve the email and, if so, should the motion for sanctions have been granted?   Please share any comments you might have or if you’d like to know more about a particular topic.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

Scheindlin Reverses Magistrate Judge Ruling, Orders Sanction for Spoliation of Data – eDiscovery Case Law

If you’re hoping to get away with failing to preserve data in eDiscovery, you might want to think again if your case appears in the docket for the Southern District of New York with Judge Shira Scheindlin presiding.

As reported in by Victor Li in Law Technology News, (Scheindlin Not Charmed When Revisiting Spoliation a Third Time), Judge Scheindlin, who issued two of the most famous rulings with regard to eDiscovery sanctions for spoliation of data – Zubulake v. UBS Warburg and Pension Committee of the Montreal Pension Plan v. Banc of America Securities – sanctioned Sekisui America Corp. and Sekisui Medical Co. with an adverse inference jury instruction for deleting emails in its ongoing breach of contract case, as well as an award of “reasonable costs, including attorneys’ fees, associated with bringing this motion”.

Last year, the plaintiffs sued two former executives, including CEO Richard Hart of America Diagnostica, Inc. (ADI), a medical diagnostic products manufacturer acquired by Sekisui in 2009, for breach of contract.  While the plaintiffs informed the defendants in October 2010 that they intended to sue, they did not impose a litigation hold on their own data until May 2012. According to court documents, during the interim, thousands of emails were deleted in order to free up server space, including Richard Hart’s entire email folder and that of another ADI employee (Leigh Ayres).

U.S. Magistrate Judge Frank Maas of the Southern District of New York, while finding that the actions could constitute gross negligence by the plaintiffs, recommended against sanctions because:

  • There was no showing of bad faith, and;
  • The defendants could not prove that the emails would have been beneficial to them, or prove that they were prejudiced by the deletion of the emails.

The defendants appealed.  Judge Scheindlin reversed the ruling by Magistrate Judge Maas, finding that “the destruction of Hart’s and Ayres’ ESI was willful and that prejudice is therefore presumed” and the “Magistrate Judge’s Decision denying the Harts’ motion for sanctions was therefore ‘clearly erroneous.’”

With regard to the defendants proving whether the deleted emails would have been beneficial to them, Judge Scheindlin stated “When evidence is destroyed intentionally, such destruction is sufficient evidence from which to conclude that the missing evidence was unfavorable to that party.  As such, once willfulness is established, no burden is imposed on the innocent party to point to now-destroyed evidence which is no longer available because the other party destroyed it.”

Judge Scheindlin also found fault with the proposed amendment to Rule 37(e) to the Federal Rules of Civil Procedure, which would limit the imposition of eDiscovery sanctions for spoliation to instances where the destruction of evidence caused substantial prejudice and was willful or in bad faith, stating “I do not agree that the burden to prove prejudice from missing evidence lost as a result of willful or intentional misconduct should fall on the innocent party.  Furthermore, imposing sanctions only where evidence is destroyed willfully or in bad faith creates perverse incentives and encourages sloppy behavior.”

As a result, Judge Scheindlin awarded the defendants’ request for an adverse inference jury instruction and also awarded “reasonable costs, including attorneys’ fees, associated with bringing this motion”.  To see the full opinion order (via Law Technology News), click here.

So, what do you think?  Should sanctions have been awarded?   Please share any comments you might have or if you’d like to know more about a particular topic.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

Permissive Adverse Inference Instruction Upheld on Appeal – eDiscovery Case Law

In Mali v. Federal Insurance Co., Nos. 11-5413-cv, 12-0174-cv (XAP) (2d Cir. June 13, 2013), the Second Circuit explained the distinctions between two types of adverse inference instructions: a sanction for misconduct versus an explanatory instruction that details the jury’s fact-finding abilities. Because the lower court opted to give a permissive adverse inference instruction, which is not a punishment, the court did not err by not requiring the defendant to show that the plaintiffs acted with a culpable state of mind.

After a fire destroyed a barn converted into a residence, the plaintiffs sought to recover $1.3 to $1.5 million from their insurance policy. The insurance company made three payments before becoming skeptical of the plaintiffs’ claim. In particular, the company balked at the plaintiffs’ statement that they had high-end amenities, such as four refrigerators and copper gutters, and their sketch of the barn’s layout, which showed fourteen rooms, a second floor with four rooms and a bathroom, and four skylights. During discovery, the plaintiffs claimed they had no photographs of the barn, but at trial, an appraiser testified that the plaintiffs had shown her photographs of items in the barn and of the barn, which she testified only had one floor, not two as the plaintiffs claimed.

The defendants asked the court to impose an adverse inference instruction on the plaintiffs as a sanction for destroying the photographic evidence. Over the plaintiffs’ objection, the court instructed the jury that it could draw an adverse inference from the plaintiffs’ failure to produce the photographs. The jury agreed with the defendant and found the plaintiffs had submitted fraudulent claims that forfeited their insurance coverage.

On appeal, the plaintiffs argued that the jury’s verdict should be vacated and that a new trial was required because the court did not make findings to justify this sanction. However, the appellate court ruled that the plaintiffs’ argument was “based on a faulty premise” because the trial court “did not impose a sanction on the Plaintiffs.” Therefore, no findings were required. It also found the plaintiffs’ reliance on a prior Second Circuit decision, Residential Funding Corp. v. DeGeorge Financial Corp., 306 F.3d 99, 107 (2d Cir. 2002), where the court ruled that a trial court “must find facts that justify” an adverse inference instruction based on spoliation, inapposite. In Residential Funding, the plaintiff failed to meet its discovery obligations because it did not produce e-mails or backup tapes. The court refused to impose the defendant’s requested sanction, which was an instruction to the jury that it “‘should presume the e-mails . . . which have not been produced, would have disproved [Residential]’s theory of the case,’” because the defendant had not provided facts sufficient to support the sanction.

Here, the Second Circuit explained the distinction between the two types of adverse inferences in these cases: (1) one that punishes “misconduct that occurred outside the presence of the jury during the pretrial discovery proceedings, often consisting of a party’s destruction of, or failure to produce, evidence properly demanded by the opposing party,” and (2) one that “simply explains to the jury, as an example of the reasoning process known in law as circumstantial evidence, that a jury’s finding of certain facts may (but need not) support a further finding that other facts are true.” The court ruled that the latter instruction “is not a punishment” but instead is “an explanation to the jury of its fact-finding powers.”

The Mali court found the trial court’s instructions did not “direct the jury to accept any fact as true” or “instruct the jury to draw any inference against the Plaintiffs.” Because “the court left the jury in full control of all fact finding,” it fell within the explanatory classification of instructions.

So, what do you think?  Was the permissive adverse inference instruction warranted?   Please share any comments you might have or if you’d like to know more about a particular topic.

Case Summary Source: Applied Discovery (free subscription required).  For eDiscovery news and best practices, check out the Applied Discovery Blog here.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

Spoliation Sanctions Can Apply to Audio Files Too – eDiscovery Case Law

In Hart v. Dillon Cos., 2013 U.S. Dist. (D. Colo. 2013), Colorado Magistrate Judge David L. West granted the plaintiff’s Motion for Sanctions for Spoliation of Evidence for failing to preserve a tape recorded interview with the plaintiff and set a hearing and oral argument as to what sanctions should be imposed for October.

As noted in the opinion, here are the facts:

  • On August 23, 2011, the plaintiff was terminated by the defendant for allegedly giving herself the incorrect pay rate while working in the bookkeeping department. As part of the defendant’s investigation, a loss prevention specialist for the defendant secretly tape recorded an interview with the plaintiff on August 6 which in part led to the termination of the plaintiff.
  • On November 1, 2011, the plaintiff filed an E.E.O.C. charge of discrimination.
  • On November 7, 2011, the defendant denied the plaintiff’s request for arbitration knowing the plaintiff would probably litigate the matter.
  • Sometime between January and March of 2012, the loss prevention specialist inadvertently taped over or erased his interview with the plaintiff.
  • On January 30, 2012, the plaintiff filed her Complaint.
  • On March 1, 2012, the defendant issued a litigation hold on all related documentation. Before the contents of the tape were destroyed, Pollard prepared a “case narrative” in writing which the defendant asserts is substantially accurate and the plaintiff claims does not include exculpatory information and the tenor of the interview.

As noted in the opinion, there is a three part test to determine spoliation of evidence:

1. Is the evidence relevant to an issue at trial?

2. Did the party have a duty to preserve the evidence because it knew or should have known, that litigation was imminent?

3. Was the other party prejudiced by the destruction of the evidence?

Judge West found that the interview was relevant as the defendant relied on the interview as part of the decision to terminate the plaintiff.  He also found that the defendant had a duty to preserve the data as far back as November 7, 2011, when the plaintiff’s request for arbitration was denied.  And, he found that the plaintiff was prejudiced by destruction of the audio, noting as many as 21 discrepancies between the defendant’s case narrative and the plaintiff’s stated recollection in her deposition and affidavit.  As he noted:

“Defendant was clearly four (4) months late in issuing a “litigation hold” concerning the tape in Pollard’s possession, and the Court finds Defendant is highly culpable for the failure to preserve the taped interview.

A failure to preserve evidence may be negligent, grossly negligent, or willful. After the duty to preserve attaches, the failure to collect taped recording from a key player is grossly negligent or willful behavior.”

Thus, Judge West granted the plaintiff’s Motion for Sanctions for Spoliation of Evidence and ordered the hearing to determine the sanctions to be applied to the defendant.

So, what do you think?  Did the judge make the right decision?  Please share any comments you might have or if you’d like to know more about a particular topic.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.