Rod Satterwhite and David Greenspan are members of the Labor & Employment group at McGuireWoods LLP. Both handle employment litigation on behalf of employers, and advise companies on employment issues regularly.

November 2005 - Posts

Why T.O. Lost

         The recent arbitration decision in the grievance filed by Terrell Owens against the Philadelphia Eagles and the NFL Management Council has several timeless lessons in it for all employers, despite the high-profile/high-dollar-value parties involved.  Although the union forcefully argued that the incidents for which Owens was suspended and ultimately placed on the inactive roster were a series of isolated events, the record maintained by the Eagles through a series of letters to Owens and his agent, coupled with the testimony of the head coach regarding his conversations with the two, allowed the arbitrator to discern an orchestrated pattern of conduct aimed at forcing Owens' employer to break its contract with Owens.  Once this orchestrated pattern was established, the arbitrator had little trouble in denying the grievance. 

            The Eagles made the arbitrator's job much easier by a series of letters to Owens detailing his instances of misconduct, as well as laying out their own theory that the misconduct was simply designed to get Owens out of a contract he wished he hadn't signed.  In addition, the Eagles' letters pointed out that Owens had publicly lied on several occasions regarding a so-called "secret waiver" that Owens claimed he was forced to sign relating to his medical condition at the end of the 2004 season.  This further undercut Owens' credibility when he testified at the arbitration hearing. 

 

            Finally, the Eagles did not make a unilateral decision until very late in the game with Owens, and even then offered him a way to avoid suspension and deactivation by making a public apology and addressing his concerns with the Eagles' quarterback directly.  For whatever reason, Owens refused to speak directly either to the football team or to the quarterback, and it was at that point that the Eagles suspended him.   

            The very clear warnings communicated to Owens in several letters from Eagles management, to paraphrase the arbitrator, acted as progressive discipline, properly advising Owens of unacceptable behavior, warning him that his tenure was becoming increasingly challenged, and attempting to provide for the possibility of better behavior in the future.  When these efforts failed, the arbitrator found that a four-game suspension was appropriate.

             The arbitrator also decided that there was no limitation on the Eagles coaching staff deactivating Owens and prohibiting him from returning to the Eagles facilities for the rest of the season.  The arbitrator's focus here was very narrow, he specifically noted (italics in the original) "the challenge faced by this team, dealing with this player in these particular circumstances."  Again, the "campaign of disruption" threatened and implemented by Owens and his agent was the determining factor for the arbitrator, who noted that what the Eagles had to deal with was not past bad behavior, but an ongoing threat of continued disruption.  He found that the Eagles' coaches properly exercised their discretion to protect the team and the interests of the football club by keeping Owens away from his teammates. 

            The NFL Players Association is understandably miffed by the arbitrator's decision, but really, it appears that Owens put himself in a uniquely disadvantageous position vis a vis his employer.  The employer carefully documented the incidents of problematic conduct, announced in its correspondence with Owens its theory of what he was doing and why, and then confronted him with the prospect of discipline or corrective action, which Owens refused.  I don't think the union should be particularly worried about the precedential value here.  I cannot imagine another player putting himself in this kind of a position, and the arbitrator seems to agree. 

Ball of Confusion

A recent Sixth Circuit case shows, again, how careful an employer must be when monitoring Family and Medical Leave Act absences.  This is a long story, but stay with me. 

 

            In Wilkerson v. Auto Zone, Inc., the Sixth Circuit ruled that the lack of coordination between employer managers, which resulted in a failure to notify the employee that her FMLA leave had expired, meant that the employer could be found guilty of interfering with FMLA rights when it fired the absent employee, even if her FMLA rights expired two weeks before she returned to work.

 

            Wilkerson went out on maternity leave and claimed that she was told she would have six weeks of FMLA leave before the baby's birth, and six weeks after.  But because Wilkerson had used intermittent leave prior to leaving work to give birth, she actually ran out of FMLA leave four weeks following the birth of the baby, rather than six.  Auto Zone failed to inform her of this fact, however.  Further complicating the issue, Wilkerson tested positive for a drug masking agent on a routine urinalysis that was reported to the company shortly after she left on FMLA leave.  Although it was the company's normal practice to advise an employee of a positive drug test, Auto Zone did not so advise Wilkerson, and instead determined that she would be terminated because of the failed drug test when she returned from maternity leave. 

 

            Before she returned, Wilkerson called Auto Zone regarding a medical release she needed to return to work (inexplicably, at the company's request).  Also inexplicably, the human resources official monitoring Wilkerson's absence expected her to return to work after five weeks of FMLA leave.  When Wilkerson failed to show up after five weeks, the HR official notified company management that Wilkerson had not returned to work when expected.

 

            Wilkerson ultimately showed up after six weeks of leave and was terminated for failing to report for work or call in her absence after five weeks.  She was not advised that she was terminated for the positive drug test.

 

            Wilkerson sued, claiming that Auto Zone denied her right to reinstatement and retaliating against her for taking FMLA leave.  A jury found in her favor, awarding $56,000 in damages. 

 

            As you might expect from such a complicated fact pattern, the Sixth Circuit had several things to sort out.  The initial issue is whether Wilkerson was entitled to reinstatement after six weeks of leave, even though her FMLA entitlement expired after only four weeks.  The Sixth Circuit held that an employer must notify an employee in writing when leave is designated as FMLA leave, and if the employer fails to do so, the leave may not be counted against the employee's 12-week allotment.  The court found that this holding was not in conflict with the Supreme Court's Ragsdale decision, even though it effectively awards additional FMLA leave above the statutory entitlement.  The Sixth Circuit found that because the employee reasonably believed that she was entitled to the additional two weeks of leave, she was prejudiced by the employer's failure to notify her of exactly when the FMLA entitlement would run out.

 

            Similarly, the court rejected the company's claim that Wilkerson's leave entitlement ended when her doctor released her to return to work after five weeks of leave because Wilkerson was unaware of the company's receipt of the release, despite her calls to verify its receipt.  As for the jury's rejection of the company's claim that it would have fired Wilkerson anyway because of her drug test results, the court noted that the company's failure to notify Wilkerson of the results, as it would normally, along with its formal notice to Wilkerson that she was being fired for attendance, provided ample basis for the jury to reject the company's evidence. 

 

            This case is almost a model for how not to manage an FMLA claim.  The company's failure to get its story straight regarding why it fired the plaintiff (there were actually three separate reasons for the company's termination decision), failure to properly monitor exactly how much FMLA time the plaintiff had, failure to provide her with notice as to when her FMLA leave would end, and failure to notify her of her failed drug test, provided a basis for the jury to disbelieve all of the company's reasons.  The Sixth Circuit simply affirmed the decision.  The lesson for employers?  Carefully monitor and communicate consistently with anyone out on FMLA leave; have a clear understanding on everyone's part as to exactly how much leave is available and when it will end; when you have more than one reason for terminating an employee, communicate all viable reasons at the time of termination.

Friends, Romans, Countrymen, lend me your . . .

You couldn't make this one up if you tried. 

The facts:  employee signs an employment contract accepting a two-year assignment to work in Manila; employee arrives in Manila and stays in a hotel while searching for an apartment for himself and his family; four days after his arrival, employee exits a restaurant and is suddenly kidnapped by three men who hold him hostage for three weeks, chain him to the floor, attempt to hang him, and torture him; the kidnappers seek an undisclosed amount of ransom from the employer; employer does not pay ransom until it receives a videotape (read Proof of Life) showing the kidnappers cutting off part of the plaintiff’s ear (graphic, but true).

The case:  slightly maimed, and no doubt, emotionally distressed, the employee makes his way to a court room halfway around the globe and sues his employer - in tort. The employer, not surprisingly, raised as a defense the language of the contract the employee had signed, which stated that workers’ compensation insurance would provide the exclusive remedy for injuries arising out of and in the course of his employment.  In the past, D.C. courts have adopted the “coming and going” rule, which provides that employee injuries sustained while en route to or from work are not in the course of employment and therefore are not compensable under the Workers’ Compensation Act. In this case the employer unsuccessfully argued that the plaintiff fell underneath an exception to the “coming and going” rule called the “traveling-employee” exception. Under this exception, employees injured while engaged in continuous travel because of the demands of the job are covered by workers’ compensation. The Court of Appeals, however, found that the “traveling-employee” exception did not apply in the instant case. Noting that the employer was unable to cite to any authority supporting the argument that an employee is converted into a “traveling-employee” because he starts a new job at a fixed out-of-state location, the Court stated that its decision reflects “the fact that the traveling employee exception cannot be used to bypass the jurisdictional limits of state workers’ compensation laws.”

The outcome:  the Court of Appeals allowed the employee's claims to proceed.

My opinion (not that you asked for it):  Not completely clear.  There's no doubt the employee's plight evokes sympathy, even though he was apparently held by kidnappers of questionably competence who "tried to hang him" but for some reason were unable to do so.  Nevertheless, the employer here appropriately contracted to provide for insurance to address workplace injuries.  Even though this is not the typical workplace injury, the law should allow employers to manage their risks.  Here, those efforts were rejected, essentially leaving the employer responsible for the actions of a third party it could not possibly predict or control.

Ali Kahn v. Parsons Global Services Ltd., D.C. Cir., No. 04-7162, 11/15/05

Manage This

In this age of easily hurt feelings and heightened sensitivity to just about everything, it's nice to see a common sense decision in an employment case.  The Tenth Circuit just ruled - brace yourself - that a supervisor who "set goals and deadlines for an ongoing project, requested that [an employee] 1) keep track of her daily activities in fifteen-minute intervals for seven days, 2) work in her cubicle so [the supervisor] could more closely supervise her, and 3) inform [the supervisor] of dates she would be out of the office" did not constructively discharge the employee she was managing.  Turnwall v. Trust Co. of America, No. 04-1303 (10th Cir. 2005).

Apparently, shortly after the meeting in which Ms. Turnwall's supervisor set out the expectations described above, she "began to experience fatigue and memory loss" due to a medical condition, but never requested an extension or discussed the issue with her supervisor.  She just kept missing deadlines, and then claims she found it offensive when she was "criticized" for "dropping the ball."  She took intermittent leave under the FMLA during this time, went on a two-week vacation, then came back to work long enough to resign.  Then she sued for constructive discharge and intentional infliction of emotional distress. 

Thankfully, the Tenth Circuit held that the working conditions weren't objectively intolerable, and that there was no outrageous conduct, so they got it right.  But what does this lawsuit say about the average supervisor's ability to manage an employee who admittedly had problems prioritizing her work?  Goal setting and regular monitoring of progress are textbook management techniques, and were perfectly appropriate under these circumstances.  Nevertheless, the employer here had to defend a federal lawsuit, and a subsequent appeal, at no small cost, essentially because somebody couldn't handle criticism from a supervisor.

We are blessed with excellent Federal Judges here in the Eastern District of Virginia.  Ten years ago, one of them, the Honorable James Spencer, wrote perhaps the best description ever penned regarding the tendency in today's workplace for people to jump on the victim bandwagon:

"Personality conflicts are a fact of life, occurring in the work-place with the frequency of overly-demanding supervisors and crushed employee expectations. And yes, discrimination is also alive and well in America today. But one will not unearth invidious distinctions lurking beneath every act of discipline or every denial of advancement. Any attempt to argue otherwise trivializes the laws enacted to eradicate the bigotry that still blocks the path to individual achievement and inhibits our collective advancement.

It also fosters a culture of victims. This Court does not have the power to prevent the rain from falling into anyone's life, and is not about to intercede in every work-place squabble. Where, as here, the law offers no remedy, the responsibility for recovering from the occasional affronts of office life falls at the feet of the complainant.  Thus, a person who clings steadfastly to the belief that she has been unjustly wronged, when all the evidence suggests otherwise, risks more than a judicial defeat. She also imperils her own ability to rise above the normal setbacks of life and renders herself ill-prepared to face the next inevitable pitfall. And this self-inflicted wound is far more damaging.

To those souls who still labor under the heavy hand of illegal workplace discrimination, the doors of this Court will remain ever open. The pretenders, though, must learn to wrest control of their own lives from deleterious circumstances without seeking recourse from the courts."

Keegan v. Dalton, 899 F. Supp. 1503 (E.D. Va. 1995). 

Couldn't have said it better myself.

Taking a Bite out of the FMLA

A recent federal case coming out of St. Paul, Minnesota may save employers a headache when it comes to granting leave to their employees under the FMLA. Judge Donovan Frank, writing for the U.S. District Court for the District of Minnesota, rejected an employee’s FMLA claim outright that he was illegally denied leave for the maladies of sinusitis and a tooth-ache (hence the title - yes, it's corny). In Hastings v. Carlson Mktg. Group, Inc., D. Minn., No. 04-3370, 10/27/05), the court held that the plaintiff’s ills were not serious conditions under the FMLA as a matter of law, and granted summary judgment for the employer stating that neither a toothache nor sinusitis are qualifying serious health conditions. In this case the plaintiff was scheduled to return to work after a period of leave. Instead, when the plaintiff awoke that morning with “mind numbing” tooth pain, he phoned his secretary to say he would not be making it in until the afternoon. The plaintiff ended up sleeping until 5:00 pm and was soon thereafter terminated and told by his employer that it was too late to get medical certification for his absence. In this case, the plaintiff testified that he was only incapacitated for one day, not three or more as required by the FMLA in order to be a serious health condition. However, the court stated that even if plaintiff had not shot himself in the foot in this way, and could prove that he was incapacitated for more than three days, he still would fail to make a showing that a toothache constitutes a serious health condition. Moreover, the court rejected the plaintiff’s argument that the employer was estopped from arguing that the condition was not serious because it had failed to request medical certification. Although possibly a minor victory, this court decision will save employers from the headache of being required under the FMLA to deal with employees’ trivial (albeit “mind numbing”) health conditions. Sometimes, you just have to take a couple of aspirin and do your job. At least it’s not the employers who are required to take the pain killers this time.

Bringing Home the Bacon

After intense lobbying by pro-labor House Republicans, President Bush's Administration has decided to reinstate the prevailing wage provisions of the Davis-Bacon Act to the Gulf Coast Region. Labor Secretary Elaine Chao said late last week that the rule mandating local prevailing wages on projects over $2000 would come back into force effective November 8th. President Bush had suspended the rule in wake of Hurricane Katrina, based on a provision that allows the President to do so in the event of "national emergency." The suspension turned into a political hot button, often "confused" by the media as a suspension of minimum wage, which did not occur. Construction groups oppose the move to bring back the rule, saying it will impede the rebuilding process at a time when so much needs to be done to get the region back on its feet. Labor groups praised the move, countering that the people who got hurt when the rule went away were the workers actually doing the rebuilding. One thing is for sure: the move preempted what would have been a derisive fight in Congress over proposed resolution to bring prevailing wages back. And maybe one less derisive fight maybe isn't such a bad consequence.  I seem to recall something about choosing battles wisely . . . .