Friday, August 23, 2013

WIRTW #285 (the “back to school” edition)


photo

(Yes, I’m “that” dad).

Here’s the rest of what I read this week:

Discrimination
Social Media & Workplace Technology
HR & Employee Relations
Wage & Hour
Labor Relations

Thursday, August 22, 2013

Relying on stereotypes will put a target on your back


According to The Huffington Post, a group of Hispanic employees is suing Target for national origin discrimination. Their evidence—an internal memo that included the following “Multi-Cultural Tips” for its managers:

a. Food: not everyone eats tacos and burritos;

b. Music: not everyone dances to salsa;

c. Dress: not everyone wears a sombrero;

d. Mexicans (lower education level, some may be undocumented);

e. Cubans (Political refugees, legal status, higher education level); and

f. They may say ‘OK, OK’ and pretend to understand, when they do not, just to save face.

That’s a pretty good smoking gun, if you ask me.

It served as a good reminder about the dangers of stereotypes in the workplace.

There is no hiding that stereotypes—both positive and negative—exist. To some degree we all harbor them (and anyone who tells you differently is lying to you and themselves). The better job you do of insulating your business’s personnel decisions from stereotypes, the less often you will find yourself in need of my services—which is a positive stereotype you can embrace.

This post originally appeared on The Legal Workplace Blog.

Wednesday, August 21, 2013

Where’s Waldo? She’s teaching you a lesson on the high cost of sexual harassment


While employed as an electrical line worker for Consumers Energy Company from 2001 through 2005, Theresa Waldo claimed that she suffered the following incidents of sexual harassment, about which she complained to her supervisor, union rep, and HR manager, each of whom allegedly ignored her:

  1. She was repeatedly called derogatory and demeaning names, such as “bitch” and “wench.”
  2. Coworkers threw her purse out of a work truck and into the dirt, telling her that “there were no purses allowed in these trucks.” When she responded by carrying a smaller purse in her pocket, she was called a “dike.”
  3. Her coworkers refused to let her travel to a bathroom, instead telling her that if she “wanted to work a man’s job,” she had “to pee like a man.”
  4. Coworkers locked her in a porta-potty with duct tape.
  5. Coworkers isolated her at work sites by excluding her from lunch trips and forcing her to walk instead of riding in trucks with the male employees.
  6. There were sexually explicit pictures on the work trucks.

Based on the foregoing, a jury awarded Waldo $400,000 in compensatory damages and $7,500,000 in punitive damages on her sexual harassment claim. Applying Title VII’s damage caps, the trial judge reduced those awards to a combined $300,000. In addition to the capped damage award, the judge also awarded Waldo $684,506 in attorney’s fees, which the 6th Circuit affirmed.

Who wins these cases? According to Judge Sutton’s dissenting opinion, it’s the lawyers, not the litigants:

I join all sections of the majority’s opinion save one: its decision to uphold the district court’s award of $684,506 in attorney’s fees—all but $1,000 of the fees requested by Waldo’s attorney without any additional reduction for time or rate, including for all work incurred to lose the first jury trial, all work incurred to lose six of the seven claims (four of them state law claims) and for all work incurred to win $300,000 in the second jury trial. One can be forgiven for thinking that Waldo’s two attorneys, not Waldo, were the true winners. This is good work if you can get it.

Harassment takes a toll. It exactly a high emotional cost on the victim. It exacts a steep legal cost on the company defending a lawsuit that can be salacious and unpopular. Yet, as this case illustrates, the people that often win are the lawyers. It may sound odd for a lawyer to argue against litigation. Yet, as I’ve heard one of my partners espouse more than once, “When you’re litigating you’re losing.” This case is the perfect example. From start to finish, Theresa Waldo spent more than 8 years of her life (from June 2005 until August 2013) litigating. For that time and aggravation, not to mention the on-the-job harassment that she suffered, she was awarded $300,000. Her lawyers, on the other hand, pocketed more than double that amount.

Who really won, and what does this case teach us about the benefit of evaluating the risk of cases and resolving those that have merit.

Tuesday, August 20, 2013

Why you should take all harassment complaints seriously


Today I am going to discuss two racial harassment cases decided by the same court, on the same day, but with different results.
  • In Paasewe v. Action Group, Inc. (6th Cir. 7/17/13), the plaintiff alleged that he was called “boy,” threatened because he wore a Barack Obama t-shirt, and was demeaned because he was a black man driving a nice car. The court concluded that a jury question existed on whether Paasewe’s allegations gave rise to a racially hostile work environment.
  • In Nicholson v. City of Clarksville (6th Cir. 7/17/13), the plaintiff alleged that co-workers repeated used the n-word and other offensive phrases to describe African-Americans, in addition to incidents of profanity directed at African-American employees. The court concluded that no jury could reasonably concluded that Nicholson had been subjected to a racially hostile work environment, and affirmed the trial court’s dismissal of his harassment claim.
You can read each of these cases for yourself, and come up with good arguments for, and against, the employer in each. The point I want to make, however, runs deeper than any analysis of the legal merits (or lack thereof) of each case. Deciding whether a workplace is sufficiently “hostile” to support a harassment claim under the civil rights laws is highly subjective. One judge’s or jury’s illegal hostile environment is another’s workplace triviality.
An employer’s primary goal should not be to win these cases on their merits when filed, but to prevent them from being filed in the first place. How does a business accomplish this goal?
  • Have a written anti-harassment policy.
  • Provide periodic anti-harassment training.
  • Foster open channels of communication between employees and management.
  • Take all workplace complaints seriously by investigating each (no matter how trivial it may seem), and by imposing effective remedial action if necessary.
  • Maintain a diverse workforce.
Cherry picking only those complaints that you believe are serious or legitimate opens up to scrutiny those complaints that are buried or ignored, which, in the hands of the right plaintiff could prove to be an expensive omission.

Monday, August 19, 2013

How to draft an enforceable noncompete agreement in 5 steps


According to the Wall Street Journal, litigation over noncompete agreements is rising:
More employers are requiring their new workers to sign “noncompete” agreements, which they say are needed to prevent insiders from taking trade secrets, business relationships or customer data to competing firms when they leave.… 
The number of published U.S. court decisions involving noncompete agreements rose 61% since 2002, to 760 cases last year…. Since most cases are settled out of court and most opinions aren’t reported, that tally is likely low.
Yet, having an employee sign a noncompete agreement and being able to enforce that agreement against that employee are two completely different animals. In today’s job market, courts have become increasingly skeptical of agreements that limit an employee’s ability to find employment.

Thus, what steps can you take to maximize your ability to enforce the agreements that your employees sign? Here are 5 practical steps.

1. Pick the right type of covenant. What type of competition are you trying to protect? Are you trying to protect your company’s most guarded secrets from you biggest competitors, or are you trying to prevent a salesperson from cherry picking your customers? If all you need is an agreement prohibiting an employee from soliciting customers, clients, or vendors, then limit the agreement to protect that interest. Putting it another way, if all you need is a no-solicitation agreement to protect your legitimate interests, then only require such an agreement as a condition of employment. Do not cast too wide a net, or a court will either narrow it for you, or, worse, toss out the entire out to sea.

2. Know your jurisdiction. Different states have different laws pertaining to the enforceability of noncompete agreements. California, for example, will only enforce such agreements in very limited circumstances, while Ohio will enforce any agreement reasonable in time, geographical scope, and the legitimate interest you seek to protect. Picking the right state’s law to apply to your agreement could make the difference between and enforceable contract and a worthless piece of paper.

3. Provide consideration. An employee must receive something of value in exchange for giving up the right to compete. If the covenant is signed at the beginning of employment, the hiring itself usually meets this requirement. For current employees, though, what qualifies as “value” varies from state to state. In Ohio, for example, a keeping an at-will employee employed is enough. Other states, however, require something of monetary value, such as a raise, bonus, or extra vacation days.

4. Enforce, enforce, enforce. Do not be selective in enforcing your contracts. Suppose Employee A and Employee B are subject to the same noncompete covenants. Employee A quits and works for a competitor, and you ignore it. If Employee B does the same, but you sue to enforce that noncompete, you will have a hard time proving the legitimacy of the business interest you are seeking to protect in light of the fact that you chose to ignore the same as to Employee A.

5. Ask for help. The Internet is a wonderful tool. A wealth of information is a world away. In the click of a mouse you can learn who led the National League in stolen bases in 1971 (it’s Lou Brock), or you can find examples of noncompete agreements. Be wary, though, of using these examples in your business without first having your counsel vet them. As noted above, laws vary from state to state. They also change from year to year as new statutes are passed, old statutes are amended, and court pass judgment on various legal issues. No matter the quality of the appearance of the form you locate or the trustworthiness of site on which you find it, you have no idea when it was drafted, which state’s law under which it was drafted to comply, or if counsel ever reviewed it. There is nothing wrong with a little DIY legal work on the Internet. There is a lot wrong, however, with all your legal work being DIY. If you don’t want to pay your lawyer to start from scratch, at least let him or her review your forms and offer an opinion on their viability in your specific jurisdiction.

These five steps aren’t the only considerations in drafting a strong, enforceable noncompete agreement. But, they are a good foundation to placing you in the best position to protect your business from an employee trying to work for a competitor.

Friday, August 16, 2013

WIRTW #284 (the “help if you can” edition)


I’ve never used this space to ask anyone to donate to anything. This week is an exception.

My niece had a scare. After months of knee pain, doctors found a 6 cm mass on her tibia. We feared the worst. After Wednesday’s surgery we received the best possible news—a benign giant cell tumor that had eaten away her leg until her tibia resembled Swiss cheese. She is on the road to recovery, which includes long and difficult rehab coupled with the risk that her repaired and rebuilt leg could fail.

She also faces crippling out-of-pocket medical expenses that will saddle her family for years, which includes my 1- and 2-year-old great-nieces, and her husband, a veterinary resident who’s taken an unpaid leave of absence to be with his family.

If you want to read the entire story, jump over to EncouragingErin.com, a blog/donation site we established to help my niece and her family. All help, thoughts, and words of encouragement are appreciated. Thanks for reading.

Here’s the rest of what I read this week:

Discrimination

Social Media & Workplace Technology

HR & Employee Relations

Wage & Hour

Labor Relations

Thursday, August 15, 2013

Clearing up some misconceptions on social media and privacy


“Bosses force woman to show Facebook page to prove she's not lying,” reads this headline on the venerable technology website, CNET. According to the article, the New Zealand Employment Relations Authority has required a fired flight attendant to provide her ex-employer with access to her Facebook page to prove, or disprove, the fact that her use of sick leave was legitimate.

What follows are three incorrect statements in an attempt to deconstruct this issue:
  1. “If such precedents continue to be set, everything that is digitally accessible may become evidence if an aggressive litigator decides that it might be useful.” In reality, the precedents are wildly inconsistent. Courts across the country are weighing the privacy rights of a litigant versus the relevance of the requested social media information. In this case, the judge favored the latter. A different judge could have reached a different result. One case, however, cannot be read as an indictment of the erosion of personal privacy rights.
  2. “Employers all over the world have begun to demand Facebook access to private accounts—some at the job interview stage.” This statement is not one of fact, but instead one of hyperbolic opinion. In reality, my research reveals that very few employers engage in this practice. Don’t just take my word for it. Also take the word of an Australian law firm that conducted a similar survey, with similar results.
  3. “Six U.S. states have now deemed it illegal for employers to do this.” In gross over-reaction to this issue, it’s sadly 11 states that have banned employers from requiring access to an employee’s social media account. Regardless, these laws do not prohibit a judge from providing access as part of the discovery process.
Employers are not requiring employees to turn over access to their personal social media pages. Court sometimes require litigants to turn over social media information when it might be helpful to prove or disprove a claim. End of story.

Wednesday, August 14, 2013

6th Circuit permits employers to enforce reasonable call-in rules for FMLA leave


In Cavin v. Honda of America Manufacturing, he 6th Circuit held that “the FMLA does not permit an employer to limit his employee’s FMLA rights by denying them whenever an employee fails to comply with internal procedural requirements that are more strict than those contemplated by the FMLA.” Six years later, however, the Department of Labor amended the key FMLA regulation that underpinned the Cavin decision. 

That regulation, 29 C.F.R. § 825.302(d) now reads as follows:

An employer may require an employee to comply with the employer’s usual and customary notice and procedural requirements for requesting leave, absent unusual circumstances.… Where an employee does not comply with the employer’s usual notice and procedural requirements, and no unusual circumstances justify the failure to comply, FMLA-protected leave may be delayed or denied.

So, what happens now when an employer has a call-in rule that is more strict than the FMLA? According to White v. Dana Light Axle Manuf. (6th Cir. 8/7/13) [pdf]:

An employer may enforce its usual and customary notice and procedural requirements against an employee claiming FMLA-protected leave, unless unusual circumstances justify the employee’s failure to comply with the employer’s requirements.

What does this case mean for you? It means that you should consider implementing reasonable call-in requirements to help curb FMLA abuse and over-use. If the statute allows you to take advantage of these policies, why not help level the playing field against a statute that, more often than not, favors the employee.

Tuesday, August 13, 2013

Federal court slams the door on EEOC’s criminal background check lawsuit


In EEOC v. Freeman (D. Md. 8/9/13) [pdf], the U.S. District Court for the District of Maryland dismissed a race discrimination lawsuit filed by the EEOC. Consistent with its Enforcement Guidance on the Consideration of Arrest and Conviction Records in Employment Decisions under Title VII, the EEOC alleged that Freeman’s criminal background checks on all job applicants violated Title VII by disparately impacting African-American job seekers.

In dismissing the lawsuit, the Court focused on the factual failings of the EEOC’s statistical expert. Eric Meyer’s Employer Handbook Blog has the details of the Court’s opinion.

The opinion also provides the most scathing indictment to date of the EEOC’s position on the use of criminal background checks by employers. Despite its length, it’s worth reprinting in its entirety.

For many employers, conducting a criminal history or credit record background check on a potential employee is a rational and legitimate component of a reasonable hiring process. The reasons for conducting such checks are obvious. Employers have a clear incentive to avoid hiring employees who have a proven tendency to defraud or steal from their employers, engage in workplace violence, or who otherwise appear to be untrustworthy and unreliable….

The present case is only one of a series of actions recently brought by the EEOC against employers who rely on criminal background and/or credit history checks in making hiring decisions. For example, in two recent complaints filed against discount retailer Dollar General Corp. and car manufacturer BMW, the EEOC claimed that those employers improperly used criminal background checks to bar potential employees, resulting in a disparate impact on African-American applicants….

Indeed, the higher incarceration rate [of African-Americans than Caucasians] might cause one to fear that any use of criminal history information would be in violation of Title VII. However, this is simply not the case. Careful and appropriate use of criminal history information is an important, and in many cases essential, part of the employment process of employers throughout the United States. As Freeman points out, even the EEOC conducts criminal background investigations as a condition of employment for all employees, and conducts credit background checks on approximately 90 percent of its positions….

By bringing actions of this nature, the EEOC has placed many employers in the “Hobson’s choice” of ignoring criminal history and credit background, thus exposing themselves to potential liability for criminal and fraudulent acts committed by employees, on the one hand, or incurring the wrath of the EEOC for having utilized information deemed fundamental by most employers. Something more, far more, than what is relied upon by the EEOC in this case must be utilized to justify a disparate impact claim based upon criminal history and credit checks. To require less, would be to condemn the use of common sense, and this is simply not what the discrimination laws of this country require.

This case is an important first step towards a reasoned and rational understanding of the role of criminal background checks for employers. The Freeman case, however, will not be the final word. District courts nationwide will face this issue and, depending on the judge hearing the case, will agree or disagree with the EEOC’s hard-line position. It will then be up to the appellate courts, and, hopefully, the Supreme Court, to have the final say.

In the meantime, employers need to understand that criminal background checks are the EEOC’s hit list. Regardless of how this issue ultimately plays out, using a conviction record as a disqualifying factor for employment without engaging in the individualized inquiry required by the EEOC’s Enforcement Guidance will raise the EEOC’s ire and could subject an employer to an enforcement lawsuit.

I am hopeful that, in the end, common sense will prevail and rescue employers from the Hobson’s choice recognized by the Freeman court. Until then, these practices remain risky. Employers will have to balance the risk of an EEOC enforcement action against the benefit to be gained from the access to and use of criminal conviction records in hiring and employment.

Monday, August 12, 2013

6th Circuit rejects contract that shortens statute of limitations for wage claims


Twice in the last three years, the 6th Circuit has signed off on contracts between an employer and employee that shortened the time for an employee to bring a discrimination claim (here and here). 

Last week, however, that same court reversed course and refused to recognize a contractual clause that limited an employee’s right to file a wage and hour claim.

In Boaz v. FedEx (6th Cir. 8/6/13) [pdf], the 6th Circuit reviewed the following clause in an employment agreement:

To the extent the law allows an employee to bring legal action against Federal Express Corporation, I agree to bring that complaint within the time prescribed by law or 6 months from the date of the event forming the basis of my lawsuit, whichever expires first.

Boaz sued FedEx in 2009—both for wage and hour violations and violations of the Equal Pay Act—that she alleged occurred between 2004 and 2008. FedEx moved to dismiss the lawsuit, claiming that the six-month limit in her employment agreement barred her claims.

The 6th Circuit disagreed:

An employment agreement “cannot be utilized to deprive employees of their statutory [FLSA] rights.” That is precisely the effect that Boaz’s agreement has here. Thus, as applied to Boaz’s claim under the FLSA, the six-month limitations period in her employment agreement is invalid.…

Congress enacted the Equal Pay Act as an amendment to the FLSA. By then the Supreme Court had already held that employees cannot waive their FLSA claims for unpaid wages and liquidated damages. We therefore presume that, by folding the Equal Pay Act into the FLSA, Congress meant for claims under the Equal Pay Act to be unwaivable as well.

FedEx argued to the 6th Circuit that this holding establishes a split among the statutory limitations periods that employers can contractually limit.

FedEx responds that courts have enforced agreements that shorten an employee’s limitations period for claims arising under statutes other than the FLSA—such as Title VII. And FedEx argues that the discrimination barred by Title VII (i.e., racial discrimination) is just as bad as the discrimination barred by the FLSA, and hence that, if an employee can shorten her Title VII limitations period, she should be able to shorten her FLSA limitations period too. 

The 6th Circuit rejected FedEx’s argument for two reasons. 

     First, unlike claims under the FLSA, employees can waive their claims under Title VII. 

     Secondly, an employer that violates the wage and hour laws gains a competitive advantage that does not exist by violating the FLSA.

Despite this case, I still believe that agreements that lessen statutes of limitations are an important tool to limit risk, especially in a state like Ohio, which has a six-year statute of limitations for discrimination claims (except age). If nothing else, you can limit your risk for discrimination and other employment claims, even if your wage-and-hour risk might carry forward longer. 

Friday, August 2, 2013

WIRTW #283 (the “vaycay” edition)


According to a recent survey conducted by TeamViewer, 52 percent of employed Americans plan on working during their summer vacations. While it will be impossible for me to get away from email, I will be taking the week off from writing blog posts.

I’ll see everyone with fresh content on Monday, August 12. In the meantime, however, do not forget that the deadline to submit your nominees for consideration in the ABA Journal’s Blawg 100 is Friday, August 9.

Here’s the rest of what I read this week:

Discrimination

Social Media & Workplace Technology

HR & Employee Relations

Wage & Hour

Labor Relations

Thursday, August 1, 2013

What to look for in the coming year from the EEOC


Yesterday, I had the pleasure of speaking on social media at ACI’s Employment Discrimination Conference in New York City. One of the benefits of speaking at such an event is the ability to hear the other great speakers. Yesterday was no exception.

The conference’s keynote speaker was Constance Barker, one of the EEOC’s two Republican Commissioners. She was thoughtful and eloquent in sharing her personal opinion on the direction of her Agency.

One of the highlights of her remarks was the sharing of four issues on the Agency’s radar that she expects will appear as formal, written Enforcement Guidance in the coming year.

Needless to say, the EEOC’s activism is not going away (at least between now and 2016). Employers need to keep an close eye on these issues as the develop in the future at the Agency.

Wednesday, July 31, 2013

Fired news reporter, Shea Allen, illustrates the meaning of “profersonal” for today’s workers


It’s exactly a year to the day that I first wrote about the disappearing line between the professional and personal online. Jason Seiden, the co-founder and CEO of Ajax Social Media, calls it profersonal, social media’s intertwining of our professional and personal personas.

Yesterday, the Today Show brought us a textbook example. Shea Allen, a Hunstville, Alabama, television news reporter, lost her job because of a post she wrote on her personal blog. The post, entitled, “No Apologies: Confessions of a red headed reporter,” included the following:

  • I’ve gone bra-less during a live broadcast and no one was the wiser.
  • My best sources are the ones who secretly have a crush on me.
  • I am better live when I have no script and no idea what I’m talking about.
  • I’m frightened of old people and I refuse to do stories involving them or the places they reside.
  • I’ve taken naps in the news car.
  • If you ramble and I deem you unnecessary for my story, I’ll stop recording but let you think otherwise.

That an employee was fired for something she posted on her personal blog is not necessarily newsworthy. However, it makes for an interesting juxtaposition with a recently published report on business ethics and social media.

According to the National Business Ethics Survey® of Social Networkers:

  • 79 percent of social networkers (defined as an employee who has an account on at least one social network) consider how their employer would react before posting something work-related on a personal social networking site
  • 64 percent consider how their employer would react to personal information posted to a personal site
  • 26 percent believe it is acceptable to post about their job even if they do not identify their employer.

It is comforting to read that nearly 8 out of 10 social networkers consider their employer before posting. Yet, when one considers that according to the Today Show, 53 percent of Americans side with Shea Allen and feel that she shouldn’t have lost her job, it is clear that there still is work to be done in educating employees about what it means to profersonal.

Thus, I’ll leave you with my words on this topic from one year ago, which bear repeating:

Employees need to realize that anything they say online can impact their professional persona, and that every negative or offensive statement could lead to discipline or termination (even if employers can overreact in these situations). Until people fully understand that social media is erasing (has erased?) the line between the personal and the professional, these issues will continue to arise. It is our job as employers to help educate our employees about living in a “profersonal” world.

Tuesday, July 30, 2013

The DOL’s “Fair Labor Data Challenge” presents an interesting strategy, but is it fair?


The Department of Labor is asking for help to create an iPhone/Android app to aid employees in tracking corporate wage-and-hour compliance.

The DOL Fair Labor Data Challenge will “help consumers locate … establishments and view their federal enforcement and violations history as well as read consumer reviews to help them decide where to spend their hard-earned wages.”

According to the DOL, the “app … would work with existing social media and would allow consumers to see if an establishment that they want to frequent has been in compliance with federal labor laws.” Its hope is that by “providing consumers with information at their fingertips about which businesses have treated their workers fairly and lawfully, the app will empower them to make informed choices about where to shop, eat, or even vacation.” Thankfully, in addition to flagging underpaying scofflaws, it “also will recognize those employers who are doing the right thing and playing by the rules.”

In other words, the DOL wants to shame employers into wage-and-hour compliance. The DOL itself says, “Our investigators can’t be in every workplace, and we’ll never reach every establishment through our traditional forms of outreach.” So, to compensate for its enforcement black-hole, the DOL is turning to viral outreach to create a way for people to soft-boycott those businesses that employees say do not comply with the wage-and-hour laws.

I will be very curious to see what this final product looks like if it ever hits the App Store. For this app to live up to its “fair” name, it must provide employers the ability to rebut negative comments. Otherwise, this app will be nothing more than a one-sided vent for disgruntled employees. Regardless, employers should keep this issue on their radars as yet another reason to get their wage-and-hour practices in line.

Monday, July 29, 2013

Court rejects use of social media evidence in defense of wage-and-hour claim


One of the difficulties employers face in defending wage and hour lawsuits alleging “off-the-clock” work is how to prove a negative. The employees say, “We worked during our lunch breaks,” (for example), and the employer says, “No they weren’t.” The trick, however, is how to prove that negative.

Could social media provide some help? If employees are posting to Facebook, Twitter, etc. at time during which they claim to have been working, can an employer argue that the posts help establish that the employees could not have been “working” during those times?

In Jewell v. Aaron’s, Inc. (N.D. Ga. 7/19/13) [pdf], the employer attempt to make that exact argument. To help prove its claim that the employee-class members did not work through their lunch breaks, Aarons sought an order compelling the production of the plaintiffs’ social media activities “during their working hours.”

Despite the limited nature of the request to “working hours” only, the district court still rejected this request:

Even though certain social media content may be available for public view, the Federal Rules do not grant a requesting party “a generalized right to rummage at will through information….” Defendant has not made a sufficient predicate showing that the broad nature of material it seeks is reasonably calculated to lead to the discovery of admissible evidence…. The exemplar evidence of Kurtis Jewell’s Facebook activity does not persuade the Court that the Facebook postings will show, contrary to Plaintiffs’ claims, that they were not forced to work through their meal periods. The Court agrees with Plaintiff that whether or not an opt-in plaintiff made a Facebook post during work may have no bearing on whether or not the opt-in plaintiff received a bona fide meal period may have no bearing on whether or not the opt-in plaintiff received a bona fide meal period….”

If this employer was merely guessing that there might exist something useful in the plaintiff’s Facebook account, I would have a easier time understanding the Court’s belief that the employer was fishing. This employer, however, was relying on actual time-stamped examples from the lead plaintiff’s Facebook profile [pdf].

I applaud this employer’s attorneys attempted creative use of social media to defend this wage-and-hour claim, and am troubled by this Court’s unfair hamstringing of that effort.

Friday, July 26, 2013

WIRTW #282 (the “shut yo’ mouth” edition)


Language and race have been in the news lately. From Trevon Martin to Paula Deen, it seems that everyone is talking about the meaning of race in 2013-America. It seems appropriate, I suppose, to share this video, and, maybe, bring a little levity to a very serious topic. 

Here’s the rest of what I read this week:

Discrimination

Social Media & Workplace Technology

HR & Employee Relations

Wage & Hour

Labor Relations

Thursday, July 25, 2013

Giving Employee the “Milton Treatment” Leads to Discrimination Claim


And I said, I don’t care if they lay me off either, because I told, I told Bill that if they move my desk one more time, then, then I’m, I’m quitting … I’m going to quit. And, and I told Dom too, because they’ve moved my desk … four times already this year, and I used to be over by the window, and I could see … the squirrels, and they were merry, but then, they switched … from the Swingline to the Boston stapler, but I kept my Swingline stapler because it didn’t bind up as much … and I kept the staples for the Swingline stapler and it’s not okay because if they take my stapler then I’ll have to … I’ll set the building on fire...

– Milton Waddams, Office Space

I love the movie Office Space. One of the movie’s best sub-plots involves Milton Waddams. Milton works for Bill Lumbergh, and is Lumbergh’s punching bag. Lumbergh belittles him, steals his red Swingline stapler, continuously reduces the size of his cube, and, ultimately, transfers him to a basement storage closet. All the while, Milton mumbles under his breath that he’s going to set the building on fire. True to his word, Milton ultimately gets his revenge by burning down the office.

Why am I telling you the plot of Office Space? Because, according to this story in the St. Joseph, Missouri, News-Press, a former employee of the Missouri Department of Transportation is alleging that the department discriminated against her because of her age by … are you ready … moving her out of her office and forcing her to work from a moldy storage closet.

While there are two sides to every story, generally it is a bad idea to react to an employee’s internal complaint about age discrimination by moving her workspace from an office to a storage closet. Milton earned his revenge by arson. This employee is seeking hers via the courts. Either way, giving any employee the Milton treatment, let alone doing so on the heels of a complaint about discrimination or some other protected activity, is a horrendous idea.

This post originally appeared on The Legal Workplace Blog.

Wednesday, July 24, 2013

Is this the worst fake doctor’s note ever? And what could you do about it?


Buzzfeed recently published the above note, which an employee provided asking his boss for a day off from work. Not only did the employer refuse the time off, but, as you can see above, the employer edited the note, remarked on all of the typos, errors, and misspellings, and returned it to the employee with the caption, “How NOT to fake a doctor’s note.”

Even though an employer might have every reason to believe that a doctor’s note is fake, an employer runs the risk of an FMLA violation by summarily denying time off without following the FMLA’s procedures for authenticating a medical certification.

Authentication

  • The FMLA permits an employer to contact the medical provider who purported to provide the certification to authenticate the document.
  • Authentication means providing the health care provider with a copy of the certification and requesting verification that the health care provider who signed the document completed or authorized it.
  • An employer may not request any additional medical information.
  • An employer must first provide the employee with the opportunity to authenticate the note.
  • If, however, the employee fails or refuses, the employer, through a health care provider, human resources professional, leave administrator, or management official—but not the employee’s immediate supervisor—may contact the employee’s health care provider directly for purposes of authentication.

Second and Third Opinions

An employer who has reason to doubt the validity of a medical certification may require the employee to obtain a second (and possibly third) opinion:

  • The second opinion must be at the employer’s expense.
  • Pending receipt of the second opinion, the employee is provisionally entitled to all of the benefits of the FMLA, including intermittent leave. If the certifications do not ultimately establish the employee’s entitlement to FMLA leave, the employer then has the right to retroactively designate the leave as non-FMLA.
  • An employer is permitted to designate the health care provider to furnish the second opinion, but the selected health care provider must be one that it does not regularly contract with otherwise regularly use the services of.
  • If the opinions of the employee’s and the employer’s designated health care providers differ, the employer may require the employee to obtain certification from a third health care provider, again at the employer’s expense. This third opinion is final and binding.
  • Upon request by the employee, an employer is required to provide the employee with a copy of the second and third medical opinions within five business days of such request.

Your gut instinct might say fire this employee, but following that instinct could get you in trouble under the FMLA if note turns out to be legit. Following the FMLA’s rules for authentication, and second and third opinions, will give you the legal ammo to fire the offending employee. In the meantime, place the employee on conditional FMLA leave, which is unpaid. A few weeks down the road, once you confirm that the note is inauththentic, you can fire the employee without having incurred much expense or burden in the interim (save a couple of medical exams if you have to go the route of second and third opinions).

For more on verifying FMLA leaves of absence, I recommend Jeff Nowak’s recent post on his FMLA Insights Blog, entitled, Is Your Employee Paying a Deception Service to Provide You a Fake Doctor's Note or FMLA Certification?

Tuesday, July 23, 2013

Instagram, Vine, and … the NLRB (uh-oh)


Are you concerned about the impact of micro photo and video sites such as Instagram and Vine on your workplace? For the past few months, Dan Schwartz, writing at his Connecticut Employment Law Blog, has been all over this issue, suggesting that in light of the growing popularity of these sites, now more than ever employers need social media policies, while also cautioning that the regulation of workplace photos and videos would be the next social media enforcement frontier for the NLRB.

It appears that Dan’s prediction was right on the money. Last week, the NLRB’s Office of General Counsel published an Advice Memorandum [pdf] (dated March 21, 2012, but, for reasons unknown, which sat unpublished for 16 months).

Among other issues, the memo took up the following prohibition in a supermarket chain’s social media policy:

Do not use any … photographs or video of the Company’s premises, processes, operations, or products, which includes confidential information owned by the Company, unless you have received the Company’s prior written approval.

According to the NLRB Office of G.C., that policy is, on its face, an overly restrictive ban on employees’ rights to engage in protected concerted activity:

We further find that the portion of the rule prohibiting employees from photographing or videotaping the Employer’s premises is unlawful as such a prohibition would reasonably be interpreted to prevent employees from using social media to communicate and share information regarding their Section 7 activities through pictures or videos, such as of employees engaged in picketing or other concerted activities.

Amazingly, the only citation provided in support of this broad legal statement is a 22-year-old case, which held that an employee’s tape recording of a jobsite to provide evidence in a Department of Labor investigation is protected. Folks, there is a huge difference between recording something at work to gather evidence for a government investigation, and this.

The NLRB needs to allow employers to promulgate reasonable rules that protect their legitimate interests (e.g., confidentiality, or ensuring that employees are actually working during working hours), while protecting the rights to employees to engage in legitimate protected activity (e.g., complaining about discrimination or working conditions, or gathering evidence for a government investigation). Otherwise, the NLRB is attacking facially neutral policies because of an imagined parade of horribles that could never materialize, all the while making it exceedingly difficult for businesses to draft policies that establish reasonable baseline expectations for workers and management.

Hat tip: Labor and Employment Law Perspectives

Monday, July 22, 2013

“That guy” has a valid retaliation claim?


small__4898751003Every workplace has “that guy.” The employee who can’t quite seem to keep his mouth shut, who says inappropriate things, the one you know will someday lead to a harassment lawsuit. (Hint: If you can’t think of who “that guy” is in your workplace, it might be you).

Dunn v. Automotive Finance Corp. (M.D. Tenn. 7/2/13) is about “that guy,” but with a twist. “That guy” was Robert Dunn, a manager terminated by Automotive Finance Corp. for making inappropriate racially based comments during a social gathering following a training session. Present for Dunn’s alleged comments were four other white managers, along with one African-American assistant manager, Rick Hopkins. Several of those present complained about Dunn’s comments; the company investigated and fired Dunn.

Dunn was accused of making three racially insensitive comments:

  • A comment that Tiger Woods was being judged by a white man’s standard, as compared to Michael Vick, who went to prison.
  • A comment that his mother was Indian and not allowed to sit with White people back in the day.
  • In reference to a statement that Hopkins would be the next manager at the company, Dunn said, “Good luck. Have you seen a family photo of this place?” and that the company had very few African-American managers “walking the halls.”

    What was Dunn’s explanation when a co-worker expressed her discomfort at his statements? “That’s just how I am, because I’m a country boy.” When that same co-worker complained to management about Dunn’s comments; the company investigated and fired him.

    Here’s the twist. Dunn sued for retaliation, claiming that Title VII protected his comment about a lack of upward mobility for African-Americans within the company. Incredibly, the court agreed that Dunn’s statement at least presented a question for a jury to determine as to whether that comment is protected from retaliation under Title VII.

      Dunn made one comment or a set of comments that could reasonably be construed as protected activity: complaining in front of the Branch Managers that AFC discriminated on the basis of race with regard to promoting black managers. There are competing accounts as to precisely what Dunn said, although the witnesses who recall the incident appear to agree that Dunn accused AFC of being a racist company and/or that Dunn stated that AFC would not promote Hopkins because he is black…. The fact that Dunn made this comment in front of a black Assistant Branch Manager and that it made the white employees “uncomfortable” was just a side effect of speaking his mind that the company had and would continue to practice illegal racial discrimination.

      The company argued that Dunn was merely seeking “to insulate himself from the consequences of [his] inappropriate conduct by concocting a post hoc rationalization that he had actually engaged in some form of ‘opposition’ activity.” I agree.

      Cases like this one undermine the protections offered by the anti-retaliation laws, and send the wrong message to employers. The company fired Dunn because a co-worker complained about inappropriate race-based comments. The employer met is obligation under Title VII to investigate the allegations, and implement corrective measures to ensure that the comments stopped. Yet, the employer got punished for meeting its anti-harassment obligations. If the employer retained Dunn, it could have faced a potential harassment lawsuit. An employer should not have to choose between a harassment lawsuit by an offended employee, or a retaliation lawsuit by an alleged harasser who appears less than genuine in his “complaints.”

      This case also is a perfect example of the maxim that any employee can sue at any time for any reason, and helps illustrate my point that because of the risk of lawsuits, employers are exceedingly gun-shy about firing employees.

      photo credit: foreverdigital via photopin cc

      Friday, July 19, 2013

      WIRTW #281 (the "is it live or is it Memorex" edition)


      Earlier this week, I appeared on Huffington Post Live, in a segment discussing discrimination laws, at-will employment, and the rights of employers to terminate employees. If you missed it live, here’s your chance to see me live and in Internet-buffered color:


      Also, if you missed this month’s Employment Law Blog Carnival, hosted by Robin Shea, it is worth a trip down Route 66 to read the best employment-law posts from the past month.

      Here’s the rest of what I read this week:

      Discrimination

      Social Media & Workplace Technology

      HR & Employee Relations

      Wage & Hour

      Labor Relations

      Thursday, July 18, 2013

      Ohio Supreme Court strikes blow to class action lawsuits


      In recent terms, the U.S. Supreme Court has shown some hostility to class action lawsuits. 
      • In Wal-Mart v. Dukes, the Court concluded that a district court must examine the underlying merits of a claim to determine if class certification is appropriate, and that a class must have some glue binding disparate decisions to justify certifying all of those decisions for consideration in one class. 
      • In Comcast v. Behrend, the Court expanded upon Dukes by concluding that a class that requires individualized proof to establish damages for each class member cannot survive as a class action.
      The impact of these two decisions might to send class litigants, if possible, to state court. Dukes and Comcast are federal decisions under Federal Civil Rule 23. If a state’s class-action-certification rules are more lenient, then the class’s attorney will do whatever it takes to keep the class in state court. 

      Yesterday, however, the Ohio Supreme Court made this strategy much more difficult. Stamcco, LLC v. United Telephone Co. of Ohio [pdf], is not an employment case. It involves allegations of cramming — claims that the defendant added unauthorized charges the class members’ telephone bills. Yet, this case has huge implications for how all class actions are litigated under Ohio law, including classes alleging, for example, violations of Ohio’s employment discrimination or wage and hour laws.

      With extensive citations to, and discussion of, Dukes, the Court held:
      At the certification stage in a class-action lawsuit, a trial court must undertake a rigorous analysis, which may include probing the underlying merits of the plaintiff’s claim, but only for the purpose of determining whether the plaintiff has satisfied the prerequisites of Civ.R. 23.
      Implicitly adopting the logic of Comcast, the Court also held:
      We now recognize that the need for individualized determinations is dispositive in concluding that the class does not comport with Civ.R. 23.
      Rejecting the plaintiff’s claim that a court could apply a simple formula to data provided by the defendant to determine each member’s claim, the Court concluded that this case cried out for individualized determinations:
      Unauthorized third-party charges are better resolved on an individual basis with the third party or UTO. UTO’s phone bills identify third-party charges, the entity responsible for the charge, and a toll-free number for billing inquiries. Moreover, UTO claims that it has a policy of removing third-party charges for the purpose of maintaining good will with its clients. Finally, for larger charges or where the charge cannot be resolved over the phone, small-claims court is also an option. Accordingly, because ascertaining whether third-party charges are authorized will require individualized determinations, common issues do not predominate.
      One could apply the same logic to wage and hour claims. If an employer has, for example an open-door policy, and will consider providing redress to employees on a case-by-case basis for complaints about missing wages, one cannot apply a simple formula to calculate class-wide damages. Moreover, while the plaintiffs’ bar will lose their minds over the idea of small-claims court, it remains a viable option for employees to inexpensively litigate their right to missing wages. The $3,000 limit for small claims will cover the vast majority of individual wage and hour claims.

      Stamcco is a huge victory for Ohio businesses. It is now that much harder to establish a class action, confirming that Ohio’s class-action rules fall in line with their federal counterparts.

      Wednesday, July 17, 2013

      Who owns personal email on an employer-issued smartphone?


      The following scenario is playing out in companies all over America. A company issues a smartphone to an employee. The company owns and pay for the device, but allows the employee to use the device for personal reasons, including accessing a personal email account, such as Gmail. The employee returns the phone, but does not first erase her personal email from the device. Is it legal for the employer, who owns and pays for the phone, to access the employee’s personal email account after the device’s return?

      According to Lazette v. Kulmatycki (N.D. Ohio 6/5/13), the answer is no. In Lazette, the facts alleged are significantly worse than my fact-pattern above. After Lazette returned the phone, her supervisor, over the course of 18 months, surreptitiously read 48,000 of Lazette’s personal emails, including those involving her family, career, financials, health, and other personal matters.

      The meat of the decision concerns whether the employer violated the Stored Communications Act (although Lazette also brought federal- and state-law wiretap claims, and common law claims for invasion of privacy and intentional infliction of emotional distress. The Stored Communications Act prohibits the unauthorized access of personal email and other Internet accounts. Think of it as an anti-wiretapping law for the Internet. The court refused to dismiss the Stored Communications Act claim, concluding that Lazette had pleaded sufficient facts in her complaint for the case to proceed to discovery. if you are at all interested in the SCA, what it covers, and how it works, I commend this case to your reading list.

      Aside from the legal intricacies of the Stored Communications Act, this case raises important practical considerations about the risks companies are taking via the use of mobile devices at work. Smartphones aren’t going away. Indeed, if you’re anything like me, it’s become more of an appendage than a phone. So, how should companies manage the risks of these devices under increasing judicial scrutiny and application of the Stored Communications Act? Let me offer three practical tips:

      1. Draft a policy. Under the Stored Communications Act, personal data is sacred. Telling employees that they do not have any expectation of privacy in company-owned mobile devices might not save you from a Stored-Communications-Act claim if one employee surreptitiously accesses another employee’s personal email account. For sure, have a policy that spells out an employee’s reasonable lack-of-privacy expectations, but have a similar policy statement prohibiting employees from accessing the personal email or other Internet account of others.
      2. Wipe the device. Curiosity might have killed the cat, but you shouldn’t let it kill your company. Left to their own devices, people will snoop. Don’t give them the opportunity to do so. When a mobile device is returned by an employee, wipe it clean of all personal information and data.
      3. But, quarantine it first. I suggest, however, that before you wipe a device you pause to make sure that you don’t need any data on the device. Once it’s wiped, it’s going to be very hard, if not impossible, to recover that data. Are there pending lawsuits for which data on that phone might be discoverable? If so, you better save it until you can determine what, if anything, needs to be preserved or produced. Are you concerned that the ex-employee might have been talking to a competitor or walked off with your trade secrets or other confidential or proprietary information? if so, you better check the phone to see if there is any evidence you can use to build your claim before you wipe it clean.

      (Hat tip: Privacy & Information Security Law Blog)

      Tuesday, July 16, 2013

      The one thing you can never release in a settlement agreement


      Legal disputes end in one of two ways—either with a judgment by a court or an agreement between the parties. The vast majority of cases follow the latter course.

      When parties enter an agreement to settle a dispute—either in a settlement agreement ending litigation or a severance agreement ending one’s employment—the goal is to release all claims brought, or that could have been brought. An employer is paying the employee, in part, for the certainty that the employee will not file other claims against it in the future for past acts. Thus, these agreements typically contain general releases, along with covenants not to sue.

      Do not, however, make the mistake of including in your agreement a covenant forbidding the employee from filing a discrimination charge with the EEOC or other agency. The EEOC will view such a provision as retaliatory under Title VII.

      Last week, the Agency announced that it had reached a settlement with Baker & Taylor over claims that the company “violated Title VII by conditioning employees’ receipt of severance pay on an overly broad, misleading and unenforceable severance agreement that interfered with employees’ rights to file charges and communicate with the EEOC.” The EEOC alleged that the company required employees “to sign a release agreement that could have been understood to bar the filing of charges with the EEOC and to limit communication with the agency” in order to receive their severance pay.

      The offending provisions (taken from the EEOC’s Complaint) were as follows:
      • “I further agree never to institute any complaint, proceeding, grievance, or action of any kind at law, in equity, or otherwise in any court of the United States or in any state, or in any administrative agency of the United States or any state, country, or municipality, or before any other tribunal, public or private, against the Company arising from or relating to my employment with or my termination of employment from the Company, the Severance Pay Plan, and/or any other occurrences up to and including the date of this Waiver and Release, other than for nonpayment of the above-described Severance Pay Plan.”
      • “I agree that I will not make any disparaging remarks or take any other action that could reasonably be anticipated to damage the reputation and goodwill of Company or negatively reflect on Company.  I will not discuss or comment upon the termination of my employment in any way that would reflect negatively on the Company. However, nothing in this Release will prevent me from truthfully responding to a subpoena or otherwise complying with a government investigation.”
      How could this problem have been avoided, while still providing the employer relative certainty that it will not have future legal dealings with the releasing employee? A simple disclaimer tacked onto the back-end of the release language, stating that nothing in agreement prevents, or is intended to prevent, the employee from filing a charge of discrimination with the EEOC, or with a state or local civil rights agency. You can couple that language with a covenant providing that in the event that the employee files such a charge, the employee disclaims the right to seek or recover money damages from such a filing.

      With this language, the employee retains the right to file a charge (minus damages), the EEOC retains the right to seek redress of civil rights violations, and the employer retains peace of mind that the employee has signed as strong of a release as Title VII allows.

      Monday, July 15, 2013

      Fight the power! A timeless lesson on employee relations from "What's Happening!!"


      As I settled in for a quiet Friday night in front of the TV, I stumbled upon one of my guilty pleasures — “What’s Happening!!” If your unfamiliar with this late 70s sitcom gem, it tells the story of three high-school friends growing up in the Watts section of Los Angeles, Raj, Dwayne, and Rerun, along with Raj’s pest of a little sister, Dee, their strong-willed single mom, Mabel, and the wise-cracking waitress at the local diner, Shirley.

      The episode upon which I stumbled is called One Strike and You’re Out. Its not as good as the classic “Doobie Brothers” episode, but, beggars can’t be choosers, right?

      Here’s the synopsis, courtesy of Wikipedia:
      Rerun being fired from the supermarket is the last straw for Raj, who rallies the rest of the workers to take some action against their boss Mr. Pronson. However, when the staff goes on strike, Raj finds himself in a jam, since Mama has lost her job and the family now has no source of income.
      Enjoy this little slice of sitcom history, which teaches the important and timeless lesson that appearances aren’t always what they seem with your employees, what motivates their actions might not be what you think, and employees have lives outside of work that can, and often do, impact how they behave on the job.

      Part One:



      Part Two: