6 UNITED STATES DISTRICT COURT 7 WESTERN DISTRICT OF WASHINGTON AT SEATTLE 8 SETONDJI VIRGILE NAHUM Case No.: 19-cv-01114-BJR 9 Plaintiff, 10 ORDER DENYING MOTION TO v. COMPEL 11 THE BOEING COMPANY, et al. 12 Defendants. 13
14 I. INTRODUCTION 15 Plaintiff Setonji Nahum (“Plaintiff”)1 brings this employment discrimination action against 16 The Boeing Company (“Boeing”) and one of its managers, Jeffrey Dillaman, (collectively, 17 “Defendants”) in which he asserts several employment-related causes of action. Currently before 18 the Court is Plaintiff’s motion to compel discovery, which Defendants oppose. Dkt. Nos. 70, 73. 19 Having reviewed the motion, opposition thereto, the relevant legal authority, and the record of the 20 case, the Court will deny the motion. The reasoning for the Court’s decision follows. 21 22 23
24 1 Plaintiff is pro se. 1 II. BACKGROUND 2 Plaintiff served Defendants with his first request for written discovery and production of 3 documents on October 1, 2019. Dkt. No. 70, Ex. A. Defendants responded to the discovery request 4 on March 27, 2020.2 Plaintiff alleges that Defendants’ document production was insufficient and,
5 as such, in mid-April 2020, the parties held a meet and confer conference to discuss Plaintiff’s 6 concerns regarding Defendants’ production.3 During this telephone conference, Plaintiff identified 7 additional materials that he wanted Defendants to produce.4 Defendants allege that Plaintiff’s 8 2 Defendants alleged that they produced the following documents in response Plaintiff’s discovery request: 9 • Plaintiff’s personnel file, including his application materials, training history, performance evaluation, and payroll records; 10 • Plaintiff’s labor relations file, including documents related to his union grievances of his corrective actions and communications with union representatives; • Boeing’s file on Plaintiff’s EEOC charge, including investigation materials, witness statements, and 11 submissions to the EEOC; • Boeing’s file on Plaintiff’s unemployment claim; 12 • Investigation files maintained by Boeing’s fact-finding investigators, including emails and substantive work product, relating to Plaintiff’s corrective action and discharge; 13 • Investigation files maintained by the Boeing’s EEO and Ethics departments regarding Plaintiff’s challenges to his corrective actions; • substantive work product, that Plaintiff himself submitted to the investigator to support his claims 14 that corrective action was unwarranted; • Documents regarding Plaintiff’s performance maintained by Plaintiff’s manager, Jeffrey Dillaman, 15 including emails and notes documenting concerns about Plaintiff’s performance, emails received from coworkers concerning Plaintiff, and communication with fact-finders and investigators; 16 • Documents regarding Plaintiff’s performance maintained by Plaintiff’s second-level manager, including organizational charts, emails and notes documenting concerns about Plaintiff’s performance, emails received from coworkers concerning Plaintiff, and communication with fact- 17 finders; • All SATs assigned to Plaintiff during his employment, including, but not limited to, those related to 18 his corrective actions; • All PPCR reports assigned to Plaintiff during his employment, including, but not limited to, those 19 related to his corrective actions; and • Relevant company policies. Dkt. No. 74 Declaration of Kathryn J. Ranieri at ¶¶ 6, 8 20 3 Defendants have their own concerns regarding Plaintiff’s response to their discovery requests but have not yet moved to compel his responses, but continue to attempt to resolve this issue without this Court’s intervention. 21 4 Defendant requested the following additional documents: • Documents related to his work stored on Boeing’s shared files; 22 • Bar charts and doors packages for control codes 304BM, 306, and 307; • Bar charts from the analyst who held Plaintiff’s position before him; • Governing protocols for PPCRs; 23 • Line of Balance data; • Correspondence/documents evidencing other employees saying that they refused to work with 24 Plaintiff; and 1 request for additional material was overbroad, unduly burdensome, and irrelevant; nevertheless, 2 Defendants agreed to “search[] for and collect[] [the] additional documents”. Dkt. No. 74, 3 Declaration of Kathryn J. Ranieri at ¶ 15. Thereafter, on June 11 and 16, 2020, Defendants 4 produced “all work files uploaded by Plaintiff to his team’s shared folders, all bar charts in the
5 shared folder from both Plaintiff and the preceding analyst in his role, Line of Balance files, PPCR 6 authoritative documents, and additional email correspondence regarding Plaintiff’s work product.” 7 Dkt. No. 73, (citing Ranieri Decl. at ¶ 21). Defendants allege that with this production, they have 8 produced all documentation responsive to Plaintiff’s discovery requests that is relevant to his 9 claims in this lawsuit. 10 Plaintiff disagrees. He claims that “[D]efendants ha[ve] not shown any desire to take [his] 11 request for discovery seriously. Instead the [D]efendants have been producing whatever [they] 12 wish[] to produce as opposed to providing clear answers to the discovery and actually sufficiently 13 satisfy the plaintiff’s request for discovery.” Dkt. No. 70 at 2-3. He complains that Defendants 14 have produced “disjointed email communication, non-genuine material, and multiple set[s] of
15 irrelevant materials.” Id. at 2. He also alleges that the “font and formatting” of the documents 16 produced indicate that Defendants “have been t[a]mpering with the evidence in this federal case.” 17 Id. at 4. Therefore, Plaintiff requests that this Court order Defendants to promptly comply with his 18 outstanding discovery requests. 19 III. STANDARD OF REVIEW 20 Federal Rule of Civil Procedure (“FRCP”) 37(a)(1) provides that in the event a party does 21 not respond to a discovery request the proponent of the discovery “may move for an order 22 compelling disclosure or discovery.” Fed. R. Civ. Pro. 37(a)(1); see also Lim v. Franciscan Health 23 • Documents related to an audit he performed as an independent contractor. 24 Dkt. No. 73 at 5. 1 Systems, 2006 WL 3544605, *1 (W.D. Wash. Dec. 8, 2006) (“Where the response to discovery is 2 unsatisfactory, the party seeking discovery may file a motion to compel discovery . . . .”). The 3 movant must certify that he has “in good faith conferred or attempted to confer with the person or 4 party failing to make disclosure or discovery in an effort to obtain it without court action.” Fed. R.
5 Civ. Pro. 37(a)(1). The movant bears the burden of informing the Court: “(1) which discovery 6 requests are the subject of his motion to compel, (2) which of the [] responses are disputed, (3) 7 why the responses are deficient, (4) the reasons [the] objections [if any] are without merit, and (5) 8 the relevance of the requested information to the prosecution of his action.” Hupp v. San Diego 9 County, 2014 WL 1404510, *2 (S.D. Cal. April 10, 2014) (citing Brooks v. Alameida, 2009 WL 10 331358, at *2 (E.D.Cal. Feb.10, 2009) (“Without knowing which responses plaintiff seeks to 11 compel or on what grounds, the court cannot grant plaintiff's motion.”)). 12 IV. DISCUSSION 13 Defendants object to Plaintiff’s motion to compel on two grounds. First, they charge that 14 the motion is procedurally deficient because Plaintiff failed to exhaust the meet and confer
15 requirement specified in Local Civil Rule 37(a)(1) (“LCR 37(a)(1)”) and this Court’s Standing 16 Order for Civil Cases (“Standing Order”). Second—as to the merits of the motion—Defendants 17 claim that they have fully complied with their discovery obligations and, indeed, produced material 18 far in excess of such obligations in order to work cooperatively with Plaintiff.
Free access — add to your briefcase to read the full text and ask questions with AI
6 UNITED STATES DISTRICT COURT 7 WESTERN DISTRICT OF WASHINGTON AT SEATTLE 8 SETONDJI VIRGILE NAHUM Case No.: 19-cv-01114-BJR 9 Plaintiff, 10 ORDER DENYING MOTION TO v. COMPEL 11 THE BOEING COMPANY, et al. 12 Defendants. 13
14 I. INTRODUCTION 15 Plaintiff Setonji Nahum (“Plaintiff”)1 brings this employment discrimination action against 16 The Boeing Company (“Boeing”) and one of its managers, Jeffrey Dillaman, (collectively, 17 “Defendants”) in which he asserts several employment-related causes of action. Currently before 18 the Court is Plaintiff’s motion to compel discovery, which Defendants oppose. Dkt. Nos. 70, 73. 19 Having reviewed the motion, opposition thereto, the relevant legal authority, and the record of the 20 case, the Court will deny the motion. The reasoning for the Court’s decision follows. 21 22 23
24 1 Plaintiff is pro se. 1 II. BACKGROUND 2 Plaintiff served Defendants with his first request for written discovery and production of 3 documents on October 1, 2019. Dkt. No. 70, Ex. A. Defendants responded to the discovery request 4 on March 27, 2020.2 Plaintiff alleges that Defendants’ document production was insufficient and,
5 as such, in mid-April 2020, the parties held a meet and confer conference to discuss Plaintiff’s 6 concerns regarding Defendants’ production.3 During this telephone conference, Plaintiff identified 7 additional materials that he wanted Defendants to produce.4 Defendants allege that Plaintiff’s 8 2 Defendants alleged that they produced the following documents in response Plaintiff’s discovery request: 9 • Plaintiff’s personnel file, including his application materials, training history, performance evaluation, and payroll records; 10 • Plaintiff’s labor relations file, including documents related to his union grievances of his corrective actions and communications with union representatives; • Boeing’s file on Plaintiff’s EEOC charge, including investigation materials, witness statements, and 11 submissions to the EEOC; • Boeing’s file on Plaintiff’s unemployment claim; 12 • Investigation files maintained by Boeing’s fact-finding investigators, including emails and substantive work product, relating to Plaintiff’s corrective action and discharge; 13 • Investigation files maintained by the Boeing’s EEO and Ethics departments regarding Plaintiff’s challenges to his corrective actions; • substantive work product, that Plaintiff himself submitted to the investigator to support his claims 14 that corrective action was unwarranted; • Documents regarding Plaintiff’s performance maintained by Plaintiff’s manager, Jeffrey Dillaman, 15 including emails and notes documenting concerns about Plaintiff’s performance, emails received from coworkers concerning Plaintiff, and communication with fact-finders and investigators; 16 • Documents regarding Plaintiff’s performance maintained by Plaintiff’s second-level manager, including organizational charts, emails and notes documenting concerns about Plaintiff’s performance, emails received from coworkers concerning Plaintiff, and communication with fact- 17 finders; • All SATs assigned to Plaintiff during his employment, including, but not limited to, those related to 18 his corrective actions; • All PPCR reports assigned to Plaintiff during his employment, including, but not limited to, those 19 related to his corrective actions; and • Relevant company policies. Dkt. No. 74 Declaration of Kathryn J. Ranieri at ¶¶ 6, 8 20 3 Defendants have their own concerns regarding Plaintiff’s response to their discovery requests but have not yet moved to compel his responses, but continue to attempt to resolve this issue without this Court’s intervention. 21 4 Defendant requested the following additional documents: • Documents related to his work stored on Boeing’s shared files; 22 • Bar charts and doors packages for control codes 304BM, 306, and 307; • Bar charts from the analyst who held Plaintiff’s position before him; • Governing protocols for PPCRs; 23 • Line of Balance data; • Correspondence/documents evidencing other employees saying that they refused to work with 24 Plaintiff; and 1 request for additional material was overbroad, unduly burdensome, and irrelevant; nevertheless, 2 Defendants agreed to “search[] for and collect[] [the] additional documents”. Dkt. No. 74, 3 Declaration of Kathryn J. Ranieri at ¶ 15. Thereafter, on June 11 and 16, 2020, Defendants 4 produced “all work files uploaded by Plaintiff to his team’s shared folders, all bar charts in the
5 shared folder from both Plaintiff and the preceding analyst in his role, Line of Balance files, PPCR 6 authoritative documents, and additional email correspondence regarding Plaintiff’s work product.” 7 Dkt. No. 73, (citing Ranieri Decl. at ¶ 21). Defendants allege that with this production, they have 8 produced all documentation responsive to Plaintiff’s discovery requests that is relevant to his 9 claims in this lawsuit. 10 Plaintiff disagrees. He claims that “[D]efendants ha[ve] not shown any desire to take [his] 11 request for discovery seriously. Instead the [D]efendants have been producing whatever [they] 12 wish[] to produce as opposed to providing clear answers to the discovery and actually sufficiently 13 satisfy the plaintiff’s request for discovery.” Dkt. No. 70 at 2-3. He complains that Defendants 14 have produced “disjointed email communication, non-genuine material, and multiple set[s] of
15 irrelevant materials.” Id. at 2. He also alleges that the “font and formatting” of the documents 16 produced indicate that Defendants “have been t[a]mpering with the evidence in this federal case.” 17 Id. at 4. Therefore, Plaintiff requests that this Court order Defendants to promptly comply with his 18 outstanding discovery requests. 19 III. STANDARD OF REVIEW 20 Federal Rule of Civil Procedure (“FRCP”) 37(a)(1) provides that in the event a party does 21 not respond to a discovery request the proponent of the discovery “may move for an order 22 compelling disclosure or discovery.” Fed. R. Civ. Pro. 37(a)(1); see also Lim v. Franciscan Health 23 • Documents related to an audit he performed as an independent contractor. 24 Dkt. No. 73 at 5. 1 Systems, 2006 WL 3544605, *1 (W.D. Wash. Dec. 8, 2006) (“Where the response to discovery is 2 unsatisfactory, the party seeking discovery may file a motion to compel discovery . . . .”). The 3 movant must certify that he has “in good faith conferred or attempted to confer with the person or 4 party failing to make disclosure or discovery in an effort to obtain it without court action.” Fed. R.
5 Civ. Pro. 37(a)(1). The movant bears the burden of informing the Court: “(1) which discovery 6 requests are the subject of his motion to compel, (2) which of the [] responses are disputed, (3) 7 why the responses are deficient, (4) the reasons [the] objections [if any] are without merit, and (5) 8 the relevance of the requested information to the prosecution of his action.” Hupp v. San Diego 9 County, 2014 WL 1404510, *2 (S.D. Cal. April 10, 2014) (citing Brooks v. Alameida, 2009 WL 10 331358, at *2 (E.D.Cal. Feb.10, 2009) (“Without knowing which responses plaintiff seeks to 11 compel or on what grounds, the court cannot grant plaintiff's motion.”)). 12 IV. DISCUSSION 13 Defendants object to Plaintiff’s motion to compel on two grounds. First, they charge that 14 the motion is procedurally deficient because Plaintiff failed to exhaust the meet and confer
15 requirement specified in Local Civil Rule 37(a)(1) (“LCR 37(a)(1)”) and this Court’s Standing 16 Order for Civil Cases (“Standing Order”). Second—as to the merits of the motion—Defendants 17 claim that they have fully complied with their discovery obligations and, indeed, produced material 18 far in excess of such obligations in order to work cooperatively with Plaintiff. The Court will 19 address each argument in turn. 20 A. Whether the Motion to Compel Is Procedurally Defective 21 Defendants urge this Court to deny the motion to compel as procedurally noncompliant 22 because Plaintiff failed to meaningfully exhaust the meet-and-confer requirements under LCR 23 37(a)(1). Defendants allege that the parties agreed to reconvene their meet-and-confer efforts after
24 1 Defendants’ latest document production on June 16, 2020 but, instead, Plaintiff filed the instant 2 motion. Defendants also note that Plaintiff filed the instant motion without first contacting the 3 Court to schedule a telephonic conference as is required by this Court’s Standing Order. See Dkt. 4 No. 32, p. 3 at III.
5 Plaintiff counters that he did meaningfully exhaust the meet-and-confer requirements under 6 LCR 37(a)(1) by meeting with Defendants’ counsel on three separate occasions to discuss his 7 concerns regarding Defendants’ production, but that such meetings did not resolve his concerns. 8 Plaintiff also argues that this Court’s requirement that parties schedule a telephone phone 9 conference with the Court prior to filing a motion to compel does not apply to the instant motion. 10 Dkt. No. 75 at 5. 11 The Court will dispose of the easiest argument first. Section III “Discovery Disputes” of 12 the Court’s Standing Order unequivocally states that in the event a discovery dispute arises and 13 “the parties are unable to reach an agreement on [the issue] after conferring, they shall arrange a 14 telephone hearing with the Court regarding the issue.” Dkt. No. 32, p. 3. The Standing Order
15 further instructs that an “opposed discovery motion[]” shall not be filed until the telephone hearing 16 has occurred. Id. Plaintiff failed to comply with these instructions; as such, the Court could 17 “summarily den[y] or stri[ke]” the motion. Id. However, given that Plaintiff is pro se, and the 18 need to move this case forward, the Court will address Plaintiff’s motion. In the future, the Court 19 expects Plaintiff to comply with the procedures set forth in the Standing Order. 20 As for Defendants’ claim that Plaintiff failed to comply with the meet and confer 21 requirement under LCR 37(a)(1), the Court disagrees. Both parties admit that they met at least 22 three times in an effort to resolve Plaintiff’s concerns about Defendants’ document production. 23 Indeed, these meeting resulted in the additional production of documents. The Court appreciates
24 1 the effort demonstrated by Defendants’ counsel to work cooperatively with Plaintiff (as evidenced 2 by the email correspondence cited in Defendants’ opposition to the instant motion) and agrees it 3 would have been more productive had Plaintiff continued to meet with counsel. Nevertheless, the 4 Court concludes that Plaintiff has sufficiently exhausted the meet-and-confer requirement under
5 LCR 37(a)(1) to move forward with the instant motion. 6 B. Whether Defendants Have Complied with Their Discovery Obligations 7 As stated above, Plaintiff bears the burden of informing the Court which discovery requests 8 are the subject of the motion to compel and why Defendants’ responses are insufficient. Hupp, 9 2014 WL 1404510, *2 (S.D. Cal. April 10, 2014); see also Dkt. No. 32, p. 3 at III Standing Order 10 (requiring that a motion to compel contain “verbatim recitations of the discovery request[s]” that 11 the movant believes have not been appropriately responded to by the producing party, as well as a 12 recitation of the “objection (if any)” to the requests). Without this information, the Court is placed 13 in the untenable position of having to simply guess what Plaintiff’s objections are to Defendants’ 14 production. Worse yet, Defendants are unable to adequately respond to Plaintiff’s objections.
15 Plaintiff provides none of the required information in his motion to compel. Plaintiff does 16 better in his reply brief where he sets forth for the first time the specific documents he claims 17 Defendants have refused to provide him. Specifically, he claims that Defendants have refused to 18 produce “his daily log of tasks and activities, specific logs of discriminative and harassment 19 occurrences, all communication and materials shared between Talx Uclm Services and the Boeing 20 company as it pertains to the plaintiff, all emails folders within the plaintiff’s Boeing outlook email 21 system, Audits and completed tasks and assignment data and possibly [a] copy of performance 22 evaluation of the plaintiff work on the 787 program while a contractor of the Boeing Company … 23 [.]” Dkt. No. 75 at 10. However, Plaintiff still fails to identify which specific discovery such
24 1 || documents would be responsive to, nor state what Defendants’ objection is to producing such 2 || documents. Furthermore, given that Plaintiff provides this detail for the first time in his reply brief, 3 || Defendants did not have a chance to respond. 4 However, Defendants’ opposition makes it clear that it has already provided “[d]Jocuments 5 related to [Plaintiffs] work stored on Boeing’s share files”, “[d]ocuments related to [the] audit 6 || [Plaintiff] performed as an independent contractor”, and “[i]nvestigation files maintained by 7 || Boeing’s EEO and Ethics departments regarding Plaintiffs challenges to his corrective actions, 8 || including all materials, such as substantive work product, that Plaintiff himself submitted to the 9 investigator to support his claim that corrective action was unwarranted”. See Dkt. No. 73 10 || generally. Defendants further clarify that they produced these documents in the “custodian files . 11 ||. . as they were kept by each custodian in their normal course of business, without reordering, 12 || dismantling, or deduplicating—and certainly without falsifying, fabricating, or tampering with 13 |}such documents.” Dkt. No. 73 at 12. Thus, it appears from the record that Defendants have 14 || complied with Plaintiff's discovery requests. Thus, it is clear to the Court that Defendants have 15 || complied with their discovery obligations. Plaintiff's motion to compel must be denied. 16 V. CONCLUSION 17 For the foregoing reasons, this Court HEREBY DENIES Plaintiff's motion to compel. Dkt. 18 || No. 70. If further discovery disputes arise in the future, the parties shall request a telephone hearing 19 || with the Court before filing a motion to compel. 20 Dated this 24th day of July 2020. 21 Autos eben, 22 BARBARA J. ROTHSTEIN UNITED STATES DISTRICT JUDGE 23