Doev.Trump

UNITED STATES DISTRICT COURT WESTERN DISTRICT OF WASHINGTON AT SEATTLEDec 20, 2018
CASE NO. C17-0178JLR (W.D. Wash. Dec. 20, 2018)

CASE NO. C17-0178JLR CASE NO C17-1707JLR

12-20-2018

JOHN DOE, et al., Plaintiffs, v. DONALD TRUMP, et al., Defendants. JEWISH FAMILY SERVICES, et al., Plaintiffs, v. DONALD TRUMP, et al., Defendants.


ORDER GRANTING IN PART AND DENYING IN PART PLAINTIFFS' MOTION TO COMPEL (RELATING TO BOTH CASES)

I. INTRODUCTION

Before the court is Plaintiffs' joint motion to compel discovery from Defendants. (Mot. (Dkt. # 166).) Defendants oppose the motion. (Resp. (Dkt. # 169).) The court has considered the motion, the parties' submissions in favor of and in opposition to the motion, other relevant portions of the record, and the applicable law. Being fully advised, the court GRANTS in part and DENIES in part the motion. // // // //

This is a consolidated action. (See 11/29/17 Order (Dkt. # 61).) Plaintiffs from cause number C17-0178JLR include: Jewish Family Services of Seattle, Jewish Family Services of Silicon Valley, Allen Vaught, Afkab Mohamed Hussein, John Does 1-3 and 7, and Jane Does 4-6's (collectively, "JFS Plaintiffs"). Plaintiffs from cause number C17-1707JLR include: John Doe, Episcopal Diocese of Olympia, Joseph Doe, James Doe, Council on American Islamic Relations - Washington, Jack Doe, Jason Doe, and Jeffrey Doe (collectively, "Doe Plaintiffs"). Both sets of Plaintiffs bring the present motion.

Defendants include: President Donald Trump, United States Department of State ("DOS"), Secretary of State Mike Pompeo, United States Department of Homeland Security ("DHS"), DHS Secretary Kirstjen M. Nielsen, United States Customs and Border Protection ("USCBP"), Commissioner of USCBP Kevin McAleenan, Field Director of the Seattle Field Office of USCBP Michele James, Office of the Director of National Intelligence, and Director of National Intelligence ("DNI") Daniel Coats (collectively, "Defendants").

As noted above, the court consolidated cause numbers C17-0178JLR and C17-1707JLR. (See 11/29/17 Order); see also supra Note 1. All references in this order to the docket are to cause number C17-0178JLR unless the docket number is preceded by "17-1707." For example, if the docket number in the citation appears as "17-1707 Dkt. # 1," then the docket reference is to cause number C17-1707JLR.

Plaintiffs request oral argument. (See Mot. at 1.) The court, however, determines that oral argument would not be of assistance in deciding the motion. See Local Rules W.D. Wash. LCR 7(b)(4). Accordingly, the court denies Plaintiffs' request.

II. BACKGROUND

A. The Case History

President Trump has issued a series of executive orders concerning immigration and refugees. (See 7/27/18 Order (Dkt. # 155) at 3-7.) This litigation most recently addressed the fourth such order, Executive Order 13815 ("EO4"), entitled "Resuming the United States Refugee Admissions Program with Enhanced Vetting Capabilities." 82 Fed. Reg. 50,055 (Oct. 24, 2017). Although EO4's title indicates that the government has resumed refugee admissions, the memorandum that accompanied EO4—known as the "Agency Memo"—imposed another ban on certain categories of refugees. (See Lin Decl. (Dkt. # 46) ¶ 3, Ex. B (attaching a copy of the Agency Memo).)

First, the Agency Memo suspended indefinitely "following-to-join" ("FTJ") derivative refugees. Every year, approximately 2,500 refugees in the United States are able to reunite with their immediate family members through the FTJ process. (Agency Memo at 2 n.1.) The Agency Memo stated that most FTJ refugee applicants do not undergo the same security procedures as the principal refugee who has already resettled in the United States. (Id. at 2-3.) The Secretaries of DOS and DHS and the DNI determined that FTJ refugees should not be admitted to the United States until additional screening procedures were in place. (Id. at 3.)

Under the Immigration and Nationality Act ("INA"), subject to numerical limits that the President sets annually, the Secretary of DHS may admit "any refugee who is not firmly resettled in any foreign country, is determined to be of special humanitarian concern to the United States, and is admissible (except as otherwise provided under ([8 U.S.C. § 1157(c)(3)]) as an immigrant." 8 U.S.C. § 1157(c)(1). Refugees admitted under this provision are "principal refugees." See 8 C.F.R. § 207.7(a). "Derivative refugees" are the spouses and unmarried minor children of an admitted principal refugee. See id. When derivative refugees travel to join a principal refugee more than four months after the principal refugee's admission, they are FTJ derivative refugees, rather than "accompanying" derivative refugees. See id.

Second, the Agency Memo suspended for at least 90 days the entry of refugees who are "nationals of, and stateless persons who last habitually resided in, 11 particular countries previously identified as posing a higher risk to the United States through their designation on the Security Advisory Opinion (SAO) list." (Id. at 2-3.) The Agency Memo does not identify the countries designated on the SAO list, but they are believed to be Egypt, Iran, Iraq, Libya, Mali, North Korea, Somalia, South Sudan, Sudan, Syria, and Yemen. (See PI Order (Dkt. # 92) at 10-11 n.6; 11/16/17 Smith Decl. (17-1707 Dkt. # 44) ¶ 3.) The Agency Memo required DOS and DHS to "conduct a review and analysis" of the United States Refugee Admissions Program ("USRAP") for refugees from SAO countries for an additional 90 days—notwithstanding the agencies' previous review of USRAP pursuant to EO1 and EO2. (See id.) In addition, the Agency Memo diverted resources dedicated to processing refugees who are citizens of (or stateless persons who last resided in) SAO countries and reallocated those resources to processing refugee applicants from non-SAO countries. (Id.)

JFS Plaintiffs filed suit and Doe Plaintiffs amended their complaint to challenge the Agency Memo's suspension of FTJ and SAO refugee admissions (see TAC (Dkt. # 42); Compl. (17-1707 Dkt. # 1)); and both sets of Plaintiffs moved for a preliminary injunction blocking those provisions of the Agency Memo (see Doe PI Mot. (Dkt. # 45); JFS PI Mot. (17-1707 Dkt. # 42)). On November 29, 2017, the court consolidated the two actions. (See 11/29/17 Order.) On December 23, 2017, the court granted both JFS Plaintiffs' and Doe Plaintiffs' motions and enjoined Defendants from enforcing (1) "those provisions of the Agency Memo that suspend the processing of FTJ refugee applications or suspend the admission of FTJ refugees into the United States," and (2) "those provisions . . . that suspend or inhibit, including through the diversion of resources, the processing of applications or the admission into the United States of refugees from SAO countries." (PI Order at 64-65.) The court, however, limited its preliminary injunction to refugees "with a bona fide relationship to a person or entity within the United States." (Id. at 65.)

See supra note 1.

See supra note 1.

Within a few days, Defendants moved for an "emergency" stay of the injunction pending appeal. (MFS (Dkt. # 95).) In that motion, Defendants narrowly interpreted the court's injunction. (See id. at 4-6.) Defendants asserted that they were not required to undo any actions taken or decisions made prior to December 23, 2017, to implement the SAO or FTJ suspensions. (See id.) On January 9, 2018, the court denied Defendants' motion (1/9/18 Order (Dkt. # 106) at 7-16) and rejected their cramped interpretation of the court's preliminary injunction (id. at 5-7). The court admonished Defendants for attempting "to unilaterally modify the preliminary injunction" and ordered them to "restore the status quo prior to the issuance of the Agency Memo with respect to the processing of applications from FTJ refugees and refugees from SAO countries." (Id. at // 5-6.) On January 4, 2018, Defendants filed a notice of appeal concerning the court's preliminary injunction. (NOA (Dkt. # 99).)

On February 6, 2018, following the completion of the 90-day SAO refugee review on January 22, 2018, and the implementation of additional procedures for FTJ refugees on or about February 1, 2018 (see 1/31/18 Notice (Dkt. # 119) at 1-2), Defendants moved to dismiss as moot their appeal (and Plaintiffs' cross-appeal) in the Ninth Circuit. See Doe v. Trump, No. 18-35026 (9th Cir.), Dkt. # 24 at 2. On March 29, 2018, the Ninth Circuit denied Defendants' motion to dismiss and instead granted Plaintiffs' request to remand the consolidated case so that this court could address the issue of mootness in the first instance. (3/29/18 9th Cir. Order (Dkt. # 126); 9th Cir. Mandate (Dkt. # 144).)

On remand, this court ordered the parties to file a joint status report proposing how the court should proceed on remand to address the issue of mootness. (Id. at 3.) In accordance with their joint status report (JSR (Dkt # 129)), JFS Plaintiffs filed a motion to reinstate a prior request for limited discovery on Defendants' compliance with the preliminary injunction and mootness (see 2d MFD (Dkt. # 131)), in which Doe Plaintiffs joined (see 5/7/18 Order (Dkt. # 141) (granting Doe Plaintiffs' motion to join)); and Defendants filed a motion to dismiss based on mootness (see MTD (Dkt. # 145)). Based on the parties' submissions, the court found that Plaintiffs had "demonstrated a bona fide factual dispute concerning the existence and effectiveness of Defendants' steps to discontinue the enjoined aspects of the Agency Memo." (7/27/18 Order at 28.) Accordingly, the court concluded that allowing Plaintiffs to conduct limited jurisdictional discovery into the issues of compliance with the preliminary injunction and mootness was warranted. (Id. at 28.) The court also denied Defendant's motion to dismiss, but did so without prejudice to renewing the motion after Plaintiffs completed their jurisdictional discovery. (Id.)

B. The Parties' Conduct of Discovery

The court granted Plaintiffs 90 days to conduct the necessary discovery into mootness. (Id. at 29.) The following briefly recounts the parties' intricate conduct of jurisdictional discovery during that period.

1. Requests for Production of Documents

On August 1, 2018, just two days after receipt of the court's order granting jurisdictional discovery, Plaintiffs served Defendants with a joint request for production of documents that consisted of three requests ("First RFPs"). (Keaney Decl. (Dkt. # 167) ¶ 2.) On August 7, 2018, Defendants stated that they would provide their objections within 21 days and produce responsive documents within 45 days. (Id. ¶ 6, Ex. 21 at 1.) In addition, Defendants stated that they did "not intend to respond to 'Request for Production No. 3' [("RFP No. 3")] as written." (Id. at 2 (underlining and bolding omitted).) On August 22, 2018, Defendants served written objections to Plaintiffs' First RFPs. (Id. ¶ 8, Ex. 22.) Among other objections, Defendants also declined to respond to Request for Production No. 1 ("RFP No. 1") as written and unilaterally narrowed the request to only "final, formal guidance documents," instead of all "policies, directives, instructions, guidelines, guidance, advisals, cables, notices, training, memorand[a]" and similar documents. (Id.) Counsel for Plaintiffs and Defendants exchanged correspondence in late August and early September, 2018, outlining their respective positions concerning Defendants' objections. (Id. ¶¶ 9-10, Exs. 23-24.)

Defendants produced 786 pages of records responsive to Plaintiffs' First RFPs on September 14, 2018—45 days after service of the requests. (Id. ¶ 11.) Defendants produced an additional 22 pages on October 12, 2018—73 days after service of the requests. In total, Defendants produced 808 pages of documents. (Id.)

2. Privilege Log

On September 21, 2018, Defendants served Plaintiffs with an admittedly incomplete privilege log. (Id. ¶ 13.) Defendants served Plaintiffs with revised privilege logs on September 25, October 17, and October 22, 2018. (Id. ¶¶ 14 19-20, Ex. 3.) Defendants withheld certain documents claiming a "law enforcement sensitive privilege." (Id. ¶ 34.) The parties conducted a telephonic meet and confer conference on October 16, 2018. (Id.) Although Defendants lifted some of the redactions to the documents they produced as a result of the October 16, 2018, conference, they also added redactions based on the parties' Federal Rule of Evidence 502(d) agreement. (Id. ¶ 35; see also 502(d) Order (Dkt. # 160).)

3. Interrogatories

On August 10, 2018, the parties met and conferred about Defendants' objections to RFP No. 3. (Keaney Decl. ¶ 7.) The parties agreed that Plaintiffs should narrow their request and re-issue RFP No. 3 as a set of interrogatories. (Id.) On August 17, 2018, Plaintiffs served Defendants with Plaintiffs first set of interrogatories ("First ROGs"). (Id. ¶¶ 7, 21, Ex. 5.) On September 1, 2018, Defendants sent their objections to the First ROGs and indicated that six were overly burdensome. (Id. ¶ 24, Ex. 30.) On September 5, 2018, Defendants indicated that they would need until September 26, 2018, to respond to Plaintiffs' First ROGs. (Id. ¶ 25.) Defendants served written responses and objections to Plaintiffs' First ROGs on September 26, 2018—40 days after service. (Id. ¶ 28.)

On September 6, 2018, Plaintiffs agreed to narrow the six interrogatories that Defendants identified as overly burdensome and propounded a narrower set of these six interrogatories ("Third ROGs"). (Id. ¶ 26, Ex. 6.) On October 5, 2018, Defendants produced their written responses and objections to Plaintiffs' Third ROGs. (Id. ¶ 29.)

Doe Plaintiffs propounded a single interrogatory related to the FTJ suspension, which was labelled as "Plaintiff Joseph Doe's Second Set of Interrogatories to Defendants." (Keaney Decl. ¶ 26 n.1.) This set of interrogatories is not at issue in Plaintiffs' motion.

Defendants supplemented their responses to Plaintiffs First ROGs on October 10, 2018. (Id. ¶ 30.) Defendants supplemented their responses to Plaintiffs Third ROGs on October 11, 2018. (Id. ¶ 30.)

After reviewing Defendants' September 14 and October 12, 2018, document productions, as well as Defendants' final supplemental responses on October 10 and October 11, 2018, to Plaintiffs' First ROGs and Third ROGs, respectively, Plaintiffs determined that six follow-up interrogatories were necessary to aid in Plaintiffs' assessment of Defendants' compliance with the court's preliminary injunction. (Id. ¶ 32.) Accordingly, on October 5, 2018, Plaintiffs served Defendants with a fourth set of interrogatories ("Fourth ROGs"). (Id. ¶ 32, Ex. 1.) On October 9, 2018, Defendants sent a letter to Plaintiffs refusing to respond to Plaintiffs' Fourth ROGs. (Id. ¶ 33, Ex. 31.) Specifically, Defendants complained that Plaintiffs' Fourth ROGs were "tardy" because the period the court set for jurisdictional discovery was "set to close on [October 25, 2018,] less than three weeks from the date Plaintiffs served their [Fourth ROGs]." (Id.) Defendants also complained that Fourth ROGs were burdensome because they seek "week-by-week data" and information about refugee applicants who are not Plaintiffs' attorneys' clients. (Id.; see also Gauger Decl. (Dkt. # 169-1) ¶¶ 4, 8-9.)

4. Deposition Requests

After reviewing Defendants' document productions and interrogatory responses, Plaintiffs decided that they would like to take the depositions of two employees of Defendant agencies, Kelly Gauger and Jennifer Higgins. (Id. ¶ 38.) Both of these individuals have submitted multiple declarations to the court during the course of this litigation. (See Dkt. ## 51-1, 114-1, 114-2, 142-1, 142-2, 169-1.) Plaintiffs also decided to note two Federal Rule of Civil Procedure 30(b)(6) depositions. (Keaney Decl. ¶ 38.) Plaintiffs first informed Defendants of their intention to request Rule 30(b)(6) depositions on October 4, 2018—more than twenty days prior to the October 25, 2018, discovery cutoff. (See Resp. Ex. H.) Plaintiffs further notified Defendants of their intentions concerning both the fact witness and Rule 30(b)(6) depositions on October 10, 2018. (Keane Decl. ¶ 38, Ex. 32.) Defendants responded on the same day stating that "for the proposed depositions, the parties will likely need to ask guidance from the Court," and that it is "doubt[ful] that Defendants will be amenable to your eleventh hour and expansive deposition requests." (Id. ¶ 39, Ex. 33.)

Ms. Higgins is the Associate Director of the Refugee, Asylum, and International Operations ("RAIO") Directorate at the United States Citizenship and Immigration Services ("USCIS"). Defendants have submitted three declarations from Ms. Higgins in this litigation, the latter two concerning injunction compliance. (Dkt. ## 51-1, 114-2, 142-2.) Ms. Gauger is the Acting Director of the Admissions Office of the Bureau of Population, Refugees, and Migration ("PRM/A") of DOS. Defendants have submitted three declarations from Ms. Gauger, the first two concerning injunction compliance. (Dkt. ## 114-1, 142-1, 169-1.)

Plaintiffs requested a meet and confer conference regarding the deposition requests, which occurred on October 16, 2018. (Id. ¶¶ 41-42.) At the meet and confer conference, Defendants asked Plaintiffs to serve their Rule 30(b)(6) notices to enable Defendants to determine their position. (Id. ¶ 42.) On October 17, 2018, Plaintiffs served their Rule 30(b)(6) notices, which are identical except that one notice is directed to DOS and the other is directed to DHS. (Id. ¶ 42, Ex. 2.) On October 19, 2018, Defendants declined to permit Plaintiffs access to either of the two factual witness or to produce the requested Rule 30(b)(6) deponents. (Id. ¶ 43, Ex. 35.)

5. The Present Motion

On October 22, 2018, Plaintiffs filed the present motion to compel. Plaintiffs seek an order compelling Defendants to respond to Plaintiffs' Fourth ROGs, to produce two Rule 30(b)(6) deponents as requested, and to allow Plaintiffs to depose Ms. Higgins and Ms. Gauger. (Mot at 10.) In addition, Plaintiffs seek an order compelling Defendants to produce two types of information that they have previously redacted: (1) any information that would tend to reveal the names of any of the 11 SAO countries (id. at 10-11); and (2) information that Defendants have redacted as non-responsive from previously produced documents, including (a) information about individual refugees and (b) documents, such as policy manuals and/or guidance documents that are attached, hyperlinked, or otherwise expressly incorporated in documents implementing either the Agency Memo or the preliminary injunction (id. at 11-12). Defendants oppose Plaintiffs' motion. (See Resp.) The court now considers Plaintiffs' motion to compel discovery.

Defendants argue that Plaintiffs failed to "meaningfully meet and confer with Defendants." (Resp. at 3 (underlining and capitalization omitted).) See Local Rule W.D. Wash. LCR 37(a)(1) (requiring the moving party in a discovery dispute to certify that "the movant has in good faith conferred or attempted to confer with the . . . party failing to make disclosure or discovery in an effort to resolve the dispute without court action."). The court rejects Defendants' argument. As is described above, the parties were in regular contact throughout the discovery period, and the Plaintiffs conducted specific meet and confer telephonic conferences on August 10, 2018 and October 16, 2018. See supra § II.B; (see also Keaney Decl. ¶ 62.)

III. ANALYSIS

A. The Standard for Obtaining Discovery

Federal Rule of Civil Procedure 26 governs the standard for producing discovery. See Fed. R. Civ. P. 26; Ciuffitelli v. Deloitte & Touche LLP, No. 3:16-CV-0580-AC, 2016 WL 6963039, at *3 (D. Or. Nov. 28, 2016). In general, "[p]arties may obtain discovery regarding any nonprivileged matter that is relevant to any party's claim or defense and proportional to the needs of the case, considering the importance of the issues at stake in the action, the amount in controversy, the parties' relative access to relevant information, the parties' resources, the importance of the discovery in resolving the issues, and whether the burden or expense of the proposed discovery outweighs its likely benefit." Fed. R. Civ. P. 26(b)(1). "The 2015 amendments to Rule 26(b)(1) emphasize the need to impose 'reasonable limits on discovery through increased reliance on the common-sense concept of proportionality.'" Roberts v. Clark Cty. Sch. Dist., 312 F.R.D. 594, 603 (D. Nev. 2016) (internal citation omitted). Information need not be admissible to be discoverable. Id. The court has broad discretion in determining relevancy for discovery purposes. Surfvivor Media, Inc. v. Survivor Prods., 406 F.3d 625, 635 (9th Cir. 2005). As noted above, in the present context, relevancy is limited to jurisdictional discovery on mootness. (See 7/27/18 Order at 28-29.)

Under Federal Rule of Civil Procedure 37, "a party seeking discovery may move for an order compelling an answer, designation, production, or inspection." Fed. R. Civ. P. 37(a)(3)(B). The court may order a party to provide further responses to an "evasive or incomplete disclosure, answer, or response." See Fed. R. Civ. P. 37(a)(4). Although the party seeking to compel discovery has the burden of establishing that its requests are relevant, see Fed. R. Civ. P. 26(b)(1), "[t]he party who resists discovery has the burden to show that discovery should not be allowed, and has the burden of clarifying, explaining, and supporting its objections" with competent evidence, see Blemaster v. Sabo, No. 2:16-CV-04557 JWS, 2017 WL 4843241, at *1 (D. Ariz. Oct. 25, 2017) (quoting DIRECTV, Inc. v. Trone, 209 F.R.D. 455, 458 (C.D. Cal. 2002)); see also Blankenship v. Hearst Corp., 519 F.2d 418, 429 (9th Cir. 1975) (holding that the defendants did not meet their burden of showing in their motion for a protective order why discovery was denied). The party resisting discovery on grounds of privilege also bears the burden to show that the requested discovery is so protected. See Everest Indem. Ins. Co. v. QBE Ins. Corp., 980 F. Supp. 2d 1273, 1277 (W.D. Wash. 2013). // // //

B. The Fourth ROGs

Defendants object to Plaintiffs' Fourth ROGs on grounds of (1) undue burden, and (2) timeliness. (Resp. at 5-6.) As discussed below, the court declines to sustain either objection and grants Plaintiffs' motion to compel with respect to the Fourth ROGs.

1. Burden

Defendants assert that responding to Plaintiffs' Fourth ROGs would impose an undue burden. (Resp. at 5-6.) Although Defendants describe the time spent responding to past discovery requests (see Gauger Decl. ¶¶ 4, 8-9), they do not estimate the time needed to respond to the additional six (6) questions contained in Plaintiffs' Fourth ROGs (see generally id.). Instead, Defendants perfunctorily recite that responding to the Fourth ROGs "would impose significant burdens on [the Refugee Processing Center ("RPC")]." (Id. ¶ 9.). Without some indication of why responding to the specific discovery requests at issue here is unduly burdensome, the court cannot sustain Defendants' objection.

Further, the court is unconvinced that Plaintiffs' prior discovery requests imposed an undue burden on Defendants. For example, Defendants complain that the Office of the Legal Advisor, Human Rights and Refugees ("L/HRR") presently "has the primary responsibility within [DOS] for overseeing the search and production tasks to respond to discovery requests" and "has only one attorney assigned to handle legal matters relating to the USRAP and who was available to perform the review of the documents and data that have been produced to date." (Id. ¶¶ 3, 6.) Defendants also state that "[t]here are no other personnel in PRM/A specifically assigned to assist in the search and production, and [they] currently lack capacity to assign dedicated personnel to this work" and are "already below regular staffing levels due to [DOS's] hiring freeze." (Id.) Nevertheless, Defendants state that they assigned a team of RPC contractors to complete the work and that this team, collectively, spent 228 hours gathering the data responsive to Plaintiffs' requests. (Id. ¶ 4.) Defendants never state how many people comprised the team of RPC contractors; but in any event, a total of 228 hours to respond to jurisdictional discovery requests does not seem unduly burdensome to the court or out of proportion to the needs of this complex case. See Fed. R. Civ. P. 26(b)(1).

Further, if there are insufficient legal resources within L/HRR and PRM/A to handle the discovery requests precipitated by President Trump's various executive orders on immigration and refugees, Defendants do not explain why they could not assign additional resources from the United States Department of Justice ("DOJ") to assist in responding to discovery. Assisting a client in reviewing documents for responsiveness and privilege is a typical responsibility performed by legal counsel in all types of litigation before this court. DOJ refers to itself as "the world's largest law office, employing more than 10,000 attorneys nationwide." See United States Department of Justice, Office of Attorney Recruitment, https://www.justice.gov/oarm (last visited Dec. 17, 2018). Given these vast DOJ resources, the court is confident that Defendants can handle an additional six interrogatories without experiencing undue burden and, therefore, declines to sustain Defendants' objection on this ground.

Finally, the court agrees with Plaintiffs that Defendants cannot avoid their duties to respond to Plaintiffs' otherwise reasonable and targeted discovery requests by failing to dedicate sufficient resources. (See Reply (Dkt. # 170) at 3.) "In order to adequately respond to discovery in civil litigation all parties incur unwanted burdens and costs." Costantino v. City of Atl. City, 152 F. Supp. 3d 311, 328 (D.N.J. 2015) (explaining that a governmental defendant "cannot shirk its responsibilities by failing to dedicate sufficient resources to respond to appropriate and necessary discovery"). What Defendants describe is not "undue" burden, but the ordinary burdens that civil litigants must bear. As noted above, given DOJ's resources, Defendants are in a better positon than most to muster the necessary resources for the limited discovery at issue here. For all of the foregoing reasons, the court rejects Defendants' undue burden objection with respect to Plaintiffs' Fourth ROGs.

2. Timeliness

Defendants also object that Plaintiffs served their Fourth ROGs too late because Plaintiffs served them only 20 days prior to the close of the discovery period. (Resp. at 6.) Defendants are correct that, to be timely, courts typically require a party to serve interrogatories or requests for production at least 30 days prior to the discovery cutoff. (See Resp. at 6 (citing Reed v. Morgan, No. 3:16-CV-05993-BHS-DWC, 2017 WL 4408076, at *1-2 (W.D. Wash. Oct. 4, 2017).) For example, the Morgan court, on which Defendants rely, denied the plaintiffs motion to compel because the defendants' responses would have been due 3 days after the discovery deadline had passed. 2017 WL 4408076, at *2. Notably, however, the Morgan court still concluded that "the interests of justice dictate that the parties should be allowed additional discovery." Id. (citing Oakes v. Halvorsen Marine Ltd., 179 F.R.D. 281, 283 (C.D. Cal. 1998) (stating that "the purpose of discovery is to remove surprise from trial preparation so the parties can obtain evidence necessary to evaluate and resolve their dispute")). Thus, the rule that discovery must be served so that a party is capable of responding within the discovery period "is not absolute." Bishop v. Potter, No. 2:08-cv-00726-RLH-GWF, 2010 WL 2775332, at *2 (D. Nev. July 14, 2010).

Indeed, Defendants complaints about timeliness ignore whether—as Plaintiffs assert—there is good cause to modify the scheduling order to accommodate Defendants' responses to the Fourth ROGs. (See Mot. at 9 (citing Wealth by Wealth, Inc. v. Ericson, No. C09-1444JLR, 2010 WL 11566111, at *3 (W.D. Wash. July 12, 2010).) In determining whether "good cause" exists under Federal Rule of Civil Procedure 16(b) to modify a case schedule, the court "primarily considers the diligence of the party seeking amendment." Johnson v. Mammoth Recreations, Inc., 975 F.2d 604, 609 (9th Cir. 1992). "Although the existence or degree of prejudice to the party opposing the modification might supply additional reasons to deny a motion, the focus of the inquiry is upon the moving party's reasons for seeking modification." Id. "If that party was not diligent, the inquiry should end." Id. Good cause exists when the deadline in the scheduling order "cannot reasonably be met despite the diligence of the party seeking the extension." Id.; see Noyes v. Kelly Servs., 488 F.3d 1163, 1174 (9th Cir. 2007). Ultimately, "[w]hat constitutes good cause . . . necessarily varies with the circumstances of each case." 6A Charles A. Wright, Arthur R. Miller & Mary Kay Kane, Federal Practice and Procedure: Civil § 1522.2 (2d ed. 1990).

The court is convinced, based on the record recited above, that Plaintiffs acted diligently here. See supra § II.B. They issued limited and targeted discovery and attempted in good faith to quickly adjust those requests based on objections articulated by Defendants. See id. Further, although the court does not find that Defendants acted in a dilatory manner, Defendants' response times consumed large portions of the 90-day discovery period. For example, although Defendants produced the bulk of their documents (786 pages) within 45 days of service of Plaintiffs' requests, Defendants did not complete their document production (adding an additional 22 pages) until 73 days following service. (Kearney Decl. ¶ 11.) Although the number of documents produced does not always reflect the time required to produce them, here, the total number—808 pages—is modest, suggesting that less rather than more time should have been required. In addition, Defendants also did not serve written responses to Plaintiffs' First ROGs until September 26, 2018—40 days after service. (Id. ¶ 28.) However, the response time typically required under the Rules, absent a stipulation of the parties or order of the court, is just 30 days. See Fed. R. Civ. P. 33(b)(2) ("The responding party must serve its answers and any objections within 30 days after being served with the interrogatories."). The court notes the timing of Defendants' responses not to criticize Defendants, but to highlight the fact that both sides have taken more time than the court anticipated to complete the jurisdictional discovery at issue. Plaintiffs needed to wait for Defendants' responses before they could assess if additional discovery would be required. Plaintiffs were not dilatory in either reviewing Defendants' responses or issuing follow-up discovery. See supra § II.B. Finally, Defendants fail to explain why extending the jurisdictional discovery cutoff to accommodate their responses will result in undue prejudice to them. (See Resp. at 6-7.) Thus, the court finds that there is good cause to extend the discovery cutoff with respect to Plaintiffs' Fourth ROGs, grants Plaintiffs' motion to compel, and orders Defendants to respond to Plaintiffs' Fourth ROGs within 45 days of the filing date of this order.

Although Defendants do not propose a timeline for completing additional discovery, they complain that the additional 35 days sought by Plaintiffs is too short. (See Gauger Decl. ¶ 9.) Accordingly, the court allows 45 days for Defendants to respond.

C. Depositions

Plaintiffs also seek an order compelling Defendants to produce two Rule 30(b)(6) deponents and to allow Plaintiffs to depose Ms. Higgins and Ms. Gauger. (Mot at 10.) Defendants object that these deposition requests are (1) unduly burdensome, and (2) "troublingly late." (Resp. at 5-7.) Again, as discussed below, the court declines to sustain either objection and grants Plaintiffs' motion to compel the requested depositions.

1. Burden

Defendants assert that the depositions requested by Plaintiffs are burdensome because they "effectively encompass all of their requested discovery." (Id. at 5.) They also object that taking the depositions of Ms. Higgins and Ms. Gauger would be duplicative of the requested Rule 30(b)(6) depositions. (Id.)

Defendants also object that "fact witness testimony is particularly inappropriate before any 30(b)(6) deposition." (Resp. at 5.) However, the Federal Rules of Civil Procedure are unambiguous on this point: Unless the parties so stipulate or the court orders otherwise, the "methods of discovery may be used in any sequence." Fed. R. Civ. P. 26(d)(3)(A).

A party may "by oral questions, depose any person" and may notice an entity—including a governmental agency—for deposition pursuant to Rule 30(b)(6). Fed. R. Civ. P. 30(a)(1), (b)(6). Both fact witness and Rule 30(b)(6) depositions are subject to the limitations of Rule 26(b)(2)(C), which provides that a court shall limit the frequency or extent of discovery that: (i) is unreasonably cumulative, duplicative, or burdensome; (ii) is dilatory; or (iii) fails a balancing test that weighs the burden or expense of the discovery sought against its benefit, in light of the specific facts of the case. See Fed. R. Civ. P. 26(b)(2)(C)(i)-(iii). District courts enjoy broad discretion to fashion discovery such that a proper balance between Rule 26's broad discovery mandates and appropriate restrictions on such discovery is achieved. See Laub v. U.S. Dep't of Interior, 342 F.3d 1080, 1093 (9th Cir. 2003).

First, the court rejects the notion that taking a Rule 30(b)(6) deposition is necessarily duplicative of a fact witness deposition even if the same person is being deposed in both instances. Rule 30(b)(6) expressly provides that "[t]his paragraph (6) does not preclude a deposition by any other procedure allowed by these rules." Fed. R. Civ. P. 30(b)(6). The deposition of an individual and the deposition of the same person as a representative of the organization are two distinct matters and can be utilized as distinct forms of evidence. See Taylor v. Shaw, No. 2:04CV01668LDGLRL, 2007 WL 710186, at *2 (D. Nev. Mar. 7, 2007) ("Rule 30 allows depositions of a witness in his individual capacity and in an organizational capacity because the depositions serve distinct purposes and impose different obligations."). For example, a fact witness is generally limited to his or her own personal knowledge, whereas a Rule 30(b)(6) deponent testifies on behalf of the organization. See Fed. R. Civ. P. 30(b)(6) ("The named organization must then designate one or more officers, directors, or managing agents, or designate other persons who consent to testify on its behalf . . . ."). Thus, Plaintiffs are entitled to seek both types of discovery from Defendants, and the court does not consider these forms of discovery "duplicative" even if they address similar or overlapping subject matters.

Further, the court does not consider a fact witness deposition to be generally duplicative of prior written discovery. Parties are ordinarily entitled to test interrogatory responses and document production through depositions—particularly where, as here, the party seeking discovery argues persuasively that the opposing party's responses to date have raised as many questions as they have answered. (See Mot. at 3-8); see also Taylor, 2007 WL 710186, at *3 (ruling that the defendant is entitled to take depositions and they are not cumulative where the plaintiff's responses to written discovery requests were inconsistent). Defendants have not demonstrated that the two fact witness depositions and the two Rule 30(b)(6) depositions that Plaintiffs seek are so burdensome, cumulative, or out of proportion to the needs of the case as to justify a denial of Plaintiffs' request for these depositions. See Fed. R. Civ. P. 26(b)(1). // // //

In response to Plaintiffs' arguments that Defendants' written discovery responses raise numerous and additional questions about Defendants' compliance with the court's preliminary injunction, Defendants submit three declarations in an effort to clarify their earlier responses. (See Ingraham Decl. (Dkt. # 169-3); Smith Decl. (Dkt. # 169-4); Ruppel Decl. (Dkt. # 169-5).) In the court's view, this simply reinforces Plaintiffs' need to conduct depositions to test and clarify Defendants' written responses. Depositions are a usual tool for expanding upon and clarifying written answers or testimony because the answering party must respond orally to questions that can be modified and refined as the deposition progresses and the answering party can also clarify answers and provide more detail as needed in real time.

2. Timeliness

Defendants also argue that Plaintiffs' requests for two fact witness depositions and two Rule 30(b)(6) depositions are untimely. (See Resp. at 6-7.) The court rejects this argument for the same reasons that it rejected Defendants' timeliness objections concerning Plaintiffs' Fourth ROGS. See supra § III.B.2.

Further, unlike the 30-day response time allowed for interrogatories and requests for production, which arguably rendered Plaintiffs' Fourth ROGs untimely, see Fed. R. Civ. P. 33(b)(2) (allowing 30 days for the responding party to serve its answers and objections to interrogatories), Fed. R. Civ. P. 32(b)(2)(A) (allowing 30 days for the answering party to respond in writing to requests for production), there is no definitive response time with respect to a deposition other than providing reasonable notice, see Fed. R. Civ. P. 30(b)(1) (requiring "reasonable written notice" for a deposition). Defendants have not stated that they were unable to reasonably produce the requested witnesses prior to the October 25, 2018, discovery cutoff. (See Resp. at 6-7.) Defendants only assert that the deposition requests were "troublingly late." (Id. at 6.) In fact, in Defendants' counsel's correspondence to Plaintiffs' counsel, Defendants' counsel stated that he "doubted that Defendants would be amenable to [Plaintiffs'] eleventh hour and expansive deposition requests." (Keaney Decl. ¶ 39, Ex. 33.) Yet, the "eleventh hour" of a discovery period is still within the discovery period, and there is no basis for denying // a discovery request simply because it is served toward the end of the designated period. Indeed, it is the court's experience that litigants are often quite productive in the "eleventh hour" of a discovery period. Accordingly, the court declines to sustain Defendants' timeliness objection to Plaintiffs' fact witness and Rule 30(b)(6) depositions. The court therefore grants Plaintiffs' motion to compel these depositions and orders Defendants to produce these deponents within 45 days of the filing date of this order.

The court does find Plaintiffs' request for two fact and two Rule 30(b)(6) deponents to be "expansive."

D. Law Enforcement Privilege

Defendants have redacted from the documents they produced any information that would tend to reveal the names of the SAO countries. (See Mot. at 10; Resp. at 7 ("Defendants redacted a handful of documents that contained SAO information.").) Defendants assert that this information is privileged as "law enforcement sensitive." (See Keaney Decl. ¶ 20, Ex. 3 (attaching privilege log).) Defendants maintain that if the government disclosed or publicly acknowledged this information it "could reasonably be expected to . . . cause harm to law enforcement and counterterrorism investigations," and "undermine [DOS's] security vetting efforts." (Latta Decl. (Dkt. # 169-2) ¶ 3.) Plaintiffs argue that Defendants' redactions "handicap[] Plaintiffs' ability to assess compliance with the preliminary injunction of a nationality-based suspension of refugee processing, by obscuring how particular refugees of those nationalities have been treated." (Mot. at 11 (italics in original).)

The parties dispute both the validity and applicability of this claimed privilege. (See id. at 10-11; Resp. at 8.) In the context of the preliminary injunction, the court did not need to decide the issue because Defendants acknowledged that "the court could 'rely on Plaintiffs' allegations [concerning the identity of the SAO countries] for purposes of addressing the issues'" presented there. (PI Order at 10-11 n.6.) The court need not decide the issue now either because Plaintiffs offered to accept the production of this material under "an appropriate protective order" (see Keaney Decl. ¶ 17, Ex. 27 at 5-6), and Defendants agreed to do so (see Resp. at 9; Resp., Ex. O (Dkt. # 169-15) at 3 ("Defendants have determined . . . that we will lift the SAO redactions, provided Plaintiffs agree to a protective order prohibiting the dissemination of this information in unredacted form.")).

The issue, nevertheless, remains before the court because Plaintiffs subsequently withdrew their prior offer stating that because they had already briefed the issue, they were now "content for the [c]ourt to rule on Defendants' claim of [law enforcement] privilege . . . ." (Resp., Ex. O at 1.) Plaintiffs also complain that the "attorneys' eyes only" protective order offered by Defendants is "overly strict." (Id.; see also Reply at 5 n.8.) Yet obtaining the SAO information under an "attorneys' eyes only" protective order should suffice if Plaintiffs' need for the information is as stated—to assess Defendants' compliance with a nationality-based suspension of refugee processing. (See Mot. at 11.) Accordingly, the court will hold Plaintiffs to their prior agreement. The court therefore grants Plaintiffs' motion to compel Defendants to produce the SAO information and orders Defendants to do so, but Defendants are only required to do so pursuant to a protective order as discussed herein. // //

E. Information Redacted as Nonresponsive

Defendants have redacted information as "nonresponsive" from documents, including: (1) refugee applicants' personal information, and (2) several policy manuals and/or guidance documents concerning the Agency Memo or preliminary injunction that are either attached to emails or otherwise expressly incorporated in documents but that Defendants did not deem to be "final" or "formal" manuals or guidance documents. (See Mot. at 11-12; Resp. at 9-10; Reply at 6.) Plaintiffs move to compel Defendants to produce these materials but are agreeable to placing any personally identifiable information under a protective order. (See Mot. at 11-12.) Defendants oppose the production of any of the redacted material. (Resp. at 9-10.)

District courts appear to be split on the issue of whether a party may unilaterally redact material that the party deems to be nonresponsive or irrelevant from an otherwise responsive document. See Bonnell v. Carnival Corp., No. 13-22265-CIV, 2014 WL 10979823, at *3 (S.D. Fla. Jan. 31, 2014). This court, however, agrees with those courts who generally disapprove of the practice. Redaction is generally an inappropriate tool for excluding information that a party considers to be irrelevant or nonresponsive from documents that are otherwise responsive to a discovery request. See Bartholomew v. Avalon Capital Grp., Inc., 278 F.R.D. 441, 451 (D. Minn. 2011) (citing In re Medeva Sec. Litig., No. 93-4376-KN AJWX, 1995 WL 943468, at *3 (C.D. Cal. May 30, 1995), David v. Alphin, No. 3:07cv11, 2010 WL 1404722, at *7-*8 (W.D.N.C. Mar. 30, 2010), and Evon v. Law Offices of Sidney Mickell, Civ. No. S-09-0760 JAM GGH, 2010 WL 455476, at *2 n.1 (E.D. Cal. Feb. 3, 2010)). It is a rare document that contains only relevant information; and irrelevant information within an otherwise relevant document may provide context necessary to understand the relevant information. See id. "[U]nilateral redactions are inappropriate if they seek not to protect sensitive or protected information, but merely to keep non-responsive information out of an adversary's hands. United States v. McGraw-Hill Companies, Inc., No. CV 13-0779-DOC JCGX, 2014 WL 8662657, at *4 (C.D. Cal. Sept. 25, 2014).

Further, Rule 34 concerns the discovery of "documents"—not of excerpts of documents or subsets of words within documents. See Fed. R. Civ. P. 34. Thus, courts generally view "documents" as relevant or irrelevant—not portions thereof—for purposes of Rule 34. "This is the only interpretation of [Rule] 34 that yields 'just, speedy, and inexpensive determination[s] of every action and proceeding.'" Bartholomew, 278 F.R.D. at 452 (quoting Fed. R. Civ. P. 1).

The court does not rule that a party may never redact a document on grounds of irrelevance, only that such redactions are not the generally accepted or best practice, and there is insufficient justification for departing from the norm here.

Further, the unilateral redaction of irrelevant or nonresponsive material from otherwise responsive documents "gives rise to suspicion that relevant material harmful to the producing party has been obscured" and "tends to make documents confusing or difficult to use." In re Medeva Sec. Litig., 1995 WL 943468, at *3. "Redaction is, after all, an alteration of potential evidence." Evon, 2010 WL 455476, at *2 n.1. Parties should not unilaterally decide what nonresponsive portions of a document are necessary for context and what portions are not. Needless to say, opposing parties are likely to view this determination differently. For these reasons, the practice is also likely to result, as it did here, in the litigation of collateral issues and the needless expenditure of resources. See In re Medeva Sec. Litig., 1995 WL 943468, at *3. These drawbacks outweigh the minimal harm that may result from disclosure of some irrelevant or nonresponsive material. See id. Moreover, except for the disclosure of certain refugee applicants' personal information, Defendants have not identified any prejudice that might result from the production of the redacted material here; and the privacy issue can easily be addressed by the entry of an appropriate protective order. Thus, the court concludes that "the better . . . approach is to not provide litigants with the carte blanche right to willy-nilly redact information from otherwise responsive documents in the absence of privilege, merely because the producing party concludes on its own that some words, phrases, or paragraphs are somehow not relevant." Bonnell, 2014 WL 10979823, at *4. Accordingly, the court grants Plaintiffs motion to compel the materials Defendants redacted on grounds of nonresponsiveness or irrelevance, but requires the entry of a protective order with respect to any redacted personal information of refugee applicants. // //

The court's ruling applies not only to the portions of documents that Defendants redacted based on nonresponsiveness or irrelevance, but also to the attachments to responsive documents that Defendants withheld on the same grounds. See Virco Mfg. Corp. v. Hertz Furniture Sys., No. CV 13-2205 JAK(JCX), 2014 WL 12591482, at *5 (C.D. Cal. Jan. 21, 2014) ("This Court agrees with those courts which have held that emails produced in discovery should be accompanied by their attachments or that the attachments should be produced along with information sufficient to enable a receiving party to identify the email(s) to which the attachment corresponds."). --------

IV. CONCLUSION

Based on the foregoing analysis, the court GRANTS in part and DENIES in part Plaintiffs' joint motion to compel discovery (Dkt. # 166). The court further ORDERS Defendants to produce the discovery described above and to permit Plaintiffs to conduct the depositions described above within 45 days of the filing date of this order.

Dated this 20th day of December, 2018.

/s/_________

JAMES L. ROBART

United States District Judge