About Us  |  About Cheetah®  |  Contact Us

WK WorkDay Blog

Subscribe to the Employment Law Daily RSS Subscribe

“My fiancée got me fired”: The evolution of retaliation claims

July 1st, 2009  |  Deborah Hammonds

>With the Sixth Circuit’s recent pro-employer ruling on associational retaliation, and a current split on the matter unfolding among the circuits, this issue may well be headed to the Supreme Court next term…to a Court under Chief Justice Roberts that has been decisively pro-employee in its retaliation decisions. But is this case really much ado about nothing?

In Thompson v North American Stainless, LP, a male employee, who alleged that he was fired shortly after his fiancée filed an EEOC sex-bias charge against their shared employer, had no reprisal claim under Title VII. The plain and unambiguous statutory language of Title VII’s anti-retaliation provision requires employees to personally engage in protected activity, held a 10-6 en banc Sixth Circuit, affirming a district court’s grant of summary judgment for the employer. The majority observed that the plain language of Title VII will protect most close relationships because “‘[i]n most cases, the relatives and friends who are at risk of retaliation will have participated in some manner in a co-worker’s charge of discrimination.” Here, though, the employee did not claim that he engaged in any statutorily protected activity either on his own behalf or on behalf of his fiancée.

In so holding, the Sixth Circuit joined the Third, Fifth and Eighth Circuits, which have previously considered and rejected similar associational retaliation claims.

Note, however, the EEOC takes the position in its Compliance Manual that Title VII prohibits retaliation against someone so closely related to, or associated with, the person exercising his or her statutory rights that it would discourage that person from pursuing those rights. For example, “it would be unlawful for [an employer] to retaliate against an employee because his or her spouse, who is also an employee, filed an EEOC charge.” Both spouses, in such circumstances, could bring retaliation claims, said the agency. Does this mean simply having that close association to the charging party, without engaging in protected activity, is enough to also assert an associational retaliation claim? It seems that way, according to the EEOC. The Seventh and Eleventh Circuits have also interpreted Title VII’s anti-retaliation provision broadly to protect associated third parties from retaliation.

What does all this mean? Well, in its holding, the majority wrote: “[the] plaintiff and the EEOC request that we become the first circuit court to hold that Title VII creates a cause of action for third-party retaliation on behalf of friends and family members who have not engaged in protected activity.” (Emphasis added).

Personally, I think the majority got it right by not doing so. The Sixth Circuit appears not to question the legality of associational retaliation claims, but believes that merely having an “association” with the charging party, without also personally engaging in some protected activity, is not enough. The employee did not personally oppose any alleged discrimination. And we won’t get into whether “silent opposition” is opposition, even if some dissenting judges seem to think it is. If, however, the employee had engaged in some kind of participation activity, like help his fiancée complete her EEOC sex-bias charge, and participated in any interview with the agency, he likely would have been able to get past summary judgment on his retaliatory discharge claim. But, the employee admitted he did not personally oppose any alleged discrimination or participate in her charge. So, no dice.

None of this means employers should rest on their laurels. The Supreme Court seems to like retaliation cases and may take this one just to clarify the issues. Besides, there is this circuit split, a split that may have more to do with whether closely associated individuals have personally engaged in a protected activity, not with whether the reach of Title VII’s anti-retaliation provision includes associational discrimination claims. Of note, the employee’s attorney indicated that he is considering filing a cert petition.

In the meantime, a little retaliation-prevention training couldn’t hurt, since the EEOC reported that the number of retaliation claims filed with the agency jumped from 22,663 in FY 2007 to 32,690 in FY 2008, a nearly 23-percent increase. This was the second highest increase in charge filings, next to age discrimination.


GM bankruptcy hints at risks to non-unionized employees

June 30th, 2009  |  Matt Pavich

>The judge presiding over the General Motors bankruptcy last week denied an application by the General Motors Retirees Association (GMRA) to form a benefits committee that would advocate for the beleaguered car manufacturer’s salaried retirees in the bankruptcy proceedings. The company, ruled the judge, had the right, pre-bankruptcy, to modify or terminate the retirees’ health and life insurance benefits and the retirees cannot now challenge that right.

“While I do understand the importance of this to the retirees,” said U.S. Judge Robert Gerber, “I can’t guarantee the retirees rights that they don’t have outside of bankruptcy.”

But not all the GM retirees have been left to fend for themselves. The hourly retirees who comprise the majority of GM’s retirees have been, and continue to be, represented by the United Auto Workers. Those employees will have a voice in the future of the auto company and their benefits; indeed, the UAW is now one of the largest shareholders in the “new” GM. The salaried retirees, who worked as engineers, clerks and project managers, stand to lose two-thirds of their benefits, including the total elimination of dental, vision and long-term disability coverage. These retirees are not guaranteed any input whatsoever and have been forced to turn to Congress for protection.

This ruling raises several issues. Is it just that one group of retirees will disproportionately sacrifice? What, if anything, can Congress do to protect these retirees? Would offering anything beyond basic protections to the retirees only feed the perception among big industry that the government will step in to correct their mistakes? And why would unions not use this as an example in their organizing drives?

Proponents of the Employee Free Choice Act have long argued that employers take extraordinary means to thwart organizing. They further argue that now, more than ever, employees need the strength of a union to protect them. Whatever the reasons for the non-unionized nature of the GMRA retirees, it is indisputable that they are receiving poorer treatment than their unionized counterparts.

Retirees were always going to have to make sacrifices in order for GM to eventually emerge as a profitable company. All retirees will, in fact, experience cuts to their benefits. But the non-unionized retirees will, by far, have the worst of it. To paraphrase George Orwell, all retirees will suffer equally, but some will suffer more equally than others.


Refusal to certify exams in order to avoid race-bias claims was discriminatory, High Court rules

June 29th, 2009  |  Deborah Hammonds

>The City of New Haven, Connecticut, violated Title VII when it tossed the results of firefighters’ promotion exams on the premise that certifying the results would lead to disparate impact litigation, ruled the US Supreme Court. The case has been even more closely watched because of the role that Judge Sonia Sotomayor, the Obama Administration’s nominee for the announced Supreme Court vacancy, played in the appeals court’s decision below that upheld the city’s actions. (Ricci v DeStefano, Dkt Nos 07-1428, 08-328, June 29, 2009, to be reported at 92 EPD ¶43,602)

Background. The city refused to certify the exam results when it appeared no black or Hispanic applicants would be eligible for promotion to the rank of Lieutenant and no black applicants and, at most, two Hispanic applicants would be eligible for promotion to the rank of Captain. Expressing a fear of possible litigation from nonpromoted, nonwhite applicants if the results were certified, the city refused to certify the exams and no promotions were made. Eighteen candidates, 17 white and one Hispanic, filed suit under Title VII and other federal and state laws alleging the refusal to certify was racially discriminatory.

A federal district court granted the defendants’ motion for summary judgment, holding the defendants’ motivation to avoid making promotions based on a test with a racially disparate impact, even in a political context, does not, as a matter of law, constitute discriminatory intent, and, therefore, such evidence is insufficient for plaintiffs to prevail on their Title VII claim.”

The Second Circuit Court of Appeals affirmed the decision in an unpublished order that was later withdrawn and replaced with a per curiam opinion (91 EPD ¶43,235) and an order denying a rehearing and rehearing en banc with written concurrences and a dissent (91 EPD ¶43,236). The Supreme Court granted cert on January 9, 2009.

Supreme Court ruling. The High Court noted that under Title VII, before an employer can engage in intentional discrimination for the asserted purpose of avoiding or remedying an unintentional, disparate impact, the employer must have a strong basis in evidence to believe it will be subject to disparate-impact liability if it fails to take the race-conscious, discriminatory action. Here, all the evidence showed the city rejected the test results because the higher scoring candidates were white, wrote the Court. “Whatever the city’s ultimate aim – however well intentioned or benevolent it might have seemed – the city made its employment decision because of race. The city rejected the test results solely because the higher scoring candidates were white. The question is not whether that conduct was discriminatory but whether the city had a lawful justification for its race-based action.”

Using the strong-basis-in-evidence standard, the Court found no substantial basis in evidence that the exams were deficient. After laying out the detailed steps taken to develop and administer the exams, the Court rejected the city’s claims that the exams were not job-related and consistent with business necessity, noting the assertions were “blatantly contradicted” by the record that also included “painstaking analyses of the questions asked to assure their relevance to the captain and lieutenant positions.” The city “turned a blind eye to evidence that supported the exams’ validity,” wrote the Court.

The city could not disregard the exams solely because it feared litigation from black or Hispanic applicants. “Fear of litigation alone” cannot justify an employer’s “reliance on race to the detriment of individuals who passed the examinations and qualified for promotions,” concluded the Court. Such action was impermissible under Title VII and the petitioners were entitled to summary judgment. The High Court determined it “need not” decide the underlying constitutional question. Accordingly, the Second Circuit’s opinion was reversed and the cases were remanded for further proceedings consistent with this opinion.

The 5-4 decision was written by Justice Kennedy, who was joined by Chief Justice Roberts and Justices Scalia, Thomas and Alito. Justice Scalia filed a concurring opinion. Justice Alito filed concurring opinion joined by Justices Scalia and Thomas. Justice Ginsburg filed a dissent joined by Justices Stevens, Souter and Breyer.


Monitoring “keystrokes” a privacy issue, or just good business practice?

June 26th, 2009  |  Lucas Otto

>Interested in monitoring your employees’ computer-related movements? Worried your employer might be watching “too closely” while you are sitting in front of your computer? In Brahmana v Lembo, N.D. Cal. May 20, 2009, one employee, one employer and a federal trial court in California are about to at least decide if monitoring down to the very keystroke violates privacy rights, or at least those rights under the Electronic Communications Privacy Act (ECPA). This law sets out the stipulations for the access, use, disclosure, interception and privacy protections of electronic communications.

The employee in the case alleged that his employer unlawfully monitored his computer keystrokes in order to obtain the password to his personal email account, and the employee bolstered this argument by alleging that the employer knew information that was never shared and could have only been known by reading his personal emails. According to the employee, his employer used monitoring tools such as local area network analyzers and key loggers to record his keystrokes when he entered his email password, in violation of the ECPA. The employer sought a dismissal of this claim

The Ninth Circuit Court noted that gaining access to stored electronic information does not violate the ECPA; however, the Act is implicated when electronic communications are “intercepted” during transmission. The court therefore reasoned that the employee’s allegations were “… sufficient to render plausible the claim that [the employee’s] communications were monitored in some way, but they do not specify whether the particular means of monitoring might monitor keystrokes that had actually affected interstate commerce,” as required by the statute. Because some means of the alleged monitoring may constitute a violation of federal law, the employee’s complaint was not dismissed.

As this case proceeds, the impact its final decision delivers will most certainly prove to have a powerful effect on both employer and employee. On the one hand, employees today often rely heavily on their workplace computer, and the Internet has proven to be both a valuable working tool, as well as an “escape” during the workday. On the other hand, while employers know a happy employee is a productive employee, “productivity” is always the key, and most employers want employees working, not surfing, and so the use of monitoring software seems to be one way to curb excessive Internet use.

Moving forward, the employer’s defense will provide an idea of what it did or did not do, and whether it actually monitored keystrokes and intercepted private information, and whether this was a violation of the ECPA. But a question that may not get posed, but is certainly on the minds of both employer and employee is: If this type of monitoring is legal, does an employer have carte blanche to monitor an employee’s computer use, and if so, how will that impact the workplace?


The latest lesson on the “ordinary meaning” of a critical preposition

June 24th, 2009  |  Pamela Wolf

>The US Supreme Court on June 18, 2009 gave us a new lesson on the “ordinary meaning” of the words “because of.” Construing this critical preposition in the text of the Age Discrimination in Employment Act (ADEA), a five-Justice majority concluded the statute’s requirement that an adverse employment action was taken “because of” age means that “age was the ‘reason’ that the employer decided to act.” (Gross v FBL Fin Servs, Inc, USSCt, Dkt 08-441). Thus, held the majority, to establish a disparate treatment claim under “the plain language” of the ADEA, “a plaintiff must prove that age was the ‘but-for’ cause of the employer’s adverse decision.” Age bias must be the sole cause, not just one cause.

Of course, as we all know, reasonable minds can differ. And in this case, four Justices had an entirely different take on the meaning of those two little words: “The most natural reading of this statutory text prohibits adverse employment actions motivated in whole or in part by the age of the employee,” wrote Justice Stevens, joined by Justices Souter, Ginsburg and Breyer, dissenting. Acknowledging the majority’s correct citation of the dictionary definition of the controversial preposition – “‘by reason of’ or ‘on account of,’” – Justice Stevens emphasized in a footnote that the dictionary does not define “because of” as “‘solely by reason of’ or ‘exclusively on account of.’”

In a separate dissent authored by Justice Breyer and joined by Justices Souter and Ginsburg, the Justices declare: “The words ‘because of’ do not inherently require a showing of ‘but-for’ causation.” These three dissenting Justices found no reason to read the disputed preposition to require “but-for” causation.

Then there’s the matter of the meaning ascribed to the same two words in the High Court’s Price Waterhouse v Hopkins decision (49 EPD ¶38,936). Justice Stevens reminded the Gross Court that the words “because of” in the earlier plurality opinion concerning a Title VII sex-bias claim meant “that gender must be irrelevant to employment decisions.” “As we made clear, when ‘an employer considers both gender and legitimate factors at the time of making a decision, that decision was because of sex,’” Justice Stevens wrote.

I know– different Court, different Justices – only three of the Court’s current Justices were on the Court in 1989 when Price Waterhouse was decided. Still, it seems that the “ordinary meaning” of the words “because of” would not have changed so much in the ensuing 20 years. After all, the majority in Gross relied on definitions obtained from dictionaries published in 1966 and 1933.

In any event, I suspect the confusion over this recent lesson on the “ordinary meaning” of this critical preposition will soon be irrelevant. Relying on its narrow construction of the words “because of,” the High Court closed off to age-bias plaintiffs the mixed-motives route (available in Title VII cases) that would enable proof of employment discrimination when the prohibited bias was at least one, but not the only, motive for an adverse action. With so many older individuals in the workforce and the increased incidence of age-bias claims, I don’t think this higher standard for age-bias claims will remain the law for long. The 29-percent increase in EEOC age bias charges filed in 2008 over those filed in 2007 – a 48-percent jump from the number filed in 2005 – should provide enough momentum for Congress to take action.