1 WO 2 3 4 5 6 IN THE UNITED STATES DISTRICT COURT 7 FOR THE DISTRICT OF ARIZONA
9 United Association National Pension Fund, et No. CV-22-02126-PHX-MTL al., 10 ORDER Plaintiffs, 11 v. 12 Carvana Company, et al., 13 Defendants. 14 15 Pending before the Court is Plaintiffs’ “Motion to Compel Compliance” (doc. 214). 16 Plaintiffs’ Motion seeks to compel Defendants compliance with the Court’s August 21, 17 2025, Order.1 (Doc. 214 at 2.) In the Court’s August 21, 2025, Order, the Court permitted 18 a limited test of Plaintiffs’ proposed eDiscovery tool—the Forensic Email Collector 19 (“FEC”)—on emails from two Electronically Stored Information (“ESI”) custodians. (Doc. 20 196 at 4.) This test would determine if the production of contemporaneous hyperlinked 21 documents using FEC was possible without undue burden or expense for Defendants. (Id.) 22 The Court noted that, were the test run “successful in producing point-in-time hyperlinked 23 documents of evidentiary value without undue burden or expense, the parties may raise the 24 issue of conducting additional discovery into point-in-time hyperlinked documents by 25 filing a motion with the Court.” (Id.) 26 Upon review of the Parties’ written and oral arguments, the Court holds as follows. 27 First, Plaintiffs shall select 250 responsive emails which Defendants shall, using FEC,
28 1 Discover matters in this case have been referred to this Court by the Honorable United States District Judge Michael T. Liburdi. See (doc. 125.) 1 produce the most contemporaneous version of hyperlinked documents. Plaintiffs’ choice 2 of responsive emails is not limited to the 2 previously select ESI custodians. Rather, 3 Plaintiffs may select responsive emails from any of the 25 ESI custodians. Defendants, 4 after receiving Plaintiffs’ selection, shall have 10 days to provide the most 5 contemporaneous version of non-privileged hyperlinked documents attached to the 250 6 emails. 7 Second, Defendants shall provide all responsive and non-privileged documents in 8 the ESI custodians’ Google Vault collection to Plaintiffs. Thereafter, Plaintiffs may select 9 200 documents that Defendants shall use in searching for a potential parent email. If a non- 10 privileged parent email is found, Defendants must produce said email. 11 I. Background. 12 On August 3, 2022, Plaintiffs initiated this action by filing their Complaint alleging 13 violations of the Securities Exchange Act of 1934. (Doc. 1 at 2, 33.) On March 12, 2025, 14 the District Court issued an Order governing Electronic Discovery in this action. (Doc. 15 137.) In pertinent part, the Order stated that: 16 [t]he parties agree that if any part of a communication or its attachments is responsive, the entire communication and attachments will be 17 produced, except any attachments that must be withheld or redacted on the 18 basis of privilege. The parties will meet and confer about whether there is an appropriate basis for withholding a family document for any reason other 19 than attorney-client or work product privilege. The attachments will be 20 produced sequentially after the parent communication. The parties understand that hyperlinked documents will be collected 21 and produced in this case. The parties shall use their reasonable best efforts to collect documents that are links in documents and communications, 22 including, but not limited to, Google G Suite, Microsoft 365, etc. Where the 23 automatic collection of the hyperlinked document is technologically feasible, reasonable, and not unduly burdensome, the hyperlinked document will be 24 collected. The parties will work diligently and collaboratively to come to a 25 common understanding as to the scope of the collection, review, and production and any other issue that arises. In addition, the parties will work 26 diligently and collaboratively to come to a common understanding as to what 27 is reasonable, technically feasible, and not unduly burdensome (e.g., showing the hyperlinked relationship between documents and producing point-in- 28 time version of hyperlinked documents). To the extent the parties are not able 1 to come to an agreement, any disputes will be promptly raised with the Court. 2 (Id. at 8.) 3 On July 24, 2025, the Parties filed a Joint Discovery Motion (doc. 177) regarding 4 the production of contemporaneous hyperlinked documents alongside their parent emails. 5 (Doc. 177 at 2–5.) At issue was the “potential feasibility and utility of implementing the 6 proposed FEC tool to collect versions of hyperlinked documents contemporaneous to the 7 emails sent.” (Doc. 196 at 3.) Plaintiffs insisted on receiving contemporaneous versions of 8 hyperlinked documents so that they may establish “who knew what and when[.]” (Doc. 9 177 at 2.) Defendants responded that contemporaneous versions of hyperlinked documents 10 could not be reliably collected due to Defendants use of Google Workplace’s suite of web- 11 based applications, including Google Vault. (Id. at 3); (doc. 177-6 at 5.) 12 On August 21, 2025, this Court issued an Order addressing the Parties Joint 13 Discovery Motion. (Doc. 196.) The Court ordered that: 14 Plaintiff[s may] select up to two custodians comprising a small subset of the overall scope of emails and corresponding hyperlinked documents at issue in 15 the case. Defendants must produce responsive documents—i.e., the versions 16 of any documents as closely contemporaneous to, but preceding, the email communication as is feasible—on or before December 1, 2025, absent 17 further order of the Court. The Court assumes FEC will be used, but the 18 parties may agree to other methods. 19 (Id. at 4.) The Court further noted that “If this limited test is successful in producing point- 20 in-time hyperlinked documents of evidentiary value without undue burden or expense, the 21 parties may raise the issue of conducting additional discovery into point-in-time 22 hyperlinked documents by filing a motion with the Court.” (Id.) 23 Upon receiving Plaintiffs’ Motion to Compel Compliance (doc. 214) on November 24 24, 2025, this Court scheduled a telephonic discovery hearing for December 12, 2025. 25 (Doc. 216.) On December 12, 2025, the the Court conducted the telephonic discovery 26 hearing. (Doc. 226.) On December 17, 2025, the Court provided the Parties with a 27 Tentative Ruling. In the Tentative Ruling, the Court notified the Parties of its willingness 28 to rehear arguments on Plaintiffs’ Motion to Compel Compliance during the Court’s 1 January 8, 2026, telephonic hearing. 2 II. The Parties’ Arguments. 3 On November 24, 2025, Plaintiffs filed their “Motion to Compel Compliance” (doc. 4 214), containing both Parties’ arguments. Thereafter, the Parties conducted oral arguments 5 before the Court on December 12, 2025, and January 8, 2026.2 The Parties’ arguments are 6 summarized below. 7 A. Plaintiffs’ Position. 8 Plaintiffs assert that Defendants have failed to comply with the Court’s August 21, 9 2025, Order. (Id. at 2.) In their written submission, Plaintiffs allege that Defendants are 10 severing hyperlinked documents from their parent emails, and are refusing to provide both 11 unless the hyperlinked documents and parent emails are independently responsive. (Id.) 12 Doing so, Plaintiffs contend, expressly violates this Court’s and the District Court’s prior 13 Orders, which stated that “‘if any part of a communication or its attachments is responsive, 14 the entire communication and attachments will be produced’ except for attachments 15 withheld or redacted for privilege.” (Id.) (quoting doc. 196 at 2); (doc. 137 at 8.) 16 During the December 12, 2025, discovery hearing, Plaintiffs clarified their 17 arguments, asserting the following. First, that this dispute is about what version of 18 documents will be produced.
Free access — add to your briefcase to read the full text and ask questions with AI
1 WO 2 3 4 5 6 IN THE UNITED STATES DISTRICT COURT 7 FOR THE DISTRICT OF ARIZONA
9 United Association National Pension Fund, et No. CV-22-02126-PHX-MTL al., 10 ORDER Plaintiffs, 11 v. 12 Carvana Company, et al., 13 Defendants. 14 15 Pending before the Court is Plaintiffs’ “Motion to Compel Compliance” (doc. 214). 16 Plaintiffs’ Motion seeks to compel Defendants compliance with the Court’s August 21, 17 2025, Order.1 (Doc. 214 at 2.) In the Court’s August 21, 2025, Order, the Court permitted 18 a limited test of Plaintiffs’ proposed eDiscovery tool—the Forensic Email Collector 19 (“FEC”)—on emails from two Electronically Stored Information (“ESI”) custodians. (Doc. 20 196 at 4.) This test would determine if the production of contemporaneous hyperlinked 21 documents using FEC was possible without undue burden or expense for Defendants. (Id.) 22 The Court noted that, were the test run “successful in producing point-in-time hyperlinked 23 documents of evidentiary value without undue burden or expense, the parties may raise the 24 issue of conducting additional discovery into point-in-time hyperlinked documents by 25 filing a motion with the Court.” (Id.) 26 Upon review of the Parties’ written and oral arguments, the Court holds as follows. 27 First, Plaintiffs shall select 250 responsive emails which Defendants shall, using FEC,
28 1 Discover matters in this case have been referred to this Court by the Honorable United States District Judge Michael T. Liburdi. See (doc. 125.) 1 produce the most contemporaneous version of hyperlinked documents. Plaintiffs’ choice 2 of responsive emails is not limited to the 2 previously select ESI custodians. Rather, 3 Plaintiffs may select responsive emails from any of the 25 ESI custodians. Defendants, 4 after receiving Plaintiffs’ selection, shall have 10 days to provide the most 5 contemporaneous version of non-privileged hyperlinked documents attached to the 250 6 emails. 7 Second, Defendants shall provide all responsive and non-privileged documents in 8 the ESI custodians’ Google Vault collection to Plaintiffs. Thereafter, Plaintiffs may select 9 200 documents that Defendants shall use in searching for a potential parent email. If a non- 10 privileged parent email is found, Defendants must produce said email. 11 I. Background. 12 On August 3, 2022, Plaintiffs initiated this action by filing their Complaint alleging 13 violations of the Securities Exchange Act of 1934. (Doc. 1 at 2, 33.) On March 12, 2025, 14 the District Court issued an Order governing Electronic Discovery in this action. (Doc. 15 137.) In pertinent part, the Order stated that: 16 [t]he parties agree that if any part of a communication or its attachments is responsive, the entire communication and attachments will be 17 produced, except any attachments that must be withheld or redacted on the 18 basis of privilege. The parties will meet and confer about whether there is an appropriate basis for withholding a family document for any reason other 19 than attorney-client or work product privilege. The attachments will be 20 produced sequentially after the parent communication. The parties understand that hyperlinked documents will be collected 21 and produced in this case. The parties shall use their reasonable best efforts to collect documents that are links in documents and communications, 22 including, but not limited to, Google G Suite, Microsoft 365, etc. Where the 23 automatic collection of the hyperlinked document is technologically feasible, reasonable, and not unduly burdensome, the hyperlinked document will be 24 collected. The parties will work diligently and collaboratively to come to a 25 common understanding as to the scope of the collection, review, and production and any other issue that arises. In addition, the parties will work 26 diligently and collaboratively to come to a common understanding as to what 27 is reasonable, technically feasible, and not unduly burdensome (e.g., showing the hyperlinked relationship between documents and producing point-in- 28 time version of hyperlinked documents). To the extent the parties are not able 1 to come to an agreement, any disputes will be promptly raised with the Court. 2 (Id. at 8.) 3 On July 24, 2025, the Parties filed a Joint Discovery Motion (doc. 177) regarding 4 the production of contemporaneous hyperlinked documents alongside their parent emails. 5 (Doc. 177 at 2–5.) At issue was the “potential feasibility and utility of implementing the 6 proposed FEC tool to collect versions of hyperlinked documents contemporaneous to the 7 emails sent.” (Doc. 196 at 3.) Plaintiffs insisted on receiving contemporaneous versions of 8 hyperlinked documents so that they may establish “who knew what and when[.]” (Doc. 9 177 at 2.) Defendants responded that contemporaneous versions of hyperlinked documents 10 could not be reliably collected due to Defendants use of Google Workplace’s suite of web- 11 based applications, including Google Vault. (Id. at 3); (doc. 177-6 at 5.) 12 On August 21, 2025, this Court issued an Order addressing the Parties Joint 13 Discovery Motion. (Doc. 196.) The Court ordered that: 14 Plaintiff[s may] select up to two custodians comprising a small subset of the overall scope of emails and corresponding hyperlinked documents at issue in 15 the case. Defendants must produce responsive documents—i.e., the versions 16 of any documents as closely contemporaneous to, but preceding, the email communication as is feasible—on or before December 1, 2025, absent 17 further order of the Court. The Court assumes FEC will be used, but the 18 parties may agree to other methods. 19 (Id. at 4.) The Court further noted that “If this limited test is successful in producing point- 20 in-time hyperlinked documents of evidentiary value without undue burden or expense, the 21 parties may raise the issue of conducting additional discovery into point-in-time 22 hyperlinked documents by filing a motion with the Court.” (Id.) 23 Upon receiving Plaintiffs’ Motion to Compel Compliance (doc. 214) on November 24 24, 2025, this Court scheduled a telephonic discovery hearing for December 12, 2025. 25 (Doc. 216.) On December 12, 2025, the the Court conducted the telephonic discovery 26 hearing. (Doc. 226.) On December 17, 2025, the Court provided the Parties with a 27 Tentative Ruling. In the Tentative Ruling, the Court notified the Parties of its willingness 28 to rehear arguments on Plaintiffs’ Motion to Compel Compliance during the Court’s 1 January 8, 2026, telephonic hearing. 2 II. The Parties’ Arguments. 3 On November 24, 2025, Plaintiffs filed their “Motion to Compel Compliance” (doc. 4 214), containing both Parties’ arguments. Thereafter, the Parties conducted oral arguments 5 before the Court on December 12, 2025, and January 8, 2026.2 The Parties’ arguments are 6 summarized below. 7 A. Plaintiffs’ Position. 8 Plaintiffs assert that Defendants have failed to comply with the Court’s August 21, 9 2025, Order. (Id. at 2.) In their written submission, Plaintiffs allege that Defendants are 10 severing hyperlinked documents from their parent emails, and are refusing to provide both 11 unless the hyperlinked documents and parent emails are independently responsive. (Id.) 12 Doing so, Plaintiffs contend, expressly violates this Court’s and the District Court’s prior 13 Orders, which stated that “‘if any part of a communication or its attachments is responsive, 14 the entire communication and attachments will be produced’ except for attachments 15 withheld or redacted for privilege.” (Id.) (quoting doc. 196 at 2); (doc. 137 at 8.) 16 During the December 12, 2025, discovery hearing, Plaintiffs clarified their 17 arguments, asserting the following. First, that this dispute is about what version of 18 documents will be produced. Second, under the colors of the best evidence rule, that where 19 a contemporaneous version is available, they are entitled to it; But if the contemporaneous 20 version is unavailable, they are entitled to the non-contemporaneous version. Third, 21 Plaintiffs’ assert—when applying the search terms through Google Vault3—if either a 22 hyperlink document or email is responsive, they must be produced. Specifically on this 23 third point, Plaintiffs note that the ability to link an otherwise authorless document to an 24 2 The Court acknowledges but does not summarize the Parties’ Stipulation received 25 prior to the January 8, 2026, hearing. 3 “Google Vault is a platform that, among other things, preserves [emails] and other 26 types of accounts and allows for Google Vault administrators to search through users’ accounts[.] Google Vault preserves emails through litigation holds[.] Once a litigation hold 27 is in place on a user’s account, no one can delete emails from the preserved hold in Google Vault.” Kenno v. Colo. Governor’s Off. of Info. Tech., No. 19-CV-00165-MEH, 2021 WL 28 2682619, at *1 (D. Colo. June 30, 2021), aff’d sub nom. Kenno v. Colo. Governor’s Off. of Info. Tech., No. 21-1353, 2023 WL 2967692 (10th Cir. Apr. 17, 2023). 1 email would allow Plaintiffs to understand “who knew what and when.” 2 During the January 8, 2026, discovery hearing, Plaintiffs re-asserted their desire to 3 use FEC in this matter. However, in light of Defendants’ findings on the burden of using 4 FEC,4 Plaintiffs revised their request. Specifically, Plaintiffs requested that they may 5 choose 1,000 responsive emails from all 25 ESI custodians that Defendants shall run 6 through FEC to find the most contemporaneous version of hyperlinked attachments. 7 Additionally, Plaintiffs seek the opportunity to request further production through FEC 8 were this new search to prove fruitful. 9 B. Defendants’ Position. 10 Defendants respond that Plaintiffs’ allegations of non-compliance are unfounded, 11 because under the Court’s August 21, 2025, Order, Defendants were required to establish 12 a process for determining which versions of hyperlinked documents are required to be 13 produced. (Doc. 214 at 3–4.) Specifically, Defendants assert they are only required to 14 provide contemporaneous versions of hyperlinked documents if and when the Court 15 determines that they are proportional to the needs of the case.5 (Id. at 4.) 16 During the December 12, 2025, discovery hearing, Defendants clarified their 17 arguments, asserting the following. First, Defendants allege that the use of FEC has not 18 been productive. Namely, FEC was only able to collect .4% of top-level executive 19 hyperlinked documents modified within 24 hours in Google Vault. In terms of cost, 20 Defendants noted that the use of FEC was “about 105 times more expensive than Carvana’s 21 average per document cost in this litigation.” Further, Defendants asserted that FEC was 22 unable to collect 93% of parent emails containing hyperlinks. 23 Second, when the search terms are applied to documents in Google Vault, 24 Defendant cannot readily discern if it was used as a hyperlink attachment to an email— 25 and, by virtue, what email it is directly attached to. Third, Defendants asserted that they 26 4 Infra section II.B. 27 5 On this point, Defendants assert that “Plaintiffs misstate how Carvana is reviewing and producing non-contemporaneous hyperlinked documents, and are incorrect that 28 Carvana is not producing responsive hyperlinked documents if an email is non- responsive.” (Doc. 214 at 4 n.2.) 1 are not obligated to provide both the contemporaneous version of hyperlink documents and 2 their non-contemporaneous counterparts. 3 During the January 8, 2026, discovery hearing, Defendants re-argued that FEC was 4 grossly inefficient in this action. Specifically, Defendants argued that of 112,889 total 5 emails, FEC was only able to capture 7,592 responsive emails with hyperlinks. Of those 6 7,592 emails collected, “many [hyperlinked documents] still had modifications after” the 7 date the parent email was sent. In terms of burden, Defendants spent 1,170 hours and over 8 $200,000 dollars using FEC for the 2 ESI custodians. This translated to a $425 per 9 document price tag for using FEC, which was “105 times more expensive” than using 10 traditional ESI discovery techniques. 11 In light of these findings, Defendants requested that Plaintiffs be permitted to select 12 200 emails which Defendants will use FEC on. Defendants noted that, were the Court to 13 require the search of 250 responsive emails with FEC, such search could be completed 14 within 7-to-10 days. 15 III. Legal Standards. 16 A district court has broad discretion to permit or deny discovery. Hallett v. Morgan, 17 296 F.3d 732, 751 (9th Cir. 2002). Generally, discoverable information is “any 18 nonprivileged matter that is relevant to any party’s claim[,] . . . proportional to the needs 19 of the case[,]” and is not unduly burdensome. Fed. R. Civ. P. 26(b)(1) (emphasis added). 20 Courts will limit discovery where: “(i) the discovery sought is unreasonably cumulative or 21 duplicative, or can be obtained from some other source that is more convenient, less 22 burdensome, or less expensive; (ii) the party seeking discovery has had ample opportunity 23 to obtain the information by discovery in the action; or (iii) the proposed discovery is 24 outside the scope permitted by Rule 26(b)(1).” Fed. R. Civ. P. 26(b)(2)(C)(i)–(iii). A party 25 may request production of evidence that is “within the scope of Rule 26(b)[.]” Fed. R. Civ. 26 P. 34(a). 27 In the instant action, the Parties have been unable to come to an agreement on how 28 ESI should be handled. “The Court has broad authority and discretion to assist the Parties 1 in resolving ESI disputes.” In re Soc. Media Adolescent Addiction/Personal Inj. Prods. 2 Liab. Litig., No. 22-md-03047-YGR (PHK), 2024 WL 1786293, at *2 (N.D. Cal. Feb. 20, 3 2024) (citing Phillips ex rel. Ests. of Byrd v. Gen. Motors Corp., 307 F.3d 1206, 1211–12 4 (9th Cir. 2002)). In addressing such ESI discovery disputes, the Court is guided by Rule 5 34’s requirement that the producing party provide ESI documents in “a reasonably usable 6 form or forms.” Fed. R. Civ. P. 34(a)(1)(A), (b)(2)(E)(ii). 7 IV. Discussion. 8 In interpreting the Parties’ written and oral arguments, the Court finds the following 9 two issues in dispute: (a) to what extent shall Defendants be obligated to use FEC on 10 responsive emails from all 25 ESI custodians; and (b) whether Defendants are obligated to 11 produce non-privileged responsive documents from Google Vault. 12 The use of hyperlinked documents in emails—while not completely novel— 13 presents challenges that are not incurred when parties use traditional attachments. See In 14 re Uber Techs., Inc., Passenger Sexual Assault Litig., No. 23-md-03084-CRB (LJC), 2024 15 WL 1772832, at *2 (N.D. Cal. Apr. 23, 2024) (“In sum, the briefing and evidence, as well 16 as related case law, have made clear that cloud computing and document retention through 17 Google Drive and Google Vault introduce a host of challenges to producing hyperlinked 18 documents from Google Drive and other sources.”). Although both traditional attachments 19 and hyperlinked documents contained within an email may serve similar purposes, courts 20 are loathe to treat them interchangeably. See Nichols v. Noom Inc., No. 20-CV-3677 (LGS) 21 (KHP), 2021 WL 948646, at *4 (S.D.N.Y. Mar. 11, 2021) (“[T]he Court does not agree 22 that a hyperlinked document is an attachment.”), objections overruled, No. 20 CIV. 3677 23 (LGS), 2021 WL 12307293 (S.D.N.Y. Apr. 30, 2021). 24 While traditional attachments to emails may be fixed in time, mitigating issues of 25 contemporality, these older forms of communication are being phased out for appended 26 hyperlinks that can facilitate quicker communication and collaboration. In considering 27 innovations such as hyperlinked documents, the Court must ensure that it does not 28 “embarrass the future[,]” see Carpenter v. United States, 585 U.S. 296 (2018) (citation 1 omitted), nor inhibit Plaintiffs’ right to discovery of ESI. With these preliminary 2 considerations in mind, the Court will address the three issues in dispute. 3 A. Expanded Use of FEC to Obtain the Most Contemporaneous Version of 4 Hyperlinked Documents from All ESI Custodians. 5 The first issue involves whether the Court will require additional use of FEC in the 6 Parties attempts to produce the most contemporaneous version of hyperlinked documents 7 attached in responsive parent emails from all 25 ESI custodians. In addressing this issue, 8 the Court finds the following principles to be beneficial. First, Rule 34 requires that the 9 producing party must produce ESI in a form that is “in a reasonably usable form,” qualified 10 by the consideration that “[a] party need not produce the same electronically stored 11 information in more than one form.” Fed. R. Civ. P. 34(b)(2)(E)(ii)–(iii). Second, “ESI 12 should not be produced in a format that makes it unreasonably difficult or burdensome for 13 the requesting party to use the documents efficiently in the litigation.” Nichols, 2021 WL 14 948646, at *3 (citation omitted). Third, with ESI, it is appropriate to limit collection and 15 review to non-duplicative, relevant information.” Id. 16 With these principles in mind, the Court finds the best way to proceed on this issue 17 is to strike a fine balance between burden and benefit. Namely, Plaintiffs may select 250 18 responsive emails6 that Defendants will be required to run an FEC search upon to find the 19 most contemporaneous version7 of hyperlinked documents contained in the parent emails. 20 This search is not limited to the two previously selected ESI custodians. Rather, Plaintiffs 21 may select any 250 responsive emails from any of the 25 identified ESI custodians.8
22 6 A required search of 250 responsive emails appears congruent with other courts’ orders. See In re Uber, 2024 WL 1772832, at *4 (requiring the production of 23 contemporaneous versions of 200 hyperlinked documents); See also Shenwick v. Twitter, Inc., No. 16-cv-05314-JST (SK), 2018 WL 5735176, at *1 (N.D. Cal. Sept. 17, 2018) 24 (requiring defendants to produce 200 hyperlinked documents found embedded in parent emails). 25 7 The Court defines the “most contemporaneous version” as the version of any document that is as close to the version of the document as it existed: (a) when its 26 responsive parent email was sent; or, for documents without parent emails, (b) between January 1, 2020, to February 28, 2023, for Carvana Defendants, and July 1, 2021, to 27 October 31, 2022 for UW Defendants. See (doc. 196 at 5–6). 8 The Court is mindful of the duplication issue that this Order will create. However, 28 because of the limited number of emails that will undergo FEC—and, by virtue, the limited costs of such—the Court does not find that duplication should prevent disclosure here. 1 This Order does not limit nor extinguish Defendants obligation to provide any and 2 all responsive parent emails and their hyperlinked attachments to Plaintiffs. Because the 3 most contemporaneous versions of non-privileged hyperlinked documents attached to 4 responsive parent emails is broadly relevant9 and proportional for Plaintiffs’ litigation 5 needs, they must be produced. Accordingly, Defendants shall provide the most 6 contemporaneous version of all hyperlinked attachment from responsive parent emails 7 using traditional ESI discovery techniques.10 8 The Court is mindful that hyperlinked documents are different than static 9 attachments. Because, by their nature, hyperlinked documents do not remain static, finding 10 the version of the document as it existed on a specific date and time is laborious. 11 However, the difficulty surrounding hyperlinked documents does not justify their 12 complete withholding by Defendants. Plaintiffs have a broad right to discovery under the 13 federal rules. See Fed. R. Civ. P. 26(b)(1) (emphasis added). While hyperlinked documents 14 present challenges that the drafters of the Federal Rules of Civil Procedure may never had 15 considered, novelty should not trump discovery. 16 B. Responsive Documents in Defendants’ Google Vault. 17 The next issue involves the treatment of responsive documents in the ESI 18 custodians’ Google Vault collections. As the Court understands Plaintiffs’ argument, 19 Plaintiffs requests the production of all non-privileged responsive documents within the 20 ESI custodians’ Google Vault collections, which will then be used to search through all 25 21 9 The Court does not find relevancy to be a major issue with hyperlinked documents 22 attached to responsive emails. To be discoverable, information must be “relevant to a party’s claim or defense.” Fed. R. Civ. P. 26(b)(1). Evidence need not be admissible to be 23 relevant. See id. The potential information Plaintiffs may receive from contemporaneous documents—such as who knew what and when—is eminently relevant to Plaintiffs’ 24 claims. Consequently, it will be up to the Parties to determine whether each specific hyperlinked document is or is not relevant to the needs of the case. See UAB “Planner5D” 25 v. Meta Platforms, Inc., 746 F. Supp. 3d 806, 808 (N.D. Cal. 2024) (“Courts rarely get involved in assessing specific documents for relevance but rather make general orders 26 about categories of documents that a party must produce. Courts in general rely upon parties to assess relevance, and the system of discovery is based on trust that a party 27 produces documents after a review and assessment for relevance and responsiveness.”). 10 The Court defines “traditional ESI discovery techniques” as a Google Vault search 28 used without FEC or a script. In other words, Defendants are not obligated to make and use a script in their search, nor are they obligated to use FEC beyond the 250 documents. 1 ESI custodians’ emails in the hope of finding a parent email. In effect, Plaintiffs request 2 that the Court issue an order requiring Defendants to run a reverse search of what is 3 envisioned in Section IV.A. 4 The Court finds the general production of the most contemporaneous version11 of 5 responsive documents from the ESI custodians’ Google Vault collections—so long as they 6 are not privileged or irrelevant—to be proportional to the Plaintiffs’ needs. Such a request 7 also comports with Section V.C of the District Court’s ESI Order. See (doc. 137 at 7.) 8 Further, Defendants already appear to have been searching these Google Vault collections 9 and producing responsive non-privileged documents.12 10 But, regarding the reverse search, Plaintiffs have not provided any evidence on how 11 such a search could be done. Additionally, Plaintiffs have not presented any arguments on 12 how such a search is proportional to their needs, nor shown that such a search would not 13 be unduly burdensome for Defendants. With this dearth of evidence, the Court, at this time, 14 will not require Defendants to run a full reverse search using responsive non-privileged 15 documents from their ESI custodians’ Google Vault collections. Instead, the Court will 16 allow Plaintiffs, once all responsive and non-privileged documents in the ESI custodians’ 17 Google Vault collections are produced, to select 200 documents that Defendants will 18 attempt to locate a parent email, if one exists. If a parent email exists, Defendants shall 19 produce it as long as it does not contain privileged information. Such limited search appears 20 proportional to Plaintiffs’ needs of knowing ‘who knew what and when,’ but will not be 21 unduly burdensome for Defendants. 22 In conclusion, Defendants must produce the most contemporaneous version of
23 11 See supra note 7. 12 As stated by Defendants’ counsel during the December 12, 2025, hearing: 24 We then ran our search terms against all documents that were 25 associated with a custodian, and also any folders in Google Drive that had been identified as likely containing potentially relevant information. 26 We then reviewed those for the emails and the Google Drive documents for responsiveness, and again, they are not associated in any way 27 at that time. There’s no family relationship. And then we produced the responsive—what is responsive and not privileged from that review. 28 Hearing Transcript at 24:17–25 (emphasis added). 1 responsive and non-privileged documents from the 25 ESI custodians’ Google Vault 2 collections. If the most contemporaneous version of a responsive document is not 3 obtainable, Defendants must produce a non-contemporaneous version of said document. 4 Finally, Plaintiffs may select 200 documents which Defendants will then use to search 5 emails from all 25 ESI custodians for parent emails, if a parent email exists. Defendants 6 shall use traditional ESI discovery techniques13 in this search. If a parent email is found, 7 Defendants shall produce it. 8 Accordingly, 9 IT IS ORDERED that Plaintiffs’ Motion to Compel Compliance (doc. 214) is 10 GRANTED IN PART AND DENIED IN PART. 11 IT IS FURTHER ORDERED that Plaintiffs SHALL select 250 responsive parent 12 emails with hyperlinked attachments that Defendants SHALL RUN AN FEC SEARCH 13 UPON. 14 IT IS FURTHER ORDERED that Defendants shall complete the FEC search and 15 provide Plaintiffs with the most contemporaneous version of non-privileged hyperlinked 16 attachments within 10 DAYS of receiving Plaintiffs’ selection. 17 IT IS FURTHER ORDERED that this Order DOES NOT preclude further usage 18 of FEC in this action. However, Plaintiffs have a heavy burden to meet if they seek to 19 compel further FEC usage in this action. 20 IT IS FURTHER ORDERED that Defendants must produce the most 21 contemporaneous version of responsive and non-privileged documents from the 25 ESI 22 custodians’ Google Vault collections using traditional ESI discovery techniques. If the 23 most contemporaneous version of a responsive document is not obtainable, Defendants 24 must produce a non-contemporaneous version of said document. 25 IT IS FURTHER ORDERED that Plaintiffs may select 200 responsive documents 26 from the ESI custodians’ Google Vault collections which Defendants will then use to 27 search emails from all 25 ESI custodians for parent emails. Defendants shall use traditional 28 13 See supra note 10. || ESI discovery techniques in this search. If a parent email is found, Defendants must 2|| produce it unless said email is privileged. Nothing in this Order should be construed as || precluding further requests to select additional responsive documents to run a search for 4|| parent emails. However, Plaintiffs bear the burden of establishing a need for further || searches. 6 Dated this 9th day of January, 2026. 7 Lo 8 S[seo 9 United States Magistrate Judge 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28
-12-