A few labor and employment gems I got this week

A couple of interesting gems I got this week from other people (thanks, you guys!):

Pro hac vice statements defeat summary judgment! A federal judge in North Carolina denied summary judgment to a law firm who was sued by an associate for wrongful discharge based on race. Although the law firm's evidence showed thatJewels Andalusite.jpg the associate was a poor performer, the judge found that statements made in a motion to admit her pro hac vice in New York (saying she was in good standing, and yadayadayada) created a genuine issue of material fact as to whether "poor performance" was a pretext.

My friend (as long as she isn't suing one of my clients) and most-worthy adversary Julie Fosbinder of Charlotte was representing the plaintiff, so I'm not surprised that she (a) thought of it this idea, and (b) persuaded the judge. Law firms, when firing an associate for poor performance, something to think about . . .

(Hat tip to my partner and mentor Randy Loftis.)

At least one EEOC office says no need to comply with employment provisions of GINA when dealing with workers' comp claims. And a reader of this blog -- I will not identify her unless she wants me to -- told me that she received an off-the-record opinion from her local EEOC office about whether an employer must comply with the Genetic Information Nondiscrimination Act when administering workers' compensation claims. Surprisingly, the EEOC office told her NO, they do not. Don't even have to provide the safe harbor language (although I would). The EEOC's position was that this is not an employment-related issue, so Title II of the GINA does not apply.

I wanted to share this wisdom while it was still hot . . . but I'll be back with a full-blown post tomorrow.

Employers, you might (or might not) be liable for retaliation if . . .

Our friend Judy Greenwald from Business Insurance magazine reported this week that the number of EEOC charges filed in fiscal year 2011 (which ended September 30, 2011) was relatively flat, with the exception of one big category . . . retaliation.

Mobile Home smaller.jpgRetaliation is essentially taking action against an employee because the employee engaged in some type of activity that is protected by law. The law breaks it down into three parts, each of which the employee has to prove:

1-The employee engages in some type of legally protected activity (more on this below).

2-"Adverse employment action" is taken by the company.

3-There is a "causal nexus" (that's "connection" to you and me) between the protected activity and the adverse action. In other words, there has to be some reason to believe that the adverse action was taken because of the protected activity.

Almost all federal and state employment laws have anti-retaliation provisions. In the labor relations arena, the "non-discrimination" provisions in the National Labor Relations Act are essentially anti-retaliation provisions. A wrongful discharge lawsuit where an employee claims he was terminated for refusing to break the law or for complying with the law is also essentially a retaliation claim.

"Protected activity" can include such things as filing a charge or lawsuit, providing truthful testimony or other help to someone else in connection with a charge or lawsuit, or making an internal complaint about unlawful practices. These activities may be protected even if the employee is wrong -- as long as the employee had a good-faith belief that the employer's conduct was illegal. (Sometimes the employee's belief must also be objectively reasonable to be protected -- check the relevant law and the interpretations from courts in your jurisdiction.)

However, the employer may not be liable if the employee expresses herself in an inappropriate way -- for example, by spray painting on your corporate headquarters building, "MEGACORP DISCRIMINATES AGAINST WOMEN!!!!" (Thank heaven for small favors, huh?)

Now that you have that background, what I'd really like to talk about today is how an employee proves retaliation and how an employer disproves it. With a hat tip to Jeff Foxworthy (you knew there was a reason for that photo of a trailer!),

"YOU MIGHT BE LIABLE FOR RETALIATION IF . . ."

1-You took action against the employee a short time after you found out about the protected activity. Yes, there might be an innocent explanation, and you'll get a chance to provide it, but it looks very suspicious if the adverse action occurred, just as an example, the day after you received your copy of Joe's race discrimination charge in the mail. If the time interval was less than six months and you don't have a good explanation, you might be liable for retaliation.

2-That gun is smokin'! You, or another member of management who directly or indirectly participated in the decision made a statement indicating a retaliatory intent. You know, something like, "I can't believe that little dickens filed an EEOC charge against us! I'll fix her wagon!" If one of the key individuals made a "smoking gun" statement like this before the adverse action was taken, you might be liable for retaliation.

3-You have no "interventions." In other words, there is no intervening event to "break" what we lawyers like to call "the chain of causation." Mary had outstanding performance reviews before she complained that Mr. Romeo was sexually harassing her. She was fired a month later. There was nothing significant that occurred between her harassment complaint and her termination that would "explain away" the suspicious timing of the termination . . . for example, that Mary had botched a million-dollar deal after she complained, or got caught with her hand in the petty cash drawer, or was part of a department that was already scheduled for elimination. If there is a relatively short time between the protected activity and the adverse action, and there is no significant intervening event, you might be liable for retaliation.

4-A foolish consistency is not the hobgoblin of little minds. (Except when it is.) Employers, if you have to take action against an employee who engaged in protected activity, examine your conscience: "Would I be doing the same thing if Lemuel had not complained on behalf of himself and his co-workers about having to work too much overtime?" Oh, really? Are you sure? If you answer that question, "no" or "maybe," then don't take the action. If you answer it "yes," then you're still not done. Now ask yourself this: "Even if I am satisifed that I'm treating Lemuel no differently from any other employee, will I be able to prove it in court?" If you can't convince a third party that you treated Lemuel the same way you would have treated any other employee with similar issues, you might be liable for retaliation.

5-A foolish consistency is the hobgoblin of little minds. (Except when it isn't.) Do you have other employees who've filed charges or lawsuits against you while they were still employed? Or workers' compensation claims? Or who made internal complaints about discrimination, sexual harassment, working conditions, safety, or what have you? Did bad things happen to them? This could show that you have a pattern of retaliating against employees who engage in protected activity. If so, a judge or jury is likely to find that you probably treated this particular employee the same way, and you might be liable for retaliation. 

We aim to be "fair and balanced," so here is the other side.

YOU MIGHT NOT BE LIABLE FOR RETALIATION IF . . .

1-You are blissfully ignorant. You can't retaliate for something you didn't know about. If you fired Velveeta before you knew that she had been involved in union organizing, then you should be ok. In fact, if you can prove that you made the decision to fire Velveeta, and then found out she was involved in union organizing, and then fired her per the original decision, you'll probably win because the decision had already been made while you were knew nothing of her protected activity. This, by the way, is one of the best reasons to document decisions to terminate employees, even if the termination isn't actually carried out until later.

If the decision was made before you knew about the protected activity, you might not be liable for retaliation.

2-It's been a long time coming. If at least six months has elapsed between the time you found out about Todd's workers' comp claim and the day that you decided to fire Todd, most courts will give you the benefit of the doubt that the decision was not related to his protected activity. Todd can overcome that presumption by presenting evidence that you were still upset with him about his workers' comp claim even after all that time, but assuming he doesn't have any, you might not be liable for retaliation.

3-You have an "intervention." You found out last week that Banshie had filed an EEOC charge against you. Yesterday, you caught her (on tape!) slapping her supervisor across the face for no good reason whatsoever. YES, you can fire Banshie for slapping her boss, even though she just recently filed a charge that you know about. This is what we call a significant intervening event that "breaks" the chain of causation. If a significant intervening event occurred that provided the ground for the adverse action, then you might not be liable for retaliation.

4-A foolish consistency is not the hobgoblin of little minds. (Except when it is.) Yes, you terminated Dishwater only three weeks after finding out about his testimony against the company in Carol's discrimination lawsuit, but he had exceeded the maximum number of absences (non-FMLA/ADA, of course) under your policy, and you checked before you did it and made sure that every other employee whose attendance reached the same level had also been terminated. You also found that Dishwater had received all of the progressive warnings to which he was entitled under your policy. If you treat the "protected" employee the same way you would have treated anyone else with comparable history, then you might not be liable for retaliation.

5-A foolish consistency is the hobgoblin of little minds. (Except when it isn't.) Yes, you fired Chloreen for poor performance a couple of months after you found out that she'd filed a charge against you. But you have 50 other employees who have filed charges, lawsuits, or workers' comp claims, or who have made internal harassment complaints, etc., etc., who are all still working for you and are in good standing. If you have a long list of employees who are rocking along at work without problems even though they're "protected," then you might not be liable for retaliation.

PHYSICIAN, HEAL THYSELF! Good lessons for employers from AMA case

It could be that the purpose of your life is only to serve as a warning to others.

In any event, that must be what the American Medical Association is thinking. The organization took it on the chin this week in a case involving the Family and Medical Leave Act.300px-The_Anatomy_Lesson.jpg

The case is well worth a post-mortem because of what it teaches employers about "causation" in retaliation and protected concerted activity cases.

Names have been changed to protect the allegedly* guilty.

*Even though the AMA lost a battle with this decision, it has not lost the war. The court found that summary judgment should not have been granted, but that means that the case will be tried before a jury. A jury might side with the plaintiff, but it might also side with the AMA.

Here's what happened:

The AMA, like just about every other employer, suffered from the economic downturn in 2008, and a manager -- we'll call him Dr. Pepper -- was told to reduce costs. Eventually it was determined that he was going to have to eliminate one position.

(One more disclaimer before I go on. Despite my fictional "doctor" names, none of the individuals actually involved in this case were physicians, as far as I can tell.)

Dr. Pepper chose an individual to eliminate -- we'll call him Dr. Seuss -- and sent an email to his boss informing her that he had chosen Seuss, and the rationale for selecting him. The gist of the rationale was that most of Seuss's work was going away anyway, so it made the most sense to eliminate his position.

Dr. Pepper's boss -- we'll call her Dr. Scholl -- sent him a reply asking whether the plaintiff, Dr. Dre, should have been eliminated along with Seuss. Pepper replied no, because he did not think it would be wise to eliminate any more positions than absolutely necessary. Scholl apparently was cool with this answer. This all happened in late October 2008.

So, we get to November 20 at a conference. Dr. Dre was there with Dr. Pepper. Dre told Pepper that he was going to have surgery on his knee in January, would be out of work for a few weeks, and was going to apply for short-term disability.

I hope you've stayed with me, because now it gets interesting.

Ten days after this conversation, on Sunday night of Thanksgiving weekend, Dr. Pepper sent an email to Dr. Scholl, apologizing for his "11th hour" change in decision, and telling her that he now wanted to eliminate Dr. Dre instead of Dr. Seuss. Among other things, Pepper said that they could more easily weather the loss of Dre because they were preparing for him to go out on disability anyway.

Poor Dr. Dre was terminated in January, and he hired a lawyer, and his lawyer sent a nasty letter to the AMA in February. The AMA's in-house attorney informed the organization's HR representative about the threatened litigation. We'll call the HR rep Dr. Bombay. (Nowadays, should that be Dr. Mumbai?)

It turns out that Dr. Bombay and Dr. Pepper had discussed the decision to terminate Dr. Dre back in November and that Bombay had taken handwritten notes. Upon learning of the threatened litigation the following February, Bombay typed up his notes and shredded his original handwritten notes, and he dated the typed notes "November 25, 2008," even though it was now February 2009.

Hmmmmm! Verrrrrrry interesting.

But, wait! There's more!

It turned out that Dr. Pepper's calendar didn't show a meeting with Dr. Bombay on November 25, and Pepper didn't remember having had one. Even worse, he testified that he didn't decide to eliminate Dr. Dre until after that date. All this made Bombay's backdating look even more dishonest.

In May 2009, the AMA eliminated about 100 more employees, including Dr. Seuss, the person Dr. Pepper had originally planned to eliminate. Apparently this was enough for a district court to grant summary judgment to the AMA. (I know! I'm not sure how that happened, either.)

But the U.S. Court of Appeals for the Seventh Circuit, which hears appeals from federal courts in Illinois, Indiana, and Wisconsin, reversed, which means that Dr. Dre will be allowed to take his FMLA "interference" and retaliation claims* to trial.

*FMLA "interference" is simply a denial of FMLA leave to someone who is entitled to it, or doing something to discourage the individual from taking FMLA leave. It does not require a bad motive on the part of the employer and can even be based on a mistake or misunderstanding. In the case of FMLA retaliation, the employer "punishes" the employee for requesting or taking FMLA leave. Proof of the employer's unlawful motive is required for a retaliation claim.

So, let's make the usual Y-shaped incision and see what lessons can we learn from our "autopsy" of this case.

1. Timing is really, really important. On October 28, Dr. Pepper told his boss that Seuss should be eliminated, and he gave a good reason for the selection. He also told her that he thought it would be unwise to eliminate anyone else, and specifically Dre. On November 20, Dre informed Pepper that he would need to take FMLA leave in January. Within 10 days, Pepper reversed his RIF decision and recommended that Dre be eliminated instead of Seuss. Whatever Dr. Pepper's actual motive, this timing looks quite damning, doesn't it? The Seventh Circuit thought so, too.

2. Mentioning the FMLA leave in the poorly-timed email was not cool. In Dr. Pepper's "11th-hour" email, he said that the department could adjust easily to Dr. Dre's elimination because they were already preparing for his medical leave. Yes, I know there could be an innocent explanation for this: Pepper wasn't giving that as his motivation, he was simply giving his opinion about the effect of the decision. But this statement, especially when considered along with everything else, helps to make it look like the FMLA leave request was the reason for the selection.

3. Backdating documents is really not cool. Here's what I always tell clients: It's fine to document an event after the fact, even long after the fact, and I strongly recommend it if you didn't document at the time. But never, ever, ever, ever, ever, ever, ever in a million zillion years backdate it -- unless you are sure that the backdating is "transparent" (for example, drawing a line through the current date so that the original date is still visible, or saying something like "Created 10/22/11 based on event that occurred 6/1/11."). Any other kind of backdating looks dishonest and, as the Seventh Circuit noted, is more evidence that the employer may have had an unlawful motive and was trying to cover its tracks.

4. Destroying handwritten notes upon learning of threatened litigation (aka "spoliation") is the uncoolest of all. If you're not expecting litigation and don't have reason to expect it, then you can create a "draft" document and destroy the draft after creating the "final" version. But once you either become aware of litigation or have reason to expect it, your right to do this is gone. You must save all of your relevant documentation. Dr. Bombay, the HR representative who destroyed his handwritten notes after learning of the threat of a lawsuit, committed "spoliation," whether he realized it was wrong or not. As a result, when the case goes to trial, the judge may instruct the jury that the notes would have been favorable to Dr. Dre's case.

5. To err is human: be willing to cut your losses if you messed up, or if it will look like you messed up even if you didn't. In this case, it appears that Dr. Dre would have survived at the AMA only about 5 more months if Pepper had stuck with his original plan to eliminate Seuss in January. The undisputed evidence showed that the AMA had a massive reduction in May, and it probably would have included Dre if he'd still been around. Damages under the FMLA are limited to so-called "make-whole" relief (essentially, back pay, back benefits, costs and attorneys' fees, possibly doubled in the case of a willful violation). Even assuming the AMA might have been on the hook for a "willful" violation, it probably had a strong argument that it would not have owed much more than 10 months' pay to Dre, plus his costs and fees. Given that, it might have made economic sense for the AMA to have settled the case in mediation. (Please note that mediations are confidential, so it is very possible that the AMA tried to do just that.)

I was tempted to end this post with a rap about Dr. Dre, the AMA, the FMLA, the month of May, Dr. Bombay, and "anyway." Then I thought better of it. You're welcome.