McGoveran v. Amazon Web Services, Inc.

District Court, D. Delaware·Decided October 18, 2024·No. 1:20-cv-01399·Unknown

Opinion

IN THE UNITED STATES DISTRICT COURT FOR THE DISTRICT OF DELAWARE CHRISTINE MCGOVERAN, et al., individually and on behalf of all others similarly situated, known and unknown, Plaintiffs, No. 1:20-cv-01399-SB v. AMAZON WEB SERVICES, INC. Defendant. Alexander L. Braitberg, Andrew D. Schlichter, Joel Rohlf, Nathan D. Stump, Peter Cosgrove, SCHLICHTER BOGARD LLP, St. Louis, Missouri; David T. Crumplar, JACOBS & CRUMPLAR, P.A., Wilmington, Delaware Counsel for Plaintiffs. Jody C. Barillare, MORGAN LEWIS & BOCKIUS LLP, Wilmington, Delaware; Ari M. Selman, MORGAN LEWIS & BOCKIUS LLP, New York, New York; Elizabeth Herring- ton, MORGAN LEWIS & BOCKIUS LLP, Chicago, Illinois; Jordan McCrary, MORGAN LEWIS & BOCKIUS LLP, Los Angeles, California; Raechel K. Kummer, MORGAN LEWIS & BOCKIUS LLP, Washington, DC. Counsel for Defendant. MEMORANDUM OPINION October 18, 2024

BIBAS, Circuit Judge, sitting by designation. Plaintiffs’ lawyers squandered their discovery time. They repeatedly asked for extensions, and I repeatedly denied those requests because they failed to show good cause. Yet they kept asking for more. While they were busy doing that, the months

passed. They kept trying to reopen fact discovery when they should have been con- ducting expert discovery. Because plaintiffs gave me no good reason to modify the scheduling order, I refused to do so—six times. This motion to reconsider is just their latest attempt to rehash this issue. Motions to reconsider exist to let district judges “correct manifest errors of law or fact or to present newly discovered evidence.” Max’s Seafood Cafe ex rel. Lou-Ann, Inc. v. Quinteros, 176 F.3d 669, 677 (3d Cir. 1999) (internal quotation marks omitted).

A party asking for reconsideration must show (1) a change in controlling law, (2) availability of new evidence, or (3) a need to prevent injustice, fix a factual error, or correct a clear legal mistake. Id. None is present. Rather, plaintiffs repeat the same points, asking again to reopen discovery. The answer is still no. I deny plaintiffs’ mo- tion for reconsideration. Seeking to avoid that outcome, plaintiffs also ask me to let them dismiss the only

named plaintiffs with standing. Because that is a ploy to avoid judgment against them, I deny that request too. I. FACT AND EXPERT DISCOVERY REMAINS CLOSED “A schedule may be modified only for good cause and with the judge’s consent.” Fed. R. Civ. P. 16(b)(4); Lehman Bros. Holdings v. Gateway Funding Diversified Mortg. Servs., L.P., 785 F.3d 96, 102 (3d Cir. 2015). In the last year, plaintiffs have asked me to change the fact discovery deadline six times. I denied all six for lack of good cause. Plaintiffs have not shown that anything has changed. A. I will not reopen fact discovery

Plaintiffs sued Amazon Web Services for allegedly violating the Illinois Biometric Information Privacy Act. I dismissed many of the claims, but one remained. D.I. 74. So in July 2023, I issued a scheduling order setting out how this case would proceed. D.I. 81. That order accepted the parties’ proposed deadline of March 15, 2024, as the cutoff for fact discovery. D.I. 80, 81. Six months later, in December 2023, a discovery dispute arose. I issued an order requiring Amazon to provide five more custodians, answer relevant interrogatories,

and meet and confer with plaintiffs about other issues. D.I. 114. But even after that, the parties told me they could not resolve a few search-term issues. D.I. 115. So I held a status conference on December 22, in which I told the parties I would not change any discovery deadlines without a stronger showing of cause; but I added that I might consider extending the deadlines a few weeks to finish up straggling items. See D.I. 152 at 2. I issued an oral order, directing plaintiffs to

submit new search terms and ordering Amazon to run the searches on all electronic discovery, except Slack. D.I. 118. Plaintiffs asked me to extend discovery at that time. But I denied the request, telling them to raise the issue again in mid-February, a month before fact discovery was set to close under the scheduling order. Id. In early January 2024, I ordered Amazon to produce documents based on plain- tiffs’ newest proposed list of search terms, which complied with my previous order. D.I. 123. Then in February, I held a hearing and required Amazon to finish all document production by the end of that month. D.I. 136. At that meeting, I reiterated that I would not extend discovery wholesale. See D.I. 152 at 2. I told plaintiffs to show me particular depositions that hinged on late-breaking documents and reasons why

they could not be completed by the deadline. See id. The day of that February hearing, plaintiffs filed a motion asking again to extend the fact discovery deadline. D.I. 135. They argued that Amazon had dragged its feet when producing documents, making it impossible for them to review all the docu- ments and depose witnesses by the mid-March deadline. Id. at 2. They complained that Amazon had produced only 3,000 documents, supposedly a fraction of what was produced in similar cases. Id. They accused Amazon’s lawyers of “refus[ing] to collab-

orate with plaintiffs on a proposed amended schedule,” instead seeking to “benefit from” violating the scheduling order. Id. at 3. They claimed that Amazon’s tactics were sanctionable. Id. at 7. So they proposed pushing back the fact discovery deadline by nine weeks. Id. at 9; D.I. 147-1 at 2. Amazon responded that it had produced 14,000 pages by early November, and it had to review an additional 65,000 documents after November 3 because of the

Court’s discovery-dispute ruling. D.I. 137 at 1. It had a thirty-lawyer team review more than 60,000 documents, producing 3,000 responsive pages and other native files in about a month. Id. at 2. I found Amazon’s representations credible. There was no good reason to extend discovery. So I stated again that I was “not inclined to grant a blanket discovery ex- tension but might entertain narrowly tailored requests for extensions.” D.I. 148. I gave plaintiffs until the March 2024 fact-discovery deadline to “amend their broad request.” Id. They trimmed their proposed extension from nine to seven weeks. D.I. 150-1 at 3. Otherwise their request remained unchanged. This was another blanket

discovery extension that I was not inclined to grant. Two days later, under the con- trolling scheduling order, fact discovery closed. D.I. 81. But a standing issue remained. D.I. 171. The named plaintiffs needed to show that they had suffered an injury-in-fact—that their phone calls were authenticated with- out consent. Id. So I ordered “limited discovery to assure the court that each of the twelve named plaintiffs” was actually injured. Id. I gave the parties until mid-May 2024 to conduct this limited discovery. Id. I reiterated this deadline a few weeks later.

D.I. 174. And I let plaintiffs depose a few witnesses to gather relevant information. D.I. 181. I also stayed all other discovery deadlines for thirty days, starting on April 22, 2024. Id. A month later, in May, plaintiffs asked to reopen fact discovery. D.I. 185 at 4. They claimed that they were still entitled to significantly more discovery on the merits and needed at least seven more weeks to get it. Id. I told plaintiffs that they could resub-

mit their motion to issue a new scheduling order once they got back some final bits of standing-related discovery. D.I. 189. This oral order inadvertently implied that the stay was still in place, but it had already expired by its original terms. D.I. 181. The parties did not raise this mistake with the Court, and it did not affect either party’s substantial rights.

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

McGoveran v. Amazon Web Services, Inc., (D. Del. 2024).

McGoveran v. Amazon Web Services, Inc. (McGoveran v. Amazon Web Services, Inc.) — published by Counsel Stack Legal Research, free access to 12M+ legal documents.

Related