1 2 3 4 5 6 7 8 UNITED STATES DISTRICT COURT 9 NORTHERN DISTRICT OF CALIFORNIA 10 San Francisco Division 11 SHOSHA KELLMAN, Case No. 17-cv-06584-LB
12 Plaintiff, ORDER ON PARTIES’ JOINT 13 v. DISCOVERY LETTER
14 WHOLE FOODS MARKET Re: ECF No. 182 CALIFORNIA, INC., et al., 15 Defendants. 16 17 INTRODUCTION 18 The parties to the above-captioned case brief two “sub-issues” in their joint letter. First, to 19 what extent the defendants (WF) may redact non-responsive and irrelevant information from their 20 productions, and, second, whether WF has sufficiently described a select number of documents 21 which were redacted or withheld for attorney-client privilege or work product privilege.1 The court 22 finds WF may not redact, only withhold, documents for non-responsive information and orders 23 WF to submit an updated privilege log consistent with the court’s orders below. 24 25 26 27 1 Joint Letter – ECF No. 182 at 1. Citations refer to material in the Electronic Case File (ECF); 1 ANALYSIS 2 WF contends the present joint letter is premature because the parties are still conferring on the 3 bounds of discovery. WF removed redactions from 501 documents the day before this letter was 4 filed,2 and the plaintiff asserts that the thirteen overarching categories of relevancy are “still in 5 dispute.”3 An updated privilege log was produced the day before this letter was filed. Thus, this 6 court’s opinion addresses only the two disputes raised in the letter. Should a dispute remain after 7 the production of a new privilege log and redactions for relevancy are removed, the parties are free 8 to file another joint discovery letter. 9 10 1. Redactions for Non-responsive and Irrelevant Information 11 The plaintiff asserts that WF does not have discretion to review and redact documents for 12 relevance or responsiveness. Instead, they assert the protective order protects any trade secret or 13 confidentiality concerns.4 Additionally, the plaintiff claims the ESI Protocol permits redactions 14 only for privilege or immunity, and that Rule 34 disfavors redactions for responsiveness because 15 such redactions alter the document.5 But the ESI Protocol makes no such restriction. It says a party 16 “may” redact material that is protected by any privilege or immunity recognized under applicable 17 law or regulation.6 WF responds that it is permitted to redact non-responsive information by the 18 ESI Protocol’s more general language that requires the parties to produce “any relevant, 19 responsive and non-privileged material” consistent with the requirements of the ESI Protocol.7 20 The plaintiffs also cite to the Federal Rules which require that documents be produced “as they 21 are kept in the usual course of business,” which, they assert, includes without redactions. Fed. R. 22 Civ. P. 34(b)(2)(E)(i); Evon v. Law Offs. of Sidney Mickell, No. S-09-0760-JAM (GGH), 2010 WL 23 24 2 Joint Letter – ECF No. 182 at 3. 3 Id. at 1. 25 4 Protective Order – ECF No. 71. 26 5 Joint Letter – ECF No. 182 at 2. 27 6 ESI Protocol – ECF No. 131 at 5:14–16 (“A producing party may redact . . . material that is protected from disclosure by any privilege or immunity recognized under applicable law or regulation.”) 1 455476, at *2 n.1 (E.D. Cal. Feb. 3, 2010) (“Redaction is, after all, an alteration of potential 2 evidence.”). WF claims that redactions for responsiveness and relevancy fulfill Rule 26’s 3 requirement that discovery be “proportional.”8 4 At this point, neither the ESI protocol nor the Federal Rules expressly prohibit redactions for 5 responsiveness. Other courts disfavor redactions for responsiveness except in very limited 6 circumstances. Laub v. Horbaczewski, 331 F.R.D. 516, 526 (C.D. Cal. Apr. 22, 2019) (“[A] party 7 may not redact otherwise responsive documents because those documents contain irrelevant 8 material.”); Doe v. Trump, 329 F.R.D. 262, 276 (W.D. Wash. 2018) (“[T]he unilateral redaction of 9 irrelevant or nonresponsive material from otherwise responsive documents gives rise to suspicion 10 that relevant material harmful to the producing party has been obscured and tends to make 11 documents confusing or difficult to use.”) (cleaned up); Barnes v. Equinox Grp., No. 10-cv-3586- 12 LB, 2012 WL 13060044, at *4 (N.D. Cal. June 14, 2012) (ordering production of financial 13 information and allowing narrow redactions for personal nonresponsive information). 14 This court follows the case law and the ESI Protocol’s own guidance that redactions may be 15 made to responsive documents to protect privileged information and, at least on this record, 16 disallows WF from redacting for responsiveness or relevancy. WF did not identify harm or 17 burden. Proportionality is a better argument for defining the methods to obtain responsive 18 information, not to redact for responsiveness or relevance after the ESI search has been conducted. 19 20 2. Redactions and Withholdings for Work Product and Attorney-Client Privilege 21 The parties also dispute whether certain documents withheld by WF qualify for protection 22 under the doctrines of attorney-client privilege or work-product protection, and if WF has done 23 enough to explain why the privilege applies. 24 25 26 27 1 2.1 Privileged attachments to an attorney-client communication 2 The plaintiff argues that WF provided an insufficient basis for asserting privilege on a number 3 of documents that were attached to non-privileged emails.9 To sufficiently withhold or redact a 4 document for privilege reasons, the withholding party must identify relevant names, dates, and 5 “the basis for the assertion of a privilege or other protection for all Privileged Material in the 6 document.”10 7 The plaintiffs cite to several cases which held that the generalized statement that a document 8 “reflects” legal advice is insufficient to support a privilege claim, e.g., Dolby Labs Licensing 9 Corp. v. Adobe Inc., 402 F. Supp. 3d 855, 866 (N.D. Cal. 2019), and that documents are not 10 inherently privileged if they were attached to a privileged communication. See, e.g., Fed. Trade 11 Comm. V. Boehringer Ingelheim Pharms., Inc., 180 F. Supp. 3d 1, 31 (D.D.C. 2016) 12 (“[A]ttachments to privileged communications are not thereby automatically privileged.”). WF 13 must show each attachment individually satisfies the criteria for privilege. 11 14 On February 23, 2021, WF provided the following description for ten at-issue documents: 15 “Attachment to attorney client communication regarding product incidents. Document was 16 collected and transmitted in course of, and in the furtherance of, the provision of legal advice. The 17 document further necessarily discloses the content of legal advice in the transmission email.”12 18 The plaintiff argues this description is insufficient grounds to assure that privilege applies not only 19 because the log does not support the assertion, but also claiming a document “reflects” legal 20 advice does not make it so. Additionally, some of the documents were attached to emails sent by a 21 third-party or did not identify an attorney as being a sender, recipient, carbon copy recipient, or 22 blind carbon copy recipient to the email.13 23 24
25 9 Privilege Log – ECF No. 182-17, Nos. 30, 42, 48–49, 53-54, 56–57, 100, 107. 26 10 Protective Order – ECF No. 71 at 11 (Section 14). 11 Joint Letter – ECF No. 182 at 5. 27 12 Id. at 6–7. 1 WF, apparently, amended the descriptions in an updated privilege log the day before this joint 2 letter was filed and addresses several documents directly.14 3 First, WF describes Line Nos. 100 and 107 as attachments to an attorney-client communication 4 that was “collected and transmitted in course of, and in the furtherance of, the provision of legal 5 advice.
Free access — add to your briefcase to read the full text and ask questions with AI
1 2 3 4 5 6 7 8 UNITED STATES DISTRICT COURT 9 NORTHERN DISTRICT OF CALIFORNIA 10 San Francisco Division 11 SHOSHA KELLMAN, Case No. 17-cv-06584-LB
12 Plaintiff, ORDER ON PARTIES’ JOINT 13 v. DISCOVERY LETTER
14 WHOLE FOODS MARKET Re: ECF No. 182 CALIFORNIA, INC., et al., 15 Defendants. 16 17 INTRODUCTION 18 The parties to the above-captioned case brief two “sub-issues” in their joint letter. First, to 19 what extent the defendants (WF) may redact non-responsive and irrelevant information from their 20 productions, and, second, whether WF has sufficiently described a select number of documents 21 which were redacted or withheld for attorney-client privilege or work product privilege.1 The court 22 finds WF may not redact, only withhold, documents for non-responsive information and orders 23 WF to submit an updated privilege log consistent with the court’s orders below. 24 25 26 27 1 Joint Letter – ECF No. 182 at 1. Citations refer to material in the Electronic Case File (ECF); 1 ANALYSIS 2 WF contends the present joint letter is premature because the parties are still conferring on the 3 bounds of discovery. WF removed redactions from 501 documents the day before this letter was 4 filed,2 and the plaintiff asserts that the thirteen overarching categories of relevancy are “still in 5 dispute.”3 An updated privilege log was produced the day before this letter was filed. Thus, this 6 court’s opinion addresses only the two disputes raised in the letter. Should a dispute remain after 7 the production of a new privilege log and redactions for relevancy are removed, the parties are free 8 to file another joint discovery letter. 9 10 1. Redactions for Non-responsive and Irrelevant Information 11 The plaintiff asserts that WF does not have discretion to review and redact documents for 12 relevance or responsiveness. Instead, they assert the protective order protects any trade secret or 13 confidentiality concerns.4 Additionally, the plaintiff claims the ESI Protocol permits redactions 14 only for privilege or immunity, and that Rule 34 disfavors redactions for responsiveness because 15 such redactions alter the document.5 But the ESI Protocol makes no such restriction. It says a party 16 “may” redact material that is protected by any privilege or immunity recognized under applicable 17 law or regulation.6 WF responds that it is permitted to redact non-responsive information by the 18 ESI Protocol’s more general language that requires the parties to produce “any relevant, 19 responsive and non-privileged material” consistent with the requirements of the ESI Protocol.7 20 The plaintiffs also cite to the Federal Rules which require that documents be produced “as they 21 are kept in the usual course of business,” which, they assert, includes without redactions. Fed. R. 22 Civ. P. 34(b)(2)(E)(i); Evon v. Law Offs. of Sidney Mickell, No. S-09-0760-JAM (GGH), 2010 WL 23 24 2 Joint Letter – ECF No. 182 at 3. 3 Id. at 1. 25 4 Protective Order – ECF No. 71. 26 5 Joint Letter – ECF No. 182 at 2. 27 6 ESI Protocol – ECF No. 131 at 5:14–16 (“A producing party may redact . . . material that is protected from disclosure by any privilege or immunity recognized under applicable law or regulation.”) 1 455476, at *2 n.1 (E.D. Cal. Feb. 3, 2010) (“Redaction is, after all, an alteration of potential 2 evidence.”). WF claims that redactions for responsiveness and relevancy fulfill Rule 26’s 3 requirement that discovery be “proportional.”8 4 At this point, neither the ESI protocol nor the Federal Rules expressly prohibit redactions for 5 responsiveness. Other courts disfavor redactions for responsiveness except in very limited 6 circumstances. Laub v. Horbaczewski, 331 F.R.D. 516, 526 (C.D. Cal. Apr. 22, 2019) (“[A] party 7 may not redact otherwise responsive documents because those documents contain irrelevant 8 material.”); Doe v. Trump, 329 F.R.D. 262, 276 (W.D. Wash. 2018) (“[T]he unilateral redaction of 9 irrelevant or nonresponsive material from otherwise responsive documents gives rise to suspicion 10 that relevant material harmful to the producing party has been obscured and tends to make 11 documents confusing or difficult to use.”) (cleaned up); Barnes v. Equinox Grp., No. 10-cv-3586- 12 LB, 2012 WL 13060044, at *4 (N.D. Cal. June 14, 2012) (ordering production of financial 13 information and allowing narrow redactions for personal nonresponsive information). 14 This court follows the case law and the ESI Protocol’s own guidance that redactions may be 15 made to responsive documents to protect privileged information and, at least on this record, 16 disallows WF from redacting for responsiveness or relevancy. WF did not identify harm or 17 burden. Proportionality is a better argument for defining the methods to obtain responsive 18 information, not to redact for responsiveness or relevance after the ESI search has been conducted. 19 20 2. Redactions and Withholdings for Work Product and Attorney-Client Privilege 21 The parties also dispute whether certain documents withheld by WF qualify for protection 22 under the doctrines of attorney-client privilege or work-product protection, and if WF has done 23 enough to explain why the privilege applies. 24 25 26 27 1 2.1 Privileged attachments to an attorney-client communication 2 The plaintiff argues that WF provided an insufficient basis for asserting privilege on a number 3 of documents that were attached to non-privileged emails.9 To sufficiently withhold or redact a 4 document for privilege reasons, the withholding party must identify relevant names, dates, and 5 “the basis for the assertion of a privilege or other protection for all Privileged Material in the 6 document.”10 7 The plaintiffs cite to several cases which held that the generalized statement that a document 8 “reflects” legal advice is insufficient to support a privilege claim, e.g., Dolby Labs Licensing 9 Corp. v. Adobe Inc., 402 F. Supp. 3d 855, 866 (N.D. Cal. 2019), and that documents are not 10 inherently privileged if they were attached to a privileged communication. See, e.g., Fed. Trade 11 Comm. V. Boehringer Ingelheim Pharms., Inc., 180 F. Supp. 3d 1, 31 (D.D.C. 2016) 12 (“[A]ttachments to privileged communications are not thereby automatically privileged.”). WF 13 must show each attachment individually satisfies the criteria for privilege. 11 14 On February 23, 2021, WF provided the following description for ten at-issue documents: 15 “Attachment to attorney client communication regarding product incidents. Document was 16 collected and transmitted in course of, and in the furtherance of, the provision of legal advice. The 17 document further necessarily discloses the content of legal advice in the transmission email.”12 18 The plaintiff argues this description is insufficient grounds to assure that privilege applies not only 19 because the log does not support the assertion, but also claiming a document “reflects” legal 20 advice does not make it so. Additionally, some of the documents were attached to emails sent by a 21 third-party or did not identify an attorney as being a sender, recipient, carbon copy recipient, or 22 blind carbon copy recipient to the email.13 23 24
25 9 Privilege Log – ECF No. 182-17, Nos. 30, 42, 48–49, 53-54, 56–57, 100, 107. 26 10 Protective Order – ECF No. 71 at 11 (Section 14). 11 Joint Letter – ECF No. 182 at 5. 27 12 Id. at 6–7. 1 WF, apparently, amended the descriptions in an updated privilege log the day before this joint 2 letter was filed and addresses several documents directly.14 3 First, WF describes Line Nos. 100 and 107 as attachments to an attorney-client communication 4 that was “collected and transmitted in course of, and in the furtherance of, the provision of legal 5 advice. The document further necessarily discloses the content of legal advice in the transmission 6 email.”15 WF does not identify an author. Thin as it is, this is an individual description that 7 outlines the basis for asserting privilege. Thus, it abides by the requirements of the case law, and 8 the Protective Order. 9 Second, Line No. 60 is no longer the subject of a privilege claim. WF produced the document 10 and updated the privilege log the day before filing this letter.16 11 Third, WF assures that it “already agreed to revise” the entry for Line No. 30 because it was 12 authored by an attorney. There is no point in the court issuing a decision on an obsolete 13 description. 14 Fourth, Line No. 48 was initially authored by a third party, but WF now explains that the 15 document is a part of a communication seeking legal advice by Mr. Pearlman and was sent as an 16 attachment to attorney Carol Bellon. This explanation is sufficient, but must be reflected in the 17 next version of the privilege log. 18 Fifth, it appears that Line Nos. 53 and 54 are attachments to Line 52 which is a privileged 19 email and the last email in a chain. These documents may be test reports, and may have been some 20 misunderstanding as to what email the documents Line Nos. 53 and 54 were attached. These 21 documents also may have been produced elsewhere in the production, making a ruling on these 22 documents premature. But, to be clear, the attorney-client privilege protects only communications 23 and not underlying facts and, should the attachments contain facts, they cannot be privileged. 24 25 26 14 Id. at 6–7. 27 15 Id. at 6–7; see ECF No. 182-18 at 3. 1 Upjohn Co. v. United States, 449 U.S. 383, 396 (1981). This analysis applies to attachments to any 2 emails. 3 Sixth, the plaintiff argues that the attachments listed at Line Nos. 30, 42, 49 and 56–57 were 4 all created a year before the parent email was authored. WF sees nothing about that fact that 5 precludes asserting privilege, and again claims the attachment may “divulge the email’s contents 6 as an attachment created at the time of transmission.”17 But again, “privilege extends only to 7 communications and not to facts.” Upjohn, 449 U.S. at 395. WF must provide a privilege log 8 description that provides a basis for asserting privilege over these documents and gives some 9 reason to believe they are not facts mistakenly swept under the attorney-client privilege or produce 10 them. 11 12 2.2 Privilege claims for documents with no person identified 13 On January 8, 2021, WF clawed back two documents as privileged but which were 14 inadvertently produced.18 WFM004077 and WFM0015733. On the September 14, 2021, version 15 of the privilege log, WF apparently fails to describe the documents as being a part of a 16 communication containing or prepared in anticipation of providing legal advice. Instead, one is 17 described as sent to a non-lawyer member of the legal department, and the other was “drafted by 18 Defendant’s legal department.” These descriptions are insufficient and WF must either amend the 19 privilege log to give a clearer basis for asserting privilege or produce the documents. 20 21 2.3 “Exclusive Brands Claims Guide” 22 WF claimed work product privilege over Line Nos. 25, 44–46, and 111–112, before replacing that 23 claim with a privilege claim as the document was attached to an attorney-client email which 24 “necessarily discloses the content of legal advice in the transmission email.” 19 This description is 25 26 17 Joint Letter – ECF No. 182 at 7. 27 18 Email between parties – ECF No. 182-20. 1 insufficient. WF must provide a revised description of the document that gives the basis for assertit 2 || privilege or produce the document. 3 4 CONCLUSION 5 In conclusion, the defendants are required to submit a revised privilege log within 14 days of 6 the filing of this order that is consistent with the court’s findings above. 7 8 IT IS SO ORDERED. 9 Dated: September 30, 2021 LAE 10 LAUREL BEELER I United States Magistrate Judge 12
15 16
= 17
Z 18 19 20 21 22 23 24 25 26 27 28