Shreves v. Frontier Rail Corporation

CourtDistrict Court, E.D. Washington
DecidedFebruary 21, 2020
Docket1:19-cv-03012
StatusUnknown

This text of Shreves v. Frontier Rail Corporation (Shreves v. Frontier Rail Corporation) is published on Counsel Stack Legal Research, covering District Court, E.D. Washington primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Shreves v. Frontier Rail Corporation, (E.D. Wash. 2020).

Opinion

1 U.S. FDILISETDR IINC TT HCEO URT EASTERN DISTRICT OF WASHINGTON

Feb 21, 2020 2 SEAN F. MCAVOY, CLERK 3 UNITED STATES DISTRICT COURT EASTERN DISTRICT OF WASHINGTON 4 JAKE SHREVES, No. 1:19-cv-03012-SMJ 5 Plaintiff, ORDER GRANTING MOTION 6 FOR PROTECTIVE ORDER v. 7 FRONTIER RAIL CORPORATION 8 and YAKIMA CENTRAL RAILWAY CORPORATION, 9 Defendants. 10 11

12 Before the Court is Defendants Frontier Rail Corporation and Yakima 13 Central Railway Corporation’s Motion for a Protective Order, ECF No. 33. Having 14 reviewed the record and the file in this matter, the Court is fully informed. For the 15 reasons set forth below, the Court grants Defendants’ motion and incorporates the 16 proposed protective order with limited exception. 17 BACKGROUND 18 Plaintiff brought this action under the Federal Employer’s Liability Act 19 (FELA) to recover for injuries he sustained after allegedly falling into a hole near 20 railroad tracks while he alleges he was acting as an employee of Defendants. See 1 ECF No. 10 at 3–7. Plaintiff also brought claims under the Federal Railroad Safety 2 Act (FRSA) alleging he was terminated in retaliation for reporting his workplace

3 injury and hazardous workplace conditions. See generally ECF No. 10. 4 The parties have begun to engage in discovery and propounded requests for 5 production of documents. See, e.g., ECF No. 37-4. Defendants represent they have

6 sought discovery regarding Plaintiff’s medical history, including requests for 7 production of medical records and subpoenas to Plaintiff’s medical providers. ECF 8 No. 33 at 3–4. Plaintiff sought production of several categories of documents, 9 including Defendants’ “corporate structure and ownership” and “year-end

10 profit/loss statement[s]” as well as “Plaintiff’s entire, unredacted, personnel file,” 11 and “each and every document and communication . . . between [the Occupational 12 Safety and Health Administration (“OSHA”)] and/or the Department of Labor and

13 [Defendants or defense] counsel in connection with Plaintiff’s OSHA Complaint 14 under the FRSA.” See ECF No. 37-5. 15 On November 11, 2019, defense counsel emailed Defendants’ discovery 16 responses to Plaintiff’s counsel. ECF No. 34-1 at 7. Defense counsel also attached

17 a proposed stipulated protective order intended to govern the production of 18 confidential information in discovery. Id.; see also ECF No. 33-1 (proposed 19 protective order). Four days later, Plaintiff’s counsel responded. Id. at 6. Plaintiff’s

20 counsel declined to stipulate to the proposed protective order because Defendants 1 failed to provide justification for it. Id. Plaintiff’s counsel also described 2 Defendants’ discovery responses as “ridiculous” and wrote that if defense counsel

3 was “confused, or unsure how to comply with the federal rules, please let me know 4 and I will be happy to provide you with some guidance.” Id. at 7. 5 Several days later, defense counsel responded that a protective order was

6 necessary to protect “confidential business information” as well as information 7 about individuals not party to the litigation. Id. at 5. Defense counsel also made 8 clear the proposed protective order applied equally to confidential documents 9 produced by Plaintiff, namely Plaintiff’s medical records. Id. Plaintiff’s counsel

10 replied twenty minutes later, again declining to stipulate to the protective order, and 11 reiterating Plaintiff’s position that Defendant’s discovery responses were “full of 12 improper and unsubstantiated boilerplate objections.” Id. at 4.

13 The next day, defense counsel responded that he hoped to reach agreement 14 to avoid unnecessary motions practice and to protect against “dissemination of 15 confidential business information and personal information.” Id. at 3. Plaintiff’s 16 counsel replied:

17 // 18 // 19 //

20 // 1 So here’s how this actually works. As the party seeking a protective order, the burden is yours to demonstrate that one is necessary. That 2 requires you to specify what exactly you feel needs to be protected. So for example, you literally have to identify whatever the document is, 3 what the document contains that you think makes it subject to a protect [sic] order, and why there would be harm to your client in the absence 4 of a protective order. You are trying to do this in reverse and you simply are not going to get agreement from us by making vague references to 5 confidential business information and personal information.

6 Quit screwing around and wasting everyone’s time. Fix your discovery responses to reflect the fact that you all have law degrees and a 7 rudimentary understanding of the [Federal Rules of Civil Procedure]. And if you manage to make some actual showing of a need for a 8 protective order we can discuss then. But the time for you to do so is quickly running out because we are ready to file our motion to compel. 9

10 Id. at 3. 11 Defense counsel responded and once again stated Defendant’s desire to reach 12 agreement without the Court’s involvement. Id. at 2. Plaintiff’s counsel responded: 13 “You have not identified anything that needs to be protected. Please stop emailing 14 on this subject.” Id. The parties exchanged a similar pair of emails but failed to 15 reach a solution. Id. at 1. 16 On November 22, 2019, Defendant moved for a protective order. See ECF 17 No. 33. Defendants represent one is needed because the employment relationship 18 between Plaintiff and Defendants is disputed and will necessitate discovery of 19 confidential business information. Id. at 7. Defendants also contend discovery will 20 include private information of current and past employees who are not party to the 1 litigation, as well as Plaintiff’s private health records. Id. at 8. 2 Plaintiff argues a protective order is unnecessary because Defendants have

3 not identified any information warranting protection and because their discovery 4 responses include “boilerplate objections.” ECF No. 36 at 2. Plaintiff also argues 5 Defendants failed to engage in a meaningful “meet-and-confer” before moving for

6 a protective order. Id. at 3–5. As such, Plaintiff requests an award of fees and costs 7 incurred in briefing his response to Defendants’ motion, contending Defendants’ 8 conduct is “at the height of bad faith.” Id. at 10. 9 LEGAL STANDARD

10 Under Federal Rule of Civil Procedure 26(b)(1), “[p]arties may obtain 11 discovery regarding any nonprivileged matter that is relevant to any party’s claim 12 or defense.” This is a liberal standard, and information “need not be admissible in

13 evidence to be discoverable.” Id. But the right to discover relevant information is 14 neither absolute nor immune from restriction. Accordingly, “[t]he court may, for 15 good cause, issue an order to protect a party or person from annoyance, 16 embarrassment, oppression, or undue burden or expense,” including by prescribing

17 the terms under which discovery is provided. Fed. R. Civ. P. 26(c)(1). 18 The party seeking a protective order “bears the burden of showing specific 19 prejudice or harm will result if no protective order is granted. Phillips ex rel. Estates

20 of Byrd v. Gen. Motors Corp., 307 F.3d 1206, 1210–11 (9th Cir. 2002) ((citing 1 Beckman Indus., Inc. v. Intern. Ins. Co., 966 F.2d 470, 476 (9th Cir. 1992)).

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

Related

Cite This Page — Counsel Stack

Bluebook (online)
Shreves v. Frontier Rail Corporation, Counsel Stack Legal Research, https://law.counselstack.com/opinion/shreves-v-frontier-rail-corporation-waed-2020.