Maria Groeschel v. Benevity International Inc.

• Court: District Court, W.D. Washington
• Decided: February 24, 2026
• Docket: 2:24-cv-01686
• Status: Unknown

Opinion

1 2

3 4 5 UNITED STATES DISTRICT COURT 6 WESTERN DISTRICT OF WASHINGTON AT SEATTLE 7 MARIA GROESCHEL, an individual, CASE NO. 2:24-cv-01686-JNW 8 Plaintiff, ORDER DENYING DEFENDANT’S 9 MOTION TO REOPEN DISCOVERY v. AND GRANTING PLAINTIFF’S 10 MOTION FOR PROTECTIVE ORDER BENEVITY INTERNATIONAL INC., a 11 foreign corporation,

12 Defendant. 13 14 1. INTRODUCTION Plaintiff Maria Groeschel pursues discrimination and state-law contract 15 16 claims against her former employer, Benevity International Inc. (“Benevity”). Trial is set for April 6, 2026, and the discovery deadline was November 7, 2025. See Dkt. 17 18 No. 12 at 2. After the discovery deadline, Benevity served a subpoena on Groeschel’s subsequent employer, Dropbox. Groeschel moves for a protective order and to quash 19 20 the subpoena, in part, because the subpoena is untimely. In response, Benevity moves to reopen discovery solely to serve its subpoena on Dropbox. It explains that 21 Dropbox’s response to its subpoena will provide relevant information about: (1) 22 23 Groeschel’s job offer from Dropbox; (2) how Groeschel has mitigated her damages; 1 and (3) the circumstances surrounding Groeschel’s departure from Dropbox. Dkt. 2 No. 51 at 2, 3. Having considered the briefing, the record, and the relevant law, the

3 Court DENIES Benevity’s motion to reopen and GRANTS Groeschel’s motion for 4 protective order. 5 2. DISCUSSION 6 2.1 The Court denies Benevity’s motion to reopen discovery. 7 When ruling on motions to reopen discovery, the Ninth Circuit has instructed 8 district courts to consider these factors: (1) “whether trial is imminent,” (2) “whether 9 the request is opposed,” (3) “whether the non-moving party would be prejudiced,” (4) 10 “whether the moving party was diligent in obtaining discovery within the guidelines 11 established by the court,” (5) “the foreseeability of the need for additional discovery 12 in light of the time allowed for discovery by the district court,” and (6) “the 13 likelihood that the discovery will lead to relevant evidence.” City of Pomona v. SQM 14 N. Am. Corp., 866 F.3d 1060, 1066 (9th Cir. 2017) (quotation omitted). After 15 considering these factors, the Court finds that reopening discovery is unwarranted. 16 Trial is less than two months away, Groeschel opposes the motion, and she 17 would be prejudiced by reopening discovery at this late stage given the significant 18 scope of information Benevity seeks from Dropbox, including her complete 19 personnel file. Most significantly, the moving party—Benevity—was not diligent. 20 Benevity served no written discovery in this case, nor did it subpoena Dropbox 21 within the discovery window. Benevity explains that these were deliberate tactical 22 decisions based on financial considerations and its belief that it did not need 23 1 additional discovery. Dkt. No. 51 at 6. But a party that makes a strategic choice to 2 forgo available discovery cannot later claim good cause to reopen it.

3 Nor was the need for this discovery unforeseeable. Benevity knew throughout 4 discovery that Groeschel worked at Dropbox. The bulk of what the subpoena 5 seeks—her application, personnel file, compensation, and benefits—existed well 6 before the deadline. And while Groeschel’s departure from Dropbox occurred in 7 November 2025, near the close of discovery, Benevity did not learn of it until the 8 first week of December, Dkt. No. 52 ¶ 3, and did not file this motion until January

9 21, 2026—over six weeks later. That delay further undermines any claim of 10 diligence. 11 Finally, the likelihood that the discovery will lead to relevant evidence is 12 speculative at best. Benevity theorizes that Groeschel’s departure from Dropbox 13 “may provide corroboration” for its own termination decision because “Dropbox is 14 the fourth employer in a row in which Plaintiff has failed to maintain employment 15 for two years.” Dkt. No. 51 at 7. But there has been no showing that Groeschel was

16 terminated by Dropbox, and the Court declines to reopen discovery based on 17 speculation that her personnel file might reveal a pattern of misconduct. See 18 Greenburg v. Red Robin Int’l, Inc., No. C17-6052-BHS, 2018 WL 2329671, at *1 19 (W.D. Wash. May 23, 2018) (declining to permit a “fishing expedition into 20 [plaintiff’s] private records based on a hypothetical”). To the extent Benevity needs 21 information bearing on mitigation—such as Groeschel’s post-termination

22 compensation—that need does not require reopening discovery. The duty to 23 supplement discovery responses under Federal Rule of Civil Procedure 26(e) 1 continues after the discovery cutoff. See K.J.P. v. County of San Diego, 621 F. Supp. 2 3d 1097, 1138 (S.D. Cal. 2022). Groeschel remains bound by that obligation. After

3 considering the relevant factors, see Pomona, 866 F.3d at 1066, the Court finds that 4 they do not support reopening discovery here. The Court denies Benevity’s motion 5 to reopen discovery. 6 2.2 Neither party is entitled to sanctions. 7 Groeschel asks for sanctions in response to Benevity’s motion to reopen 8 discovery, arguing that she should not be “required to expend time, resources, costs, 9 and attorneys’ fees to defend against motions that are untimely and the result of 10 Benevity’s failure to act with diligence.” Dkt. No. 56 at 7. But the authority she cites 11 –Rule 37(c)(1)—governs sanctions for failure to disclose or supplement, not for filing 12 a non-frivolous motion to reopen discovery. Thus, the Court denies Groeschel’s 13 motion for sanctions. 14 Benevity, in turn, requests sanctions against Groeschel’s counsel under 28 15 U.S.C. § 1927, which authorizes imposing costs and fees against any attorney who 16 “multiplies the proceedings in any case unreasonably and vexatiously.” “The 17 imposition of sanctions under section 1927 requires a finding that counsel acted 18 recklessly or in bad faith.” United States v. Blodgett, 709 F.2d 608, 610 (9th Cir. 19 1983) (citation modified). The Court does not find that Groeschel’s counsel has 20 “multiplied” these proceedings or acted in bad faith. Accordingly, the Court denies 21 Benevity’s motion for sanctions. 22 23 1 2.3 The Court grants Groeschel’s motion for a protective order. District courts in the Ninth Circuit have held that subpoenas for documents 2 issued under Federal Rule of Civil Procedure 45 are “not exempt from discovery 3 deadlines in scheduling orders.” Polskie Linie Lotnicze LOT S.A. v. The Boeing Co., 4 Case No. C21-1449RSM, 2026 WL 234071, at *1 (W.D. Wash. Jan. 29, 2026) 5 (quotations omitted); Davis v. Tri-Cnty. Met. Transp. Dist. of Or., No. 3:12–cv–0808– 6 SI, 2015 WL 3823826, at *1 (D. Or. June 18, 2015) (quoting Integra Lifesciences I, 7 Ltd. v. Merck KgaA, 190 F.R.D. 556, 561–62 (S.D. Cal. 1999) (collecting cases)). 8 Likewise, many courts have held that subpoenas issued after the close of discovery 9 impermissibly seek to circumvent discovery deadlines. Davis, 2015 WL 3823826, at 10 *1 (quoting Integra Lifesciences I, Ltd., 190 F.R.D. at 561–62 (“Plaintiffs are correct 11 in their assertion that the subpoena issued by Defendants was an improper use of 12 discovery devices after the close of discovery in this case.”)). Because the Court 13 denies Benevity’s motion to reopen discovery, and because Benevity served the 14 subpoena on Dropbox after the close of discovery, Groeschel’s motion for protective 15 order is granted. 16 17 3. CONCLUSION 18 Accordingly, the Court ORDERS that Defendant’s motion to reopen discovery 19 is DENIED, Dkt. No. 51, and Plaintiff’s motion for protective order is GRANTED, 20 Dkt. No. 50. Benevity’s subpoena issued to Dropbox on December 9, 2025, is 21 QUASHED. 22

23 1 Dated this 24th day of February, 2026.

3 United States District Judge 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23