SinglePoint Direct Solar LLC v. Curiel

District Court, D. Arizona·Decided March 21, 2023·No. 2:21-cv-01076·Unknown

Opinion

1 WO 2 3 4 5 6 IN THE UNITED STATES DISTRICT COURT 7 FOR THE DISTRICT OF ARIZONA

9 SinglePoint Direct Solar LLC and No. CV-21-01076-PHX-JAT SinglePoint Incorporated, 10 ORDER Plaintiffs, 11 v. 12 Solar Integrated Roofing Corporation and 13 USA Solar Network LLC,

14 Defendants. 15 16 I. Summary of Issue before the Court 17 Pending before the Court is a discovery dispute between the parties. (Doc. 186). At 18 bottom, the issue is that Plaintiffs believe Defendants’ ESI search terms are objectionable 19 because the terms produced many responsive documents. More specifically, Plaintiffs 20 agree that 122,607 responsive documents must be produced, but argue that the remaining 21 287,381 documents are so voluminous as to be objectionable. 22 Other than these general statements, recounting Plaintiffs’ objections to Defendants’ 23 ESI search terms defies a simple summary. Search terms were exchanged in July of 2022. 24 On September 26, 2022, Plaintiffs objected to the majority of Defendants’ search terms. 25 In January 2023, Plaintiffs made additional objections. Then on March 3, 2023, Plaintiffs 26 made more objections. At some point during these rolling objections, Defendants 27 narrowed their ESI search terms but not to the satisfaction of Plaintiffs. The parties now 28 agree that 28 of Defendants’ ESI search terms remain in dispute. (A list of the in-dispute 1 terms and the number of responsive documents to each of them is at Doc. 186-1 at 4-5). 2 Again, Plaintiffs object to reviewing and (as necessary) producing 287,381 documents that 3 “hit” when the search terms were run. 4 Defendants seek to have the Court overrule all of Plaintiffs’ objections. Defendants 5 argue that Plaintiffs have waived their objections by not timely asserting them, and that 6 their boilerplate objections are legally insufficient and should be rejected for this 7 alternative reason. Finally, Defendants argue that if they do not prevail on either of these 8 procedural objections, all of Plaintiffs objections are not well taken and should be overruled 9 on their merits. 10 II. Timeliness 11 Turning first to the timeliness of Plaintiffs’ objections, the parties joint briefing does 12 not lay out an exact chronology of when Plaintiffs first made objections, and the scope of 13 those objections. 14 The best timeline the Court can put together is that in July of 2022 the parties 15 exchanged search terms (the Court believes this exchange was the result of discovery 16 propounded in April 2022, but that is unclear). (Doc. 186-1 at 3). On September 26, 2022, 17 Plaintiffs made some objections to Defendants’ proposed search terms. (Id.). On 18 December 21, 2022, the parties “agreed” to run their respective search terms against the 19 data base of documents. (Id.). The Court is unclear what “agreed” means in this sentence. 20 Defendants produced their responsive documents on March 4, 2023. (Id.). The 21 Court does not know what agreement between the parties allowed Defendants to respond 22 8 months after the parties exchanged search terms and over 2 months after the terms were 23 “agreed” to be run. As for Plaintiffs, on January 9, 2023, they sent “additional” objections 24 to their September 26, 2022, objections. (Id.). These January-2023 objections were 25 obviously after the December 21, 2022 “agreement”. (Id.). The Court has not been given 26 an exact copy of Plaintiffs’ September 2022 or January 2023 objections. On January 25, 27 2023, Plaintiffs again “agreed” to run Defendants search terms. (Id.). The Court still does 28 1 not know what the parties mean by “agreed.”1 2 On March 3, 2023, Plaintiffs made another round of objections. (Doc. 186-1 at 4 3 (the objection is quoted in full in this document)). It is from this March 3, 2023, objection 4 that the Court has summarized the objections discussed below. As stated above, 5 Defendants claim either all or some of Plaintiffs’ objections are untimely. 6 The parties agreed-to ESI protocols (which the Court did not adopt or reject (see 7 Doc. 145)) state the following regarding objections to ESI requests, “[the requesting party 8 will]…provide the Disclosing Party with a reasonable opportunity (no less than 14 days) 9 to object to the scope of the request.” (Doc. 186-1 at 3). If the Court were asked to rule 10 on these protocols back in July 2022, the Court would have found that the parties’ protocols 11 are unmanageable because they do not set a specific timeframe for objections. The Court 12 would have also found that objecting in March of 2023 to search terms that were exchanged 13 in July of 2022 is not “reasonable”. But the protocols do not say an objection will be made 14 “in a reasonable time”. They say that the responding party will get at least a reasonable 15 time. The parties’ poorly crafted protocols defeat Defendants’ argument that the objections 16 are untimely. 17 Moreover, Plaintiffs objected in March of 2023. Defendants responded in March of 18 2023. If Plaintiffs’ objections are sanctionably late, Defendants responses are equally, 19 sanctionably late. Clearly both parties seemed to believe March 2023 “responses” to the 20 outstanding discovery were “reasonable”. Accordingly, the Court will not find Plaintiffs’ 21 objections to be waived on the basis of timeliness. 22 III. Boilerplate Objections 23 Next, Defendants argue Plaintiffs objections are “boilerplate” and that a boilerplate 24 objection is inadequate to preserve an objection. Legally, Defendants are correct that 25 boilerplate objections do not preserve an objection. See Blemaster v. Sabo, No. 2:16-CV- 26 04557 JWS, 2017 WL 4843241, at *4 (D. Ariz. Oct. 25, 2017). Factually, Defendants are 27 correct that Plaintiffs’ March-2023 objection, quoted at Doc. 186-1 at 4, as applied to 28

28 1 To the extent “agreed” merely means “run the search terms in the database,” there is no excuse for the parties’ delay from July 2022 to December 2022 to complete this step. 1 distinct search terms is a boilerplate objection. However, at Doc. 186-1 at 4, it states, “By 2 way of example, Plaintiffs have objected to the search term ‘acquisition’ on the basis that 3 the term is not relevant to the case.” (emphasis added). This sentence leads the Court to 4 believe Plaintiffs made more particularized objections at some point. Thus, on this record, 5 the Court cannot conclude that Plaintiffs’ objections, which the Court does not have all of, 6 were only boilerplate objections. Thus, the Court rejects Defendants argument (without 7 prejudice) that all of Plaintiffs’ objections were waived for lack of specificity. 8 IV. Objections 9 A. Proportionality 10 Regarding proportionality, the Court agrees that 409,988 responsive documents is 11 voluminous. However, Plaintiffs chose to bring a wide-ranging lawsuit based on 13 claims 12 for relief, eight of which relate to the remaining Defendants. The remaining causes of 13 action are sophisticated and include: (1) cause of action (“COA”) No. 1, Lanham Act 14 Violation (15 U.S.C. § 1125(a))–SDS against all Defendants; (2) COA No. 2, 15 Misappropriation of Trade Secrets in violation of the Defend Trade Secrets Act, 18 U.S.C. 16 § 1836 et seq. – SDS against all Defendants; (3) COA No. 7, Unfair Competition – SDS 17 against all Defendants; (4) COA No. 8, Violation of Arizona Uniform Trade Secrets Act 18 (A.R.S. § 44-401 et seq.) – Plaintiffs against all Defendants; (5) COA No. 9, Intentional 19 Interference with Contract/Business Expectancy – SDS against all Defendants; (6) COA 20 No. 10, Conversion – SDS against all Defendants; (7) COA No. 11, Unjust Enrichment – 21 Plaintiffs against all Defendants; and, (8) COA No.

Free access — add to your briefcase to read the full text and ask questions with AI

SinglePoint Direct Solar LLC v. Curiel, (D. Ariz. 2023).

SinglePoint Direct Solar LLC v. Curiel (SinglePoint Direct Solar LLC v. Curiel) — published by Counsel Stack Legal Research, free access to 12M+ legal documents.

Related