throbber
Case 4:20-cv-05640-YGR Document 304 Filed 02/01/21 Page 1 of 3
`
`
`
`
`
`
`
`
`
`
`
`UNITED STATES DISTRICT COURT
`
`NORTHERN DISTRICT OF CALIFORNIA
`
`Case No. 20-cv-05640-YGR (TSH)
`
`
`DISCOVERY ORDER
`
`Re: Dkt. No. 297
`
`EPIC GAMES, INC.,
`
`Plaintiff and Counter-
`
`defendant,
`
`v.
`
`APPLE INC.,
`
`Defendant and
`
`
`
`Counterclaimant.
`
`
`
`
`
`We are here on Epic Games’ motion to compel Apple to produce non-custodial documents
`
`responsive to RFPs 12-14, 18, 19, 25 and 31 by February 5, 2021. ECF No. 297. Epic served
`
`these RFPs on October 23, 2020. ECF No. 275, Ex. 1. On December 26, 2020 Apple agreed to
`
`produce non-custodial documents in response to these RFPs. ECF No. 297-7. On January 27,
`
`2021, Apple stated that it planned to complete those productions by February 15, 2021. ECF No.
`
`297-13.
`
`The case scheduling order provides that the fact discovery cutoff is February 15, 2021,
`
`which is also the date that opening expert reports are due. ECF No. 116. In setting this schedule,
`
`Judge Gonzalez Rogers set a separate deadline of January 6, 2021 for the completion of document
`
`productions. ECF No. 111 at 100. Epic observes that there is no disagreement about whether
`
`Apple must produce non-custodial documents in response to these RFPs because it agreed to do
`
`so. Epic also observes that Apple did not produce them by the January 6 deadline to do so. Epic
`
`now argues that the Court should order Apple to produce them by February 5 so that Epic’s
`
`experts will have at least some opportunity to consider them in preparing their expert reports.
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`Northern District of California
`
`United States District Court
`
`

`

`Case 4:20-cv-05640-YGR Document 304 Filed 02/01/21 Page 2 of 3
`
`
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`Apple responds that the close of fact discovery is February 15 and asserts it will produce
`
`the documents by then. Apple acknowledges that with respect to document productions, January 6
`
`was the deadline to produce. But Apple says that it has told everyone that due to Epic’s excessive
`
`document demands, it would not be able to complete document productions by January 6, and
`
`Apple observes that Epic itself has made some document productions after that date, which Epic
`
`agrees is true. More generally, Apple blames Epic for requesting (and obtaining) a fast case
`
`schedule and then asking for lots of discovery, which Apple says renders that schedule infeasible.
`
`Let’s begin with the ground rules. January 6 was the Court-ordered deadline to complete
`
`document productions. If Judge Gonzalez Rogers had set a February 15 deadline for the close of
`
`fact discovery and said nothing else, then February 15 would have been the deadline for all forms
`
`of discovery, including document productions. But she did say something else, which is that
`
`document productions had to be completed by January 6. Accordingly, Apple’s argument that it is
`
`acceptable for it to complete these document productions by February 15 is wrong.
`
`Both sides have violated the January 6 deadline, but that deadline was never altered by
`
`Judge Gonzalez Rogers. You’re not allowed to violate a court order just because your opponent
`
`did, or because you announced to the world that compliance was infeasible and you planned to
`
`violate it. So, Epic’s own failures to produce by that date don’t excuse Apple’s non-compliance,
`
`and Apple’s existing non-compliance with that deadline does not justify more noncompliance.
`
`Besides, Epic is making a more specific argument now and is not just complaining about
`
`missed deadlines. Epic is saying that for Apple to produce these particular documents by
`
`February 15 prejudices Epic’s ability to have its experts use them. Given the topics at issue, it is
`
`logical that Epic’s experts would want to be able to consider these documents in preparing their
`
`reports.
`
`Apple does not have a good response to this problem and at the hearing acknowledged this.
`
`Apple said it is working as hard as possible but cannot promise to complete these document
`
`productions by February 5. At this point the Court views the problem as a practical one. Epic is
`
`entitled to these documents in time for its experts to be able to review them, but this is a late-
`
`breaking discovery dispute and February 5 is only four days away. The Court will not order
`
`Apple to do something that might be impossible, but it will order Apple to try as hard as it can.
`
`2
`
`Northern District of California
`
`United States District Court
`
`

`

`Case 4:20-cv-05640-YGR Document 304 Filed 02/01/21 Page 3 of 3
`
`
`
`Accordingly, the Court orders Apple to use its best efforts to produce non-custodial documents
`
`responsive to RFPs 12-14, 18, 19, 25 and 31 by February 5, 2021
`
`IT IS SO ORDERED.
`
`
`
`Dated: February 1, 2021
`
`
`
`
`
`THOMAS S. HIXSON
`United States Magistrate Judge
`
`3
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`Northern District of California
`
`United States District Court
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket