Close
Enter your
text here

Privileged

Another Disclosure of Privileged Documents Fails the Five Factor Test – eDiscovery Case Law
 

In Inhalation Plastics, Inc. v. Medex Cardio-Pulmonary, Inc., 2:07-CV-116 (N.D. Ohio), Ohio Magistrate Judge Norah McCann King found that the defendant had waived the attorney-client privilege was waived for 347 emails inadvertently produced, because they failed all factors in the five factor test to determine whether the inadvertent disclosure entitles the producing party to the return of the documents in question.

Background of Inadvertent Disclosure

In a breach of contract lawsuit, the defendant produced 7,500 hard copy pages including 347 pages of emails (4.6% of the total) for which legal personnel were senders or recipients. The defendant did not assert privilege on any of the 347 pages of emails until the plaintiff sought to depose those legal personnel. As a result of the defendant seeking to assert privilege on those emails, the plaintiff filed a motion for a determination that the documents are not privileged and submitted them for in camera review.

Five Factor Test

Noting that the producing party has the burden to prove that the disclosure of privileged documents was truly inadvertent, Judge King referenced the now popular five factor test to determine whether an inadvertent disclosure entitles the producing party to have the documents returned, as follows:

“(1) the reasonableness of precautions taken in view of the extent of document production, (2) the number of inadvertent disclosures, (3) the magnitude of the disclosure, (4) any measures taken to mitigate the damage of the disclosures, and (5) the overriding interests of justice.”

Analysis of Factors

With regard to the first factor, despite the fact that the defendant claimed that this production “was reviewed by several layers of attorneys who isolated the privileged documents and prepared for electronic production in the same way” as their previous productions, Judge King noted that the defendant did not specify “who reviewed the production, what steps were taken to review the documents for privilege or whether the production was different in form from prior productions” and noted that no privilege log was produced.  As a result, Judge King found that the defendant failed the first factor.

With regard to the second factor, Judge King compared the rate of disclosure of privileged documents in this case (4.6% of the total) to two other cases where privilege was also waived (134 out of 10,085 pages and 93 documents out of 15,000 documents respectively) and found the number of disclosures to be “relatively high”, so the defendant failed the second factor.

Regarding the third factor, the fact that the documents appeared to be relevant to the plaintiff's claims and they attempted to use them in depositions caused the defendant to fail the third factor.

On the fourth factor, the defendant did immediately invoke privilege when it discovered that the documents had been inadvertently produced.  However, they did not follow the procedure in Federal Rule of Civil Procedure 26(b)(5)(B), which requires:

“If information produced in discovery is subject to a claim of privilege . . . the party making the claim may notify any party that received the information of the claim and the basis for it. After being notified, a party . . . may promptly present the information to the court under seal for a determination of the claim. The producing party must preserve the information until the claim is resolved.”

As Judge King noted, “Medex did not identify any particular documents covered by the privilege, did not provide a proper privilege log and, beyond conclusory statements, Medex did not state a basis for the claimed privilege.”  So, they failed the fourth factor.

At this point, if this was a boxing match, it would be stopped.  In granting the plaintiff’s motion, Judge King stated: “To summarize, the Court finds that Medex did not take reasonable precautions to protect its privileged information, the number of documents disclosed is significant, no privilege log was provided at the time of disclosure, the contents of some of the documents may be relevant to the heart of the dispute, and Medex made insufficient attempts to mitigate its damage even after it learned of the disclosure.”

So, what do you think?  What do you to ensure your firm will pass the five factor test for inadvertent disclosures of privileged documents?  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 Two Years Old Today!
 

It’s hard to believe that it has been two years ago today since we launched the eDiscoveryDaily blog.  Now that we’ve hit the “terrible twos”, is the blog going to start going off on rants about various eDiscovery topics, like Will McAvoy in The Newsroom?   Maybe.  Or maybe not.  Wouldn’t that be fun!

As we noted when recently acknowledging our 500th post, we have seen traffic on our site (from our first three months of existence to our most recent three months) grow an amazing 442%!  Our subscriber base has nearly doubled in the last year alone!  We now have nearly seven times the visitors to the site as we did when we first started.  We continue to appreciate the interest you’ve shown in the topics and will do our best to continue to provide interesting and useful eDiscovery news and analysis.  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, The Electronic Discovery Reading Room, Unfiltered Orange, Litigation Support Blog.com, Litigation Support Technology & News, Ride the Lightning, InfoGovernance Engagement Area, Learn About E-Discovery, Alltop, Law.com, Justia Blawg Search, Atkinson-Baker (depo.com), ABA Journal, Complex Discovery, Next Generation eDiscovery Law & Tech Blog 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!

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!

We talked about best practices for issuing litigation holds and how issuing the litigation hold is just the beginning.

By the way, did you know that if you deleted a photo on Facebook three years ago, it may still be online?

We discussed states (Delaware, Pennsylvania and Florida) that have implemented new rules for eDiscovery in the past few months.

We talked about how to achieve success as a non-attorney in a law firm, providing quality eDiscovery services to your internal “clients” and how to be an eDiscovery consultant, and not just an order taker, for your clients.

We warned you that stop words can stop your searches from being effective, talked about how important it is to test your searches before the meet and confer and discussed the importance of the first 7 to 10 days once litigation hits in addressing eDiscovery issues.

We told you that, sometimes, you may need to collect from custodians that aren’t there, differentiated between quality assurance and quality control and discussed the importance of making sure that file counts add up to what was collected (with an example, no less).

By the way, did you know the number of pages in a gigabyte can vary widely and the same exact content in different file formats can vary by as much as 16 to 20 times in size?

We provided a book review on Zubulake’s e-Discovery and then interviewed the author, Laura Zubulake, as well.

BTW, eDiscovery Daily has had 150 posts related to eDiscovery Case Law since the blog began.  Fifty of them have been in the last six months.

P.S. – We still haven't missed a business day yet without a post.  Yes, we are crazy.

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 Case Law: Google Awarded $1 Million from Oracle, But Denied Discovery Costs
 

As noted in SiliconBeat and ARN, Judge William Alsup ordered Oracle on Tuesday to pay Google $1 million as reimbursement for Google’s fees for a court-appointed expert in their court battle over intellectual property and Google’s Android software.  However, the ruling is only a partial victory for Google, who was seeking $4 million from Oracle in reimbursement of costs associated with the case.

Claims Against Google Dismissed Despite Inadvertent Disclosure

As you may recall, claims against Google that its Android mobile phone platform infringes Oracle's copyrights relating to the Java computer language were dismissed by Judge Alsup back on May 31.  The claims were dismissed despite a significant inadvertent disclosure of information during discovery by Google, where drafts of a privileged email were not caught by Google’s search technology since they didn’t include the words “Attorney Work Product”, nor were they yet addressed to in-house counsel.  Judge Alsup ruled late last year that the draft emails were not privileged and the Federal Circuit court upheld that ruling.  However, these rulings did not ultimately cost Google as Oracle’s claims were dismissed.  As Judge Alsup noted, “Oracle initially sought six billion dollars in damages and injunctive relief but recovered nothing after nearly two years of litigation and six weeks of trial.”  Oracle plans to appeal.

Google Seeks Recovery of Costs

As the prevailing party, Google was able to seek recovery of costs and did so, seeking nearly $4 million from Oracle.  As noted above, Judge Alsup awarded Google $1 million as reimbursement for Google’s fees for a court-appointed expert.  However, Judge Alsup rejected Google's request that Oracle also pay $2.9 million for discovery-related costs, calling the search giant's arguments "unpersuasive".

“The problem with Google's e-discovery bill of costs is that many of [the] item-line descriptions seemingly bill for 'intellectual effort' such as organizing, searching, and analyzing the discovery documents," Judge Alsup stated in the ruling. "Most egregious are attempts to bill costs for 'conferencing,' 'prepare for and participate in kickoff call,' and communications with co-workers, other vendors, and clients. These are non-taxable intellectual efforts.”

So, what do you think?  Should Google have been reimbursed more?  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 Case Law: More Sanctions for Fry’s Electronics
 

In E.E.O.C. v Fry’s Electronics, Inc., No. C10-1562RSL, 2012 U.S. Dist. (W.D. Wash. July 3, 2012), Washington District Judge Robert S. Lasnik ordered several sanctions against the defendant in this sexual harassment case (including ordering the defendant to pay $100,000 in monetary sanctions and ordering that certain evidence be considered presumptively admissible at trial), but stopped short of entering a default judgment against the defendant.  This ruling came after having previously ordered sanctions against the defendant less than two months earlier.

Prior Sanctions

On May 10, Judge Lasnik granted in part plaintiffs' motion for sanctions in this case, finding that the defendant had spoliated evidence, including data and computer hard drives. In that ruling, Judge Lasnik believed that the prejudicial effect of the spoliation could be counteracted by “(a) instructing the jury that one of the justifications for firing [one of the plaintiffs] was pretextual and (b) allowing plaintiff considerable leeway in arguing what information might have been gleaned from the computer hard drives had they not been destroyed by defendant”. At the time, Judge Lasnik also indicated “some concern regarding the efficacy and thoroughness of defendant's searches” which led to more information being discovered after he ordered a second search.

Additional Spoliation and Misconduct

During a Rule 30(b)(6) deposition held on May 30, the plaintiffs learned for the first time that the accused individual had previously been accused of sexual harassment in 2001 and that an investigation had been conducted. According to Judge Lasnik, the defendant “intentionally withheld this information and the related documents from discovery by raising unfounded objections and ‘negotiating’ a narrowing of the discovery requests” and found the defendant's conduct to be “unfair, unwarranted, unprincipled, and unacceptable”.

Misconduct by the defendants noted by Judge Lasnik also included the redaction of responsive information, “[e]ven after defendant's objections to certain discovery requests were overruled”, as well as production of hundreds of pages of information with the “fallacious argument” that they were relevant to the claims.

Consideration of Default Judgment Sanction

Judge Lasnik noted that it is “once again left to determine whether to strike defendant's answer and enter default judgment against it”, but noted that dismissal is a “harsh sanction” and the following factors must be considered when determining “whether a dispositive sanction is appropriate under either its inherent powers or Rule 37(b): (1) the public's interest in the expeditious resolution of litigation; (2) the Court's need to manage its docket efficiently and effectively; (3) the risk of prejudice to the party seeking sanctions; (4) the public policy in favor of considering cases on the merits; and (5) the availability of less drastic sanctions.”  While finding that the first three factors supported a dispositive sanction, Judge Lasnik ruled against a dispositive sanction in factor 4, indicating that “[t]he public has an interest in a determination of those issues based on the facts, rather than by judicial fiat”.

Lesser Sanctions Ordered

Instead, Judge Lasnik ordered lesser sanctions, indicating that “Defendant's affirmative defenses related to (i) its efforts to prevent and correct harassment in the workplace, (ii) plaintiffs' failure to utilize protective and corrective opportunities provided by defendant, (iii) its good faith and/or privilege to act as it did in this case are STRICKEN.” He also stated that certain documents and testimony related to “other complaints or reports of sexual harassment” at the company were “presumptively admissible at trial”. He also ordered sanctions of $100,000 “to offset the excess costs caused by defendant’s discovery violations, to punish unacceptable behavior, and as a deterrent to future bad conduct” to be split evenly between the two individual plaintiffs, the EEOC and the Court Clerk.

So, what do you think?  Are you surprised that the defendant didn’t receive a default judgment sanction?  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 Case Law: Counsel, The Inadvertent Disclosure "Buck" Stops With You
 

Here is yet another case of inadvertently disclosed privileged documents.  In Blythe v. Bell, 2012 NCBC 42, North Carolina Business Superior Court Judge James L. Gale denied a motion for an order compelling the return of privileged documents inadvertently disclosed by the defendants, ruling that privilege had been waived on those documents.

In this case, the defendants produced 3.5 million documents on two hard drives which were ultimately determined to contain approximately 1,700 potentially privileged documents (the documents were to or from the outside counsel’s domain, an easy criteria to identify potentially privileged documents).  The defendants contracted with an outside consultant (Computer Ants) to obtain, process, and search their eMails for responsive documents.  For their part, the plaintiffs questioned whether Computer Ants was sufficiently qualified as an expert in electronic discovery to reasonably justify Defendants’ reliance on it to protect against the production of privileged information.  Prior to establishing Computer Ants, the owner (Thomas Scott) had worked as a truck driver, a Bass Pro Shop Security Manager, a respiratory therapist, and a financial auditor for a retail seller.  He had “never provided any forensic computer services in the context of a lawsuit” nor had ever “been engaged as a computer expert or provided an opinion in any legal proceeding”.  Sounds as if the plaintiffs had a legitimate concern.

Judge Gale used a five-factor balancing test previously used in Morris v. Scenera Research, LLC, which considers: “(1) the reasonableness of the precautions taken to prevent inadvertent disclosure; (2) the number of inadvertent disclosures; (3) the extent of the disclosures; (4) any delay in measures taken to rectify the disclosures; and (5) the overriding interests of justice.”

Judge Gale noted that “One federal district court characterizes the need for advance efforts to protect against waiver as “’paramount.’”  However, the defendant produced “the hard drives prepared by Computer Ants without any review or sampling or other quality assurance effort to assess whether the consultant’s efforts had been successful in eliminating privileged communications. Defendants admit that they relied exclusively on ‘this contractor and this procedure’ to filter out documents potentially subject to the attorney-client privilege.”

Since “the multi-factor balancing test applied by the federal courts on this record is controlled by the first factor”, Judge Gale, while noting that the “court takes no pleasure in finding the waiver of attorney-client privilege”, nonetheless had no choice but to do so based on the first factor alone.

So, what do you think?  How do you evaluate your eDiscovery provider to ensure their qualifications?  What precautions do you take to prevent inadvertent disclosure?  Please share any comments you might have or if you’d like to know more about a particular topic.

Source: JD Supra, via Brooks, Pierce, McLendon, Humphrey & Leonard LLP

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 Best Practices: Types Of Metadata and How They Impact Discovery
 

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, such as in cases like this one we recently covered here.

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 for eDiscovery.
  • 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.

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.

eDiscovery Best Practices: Documentation is Key to a Successful Discovery Effort
 

We like to point out good articles about eDiscovery on this blog to keep our readers aware of trends and best practices.  I recently read an article on InsideCounsel titled E-discovery: Memorializing the e-discovery process, written by Alvin Lindsay, which had some good specific examples of where good documentation is important to prevent sanctions and save litigation costs.

Litigation Holds

The author notes that, since the Zubulake opinions issued by Judge Shira Scheindlin in 2003 and 2004, 1) most jurisdictions have come to expect that parties must issue a litigation hold “as soon as litigation becomes reasonably foreseeable”, and 2) “oral” litigation holds are unlikely to be sufficient since the same Judge Scheindlin noted in Pension Committee that failure to issue a “written” litigation hold constitutes “gross negligence”.  His advice: “make sure the litigation hold is in writing, and includes at minimum the date of issue, the recipients and the scope of preservation”.  IT personnel responsible for deleting “expired” data (outside of retention policies) also need to receive litigation hold documentation; in fact, “it can be a good idea to provide a separate written notice order just for them”.  Re-issuing the hold notices periodically is important because, well, people forget if they’re not reminded.  For previous posts on the subject of litigation holds, click here and here.

Retention Policies and Data Maps

Among the considerations for documentation here are the actual retention and destruction policies, system-wide backup procedures and “actual (as opposed to theoretical) implementation of the firm’s recycle policy”, as well as documentation of discussions with any personnel regarding same.  A data map provides a guide for legal and IT to the location of data throughout the company and important information about that data, such as the business units, processes and technology responsible for maintaining the data, as well as retention periods for that data.  The author notes that many organizations “don’t keep data maps in the ordinary course of business, so outside counsel may have to create one to truly understand their client’s data retention architecture.”  Creating a data map is impossible for outside counsel without involvement and assistance at several levels within the organization, so it’s truly a group effort and best done before litigation strikes.  For previous posts on the subject of data maps, click here and here.

Conferences with Opposing Counsel

The author discusses the importance of documenting the nature and scope of preservation and production and sums up the importance quite effectively by stating: “If opposing parties who are made aware of limitations early on do not object in a timely fashion to what a producing party says it will do, courts will be more likely to invoke the doctrines of waiver and estoppel when those same parties come to complain of supposed production infirmities on the eve of trial.”  So, the benefits of documenting those limitations early on are clear.

Collecting, Culling and Sampling

Chain of custody documentation (as well as a through written explanation of the collection process) is important to demonstrating integrity of the data being collected.  If you collect at a broad level (as many do), then you need to cull through effective searching to identify potentially responsive ESI.  Documenting the approach for searching as well as the searches themselves is key to a defensible searching and culling process (it helps when you use an application, like FirstPass®, powered by Venio FPR™, that keeps a history of all searches performed).  As we’ve noted before, sampling enables effective testing and refinement of searches and aids in the defense of the overall search approach.

Quality Control

And, of course, documenting all materials and mechanisms used to provide quality assurance and control (such as “materials provided to and used to train the document reviewers, as well as the results of QC checks for each reviewer”) make it easier to defend your approach and even “clawback” privileged documents if you can show that your approach was sound.  Mistakes happen, even with the best of approaches.

So, what do you think?  These are some examples of important documentation of the eDiscovery process – can you think of others?  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 Case Law: Privilege Waived Because Defendants Failed to Notice “Something Had Gone Awry” with Their Production
 

In D’Onofrio v. Borough of Seaside Park, No. 09-6220 (AET), (D.N.J. May 30, 2012), New Jersey Magistrate Judge Tonianne Bongiovanni denied the defendants’ motion for discovery to reclaim privileged documents that were inadvertently produced, finding that privilege was waived because the defendants failed to take reasonable measures to rectify the disclosure. 

During the course of discovery in a case where the plaintiff alleged the defendants engaged in conduct that violated the plaintiff’s constitutional and statutory rights, the defendants reviewed 14 boxes of documents for possible production to the plaintiff. Six of those boxes, the “Ryan/McKenna” boxes, were reviewed by a partner at the law firm representing the defendants. The partner marked certain documents as privileged and then instructed a clerical employee to separate privileged and non-privileged documents, to Bates stamp the separated documents, and to burn the non-privileged documents onto a disc for production. The clerical employee failed to follow instructions, and privileged documents were inadvertently produced. 

Despite subsequent events where the defendants could have discovered the mistake, the defendants remained unaware of the accidental disclosure for approximately eight months until the plaintiff attached some of the privileged documents to an exhibit of his brief on an unrelated matter. The intervening events where the defendant failed to notice the production of privileged documents included the following: (1) the defendants voluntarily recalled the disc to reorganize the documents and remove electronic comments inadvertently left on some documents, and then resubmitted the disc to the plaintiff; (2) the defendants again recalled the disc after the plaintiff informed them the new disc was unreadable, and, after a clerical employee performed a “quality control audit” on the disc to ensure the defendants were producing the same set of documents, the defendants again produced the disc; (3) the defendants created a privilege log but did not realize the number of documents for the Ryan/McKenna boxes marked privileged was too small; and (4) after the plaintiff informed them that some of the documents on another disc were out of order, the defendants discovered hundreds of privileged documents from the “borough” boxes, another set of boxes, had been accidentally produced, but the defendants did not re-review the Ryan/McKenna documents that were produced.

Judge Bongiovanni articulated the applicable standard of review under Federal Rule of Evidence 502(b), stating that the factors to be considered in determining whether a waiver occurred are: (1) the reasonableness of the precautions taken to prevent inadvertent disclosure in view of the extent of the document production; (2) the number of inadvertent disclosures; (3) the extent of the disclosure; (4) any delay and measures taken to rectify the disclosure; and (5) whether the overriding interests of justice would or would not be served by relieving the party of its error.

Judge Bongiovanni had no trouble finding that the defendants “initially” took reasonable precautions to prevent production of privileged documents by devoting sufficient time to review, having a partner personally review all of the Ryan/McKenna documents, delegating to a clerical employee the task of separating privileged and non-privileged documents, and even by reviewing the disc before producing it to the plaintiff.

She then noted that the number and extent of the defendant’s unintentional disclosures were “neutral.”

Turning to the defendants’ efforts to rectify the disclosure, however, Judge Bongiovanni concluded that the defendants “did not take reasonable steps to remedy their error.” She stated, “Defendants should have been aware that something was amiss with their document production long before Plaintiff relied on three privileged documents” in his brief. Furthermore, although the defendants were not obligated to “engage in a post-production review to determine whether any protected communication or information [was] produced by mistake,” once a party is “‘on notice that something [i]s amiss with its document production and privilege review,’ then that party has an obligation to ‘promptly re-assess its procedures and re-check its production.’” The court pointed out that “the combination of the inadvertently produced attorney electronic comments and 728 pages of privileged Borough documents should have put the [ ] Defendants on notice that something had gone profoundly awry with their document production and privilege review.” A “reasonable person” would have rechecked the disc containing the Ryan/McKenna documents, and yet the defendants failed to do so.

Finally, the court also found that the interests of justice favored finding that a waiver occurred because the defendants’ “negligence” led to the inadvertent disclosure of privileged information.

So, what do you think?  Was the ruling fair?  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.

eDiscovery Case Law: Inadvertent Disclosure By Expert Waives Privilege
 

In Ceglia v. Zuckerberg, No. 10-CV-00569A(F), (W.D.N.Y. Apr. 19, 2012) (the case where Paul Ceglia is suing claiming 84% ownership of Facebook due to an alleged agreement he had with Mark Zuckerberg back in 2003), New York Magistrate Judge Leslie G. Foschio ruled that an information technology expert’s inadvertent disclosure waived the attorney-client privilege where the plaintiff could not show that it (1) took reasonable steps to prevent the disclosure of the e-mail and (2) took reasonable steps to rectify the error once it discovered the disclosure.

This case involved a dispute over the authenticity of a contract, and in seeking assistance to resolve pretrial matters, the plaintiff filed this motion to compel and asserted, among other things, that the attorney-client privilege should protect an e-mail that was inadvertently disclosed to the defendants. The court set forth the standard under Federal Evidence Rule 502(b) that applies to whether an inadvertent disclosure waives a privilege: “the privilege will not be waived if (1) the disclosure is inadvertent; (2) the privilege holder took reasonable steps to prevent disclosure; and (3) the privilege holder took reasonable steps to rectify the error.” Furthermore, “‘the burden is on the party claiming a communication is privileged” to establish that it met these requirements and that “the opposing party will not be unduly prejudiced by a protective order.”

Because the plaintiff failed to “personally supervise” the actions of the information technology expert he had hired, despite that he understandably hired such an expert to assist him while he was out of town, he “also failed to take reasonable steps to prevent the inadvertent disclosure” of the e-mail. Judge Foschio suggested that instead the defendants could have had the expert “first forward any documents” so that the plaintiff “could have reviewed the documents to ensure there w[ere] no extraneous, privileged materials attached.” If the plaintiff needed to oversee the expert in person, the court admonished, he “should have made himself present to do so.”

Judge Foschio also found that the plaintiff did not take reasonable steps to rectify the inadvertent disclosure. Noting that “the delay in seeking to remedy an inadvertent disclosure of privileged material is measured from the date the holder of the privilege discovers [ ] such disclosure,” and that “[g]enerally, a request for the return or destruction of inadvertently produced privileged materials within days after learning of the disclosure is required to sustain this second element,” the court pointed out that the plaintiff not only waited more than two months to try to rectify the error but also offered no explanation for such a lengthy delay.

Moreover, Judge Foschio stated, “Plaintiff has utterly failed to offer any explanation demonstrating that protecting belated protection of the . . . email will not be unduly prejudicial to Defendants.” Thus, because the plaintiff failed to establish any elements of the test required under the evidentiary rules, any privilege that may have attached to the disputed e-mail was waived.

Case Summary Source: Applied Discovery (free subscription required).

So, what do you think?  Should privilege have been waived or should the plaintiffs have been granted their request for the email to be returned?  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 Cautionary Tales: Inadvertent Disclosure Leaves Naked Short Selling Practices Exposed
 

While traveling back from Los Angeles for LegalTech West Coast 2012 (LTWC) this week, I saw an interesting story on the Above the Law blog (with references to The Economist, DeepCapture and Rolling Stone) regarding a litigation blunder committed by a major law firm on behalf of a major client, inadvertently disclosing an unredacted version of a sensitive document.

The California office of Morgan Lewis handling high-profile litigation for Goldman Sachs accidentally released an unredacted version of a document that the firm and its clients have spent years trying to keep secret.   Overstock.com sued Goldman Sachs (as well as Merrill Lynch and also other banks now no longer involved in the case), claiming that the banks caused its stock to fall through the practice of “naked” short selling (which is selling stock you don’t have and didn’t borrow, creating an artificial supply of stock shares).  The suit was dismissed by a California judge, who ruled that not enough of the alleged wrongdoing happened in the state.  According to The Economist:

“That was how things stood until the end of last week, when the defendants’ lawyers sent their opposition to a plaintiffs’ motion to the other parties in the case. One of the exhibits attached to this, presumably inadvertently, was an unredacted version of an earlier filing by Overstock, opposing the defendants’ motion to seal papers. Within this exhibit is an intriguing six-page section, “Facts Defendants Improperly Seek to Seal” (pages 14-20 of this), containing excerpts of e-mails written by Goldman and Merrill employees.”

According to DeepCapture, the responsible lawyer is alleged to be Joseph Floren, a partner at Morgan Lewis.  Ironically, Goldman and its attorneys have spent a significant amount of time (which means significant money) to keep this information sealed only to have this “blunder” release it publicly.

Matt Taibbi of Rolling Stone provides a commentary regarding information contained in the filing (language warning!), as follows:

“Now, however, through the magic of this unredacted document, the public will be able to see for itself what the banks’ attitudes are not just toward the “mythical” practice of naked short selling (hint: they volubly confess to the activity, in writing), but toward regulations and laws in general.

“Fuck the compliance area – procedures, schmecedures,” chirps Peter Melz, former president of Merrill Lynch Professional Clearing Corp. (a.k.a. Merrill Pro), when a subordinate worries about the company failing to comply with the rules governing short sales.

We also find out here how Wall Street professionals manipulated public opinion by buying off and/or intimidating experts in their respective fields. In one email made public in this document, a lobbyist for SIFMA, the Securities Industry and Financial Markets Association, tells a Goldman executive how to engage an expert who otherwise would go work for “our more powerful enemies,” i.e. would work with Overstock on the company’s lawsuit.”

A copy of the unredacted filing is located here.  Needless to say, clear naming of files as to whether they are redacted or unredacted, along with a thorough quality check, could have prevented this mistake.  I’ll leave it up to you to decide whether the mistake represents a form of karma in exposing these corporate practices.  🙂

So, what do you think?  What procedures do you have in place for avoiding inadvertent disclosures?  Please share any comments you might have or if you’d like to know more about a particular topic.

eDiscovery Daily will take a break for Memorial Day weekend.  See you on Tuesday!

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.