Lusk v. Five Guys Enterprises LLC ( 2022 )


Menu:
  • 1 2 3 4 UNITED STATES DISTRICT COURT 5 EASTERN DISTRICT OF CALIFORNIA 6 7 JEREMY R. LUSK, CASE NO. 1:17-cv-00762-AWI-EPG 8 Plaintiff, ORDER ON PLAINTIFF’S THIRD- 9 v. AMENDED MOTION FOR PRELIMINARY APPROVAL 10 FIVE GUYS ENTERPRISES LLC; AND ENCORE FGBF, LLC, 11 (Doc. No. 75) Defendants. 12 13 14 In this class action lawsuit, Jeremy Lusk is suing Five Guys Enterprises LLC and Encore 15 FGBF, LLC, on grounds that they violated federal and California credit/consumer reporting laws, 16 California wage-and-hour laws, and California unfair competition law. Although the parties have 17 reached a proposed class settlement, the Court has denied Lusk’s first three motions under Federal 18 Rule of Civil Procedure 23(e) for preliminary approval of the settlement and conditional 19 certification of the putative class. Lusk now moves a fourth time for such relief. For the reasons 20 discussed below, the Court will deny this motion. 21 22 BACKGROUND 23 Lusk filed his lawsuit in state court on May 2, 2017, and Defendants removed the action. 24 Thereafter, Lusk filed a first-amended complaint, wherein he pleaded the following twelve class 25 claims: (1) failure to make a proper disclosure, in violation of the federal Fair Credit Reporting 26 Act, 15 U.S.C. § 1681b(b)(2)(A); (2) failure to provide a proper summary of rights, in violation of 27 the Fair Credit Reporting Act, 15 U.S.C. §§ 1681d(a)(1) and 1681g(c); (3) failure to make a 28 proper disclosure, in violation of California’s Investigative Consumer Reporting Agencies Act, 1 Cal. Civ. Code § 1786.16(a)(2)(B); (4) failure to make a proper disclosure, in violation of 2 California’s Consumer Credit Reporting Agencies Act, Cal. Civ. Code § 1785.20.5(a); (5) failure 3 to provide meal periods or compensation in lieu thereof, in violation of Cal. Labor Code §§ 226.7, 4 512, and 1198, and California Industrial Welfare Commission Wage Order 5-2001 (“Wage Order 5 5”); (6) failure to provide rest periods or compensation in lieu thereof, in violation of Cal. Labor 6 Code §§ 226.7 and 1198, and Wage Order 5; (7) failure to pay earned wages, including overtime 7 wages, in violation of Cal. Labor Code §§ 204, 223, 510, 1194, 1197, and 1198, and Wage Order 8 5; (8) failure to reimburse for necessary gas and mileage expenditures, in violation of Cal. Labor 9 Code § 2802(a); (9) failure to provide accurate itemized wage statements, in violation of Cal. 10 Labor Code § 226; (10) failure to pay separation wages, in violation of Cal. Labor Code §§ 201– 11 203; (11) violations of California’s unfair competition law (“UCL”), Cal. Bus. & Prof. Code 12 § 17200 et seq.; and (12) entitlement to civil penalties under California’s Private Attorney General 13 Act (“PAGA”), Cal. Lab. Code § 2698 et seq. Doc. No. 13 (“FAC”). 14 After conducting some discovery, the parties participated in mediation and reached a 15 proposed agreement for a class-wide settlement. Doc. No. 29. Lusk has since moved three times 16 for preliminarily approval of that proposal and conditional certification of the putative class, with 17 the Court denying each motion. Doc. Nos. 36, 43, 52, 55, 61, 66. Lusk now moves for the same 18 relief for a fourth time. Doc. No. 75 (“Motion”).1 With his latest motion, Lusk submits a 19 supporting declaration from counsel, which itself comes with attached copies of the proposed class 20 settlement, class notice, and class member claim form. Doc. No. 76 (“Setareh Decl.”); Doc. No. 21 76-1.2 For the first time, Defendants have submitted a statement of non-opposition and 22 supplemental briefing on Lusk’s motion, along with a declaration from counsel. Doc. No. 78; 23 Doc. No. 78-1 (“Woo Decl.”). 24 25 26 1 In this order, citations to specific page numbers of Document No. 75 will refer to the pdf pagination of that document, and not the pagination used in the motion itself. 27 2 The settlement, class notice, and claim form are all found at the same docket number. Doc. No. 76-1 at 1–25 28 (“Proposed Settlement”); 27–32 (“Settlement Notice”); 34–35 (“Claim Form”). Lusk has also separately submitted a 1 LEGAL STANDARD 2 Federal Rule of Civil Procedure 23(e) requires judicial review and approval of any class 3 settlement. This process generally involves three stages. In the first, the parties move for 4 “preliminary approval” of the proposed settlement and, if necessary, “conditional certification” of 5 the class. 4 William B. Rubenstein, Newberg on Class Actions § 13:16 (5th ed.). If the court 6 grants this threshold relief, the second and third stages require (1) the provision of notice to the 7 class members, along with an opportunity for them to object to or opt out of the proposed 8 settlement, and (2) a “final approval” determination (and actual class certification, if necessary) 9 following a fairness hearing. Id. 10 To secure preliminary approval and condition certification, the parties must provide 11 sufficient information for the court to determine that it “will likely be able to” grant final approval 12 of the settlement under Rule 23(e)(2) and certify the class for a judgment on the settlement. Fed. 13 R. Civ. P. 23(e)(1)(B). As to the first determination, Rule 23(e)(2) states that a binding class 14 settlement may be approved only on finding that it is “fair, reasonable, and adequate.” Fed. R. 15 Civ. P. 23(e)(2). As to the second determination, a class may be certified if it meets the four 16 prerequisites under Rule 23(a) and at least one of the three categories of class actions under Rule 17 23(b). Fed. R. Civ. P. 23(a)–(b). 18 The court’s role in the class settlement process is an important one, as “the parties that are 19 present and settling the case—class counsel, the class representatives, and the defendants—are 20 proposing to compromise the rights of absent class members.” Newberg on Class Actions 21 § 13:40. To ensure the interests of the absent class members are properly safeguarded, the “judge 22 must adopt the role of a skeptical client and critically examine the class certification elements, the 23 proposed settlement terms, and procedures for implementation.” Id. (quoting Manual for Complex 24 Litigation § 21.61 (4th ed.)). 25 26 DISCUSSION 27 The Court will deny Lusk’s latest motion because, once again, he has not provided 28 sufficient information showing that the proposed settlement is likely to be approved as “fair, 1 reasonable, and adequate” upon certification of the class under Rule 23. 2 3 A. Preliminary Approval 4 As noted above, at the preliminary approval stage, the court need only determine that the 5 proposed settlement is “likely” to be finally approved under Rule 23(e)(2). Rule 23(e)(2) itself 6 provides that a court may approve a class-binding settlement only on finding that the settlement is 7 “fair, reasonable, and adequate.” Fed. R. Civ. P. 23(e)(2). Before making such a finding, courts 8 must consider whether: (1) the class representative and counsel have adequately represented the 9 class; (2) the proposal was negotiated at arm’s length; (3) the relief provided for the class is 10 adequate in light of the costs, risks, and delay of trial and appeal; the effectiveness of any 11 proposed method of distributing relief to the class, including the method of processing class- 12 member claims; the terms of any proposed award of attorney’s fees, including timing of payment; 13 and any agreement made in connection with the proposal; and (4) the proposal treats class 14 members equitably relative to each other. Id.; see also In re Bluetooth Headset Prods. Liab. Litig., 15 654 F.3d 935, 946 (9th Cir. 2011) (quoted source omitted) (enumerating additional non-exhaustive 16 factors that are to be considered for purposes of granting final approval of a class settlement). 17 While Rule 23(e) does not mandate that courts consider these same factors for purposes of 18 determining whether preliminary approval is warranted, doing so often proves useful given the 19 role these factors play in final approval determinations. The court may also consider any other 20 topic that it regards as pertinent to determining whether the proposed settlement is fair, reasonable, 21 and adequate. See Fed. R. Civ. P. 23(e)(2) advisory committee’s note to 2018 amendment. 22 Naturally, the showing of fairness of a proposal will vary from case to case. Bluetooth Headset 23 Prods. Liab. Litig., 654 F.3d at 946. Where a settlement has been negotiated before certification, 24 however, there exists “an even greater potential for a breach of fiduciary duty owed the class 25 during settlement,” which means “such agreements must withstand an even higher level of 26 scrutiny for evidence of collusion or other conflicts of interest than is ordinarily required under 27 Rule 23(e) before securing the court’s approval as fair.” Id. 28 In its order denying Lusk’s third motion, the Court raised numerous concerns it had 1 regarding the proposed settlement. Many of these have since been adequately addressed by the 2 parties and warrant no extended discussion here.3 Because others have not, however, the Court 3 must again address lingering issues regarding the adequacy of class relief and the treatment of 4 putative class members. 5 6 1. Adequacy of Class Relief 7 The relief obtained by the class is often described as the most important part of a class 8 settlement. Carlin v. DairyAmerica, Inc., 380 F. Supp. 3d 998, 1011 (E.D. Cal. 2019). To 9 determine whether proposed relief is fair and reasonable, the court compares the amount that will 10 be recovered with the estimated value of the class claims if they were to be successfully litigated. 11 Id. (cited source omitted). As part of this comparison, the court must gauge the relative strength 12 of the plaintiff’s case as “[e]ven a fractional recovery of the possible maximum recovery amount 13 may be fair and adequate in light of the uncertainties of trial and difficulties in proving the case.” 14 Millan v. Cascade Water Servs., Inc., 310 F.R.D. 593, 611 (E.D. Cal. 2015) (collecting cases 15 approving settlements that were assumed to be fractions of the maximum potential recovery); see 16 also In re Mego Fin. Corp. Sec. Litig., 213 F.3d 454, 459 (9th Cir. 2000) (“It is well-settled law 17 that a cash settlement amounting to only a fraction of the potential recovery does not per se render 18 the settlement inadequate or unfair.” (quoted source omitted)). 19 20 3 To make a record, the Court recognizes that Lusk has adequately addressed both the risks attendant to the class 21 claims based on credit reporting statutes and unpaid wages (and assigned nominal or zero value to these claims), and the calculated number of meal and rest period violations in light of permissible recovery under Labor Code § 226.7 for 22 such claims. The parties have also revised the Settlement Notice and the Claim Form to include the credit reporting statutes amongst the extended list of released claims. Doc. No. 76-1 at 29, 35. And Lusk has submitted evidence 23 showing that the proposed settlement, with its latest revisions, was submitted to the California Labor and Workforce Development Agency for purposes of the PAGA claim. Setareh Decl., ¶ 34; Doc. No. 76-2. Finally, as to that claim, 24 the Court remains unconvinced by Lusk’s citation to Labor Code § 2699(e)(2)—and the authority it bestows on courts to discretionarily decrease unjust and oppressive PAGA awards—as justification for his substantial reduction of the 25 PAGA claim from a (newly calculated) value of $5,144,450 to $100,000 in the proposed settlement. Lusk’s citation to Cotter v. Lyft, Inc., 193 F. Supp. 3d 1030, 1037 (N.D. Cal. 2016), is also inapt, in so far as the court there approved 26 of a (less) drastic reduction of a PAGA claim while citing § 2699(e)(2) because the case was premised on an employee-independent contractor question for which there was “no straight answer” under California law. Lusk does 27 not draw this case parallel to that aspect of Cotter, and the Court finds no basis for him to have even tried. All that said, the Court finds that the math proposed here will suffice given other case law approving small PAGA awards 28 within a much larger class settlement. See Attia v. Neiman Marcus Grp., Inc., No. 8:16-cv-00504-DOC (FFM), 2019 1 a. The UCL Claim 2 In past motions, Lusk has not addressed the value and risks of the UCL claim. Doc. No. 3 43 at 13; Doc. No. 66 at 12. In his latest motion, Lusk takes steps to solve this continuing 4 problem. Motion at 38–39. Namely, he explains that, as pleaded, the UCL claim is entirely 5 derivative of some of the Labor Code claims, which in turn means that it carries all the risks that 6 attach to those underlying allegations. FAC, ¶¶ 173–174 (incorporating meal period, rest period, 7 unpaid wages, and unreimbursed expenses allegations for purposes of the UCL claim). The Court 8 credits this explanation, but still finds no information within Lusk’s greater potential recovery 9 analysis regarding the estimated value of the UCL claim. Motion at 24–26. Without this 10 information, the Court is left to surmise that the claim is worthless. This is exactly where the 11 Court was with Lusk’s last motion as well. In denying that motion, the Court informed Lusk that 12 if this claim is in fact entirely without merit, he needs to explain why that is the case and why the 13 Court should approve of the proposed settlement’s broad release of UCL claims for nothing in 14 return. Doc. No. 66 at 12. Lusk can add to that task an explanation for why the UCL claim is 15 considered worthless when it is based entirely on the same Labor Code allegations that populate 16 claims he estimates are collectively worth over $4.5 million. See also Cal. Bus. & Prof. Code 17 § 17205 (“Unless otherwise expressly provided, the remedies or penalties provided by this chapter 18 are cumulative to each other and to the remedies or penalties available under all other laws of this 19 state.”). 20 21 b. Class period 22 The Court previously expressed concern with the parties’ proposal to define the applicable 23 class period as “the period of time from August 22, 2013 through the date of Preliminary Approval 24 of the Settlement.” Doc. No. 66 at 14–16. As the Court explained, this open-ended class period 25 threatened to both undervalue the class claims and release other claims that were being assigned 26 no value in the proposed settlement. Id. The parties have responded to this concern by newly 27 defining the applicable class period as “the period of time from August 22, 2013 through October 28 19, 2020.” Proposed Settlement, ¶ 4. 1 This revision cures the problem with an open-ended class period. But the Court is 2 unconvinced that the parties have used the correct end date. Lusk justifies that choice by noting 3 that the Court denied his second motion for preliminary approval on October 19, 2020. Motion at 4 16. Yet, his successive motions suggest that the value of the class claims has remained largely 5 unchanged since the parties reached their settlement agreement on October 12, 2018. Compare 6 Doc. No. 36 at 20, with Doc. No. 52 at 18–19, and Motion at 24–26. In other words, the Court’s 7 October 19, 2020 order seemingly has nothing to do with Lusk’s valuation of the claims. Like 8 before, the Court suspects that the failure to account for this two-year span represents an 9 undervaluation of the claims. And as the Court previously explained, undervaluing the claims in 10 this fashion also comes with a gratuitous release of potential claims that could have been raised to 11 secure the recovery that is being overlooked here.4 12 13 2. Equitable Treatment of Class Members 14 Rule 23(e) requires examination of whether a proposed settlement “treats class members 15 equitably relative to each other.” Fed. R. Civ. P. 23(e)(2)(D). To consider this factor, the court 16 assesses whether the proposed settlement “improperly grant[s] preferential treatment to class 17 representatives or segments of the class.” Taafua v. Quantum Glob. Techs., LLC, No. 18-cv- 18 06602-VKD, 2021 WL 579862, at *7 (N.D. Cal. Feb. 16, 2021) (quoted source omitted). “Matters 19 of concern could include whether the apportionment of relief among class members takes 20 appropriate account of differences among their claims, and whether the scope of the release may 21 affect class members in different ways that bear on the apportionment of relief.” Fed. R. Civ. P. 22 23(e)(2)(D) advisory committee’s note to 2018 amendment. 23 In denying Lusk’s third motion, the Court explained that the proposed settlement was not 24 equitably treating class members because settlement shares failed to reflect apparent distinctions 25 26 4 Adding confusion, Lusk indicates in his motion that if October 19, 2020, is used as the end date of the class period, 27 the putative class expands from 2,206 to approximately 3,629 class members. Motion at 14 n.1. Despite acknowledging this relatively massive expansion of the putative class, Lusk continues to calculate the estimated value 28 of the class claims using the lower figure. Motion at 24–26. This itself leads to the claims being undervalued and the 1 amongst the class members based on the class claims. Doc. No. 66 at 17. As one example, the 2 Court highlighted the proposal to equally split compensation for the separation wages claim across 3 the entire putative class despite more than 40% of the class not having had a termination event 4 during the class period that would entitle them to relief under Labor Code § 203. The parties 5 responded to this problem by revising the proposed settlement. Namely, the proposed settlement 6 now dictates that 25% of the net settlement amount will be allocated for equal distribution 7 amongst those class members who experienced a termination event during the class period, while 8 the remaining 75% will be allocated for equal distribution amongst all class members. Proposed 9 Settlement, ¶ 15. Their solution fixes part of the problem, but leaves unaddressed the Court’s 10 stated concern that the same problem existed with other class claims that appear to disparately 11 affect class members. For instance, in the greater potential recovery analysis, Lusk indicates that 12 the value of the wage statement claim is premised, in part, on 996 first violations of Labor Code 13 § 226. Motion at 24. This number (996)—which matches the number of aggrieved employees for 14 purposes of the PAGA claim—is substantially less than the number of putative class members 15 (2,206). Once again, this math concerns the Court in so far as it projects that some class members 16 will receive a windfall at the expense of other class members. As the Court has noted, Lusk’s 17 pleading of separate subclasses for the meal period, rest period, unreimbursed expenses, wage 18 statement, and separation wages claims seems to recognize this precise problem. FAC, ¶¶ 20, 95, 19 108, 111, 119, 140, 143, 159, 167. The parties’ revision of the proposed settlement accounts for 20 one of these claims, but their neglect of the others is left unexplained with clear red flags present. 21 22 B. Conditional Certification 23 Rule 23 of the Federal Rules of Civil Procedure imposes a two-step test for deciding 24 whether a class may be certified. Under the first step, the court determines whether the moving 25 party has established four prerequisites: 26 (1) the class is so numerous that joinder of all members is impracticable; (2) there are questions of law or fact common to the class; (3) the claims or defenses of the 27 representative parties are typical of the claims or defenses of the class; and (4) the representative parties will fairly and adequately protect the interests of the class. 28 1 Fed. R. Civ. P. 23(a)(1)–(4). If these prerequisites are met, the court considers whether the 2 proposed class action meets at least one of the three provisions of Rule 23(b). Fed. R. Civ. P. 3 23(b). Lusk seeks certification under Rule 23(b)(3), which states that a class action may be 4 maintained if “the court finds that the questions of law or fact common to class members 5 predominate over any questions affecting only individual members, and that a class action is 6 superior to other available methods for fairly and efficiently adjudicating the controversy.” Fed. 7 R. Civ. P. 23(b)(3). As for this preliminary stage, where a settlement class has not already been 8 certified, the court must determine that it will “likely be able to . . . certify the class for purposes of 9 judgment on the proposal following the final approval hearing.” Fed. R. Civ. P. 23(e)(1)(B). To 10 make such a determination, the court needs “a suitable basis in the record.” Fed. R. Civ. P. 11 23(e)(1) advisory committee’s note to 2018 amendment. 12 Big picture, the Court’s task at hand is to project whether Lusk will be able to establish at a 13 final approval hearing that his claims are typical of the class claims and that common questions 14 predominate over individualized inquiries. Acosta v. Evergreen Moneysource Mortg. Co., No. 15 2:17-CV-00466-KJM-DB, 2018 WL 3831004, at *2 (E.D. Cal. Aug. 13, 2018); Mitchinson v. 16 Love’s Travel Stops & Country Stores, Inc., No. 1:15-cv-01474-DAD-BAM, 2016 WL 7426115, 17 at *4 (E.D. Cal. Dec. 22, 2016). It is also generally recognized that class certification must be 18 proved by a preponderance of the evidence. Martin v. Sysco Corp., 325 F.R.D. 343, 354 (E.D. 19 Cal. 2018). With that challenge looming, the Court has expressed concern with its ability to 20 actually certify this class based on the evidentiary record. Doc. No. 66 at 21–23. Although they 21 recognize this concern in their latest briefing, the parties have done little to dispel the Court’s 22 lingering apprehension.5 23 To start, counsel for Lusk once again describes the parties’ evidentiary efforts in rather 24 conclusory fashion, stating: 25 [t]he Parties conducted significant and extensive investigation of the facts and law during the prosecution of this action. Such investigation included formal written 26 27 5 As noted in the last order and above, the Court remains concerned with the lack of subclass treatment for certain 28 class claims and this concern applies in the certification context as well. Doc. No. 66 at 21. Lusk does not address 1 pages of documents (which included Defendants’ meal period and rest break policies, along with the relevant employee handbook, time punch records and wage 2 statements), as well as Plaintiff’s videotaped deposition. 3 Setareh Decl., ¶ 7. Counsel for Defendants offers something similar in his own declaration. Woo 4 Decl., ¶¶ 4–8. While these descriptions are themselves uninspiring, what the Court finds truly 5 troubling is defense counsel’s submission of sworn declarations from sixty-nine putative class 6 members. Id., ¶ 9, Ex. B. Lusk has previously referred to these declarations to emphasize 7 significant risks attendant to certain class claims. He does the same here. Motion at 28, 30, 32. 8 Defendants then do him one better by using the declarations in their statement of non-opposition 9 to support their assertions that the class claims are wholly meritless because Lusk has no evidence 10 to support his legal theories. Doc. No. 78 at 5–11.6 Defendants’ non-opposition is clearly 11 designed to assist Lusk’s argument that evidence-related risks demonstrate that the proposed 12 settlement is fair and reasonable. But in providing that help, Defendants have also re-emphasized 13 the exact problem the Court described in its last order regarding a seeming dearth of evidence that 14 will be available for the Court to use to certify the class under Rule 23. 15 All of this leaves the Court in a complicated position. Across multiple motions, Lusk has 16 offered next to nothing to show that the prospects for certification are adequately supported by the 17 record, and Defendants have now made his task even harder by presenting evidence that directly 18 undermines his certification position. Notwithstanding, the Court could provide conditional 19 certification on the ground that the class claims follow a familiar format to claims that frequently 20 garner certification. Yet, in so doing, the Court is concerned that the record presented for 21 certification and final approval of the settlement will be as barren as the parties’ current 22 descriptions suggest. If it is, and the collective evidence shows Lusk as the lone putative class 23 member who suffered from the alleged harms, there will be no grounds for the Court to conclude 24 that his claims are typical of those possessed by the broader class. Rather, Lusk’s own claims 25 will, by definition, represent individualized inquiries as opposed to predominating common 26 27 6 Defendants further bolster their assertions with excerpts of Lusk’s deposition and their employee handbooks and 28 meal and rest break policies. Doc. No. 78 at 5–11; Woo Decl., ¶¶ 6, 13, Ex. A, Ex. C. Lusk, for his part, also notes 1 questions of law or fact. In other words, certification will not be possible, as Lusk will not have 2 shown by a preponderance of the evidence that the requirements of Rule 23(a) and (b)(3) are met. 3 And all that will be left is potential confusion moving forward. Rodriguez v. Penske Logistics, 4 LLC, No. 2:14-cv-02061-KJM-CKD, 2017 WL 4132430, at *4 (E.D. Cal. Sept. 19, 2017). 5 6 C. Conclusion 7 The Court’s role in its current position is to cautiously and rigorously scrutinize this 8 attempt to settle a class action before the putative class has been certified. Roes, 1-2 v. SFBSC 9 Mgmt., LLC, 944 F.3d 1035, 1049 (9th Cir. 2019). In doing that here, the Court will deny Lusk’s 10 latest motion seeking preliminary approval and conditional certification for the reasons discussed 11 above. The Court also requests that the parties carefully consider how they would like to proceed 12 before another motion of this kind is immediately filed. At this point, Lusk appears to be doing 13 himself and the putative class he seeks to represent a disservice by trying to fit a square peg in a 14 round hole. The Court does not find clear signs of collusion here. Bluetooth Headset Prods. Liab. 15 Litig., 654 F.3d at 946. But it faces a perverse set of circumstances where Defendants are willing 16 to pay more than $1 million to settle the class claims despite their briefing and all presented 17 evidence singly pointing to a complete lack of merit in those claims. This seeming incongruity 18 could have a few different explanations, from an undervaluing of the class claims to a nuisance fee 19 agreement of low-merit claims. The Court also recognizes the possibility that this prolonged 20 inability to secure preliminary approval and conditional certification is a result of insufficient 21 effort to lay a foundation for such relief. If that is the case, an appropriate path forward may 22 include additional pre-certification discovery. Manual for Complex Litigation §§ 21.14, 21.141. 23 Regardless of the precise steps taken, however, the Court will not further consider a new motion 24 that merely tinkers with the same details that have now been inadequately presented to the Court 25 four times. In other words, to seek this form of relief in the future, Lusk must substantively 26 account for the problems discussed in this order—including, importantly, a suitable basis in the 27 record for certification—even if doing so first requires the parties to return to the negotiating table 28 or conduct more discovery. 1 ORDER 2 Accordingly, IT IS HEREBY ORDERED that: 3 1. Lusk’s third-amended motion for preliminary approval and conditional certification 4 (Doc. No. 75) is DENIED without prejudice; and 5 2. This case is referred back to the magistrate judge for further scheduling and 6 management. 7 g IT IS SO ORDERED. g |Dated: _ January 22, 2022 7 ZS □ Z Cb Led — SENIOR DISTRICT JUDGE 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 19

Document Info

Docket Number: 1:17-cv-00762

Filed Date: 1/24/2022

Precedential Status: Precedential

Modified Date: 6/19/2024