McNamara v. Wells Fargo & Company

• Court: District Court, S.D. California
• Decided: July 29, 2022
• Docket: 3:21-cv-01245
• Status: Unknown

Opinion

1 2 3 4 5 6 7 8 UNITED STATES DISTRICT COURT 9 SOUTHERN DISTRICT OF CALIFORNIA 10 11 THOMAS W. MCNAMARA, as the Case No.: 21-CV-1245-LAB-WVG Court-Appointed Receiver for Triangle 12 Media Corporation; Apex Capital Group, ORDER ON DISCOVERY DISPUTES 13 LLC; and their successors, assigns, affiliates, and subsidiaries, 14 Receiver, 15 v. 16 WELLS FARGO & COMPANY; and 17 WELLS FARGO BANK, N.A., 18 Defendants. 19

20 Pending before the Court are Thomas W. McNamara (“Receiver”) and Wells Fargo 21 & Company and Wells Fargo Bank, N.A.’s (“Defendants”) (collectively, “Parties”) 22 respective briefs regarding discovery disputes the Receiver raises. (Doc. Nos. 28, 29.) The 23 Receiver seeks to compel Defendants’ responses to certain requests for production of 24 documents (“RFPs”) the Receiver propounded. Defendants object on a variety of grounds 25 to each of the RFPs at issue. The Court has reviewed and considered the entirety of the 26 Parties’ submissions. Having done so, the Court (1) SUSTAINS IN PART AND DENIES 27 IN PART Defendants’ objections to RFPs 23 through 26; (2) OVERRULES Defendants’ 28 1 objections to RFPs 34 through 38; (3) SUSTAINS IN PART AND DENIES IN PART RFP 2 45; (4) SUSTAINS Defendants’ objection to RFPs 46 and OVERRULES Defendants’ 3 objection to 47; and (5) OVERRULES RFPs 54 and 55 and elaborates below. 4 I. PROCEDURAL BACKGROUND 5 This is action hinges on Receiver’s allegations of fraud against Defendants. Between 6 2009 and 2018, Defendants provided banking services to Apex Capital Group, LLC and 7 Triangle Media Corporation (“Enterprises”). (Doc. No. 1, ¶¶ 8, 140.) In 2018, the Federal 8 Trade Commission sued the Enterprises for perpetuating financial fraud against consumers 9 through so-called “free-trial” schemes. (Doc. No. 20, 1, 27-28.) Consequently, Thomas W. 10 McNamara was appointed as the Receiver, and he initiated this litigation on July 8, 2021. 11 (Doc. No. 1.) The Receiver brought 12 claims against Defendants for their role in 12 facilitating the Enterprises’ fraud. (Id.) Most of those claims survived Defendants’ August 13 25, 2021 Motion to Dismiss. (Doc. No. 14.) In particular, on March 30, 2022, District Judge 14 Larry Alan Burns issued his Order Granting in Part and Denying in Part Motion to Dismiss, 15 finding the Receiver’s claims for aiding and abetting (1) fraud; (2) breach of fiduciary duty; 16 (3) conversion; and (4) fraudulent transfer as well as (5) civil conspiracy could proceed. 17 (Doc. No. 20.) The discovery disputes pertinent to this Order followed. 18 Specifically, on July 1, 2022, this Court’s Chambers convened an informal 19 conference regarding five discovery disputes arising from Defendants’ objections to the 20 Receiver’s RFPs. The Parties timely raised the disputes after exhaustively meeting and 21 conferring and thus satisfied their obligations to comply with Rule 26.1(a) of this District’s 22 Civil Local Rules and Rule IV(C) of this Court’s Civil Chambers Rules. On July 5, 2022, 23 this Court issued its Order Setting Briefing Schedule on the disputes. (Doc. No. 26.) On 24 July 11, 2022, Defendants timely filed their Discovery Brief. (Doc. No. 28.) On July 18, 25 2022, the Receiver timely filed his responsive Discovery Brief. (Doc. No. 29.) Thus, the 26 discovery disputes have been fully briefed and are now ripe for this Court’s adjudication. 27 / / / 28 / / / 1 II. LEGAL STANDARD 2 Rule 26 of the Federal Rules of Civil Procedure governs this discovery dispute. 3 Under Rule 26, a party may take discovery of “any non-privileged matter that is relevant 4 to any party’s claim or defense and proportional to the needs of the case.” Fed. R. Civ. P. 5 26(b)(1). Relevance is the Court’s threshold inquiry and turns on whether evidence (1) has 6 any tendency to make a fact more or less probable than it would be without the evidence; 7 and (2) the fact is of consequence in determining the action. Fed. R. Evid. 401; Finjan, 8 LLC v. ESET, LLC, 2021 WL 1541651, at *3 (S.D. Cal. Apr. 20, 2021). At all times, 9 “District Courts have wide latitude in controlling discovery,” including in determining 10 relevancy for discovery purposes. U.S. Fidelity and Guar. Co. v. Lee Investments, LLC, 11 641 F.3d 1126, 1136 (9th Cir. 2011); Facedouble, Inc. v. Face.com, 2014 WL 585868, at 12 *1 (S.D. Cal. Feb. 13, 2014). 13 Once the propounding party establishes relevance, the responding party bears the 14 burden of substantiating its objections to show discovery should not be permitted. 15 Blankenship v. Hearst Corp., 519. F.2d 418, 429 (9th Cir. 1975); Cancino Castellar v. 16 McAleenan, 2020 WL 1332485, at *4 (S.D. Cal. Mar. 23, 2020) (quoting Superior 17 Commc'ns v. Earhugger, Inc., 257 F.R.D. 215, 217 (C.D. Cal. 2009) (“Once the 18 propounding party establishes [relevance], the party who resists discovery has the burden 19 to show discovery should not be allowed, and has the burden of clarifying, explaining, and 20 supporting its objections.’”). Specific to document requests, a request for production of 21 documents may relate to any matter that may be inquired into under Rule 26(b). Fed. R. 22 Civ. P. 34(a)(1). For each request for production, the opposing party’s “response must 23 either state that inspection and related activities will be permitted as requested or state with 24 specificity the grounds for objecting to the request, including the reasons.” Fed. R. Civ. P. 25 34(b)(2)(B); see also Ins. King Agency, Inc. v. Digital Media Sols., LLC, 2022 WL 26 2373357, at *2 (S.D. Cal. June 30, 2022) (emphasis added). 27 / / / 28 / / / 1 When analyzing the proportionality of a party's discovery requests, courts consider: 2 (1) the importance of the issues at stake in the action; (2) the amount in controversy; (3) 3 the parties’ relative access to the information; (4) the parties’ resources; (5) the importance 4 of the discovery in resolving the issues; and (6) whether the burden or expense of the 5 proposed discovery outweighs its likely benefit. Fed. R. Civ. Proc. 26(b)(1). To that end, 6 arguments against discovery – on the basis of proportionality or otherwise – must be 7 supported by “specific examples or articulated reasoning.” Medimpact Healthcare Sys., 8 Inc. v. IQVIA Inc., 2021 WL 5605281, at *2 (S.D. Cal. July 15, 2021) (citing U.S. E.E.O.C. 9 v. Caesars Entm't., 237 F.R.D. 428, 432 (D. Nev. 2006).). 10 III. DISCUSSION 11 a. Defendants’ Objections to RFPs 23 through 26 12 RFPs 23 through 26 are the first set of discovery requests at issue. Respectively, the 13 RFPs seek to obtain documents and communications (1) regarding Defendants’ compliance 14 and reporting efforts; (2) Defendants generated about the Enterprises to comply with 15 Defendants’ reporting policies; (3) regarding Defendants’ due diligence or investigation of 16 any actual, potential, alleged, or suspected suspicious activity involving the Enterprises; 17 and (4) regarding the Enterprises concerning “actual, suspected, alleged, or potential 18 violations of the Bank Secrecy Act, USA PATRIOT Act, FinCEN regulations, Customer 19 and Enhanced Due Diligence rules, Customer Identification Program requirements, 20 and/ore AML or KYC policies or laws.” (Doc. No. 29, Exh. 1, 3:24-28; 5:7-12; 6:12-17; 21 7:20-26.) 22 Defendants assert the Suspicious Activity Report (“SAR”) privilege to object to 23 production of documents responsive to the Receiver’s RFPs 23 through 26. Defendants 24 argue the Bank Secrecy Act (“BSA”) “prohibits [Defendants] from discover[ing] any 25 information that would reveal whether it did or did not file a suspicious activity report.” 26 (Doc. No. 28, 2:8-9.) In doing so, Defendants emphasize the “prohibition is unqualified 27 and cannot be waived” and string cite case law beyond this Court’s jurisdiction in support 28 thereof. Simultaneously, Defendants offer to produce documents that reveal “underlying 1 facts, transactions, and documents, such as account information, bank statements, and 2 financial transactions” while also maintaining the Receiver’s RFPs exceed this permissible 3 scope. (Id., 4: 1-5.) In response, Receiver adds color to Defendants’ offer to compromise. 4 Specifically, the Receiver notes that, during their meet and confer discussions, the Parties 5 already agreed Defendants “[should] not produce a SAR [or] any information that would 6 reveal the existence or non-existence of a SAR” but that Defendants could produce “the 7 underlying facts, transactions, and documents upon which a SAR is based.” (Doc. No. 29, 8 3:7-12.) Thus, the Court finds the trouble here is not whether documents should be 9 produced to some extent. The dispute instead centers on which particular documents are 10 discoverable and what the process governing such determinations should be. 11 As a foundational matter, the Court finds RFPs 23 through 26 are relevant to the 12 Receiver’s claims throughout this litigation. The Court agrees with the Receiver that the 13 document requests “will show [Defendants] knowledge of the Enterprises’ fraud, which is 14 a key disputed element,” particularly because the RFPs target Defendants’ surveillance, 15 compliance, reporting, and due diligence efforts. (Doc. No. 29, 2:26-28.) Although they do 16 not expressly concede the matter, Defendants’ repeated assertion of the SAR privilege is 17 demonstrative of their agreement that what RFPs 23 through 26 seeks is indeed relevant to 18 the Action. 19 Under the Annunzio-Wylie Anti-Money Laundering Act, banks are required to 20 report suspicious transaction activities to the appropriate authorities through a SAR. See 21 31 U.S.C. § 5318 et seq. Further, 12 C.F.R. section 21.11 provides “no national bank, and 22 no director, officer, employee, or agent of a national bank, shall disclose a SAR or any 23 information that would reveal the existence of a SAR.” See also 31 U.S.C. § 24 5318(g)(2)(A)(i). However, this bar on disclosure does not apply to “supporting” 25 documentation, as long as such disclosure would not reveal the existence or contents of a 26 SAR, which is in line with the agreement the Parties reached during their meet and confer 27 efforts. Erhart v. BofI Holding, Inc., 2018 WL 5994417, at *6 (S.D. Cal. Nov. 15, 2018) 28 (citing, e.g., United States v. Holihan, 248 F. Supp. 2d 179, 187 (W.D.N.Y. 2003) 1 (“Although in some cases the supporting documentation may disclose the existence of an 2 SAR and its contents, thereby thwarting the regulation's intent, any supporting 3 documentation which would not reveal either the fact that an SAR was filed or its contents 4 cannot be shielded from otherwise appropriate discovery based solely on its connection to 5 a[] SAR.”); Weil v. Long Island Sav. Bank, 195 F. Supp. 2d 383, 389 (E.D.N.Y. 2001) 6 (“The privilege is, however, limited to the SAR and the information contained therein; it 7 does not apply to the supporting documentation.”). 8 Turning to which of the relevant documents are discoverable and the process that 9 should govern such determinations, the Court notes this District’s 2018 Erhart decision is 10 instructive. There, the Court overruled defendants’ SAR privilege objection and granted 11 plaintiff’s motion to compel responses to RFPs “subject to the prohibition that no SARs or 12 documents that would reveal the existence of a SAR would be produced.” Erhart, 2018 13 WL 5994417, at *6. Thus, the Court’s finding aligned with the BSA and its regulatory 14 provisions, providing “no national bank, and no director, officer, employee, or agent of a 15 national bank, shall disclose a SAR or any information that would reveal the existence of 16 a SAR.” 31 U.S.C. § 5318(g)(2)(A)(i). Specific to this matter, the Erhart Court’s finding 17 aligns with the Parties’ own agreement. Thus, the Court arrives to the same conclusion 18 Erhart and the Parties here reached: at least some documents RFPs 23 through 26 implicate 19 are discoverable, namely those that do not constitute a SAR itself or reveal the existence 20 or non-existence of a SAR. As Erhart articulated, “producing responsive ‘supporting’ 21 documents would not necessarily divulge information regarding whether an actual SAR 22 was eventually filed.” Erhart, 2018 WL 5994417, at *6. 23 The only remaining issue is how discoverability should be decided. The Erhart 24 Court exclusively left it to the responding party, which is what the Receiver proposes here. 25 This Court, however, is not so convinced the Receiver’s proposal is workable. The Court 26 is inclined to agree with Defendants that in camera review would help determine what is 27 and is not within the scope of the SAR privilege and potentially bypass a deluge of resulting 28 discovery disputes. While the Court heavily disfavors mediating discovery disputes by the 1 document, the delicate nature of what falls within the SAR privilege demands a non- 2 traditional approach here. Accordingly, the Court SUSTAINS IN PART AND 3 OVERRULES IN PART Defendants’ objections to RFPs 23 through 26 and directs 4 Defendants as follows. 5 No later than 30 days from the date of this Order’s issuance, Defendants shall 6 produce documents to the Receiver without the Court’s involvement that is plainly outside 7 of the SAR privilege and would reveal information regarding underlying facts, 8 transactions, and documents upon which a SAR is based and not reveal the existence or 9 non-existence of a SAR. On the other hand, where a document’s discoverability is less than 10 clear, the Court finds it appropriate for Defendants to produce a privilege log to the 11 Receiver and subsequently engage in an exhaustive meet and confer. Should the Parties 12 reach an impasse over the SAR privilege’s applicability to a particular document, the 13 Parties shall jointly contact this Court’s Chambers within 30 days of the dispute arising 14 and request this Court’s in camera review. 15 b. Defendants’ Objections to RFPs 34 through 38 16 RFPs 34 through 38 are the second set of discovery requests at issue. Respectively, 17 RFPs 34 through 37 seek to obtain documents and communications regarding (1) 18 Defendants’ account opening targets, incentives, goals, and metrics; (2) employee 19 communications regarding account opening targets; (3) the number and type of new 20 accounts Defendants opened each day; and (4) due diligence of customers who sought to 21 open new accounts. (Doc. No. 29, Ex. 1, 9:21-24; 11:6-8; 12: 19-21; 14:4-7.) RFP 38 seeks 22 to obtain documents and communications regarding Defendants’ practice of “cross-selling 23 business banking services and merchant processing services.” (Id., 5:17-20.) 24 The Receiver contends these RFPs are necessary to establish Defendants’ knowledge 25 of and motives to further the Enterprises’ fraud. (Doc. No, 29, 5:14-16.) The Receiver 26 explains these RFPs target records that will substantiate Defendants’ efforts to cross-sell 27 services to the Enterprises in violation of Defendants’ own policies barring the solicitation 28 of “merchant processing customers engaged in illegal businesses.” (Id., 5:20-25.) 1 Defendants wholly disagree and object on relevance and proportionality grounds. 2 Defendants specify “documents related to generic sales incentive programs” are not 3 probative of Defendants’ intent to facilitate fraud to any extent, including, but not limited 4 to, the Enterprises’ schemes. (Doc. No. 28, 4:23-25.) To that end, Defendants caution the 5 RFPs are relevant only to uncovering employees’ motives to meet sales goals rather than 6 effectuate fraud. (Id., 5:17-22.) Finally, Defendants add the Receiver’s RFPs here amount 7 to a fishing expedition that is disproportionate to this case’s needs. (Id., 6: 6-8.) 8 As a threshold matter, the Court finds RFPs 34 through 38 are relevant. The common 9 thread binding the Receiver’s claims against Defendants is that Defendants knew about the 10 Enterprises’ fraud and, in the face of such knowledge, chose to open accounts for the 11 Enterprises in furtherance of their fraud. RFPs 34 through 38 call upon Defendants to 12 provide documents illuminating Defendants’ efforts to cross-sell services to the 13 Enterprises’ benefit. If any exists, evidence of Defendants’ efforts to cater to the 14 Enterprises would provide insight into Defendants’ motives to (1) cross-sell their services 15 in spite of the Enterprises’ misconduct or (2) more aggressively pursue cross sales because 16 of the potentially lucrative nature of the Enterprises’ misconduct. In either scenario, the 17 Receiver’s RFPs will yield documents bearing on Defendants’ knowledge of the 18 Enterprises’ business schemes as well as Defendants’ willingness or motive to participate 19 in such schemes, or entire lack thereof. In light of the claims the Receiver brings against 20 Defendants, and, for that matter, the affirmative defenses Defendant has asserted, the Court 21 can solely conclude that the discovery requests are relevant. 22 Further, the Receiver appropriately calls attention to District Judge Burns’ March 23 30, 2022 Order, which concluded “the Receiver’s allegations relating to account opening 24 targets and cross-selling of merchant processing services support his claims.” (Doc. No. 25 20, 8-9, 14.) Judge Burns specified “the Complaint allege[d] extraordinary business 26 transactions, including knowingly opening accounts with straw owners contrary to industry 27 practice… [and] the role that Wells Fargo played in that fraud as the bank that allegedly 28 opened the accounts and concealed their connections to Triangle and Apex is obvious.” 1 (Id., 10:20-11:1.) Through the looking glass of Judge Burns’ Order, the image comes into 2 full view for the Parties’ discovery purposes here. The RFPs seek insight into Defendants’ 3 knowledge of the Enterprises’ fraud and Defendants’ motives to not only open accounts 4 for the Enterprises but also cross-sell additional services to them. 5 Finally, the Court turns to Defendants’ objection on proportionality grounds. As the 6 party objecting to discovery, Defendants bear the burden of substantiating how the 7 Receiver’s instant RFPs exceed the needs of the case, which requires a showing of (1) the 8 importance of the issues at stake; (2) the amount-in-controversy; (3) the Parties’ relative 9 access to the information and documents sought; (4) the Parties’ resources; (5) the 10 importance of the discovery in resolving the issues; and (6) whether the burden or expense 11 of the Receiver’s proposed discovery outweighs the discovery’s benefit. Fed. R. Civ. Proc. 12 26(b)(1). Defendants fail to meet their burden here. They have not offered insight into any 13 of Rule 26(b)(1)’s enumerated considerations, including, but not limited to, an estimate as 14 to the hours of labor, costs, and fees reasonably required to meet the demands of the 15 Receiver’s document requests. Without such insight, the Court is left with no means to 16 sustain the objection in Defendants’ favor. As noted, explaining objections with factual 17 specificity, particularly when asserting a proportionality objection, is incumbent upon the 18 party contesting an RFP. Fed. R. Civ. Proc. 26(b)(1); Medimpact Healthcare Sys., Inc., 19 2021 WL 5605281, at *2. Defendants have not done so here. Accordingly, the Court 20 OVERRULES Defendants’ objections to RFPs 34 through 38 and ORDERS Defendants 21 to make their requisite document production no later than 30 days from the date of this 22 Order’s issuance. 23 c. Defendants’ Objections to RFP 45 24 RFP 45 is the next discovery request at issue. The RFP asks for all “documents and 25 communications concerning [Defendants’] employment and/or personnel files for each 26 Enterprise Banker,” inclusive of records concerning employees’ employment status, 27 including performance reviews and resignation and termination letters, and the reasons 28 underlying Defendants’ termination decisions from July 1, 2008 through the present. (Doc. 1 No. 29, Exh. 1, 17:1-7.) The Receiver explains this discovery request is relevant because 2 it will uncover evidence of Defendants’ knowledge of the Enterprises’ fraud and elucidate 3 the extent of such knowledge. (Doc. No. 21, 7:19-24.) Defendants object to RFP 45 on 4 three grounds, namely the request is (1) “extremely broad” as it would implicate hundreds 5 of employees who had immaterial interactions with the Enterprises; (2) irrelevant as to 6 documents not “specifically referenc[ing] compensation incentives or disciplinary action 7 for assisting these specific Enterprise Entities and Individuals;” and (3) invasive of 8 employees’ privacy rights. (Doc. No. 28, 7:7-8; 24-26; 8:6-7.) The Court SUSTAINS IN 9 PART AND OVERRULES IN PART Defendants’ first and second objections and 10 OVERRULES Defendants’ third objection. In doing so, the Court first addresses the RFP’s 11 relevance and then examines each objection in turn. 12 As a foundational matter, the Court finds RFP 45 seeks relevant information. As 13 discussed, Defendants’ employees’ knowledge of the Enterprises’ fraud during the course 14 of their employment with Defendants is directly pertinent to the Receiver’s claims. Further, 15 Defendants’ awareness of their employees’ assistance to the Enterprises for purposes of 16 facilitating fraudulent business transactions would be reflected in disciplinary proceedings, 17 up to and including termination, if any such proceedings took place. To that end, the records 18 the Receiver seeks are relevant not only as to his claims against Defendants but also to 19 Defendants’ affirmative defenses, which include good faith conduct, contributory 20 negligence, and comparative fault. (See generally Doc. No. 24.) Accordingly, the Court 21 finds the Receiver has sufficiently demonstrated RFP 45’s relevance to this litigation. 22 Notwithstanding the Court’s finding of relevance, the Court concludes Defendants’ 23 first two objections are founded, albeit to varying extents. Accordingly, the Court 24 SUSTAINS IN PART AND DENIES IN PART Defendants’ overbreadth and relevance 25 objections. As to Defendants’ first objection regarding overbreadth, the Court agrees RFP 26 45 is overbroad as to which particular employees may be implicated in this request. As 27 Defendants point out, the RFP conceivably encompasses employees who had one-time 28 interactions with the Enterprises implicating immaterial subject matter; the personnel files 1 for such individuals would do nothing to advance the Receiver’s claims or substantiate 2 Defendants’ affirmative defenses. Concurrently, however, the Receiver offers to limit the 3 scope of RFP 45 to the 25 employees Defendants identified as document custodians and 4 individuals who had the “most direct involvement with the Fraudulent Enterprises.” (Doc. 5 No. 29, 8:2-5.) The Court finds this proposed framework is consistent with both the 6 relevance and proportionality considerations at play. The Receiver’s willingness to limit 7 the scope of the request to 25 employees who Defendants themselves identify as having 8 the “most direct involvement” with the Enterprises strikes the right balance, as it aligns 9 with Defendants’ own determination regarding which specific employees had the most 10 direct involvement with the Enterprises. 11 As to Defendants’ second objection regarding relevance, the Court agrees RFP 45, 12 as written, seeks to obtain the entirety of all personnel files for the employees who worked 13 on the Enterprises’ accounts. In doing so, the Court finds the RFP is inclusive of documents 14 that would likely be irrelevant, such as copies of the employees’ initial job applications and 15 their medical records. Concurrently, and as explained, the bulk of the documents the 16 Receiver seeks through RFP 45 is likely to illuminate what the employees directly involved 17 with the Enterprises knew about the fraudulent schemes; Defendants’ awareness of their 18 employees’ involvement, if any; and Defendants’ responses to their employees’ 19 involvement, including, but not limited to, disciplinary action taken, if any. Accordingly, 20 the Court ORDERS Defendants to produce personnel files for the 25 employees as 21 discussed above, subject to the considerations outlined immediately below. Defendants 22 shall produce the documents responsive to RFP 45 no later than 30 days from the date 23 of this Order’s issuance. 24 Finally, while it appreciates Defendants’ privacy concerns over their employees’ 25 personal information as contained in their personnel files, the Court finds there is no basis 26 to sustain Defendants’ objection on such grounds. The Court’s July 25, 2022 Order 27 Granting the Parties’ Joint Motion for Protective Order serves to assuage these concerns, 28 particularly because the Parties’ mutually fashioned and agreed to the Court’s entry of their 1 proposed protective order. (Doc. No. 32.) Further, nothing stands in the way of Defendants 2 to (1) apply redactions to sensitive employee information where appropriate, such as 3 employees’ social security numbers and information regarding their family members, or 4 (2) entirely exclude from production certain documents that are plainly irrelevant to this 5 litigation, such as medical records not related to any physical or mental health conditions 6 that may have resulted from any employees’ dealings with the Enterprises. The 7 understanding that such limitations shall be imposed is reflected in the Receiver’s briefing 8 on this portion of the Parties’ discovery dispute. (Doc. No. 29, 8:11-13.) Accordingly, the 9 Court views this particular objection as one over a non-issue. As such, the Court 10 OVERRULES Defendants’ privacy objection. 11 d. Defendants’ Objections to RFPs 46 and 47 12 RFPs 46 and 47 are the fourth set of discovery requests at issue. RFP 46 seeks 13 documents and communications involving Defendants’ Board and senior management and 14 the Enterprises from July 1, 2008 through the present. (Id., Exh. 1, 18: 25-28.) RFP 47 15 seeks documents and communications concerning the Defendants’ Board and committee 16 meetings regarding the Enterprises. (Id., 20:19-25.) The Receiver explains the RFPs are, 17 again, necessary to show Defendants’ knowledge of the Enterprises’ fraudulent business 18 practices and motives to sustain such practices in light of Defendants’ knowledge. 19 Defendants object on grounds that the RFPs are premature and disproportionate to the 20 needs of the case. As to their prematurity objection, Defendants explain the information 21 from the documents requested may be readily obtained through taking discovery on lower- 22 ranking employees. Defendants add “there has been no showing that any high-level 23 executives or senior management possessed ‘unique or personal knowledge’ of the 24 schemes.” (Doc. No. 29, 8:19-28.) As to their proportionality objection, Defendants argue 25 the RFPs supply “no nexus between high-level executives with the conduct or events at 26 issue in this case” and the bankers who the Receiver purports opened accounts for the 27 Enterprises. (Doc. No. 28, 8:21-25.) 28 / / / 1 As a threshold matter, the Court finds RFPs 46 and 47 are relevant to this litigation. 2 The Court is not persuaded by Defendants’ contention that executive-level employees are 3 immune from knowing Defendants furthered the Enterprises’ fraudulent business 4 objectives, simply because Defendants’ C-Suite did not personally open the Enterprises’ 5 accounts as Defendants’ bankers did. If Defendants’ suggestion bears out, that is for the 6 Receiver to uncover throughout discovery, rather than an assumption the Receiver must 7 accept as true from the outset of discovery. In Re Nat’l W. Life Ins. Deferred Annuities 8 Litig., 2011 WL 1304587 at *3 (S.D. Cal. Apr. 6, 2011) (rejecting party’s bald assertion 9 that management-level witnesses lacked knowledge regarding opposing party’s discovery 10 requests and commenting “if these gentlemen in fact do not have the requisite knowledge, 11 that is something plaintiffs are entitled to explore and discover on their own.”) (“In Re 12 Annuities Litigation”). 13 Notwithstanding the above, the Court SUSTAINS Defendants’ objection to RFP 46 14 and OVERRULES Defendants’ objection to RFP 47. As to RFP 46, courts generally 15 require a party to take discovery on other lower-level employees before permitting 16 discovery on apex officials to avoid duplicative discovery. Symantec Corp. v. Acronis, Inc., 17 2013 WL 12184286, at *1 (N.D. Cal. Oct. 10, 2013). Here, the Receiver has repeatedly 18 asserted factual allegations of Defendants’ knowledge of and participation in furthering the 19 Enterprises’ fraud. However, the Receiver has not yet pointed to any discovery taken thus 20 far from a lower-level employee that attributes such knowledge or participation onto 21 Defendants’ senior management. This showing must be made first before opening the door 22 to the broad range of documents and communications the RFP calls for. Of course, the 23 present circumstance does not mean that the Receiver is forever precluded from taking 24 discovery from Defendants’ Board or executive-level employees. That additional 25 discovery may prove warranted later in the lifespan of the Parties’ discovery efforts here, 26 subject to a fact-specific showing on the Receiver’s part. 27 / / / 28 / / / 1 RFP 47 leads to a different outcome because of the more tailored nature of the 2 documents it seeks. RFP 47 specifically endeavors to obtain documents and 3 communications concerning the Defendants’ Board and related committee meetings 4 regarding the Enterprises. (Doc. No. 29, 20:19-25.) Board and related committee meetings 5 are inherently distinct from meetings lower-ranking employees attend in any corporate 6 environment. Thus, the Court finds Defendants’ executive-level employees would possess 7 unique knowledge about the Enterprises that would not otherwise materialize from 8 discovery taken from lower-level employees who do not, by definition, participate in Board 9 and related committee meetings. In other words, Defendants need not engage in the 10 duplicative discovery they fear to meet RFP 47’s demands. Nothing prevents Defendants 11 from identifying documents that are unique to the Board and Board’s committees’ own 12 understandings of the Enterprises’ business dealings with Defendants because such 13 documents would not overlap with any documents or communications involving lower- 14 level employees. Accordingly, if they at all exist, documents responsive to RFP 47 shall be 15 produced no later than 30 days from the date of this Order’s issuance. 16 e. Defendants’ Objections to RFPs 54 and 55 17 RFPs 54 and 55 are the last set of discovery requests at issue. RFP 54 seeks to obtain 18 Defendants’ document retention policies or procedures from July 1, 2008 through the 19 present. (Doc. No. 29, Exh. 1, 23:1-7.) RFP 55 seeks to obtain documents and 20 communications showing all means Defendants’ employees “used to communicate relating 21 to their work concerning the subject matter of this Action.” (Id., 24:22-27.) The Receiver 22 posits these RFPs are relevant because they will help identify sources of discoverable 23 information germane to the Receiver’s claims. Defendants counter the Receiver is not 24 entitled to take “discovery on discovery” and cite to Jensen in support of their position. 25 As before, the Court begins with its relevance inquiry. In doing so, the Court finds 26 both RFPs 54 and 55 are relevant to this litigation. The Receiver brings claims against 27 Defendants for, most notably, aiding and abetting fraud, aiding and abetting breach of 28 fiduciary duty, and aiding and abetting conversion. (See generally Doc. Nos. 1; 20.) The 1 relevance of establishing sources of information implicating the Receiver’s claims cannot 2 be overstated. Like any litigant who seeks to vindicate his claims, the Receiver needs to 3 know where relevant documents may be found to define the boundaries of his search to 4 prove his claims here. Defendants do not plainly address the matter. Instead, they shift their 5 entire focus on Jensen in the hopes of salvation from these discovery requests. 6 The Court has studied Jensen and finds it does not help Defendants’ cause. The 7 Jensen discovery requests sought to obtain information “regarding [the defendant’s] efforts 8 to preserve relevant and discoverable information in this matter” as well as the defendant’s 9 “efforts to search for documents and information responsive to [the] plaintiff’s discovery 10 requests.” Jensen v. BMW of N. Am., LLC, 328 F.R.D. 557, 566 (S.D. Cal. Jan. 15, 2019). 11 Here, RFP 54 calls for Defendants’ document retention policies. In turn, RFP 55 asks 12 Defendants to identify sources of relevant information. Neither request seeks to pry into 13 Defendants’ document preservation or production efforts throughout the course of this 14 litigation, which is what Jensen’s propounding party sought and what the Jensen court 15 described as “discovery on discovery.” (Id.) Thus, the Jensen discovery requests are 16 markedly distinguishable from the Receiver’s requests, and the Court finds no reason to 17 sustain Defendants’ objections to RFPs 54 and 55 on such basis. 18 To counter the Receiver’s RFPs 54 and 55, Defendants asserted exclusively 19 boilerplate objections, save their Jensen objection, and their briefing only addresses the 20 Jensen objection. As discussed, the Court is unmoved by Defendants’ “discovery on 21 discovery” argument. Moreover, Defendants’ other objections are not well taken. The 22 Court strongly disfavors and has cautioned against its Rule IV and Appendixes A and B of 23 the Court’s Civil Chambers Rules and finds Defendants have made no effort, even during 24 the briefing of this discovery dispute, to substantiate their blanket objections. The Court 25 will not reward Defendants’ failure to meet its obligations here. Accordingly, the Court 26 OVERRULES Defendants’ objections to the Receiver’s RFPs 54 and 55. 27 / / / 28 / / / 1 IV. CONCLUSION 2 Given the forgoing, the Court makes the following determinations: 3 e First, the Court SUSTAINS IN PART AND DENIES IN PART Defendants’ 4 objections to RFPs 23 through 26. No later than 30 days from the date of this 5 Order’s issuance, Defendants shall produce the documents and a privilege log in 6 response to these RFPs. 7 e Second, the Court OVERRULES Defendants’ objections to RFPs 34 through 38. No 8 later than 30 days from the date of this Order’s issuance, Defendants shall 9 produce the documents responsive to this set of RFPs. 10 || Third, the Court SUSTAINS IN PART AND DENIES IN PART Defendants’ 11 overbreadth and relevance objections to the Receiver’s RFP 45, and OVERRULES 12 Defendants’ privacy objection. No later than 30 days from the date of this 13 Order’s issuance, Defendants shall produce the 25 “directly involved” employees’ 14 personnel files subject to the protections discussed above. 15 e Fourth, the Court SUSTAINS Defendants’ objection to RFP 46 and OVERRULES 16 Defendants’ objection to RFP 47. No later than 30 days from the date of this 17 Order’s issuance, Defendants shall produce documents responsive to RFP 47. 18 ||. Fifth, and finally, the Court OVERRULES RFPs 54 and 55. No later than 30 days 19 from the date of this Order’s issuance, Defendants shall produce documents 20 responsive to both RFPs. 21 Consistent with the Court’s guidance and instructions above, Defendants shall make 22 || their document and privilege log productions to the Receiver no later than 30 days of the 23 || date of this Order’s issuance. 24 IT IS SO ORDERED. 29 |! Dated: July 29, 2022 | 3 KS 26 7 Hon. William V. Gallo 3g United States Magistrate Judge