Home » Posts tagged 'Class Action'
Tag Archives: Class Action
Knepper v. Rite Aid Corp.
In one of the most anticipated wage and hour decisions pending at the circuit court level, the Third Circuit held yesterday that Rule 23 state law wage and hour class actions (opt-out) are not inherently incompatible with FLSA collective action (opt-in). Likely ending one of the longest running and hotly contested issues in wage and hour litigation the Third Circuit “join[ed] the Second, Seventh, Ninth and D.C. circuits in ruling that this purported ‘inherent incompatibility’ does not defeat otherwise available federal jurisdiction.”
At the court below the plaintiffs had asserted a hybrid cause of action– claims under both the FLSA’s collective action mechanism and multiple states’ wage and hour laws (Rule 23 class actions). Unlike some so-called hybrids though, here the Court’s jurisdiction over the Rule 23 state law claims was based on the original jurisdiction of CAFA, rather than the supplemental jurisdiction of 1367. While the court below had held that the Rule 23 claims could not be brought together with the FLSA collective action claims, based on “inherent incompatibility” the Third Circuit disagreed and reversed.
Framing the issue, the court explained:
“This case involves a putative conflict between an opt-out Fed.R.Civ.P. 23(b)(3) damages class action based on state statutory wage and overtime laws that parallel the federal Fair Labor Standards Act (FLSA) and a separately filed opt-in collective action under 29 U.S.C. § 216(b) of the FLSA. Both suits allege violations arising from the same conduct or occurrence by the same defendant. At issue is whether federal jurisdiction over the Rule 23 class action based solely on diversity under the Class Action Fairness Act (CAFA), 28 U .S.C. § 1332(d), is inherently incompatible with jurisdiction over the FLSA action, and whether the FLSA preempts state laws that parallel its protections. ”
Although there had been many prior trial level decisions from the courts within the Third Circuit holding that so-called hybrids were “inherently incompatible,” the panel noted that “The concept of inherent incompatibility has not fared well at the appellate level. Four courts of appeals have rejected its application to dual-filed FLSA and class actions.”
Looking first to the text of the FLSA, the court agreed with the Seventh Circuit “that that the plain text of § 216(b) provides no support for the concept of inherent incompatibility.” The court then explained that a look at legislative history was unnecessary in light of the unambiguous nature of the FLSA’s text in this regard. Nonetheless, looking at the legislative history, the court concluded, “we disagree that certifying an opt-out class based on state employment law contravenes the congressional purpose behind the Portal–to–Portal Act.”
Perhaps most significantly, the court revisited its decision in De Asencio and noted that it was “distinguishable, as the Seventh, Ninth, and D.C. Circuits have all concluded. Ervin, 632 F.3d at 981 (“De Asencio represents only a fact-specific application of well-established rules, not a rigid rule about the use of supplemental jurisdiction in cases combining an FLSA count with a state-law class action.”); Wang, 623 F.3d at 761; Lindsay, 448 F.3d at 425 n. 11. Unlike the state law claims at issue in De Asencio, there is no suggestion that the claims under the MWHL and the OMFWSA are novel or complex; Rite Aid’s principal objection is that these state claims are too similar to federal claims with which the federal courts are well familiar. Nor does this case present an instance of supplemental jurisdiction, where there is statutory authority to decline jurisdiction in the factual circumstances of De Asencio. Here, independent jurisdiction exists over plaintiffs’ claims under CAFA, which provides no statutory basis for declining jurisdiction in this instance. For these reasons, we do not believe De Asencio supports dismissal.”
The court concluded:
“In sum, we disagree with the conclusion that jurisdiction over an opt-out class action based on state-law claims that parallel the FLSA is inherently incompatible with the FLSA’s opt-in procedure. Nothing in the plain text of § 216(b) addresses the procedure for state-law claims, nor, in our view, does the provision’s legislative history establish a clear congressional intent to bar opt-out actions based on state law. We join the Second, Seventh, Ninth, and D.C. Circuits in ruling that this purported “inherent incompatibility” does not defeat otherwise available federal jurisdiction.”
The court also rejected the contention that the FLSA somehow preempts more beneficial state wage and hour laws.
Click Knepper v. Rite Aid Corp. to read the entire Opinion of the Court. Click here to read the Secretary of Labor’s amicus brief in support of the plaintiff-appellant and here to read the amicus brief submitted on behalf of several employee rights’ organizations, including the National Employment Law Association (NELA).
W.D.Mo.: Court Has Subject Matter Jurisdiction Over Claims That Could Be Brought By Members of Putative Class, But Could Not Be Brought By Named Plaintiffs
Nobles v. State Farm Mut. Auto Ins. Co.
This case concered off-the-clock claims that were brought as a so-called hybrid case, so named because the claims asserted were a hybrid of several state wage and hour laws, as well as under the FLSA. As discussed here, the plaintiffs, employees of one State Farm entity (State Farm Fire) sued both their employer, and another State Farm entity (State Farm Mutual), alleging identical wage and hour violations were committed by both against similarly situated employees. By Motion to Dismiss, State Farm Mutual challenged the named-plaintiffs’ standing to assert claims against it, asserting that the named plaintiffs lacked standing to do so, because it was not their employer. The court rejected these arguments, in granting plaintiffs’ motions for conditional and class certification.
Addressing this issue the court explained:
“In its pending Motion to Dismiss, State Farm Mutual contends that because Plaintiffs lack standing to assert joint employer status, the Court lacks subject matter jurisdiction, and therefore that claim should be dismissed under Federal Rule of Civil Procedure 12(b)(1). Alternatively, State Farm Mutual contends that Plaintiffs have failed to state a claim for joint employer status and therefore it should be dismissed pursuant to Federal Rule of Civil Procedure 12(b)(6).
State Farm Mutual argues that “[o]nly State Farm Fire employees could possibly have standing to assert joint employment claims under Plaintiffs’ … theory, and there are no such plaintiffs in this case.” [Doc. # 111, at 13]. Neither Nobles nor Atchison are employees of State Farm Fire. However, standing issues “must be assessed with reference to the class as a whole, not simply with reference to the individual named plaintiffs.” Payton v. County of Kane, 308 F.3d 673, 680 (7th Cir.2002). Here, unnamed class members of the certified classes and collective include State Farm Fire employees who would have standing to bring claims under State Farm Mutual’s status as a joint employer with State Farm Fire. Thus, the Plaintiffs in this litigation have standing to assert joint employment status for members of the class.
Two recently decided cases in this district, Gilmor v. Preferred Credit Corp., No. 10–0189–CV–W–ODS, 2011 WL 111238 (W.D. Mo. Jan 13, 2011), and Wong v. Bann–Cor Mortgage, No. 10–1038–CV–W–FJG, 2011 WL 2314198 (W.D. Mo. June 9, 2011), also concluded that the court had subject matter jurisdiction over claims that could be brought by members of the certified class, but could not have been brought by any of the named plaintiffs. However, as a practical matter, it may be prudent to have a specific named Plaintiff whose named employer is State Farm Fire. See Gilmor, 2011 WL 111238, at *7. Therefore, Plaintiffs shall file an appropriate motion to designate such an employee prior to the close of discovery on the merits.”
Addressing (and rejecting) the defendants’ contention that plaintiffs had failed to sufficiently plead joint employment, the court reasoned:
“To determine whether an individual or entity is an employer, courts analyze the economic reality of the relationship between the parties.” Loyd v. Ace Logistics, LLC, No. 08–CV–00188–W–HFS, 2008 WL 5211022, at *3 (citation omitted). Although the Eighth Circuit has not yet stated a test to determine joint employer status, four factors are typically examined by courts to make this determination. They are: “whether the alleged employer: (1) had the power to hire and fire the plaintiff; (2) supervised and controlled plaintiff’s work schedules or conditions of employment; (3) determined the rate and method of payment; and (4) maintained plaintiff’s employment records.” Id. at * 3 (citing Schubert v. BethesdaHealth Grp., Inc., 319 F.Supp.2d 963, 971 (E.D.Mo.2004)).
State Farm Mutual asserts that Plaintiffs have failed to allege the elements of joint employer status or single enterprise status. This argument rests on the contention that because all of the named plaintiffs in the litigation are not employees of State Farm Fire, none of their allegations concern State Farm Mutual’s power to hire or fire any plaintiff who is an employee of State Farm Fire. [Doc. # 111, at 7].
The Court finds that this argument is a re-characterization of State Farm Mutual’s standing argument. As previously stated, Plaintiffs in this case include the certified classes. See Gilmor, 2011 WL 111238, at *6 (citing Sosna v. Iowa, 419 U.S. 393, 399 (1975)). Plaintiffs in this case include State Farm Fire employees who were subject to State Farm Mutual’s policies; and the Second Amended Complaint alleges that State Farm Mutual had the power to hire or fire them.
Second, State Farm Mutual asserts that even if the Court finds that Plaintiffs have alleged the elements of joint employment status, Plaintiffs’ factual allegations are “broad, unsupported statements” that do not provide the required factual support for Plaintiffs’ joint employment claim. [Doc. # 111, at 9]. The Court disagrees with State Farm Mutual’s characterization of Plaintiffs’ allegations. The Plaintiffs allege in their Second Amended Complaint that (1) the human resources department in State Farm Mutual retains the power to promote, retain, and discipline State Farm Fire employees, (2) State Farm Fire employees’ work and compensation are subject to State Farm Mutual’s written pay and timekeeping policy, and (3) State Farm Mutual’s and State Farm Fire’s timekeeping records are housed together, which the Court liberally construes to imply that State Farm Mutual maintains State Farm Fire’s timekeeping records.
For these reasons, the Court finds that Plaintiffs have sufficiently stated a joint employer claim.”
Click Nobles v. State Farm Mutual Automobile Insurance Company to read the entire Order.
E.D.Pa.: Defendant’s Attempt to Obtain Class Waivers From Absent Class Members While Motion for Conditional Certification Pending Impermissible; Corrective Measures Ordered
Williams v. Securitas Sec. Services USA, Inc.
Before the court was the emergency motion of plaintiffs for a protective order and corrective mailing to address defendant’s improper communications with absent class members. While plaintiffs motion for conditional certification was pending before the court (but before it had been resolved), the defendant sought to obtain class waivers of the claims in the case from its current employees, by sending each an alternative dispute resolution agreement. The court held that such attempts by the defendant amounted to an obstruction of the court’s role in managing the collective action, granted plaintiffs motion and ordered related corrective action by defendant.
The motion alleged that defendant distributed to all its employees, including its Pennsylvania employees, a document entitled “Securitas Security Services USA, Inc. Dispute Resolution Agreement” (hereinafter “the Agreement”). The body of the Agreement consists of ten paragraphs on four type-written, single-spaced pages and is written in a small font. A fifth page provides a place for the employee to acknowledge receipt of the document. In relevant part:
“The Agreement purports to require all Securitas employees to submit “any dispute arising out of or related to Employee’s employment with [Securitas] … or termination of employment” to a binding arbitration conducted pursuant to the Federal Arbitration Act (“FAA”), 9 U.S.C. § 1, et seq. It states in small boldface letters that “this Agreement requires all such disputes to be resolved only by an arbitrator through final and binding arbitration and not by way of court or jury trial.” The Agreement specifies that any dispute arising from federal “wage-hour law” and the FLSA must be arbitrated. The Agreement states, again in small bold font, “there will be no right or authority for any dispute to be brought, heard or arbitrated as a class, collective or representative action (“Class Action Waiver”).”
Paragraph 7 of the Agreement says that although the Agreement is meant to apply “broadly,” if an employee is “a named party plaintiff, or ha[s] joined as a party plaintiff this Agreement shall not apply to those Actions, and you may continue to participate in them without regard to this Agreement,” but “shall apply to all Actions in which you are not a plaintiff or part of a certified class.” The Agreement then lists five representative or class action lawsuits in which Securitas is a named defendant, including this lawsuit, “Frankie Williams and Kimberly Ord, filed 12/10/2010, USDC, Eastern District of Pennsylvania Case No. 2:10–CV–07181–HB.” The term “Actions” is defined as “litigation on behalf of [Securitas] employees in which those employees desire to represent claims of other employees in class, collective or other representative actions.” Thus, the term “Actions” does not appear to be limited only to the five lawsuits enumerated later in paragraph 7. The nature of the Williams action is not explained.
The Agreement further states that if the employee would like to participate in one of the “Actions,” he or she “may opt out of this Agreement by following the procedure set forth in Section 9, below.” To opt out of the Agreement, the employee must call a toll-free telephone number within 30 days of the date the employee received the Agreement. According to the Agreement, “Should an Employee not opt out of this Agreement within 30 days of the Employee’s receipt of this Agreement, continuing the Employee’s employment constitutes mutual acceptance of the terms of this Agreement by the Employee and [Securitas].” The Agreement declares that not opting out means an employee forfeits the right to participate in any collective or representative action. Securitas adds that it will not retaliate against any employee for opting out of the Agreement or for asserting claims according to its terms.
The fifth page of the Agreement states as follows:
ACKNOWLEDGMENT OF RECEIPT OF THE SECURITAS SECURITY SERVICES USA, INC. DISPUTE RESOLUTION AGREEMENT
BY SIGNING BELOW, I AM ACKNOWLEDGING RECEIPT OF THE SECURITAS SECURITY SERVICES USA, INC. DISPUTE RESOLUTION AGREEMENT, EFFECTIVE IMMEDIATELY.
Below this text is a place for the employee to sign and date the Agreement. There is also a place for a witness to sign his or her name.”
The court rejected defendant’s attempts to stretch the holding of the Supreme Court’s recent holding in AT&T Mobility LLC v. Concepcion, stating:
“Under Hoffman–La Roche, this court has a responsibility to prevent confusion and unfairness concerning this action in which plaintiffs seek to have the matter proceed as a collective action and to insure that all parties act fairly while the court decides whether and how this action will move forward under the FLSA. In the meantime, to prevent confusion and unfairness, we will order Securitas to rescind the Agreement with respect to its Pennsylvania employees as it relates to this litigation. We will require Securitas to set forth the nature of this action and advise its Pennsylvania employees that the Agreement is not binding with regard to those employees’ right to participate in this lawsuit, notwithstanding the fact that the employee may have signed the Agreement or failed timely to opt out.
Securitas contends that any interference by this court with its efforts to compel arbitration of disputes with its employees will be contrary to the Supreme Court’s recent decision in AT&T Mobility LLC v. Concepcion, –––U.S. ––––, 131 S.Ct. 1740, 179 L.Ed.2d 742 (2011). We disagree. In Concepcion, the Supreme Court held that, generally, states may not adopt rules of contract interpretation that undermine the “overarching purpose” of the FAA, which “is to ensure the enforcement of arbitration agreements according to their terms so as to facilitate streamlined proceedings.” Id. at 1748. There, the Court considered California contract law, which deemed unconscionable certain contracts that disallowed class arbitration. The Court found the law impermissibly stood “as an obstacle to the accomplishment of the FAA’s objectives.”
Securitas’ reliance on Concepcion is inapposite because plaintiffs’ motion for a protective order does not rely on any state-law ground to invalidate the Agreement. Here the issue is quite different. This court has found the Agreement to be a confusing and unfair communication with the class of possible plaintiffs in this action under the FLSA.
Securitas argues that invalidating the Agreement merely because this class action lawsuits is pending is equivalent to preventing it from adopting any arbitration policy at all. Whatever right Securitas may have to ask its employees to agree to arbitrate, its current effort, which specifically references this lawsuit, is confusing and misleading and clearly designed to thwart unfairly the right of its employees to make an informed choice as to whether to participate in this collective action under the FLSA. Since the Agreement by its terms will directly affect this lawsuit, this court has authority to prevent abuse and to enter appropriate orders governing the conduct of counsel and the parties. Hoffman–La Roche, 493 U.S. at 171–72. Securitas did not act fairly when it gave notice through the Agreement to potential class members concerning this lawsuit.
Defendant’s proposal to resolve the plaintiffs’ pending motion for conditional class certification before resolving issues related to the Agreement is insufficient to prevent potential plaintiffs from misapprehending their rights. The confusing nature of the Agreement may cause Securitas employees to misunderstand the nature of their rights to participate in this litigation while the court determines whether to conditionally certify a class, damage not easily undone. Similarly, Securitas’s proposal to allow its Pennsylvania employees a second 30–day opt out period if the court conditionally certifies a class is also insufficient because it is for the court, not Securitas, to determine the amount of time employees shall have to consider their right to join this action. Immediate action by this court is necessary.
Securitas shall be required to implement the corrective measures described in the accompanying order.”
In the accompanying Order, the court required that the defendant submit a proposed corrective notice to the plaintiffs within 48 hours which, among other things, stated the the dispute resolution agreement was not binding on with regard to participation in the case (i.e. they would not be precluded from joining this class if they signed the agreement at issue).
S.D.N.Y.: Because FLSA Collective Action Is Not A Class Action, FLSA Collective Action Subject To Arbitration Despite FINRA Rule Prohibiting Class Actions
Velez v. Perrin Holden & Davenport Capital Corp.
Plaintiff brought this action alleging violations of the Fair Labor Standards Act (“FLSA”) and the New York Labor Law (“NYLL”) on behalf of himself and other similarly situated stock brokers employed or formerly employed by defendant Perrin Holden & Davenport Capital Corp. (“PHD Capital”) and its officers and owners. Plaintiff sought designation of the case as as a collective action pursuant to FLSA section 216 for his FLSA claims and as a class action pursuant to Fed.R.Civ.P. 23 for his state law claims.
Defendants moved to dismiss the complaint pursuant to Fed.R.Civ.P. 12(b)(6) or, in the alternative, to compel arbitration pursuant to the Federal Arbitration Act (“FAA”), 9 U.S .C. §§ 3, 4, on the ground that Plaintiff had agreed to arbitrate his FLSA claims at the time he was hired. In line with other courts that have decided the issue, the court held that a “collective action” is not encompassed within the term “class action” as that term is used in FINRA’s rules, and thus compelled arbitration of Velez’s FLSA claims, allowing for a collective action in FINRA arbitration.
After finding that the Plaintiff’s claims were subject to arbitration, the court then discussed whether, under FINRA rules banning class actions, Plaintiff could proceed with an FLSA collective action. Reasoning he could the court explained:
“FINRA Rule 13200 mandates arbitration of disputes between the parties “except as otherwise provided.” (FINRA Rule 13200, Ex. B to Declaration of Matthew D. Kadushin dated Aug. 27, 2010 (“Kadushin Decl.”).) Notably, FINRA Rule 13204 prohibits arbitration of “class action claims.” (FINRA Rule 13204, Ex. A to Kadushin Decl.) It is thus uncontested that Velez’s state law claims-which plaintiff has asserted as a class action pursuant to Fed.R.Civ.P. 23-are ineligible for arbitration. The parties dispute, however, whether that exemption of class action claims from arbitration also applies to plaintiff’s FLSA collective action claims. While defendants contend that collective actions are distinct from class actions and therefore subject to FINRA arbitration, Velez argues that the phrase “class action” in FINRA Rule 13204 encompasses a collective action and therefore collective action claims are not arbitrable. Velez looks to the interpretation by FINRA staff members of FINRA’s rules to support his position.
Every court to address whether an FLSA collective action is arbitrable pursuant to FINRA’s rules has found in favor of arbitrability. See Gomez v. Brill Securities, Inc., No. 10 Civ. 3503, 2010 WL 4455827 (S.D.N.Y. Nov. 2, 2010); Suschil v. Ameriprise Financial Servs., Inc., No. 07 Civ. 2655, 2008 WL 974045, at *5 (N.D.Ohio Apr. 7, 2008); Chapman v. Lehman Bros., Inc., 279 F.Supp.2d 1286, 1290 (S.D.Fla.2003). This Court agrees with its sister district courts.
FINRA Rule 13204 clearly states that “[c]lass action claims may not be arbitrated” under FINRA’s Code of Arbitration Procedure. However, that rule says nothing about collective action claims. Although collective and class actions have much in common, there is a critically important difference: collective actions are opt-in actions, i.e., each member of the class must take steps to opt in to the action in order to participate in it, whereas class actions are opt-out actions, i.e., class members automatically participate in a class action unless they take affirmative steps to opt out of the class action. Collective actions bind only similarly situated plaintiffs who have affirmatively consented to join the action.
Velez urges the Court to defer to the opinions of FINRA staff who have issued letters construing collective actions to come within the ambit of class actions for the purposes of FINRA arbitration. (See, e.g., Letter from Jean I. Feeney, NASD Assistant General Counsel, dated Sept. 21, 1999, Ex. C. to Kadushin Decl.; Letter from George H. Friedman, NASD Executive Vice President, Dispute Resolution, Director of Arbitration, dated Oct. 10, 2003, Ex. D to Kadushin Decl.) However, those letters do not contain any substantial analysis, and the Feeney letter itself includes the disclaimer that “the opinions expressed herein are staff opinions only and have not been reviewed or endorsed by the Board of Directors of [the] NASD.” Moreover, FINRA’s website specifically states that “[s]taff-issued interpretive letters express staff views and opinions only and are not binding on FINRA and its Board.” (FINRA-Interpretive Letters, Ex. 1 to Affirmation of Emily A. Hayes dated Sept. 9, 2010). Such “staff opinion letters are not the sort of agency interpretation that is entitled to deference by this Court.” Gomez, 2010 WL 4455827 at *1; see also Auer v. Robbins, 519 U.S. 452, 461 (1997); Skidmore v. Swift & Co., 323 U.S. 134 (1944). If FINRA wanted to prohibit arbitration of collective action claims, FINRA is certainly able to amend its rules to do so. See FINRA Rulemaking Process, available at http://www.finra.org/In dustry/Regulation/FINRARules/RulemakingProcess (Feb. 2, 2010); see also Gomez, 2010 WL 4455827 at *2.
As noted above, the parties here have agreed in writing to arbitrate certain disputes as required by FINRA. In light of other district court opinions, this Court’s own interpretation of FINRA rules, and the federal policy favoring arbitration as an alternative forum in which to resolve disputes, this Court finds that FLSA collective actions are within the scope of the parties’ agreement to arbitrate. In addition, no congressional intent precludes arbitration of the federal FLSA claims. See, e.g., Gomez, 2010 WL 4455827 at *2; Coheleach v. Bear, Stearns & Co., 440 F.Supp.2d 338, 240 (S.D.N.Y.2006).”
Accordingly, defendants’ motion was granted to the extent that the court compelled arbitration of Plaintiff’s FLSA claims.
7th Cir.: Collective Action FLSA Claims May Proceed In A “Hybrid Action” With State Law Rule 23 Claims
Ervin v. OS Restaurant Services, Inc.
In this appeal the Seventh Circuit considered “whether employees who institute a collective action against their employer under the terms of the Fair Labor Standards Act of 1938, as amended, 29 U.S.C. § 201 et seq. (“FLSA”), may at the same time litigate supplemental state-law claims as a class action certified according to Federal Rule of Civil Procedure 23(b)(3). The district court thought not; it rejected the plaintiffs’ effort to proceed as a class under Rule 23(b)(3) on the ground that there is a “clear incompatibility” between the FLSA proceeding and the proposed class action.” Answering this question in the affirmative (finding that so-called “hybrid actions” are permissible) the Seventh Circuit reversed the lower court’s decision holding otherwise and remanded the case for further findings in accordance with its opinion.
The court explained:
“The problem, as the court saw it, stems from the fact that the FLSA requires potential plaintiffs to opt in to participate in an action, while the plaintiffs in a Rule 23(b)(3) class action are included in the case unless they opt out. Trying to use both systems side-by-side would be rife with complications, it concluded; more formally, it held that one could never find the superiority requirement of Rule 23(b)(3) satisfied if the case also involved an FLSA collective action.
The question whether these two distinct types of aggregate litigation may co-exist within one case has divided the trial courts in this circuit and elsewhere. In the Northern District of Illinois alone, compare Barragan v. Evanger’s Dog and Cat Food Co., 259 F .R.D. 330 (N.D.Ill.2009), and Ladegaard v. Hard Rock Concrete Cutters, Inc., 2000 WL 1774091 (N.D.Ill.2000), with Riddle v. National Sec. Agency, Inc., 2007 WL 2746597 (N.D.Ill.2007), McClain v. Leona’s Pizzeria, Inc., 222 F.R.D. 574 (N.D.Ill.2004), and Rodriguez v. The Texan, Inc., 2001 WL 1829490 (N.D.Ill.2001). As far as we can tell, no court of appeals has yet had occasion to address it. But see Wang v. Chinese Daily News, Inc., 623 F.3d 743, 753-55, 760-62 (9th Cir.2010) (holding that a district court properly certified a Rule 23(b)(2) class along with an FLSA collective action and properly exercised supplemental jurisdiction over the state-law claim); Lindsay v. Government Employees Ins. Co., 448 F.3d 416, 420-25 (D.C.Cir.2006) (concluding, in the context of an appeal under Rule 23(f), that the FLSA does not necessarily preclude an exercise of supplemental jurisdiction over related state-law claims); De Asencio v. Tyson Foods, Inc., 342 F.3d 301, 307-12 (3d Cir.2003) (concluding that a district court presiding over an FLSA collective action should not have exercised supplemental jurisdiction over parallel state-law claims).
We conclude that there is no categorical rule against certifying a Rule 23(b)(3) state-law class action in a proceeding that also includes a collective action brought under the FLSA. (We refer to these as “combined” actions, rather than “hybrid” actions, to avoid confusion with other uses of the term “hybrid”-e.g., for cases certified under more than one subsection of Rule 23(b).) In combined actions, the question whether a class should be certified under Rule 23(b)(3) will turn-as it always does-on the application of the criteria set forth in the rule; there is no insurmountable tension between the FLSA and Rule 23(b)(3). Nothing in the text of the FLSA or the procedures established by the statute suggests either that the FLSA was intended generally to oust other ordinary procedures used in federal court or that class actions in particular could not be combined with an FLSA proceeding. We reverse the district court’s class-certification determination and remand for further consideration in accordance with this opinion.”
Click Ervin v. OS Restaurant Services, Inc. to read the entire opinion.
The DOL had submitted an Amicus Brief in support of the Plaintiffs in this case. Click DOL Amicus Brief to read the Amicus Brief the US DOL filed in support of the plaintiff’s in this case.
D.R.I.: Collective Action FLSA Claims Not Mooted By Offer Of Judgment, In Full Satisfaction, To Named Plaintiff; Motion To Dismiss Denied
Nash v. CVS Caremark Corp.
Plaintiff pled this lawsuit for overtime benefits as a “collective action” under the Fair Labor Standards Act (“FLSA”). That is, he purported to act on behalf of himself and “other employees similarly situated” pursuant to 29 U.S.C. § 216(b). After one supposedly “similarly situated” party opted in to the case, Defendants presented both that person and Plaintiff with offers of judgment pursuant to Rule 68 of the Federal Rules of Civil Procedure. The opt-in party previously accepted the offer and was no longer part of the case; Plaintiff rejected the offer, but did not dispute that it was adequate to cover his damages. Defendants then moved to dismiss the suit on grounds that the Rule 68 offer mooted Plaintiff’s claim. However, since that time, other parties opted into the action and seeking to have their claims resolved as part of a “collective action” with Plaintiff. Denying, Defendants’ Motion to Dismiss on mootness grounds, the Court discussed the remedial purposes of the FLSA’s collective action mechanisms.
Discussing Rule 68 initially, the Court reasoned, “[n]othing in the text of Rule 68 compels dismissal of a case for lack of subject matter jurisdiction when a plaintiff rejects an adequate offer of judgment. Rather, the Rule creates what amounts to a penalty scheme when a plaintiff moves forward with litigation despite being offered the maximum damages she can hope to obtain at trial. “If the judgment that the offeree finally obtains is not more favorable than the unaccepted offer, the offeree must pay the costs incurred after the offer was made.” Fed.R.Civ.P. 68(d). Of course, as a practical matter, in some circumstances a Rule 68 offer may “eliminate[ ] a legal dispute upon which federal jurisdiction can be based,” because “[y]ou cannot persist in suing after you’ve won.” Greisz v. Household Bank (Illinois), N.A., 176 F.3d 1012, 1015 (7th Cir.1999). But this does not transform Rule 68 into an escape hatch from every lawsuit. Rather, as this case makes clear, whether a controversy becomes moot following a Rule 68 offer depends on the factual circumstances, the cause of action, and the procedural status of the claims at issue. Moreover, nothing in Rule 68 itself suggests that it should be used as a vehicle for sabotaging claim-aggregating devices like 29 U.S.C. § 216(b) and Rule 23. See Fed.R.Civ.P. 1. (explaining that the Federal Rules of Civil Procedure should be “construed and administered to secure the just, speedy, and inexpensive determination of every action and proceeding”).”
The Court then distinguished a 216(b) collective action, from a Rule 23 class action:
“The Court agrees with Judge Almond that Cruz v. Farquharson, 252 F.3d 530, 533 (1st Cir.2001), in which the First Circuit approved the dismissal of a Rule 23 action as moot, is distinguishable. Cruz emphasized that between the date the plaintiffs in that case received “complete relief,” and the date the district court dismissed the case as moot, “no new plaintiffs tried to intervene, and the named plaintiffs made no effort to amend their complaint to add new parties.” Cruz, 252 F.3d at 533. That is not so here. Four additional parties have, in fact, “tried to intervene” as “similarly situated” plaintiffs by submitting their consents for the Plaintiff to pursue claims on their behalf.
As Judge Almond noted, where even one similarly-situated plaintiff opts in to an FLSA suit after the rejection of a Rule 68 offer, courts “have refused to permit defendants to moot putative FLSA collective actions.” Yeboah v. Central Parking Sys., No. 06 CV 0128(RJD)(JMA), 2007 WL 3232509, at *3 (E.D.N.Y. Nov. 1, 2007); see Reyes v. Carnival Corp., No. 04-21861-CIV., 2005 WL 4891058, at *2 (S.D.Fla. May 25, 2005) (refusing to dismiss FLSA action where “other plaintiffs. opted in to [the] suit [after] the offer of judgment was made”); Roble v. Celestica Corp., 627 F.Supp.2d 1008, 1013-14 (D.Minn.2007) (finding that identifying opt-ins sustained jurisdiction); Rubery v. Buth-Na-Bodhaige, Inc., 494 F.Supp.2d 178, 179-80 (W.D.N.Y.2007) (denying motion to dismiss where more than fifty people had filed consents to join FLSA action). This is true even if, as here, there is no dispute about the adequacy of the offer. See Yeboah, 2007 WL 3232509, at *5 (explaining that even if the plaintiff could not dispute the sufficiency of the judgment, “it neither mooted plaintiff’s FLSA claim nor deprived [the court] of subject matter jurisdiction,” because of the “presence of opt-ins.”).
Defendants contend that the opt-ins cannot be considered “plaintiffs” or “parties” to the suit for purposes of any exception to mootness carved out by Cruz. See Cruz, 252 F.3d at 533. Cruz stressed that there had been no “decision on class certification” under Rule 23, appearing to require a formal grant of class status in order to preserve a controversy after named parties obtain full relief. Here, the case has not yet reached the equivalent stage in the § 216(b) context: “preliminary collective action certification,” which requires an initial demonstration that the plaintiff “is ‘similarly situated’ to the other members of the proposed class.” Poreda v. Boise Cascade, L.L.C., 532 F.Supp.2d 234, 238 (D.Mass.2008). In the absence of preliminary certification, Defendants argue, Plaintiff has no procedural right to act on behalf of purported “similarly situated” parties. “[A] § 216(b) plaintiff … presents only a claim on the merits …. [and][i]n contrast to the Rule 23 plaintiff, a § 216(b) plaintiff has no claim that he is entitled to represent other plaintiffs.” Cameron-Grant v. Maxim Healthcare Servs., Inc., 347 F.3d 1240, 1249 (11th Cir.2003).
In other words, Defendants insist, without the only safe harbor arguably warranted by Cruz-collective action status-this lawsuit died the moment that Plaintiff rejected his Rule 68 offer. At that time, there were no other opt-ins with live claims, and plaintiff had no right to stand in for anyone else. Later opt-ins could not resurrect the action once it expired.
This logic has some superficial appeal. But its limitation is that, if true, employers could always “use Rule 68 as a sword … and avoid[ ] ever having to face a collective action.” Sandoz v. Cingular Wireless LLC, 553 F.3d 913, 919 (5th Cir.2008). Congress clearly did not intend such an “anomaly” in enacting § 216(b). See id. Neither does Cruz, which concerns Rule 23, require the result Defendants urge here, which would effectively thwart Congress’ preference to “avoid multiple lawsuits where numerous employees” allege FLSA violations. Prickett v. DeKalb County, 349 F.3d 1294, 1297 (11th Cir.2003).
The Court recognizes that Cruz may create some tension with the underlying rationale for decisions allowing § 216(b) opt-ins to preserve jurisdiction. As explained by the Fifth Circuit in Sandoz, at bottom those cases rest on what is known as the “relation back” doctrine. See Sandoz, 553 F.3d at 921;see, e.g., Yeboah, 2007 WL 3232509, at *3 (citing Weiss v. Regal Collections, 385 F.3d 337, (3d Cir.2004), a Rule 23 case dealing with the “relation back” doctrine). Sandoz acknowledged the quandary raised by Cameron-Grant: a named FLSA plaintiff “cannot represent any other employees until they affirmatively opt in to the collective action.” Sandoz, 553 F.3d at 919 (citing Cameron-Grant, 347 F.3d at 1249.). “If our analysis stopped there,” the court reasoned, “[the plaintiff’s] case would be moot,” because she had received an adequate offer of judgment before any opt-ins joined the case. Id. Nevertheless, the court cited Sosna v. Iowa, 419 U.S. 393 (1975), as providing a solution. There, the Supreme Court observed that a Rule 23 controversy might become moot “before the district court can reasonably be expected to rule on a certification motion.” Id. at 402 n. 11. Depending on the circumstances, in such instances class certification might “be said to ‘relate back’ to the filing of the complaint,” which would preserve jurisdiction. Id. at 402 n. 11.Sandoz found that the “relation back” doctrine was just as appropriate for § 216(b) as Rule 23, because both types of actions were vulnerable to strategic mooting by Defendants. Accordingly, “there must be some time for a[n FLSA] plaintiff to move to certify a collective action before a defendant can moot the claim through an offer of judgment.” Sandoz, 553 F.3d at 921.
Defendants fairly point out that Cruz did not approve of such an approach to Rule 23, and in fact took a narrow view of Sosna. The holding in Sosna was that jurisdiction did not disappear when a named plaintiff’s claim became moot after certification of a class with live controversies. Sosna, 419 U.S. at 402. Cruz stated outright that the “holding in Sosna ” was not applicable, because the plaintiffs in Cruz had not obtained class certification. Cruz, 252 F.3d at 534. At the same time, Cruz did not address the footnote in Sosna explaining the “relation back” idea. Furthermore, no First Circuit decision has considered the question of whether it would be proper to use the “relation back” approach in the context of § 216(b).FN2
In the Court’s view, applying the “relation back” doctrine is appropriate in this case. Plaintiff represents he has not yet moved for preliminary certification because he has been busy opposing Defendants’ efforts to transfer venue and dismiss the case, which they commenced less than a month after the Complaint was filed. Under the “relation back” doctrine, the opt-ins who appeared after Plaintiff rejected the Rule 68 offer sustain jurisdiction; this will give Plaintiff the opportunity to seek provisional certification without “undue delay” after the entry of this Order. Sandoz, 553 F.3d at 921 (quoting Weiss, 385 F.3d at 348). This, in turn, will enable “due deliberation” on the issue of whether Plaintiff is the appropriate representative of a collective action. See Weiss, 385 F.3d at 348.”
Last, the Court noted that policy precludes a dismissal due to mootness under these circumstances, because of the remedial purposes of the FLSA:
“As discussed, and as Judge Almond noted, granting dismissal in these circumstances would impair the Congressional preference for collective actions embodied in 216(b). The Court offers some additional comments on this topic below. But there is also a second policy consideration that favors affirming the R & R. Specifically, the present motion underscores the unique danger of tactical manipulation in FLSA cases. Thus, as explained below, to the extent Cruz could be read to establish a broad mootness regime that reaches beyond the Rule 23 context, an exception for FLSA actions is warranted.
To begin with, it is clear that allowing Defendants to “pick off” named FLSA plaintiffs one-by-one encourages manipulation of cases and ultimately of the federal courts. See Sandoz, 553 F.3d at 919. One court in Illinois described the ways employers can hamstring collective actions if allowed to snuff named plaintiffs’ claims using Rule 68:
[The] defense strategy creates a virtually unwinnable situation for plaintiffs in collective or class action lawsuits. Defendant makes an offer of “judgment” to Plaintiff, then alleges that the action is moot. Plaintiff therefore must either pursue discovery very early in the case, when a court likely will deem it premature, or seek class certification and/or notice before discovery, which runs the risk of harming the interest of those as-yet undiscovered class members. Reed v. TJX Cos., NO. 04 C 1247, 2004 WL 2415055, at *3 (N.D.Ill. Oct. 27, 2004). The FLSA enforcement scheme clearly does not envision such a minefield. Section 216(b) does not require plaintiffs to petition for provisional certification of a “collective action” when filing a complaint. In fact, the final ruling on whether the named plaintiff may maintain a “collective action” usually occurs “after discovery is complete.” Poreda, 532 F.Supp.2d at 239. The collective action process “should be able to ‘play out’ according to the directives” of § 216(b) and the cases applying it, to permit “due deliberation by the parties and the court” on collective action certification. See Weiss, 385 F.3d at 347-48 (discussing the Rule 23 process).
The moot-and-dismiss tactic also facilitates forum-shopping and plaintiff-shopping. At oral argument, Defendants confirmed that multiple lawsuits regarding the overtime claims asserted here are pending in different jurisdictions around the country. Permitting use of Rule 68 to moot cases in one or more forums and thereby cherry-pick another, potentially with the weakest collective action representative, upends the longstanding principle that, in cases based on federal-question jurisdiction, the plaintiff is the “master of the claim.” Caterpillar, Inc. v. Williams, 482 U.S. 386, 392 (1987).
Defendants might object that Rule 23 actions present the same worries. After all, Rule 23 advances a policy similar to § 216(b): the efficient resolution of widespread small claims dependent on common legal and factual questions. Arguably, the opt-out structure of Rule 23 embodies an even firmer commitment to aggregating claims, in contrast to the opt-in rule for § 216(b) cases. And if this is true, how can the cited policies provide any basis to distinguish Cruz, where the same concerns were not enough to stave off dismissal of a Rule 23 action? In that case, the plaintiffs alleged, there was a large pool of class members, and the defendant had defused class action litigation by mooting the claims of the named parties. See Cruz, 252 F.3d at 535.
The answer to the question above is that FLSA actions are more vulnerable to manipulation than Rule 23 actions. For the latter, filing a complaint tolls the statute of limitations for all alleged class members, whether they know of the lawsuit or not. See Crown, Cork & Seal Co. v. Parker, 462 U.S. 345, 350 (1983) (“The filing of a class action tolls the statute of limitations as to all asserted members of the class ….”). In contrast, parties alleged to be “similarly situated” in a § 216(b) case must affirmatively opt in to toll the limitations period. See29 U.S.C. § 256 (explaining that an FLSA action is not considered to be commenced for a similarly situated party until he submits written consent to join the case); Bonilla v. Las Vegas Cigar Co., 61 F.Supp.2d 1129, 1136-37 (D.Nev.1999) ( “[A]ll potential plaintiffs to § 216(b) actions must file their consent to the suit to toll the statute of limitations.”) (emphasis in original).
This means that defendants can bleed value out of a large pool of outstanding FLSA claims in a way they cannot with a comparable group of Rule 23 claims. “Picking off” § 216(b) plaintiffs delays the point at which any collective action can be provisionally certified. This stalls notification to potential “ similarly situated” parties. O’Donnell v. Robert Half Int’l, Inc., 534 F.Supp.2d 173, 177 (D.Mass.2008) (“A class may be conditionally certified and notified of the pendency of an action only if the putative class members are “similarly situated” with the named plaintiffs.”) The longer it takes for an FLSA class to mature, the lower members’ damages will be once they opt in, given the two-year limitations period. See29 U.S.C. § 255 (2010). In a parallel situation under Rule 23, the clock for absentees stops upon the filing of a complaint that raises their claims. Thus, even if employers pick off some named plaintiffs, the limitations period for absentees pauses while any applicable class action is pending.
The predicament of the opt-ins in this case brings the problem into sharper focus. Widespread claims involving common issues invite lawsuits in different jurisdictions, as is the situation here. Note the disparate outcomes this creates for Rule 23 absentees and FLSA opt-ins. As a practical matter, if a Rule 23 action is dismissed, class members may not have to worry about expiration dates for their claims drawing closer. If there is another class action underway that allegedly embraces their claims, the automatic tolling rule from Crown, Cork & Seal shelters them. Opt-ins to collective actions enjoy no such protection. If the suit to which they have hitched their claims sinks-the result Defendants seek here-the clock starts running again, even if they might be “similarly situated” to the named plaintiff in another pending case. Thus, as Judge Almond observed:
[I]f [Defendants were] successful in dismissing the case as mooted, the four plaintiffs who opted in … would arguably have to either initiate new individual FLSA actions or join another applicable collective action. Thus, the tolling of the limitations period for their claims could be delayed and, if they were ultimately successful, their back pay damages could be reduced since the value of their claims is potentially diminished with each passing day. (R & R at 4-5.) The point is that FLSA opt-ins are more exposed to the erosion and possible expiration of their claims than Rule 23 absentees.
Simply put, it is easier to drown collective actions than class actions. If allowed to use Rule 68 as a weapon, defendants can torpedo complaint after complaint, leaving opt-ins to swim for the nearest viable action as their claims leak value. This justifies a more relaxed mootness standard in FLSA cases than Rule 23 cases, and therefore provides an additional basis for distinguishing Cruz.”
Thus, the Court denied Defendants’ Motion to Dismiss.
Wal-Mart To Pay $40 Million To Massachusetts Workers For Off-the-Clock Work Claims, Boston Globe Reports
The Boston Globe is reporting that the United States’ largest retailer, Wal-Mart has agreed to settle a collective action in Massachusetts for approximately $40 Million.
“Wal-Mart Stores Inc., the world’s largest retailer, has agreed to pay $40 million to as many as 87,500 current and former employees in Massachusetts, the largest wage-and-hour class-action settlement in the state’s history.
The class-action lawsuit, filed in 2001, accused the retailer of denying workers rest and meal breaks, refusing to pay overtime, and manipulating time cards to lower employees’ pay. Under terms of the agreement, which was filed in Middlesex Superior Court yesterday by the employees’ attorneys, any person who worked for Wal-Mart between August 1995 and the settlement date will receive a payment of between $400 and $2,500, depending on the number of years worked, with the average worker receiving a check for $734…
The Massachusetts case is similar to many others that have been brought against the retail behemoth by employees across the country, most alleging that the Bentonville, Ark.-based company violated laws by requiring employees to work through breaks, to work beyond their regular shifts, and similar practices. Wal-Mart has denied the allegations, but in December, the merchant agreed to pay up to $640 million to settle 63 federal and state class-action wage-and-hour lawsuits.”
To read the full story go to the Boston Globe website.
9th Cir.: Court Abused Its Discretion In Finding Predominance Requirement Satisfied, Based-In Large Part-On Employer’s Internal Policy Of Treating Its Employees As Exempt From Overtime
In re Wells Fargo Home Mortg. Overtime Pay Litigation
The case was before the Court on Defendant’s interlocutory appeal, challenging the reasoning of the lower Court in granting class certification on Plaintiff’s California state law claims. The dispute centered around whether the lower court abused its discretion in finding that the predominance requirement of Federal Rule of Civil Procedure 23(b)(3) was satisfied, based-in large part-on an employer’s internal policy of treating its employees as exempt from overtime laws. The Ninth Circuit, remanded for further factual findings, holding that while such uniform exemption policies are relevant to the Rule 23(b)(3) analysis, it is an abuse of discretion to rely on such policies to the near exclusion of other relevant factors touching on predominance.
Analyzing the issue, the Court stated, “[u]nder Rule 23(b)(3), a class may be certified where “the court finds that the questions of law or fact common to class members predominate over any questions affecting only individual members, and that a class action is superior to other available methods for fairly and efficiently adjudicating the controversy.”Fed.R.Civ.P. 23(b)(3). The predominance inquiry of Rule 23(b)(3) asks “whether proposed classes are sufficiently cohesive to warrant adjudication by representation.” Local Joint Executive Bd. of Culinary/Bartender Trust Fund v. Las Vegas Sands, Inc., 244 F.3d 1152, 1162 (9th Cir.2001) (citation and internal quotation marks omitted). The focus is on “the relationship between the common and individual issues.” Hanlon v. Chrysler Corp., 150 F.3d 1011, 1022 (9th Cir.1998).
The question here is whether the district court abused its discretion in finding Rule 23(b)(3)‘s predominance requirement was met based on Wells Fargo’s internal policy of treating all HMCs as exempt from state and federal overtime laws. To succeed under the abuse of discretion standard, Wells Fargo must demonstrate that the district court either (a) should not have relied on its exemption policy at all or (b) made a clear error of judgment in placing too much weight on that single factor vis-a-vis the individual issues.
The first line of attack, that Wells Fargo’s exemption policy was an impermissible factor, is a non-starter. An internal policy that treats all employees alike for exemption purposes suggests that the employer believes some degree of homogeneity exists among the employees. This undercuts later arguments that the employees are too diverse for uniform treatment. Therefore, an exemption policy is a permissible factor for consideration under Rule 23(b)(3).
Wells Fargo’s arguments are better construed as a challenge to the weight accorded to the internal exemption policies under the third abuse of discretion prong: mulling the proper factors but committing clear error in weighing them. To analyze this question, we first ask how much weight the district court gave to the exemption policy. Plaintiffs suggest the weight was minimal; Wells Fargo claims that the district court’s reliance was tantamount to estoppel.
A review of the California certification order lends substantial credence to Wells Fargo’s position. Although the court’s analysis of each exemption was careful and considered, its ultimate decision was clearly driven by Wells Fargo’s uniform exemption policy. Indeed, the court found “serious issues regarding individual variations among HMC job duties and experiences” but nevertheless concluded that common questions predominated because “it is manifestly disingenuous for a company to treat a class of employees as a homogenous group for the purposes of internal policies and compensation, and then assert that the same group is too diverse for class treatment in overtime litigation.”E.R. 17. As such, we must conclude that the district court’s reliance on Wells Fargo’s internal exemption policy was substantial.
This leads to the central question: whether such heavy reliance constituted a clear error of judgment in assaying the predominance factors. District courts within this circuit have split on the relevance of exemption policies. The district court relied primarily on Wang v. Chinese Daily News, Inc., 231 F.R.D. 602, 612-13 (C.D.Cal.2005), which found predominance of common issues based on an employer’s policy of treating all employees in a certain position as uniformly exempt from overtime compensation requirements. In contrast, another district court has expressed doubt about Wang, and found that uniform exemption policies are merely a minor factor in the predominance analysis. See Campbell v. PricewaterhouseCoopers, LLP, 253 F.R.D. 586, 603-04 (E.D.Cal.2008) (rejecting “estoppel” position of Wang ).
In determining which rule is appropriate, we begin by examining Rule 23 itself. A principal purpose behind Rule 23 class actions is to promote “efficiency and economy of litigation.” Am. Pipe & Constr. Co. v. Utah, 414 U.S. 538, 553 (1974). In particular, Rule 23(b)(3)‘s predominance and superiority requirements were added “to cover cases’in which a class action would achieve economies of time, effort, and expense, and promote … uniformity of decision as to persons similarly situated, without sacrificing procedural fairness or bringing about other undesirable results.'” Anchem Prods., Inc. v. Windsor, 521 U.S. 591, 615 (1997) (quoting Fed.R.Civ.P. 23(b)(3) Adv. Comm. Notes to 1966 Amendment). Thus, the ” ‘notion that the adjudication of common issues will help achieve judicial economy’ ” is an integral part of the predominance test. Zinser v. Accufix Research Inst., Inc., 253 F.3d 1180, 1189 (9th Cir.2001) (quoting Valentino v. Carter-Wallace, Inc., 97 F.3d 1227, 1234 (9th Cir.1996)). Whether judicial economy will be served in a particular case turns on close scrutiny of “the relationship between the common and individual issues.” Hanlon, 150 F.3d at 1022.
Viewed in light of these principles, the rule espoused in Wang has little justification. Wang essentially creates a presumption that class certification is proper when an employer’s internal exemption policies are applied uniformly to the employees. Such an approach, however, disregards the existence of other potential individual issues that may make class treatment difficult if not impossible. Indeed, this case is a prime example, as the district court identified “serious issues regarding individual variations” that were not susceptible to common proof, but nevertheless felt compelled to certify the class.
Of course, uniform corporate policies will often bear heavily on questions of predominance and superiority. Indeed, courts have long found that comprehensive uniform policies detailing the job duties and responsibilities of employees carry great weight for certification purposes. Damassia v. Duane Reade, Inc., 250 F.R.D. 152, 160 (S.D.N.Y.2008) (“Where … there is evidence that the duties of the job are largely defined by comprehensive corporate procedures and policies, district courts have routinely certified classes of employees challenging their classification as exempt, despite arguments about ‘individualized’ differences in job responsibilities.”). Such centralized rules, to the extent they reflect the realities of the workplace, suggest a uniformity among employees that is susceptible to common proof.
But Wells Fargo’s blanket application of exemption status, whether right or wrong, is not such a rule. In contrast to centralized work policies, the blanket exemption policy does nothing to facilitate common proof on the otherwise individualized issues.
To illustrate, consider the federal outside salesperson exemption. This exemption applies where, among other things, the employee is “customarily and regularly away from the employer’s place of … business….”29 C.F.R. § 541.500(a). Often, this exemption will militate against certification because, as the district court noted, it requires “a fact-intensive inquiry into each potential plaintiff’s employment situation….” E.R. 11. A centralized policy requiring employees to be at their desks for 80% of their workday would change this individual issue into a common one. Therefore, such a corporate policy would be highly relevant to the predominance analysis. A uniform exemption policy, however, has no such transformative power. Whether such a policy is in place or not, courts must still ask where the individual employees actually spent their time. As one court succinctly explained, “[t]he fact that an employer classifies all or most of a particular class of employees as exempt does not eliminate the need to make a factual determination as to whether class members are actually performing similar duties.” Campbell, 253 F.R.D. at 603.
In short, Wells Fargo’s uniform exemption policy says little about the main concern in the predominance inquiry: the balance between individual and common issues. As such, we hold that the district court abused its discretion in relying on that policy to the near exclusion of other factors relevant to the predominance inquiry.”
E.D.Cal.: Settlement Of Rule 23 And 216(b) Class Hybrid Action Requires Simultaneous Notice; Opt-out Notice Alone Insufficient To Bind Class On FLSA Claims
Wright v. Linkus Enterprises, Inc.
Plaintiffs filed this action against Defendant for violation of various state and federal labor laws. Before the Court was Plaintiffs’ Unopposed Motion for Preliminary Approval of Settlement of their hybrid action, which consisted of both a Federal Rule of Civil Procedure 23(b)(3) class action and a Federal Fair Labor Standards Act (“FLSA”), 29 U.S.C. § 216(b), collective action. Though the Motion was essentially unopposed, the parties did disagree as to one issue pertaining to release of claims by currently absent parties, regarding notice required to the class members (Defendant proposed an opt-out Rule 23 notice alone). The Court resolved that dispute by ordering that the parties’ existing agreement and forms be modified to provide both “opt-out” procedures as allowed under Rule 23 and “opt-in” procedures as required by the FLSA.
Explaining that opt-in notice as well as opt-out notice must be provided to class members in such a hybrid action, the Court stated, “According to Defendants, the Rule 23 opt-out procedures, under which potential plaintiffs are bound by the terms of the settlement unless they affirmatively opt out, should apply to both the state law claims and to those claims arising under the FLSA. Plaintiffs disagree arguing that, while Rule 23 applies to their state law claims, the FLSA requires potential plaintiffs to opt-in to this action in order to release any claims they may have under the FLSA. The Court agrees with Plaintiffs.
In a collective action brought under the FLSA, “[n]o employee shall be a party plaintiff to any such action unless he gives his consent in writing to become such a party and such consent is filed in the court in which such action is brought.”29 U.S.C. § 216(b). Congress enacted this provision for the purpose of “limiting private FLSA plaintiffs to employees who asserted claims in their own right and freeing employers of the burden of representative actions.” Hoffman-La Roche Inc. v. Sperling, 493 U.S. 165, 173 (1989).
Conversely, a class action brought pursuant to Rule 23(b)(3) mandates notice informing potential plaintiffs that they can avoid being bound by the terms of a settlement or judgment if they so inform the court. SeeFed.R.Civ.P. 23(c)(2)(B)(v). Thus, a plaintiff that does not affirmatively “opt-out” from the class may be bound by the disposition of the case, regardless of whether he received actual notice. Amchem Products, Inc. v. Windsor, 521 U.S. 591, 614-15 (1997).
In Kakani v. Oracle Corp., the Northern District examined the relationship between the two regimes and held that the use of “opt-out” notice would violate the FLSA.2007 WL 1793774, at *7 (N.D. Cal. June 19, 2007). That court stated that it would have been “unconscionable to try to take away the FLSA rights of all workers, whether or not they choose to join in affirmatively.”Id. (emphasis in original).
Defendants’ authority to the contrary is inapposite. First, Defendants cite Hoffman-La Roche Inc. for the proposition that district courts possess discretion over the procedural methods used to join multiple parties in a single case. However, Defendants interpret Hoffman-La Roche too broadly. That case merely established that district courts may authorize notification of potential plaintiffs regarding the opportunity to “opt-in” to a collective action. 493 U.S. at 169. Hoffman La Roche does not stand for the proposition that this Court may substitute Rule 23 “opt-out” notice for the “opt-in” notice expressly required by 29 U.S.C. § 216(b).
Defendants also cite two district court opinions, one in which the court stated without analysis that “opt-out” procedures would be used to settle both FLSA and state law claims, and one in which the federal court simply refused to enjoin a state court from releasing FLSA claims as part of a settlement that utilized “opt-out” notice. Frank v. Eastman Kodak Co., 228 F.R.D. 174, 179 (W.D.N.Y.2005); Dibel v. Jenny Craig, Inc., 2007 WL 2381237, at * 1 (S.D. Cal Aug. 10, 2007). This Court finds neither of these cases persuasive and now holds that “opt-in” procedures must be provided for the release of the instant FLSA claims.
D.N.J.: Defendant’s Motion To Dismiss Opt-out NJWL Claims As Incompatible With FLSA Opt-in Claims Denied At Pleading Stage
Perry v. Freedom Mortg. Corp.
This case was before the Court on Defendant’s motion to dismiss or strike count II of Plaintiffs Complaint, which alleged overtime law violations pursuant to the New Jersey Wage Law (“NJWL”). The Court denied Defendant’s motion, explaining that it was premature at the pleading stage. This case is of note, because there is conflict of authority within the 3rd Circuit, as to whether Rule 23 “opt-out” classes and 216(b) “opt-in” classes can ever be brought together, or whether the Court should necessary deny its inherent supplemental authority necessarily in such cases.
“The underlying Complaint in this case is a putative class claim, filed by Plaintiff, contending that Freedom violated the Fair Labor Standards Act (“FLSA”), 29 U.S.C. § 201 et seq. and the New Jersey’s Wage Law (“NJWL”), N.J.S.A. 34:11-56a et seq. by improperly classifying mortgage loan officers to prevent them from receiving overtime pay for work in excess of 40 hours a week. In its motion to dismiss Plaintiff’s NJWL claim, Freedom argues that Plaintiff’s FLSA and NJWL claims are legally incompatible. This Court concurs with and adopts Judge Linares’ reasoning in Freeman v. Hoffman-Laroche, Inc. No. 07-1503, 2007 U.S. Dist. LEXIS 92589, at * 70*10 (N.J.D. Dec. 18, 2007), determining that dismissal of a cause of action under NJWL solely for “inherent incompatibility” with FLSA is not appropriate.
Freedom’s additional argument is that the Court should dismiss Count II because Plaintiff cannot establish the “superiority” test required for class certification under Federal Rule of Civil Procedure 23(b)(3). The Court holds that this argument is premature. The parties have conducted no discovery. No motions for class certification have been filed. The Court will be in a much better position to address this issue at the class certification stage.”