Overtime Law Blog

Home » Retaliation

Category Archives: Retaliation

3d Cir.: FLSA Retaliation Provisions Protect Anticipated Collective Action Opt-ins

Uronis v. Cabot Oil & Gas Corp.

Resolving an issue of first impression, the Third Circuit recently held that a job applicant who was a potential member of a collective action, was entitled to the protections of the FLSA anti-retaliation provisions.

The FLSA prohibits discrimination against employees who have engaged in “protected activity” which, in part, includes having “testified” or being “about to testify” in any FLSA-related proceeding. 29 U.S.C. § 215(a)(3). However, until the Third Circuit’s recent decision, it was unclear whether an employee or potential employee’s status as a potential member of a collective action protected him or her from retaliation under the FLSA. The Third Circuit held that it does, and reversed the lower court’s opinion which had dismissed the Complaint and held that it did not.

In this case, a former coworker of plaintiff Matthew Uronis filed a collective action lawsuit against both Cabot Oil & Gas Corporation and a transport and rental company, claiming that the two companies were joint employers and that they failed to properly pay overtime to members of the class, in violation of the FLSA, in February 2019. Uronis, who was similarly employed by the same transport and rental company (and arguably jointly employed by Cabot), was allegedly similarly situated to the named-Plaintiff in that case, based on the definition of the putative collective action contained within the complaint in the initial case.

Subsequent to February 2019, in August 2019, Uronis alleged that he applied for a position with GasSearch Drilling Services Corporation (GDS), a subsidiary of Cabot. In response, on August 28, 2019, a GDS manager sent Uronis a text message stating that, despite his clear qualifications, GDS could not hire Uronis because he was a putative member of the collective action lawsuit against Cabot and the transport and rental company. That same day, Uronis signed his consent to join the collective action. However, he had not informed anyone at Cabot or GDS that he planned to join the lawsuit.

Following GDS refusal to hire him, based on his status a potential opt-in plaintiff, Uronis filed his own lawsuit, against Cabot and GDS, alleging they violated Section 215(a)(3) of the FLSA when GDS refused to hire him and others because they were “about to testify” in his former coworker’s lawsuit. Uronis referenced the text message from the GDS manager and attached a copy to his Complaint.

In response to the Complaint, the defendants filed a motion to dismiss on the basis that Uronis had not pled conduct constituting protected activity under Section 215(a)(3). The district court agreed, granted the defendants’ motion, and dismissed the case.

The district court concluded that Uronis was not “about to testify” because he had not alleged he was scheduled to provide testimony in the underlying collective action. On appeal, the Third Circuit reversed.

Noting first that “Congress included in the FLSA an antiretaliation provision . . . to encourage employees to assert their rights without ‘fear of economic retaliation [which] might often operate to induce aggrieved employees to quietly accept substandard conditions,” the Third Circuit stated that the FLSA “must not be interpreted or applied in a narrow, grudging manner.” In support of this position, the Court of Appeals cited to the U.S. Supreme Court’s decision in Kasten v. Saint-Gobain Performance Plastics Corporation, 563 U.S. 1 (2011), in which the Court held that an oral complaint of an FLSA violation constitutes protected activity, even though the statute (in a companion subsection) refers to a complaint that has been “filed,” which most commonly is interpreted to require a written document.

In so holding, the Supreme Court reasoned that to limit the scope of Section 15(a)(3) to the filing of written complaints would foul Congress’ intent by ‘prevent[ing] Government agencies from using hotlines, interviews, and other oral methods of receiving complaints’ and ‘discourag[ing] the use of desirable informal workplace grievance procedures to secure compliance with the [FLSA].’” The Court further noted that it had interpreted an analogous provision of the National Labor Relations Act (NLRA) to protect conduct not explicitly listed in that NLRA, specifically, to extend anti-retaliation protection to individuals who merely had participated in a National Labor Relations Board investigation, even though the language of the NLRA itself referred only to those who had “filed charges or given testimony.”

The Court of Appeals further noted that previously, in Brock v. Richardson, 812 F.2d 121 (3d Cir. 1987), it had extended the protections of Section 215(a)(3) to individuals whom the employer believed had filed a complaint with the Department of Labor, even though they had not actually done so. “Even though the statute could be narrowly read to not include retaliation based on perception, such retaliation ‘creates the same atmosphere of intimidation’ as does discrimination based on situations explicitly listed in Section 15(a)(3),” the Court of Appeals reiterated, adding that “[s]uch an atmosphere of intimidation is particularly repugnant to the purpose of the FLSA in the context of collective actions.” Similarly, “[i]f employers can retaliate against an employee because the employer believes the employee has or will soon file a consent to join an FLSA collective action, this enforcement mechanism – and employee protection – will be gutted.

However, added the Third Circuit, “Section [2]15(a)(3) is not a per se bar against any adverse employment action against an employee who is or might soon be a collective action member. Rather, it bars discrimination because of protected activity.” Again citing to Kasten, the Court of Appeals emphasized that to qualify as arguably protected activity, the employer must be given “fair notice” that a reasonably detailed and clear complaint, whether oral or written, has been asserted (as in Kasten) or, as here, that the individual was “about to testify” in an FLSA proceeding (as the Third Circuit now broadly interprets that phrase) and there must be plausible evidence (or allegations) that the employer was aware of the conduct.

Reversing the district court, the Third Circuit explained:

The reasoning of Kasten and Brock compel the conclusion that to ‘testify’ under Section [2]15(a)(3) includes the filing of an informational statement with a government entity. A consent to join a collective action is just that: it is an informational statement (that an employee is similarly situated to the named plaintiff with respect to the alleged FLSA violation) made to a government entity (the court).

Accordingly, concluded the Third Circuit, “an employee testifies under Section [2]15(a)(3) when the employee files a consent to join an FLSA collective action.”

Likewise, the Court of Appeals held that “‘about to testify’ includes testimony that is impending or anticipated, but has not been scheduled or subpoenaed.” As set forth in several other district court decisions, “‘about to’ . . . includes activity that is ‘reasonably close to, almost, on the verge of,’ or ‘intending to do something or close to doing something very soon.’” This includes individuals who, like Uronis, intended to soon file his consent to join the collective action and testify in that lawsuit, the Third Circuit noted. Finally, the Court of Appeals held, Uronis had sufficiently pled – as evidenced by the text to him from the GDS manager – not only that Cabot and GDS were aware, or at least assumed, that he would join the collective action, but that GDS was flatly refusing to hire him for this very reason. Based on these allegations, “[i]t is plausible that [GDS would not hire Uronis] because they anticipated [he] and his former co-workers would soon file consents to join the putative collective action, or otherwise provide evidence relating to it.” Accordingly, the Third Circuit said, the complaint should not have been dismissed on the pleadings and the case was due to be remanded for further consideration.

Congratulations to Morgan & Morgan attorney Angeli Murthy for her outstanding advocacy on behalf of Uronis! Ms. Murthy was supported by the Department of Labor who filed amicus in support of Uronis as well.

Click Uronis v. Cabot Oil & Gas Corp. to read the entire decision.

9th Cir.: Employer’s Attorney Can Be Sued for Retaliation as a “Person Acting Directly or Indirectly” in Employer’s Interest

Arias v. Raimondo

This case presented an issue of first impression: Can an employer’s attorney be held liable for retaliating against his client’s employee because the employee sued his client for violations of workplace laws? The district court held that he could not and dismissed the claim. On appeal the Ninth Circuit disagreed and reversed.  Specifically, the Ninth Circuit held that as a “person acting directly or indirectly” in the employer’s interest, the employer’s attorney could be subject to liability under 29 U.S.C. § 215.

In the case, the defendant-employers had hired the plaintiff-employee, an undocumented immigrant without verifying his immigration status or his right to work in the United States.  Although not explicitly stated, the Ninth Circuit’s opinion strongly implies that the defendants intentionally neglected to complete an I-9 form or verify plaintiff’s status because it knew he was not legally permitted to work in the United States.

After working for defendants for 11 years, in 2006, plaintiff filed suit in California state court against defendants, alleging that defendants violated a multitude of employment laws, and alleged among other things that defendants failed to provide him with legally mandated rest breaks and failed to pay him legally mandated overtime premiums.

The Ninth Circuit recited the following facts regarding the alleged retaliation, all taken from plaintiffs subsequent lawsuit alleging illegal retaliation that was the subject of the Ninth Circuit’s opinion:

On June 1, 2011, ten weeks before the state court trial, the Angelos’ attorney, Anthony Raimondo, set in motion an underhanded plan to derail Arias’s lawsuit. Raimondo’s plan involved enlisting the services of U.S. Immigration and Customs Enforcement (“ICE”) to take Arias into custody at a scheduled deposition and then to remove him from the United States. A second part of Raimondo’s plan was to block Arias’s California Rural Legal Assistance attorney from representing him. This double barrel plan was captured in email messages back and forth between Raimondo, Joe Angelo, and ICE’s forensic auditor Kulwinder Brar.

On May 8, 2013, Arias filed this lawsuit against Angelo Dairy, the Angelos, and Raimondo in the Eastern District of California. Arias alleged that the defendants violated section 215(a)(3) of the Fair Labor Standards Act (“FLSA”), 29 U.S.C. § 201 et seq.

Arias’s theory of his case is that Raimondo, acting as the Angelos’ agent, retaliated against him in violation of section 215(a)(3) for filing his original case against Raimondo’s clients in state court . Raimondo’s sole legal defense is that because he was never Arias’s actual employer, he cannot be held liable under the FLSA for retaliation against someone who was never his employee.

As noted by the court, Angelo Dairy and its owners settled their part of this case at the early stages of its existence.

The district court dismissed plaintiff’s claims against the defendants’ attorney holding that he was not covered under the FLSA’s retaliation provisions because he was not plaintiff’s employer.  Noting that the FLSA’s retaliation provision defines those subject to liability in a much broader way than the underlying definition of employer (which is broad to begin with) the Ninth Circuit reversed.

Discussing the issue before it the court explained:

Notwithstanding section 215(a)(3)’s reference to “any person,” section 203(a)’ s inclusion of a legal representative as a “person,” and section 203(d)’s plain language defining “employer,” the district court granted Raimondo’s motion to dismiss pursuant to Federal Rule of Civil Procedure 12(b)(6). The court did so without the benefit of oral argument, concluding that because Arias “ha[d] not alleged that [Raimondo] exercised any control over [his] employment relationship,” Raimondo as a matter of law could not be Arias’s employer.

The Ninth Circuit rejected this reasoning noting that the statutory definition of those who may be subject to liability under the FLSA’s retaliation provision include a broader spectrum of people:

Section 215(a)(3), an anti-retaliation provision, makes it unlawful “for any person … to discharge or in any other manner discriminate against any employee because such employee has filed any complaint … under or related to this chapter.” The FLSA defines the term “person” to include a “legal representative.” Id. § 203(a). Section 216(b) in turn creates a private right of action against any “employer” who violates section 215(a)(3); and the FLSA defines “employer” to include “any person acting directly or indirectly in the interest of an employer in relation to an employee.” Id. §§ 203(d), 216(b).

Controversies under FLSA sections 206 and 207 that require a determination of primary workplace liability for wage and hour responsibilities and violations, on one hand, and controversies arising from retaliation against employees for asserting their legal rights, on the other, are as different as chalk is from cheese. Each category has a different purpose. It stands to reason that the former relies in application on tests involving economic control and economic realities to determine who is an employer, because by definition it is the actual employer who controls substantive wage and hours issues.

Retaliation is a different animal altogether. Its purpose is to enable workers to avail themselves of their statutory rights in court by invoking the legal process designed by Congress to protect them. Robinson v. Shell Oil Co., 519 U.S. 337, 346 (1997) (the “primary purpose of antiretaliation provisions” is to “[m]aintai[n] unfettered access to statutory remedial mechanisms”).

This distctive purpose is not served by importing an “economic control” or an “economic realities” test as a line of demarcation into the issue of who may be held liable for retaliation. To the contrary, the FLSA itself recognizes this sensible distinction in section 215(a)(3) by prohibiting “any person” –not just an actual employer – from engaging in retaliatory conduct. By contrast, the FLSA’s primary wage and hour obligations are unambiguously imposed only on an employee’s de facto “employer,” as that term is defined in the statute. Treating “any person” who was not a worker’s actual employer as primarily responsible for wage and hour violations would be nonsensical…

Congress made it illegal for any person, not just an “employer” as defined under the statute, to retaliate against any employee for reporting conduct “under” or “related to” violations of the federal minimum wage or maximum hour laws, whether or not the employer’s conduct does in fact violate those laws. … Moreover, “the remedial nature of the statute further warrants an expansive interpretation of its provisions. …”  Id. at 857 (second omission in original) (quoting Herman v. RSR Sec. Servs., 172 F.3d 132, 139 (2d Cir. 1999)).

In line with this reasoning, the court concluded:

The FLSA is “remedial and humanitarian in purpose. We are not here dealing with mere chattels or articles of trade but with the rights of those who toil, of those who sacrifice a full measure of their freedom and talents to the use and profit of others …. Such a statute must not be interpreted or applied in a narrow, grudging manner.” Tenn. Coal, Iron & R.R. Co. v. Muscoda Local No. 123, 321 U.S. 590, 597 (1944).

Accordingly, we conclude that Arias may proceed with this retaliation action against Raimondo under FLSA sections 215(a)(3) and 216(b). Raimondo’s behavior as alleged in Arias’s complaint manifestly falls within the purview, the purpose, and the plain language of FLSA sections 203(a)203(d), and 215(a)(3).

Our interpretation of these provisions is limited to retaliation claims. It does not make non-actual employers like Raimondo liable in the first instance for any of the substantive wage and hour economic provisions listed in the FLSA. As illustrated by the Court’s opinion in Burlington, the substantive provisions of statutes like Title VII and the FLSA, and their respective anti-retaliation provisions, stand on distinctive grounds and shall be treated differently in interpretation and application. Ultimately a retaliator like Raimondo may become secondarily liable pursuant to section 216(b) for economic reparations, but only as a measure of penalties for his transgressions.

Click Arias v. Raimondo to read the entire opinion.

N.D.Ga.: Defendant Barred from Unilateral Meetings With Putative Class Members Outside of Formal Discovery Process, Absent Detailed Disclosures to Alleviate Concerns re Chilled Participation and/or Retaliation

Wilson v. Regions Financial Corporation 

This case was before the court for consideration of the parties’ Joint Statement regarding restrictions on communications with putative class members, as required by L.R. 23.1(C)(2) of the Northern District of Georgia.

The specific issue raised by the parties’ Joint Submission was explained as follows:

In the Joint Statement, Plaintiffs raise a concern that Defendants will question putative class members about a policy requiring employees to lodge contemporaneous internal complaints about incorrect pay (“Complaint Policy”). Plaintiffs fear that if representatives of Defendants raise the Complaint Policy in communications with putative plaintiffs, the putative plaintiffs will believe that their failure to have lodged a contemporaneous complaint about incorrect pay may have been a violation of company policy that could result in their termination from employment. In its portion of the Joint Statement, Defendants do not deny an intention to make such inquiries of employees.

Initially the court discussed the basic applicable law:

[A]n order limiting communication between parties and potential class members should be based on a clear record and specific findings that reflect a weighing of a need for limitation and the potential interference with the rights of the parties. Only such a determination can insure that the court is furthering, rather than hindering, the policies embodied in the Federal Rules of Civil Procedure, especially Rule 23.

Gulf Oil Co. v. Bernard, 452 U.S. 89, 101–102, 101 S.Ct. 2193, 68 L.Ed.2d 693 (1981). “Unsupervised, unilateral communications with the plaintiff class sabotage the goal of informed consent by urging exclusion on the basis of a one-sided presentation of the facts, without opportunity for rebuttal. The damages from misstatements could well be irreparable.” Kleiner v. First Nat’l Bank of Atlanta, 751 F.2d 1193, 1203 (11th Cir.1985).

Based on its conclusion that there were inherent risks in the anticipated questioning by the defendants, the court held that the defendants were barred from communicating with former employee putative class members regarding the subject matter of the case, outside of the regular discovery process in the case and without the consent of plaintiff’s counsel. While the court permitted defendants’ counsel to speak with current employees who were putative class members, it set forth detailed prerequisites prior to any such communications, in order to safeguard against defenadnts’ improperly influencing putative class members from exercising their rights under the FLSA:

The Court finds that the risks inherent in the anticipated questioning by Defendants warrant the following limitations on Defendants’ communications with potential class members.

There shall be no communications with any named Plaintiff or with any current or future opt-in Plaintiffs outside the formal discovery process or without the consent of the named Plaintiff’s counsel of record, except-as to any currently employed present or future opt-in Plaintiff-for routine business matters unrelated to this action.

With respect to any presentation of information, including any views or opinions, to any “putative class members” by the Defendants—whether acting through management, counsel, other employees, or any other agent of any kind—that relates to the allegations and claims in this action, whether for the purpose of gathering information in a one-on-one or group basis to defend this action or to address any employee complaints regarding past, current or future compensation practices, such communication shall commence with the following statements:

(a) The person(s) present on the Defendants’ behalf is a Defendant employee or agent acting at the direction of Defendants’ management;

(b) The person(s) present on the Defendants’ behalf is there to address a lawsuit filed against the Defendants, as well as employee complaints, involving allegations that the Defendants failed to pay employees all the wages and overtime they had earned and were entitled to receive;

(c) The lawsuit is a class-action—which means the individual may receive money as a result of the lawsuit;

(d) The allegations of wrongdoing (accurately stated), accompanied by a copy of the Third Amended Complaint;

(e) The “putative class member” is under no obligation to stay, or listen, or speak, or respond;

(f) No record of anyone who does not stay, speak, or respond is being made and no record of who does not stay, speak, or respond will be made at any future time;

(g) No adverse action will be taken if the “putative class member” chooses not to stay, speak, or respond;

(h) No adverse action will be taken if the “putative class member” says, in substance, they believe they not were not properly compensated or did not receive all compensation owed to them, whether or not they complained to anyone about any compensation issues; and

(i) The “putative class member” is free to leave at any time, including at this point.

Click Wilson v. Regions Financial Corporation to read the entire Order Regarding Communications With Putative Class Members.

While the procedural posture of this case was somewhat unique, in that the Northern District of Georgia has a detailed/explicit rule regarding pre-certification communications (and there was a Rule 23 class claim in addition to the FLSA collective action claim), this decision will likely serve as a blueprint for many courts going forward, given the chilling effect unilateral meetings with current and former employees can have, as many courts have previously noted.

Courts Reach Different Conclusions Regarding Whether FLSA Plaintiffs Should Be Allowed to Proceed Anonymously Under Pseudonyms

Although the issue comes up from time to time, there are few decisions discussing whether FLSA plaintiffs and opt-in plaintiffs may proceed with their claims anonymously notwithstanding the federal rules of civil procedure’s requirement that each party identify itself and the FLSA’s requirement under 29 U.S.C. § 216(b) that any person wishing to participate in a collective action file a consent to join.  As discussed here, two recent decisions took up this issue and reached different results, with one court in California permitting exotic dancers to proceed under pseudonyms, while a court in New York denied a similar motion on behalf of “white collar” worker at Bloomberg.

N.D.Cal.: Exotic Dancer Met Burden to Proceed Anonymously

Jane Roes 1-2 v. SFBSC Management, LLC

In the first case, the plaintiffs, a putative class of exotic dancers, requested that they be able to proceed under pseudonyms and the court granted their motion. The plaintiffs ask the court to do two things: First, to allow them to proceed under “Jane Roe” pseudonyms; and, second, to allow future plaintiffs to join this suit by filing their FLSA consents under seal. (ECF No. 17 at 1.) (Plaintiffs in FLSA collective suits must affirmatively “opt in” by filing consent forms. 29 U.S.C. § 216(b).). Noting that filing consents under seal was unnecessary in light of the order allowing each of the plaintiffs to use pseudonyms the court denied the second branch of plaintiffs’ motion.

The court applied a balancing test to reach its holding:

The plaintiffs express a legitimate concern for their privacy and, more compelling for the anonymity analysis, an understandable fear of social stigmatization. The Ninth Circuit has recognized that courts grant anonymity where it is needed to “preserve privacy in a matter of sensitive and highly personal nature.” Advanced Textile, 214 F.3d at 1068 (quoting James v. Jacobson, 6 F.3d 233, 238 (4th Cir.1993)). “In this circuit,” consequently, “we allow parties to use pseudonyms” where this is “necessary” to “protect a person from … ridicule or personal embarrassment.” Advanced Textile, 214 F.3d at 1067–68 (emphasis added).

Arguing against pseudonymity, SFBSC points to 4 Exotic Dancers v. Spearmint Rhino, No. 08–4038, 2009 WL 250054 (C.D.Cal. Jan. 29, 2009). (See ECF No. 19 at 4–5.) The plaintiffs in that case—who, as the case’s name suggests, were also exotic dancers—were denied anonymity where, in SFBSC’s view, they gave the “same reasons” for withholding their real names as the present plaintiffs. (Id. at 4.) SFBSC calls 4 Exotic Dancers “indistinguishable” from this case. (Id.)

The court does not agree that 4 Exotic Dancers compels the denial of anonymity here. That decision does not reflect how this district has understood the law of anonymity. The court in 4 Exotic Dancers cited a decision of this district, Doe v. Rostker, 89 F.R.D. 158 (N.D.Cal.1981), for the proposition that “some embarrassment or economic harm is not enough” to justify anonymity. See
4 Exotic Dancers, 2009 WL 250054, at *3 (citing Rostker, 89 F.R.D. at 162). SFBSC cites Rostker for the same idea. (ECF No. 19 at 3.) But Rostker itself distinguishes those insufficient fears (“some embarrassment or economic harm”) from the following, which justify anonymity:

A plaintiff should be permitted to proceed anonymously in cases where a substantial privacy interest is involved. The most compelling situations involve matters which are highly sensitive, such as social stigmatization …. That the plaintiff may suffer some embarrassment or economic harm is not enough. Rostker, 89 F.R.D. at 162 (emphases added). This district has thus considered “social stigmatization” among the “most compelling” reasons for permitting anonymity. This is consistent with the Ninth Circuit’s instruction in Advanced Textile that anonymity is permitted where the subject matter of a case is “sensitive and highly personal,” and where disclosing a party’s identity threatens to subject them to “harassment, … ridicule or personal embarrassment.” See Advanced Textile, 214 F.3d at 1067–68.

The plaintiffs have identified an adequate threat of personal embarrassment and social stigmatization that, under Advanced Textile, militates for allowing them to proceed under Jane Roe pseudonyms. To the extent that 4 Exotic Dancers points to a different conclusion, the court respectfully disagrees with that decision.

This case moreover falls into what may be roughly called the area of human sexuality. As SFBSC recognizes (see ECF No. 19 at 4–5), courts have often allowed parties to use pseudonyms when a case involves topics in this “sensitive and highly personal” area. The most famous case of this sort—which, however, did not address the question of pseudonymity—is certainly Roe v. Wade, 410 U.S. 113, 93 S.Ct. 705, 35 L.Ed.2d 147 (1973). But there are many others. E.g., United States v. Doe, 488 F.3d 1154, 1155 n. 1 (9th Cir.2007) (allowing defendant convicted of producing child pornography to use pseudonym); Doe v. Megless, 654 F.3d 404, 408 (3rd Cir.2011) (“Examples of areas where courts have allowed pseudonyms include … abortion, … transexuality … and homosexuality.”) (quotation omitted) (cited by SFBSC at ECF No. 19 at 4–5); John Doe 140 v. Archdiocese of Portland, 249 F.R.D. 358, 361 (D.Or.2008) (plaintiff alleging that he was sexually abused as minor allowed to proceed anonymously); Doe v. United Serv. Life Ins. Co., 123 F.R.D. 437 (S.D.N.Y.1988) (sexual orientation); Doe v. Deschamps, 64 F.R.D. 652 (D.Mont.1974) (abortion; collecting older cases).

The court does not mean to equate the various specific topics that these cases subtend. A broad brush will do: For purposes of the anonymity discussion, it is enough to observe that courts have regularly responded to the especially sensitive nature of this area and have been willing to grant parties anonymity. The same judicial instinct should apply here. SFBSC’s contention that the business of nude and semi-nude dancing “simply does not fall within” the field of “sexuality” (ECF No. 19 at 5) is unconvincing.

The court also reasoned that each of the dancers faced a real potential harm, should they be compelled to disclose their actual identities:

The court must also consider the plaintiffs’ claim that disclosing their identities would subject them to potential harm, both physical and with regard to their careers. (See ECF No. 17 at 3–4.) The Ninth Circuit has again provided guidance: “[I]n cases where, as here, pseudonyms are used to shield the anonymous party from retaliation, the district court should determine the need for anonymity by evaluating the following factors: (1) the severity of the threatened harm, (2) the reasonableness of the anonymous party’s fears; and (3) the anonymous party’s vulnerability to such retaliation.” Advanced Textile, 214 F.3d at 1068. The plaintiffs “are not required to prove that the defendants intend to carry out the threatened retaliation. What is relevant is that plaintiffs were threatened, and that a reasonable person would believe that the threat might actually be carried out.” Id. at 1071. While this language specifically addresses career retaliation by an employer defendant, its terms and concerns usefully frame the general question of whether a plaintiff seeking anonymity faces any harm. The latter is, again, a recognized basis for granting anonymity. E.g., id. at 1068 (anonymity is allowed where identification “creates a risk of … physical or mental harm”); Doe, 655 F.2d at 922 n. 1 (using pseudonyms where informant “faced a serious risk of bodily harm”).

The plaintiffs express reasonable concerns that disclosing their identities would threaten them with both career and possibly physical harm. (ECF No. 17 at 3–4.) For such “privacy and personal[-]safety reasons,” they explain, at SFBSC’s nightclubs, “it is customary for the exotic dancers to use … stage names.” (Id. at 3.) SFBSC does not deny this: either the practice or its rationale. Finally, SFBSC has “agree[d] that that the public disclosure of an exotic dancer’s true identity presents substantial risk of harm.” (ECF No. 26 at 12 (emphasis added).) This consideration favors allowing the plaintiffs to proceed pseudonymously.

Finally, the court concluded that any potential prejudice to the defendants and right to judicial access was outweighed by the potential harm the plaintiffs faced. Thus, the court granted the plaintiffs’ motion.

Click Jane Roes 1-2 v. SFBSC Management, LLC to read the entire Order on Anonymity & Sealing.

S.D.N.Y.: White Collar Worker Suing Bloomberg Failed to Meet Burden to Proceed Anonymously

Michael v. Bloomberg L.P.

In the second case, the plaintiff was willing to provide his real name to Bloomberg, but refused to do so absent an agreement from Bloomberg to keep his name confidential. Thus, by his motion, the plaintiff requested that the court permit the plaintiff to proceed pseudonymously, and plaintiff additionally asked that; (1) plaintiff’s identity be filed under seal with the court; (2) plaintiff’s name, address, and other identifying information be supplied to Bloomberg; and (3) Bloomberg be directed not to disclose plaintiff’s identity or make negative public remarks concerning plaintiff. Holding that the plaintiff had failed to meet his burden of proof to warrant the requested relief, the court denied plaintiff’s motion.

In opposition, Bloomberg argued that plaintiff’s privacy concerns were too vague and that plaintiff’s request was contrary to the written notice requirement of 216(b) of the FLSA. The court agreed and reasoned:

Bloomberg has the better of the argument. Under Rule 10(a) of the Federal Rules of Civil Procedure, a complaint must “name all the parties.” Fed.R.Civ.P. 10(a). “This requirement, though seemingly pedestrian, serves the vital purpose of facilitating public scrutiny of judicial proceedings and therefore cannot be set aside lightly.” Sealed Plaintiff v. Sealed Defendant, 537 F.3d 185, 188–89 (2d Cir. 2008) (internal quotations omitted). The use of pseudonyms “runs afoul of the public’s common law right of access to judicial proceedings, a right that is supported by the First Amendment.” Doe v. Del Rio, 241 F.R.D. 154, 156 (S.D.N.Y.2006) (internal quotations omitted); see also Doe I v. Four Bros. Pizza, No. 13 CV 1505 VB, 2013 WL 6083414, at *9–10 (S.D.N.Y. Nov. 19, 2013) (rejecting FLSA plaintiffs’ request for anonymity despite threat of retaliation from employer).

The court applied a similar balancing of interests test as the court in the Jane Roe case, but reached the opposite conclusion on the facts before it:

The Court has balanced plaintiff’s possible interest in anonymity against the potential prejudice to defendants and the public’s interest in disclosure, and concludes that the factors weigh in favor of denying plaintiff’s motion. There is no issue here of physical retaliation or mental harm against plaintiff. Nor is this the type of unusual case involving matters of a highly sensitive or personal nature—i.e., claims involving sexual orientation, pregnancy, or minor children—in which courts have justified anonymous plaintiffs proceeding pseudonymously. To depart in this case from the general requirement of disclosure would be to hold that nearly any plaintiff bringing a lawsuit against an employer would have a basis to proceed pseudonymously. The court declines to reach such a holding.

The court also rejected plaintiff’s middle ground position that he be permitted to disclose his identity to Bloomberg, under the condition that they maintain same confidentiality, in the name of judicial access.

Click Michael v. Bloomberg L.P. to read the entire Opinion.

5th Cir.: Department Head Who Notified Employer of Potential FLSA Violations Did Not Engage in Protected Activity, Because She Did Not “Step Outside Her Normal Job Role”

Lasater v. Texas A & M University-Commerce

This case was before the Fifth Circuit on appeal of an order awarding the defendant summary judgment on plaintiff’s FLSA retaliation claim. Specifically, the plaintiff, a former department head for the defendant asserted that she was terminated for raising concerns regarding the defendant’s payroll policies (and failure to comply with the FLSA) to an independent auditor and later her supervisors. The court below held that plaintiff failed to allege that she had engaged in protected activity, because she was merely performing her duties for defendant when she reported her concerns regarding non-compliance. The Fifth Circuit agreed and affirmed the award of summary judgment for the defendant.

The Fifth Circuit recited the following factual history:

This case arises from TAMUC’s termination of Lasater’s employment in December 2009. From March 2006 to December 2009, Lasater was employed as the Director of the Office of Financial Aid and Scholarships at TAMUC. Prior to that, Lasater worked in the Financial Aid Department at Texas A & M University–Corpus Christi for 17 years.

In November 2008, Lasater met with Lori Ellison, an outside auditor from The Texas A & M University System who was conducting a regularly scheduled audit. During the meeting, Lasater alleges that Ellison asked her if she had any “concerns” and Lasater told her that “there were some things that were of concern to me and I felt like I needed to, in good faith, report some things that I thought were violations, including comp time.” Lasater alleges that in the course of the conversation with Ellison she discussed a number of problems related to the university’s employee compensatory time (“comp time”) policy. First, she was concerned that comp time had to be used before vacation time; because vacation time would be lost if not taken before the end of the year, this could in turn cause employees to lose accrued comp time. She also voiced her concerns that employees in her department had accrued large balances of comp time and were too busy for Lasater to allow them to timely use their comp time and still meet the demands of her office. Third, she specifically expressed her concerns about one of her employees, Diane Lewis, who had been promoted to a position within the department exempt from the overtime requirements of the FLSA and TAMUC had declined Lasater’s request that Lewis be paid for her accrued comp time after her promotion. Finally, Lasater alleges that she reported to Ellison her concerns about the operation of TAMUC’s Financial Services division, including its failure to “draw down” its allotted federal funds and the fact that it was not performing monthly reconciliations related to federal funds for financial aid. At the time of the meeting Lasater did not suggest to Ellison that TAMUC policies regarding comp time violated the FLSA or refer to any applicable law she believed had been violated.

Relevant TAMUC policy provides that employees who are not exempt under the FLSA may earn comp time for working more than forty hours per week; the policy requires component universities to compensate employees by giving them time off rather than paying them overtime. TAMUC policy also provided that administrators who supervise staff were to ensure that no employee accrue a comp time balance in excess of 240 hours and that, if necessary, employees were to use comp time before taking vacation time. Lasater, as a supervisor, had the responsibility for approving, and the authority to deny, employee leave requests. The policy also states that an employee who transfers between departments may, upon the department managers’ agreement, be paid for accumulated comp time but no policy required payment for comp time to an employee promoted within a department. TAMUC policy additionally provides that inquiries or interpretations of FLSA legal issues should be directed to the System Human Resources Office or the Office of General Counsel.

In December 2008, Ellison reported Lasater’s concerns up the chain of command to Lasater’s supervisor, Stephanie Holley; Mary Hendrix, Vice President for Student Access and Success; and Dan Jones, President of TAMUC. Lasater alleges that shortly after her conversation with the auditor Holley and Hendrix demanded to know why she had reported the comp time issue and began to act colder toward her, harassed her, increased their scrutiny of her, and forced her to take unqualified employees.

In May 2009, Holley gave Lasater a favorable evaluation, and in August, Lasatar received a merit raise. In September 2009, Holley and Hendrix met with Lasater and discussed their concerns about the need for a training manual, the role of Lewis, and how Lasater was not “allowing other people into [her] inner circle.” In early December 2009, Rose Giles, one of Lasater’s subordinates, approached Holley to discuss her frustration with the fact that she did not feel Lasater’s staff was properly trained. Holley then spoke with Susan Grove, the Assistant Director of Scholarships, who alleged that Lasater did not adequately train her staff, spent most of her time with co-employee Lewis to the exclusion of all others, repeatedly arrived late, and had a tendency to “lash out.” Grove stated that she was so distressed by Lasater’s management style that she was planning to leave the university. On December 15, 2009, Holley and Hendrix informed Lasater that her employment was terminated.

Discussing the type of behavior a management-level employee must engage in, for such behavior/activity to constitute “protected activity,” the court explained:

[T]his circuit has recognized that an employee’s communication does not constitute a complaint unless that employee “somehow steps outside of his normal job role” so as to make clear to the employer that the employee is “taking a position adverse to the employer.” Id. at 627–28. Such a requirement is “eminently sensible for management employees” because a managerial position “necessarily involves being mindful of the needs and concerns of both sides and appropriately expressing them.” Id. at 628. Thus, voicing “concerns is not only not adverse to the company’s interests, it is exactly what the company expects of a manger.” Id. (emphasis in original). Without such a requirement, “nearly every activity in the normal course of a manager’s job would be protected activity.” Id.

Illustratively, a personnel director responsible for monitoring compliance with workplace laws did not engage in protected activity when she discussed her “concerns about the company’s possible FLSA violations” with the president of the company. McKenzie v. Renberg’s Inc., 94 F.3d 1478, 1481 (10th Cir.1996). The Tenth Circuit found her “job responsibilities” included discussing wage issues and that assisting the company with FLSA compliance was “completely consistent with her duties.” Hagan, 529 F.3d at 627 (quoting McKenzie, 94 F.3d at 1487). It held that it is “the assertion of statutory rights (i.e., the advocacy of rights) by taking some action adverse to the company … that is the hallmark of protected activity.” Id. (emphasis in original) (quoting McKenzie, 94 F.3d at 1486). Thus because McKenzie “never crossed the line from being an employee merely performing her job as personnel director to an employee lodging a personal complaint about the wage and hour practices of her employer and asserting a right adverse to the company,” her discussion of her FLSA violation concerns with the president could not reasonably “be perceived as directed towards the assertion of rights protected by the FLSA.” Id. (emphasis in original) (quoting McKenzie, 94 F.3d at 1486–87).

Applying this standard to the facts at bar, the court held that the plaintiff failed to show she stepped outside of her normal job role in reporting her concerns regarding the defendant’s comp time system to the auditor and to her supervisors. Further, the court noted that even if she had, her actions could not reasonably be construed to have asserted FLSA rights on behalf of herself or the employees who were the subject of her conversations. Thus, the court affirmed summary judgment for the defendant.

Click Lasater v. Texas A & M University-Commerce to read the entire per curiam decision.

D.Md.: Compensatory Damages for Emotional Distress Are Available Under §§ 215 and 216(b) for Retaliation Claims

Randolph v. ADT Sec. Services, Inc.

This case was before the court on several pretrial motions of the parties. As discussed here, among the issues briefed before the court was whether compensatory damages are available to a plaintiff-employee pursuing a claim of retaliation under the FLSA. The court answered this question in the affirmative, noting the issue was one of first impression within the Fourth Circuit.

Restating the parties’ respective positions, the court explained:

ADT maintains that, as a matter of law, Plaintiffs are precluded from seeking emotional distress damages because such damages are unavailable under “the very similar damages provision of the ADEA.” (ECF No. 101, at 18). Plaintiffs disagree, pointing to several circuit court opinions upholding such awards. On this issue, Plaintiffs have the better end of the argument.

The court noted that the issue presented was one of first impression in the Fourth Circuit and then examined case law from other circuit and district level courts:

Neither the Fourth Circuit nor any district court within this circuit has previously determined whether a plaintiff may recover compensatory damages from emotional distress in an FLSA action. Four circuit courts of appeal—the Sixth, Seventh, Eighth, and Ninth Circuits—have, however, either directly or indirectly addressed the issue, and all have permitted the recovery of emotional distress damages. Moore v. Freeman, 355 F.3d 558, 563–64 (6th Cir.2004) (explaining that “consensus on the issue of compensatory damages for mental and emotional distress [in FLSA cases] seems to be developing”); Broadus v. O.K. Indus., Inc., 238 F.3d 990, 992 (8th Cir.2001) (upholding a compensatory award that may have included damages for emotional distress); Lambert v. Ackerley, 180 F.3d 997, 1011 (9th Cir.1999) (affirming an award of emotional distress damages in an FLSA action); Avitia v. Metro. Club of Chi., Inc., 49 F.3d 1219, 1226–30 (7th Cir.1995) (reducing an award for emotional distress damages after finding the award excessive, but noting that such damages are available under the FLSA (citing Travis, 921 F.2d at 111–12)).

The compensatory nature of the remedies in § 216(b) supports the outcome in these cases. “The [FLSA’s] statutory scheme contemplates compensation in full for any retaliation employees suffer from reporting grievances.” Moore, 355 F.3d at 563 (citing Snapp, 208 F.3d at 934; Lanza, 97 F.Supp.2d at 740); Republic Franklin Ins. Co. v. Albemarle Cnty. Sch. Bd., 670 F.3d 563, 568 (4th Cir.2012) (citing Snapp and Lanza for the proposition that the relief provided in § 216(b) “is compensatory in nature”). The text of § 216(b) expressly provides for “such legal or equitable relief as may be appropriate to effectuate” this compensatory purpose, employing the broad phrase “without limitation” to indicate that the enumerated remedies within that section are not exhaustive. 29 U.S.C. § 216(b). “[L]ike the forms of relief mentioned [therein], damages for mental anguish are intended to compensate the injured party for harm suffered.”   Moore, 355 F.3d at 564.

Certainly, an argument could be made that the availability of liquidated damages [under § 216(b) ] would be sufficient to fully compensate a plaintiff with proof of actual economic damages but only minor, subjective mental anguish occasioned by an employer’s violation of the [FLSA]. However, in a case involving only nominal economic losses but proved retaliation consisting of concerted, directed harassment, resulting in grave emotional distress, such nominal economic damages or the available doubling of those damages would be insufficient to make the plaintiff whole. Damages for mental anguish would be the necessary compensatory legal relief “appropriate to effectuate the purposes of [the anti-retaliation provision].” Bogacki v. Buccaneers Ltd. P’ship, 370 F.Supp.2d 1201, 1203 (M.D.Fla.2005) (quoting 29 U.S.C. § 216(b)); cf. Snapp, 208 F.3d at 937 (reasoning that “district courts may have to exercise some creativity in awarding relief in retaliation cases” beyond those forms set forth in the statutory text).

The court then rejected the contrary holdings of courts that had held ADEA cases to be persuasive based upon the fact that the ADEA was patterned after the FLSA, noting that such reasoning:

fails to consider that the relief authorized under both statutes must be determined ‘not in isolation, but in conjunction with the other provisions of the Act[s], the policies they further, and the enforcement framework[s] they envision.’ Dean, 559 F.2d at 1038.” The court further distinguished the ADEA legislative framework by pointing out that “[t]he ADEA includes an administrative conciliation process that is critical to its enforcement framework… [and] [l]ooking to this process, circuit courts have repeatedly held that emotional distress damages are unavailable in ADEA actions because they would impede mediation and conciliation by discouraging early resolution of ADEA claims.

Thus, the court concluded:

Because “full compensation is the evident purpose and paramount policy” in an FLSA retaliation action, “the more reasoned approach” would permit a plaintiff who makes a proper showing to recover damages for emotional distress. Id.; Moore, 355 F.3d at 563–64. Neither party here has addressed the strength or weakness of Plaintiffs’ evidence of alleged emotional distress. Until the parties do so at trial, the court cannot conclude—as a matter of law—”that damages for mental anguish should be disallowed.” Id. at 1205–06.  Plaintiffs will be permitted to seek emotional distress damages through a jury trial, and their motion on this issue will, therefore, be granted.

In light of the continuing disagreement of courts regarding this issue, this might be one to watch for further appellate level developments in the future.

Click Randolph v. ADT Sec. Services, Inc. to read the entire Memorandum Opinion.

4th Cir.: Intracompany Complaints Regarding FLSA Violations Are Protected Activity Within the Meaning of Anti-Retaliation Provision of 29 U.S.C. § 215(a)(3)

Minor v. Bostwick Laboratories, Inc.

Jafari v. Old Dominion Transit Management Co.

In two new opinions, one published (Minor) and one unpublished (Jafari) the Fourth Circuit confirmed that post-Kasten, intracompany complaints of FLSA violations are sufficient to trigger the protections of the anti-retaliation provision of 29 U.S.C. § 215(a)(3).

In Minor, the lower court had dismissed the plaintiff’s complaint premised on a violation of 215, holding that internal complaints, as opposed to those to a government agency, do not constitute protected activity.  Reversing the lower court, the Fourth Circuit held that such intracompany complaints are indeed protected activity and thus, trigger the protections of 215.

Framing the issue the Fourth Circuit explained:

“The sole question presented by this appeal is whether an employee’s complaint lodged within her company—as opposed to a complaint filed with a court or government agency—may trigger the protection of the FLSA’s antiretaliation provision. This is an issue of first impression in this circuit.”

Initially the court noted that neither Kasten, nor any Fourth Circuit case law was directly on point.  However, following the majority of circuits to have addresssed the issue, the court concluded that the statute was ambiguous as to this point and given the remedial nature of the FLSA such informal complaints should be protected.

After discussing the ambiguity in 215’s language regarding “filing” a complaint, the court reasoned:

“The Supreme Court in Kasten determined that oral complaints could constitute protected activity within the meaning of § 215(a)(3) based upon “functional considerations.” 131 S.Ct. at 1333. In light of the ambiguous nature of § 215(a)(3)‘s “filed any complaint” language, we find that these same functional considerations dictate that intracompany complaints qualify as protected activity within the meaning of the FLSA’s antiretaliation provision.

We first consider the basic goals of the FLSA. Consistent with other authority, we conclude that, because of the statute’s remedial purpose, § 215(a)(3) must be interpreted to include intracompany complaints.

The FLSA was enacted to combat “labor conditions detrimental to the maintenance of the minimum standard of living necessary for health, efficiency, and general well-being of workers.” 29 U.S.C. § 202(a). “The central aim of the Act was to achieve … certain minimum labor standards.” Mitchell v. Robert DeMario Jewelry, Inc., 361 U.S. 288, 292, 80 S.Ct. 332, 4 L.Ed.2d 323 (1960). To ensure compliance with the provisions enacted to serve this purpose, Congress “chose to rely on information and complaints from employees seeking to vindicate rights claimed to have been denied.” Id. It included the antiretaliation provision in recognition of the fact that “fear of economic retaliation might often operate to induce aggrieved employees quietly to accept substandard conditions.” Id. In light of these objectives, the Supreme Court has consistently held that the FLSA “must not be interpreted or applied in a narrow, grudging manner.” Tenn. Coal, Iron & R.R. Co. v. Muscoda Local No. 123, 321 U.S. 590, 597, 64 S.Ct. 698, 88 L.Ed. 949 (1944). We likewise recognized in Ball that where the statutory language permits, “we are instructed to read the FLSA to effect its remedial purposes.” 228 F.3d at 363–64.

With the statute’s purpose in mind, Kasten stated that “an interpretation [of § 215(a)(3) ] that limited the provision’s coverage to written complaints would undermine the [FLSA’s] basic objectives.” 131 S.Ct. at 1333. The Supreme Court further observed that such a limitation on the scope of the anti-retaliation provision would circumscribe flexibility in enforcing the FLSA. Id . at 1334. As a supporting point, the Supreme Court stated that “insofar as the antiretaliation provision covers complaints made to employers …, [limiting the scope of § 215(a)(3) ] would discourage the use of desirable informal workplace grievance procedures to secure compliance with the Act.” Id. Following this reasoning, we conclude that an interpretation that limits § 215(a)(3)‘s coverage to complaints made before an administrative or judicial body would overly circumscribe the reach of the antiretaliation provision in contravention of the FLSA’s remedial purpose. Allowing intracompany complaints to constitute protected activity within the meaning of § 215(a)(3), on the other hand, comports with the statute’s objectives as described by Congress’s findings and the Supreme Court’s interpretation of those findings.

Amici offer several persuasive policy arguments in support of this conclusion. They point out that protection of internal complaints encourages resolution of FLSA violations without resort to drawn-out litigation—and that failure to protect internal complaints may have the perverse result of encouraging employers to fire employees who believe they have been treated illegally before they file a formal complaint. Our sister circuits have voiced the same concerns in concluding that § 215(a)(3) protects intracompany complaints. See Valerio v. Putnam Assocs., Inc., 173 F.3d 35, 43 (1st Cir.1999) (“By protecting only those employees who kept secret their belief that they were being illegally treated until they filed a legal proceeding, the Act would discourage prior discussion of the matter between employee and employer, and would have the bizarre effect both of discouraging early settlement and creating an incentive for the employer to fire an employee as soon as possible after learning the employee believed he was being treated illegally.”).

Indeed, the majority of circuits to consider the question of whether intracompany complaints are protected activity within the meaning of “filed any complaint” have answered in the affirmative, basing their decisions on the FLSA’s remedial purpose.FN8 See, e.g., Hagan v. Echostar Satellite, LLC, 529 F.3d 617, 626 (5th Cir .2008) (“We adopt the majority rule, which allows an informal, internal complaint to constitute protected activity under Section 215(a)(3), because it better captures the anti-retaliation goals of that section.”); Lambert v. Ackerley, 180 F.3d 997, 1004 (9th Cir.1999) (en banc) (finding that § 215(a)(3) covered internal complaints based on its remedial purpose); Valerio, 173 at 42 (same); EEOC v. White & Son Enters., 881 F.2d 1006, 1011 (11th Cir.1989) (same); Love v. RE/MAX of Am., Inc., 738 F.2d 383, 387 (10th Cir.1984) (same); Brennan v. Maxey’s Yamaha, Inc., 513 F.2d 179, 181 (8th Cir.1975) (same); see also EEOC v. Romeo Cmty. Sch., 976 F.2d 985, 989 (6th Cir.1992) (holding that an employee’s complaints to her employer were sufficient to trigger protection of the FLSA’s antiretaliation provision without explaining its rationale). Cf. Brock v. Richardson, 812 F.2d 121, 124–25 (3d Cir.1987) (holding that, because of the FLSA’s remedial purpose, a retaliatory firing based on an employer’s belief that an employee had filed a complaint—even when he had not—was prohibited by § 215(a)(3)). Thus, we adopt the majority view by holding that the remedial purpose of the FLSA requires intracompany complaints to be considered protected activity within the meaning of its antiretaliation provision.

Supporting our conclusion is the Secretary of Labor and the EEOC’s consistent position that intracompany complaints are included within the meaning of “filed any complaint.” We afford agency interpretations that do not have the force of law, like agency manuals and litigation documents, respect to the extent that they possess the “power to persuade.” Christensen v. Harris Cnty., 529 U.S. 576, 587, 120 S.Ct. 1655, 146 L.Ed.2d 621 (2000) (quoting Skidmore v. Swift & Co., 323 U.S. 134, 140, 65 S.Ct. 161, 89 L.Ed. 124 (1944)). Factors we consider when determining whether an agency interpretation has the power to persuade include “the thoroughness evident in its consideration, the validity of its reasoning, [and] its consistency with earlier and later pronouncements.” Skidmore, 323 U.S. at 140; see also Cunningham v. Scibana, 259 F.3d 303, 306–07 (4th Cir.2001).

Here, the EEOC has set forth the position that intracompany complaints constitute “fil[ing] any complaint” within the meaning of § 215(a)(3) in the compliance manual it issues to field offices. 2 EEOC Compliance Manual § 8–II(B) & 8–II(B) n. 12 (2006). In addition, both the Secretary and the EEOC have argued in litigation that intracompany complaints are covered by the FLSA’s antiretaliation provision. See, e.g., Br. for the Sec. of Labor and the EEOC as Amici Curiae at 26–30; Br. for the Sec. of Labor as Amicus Curiae, Kasten v. Saint–Gobain Performance Plastics Corp., 570 F.3d 834 (7th Cir.2009) (No. 08–2820). Thus, although it is not determinative, because the Secretary and the EEOC have consistently advanced this reasonable and thoroughly considered position, it “add[s] force to our conclusion.” Kasten, 131 S.Ct. at 1335.

We conclude by emphasizing that our holding that intracompany complaints may constitute “fil[ing] any complaint” under § 215(a)(3) does not mean that every instance of an employee “letting off steam” to his employer constitutes protected activity. Kasten, 131 S.Ct. at 1334. To the contrary, “the statute requires fair notice” to employers. Id. To protect employers from unnecessary uncertainty, “some degree of formality” is required for an employee complaint to constitute protected activity, “certainly to the point where the recipient has been given fair notice that a grievance has been lodged and does, or should, reasonably understand that matter as part of its business concerns.” Id. Therefore, the proper standard for the district court to apply is the aforementioned test articulated in Kasten: whether Minor’s complaint to her employer was “sufficiently clear and detailed for a reasonable employer to understand it, in light of both content and context, as an assertion of rights protected by the statute and a call for their protection.” Id. at 1335.

Minor’s allegations here meet the standard we have articulated to the extent required to survive a motion to dismiss. The facts as alleged in her complaint indicate that Minor expressed her concerns regarding FLSA violations to the chief operating officer of her company in a meeting specifically called for that purpose. Minor also alleges that this executive-level employee agreed to investigate her claims. At this stage, these allegations are sufficient. We note again that we express no view as to whether Minor should ultimately prevail under the standard we have articulated. We simply hold that, on the facts alleged, her complaint survives a motion to dismiss.”

Click Minor v. Bostwick Laboratories, Inc. to read the entire published Opinion.  Click Jafari v. Old Dominion Transit Management Co. to read the companion unpublished Opinion.  Also of interest is the DOL/EEOC Amici Brief filed in Jafari.

4th Cir.: Job Applicant Lacked Standing Under § 215 for Retaliation Against Prospective Employer; Protections Extend Only to “Employees”

Dellinger v. Science Applications International Corp.

Plaintiff commenced this action under the Fair Labor Standards Act of 1938 (“FLSA”) against Science Applications International Corporation which, she alleges, retaliated against her, in violation of the FLSA’s anti-retaliation provision, 29 U.S.C. § 215(a)(3), by refusing to hire her after learning that she had sued her former employer under the FLSA.  As discussed here, the district court granted Science Applications’ motion to dismiss, concluding that Plaintiff was not an “employee” of Science Applications, as defined in the FLSA, and that the FLSA’s anti-retaliation provision does not cover prospective employees.  On appeal, Dellinger contended that the district court’s reading of the statute was too narrow and that the FLSA’s anti-retaliation provision protects any employee that has been the victim of FLSA retaliation by “any person,” including future employers.  Affirming the dismissal, the Fourth Circuit concluded that the FLSA gives an employee the right to sue only his or her current or former employer and that a prospective employee cannot sue a prospective employer for retaliation.

Rejecting the common sense approach proffered by the Plaintiff (and supported by the DOL, who filed an Amicus Brief in support of the Plaintiff), the Fourth Circuit reasoned:

“While § 215(a)(3) does prohibit all “persons” from engaging in certain acts, including retaliation against employees, it does not authorize employees to sue “any person.” An employee may only sue employers for retaliation, as explicitly provided in § 216(b). The use of the term “person” in § 215(a) is attributable to the structure of the provision, which prohibits a number of separate acts in addition to retaliation, not all of which are acts performed by employers. For instance, § 215(a)(1) prohibits any person from transporting “any goods in the production of which any employee was employed in violation of section 206 [minimum wages] or section 207 [maximum hours] of this title.” Thus, Congress prohibited the shipment of goods produced by employees who are paid in violation of the Act, and for enforcement, it authorized the criminal prosecution of any “person” violating the prohibition. See 29 U.S.C. § 216(a). Just as there is no remedy for an employee to sue such a shipper, there is also no remedy for an employee to sue anyone but his employer for violations of the anti-retaliation provision. Accordingly, if the person retaliating against an employee is not an employer, the person is not subject to a private civil action by an employee under § 216(b).

Considering the Act more broadly, we cannot overlook the fact that the FLSA was intended at its core to provide minimum wages and maximum hours of work to ensure employees a minimum standard of living necessary for “health, efficiency, and general well-being of workers.” 29 U.S.C. § 202(a). The anti-retaliation provision is included, not as a free-standing protection against any societal retaliation, but rather as an effort “to foster a climate in which compliance with the substantive provisions of the [FLSA] would be enhanced.” Mitchell v. Robert DeMario Jewelry, Inc., 361 U.S. 288, 293 (1960). Thus, the anti-retaliation provision was meant to ensure that employees could sue to obtain minimum wages and maximum hours from their employers without the employers taking adverse action against them for the exercise of those rights. This purpose is inherent in the employment relationship, which is the context in which the substantive provisions operate.

We have been unable to find any case that extends FLSA protections to applicants or prospective employees. Indeed, prior cases have reached the conclusion that we have, applying the anti-retaliation provision only within the employer-employee relationship. See, e.g., Glover v. City of North Charleston, S.C., 942 F.Supp. 243, 245 (D.S.C.1996) (noting that the “any employee” language in the anti-retaliation provision mandates that the plaintiff have an employment relationship with the defendant); Harper v. San Luis Valley Reg’l Med. Ctr., 848 F.Supp. 911 (D.Col.1994) (same); cf. Darveau v. Detecon, Inc., 515 F.3d 334, 340 (4th Cir.2008) (requiring, as part of a prima facie FLSA retaliation case, a showing of “adverse action by the employer”); Dunlop v. Carriage Carpet Co., 548 F.2d 139 (6th Cir.1977) (holding that an employee could sue his former employer when the former employer retaliated against the employee by advising a prospective employer that the employee had previously filed an FLSA suit).

We are sympathetic to Dellinger’s argument that it could be problematic to permit future employers effectively to discriminate against prospective employees for having exercised their rights under the FLSA in the past. The notion, however, that any person who once in the past sued an employer could then sue any prospective employer claiming that she was denied employment because of her past litigation would clearly broaden the scope of the FLSA beyond its explicit purpose of fixing minimum wages and maximum hours between employees and employers. We are, of course, not free to broaden the scope of a statute whose scope is defined in plain terms, even when “morally unacceptable retaliatory conduct” may be involved. Ball v. Memphis Bar–B–Q Co., 228 F.3d 360, 364 (4th Cir.2000).

Dellinger urges us to extend the FLSA’s definition of “employee” to protect job applicants, pointing to other statutes under which applicants are protected. In particular, she refers to the Energy Reorganization Act, the National Labor Relations Act (“NLRA”), the Occupational Safety and Health Act (“OSHA”), and the Pipeline Safety Improvement Act. Reference to these statutes, however, does not advance her cause. The case cited by Dellinger with respect to the Energy Reorganization Act merely assumed, without deciding, that an applicant was covered under that Act. See Doyle v. Secretary of Labor, 285 F.3d 243, 251 n. 13 (3d Cir.2002). While the NLRA does protect prospective employees from retaliation, the Act itself defines “employee” more broadly than does the FLSA, providing that the term “employee” “shall not be limited to the employees of a particular employer” unless explicitly stated. See 29 U.S.C. § 152(3). With respect to OSHA and the Pipeline Safety Improvement Act, regulations implementing those statutes have been promulgated to extend protections to prospective employees. See 29 C.F.R. § 1977.5(b) (OSHA); 29 C.F.R. § 1981.101 (Pipeline Safety Improvement Act). The Secretary of Labor has not, however, promulgated a similar regulation for the FLSA.

Because we conclude that the text and purpose of the Fair Labor Standards Act of 1938 link the Act’s application closely to the employment relationship and because the text of the applicable remedy allows for private civil actions only by employees against their employers, we hold that the FLSA anti-retaliation provision, 29 U.S.C. § 215(a)(3), does not authorize prospective employees to bring retaliation claims against prospective employers. The judgment of the district court is accordingly affirmed.”

In a must-read strong dissent, authored by Judge King, he indicated that he would have reversed the dismissal at the district court below.  Following a lengthy discussion of the parallels in this case to the Robinson case- in which the Supreme Court reversed an en banc decision of the Fourth Circuit and concluded that similar statutory text in Title VII should be read expansively to protect former employees- Judge King explained that he would have held that job applicants are protected by § 215.  Judge King challenges the majority who he asserts ignored binding opinions from both the Supreme Court and the Fourth Circuit in favor of what he calls their “textualist” approach:

“It is unlawful under the FLSA ‘for any person,’ not just employers, ‘to discharge or in any other manner discriminate against any employee because such employee has filed any complaint or instituted … any proceeding under or related to this chapter[.]’ 29 U.S.C. § 215(a), –(a)(3). The Act criminalizes willful violations of § 215, and it also provides civil recourse to ’employees affected’ by the retaliatory acts described in subsection (a)(3). See § 216(a), –(b). Affected employees are entitled to “legal or equitable relief as may be appropriate to effectuate the purposes of” the antiretaliation provision, ‘including without limitation employment, reinstatement, promotion, and the payment of wages lost and an additional equal amount as liquidated damages.’ § 216(b). Liability attaches to ‘[a]ny employer,’ id., which ‘includes any person acting directly or indirectly in the interest of an employer in relation to an employee .’ § 203(d).

A plain reading of these several sections of the Act, taken together, indicates that Congress was concerned enough with retaliatory conduct to impose criminal penalties on actual decisionmakers (“any person”), regardless of whether that person could also be considered the employing entity or was acting at the entity’s behest. Civil liability for retaliation, on the other hand, is reserved for employers and their agents who are sued by an “employee,” which generally means “any individual employed by an employer.” § 203(e)(1). Science Applications is undoubtedly an employer subject to the Act, and Ms. Dellinger broadly qualifies as an employee, having once sued her former employer for allegedly violating the FLSA. It does not follow perforce, however, that “Dellinger could only sue Science Applications if she could show … that Science Applications was her employer.” Ante at 7 (emphasis added).

It would hardly be a stretch to interpret the FLSA to permit Ms. Dellinger’s action, particularly considering that other, similar remedial statutes already apply to employees in her situation…

…I am therefore left to wonder why, in the face of a statute’s relative silence as to a material enforcement term, we must presume that a particular avenue is foreclosed because it is not explicitly mentioned, rather than permitted because it is not specifically prohibited. See Healy Tibbitts Builders, Inc. v. Dir., Office of Workers’ Comp. Programs, 444 F.3d 1095, 1100 (9th Cir.2006) (“[F]aced with two reasonable and conflicting interpretations, [an act] should be interpreted to further its remedial purpose.”). The majority’s decision today bucks the trend begun by Robinson, which is indisputably toward an expansive interpretation of protective statutes like Title VII and the FLSA to thwart employer retaliation. See, e.g., Gomez–Perez v. Potter, 553 U.S. 474, 491 (2008) (concluding that, under applicable provision of ADEA, federal employee may state claim for retaliation as form of discrimination); CBOCS West, Inc. v. Humphries, 553 U.S. 442, 457 (2008) (ruling that anti-discrimination provisions of 42 U.S.C. § 1981 encompass action for retaliation); Jackson v. Birmingham Bd. of Educ., 544 U.S. 167, 178 (2005) (same with respect to Title IX).

Behind this impressive array of authority is the Supreme Court’s acknowledgment of the vital role that antiretaliation provisions play in regulating a vast range of undesirable behaviors on the part of employers. See, e.g., Crawford v. Metro. Gov’t of Nashville & Davidson Cnty., Tenn., 129 S.Ct. 846, 852 (2009) (observing that fear of retaliation is primary motivation behind employees’ failure to voice concerns about bias and discrimination and reversing Sixth Circuit’s judgment in employer’s favor as inconsistent with primary objective of Title VII to avoid harm to employees) (citations omitted); Burlington N. & Santa Fe Ry. Co. v. White, 548 U.S. 53, 57 (2006) (explaining that liability for Title VII retaliation extends well beyond those actions affecting terms and conditions of employment to include employer’s acts outside workplace that are “materially adverse to a reasonable employee or job applicant”). There is no reason to doubt that similar concerns obtain in the FLSA context, as expressed in Reyes–Fuentes v. Shannon Produce Farm, 671 F.Supp.2d 1365, 1368 (S.D.Ga.2009) (“Congress chose to rely upon information and complaints from employees seeking to vindicate their rights. Plainly, effective enforcement could thus only be expected if employees felt free to approach officials with their grievances”) (citations omitted).”

Given the strong dissent of Judge King, it is possible if not likely that this case might be headed to the Supreme Court.  This is certainly one to keep an eye on.

Click Dellinger v. Science Applications International Corp. to read the entire Opinion and Dissent.

E.D.Va.: Plaintiff Alleged Actionable Retaliation Claim, Where Asserted Former Employer Denied Him Work as Independent Contractor In Retaliation for Testimony in Co-Employee’s Case

Boscarello v. Audio Video Systems, Inc.

In this Fair Labor Standards Act (FLSA) retaliation action, a former employee sued his former employers alleging that defendants retaliated against him, in violation of 29 U.S.C. § 215(a)(3), by refusing to provide him work as an independent contractor following his submission of an affidavit supporting a current employee’s FLSA claim against the employers.  The case was before the court on defendants’ motion to dismiss, for failure to state a claim.  At issue on defendants’ motion was whether a former employee states a valid FLSA retaliation claim where, the alleged retaliation consists of the employer’s refusal to provide its former employee work as an independent contractor, work that the employer was not contractually obligated to provide, but which the employer indicated would be provided.  Following Fourth Circuit precedent, the court held that the Plaintiff had indeed stated a valid cause of action.

Click Boscarello v. Audio Video Systems, Inc. to read the entire Opinion.

U.S.S.C.: Oral Complaints Are Sufficient to Trigger the Anti-Retaliation Provisions of the Fair Labor Standards Act

Kasten v. Saint-Gobain Performance Plastics Corp.

Kasten brought an anti-retaliation suit against his former employer, respondent (Saint-Gobain), under the Fair Labor Standards Act of 1938 (Act), which forbids employers “to discharge . . . any employee because such employee has filed any complaint” alleging a violation of the Act, 29 U. S. C. §215(a)(3). In a related suit, the District Court found that Saint-Gobain violated the Act by placing timeclocks in a location that prevented workers from receiving credit for the time they spent donning and doffing work related protective gear. In this case Kasten claimed that he was discharged because he orally complained to company officials about the timeclocks. Holding that such oral complaints were not protected activity, the trial court granted the respondent summary judgment. Subsequently, the Seventh Circuit affirmed. Reversing, the Supreme Court held that the scope of statutory term “filed any complaint” includes oral, as well as written, complaints.

Click Kasten v. Saint-Gobain Performance Plastics Corp. to read the entire decision.