Close
Enter your
text here

Electronic Discovery

Defendant Ordered to Produce Archived Emails Even Though Plaintiff Failed to Produce Theirs – eDiscovery Case Law

In Finjan, Inc. v. Blue Coat Systems., 5:13-cv-03999-BLF (N.D. Cal. Oct. 17, 2014), California Magistrate Judge Paul S. Grewal granted the plaintiff’s motion ordering the defendant to produce relevant emails from its eight custodians, even though the plaintiff was unable to provide its own archival emails.

Case Background

As Judge Grewal stated “[t]o cut to the chase in this dispute over the scope and pace of Defendant Bluecoat Systems, Inc.’s document production in this patent infringement case”, the plaintiff moved to compel the defendant to produce email from eight custodians related to both technical documents and damages documents as well as damages testimony.  The defendant did not object to producing any of the technical discovery requested and raised only limited issues concerning the documents on damages, mostly objecting to producing custodial email from archival systems when the plaintiff was not able to do the same in return.

Each party agreed to identify eight custodians and ten terms per custodian for the other to search. The defendant did not dispute the relevance of either the custodians or search terms the plaintiff selected. But when the defendant learned that the plaintiff did not have former employees’ emails — except as produced in other litigations — the defendant balked at the idea that its custodians should have to turn over any email other than from active systems.

Judge’s Ruling

“Reduced to its essence, Rule 26(b)(2)(iii) requires this court to decide: have Blue Coat’s discovery responses been fair? Blue Coat’s discovery responses so far have largely been fair, but not entirely”, stated Judge Grewal.

Judge Grewal found that, with the exception of one document repository recently discovered (as acknowledged by defendant’s counsel), the defendant had completed its obligation regarding the technical document production.  Judge Grewal also ruled that the plaintiff “has identified no legitimate reason why it should be provided discovery on Blue Coat’s foreign sales or valuation on the whole”.  He also stated that the defendant “might reasonably be required to at least tell Finjan what the [third party] agreements are and the status of its efforts to secure consent.”

However, with regard to the archival email, Judge Grewal ruled as follows:

“Where Blue Coat has been less than fair is with respect to archival email for its eight custodians. Blue Coat may largely be in the right that it should not have to dig through legacy systems when Finjan is unable to the same for its custodians. But one party’s discovery shortcomings are rarely enough to justify another’s. And here, at least with respect to documents mentioning Finjan — the one specific category of documents Finjan could identify that it needed from archived email — Finjan’s request is reasonable.”

As a result, the defendant was ordered to “identify all license agreements whose production is awaiting third-party consent and the status of its efforts to secure that consent” within seven days and “produce all archival email from its eight designated custodians that mention Finjan and supplemental Interrogatories 5 and 6” within 21 days.

So, what do you think?  Should the defendant have to produce email when the plaintiff can’t do the same?  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.

More Organizations Have Data Breach Plans in Place, But More Are Reporting Data Breaches – eDiscovery Trends
 

You cannot talk about eDiscovery these days without talking about data security and breaches.  Bank of America, Home Depot and Target are just three examples of big name companies that have been hit by data breaches.  A recent study, conducted by the Ponemon Institute, shows that more organizations have data breach response plans and teams in place, yet more organizations are reporting at least one data breach in the past two years.

In this second annual study (Is Your Company Ready for a Big Data Breach?  The Second Annual Study on Data Breach Preparedness), sponsored by Experian® Data Breach Resolution, Ponemon Institute surveyed 567 executives in the United States about how prepared they think their companies are to respond to a data breach.  Here is a sampling of their key findings:

  • More companies have data breach response plans and teams in place. In 2014, 73% of companies had such a plan in place, up from 61% in last year’s study.  Also, more companies have teams to lead data breach response efforts – 72% of respondents, up from 67% last year.
  • Yet, data breaches have increased in frequency.  Last year, 33% of respondents said their company had a data breach involving the loss or theft of more than 1,000 records in the past two years. This year, the percentage has increased to 43%. Of those that experienced data breaches, 60% reported their company experienced more than one data breach in the past two years – up from 52% of respondents in 2013.
  • More companies have data breach response plans but they are not considered effective.  Despite the majority of companies having data breach plans, only 30% of respondents said their organizations are effective or very effective in developing and executing a data breach plan.
  • Maybe part of the reason is they don’t review their plans regularly.  Only 22% of respondents with data breach plans said their organizations review and update their plans at least yearly, with 41% of those respondents indicating no set time period for reviewing and updating the plan and 37% of those respondents having not reviewed or updated since the plan was put in place.

It’s also interesting to note that 17% of respondents were unsure whether their organization had a data breach in the past two years.  Really?  Well, at least that’s down from 22% in last year’s survey.

The 24 page report is chock-full of statistics and survey results and available here.  Thanks to Sharon Nelson and her always excellent Ride the Lightning blog for the tip.

So, what do you think? Does your organization have a plan for responding to data breaches?  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.

The Watergate 18 Minute Gap in Audio Recordings Has Nothing on This Case – eDiscovery Case Law

Anybody who remembers Watergate remembers the big deal made about an 18 1/2 minute gap in audio recordings reported by President Nixon’s secretary, Rose Mary Woods.  This case involves a gap in audio recordings much longer than that.

In Novick v. AXA Network, LLC, 07-CV-7767 (AKH) (KNF) (S.D.N.Y.Oct. 22, 2014), New York Magistrate Judge Kevin Nathaniel Fox granted the plaintiff’s request for sanctions against the defendant, awarding an adverse inference jury instruction for several weeks of spoliated audio recordings and also awarding “reasonable attorney’s fees and costs” associated with the motion as well as retaking several depositions.

Case Background

In this wrongful termination case, the plaintiff contended that the defendants committed several “strikes” justifying his request for sanctions, including spoliating audio recordings because “audio recordings from the time period August 28, 2006 through November 5, 2006 (approximately one-third of the entire time period ordered) are missing,” and “Defendants admit that they were likely erased and taped over” (per defendants letter to the plaintiff on October 25, 2013).  According to the plaintiff, “these recordings are from the most important time period of all – directly before and directly after Mr. Novick’s termination.”  The plaintiff also contended that the defendant had numerous deficiencies in their email production, where the defendant again made several promises to rectify the mistakes.

The defendants contended that “no responsive emails have been withheld and there is no evidence that any emails are missing.”  They did, however, “acknowledge that there are approximately eight weeks of audio recordings, within the period of time for which production of audio recordings was eventually ordered, that cannot be located or produced,” but “[t]his is not a new issue,” and the defendants advised plaintiff of it, on October 17, 2013, when the majority of the recordings were produced to him, and “[t]he fact that these weeks of recordings are missing constitutes the only real issue in plaintiff’s sanctions motion.”  The defendant also acknowledged that they “cannot now explain the absence of these recordings”.

Judge’s Ruling

Judge Fox stated that the court “determined that ‘[t]he defendants’ duty to preserve evidence arose when the plaintiff’s counsel notified the defendants, in the October 16, 2006 letter, that the audio recordings should be preserved because they may be relevant to future litigation’” and that the defendants conceded that “‘there are approximately eight weeks of audio recordings that are missing within the period for which defendants have been ordered to produce audio recordings,’ namely the period of August 28-31, 2006, and September 8-November 5, 2006, and they ‘have not been able to determine when, why or how these audio recordings came to be missing from the group of other audio recordings that were stored on DVDs and have been produced.’”  As a result, Judge Fox ruled that “the Court finds that the defendants spoliated relevant evidence, namely, audio recordings for the period August 28-31, 2006, and September 8-November 5, 2006”.

Judge Fox also noted that “Moreover, the defendants’ misconduct respecting the audio recordings was compounded by their deliberate and unjustified failure to search for and locate e-mail messages, as directed by the September 25, 2013 order. The defendants now admit that it was not until March 2014, that they realized that the Frontbridge archive was not searched for responsive documents, but contend this delay was ‘due to human error,’ without explaining what that error was or why they waited until March 2014 to conduct the investigation concerning the production of e-mail messages.”

As a result, Judge Fox Fox granted the plaintiff’s request for sanctions against the defendant, awarding an adverse inference jury instruction for the defendant’s actions and also awarding “reasonable attorney’s fees and costs” associated with the motion as well as retaking several depositions.

So, what do you think?  Did defense counsel’s quick reaction to the disclosure save the email’s privileged status?  Please share any comments you might have or if you’d like to know more about a particular topic.

BTW, we also covered a ruling on this case last year 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.

Simply Deleting a File Doesn’t Mean It’s Gone – eDiscovery Best Practices
 

I seem to have picked up a bit of a bug and I’m on cold medicine, so my writing brain is a bit fuzzy.  As a result, so I’m revisiting a topic that has come up a few times over the years that we covered early on in the blog’s history.  I should be back in the saddle with new posts next week!

Disk drives use an index or table to keep track of where each file begins and ends on the disk.  You may have heard terms such as “FAT” (file allocation table) or NTFS ({Windows} NT File System) – these filing systems enable the file to be retrieved quickly on the drive.  They’re like a “directory” of all of the active files on the disk.  When a file is “deleted” (i.e., actually deleted, not just moved to the Recycle Bin), the data for that file isn’t actually removed from the disk (in most cases).  Instead, the entry pertaining to it is removed from the filing system.  As a result, the area on the disk where the actual data is located becomes unallocated space.

Unallocated space, also known as inactive data or drive free space, is the area of the drive not allocated to active data. On a Windows machine, deleted data is not actually destroyed, but the space on the drive that can be reused to store new information. Until the unallocated space is overwritten with new data, the old data remains.  This data can be retrieved (in most cases) using forensic techniques. On MAC O/S 10.5 and higher, there is an application that overwrites sectors when a file is deleted. This process more securely destroys data, but even then it may be possible to recover data out of unallocated space.

Because the unallocated space on a hard drive or server is that portion of the storage space to which data may be saved, it is also where many applications “temporarily” store files when they are in use. For instance, temporary Internet files are created when a user visits a web page, and these pages may be “cached” or temporarily stored in the unallocated space.  Rebooting a workstation or server can also clear some data from the unallocated space on its drive.

Since computers are dynamic and any computer operation may write data to the drive, it is nearly impossible to preserve data in the unallocated space on the hard drive and that data is not accessible without special software tools. To preserve data from the unallocated space of a hard drive, the data must be forensically collected, which basically copies the entire drive’s contents, including every sector (whether those sectors contain active data or not). Even then, data in the unallocated space may not be complete. Because the unallocated space is used to store new data, writing a new file may overwrite part of a deleted file, leaving only part of that file in the unallocated space.

Nonetheless, “deleted” files have been recovered, collected and produced in numerous lawsuits, despite efforts of some producing parties to destroy that evidence.

So, what do you think?  Have you ever recovered deleted data that was relevant to litigation?  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.

The Importance of Metadata – eDiscovery Best Practices

This topic came up today with a client that wanted information to help justify the request for production from opposing counsel in native file format, so it’s worth revisiting here…

If an electronic document is a “house” for information, then metadata could be considered the “deed” to that house. There is far more to explaining a house than simply the number of stories and the color of trim. It is the data that isn’t apparent to the naked eye that tells the rest of the story. For a house, the deed lines out the name of the buyer, the financier, and the closing date among heaps of other information that form the basis of the property. For an electronic document, it’s not just the content or formatting that holds the key to understanding it. Metadata, which is data about the document, contains information such as the user who created it, creation date, the edit history, and file type. Metadata often tells the rest of the story about the document and, therefore, is often a key focus of eDiscovery.

There are many different types of metadata and it is important to understand each with regard to requesting that metadata in opposing counsel productions and being prepared to produce it in your own productions.  Examples include:

  • Application Metadata: This is the data created by an application, such as Microsoft® Word, that pertains to the ESI (“Electronically Stored Information”) being addressed. It is embedded in the file and moves with it when copied, though copying may alter the application metadata.
  • Document Metadata: These are properties about a document that may not be viewable within the application that created it, but can often be seen through a “Properties” view (for example, Word tracks the author name and total editing time).
  • Email Metadata: Data about the email.  Sometimes, this metadata may not be immediately apparent within the email application that created it (e.g., date and time received). The amount of email metadata available varies depending on the email system utilized.  For example, Outlook has a metadata field that links messages in a thread together which can facilitate review – not all email applications have this data.
  • Embedded Metadata: This metadata is usually hidden; however, it can be a vitally important part of the ESI. Examples of embedded metadata are edit history or notes in a presentation file. These may only be viewable in the original, native file since it is not always extracted during processing and conversion to an image format.
  • File System Metadata: Data generated by the file system, such as Windows, to track key statistics about the file (e.g., name, size, location, etc.) which is usually stored externally from the file itself.
  • User-Added Metadata: Data created by a user while working with, reviewing, or copying a file (such as notes or tracked changes).
  • Vendor-Added Metadata: Data created and maintained by an eDiscovery vendor during processing of the native document.  Don’t be alarmed, it’s impossible to work with some file types without generating some metadata; for example, you can’t review and produce individual emails within a custodian’s Outlook PST file without generating those out as separate emails (either in Outlook MSG format or converted to an image format, such as TIFF or PDF).

Some metadata, such as user-added tracked changes or notes, could be work product that may affect whether a document is responsive or contains privileged information, so it’s important to consider that metadata during review, especially when producing in native format.

Here’s an example of one case where the production of metadata was ordered and an answer to the question “Is it Possible for a File to be Modified Before it is Created?” (you might be surprised at the answer).

So, what do you think? Have you been involved in cases where metadata was specifically requested as part of discovery? 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.

Plaintiff Can’t “Pick” and Choose When it Comes to Privilege of Inadvertent Disclosures – eDiscovery Case Law

In Pick v. City of Remsen, C 13-4041-MWB (N.D. Iowa Sept. 15, 2014), Iowa District Judge Mark W. Bennett upheld the magistrate judge’s order directing the destruction of an inadvertently-produced privileged document, an email from defense counsel to some of the defendants, after affirming the magistrate judge’s analysis of the five-step analysis to determine whether privilege was waived.

Case Background

In this wrongful termination case, the plaintiff served a request for production of documents that included “all relevant non-privileged emails initiated by or received by the City of Remsen in regard to the Plaintiff and/or any of the issues set forth in Plaintiff’s complaint”.  Among the documents produced was an email, dated July 14, 2012, from defense counsel to Remsen Utility Board members and others discussing an upcoming Utility Board meeting.  Defense counsel learned of the email’s inadvertent disclosure on March 25, 2014, when the plaintiff served supplemental discovery responses on defense counsel and contacted plaintiff’s counsel within 34 minutes of the discovery.

Defense counsel asked that the email be destroyed. The plaintiff’s counsel suggested the email could be redacted to protect “advice relating to procedure,” but indicated he intended to rely on the remainder of the email unless ordered otherwise by the court.  The defendants’ filed a motion requesting that the court order the email’s destruction as an inadvertently produced privileged document, which the magistrate judge granted.

Judge’s Ruling

The Magistrate Judge, Leonard Strand, had applied the five-step analysis to determine the proper range of privilege to extend.  Those five factors were, as follows:

  1. The reasonableness of the precautions taken to prevent inadvertent disclosure in view of the extent of document production: Judge Strand found that the privileged email was “inconspicuously located among various non-privileged email messages”, which, based on the fact that defendants turned over to their counsel 440 pages of documents (including 183 pages of email messages, some pages of which contained more than one email), was upheld as “completely fair and accurate”;
  2. The number of inadvertent disclosures: Since there was only one inadvertent disclosure, Judge Bennett upheld the ruling as “not clearly erroneous”;
  3. The extent of the disclosures: Though the email was sent to six people, all six were privileged recipients of the email, so Judge Bennett upheld the ruling as “not clearly erroneous”;
  4. The promptness of measures taken to rectify the disclosure: Because defense counsel contacted plaintiff’s counsel just 34 minutes after learning of the email’s inadvertent disclosure and requested its destruction, Judge Bennett upheld the ruling as “not clearly erroneous”; and
  5. Whether the overriding interest of justice would be served by relieving the party of its error: Judge Strand, finding that the plaintiff “clearly has other evidence that he intends to rely on in support of his various claims”, ruled in favor of the defendant in this factor as well, which Judge Bennett upheld.

Judge Bennett summarized as follows: “The email is classic legal advice that should be protected by the attorney-client privilege…This interest of justice would be harmed here by permitting Pick to use the email at trial…Given the important nature of the attorney-client privilege and the manner in which the email was inadvertently disclosed, Judge Strand’s conclusion that the overriding interest in justice factor weighed against waiver is not clearly erroneous. Accordingly, Pick’s objection is overruled.”

So, what do you think?  Did defense counsel’s quick reaction to the disclosure save the email’s privileged status?  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.

What’s in a (File) Name? More Than You Think – eDiscovery Best Practices
 

When you’ve worked in litigation support and eDiscovery as long as some of us have, you just think a little bit differently – even when it comes to naming files and folders on your computer.  In her excellent Litigation Support Guru blog, Amy Bowser-Rollins provides some best practices to think more like a litigation support person.

In her post Litigation Support Naming Conventions, Amy shares her database mindset with these concepts:

  1. Using Underscores Instead of Spaces: Amy illustrates how you can use underscores instead of spaces in your file and folder names (e.g., Custodian_Name_Shared_Drive Custodian_Name.zip).  So, why would that be important?  Simply, empty space typically signifies the “end” of a character string.  When an application sees a space, it sees the “end” and stops processing. When the full string is not processed, it won’t be properly represented on your computer screen, won’t copy into emails automatically as hyperlinks, etc.  Some people prefer dashes instead of underscores as underscores can be difficult to detect when the name is underlined.
  2. Zero Filled Numbers: Is it apparent why this one is important?  It’s for sorting purposes.  In names, numbers sort left to right instead of numerically, so AnnualReport10 comes before AnnualReport8 and AnnualReport9 (because the first digit of ‘10’ – ‘1’ – comes before ‘8’ and ‘9’).  To get them to sort properly, include leading zeroes (e.g., AnnualReport08, AnnualReport09 and AnnualReport10).
  3. Dates in Year-Month-Day Format: This is another naming convention that is recommended for sorting purposes, again because numbers in names sort left to right instead of numerically (e.g., 11-11-2014-IncomingData would sort before 03-09-2012-IncomingData).  Naming the files in Year-Month-Day format (e.g., 2012-03-09-IncomingData or 20120309-IncomingData) ensures that they are properly date sorted.  Personally, I prefer dates with dashes for readability.

Using Amy’s tips can help you think more like the geeks that some of us are!  Thanks, Amy!

So, what do you think?  Do you have any file and folder naming preferences?  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.

Want an Automated, Easy and Inexpensive Way to Process Your Data? Read On – eDiscovery Trends

A couple of months ago, we had a laugh at Ralph Losey’s post that took a humorous look at the scenario where it’s Friday at 5 and you need data processed to be reviewed over the weekend.  It was a funny take on a real problem that most of us have experienced from time to time.  But, there may be a solution to this problem that’s automated, easy and inexpensive.

Anytime we talk about something that relates to our company, CloudNine Discovery, we always add the “shameless plug warning” to let people know that the topic relates to our software or a service we offer.  If you’re a regular reader of our blog, you know it doesn’t happen that often.  But, we have just made a major announcement that we believe will interest many of you.

Today, we are officially announcing the release of OnDemand Discovery®, our new application that enables you to upload your native data and have it processed and loaded directly into OnDemand®, our cloud-based online review tool.

It’s a 100% automated upload process that includes native file extraction from container files (such as Outlook PSTs and ZIP Files), metadata & text extraction and indexing, OCR of image files, duplicate identification and HTML creation, streamlining the process to get started reviewing documents for discovery.  The process automatically notifies you when we’ve received your data and then again when we’ve loaded and indexed it and when all processing (including advanced analytics for early data assessment) is complete.  So, you never have to wonder about the status of your processing job.

It’s ideal for situations where you receive data late on a Friday afternoon and have to get it ready to review over the weekend and also ideal for preparing small batches of files for review without having to run them through cumbersome processing software built for multiple gigabytes, not a small batch of files.  OnDemand Discovery is designed to handle two megabytes, two gigabytes or two hundred gigabytes or more!

There are three easy steps to give it a try:

  1. Sign up for a free account here.  You will receive an email with your credentials (including temporary password), to get started.
  2. When you first log in, you’ll see a button to “Upload Data”.  That will take you to a form to download the OnDemand Discovery client (which is a Windows based client application that resides on your desktop) for uploading data for processing.  Download and install the client to upload data.
  3. Once the client is downloaded and installed, launch the client, log in with your newly created credentials and simply follow the wizard prompts to upload the desired data set and put it into the project of your choice (which you can create if it doesn’t already exist).  It’s that easy!

For more information, feel free to check out our press release on our news page here.  You can also contact me at daustin@cloudnincloudnine.comm for more information as well.

And, as always, 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.

Judgment of $34 Million against Insurer Dodging Malpractice Claim is a “Dish” Served Cold – eDiscovery Case Law
 

In my hometown of Houston, attempting to deny coverage to a client successfully sued for discovery-related negligence cost OneBeacon Insurance Company a $34 million judgment by a federal jury.

As reported by Robert Hilson in ACEDS (Insurer dodging malpractice claim must pay $34 million for attorney’s discovery blunder, subscription required), OneBeacon Insurance Company attempted to rescind a policy from T. Wade Welch & Associates (TWW), the Houston-based law firm that was sued by former client Dish Network in 2007 after one of its attorneys provided incomplete discovery responses to Dish’s adversary. That failure resulted in so-called “death penalty” sanctions against Dish in a contractual interference case brought by Russian Media Group (RMG), which accepted a $12 million settlement.

After Dish won an arbitration award against TWW for that amount last year, OneBeacon sued TWW in federal court seeking a declaration the law firm voided coverage on its policy by failing to disclose the Dish sanctions prior to entering into that policy. OneBeacon alleged that TWW should have known that those penalties in the Dish case would give rise to a malpractice claim, which would trigger a so-called “prior knowledge exclusion” in the insurance policy that rescinds coverage, the insurer claimed. It also accused the firm of making misrepresentations on its policy application.

However, a jury in the US District Court for the Southern District of Texas begged to differ, finding that:

  • OneBeacon failed to move for a swift settlement with Dish when its liability had become clear; and
  • OneBeacon’s failure to settle the Dish claim amounted to gross negligence.

The jury assessed damages as follows:

  • TWW’s lost profits sustained in the past: $3 million;
  • TWW’s lost profits that, in reasonable probability, it will sustain in the future: $5 million;
  • Sum assessed in exemplary damages for OneBeacon’s gross negligence: $5 million;
  • Sum assessed in exemplary damages because OneBeacon’s conduct was committed knowingly: $7.5 million.

TOTAL: $20.5 million.  Plus, although the OneBeacon policy had a $5 million limit, the “Stowers Doctrine,” which holds that an insurer undertaking the defense of an insured has the obligation to make a good faith attempt to settle the insured’s claim within those policy limits, additionally put the company on the hook for the entire $12.6 million arbitration settlement.  Ouch!

This was after US district Judge Gray Miller, in June, denied summary judgment to OneBeacon, finding that it was not clear from the evidentiary record whether TWW attorneys should have reasonably foreseen the malpractice claim that eventually arose from the Dish sanctions.

For more information on the case, including the jury’s verdict, click here (subscription required).

So, what do you think?  Should OneBeacon have been “on the hook” for the settlement amount or should the “prior knowledge exclusion” have excluded them?  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.

Dealing with the Departed – eDiscovery Best Practices
 

Having addressed this recently with a client, I thought this was a good topic to revisit here on the blog…

When litigation hits, key activities to get a jump on the case include creating a list of key employees most likely to have documents relevant to the litigation and interviewing those key employees, as well as key department representatives, such as IT for information about retention and destruction policies.  These steps are especially important as they may shed light on custodians you might not think about – the departed.

When key employees depart an organization, it’s important for that organization to have a policy in place to preserve their data for a period of time to ensure that any data in their possession that might be critical to company operations is still available if needed.  Preserving that data may occur in a number of ways, including:

  • Saving the employee’s hard drive, either by keeping the drive itself or by backing it up to some other media before wiping it for re-use;
  • Keeping any data in their network store (i.e., folder on the network dedicated to the employee’s files) by backing up that folder or even (in some cases) simply leaving it there for access if needed;
  • Storage and/or archival of eMail from the eMail system;
  • Retention of any portable media in the employee’s possession (including DVDs, portable hard drives, smart phones, etc.).

As part of the early fact finding, it’s essential to determine the organization’s retention policy (and practices, especially if there’s no formal policy) for retaining data (such as the examples listed above) of departed employees.  You need to find out if the organization keeps that data, where they keep it, in what format, and for how long.

When interviewing key employees, one of the typical questions to ask is “Do you know of any other employees that may have responsive data to this litigation?”  The first several interviews with employees often identify other employees that need to be interviewed, so the interview list will often grow to locate potentially responsive electronically stored information (ESI).  It’s important to broaden that question to include employees that are no longer with the organization to identify any that also may have had responsive data and try to gather as much information about each departed employee as possible, including the department in which they worked, who their immediate supervisor was and how long they worked at the company.  Often, this information may need to be gathered from Human Resources.

Once you’ve determined which departed employees might have had responsive data and whether the organization may still be retaining any of that data, you can work with IT or whoever has possession of that data to preserve and collect it for litigation purposes.  Just because they’re departed doesn’t mean they’re not important.

So, what do you think?  Does your approach for identifying and collecting from custodians include departed custodians?  Please share any comments you might have or if you’d like to know more about a particular topic.

Image © Warner Bros.

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.