WIRTW #275 (the “reality bites” edition)

Last night, Fox debuted its new reality show, Does Someone Have To Go?, which Entertainment Weekly bills as Survivor meets The Office. Here’s the premise:

 

Needless to say, the New York Times is not impressed, unflatteringly calling the show “a victory” for companies and horrible for employees:

The squabbles are petty, ill-informed and sometimes personal, and seemingly dredge up unacknowledged tensions around race and age…. The stakes, as they are presented, are dramatic. For signing up to be on this show, employees … run the risk of conflict, humiliation and, possibly, unemployment. (Presumably, these workplaces are not unionized.)

As for me, I was glued to the TV, and will be through this show’s run. Yet, I couldn’t help but think about the scope of the release agreement these employees had to sign before appearing on the show.

Did you watch? Share your opinion in the comments below, or on Twitter with the hashtag #WorkplaceReality

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

Discrimination

• Dear Evil Skippy: Was It Harassment For My Boss To Talk My Underwear? — from Evil Skippy at Work
• When an Employer Provides More Parental Leave to Mom than Dad, is this Gender Discrimination? — from FMLA Insights
• Sixth Circuit Upholds Summary Judgment for Employers in Two Cases Brought by Terminated Pregnant Employees — from Employer Law Report
• EEOC: no post-offer inquiries about family medical history — from Overlawyered
• Inquiring about Family Medical History Violates Genetic Information Nondiscrimination Law — from Maryland Employment Law Developments
• Pointers on avoiding Diabetes Discrimination — from Mike Haberman’s Omega HR Solutions
• Lawffice Links - New EEOC Publications Galore! — from Phil Miles’s Lawffice Space
• EEOC talks employer wellness programs; provides an ADA Q&A — from Eric Meyer’s The Employer Handbook Blog
• A sanctions award in EEOC v. Spitzer, the “don’t have your lawyer investigate” case — from Warren & Associates Blog

Social Media & Workplace Technology

• The Latest Social Media Concern for Employers — from WSJ.com
• Can an LLC member violate the Stored Communications Act by accessing other members’ email? — from Internet Cases
• Using Computer Forensics to Investigate IP Theft — from Law.com
• SMBs embrace BYOD, but slow to manage mobile devices — from ZDNet
• Act On Clarifying Ownership of Work-Related Social Media Accounts Before You Become “Dinner” — from Dan Schwartz’s Connecticut Employment Law Blog
• Sitting on Big Data: The Evolution of the Mobile Workplace — from Innovation Insights

HR & Employee Relations

• Do You Know the Seven Factors That Comprise “Just Cause”? — from Trade Secret / Noncompete Blog
• What About Office Romances? — from Evil HR Lady
• The Price Of Being Pregnant at Work — from HuffPost Live
• Debunking The 'No Friends At Work' Rule: Why Friend-Friendly Workplaces Are The Future — from Forbes
• Bullying bosses beware: Your targets may undermine you — from Minding the Workplace

Wage & Hour

• USDOL "Misclassification" Focus Continues — from Wage and Hour Laws Blog
• W.H.D.?: Here We Go Again … Independent Contractors Targeted Once More — from The Wage and Hour Litigation Blog
• 8th Cir: FLSA Plaintiffs Must Spell It Out — from Molly DiBianca’s Delaware Employment Law Blog
• Proposed Overtime Legislation Passes House, Faces Uphill Battle in Senate — from Impact Litigation Journal
• Wages, Salaries & Overtime – Oh My! 4 Myths About Employee Pay — from TLNT

Labor Relations

• NLRB takes aim at employer electronic communications and social policies — from EmployerLINC
• Senate Committee Approves President’s Nominations to the NLRB — from Wyatt Employment Law Report
• It’s a Little Too Little: Is The NLRB Headed Towards Irrelevance? — from Employment Essentials

Until next week:

(Bonus points if you know the link between the new wave hit My Sharona, by The Knack, and this post.)

When state law conflicts with the EEOC on criminal background checks, who wins?

Last year, the EEOC issued its long awaited Enforcement Guidance on the Consideration of Arrest and Conviction Records in Employment Decisions under Title VII. While the Guidance was much more fair and balanced than many employer advocates (me included) expected, it does include some head-scratchers for businesses. One such conundrum is how regulated employers are supposed to act when across-the-board criminal background searches are required by state law, as the EEOC takes the position that a blanket requirement violates Title VII.

Per the EEOC:

States and local jurisdictions also have laws and/or regulations that restrict or prohibit the employment of individuals with records of certain criminal conduct. Unlike federal laws or regulations, however, state and local laws or regulations are preempted by Title VII if they “purport[] to require or permit the doing of any act which would be an unlawful employment practice” under Title VII. Therefore, if an employer’s exclusionary policy or practice is not job related and consistent with business necessity, the fact that it was adopted to comply with a state or local law or regulation does not shield the employer from Title VII liability.

How is an employer supposed to handle this conflict? Waldon v. Cincinnati Public Schools, currently pending in the Southern District of Ohio, may provide some future guidance.

That case concerns the application of Ohio H.B. 190, which became law in 2007. That law requires criminal background checks of all current school employees, regardless of whether their duties involve the care, custody, or control of children, and mandates the termination of any employee with a certain number of historical convictions, regardless of the convictions’ age.

Two African-American employees challenge that H.B. 190 has an unlawful disparate impact because of race. Both were terminated based on decades-old convictions. All told, the Cincinnati Public Schools fired 10 employees as a result of background checks conducted pursuant to H.B. 190; nine of the 10 fired were African-American.

It is early in the litigation of the Waldon case. The court denied the employer’s motion to dismiss.

First, it concluded that it was clear that the Plaintiffs pleaded a prima facie case of disparate impact.

Although there appears to be no question that Defendant did not intend to discriminate, intent is irrelevant and the practice that it implemented allegedly had a greater impact on African-Americans than others.

The existence of statistically significant disparate impact, however, if only the first step in the analysis. An employer can avoid liability if the challenged practice is justified by business necessity. While the court believed this issue to be “a close call,” it ultimately concluded that it could not make that call on a motion to dismiss:

Obviously the policy as applied to serious recent crimes addressed a level of risk the Defendant was justified in managing due to the nature of its employees’ proximity to children. However, in relation to the two Plaintiffs in this case, the policy operated to bar employment when their offenses were remote in time, when Plaintiff Britton’s offense was insubstantial, and when both had demonstrated decades of good performance. These Plaintiffs posed no obvious risk due to their past convictions, but rather, were valuable and respected employees, who merited a second chance.… Under these circumstances, the Court cannot conclude as a matter of law that Defendant’s policy constituted a business necessity.

Talk about a tough position in which to place an employer. Does the employer violate state law or violate Title VII? Ultimately, I think the correct answer should be neither. Shouldn’t the need to follow state law provide the employer’s “business necessity?” If not, employers will be faced in the untenable position of following one law and violating the other.

photo credit: kevin dooley via photopin cc

This post originally appeared on The Legal Workplace Blog.

Email surveillance as evidence of retaliation

Employees should not operate under any false ideas that they enjoy an expectation of privacy in their work email accounts. Just because an employer has the right to snoop through an employee’s email, however, does not mean the practice does not carry some degree of risk.

Consider, for example, Fields v. Fairfield County Board of Developmental Disabilities (6th Cir. 12/6/12). Fields claimed that her employer retaliated against her after it discovered an email she sent to some co-workers threatening a lawsuit against the Board. The court concluded that the email surveillance was insufficient evidence of pretext.

Simple enough? What if, however, the claim was that the company only started watching her email after it learned of the protected activity, and used evidence of misconduct in the email to support the termination decision. Could the email surveillance, in and of itself, be an adverse action sufficient to support a claim of retaliation? The legal standard for an adverse action sufficient to support a claim of retaliation is very broad. Anything that “might have dissuaded a reasonable worker from making or supporting a charge of discrimination,” qualifies as a retaliatory adverse action. If you don’t regularly review employee email accounts, and only start examining an employee’s electronic activities after that employee engages in some protected activity, might that dissuade others from engaging in protected activity?

If you are going to enforce a policy or exercise some employer right (like surveillance of corporate email or computer systems), do it consistently, not selectively and only after an employee complains about discrimination. Otherwise, you could change a legal and reasonable act (e.g., email surveillance) into evidence of unlawful retaliation.

Social media is the digital water cooler

Let’s say your business is located in a less-than-desirable neighborhood. Three of your employees engage in the following conversation on their personal Facebook pages:

Holli Thomas — needs a new job. I’m physically and mentally sickened.

Vanessa Morris — It’s pretty obvious that my manager is as immature as a person can be and she proved that this evening even more so. I’m am [sic] unbelievably stressed out and I can’t believe NO ONE is doing anything about it! The way she treats us in [sic] NOT okay but no one cares because everytime we try to solve conflicts NOTHING GETS DONE!! …

Vanessa Morris — And no one’s doing anything about it! Big surprise!

Brittany [Johnson] — “bettie page would roll over in her grave.” I’ve been thinking the same thing for quite some time.

Vanessa Morris — hey dudes it’s totally cool, tomorrow I’m bringing a California Worker’s Rights book to work. My mom works for a law firm that specializes in labor law and BOY will you be surprised by all the crap that’s going on that’s in violation 8) see you tomorrow!

Can you fire these three employees? If you answered yes, you just bought yourself an unfair labor practice charge with the National Labor Relations Board, at least according to Bettie Page Clothing (4/19/13) [pdf]. Per the NLRB:

The Facebook postings were complaints among employees about the conduct of their supervisor as it related to their terms and conditions of employment and about management’s refusal to address the employees’ concerns. The employees also discussed looking at a book about the rights of workers in California so that they could determine whether the Respondent was violating labor laws. Such conversations for mutual aid and protection are classic concerted protected activity.

Social media is today’s water cooler. Employees still might gather around the lunch table or coffee machine to gossip about work, but they are also just as likely, if not more likely, to carry over those conversations outside of the workplace through their personal social media accounts. If you wouldn’t fire an employee for a water-cooler conversation you happen to overhear, then don’t fire them for a similar conversation on a Facebook wall. In fact, you are much worse off with the social-media-based termination because the employee has a digital paper trail with which to hang you.

Employees gossip with and gripe to each other. Instead of firing these employees, maybe you need to look inward to figure out if their concerns are legitimate, and if there is something you can do about it.

[Hat tip: Employer Law Report]

Fired for suing an ex-employer? Court rejects public policy claim

Carcorp hired Barry Elam to work in its finance department. A few months into his employment with Carcorp, Elam sued his prior employer, Bob McDorman Chevrolet, claiming that it had wrongfully fired him in retaliation for his cooperating with an investigation by the Ohio Attorney General into fraudulent credit applications. A year later, Carcorp fired Elam.

Elam then sued Carcorp, claiming that it wrongfully fired him in retaliation for his lawsuit against his prior employer, in violation of Ohio’s public policy.

In Elam v. Carcorp, Inc. (4/23/13), the appellate court affirmed the trial court’s dismissal of Elam’s wrongful discharge claim.

For the uninitiated, some background on wrongful discharge in violation of public policy claims under Ohio law. These claims act as an exception to the presumption of at-will employment permitting a claim when an employee is discharged or disciplined for reasons that contravene a clear public policy. To establish a claim that an employer wrongfully discharged an employee in violation of public policy, the employee must demonstrate all of the following:

1. A clear public policy existed and was manifested in a state or federal constitution, statute or administrative regulation, or in the common law.
2. Dismissing employees under circumstances like those involved in the plaintiff’s dismissal would jeopardize the public policy.
3. Conduct related to the public policy motivated the plaintiff’s dismissal.
4. The employer lacked overriding legitimate business justification for the dismissal.

After an extensive analysis of Elam’s claimed public policy—the Open Courts provision in the Ohio Constitution—the appellate court rejected Elam’s public policy claim, on the basis that “Elam did not articulate any clear public policy that his termination from employment violated.”

In the final analysis, Elam did not demonstrate the Open Courts provision represents a clear expression of legislative policy barring an employer from discharging an employee as a result of the employee’s lawsuit against a third party. To hold otherwise would expand the public policy inherent in the Open Courts provision beyond the provision's clear meaning and infringe upon the legislature's duty to make and articulate public policy determinations.

While academically interesting, this case raises a more interesting practical consideration. These “public policy” retaliation cases often hinge on the creativity of plaintiff’s counsel to find a legislative or constitutional hook on which to hang the alleged public policy, and the court’s willingness to approve of the creativity. Indeed, the more creative the public policy, the more unpredictable the outcome of potential litigation. For this reason, employers should treat all employees complaining about anything in the workplace as ticking time bombs, as if their complaints are protected by some law or another. If a court later rejects a public policy claim, all the better.

WIRTW #274 (the “Dunder Mifflin” edition)

Last night brought us the final episode of what may be the greatest ever satire of the American workplace—The Office. Seinfeld, that is how you do a series finale.

In its honor, I bring you one of my favorite clips from my favorite episodes from show’s nine-year run, Diversity Day. If this doesn’t make your employment law skin crawl, nothing will:

 

Here are 59 other reasons we’re going to miss The Office.

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

Discrimination

• Want to cut the line at the Disney park? Call my disabled friend — from Walter Olson’s Overlawyered
• “Bashful Bladder” As A Disability? Running Water The Accommodation? — from Employment Discrimination Report
• Horniest boss ever? His employee still can’t prove sexual harassment — from The Employer Handbook Blog
• Angelina Jolie and Employment Law — from Phil Miles’s Lawffice Space
• Bad Credit Could Cost You a Job — from Nolo’s Employment Law Blog
• EEOC Brings, Settles First Ever GINA Lawsuit — from Employer’s Law Blog 
• “My Prior Complaint Was One of the Reasons for the Adverse Employment Action”: Mixed Motive Theories for Retaliation Claims Under Title VII — from HR Defense Blog

Social Media & Workplace Technology

• Social Media By the Numbers — from Social Media Strategies Summit Blog
• How Can You Avoid Lawsuits While Using Social Media to Screen Applicants? 10 Steps to Consider — from The Emplawyerologist
• Social media and nonsolicitation agreements — from Technology for HR

HR & Employee Relations

• Asking to telework when you have your period — from Ask a Manager
• Should these employees have been terminated? Tell us what you think! — from Robin Shea’s Employment & Labor Insider
• Try Acting More Like a Kindergartner — from Evil HR Lady writing at Inc.com
• Dear Evil Skippy: Can I Refuse To Hire Someone With Tattoos? — from Evil Skippy at Work
• Hipster Bias > Another HR Hurdle? — from Fistful of Talent
• Fired For Voicing My Concerns — from Work Place Coach Blog News
• Using Standard Form Employee Handbooks; Damned if You Do, Damned if You Don’t — from damnedif
• Here’s Why Bullies Are Taking Over Your Organization — from TLNT

Wage & Hour

• To Be Or Not To Be An Independent Contractor — from San Antonio Employment Law Blog
• Congressional Roundup: Republican Comp Time Bill Gets a Vote — from Bloomberg BNA
• “They Owe You” Does Not Always Mean You Can Withhold — from Trade Secret / Noncompete Blog
• FLSA Compliance: Dispelling the Great Myths — from HR Daily Advisor
• Employers Play Whack-A-Mole with Internship Lawsuits — from The Wage and Hour Litigation Blog
• Is Time Spent Traveling to Trainings Outside of Normal Working Time — from Smart HR Manager

Labor Relations

• “The N.L.R.B.’s Contested Poster” — from How Appealing
• Senate Republicans Call for Hearing on NLRB's Budget Request — from Wisconsin Employment & Labor Law Blog

Patriots cutting of diabetic player raises serious ADA issues

The New England Patriots recently cut defensive tackle Kyle Love. This news is not worthy of consideration on an employment law blog until I tell you the reason the Pats cut him. According to FoxNews, the Pats cut him two weeks after his diagnosis with Type 2 diabetes out of a concern over his “recovery time.”

If I’m Kyle Love’s agent, I’m finding him the best employment lawyer possible to argue that the Patriots cut him because of his diabetes, a protected disability.

Yesterday, the EEOC conveniently published guidance on the employment rights of people with specific disabilities. One of the specific disabilities for which the EEOC published new guidance is diabetes.

According to the EEOC, there is little doubt that diabetes is a disability protected and covered by the ADA:

As a result of changes made by the ADAAA, individuals who have diabetes should easily be found to have a disability within the meaning of the first part of the ADA’s definition of disability because they are substantially limited in the major life activity of endocrine function. Additionally, because the determination of whether an impairment is a disability is made without regard to the ameliorative effects of mitigating measures, diabetes is a disability even if insulin, medication, or diet controls a person’s blood glucose levels. An individual with a past history of diabetes (for example, gestational diabetes) also has a disability within the meaning of the ADA. Finally, an individual is covered under the third (“regarded as”) prong of the definition of disability if an employer takes a prohibited action (for example, refuses to hire or terminates the individual) because of diabetes or because the employer believes the individual has diabetes.

Given the timing of the Patriots’s decision, coupled both with its apparent failure to offer any kind of accommodation for Kyle Love’s disability, and the stated reason for its decision, Kyle Love appears to have a strong disability discrimination case. Had the Patriots called me, I would have counseled against cutting him, at least at this time and in this manner.

Consider Kyle Love’s problem in light of this hypothetical, provided by the EEOC in its diabetes guidance:

When an actor forgets his lines and stumbles during several recent play rehearsals, he explains that the fluctuating rehearsal times are interfering with when he eats and takes his insulin. Because there is no reason to believe that the actor poses a direct threat, the director cannot terminate the actor or replace him with an understudy; rather, the director should consider whether rehearsals can be held at a set time and/or whether the actor can take a break when needed to eat, monitor his glucose, or administer his insulin.

It is an understatement to characterize this termination—undertaken without any apparent consideration of whether the team could accommodate the diabetes—as high risk.

Jeffrey Nye made me aware of this story on Twitter last night, and asked, “The Patriots cut Kyle Love because he has diabetes. How can they do that?”

They can’t (or at least shouldn’t be able to in the manner in which they did it). It would not surprise me in the least if, given the high profile nature of this employment decision, the EEOC takes up Kyle Love’s cause to further its mission of disability-rights awareness.

Employee vs. independent contractor: do you know the difference

Employers take a risk when they classify someone performing services for them as an independent contractor instead of an employee. Because employers owe contractors far fewer obligations than employees, employers risk each of the following if a court determines that a mis-classification occurred:

• Unpaid overtime.
• Unpaid taxes.
• Un-provided benefits.
• A discrimination claim, or claims under other laws that protect employees but not contractors (i.e., the FMLA).

Do you know, however, how to spot the difference? Troyer v. T.John.E. Productions, Inc. [pdf], decided yesterday by the 6th Circuit, provides some insight.

The issue in the case was whether the company failed to pay overtime to three individuals who performed road crew services (setting up and breaking down displays) at the company’s collegiate and corporate events. The court determined that the company had mis-classified them, and owed them unpaid overtime as employees:

Plaintiffs testified that their working relationship with Defendants was relatively permanent, they worked hundreds of hours of uncompensated overtime over several months, and that Defendants exercised strict control over their schedule and day-to-day activities while out on the road. Defendants countered that Plaintiffs worked on a job-by-job, independent contractor basis, that the Plaintiffs had a great amount of autonomy regarding how they completed their work.

In determining whether an worker is an employee or an independent contractor, the IRS looks compares the degree of control exerted by the company to the degree of independence retained by the individual. Generally, the IRS examines this relationship in three ways:

1. Behavioral: Does the company control or have the right to control what the worker does and how the worker does his or her job?
2. Financial: Are the business aspects of the worker’s job controlled by the payer? (these include things like how worker is paid, whether expenses are reimbursed, who provides tools/supplies, etc.)
3. Type of Relationship: Are there written contracts or employee type benefits (i.e. pension plan, insurance, vacation pay, etc.)? Will the relationship continue and is the work performed a key aspect of the business?

If you are considering classifying someone performing services for you as an independent contractor, your answers to these three questions will determine whether that individual is a bona fide contractor, or instead, is a employee. When in doubt, err on the side of caution. The government applies these tests aggressively to find employee-status whenever it can. You should too, and the risks are too high to make a mistake.

How much does it cost to defend an employment lawsuit?

Last Friday I had the pleasure of appearing on Huffington Post Live, in a segment entitled, “You’re Fired! No really.” We discussed the current state of employment at-will, and whether American workers need greater protections from being terminated without just cause.If you’ve read my blog for any length of time, you know what I have some pretty strong feelings on this topic. Heck, I’ve even written an entire book on this issue of employer rights.

If you missed the show, you can watch it here, or in the imbedded video below:

Following my appearance, Texas plaintiff-side employment lawyer Chris McKinney tweeted that he was surprised at my statement that it could cost a company $250,000 to defend an employment lawsuit:

Chris was responding to my comment that the myriad laws that already protect employees from arbitrary or capricious terminations (Title VII, ADA, ADEA, FMLA, etc.), coupled with the threat of defending an expensive lawsuit, serve as enough of a deterrent to most reasonable employers from firing an employee without a good reason.

The reality is that defending a discrimination or other employment lawsuit is expensive. Defending a case through discovery and a ruling on a motion for summary judgment can cost an employer between $75,000 and $125,000. If an employer loses summary judgment (which, much more often than not, is the case), the employer can expect to spend a total of $175,000 to $250,000 to take a case to a jury verdict at trial.

Most employers, if acting rationally, will chose to retain an employee instead of assuming the risk of a $250,000 legal bill with an uncertain outcome. Moreover, employers cannot avoid this risk simply by settling every claim that is filed, lest the company risk the perception of being an easy mark by every ex-employee.

If you must terminate an employee, however, the safest, most prudent course of action is to offer a severance package—but only in exchange for a waiver and release of claims, and covenant not to sue—for all terminated employees except those terminated for some egregious or intentional misconduct. By offering severance in exchange for a release, you are capping your exposure and buying off the risk of a costly, time consuming, and burdensome lawsuit.

Cruise-ing for a lawsuit: EEOC sues company for forced practice of Scientology

The EEOC has filed against a Miami, Florida, medical service provider, alleging that it has violated Title VII’s religious discrimination provisions by forcing its employees to practice Scientology. According to the agency’s lawsuit, Dynamic Medical Services required its employees, as a condition of their employment, to spend at least half their work days attending Scientology courses.

The EEOC’s complaint [pdf] details the bizarre job requirements, which included:

• Screaming at ashtrays.
• Staring at someone for eight hours without moving.
• Undergoing a “purification audit” by connecting to a Scientology religious artifact known as an “E-meter.”

Employees who refused to participate in the Scientology religious practices, or conform to Scientology religious beliefs, were terminated.

If any of the EEOC’s allegations in the lawsuit are true, the agency is going to have an easy time winning this case, which serves a good reminder that an employer cannot force its employees to conform to, follow, or practice, the employer’s chosen religious practices and beliefs.

Hat tip: Lowering the Bar

photo credit: Rob Sheridan via photopin cc

WIRTW #273 (the “NLRB, fuggetaboutit” edition)

Remember those posters explaining employees’ rights under the National Labor Relations Act that the NLRB wanted all employers (union and non-union) to post. Well, earlier this week, the D.C. Circuit Court of Appeals issued a broad ruling striking down the NLRB’s posting requiring as a violation both of the NLRA’s “free speech” provision and the 1st Amendment of the Constitution. Bravo D.C. Circuit. Here’s some of the commentary on this case from around the blawgosphere:

• Another Bad Day in the DC Circuit for the NLRB — from Jottings By An Employer's Lawyer
• Breaking: No NLRB Union Posters, Says Appeals Court — from Dan Schwartz’s Connecticut Employment Law Blog
• D.C. Circuit Strikes Down NLRB Notice Rule — from Workplace Prof Blog
• DC Circuit Strikes Down NLRB Poster Requirement — from Phil Miles’s Lawffice Space

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

Discrimination

• EEOC Announces Enforcement Priorities — from Maryland Employment Law Developments
• Is your company a target of the EEOC? — from Employment and Labor Insider
• Sexual Harassment Complaints By Males On The Rise: 2012 EEOC Enforcement and Litigation Statistics — from Outten & Golden Employment Law Blog
• Knock knock. Who’s there? The EEOC… — from Warren & Associates Blog
• 10 Reasons To Negotiate Instead Of Suing The Bastards  — from Negotiation Law Blog
• Should Employees Sign A Waiver To Protect Employers: “I Agree Not To Engage In Wild Sex On A Business Trip?” — from Employment Discrimination Report
• When an Employee Says: I’m Gay — from HR Examiner with John Sumser
• Sexual Orientation – Is Conduct Discrimination or Stereotyping? — from HR Gazette
• Pregnancy Disability Discrimination a KEY Target of EEOC — from Mike Haberman’s Omega HR Solutions

Social Media & Workplace Technology

• Rewriting the Employee Handbook for Social Media — from InhouseBlog
• Protecting Privacy or Enabling Fraud? Employee Social Media Password Protection Laws May Clash with FINRA Rules — from Privacy Law Blog
• Should Employers Ask Candidates for Their Facebook Passwords? — from employeescreenIQ Blog
• History of Terminations & Firings Because of Employee Social Media — from Blogging4Jobs
• Patchwork of Social Media Password Protections Laws Impacts Employers — from Digital Workplace Blog

HR & Employee Relations

• Employee Handbook Haiku — from Minnesota Employer
• Doctor Non-Solicitation Agreement Not Supported By Legitimate Business Interest — from Trade Secrets and Noncompete Blog
• Bullying in the Workplace: All Eyes on NBC — from Minnesota Labor & Employment Law Blog
• Beyond Words: How Generation Y is Redefining Learning For Everyone — from TLNT
• Is Your Company’s Customer List Still A Trade Secret If Your Company Uses Labeled Delivery Trucks? — from Trading Secrets
• Shocking examples of sexism in 1960s corporate newsletters — from Ragan.com
• Why You Shouldn’t Try to Match Yahoo’s Fabulous New Maternity Leave Policy — from Evil HR Lady, Suzanne Lucas
• The don of donut discipline — from PassiveAggressiveNotes.com
• Paid Sick Leave Has Some Business Owners Feeling Ill — from You’re the Boss Blog

Wage & Hour

• Wage Hour Lawsuits Continue to Skyrocket — from The Wage and Hour Litigation Blog
• California Federal Court Relies on Comcast to Deny Class Certification of Off-The-Clock and Meal Period Claims — from Wage & Hour Counsel
• DOL Audits Will Rise With New Funding Increases — from Wage & Hour - Development & Highlights

Labor Relations

• Fact or Fiction: It’s ok to fire an employee for pro-union Facebook posts to NON-employees — from Eric Meyer’s The Employer Handbook Blog
• The Union Is Knocking at My Door: What Can I Say? — from Labor & Employment Law Perspectives
• NLRB Continues to Get in Your Facebook — from Trade Secret / Noncompete Blog
• Being Tricked into Firing an Employee is Not a Defense – More From the NLRB on Facebook Firings — from netWORKed Lawyers
• NLRB Administrative Law Judge Finds Medical Center’s Technology Usage Policies Violated Employees Rights Under the National Labor Relations Act — from Management Memo

Debunking myths of a pro-business Supreme Court

Conventional wisdom says that the current iteration of the United States Supreme Court is pro-business. In support of this position, Adam Liptak penned an article in Sunday’s New York Times, arguing that the Court led by Chief Justice John Roberts is the most business-friendly since World War II. A recent study published in the Minnesota Law Review [pdf] by Judge Richard Posner of the 7th Circuit Court of Appeals, University of Chicago economist William Landes, and University of Southern California law professor Lee Epstein (h/t ABA Journal) makes the same argument, albeit in painstaking law-review detail.

In employment cases, however, the realities of the court’s rulings have often bucked this conventional wisdom. Repeatedly, this Court had sided with the employee in cases deciding substantive individual rights under the various federal anti-discrimination statutes:

• Crawford v. Metropolitan Gov’t of Nashville — Retaliation for participating in internal discrimination or harassment investigations
• Staub v. Proctor Hospital — The cat’s paw: holding employers liable for the discriminatory animus of non-decision-makers
• Kasten v. Saint-Gobain Performance Plastics Corp. — Protecting oral wage and hour complaints under the FLSA’s anti-retaliation provision
• Thompson v. North American Stainless — Protecting oral wage and hour complaints under the FLSA’s anti-retaliation provision
• Hosanna-Tabor Evangelical Lutheran Church and School — Allowing non-ministerial employees to sue religious organizations for discrimination

Mr. Liptak recognizes, “Employees suing over retaliation for raising discrimination claims have fared quite well, for example.” Yet, much of the rest of his nearly 3,000-word opus takes the Court to task for its pro-business leanings.

The most insightful comment in the entire Times article is courtesy of Case Western Reserve School of Law Professor Jonathan Adler, who notes that the distinction is not one between business and the individual, but instead between enforcing established rights versus creating new ones. Per Professor Adler, the Roberts Court has not been “particularly welcoming to efforts by plaintiffs’ lawyers to open new avenues of litigation, but it has not done much to cut back on those avenues already established by prior cases.”

Professor Adler is correct. Those who take too great of a license to brand this Court as pro-business are ignoring the Court’s protections of key individual liberties in employment decisions. In procedural matters, this Court has, time and again, sided with the employer (Genesis Healthcare: offers of judgment mooting wage and hour collective actions; Comcast v. Behrend: the scope of class actions for claims seeking individualized damages; AT&T Mobility v. Concepcion: the enforceability of arbitration agreements). These are procedural cases. In cases deciding the application of already established rights, such as the right to be free from retaliation by one’s employer, the Court, over and over, sides with the employee.

There are still two key employment cases pending this term—Vance v. Ball St. Univ., which will decide the meaning of “supervisor” under Title VII, and University of Texas Southwestern Medical Center v. Nassar, which will decide the proper causation standard for retaliation claims under Title VII. These two rulings will help determine this Court’s developing legacy as either pro-individual or pro-business in deciding employment cases.

You’d think we’d all know the dangers of “reply all” by now

Is there any more helpless feeling in today’s business world than sending an email, and then immediately realizing that you made a mistake? The biggest cause of an emailer’s stomach sinking through the floor—”reply all.” We’ve all had it happen. This story from the Toronto Star explains how a reply-all mistake brought one company an expensive wrongful discharge lawsuit:

Maria Fernandes … accidentally received an email discussing whether or not she should be fired.

Court documents allege that Linda Guerin, the company’s Director of Operations intended to send the email to the company’s lawyers. Too late she realized Fernandes was also on the list and she unsuccessfully sent three recall notices. She also sent an email to Fernandes asking that she delete the message without opening it.

Fernandes read it, treated the information in the email as a constructive dismissal and hired a lawyer. She had worked for the company for over six years and was earning $145,000 a year.

This case is a great reminder that a mis-addressed email can cost employers dearly in a wrongful discharge lawsuit. Other reply-all risks include the disclosure of trade secrets and other confidential information.

How do you protect against this problem affecting your business? The Toronto Sun article discusses some add-ons for Outlook that will either remove the “reply all” button or require an extra confirming step to use it.

Technology, however, will only mask the symptoms. It will not cure your workplace of this problem. To really attack the problem, you need to educate and train your employees.

• Do you train your employees on proper email etiquette, including when to use (and, more importantly, not use) “reply all?”
• Do you teach your employees to proofread entire emails carefully before they click “send,” including double-checking the “to,” “cc” and “bcc” boxes?

Taking issue with the term “wage theft”

Lately, I’ve read a lot of blogs that accuse employers of committing rampant wage theft (e.g., here, here, and here).

I have a huge problem with the term “wage theft.” It suggests an intentional taking of wages by an employer. Are there employees are who paid less than the wage to which the law entitles them? Absolutely. Is this underpayment the result of some greedy robber baron twirling his handlebar mustache with one hand while lining his pockets with the sweat, tears, and dollars of his worker with the other? Absolutely not.

Yes, we have a wage-and-hour problem in this country. Wage-and-hour non-compliance, however, is a sin of omission, not a sin of commission. Employer aren’t intentionally stealing; they just don’t know any better.

And who can blame them? The law that governs the payment of minimum wage and overtime in the country, the Fair Labor Standards Act, is 70 years old. It shows every bit of its age. Over time it’s been amended again and again, with regulation upon regulation piled on. What we are left with is an anachronistic maze of rules and regulations in which one would need a Ph.D. in FLSA (if such a thing existed) just to make sense of it all. Since most employers are experts in running their businesses, but not necessarily experts in the ins and outs of the intricacies of the Fair Labor Standards Act, they are fighting a compliance battle they cannot hope to win.

As a result, sometimes employees are underpaid. The solution, however, is not creating wage theft statutes that punish employers for unintentional wrongs they cannot hope to correct. Instead, legislators should focus their time and resources to finding a modern solution to a twisted, illogical, and outdated piece of legislation.

In my most recent book, The Employer Bill of Rights: A Manager’s Guide to Workplace Law, I summarized this issue best:

Congress enacted the FLSA during the great depression to combat the sweatshops that had taken over our manufacturing sector. In the 70 plus years that have passed, it has evolved via a complex web of regulations and interpretations into an anachronistic maze of rules with which even the best-intentioned employer cannot hope to comply. I would bet any employer in this country a free wage-and-hour audit that i could find an FLSA violation in its pay practices. A regulatory scheme that is impossible to meet does not make sense to keep alive….

I am all in favor of employees receiving a full day’s pay for a full day’s work. What employers and employees need, though, is a streamlined and modernized system to ensure that workers are paid a fair wage.

Big verdicts might grab headlines, but it’s the final judgment that counts

I never thought I’d read about a case in which I could say to myself, “A $240 million jury verdict doesn’t seem all that out of whack.” Then I read about the EEOC’s recent $240 million jury verdict against Henry’s Turkey Service. The agency alleged that the farm subjected its 32 mentally disabled workers to decades of abuse:

The EEOC’s press release describes the horrible working conditions to which the turkey processing plant subjected these individuals:

Specifically, the EEOC presented evidence that for years and years the owners and staffers of Henry’s Turkey subjected the workers to abusive verbal and physical harassment; restricted their freedom of movement; and imposed other harsh terms and conditions of employment such as requiring them to live in deplorable and sub-standard living conditions, and failing to provide adequate medical care when needed.

Verbal abuses included frequently referring to the workers as “retarded,” “dumb ass” and “stupid.” Class members reported acts of physical abuse including hitting, kicking, at least one case of handcuffing, and forcing the disabled workers to carry heavy weights as punishment.  The Henry’s Turkey supervisors, also the workers’ purported caretakers, were often dismissive of complaints of injuries or pain.

Robert A. Canino, regional attorney of the EEOC’s Dallas District Office, which tried the case, … told the jury that Henry’s Turkey treated the men “like property.” … Canino urged the jury to think of the “broken lives of 32 hard-working but vulnerable intellectually disabled men” who were employees of Henry’s Turkey.

For more background on the Henry’s Turkey labor camps that this case helped bring to an end, I recommend this story from the Des Moines Register, which includes a timeline summarizing the camps’ 40-year history. In this context, the $7.5 million awarded to each of the 32 disabled employees ($5.5 million in compensatory damages, on top of another $2 million in punitive damages) begins to look more reasonable.

While the $240 million verdict is historically large (he biggest ever obtained by the EEOC), ultimately it will only serve as a symbol of the cruelty these 32 men endured. As the Des Moines Register articles points out, Henry’s Turkey’s assets cover less than two percent of the total verdict. Additionally, the Civil Rights Act of 1991 caps these non-economic damages, depending on the size of the employer:

• For employers with 15 – 100 employees, damages are capped at $50,000.
• For employers with 101 – 200 employees, damages are capped at $100,000.
• For employers with 201 –  500 employees, damages are capped at $200,000.
• For employers with more than employees, damages are capped at $300,000.

Thus, Henry’s Turkey maximum exposure for non-economic damages is $9.6 million.

Perhaps the lesson that employers should take away from this horrible story is that a verdict is only the first step in a plaintiff attempting to remedy a wrong. A verdict is simply the jury’s unfiltered opinion about what those eight people think the case is worth. That opinion, however, is not the final say; it is still subject to the law. A judge can lower the amount because of damage caps or for some other reason. A judge can take away the entire verdict by entering judgment notwithstanding the verdict for the defendant, or by ordering a new trial. A court of appeals can find some error in the case and reverse the judgment. Moreover, even if some or all of the verdict survives to a final judgment on which a plaintiff can execute, the plaintiff still has to be able to collect. A multi-million judgment against an insolvent defendant is not worth more than the paper on which it is printed.

We put so much effort into, and place so much emphasis on, the jury verdict that we can lose sight that often it is merely the end of the first act of a much longer play. The verdict might grab headlines, but for a defendant, the war is not over until the final judgment is entered.

WIRTW #272 (the “sensual harassment” edition)

We’ve all heard of sexual harassment. But, have you heard of “sensual harassment?”

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

Discrimination

• No, I am not from the Midwest. Sex Discrimination Lives On — from Molly DiBianca’s Delaware Employment Law Blog
• Third Circuit says VIPs cannot sue for Title VII discrimination — from Eric Meyer’s The Employer Handbook Blog
• Initial Discovery Protocols in Discrimination Cases: A Connecticut Update — from Dan Schwartz’s Connecticut Employment Law Blog
• First Circuit Rejects Age Discrimination Claim Based on Isolated Comment — from Employer’s Law Blog
• Sexual Harassment Complaints By Males On The Rise: 2012 EEOC Enforcement and Litigation Statistics — from Outten & Golden Employment Law Blog
• Ostracism and petty mistreatments may collectively rise to the level of hostile work environment — from Employment Law Matters
• Bills Would Extend Workplace Protections to LGBT Employees — from Washington D.C. Employment Law Update
• What It Takes To Win An Age Discrimination Suit — from Forbes

Social Media & Workplace Technology

• New Jersey Federal Court Issues Sanctions For Deletion of Facebook Profile — from Trading Secrets
• FireMe! App rescues tweeting employees from own indiscretions? — from Employment Law Worldview
• Time for those six second “selfies” with latest Vine update — from TiPb
• Twitter: A Sleeping Discovery Giant? — from Law.com
• The Mayo Clinic and Healthcare Social Media — from SocialFish
• The “Employee Tricked Me Into Firing Her” Defense — from Social Media Employment Law Blog
• NLRB Issues Facebook Firing Decision — from Phil Miles’s Lawffice Space
• “Catfishing” Gets Its First Legal Mention — from The Not-So Private Parts
• If a Tweet falls in the forest — from iFractal

HR & Employee Relations

• Workplace Violence, Part 2: Crisis management tips for employers — from Robin Shea’s Employment & Labor Insider
• When Uncle Sam calls your employees, what do you do – and not do? — from HR Cafe
• Alcohol Testing in the Workplace: An Employer’s Dilemma — from i-Sight Investigation Software Blog
• An Observation on Work-Life Balance — from Blogging4Jobs
• Paid Sick Leave Has Some Business Owners Feeling Ill — from You’re the Boss Blog
• The don of donut discipline — from PassiveAggressiveNotes.com

Wage & Hour

• DOL Audits Will Rise With New Funding Increases — from Wage & Hour - Development & Highlights
• Eighth Circuit Holds Plaintiffs Must Provide Evidence of Actual Damages Even when Employer Doesn't Keep Accurate Time Records — from Wage & Hour Counsel
• “Comp Time” Proposal: Be Careful What You Wish For — from Wage and Hour Laws Blog
• The Unpaid Internship Dilemma: Everyone Loses in This Crackdown — from TLNT

There’s no such thing as a free lunch

Your accounting records might soon look a little different—that is, if you provide perks at work such as free meals and if the IRS gets its way.

According to the Internal Revenue Code, certain employer-provided meals are exempt from the definition of “gross income” and, therefore, not taxed. To be considered non-taxed, an employer must provide a meal on its premises and for its convenience. Examples that might qualify:

• Employees working at remote sites (e.g., oil rigs).
• Emergency workers who have to be on-call.
• Employees whose peak work coincides with the lunch hour (e.g., bank tellers).

Silicon Valley’s tech companies are famous for the perks they offer to lure the best and brightest employees. One such perk—elaborately gourmet free meals (how does Facebook’s spicy she-crab soup and grilled steak with chimichurri sauce sound?). Never one to leave money on the table, the IRS is reportedly examining the taxability of these meals.

From the Huffington Post:

The free meals that tech companies like Facebook, Google, and Yahoo provide their employees should actually be taxed. But what does that really mean? Who should be paying for these meals and where is the line drawn? According to Martin J. McMahon, Jr., professor of tax law at the University of Florida, companies like Facebook and Google report these meals as tax-free fringe benefits, when they should be considered taxable fringe benefits. The cost of these meals, McMahon explains, should be considered a part of the employee’s salary. “Let’s say that an employee gets $2,000 in free meals and makes $50,000 a year. The company should report to the IRS that it paid the employee $52,000 in compensation on which the employee would be taxed,” McMahon says….As Professor McMahon explained … : “A company cannot provide tax-free meals if workers commute from home and have the ability to bring their lunches with them.”

I’m not a tax attorney. I don’t want to be a tax attorney. This might be the only tax-based post I will ever write. Here’s what to take away from this story. If you provide free food to your employees, however, you might soon need to start accounting for that food as a taxable benefit instead of tax-free benefit.

This post originally appeared on The Legal Workplace Blog.

[photo credit: Rich Anderson via photopincc]

Can we please fix Ohio’s age discrimination law?

It’s no secret that Ohio’s age discrimination statute is a hot mess. The statute has four different ways a plaintiff can file an age claim against an employer, each with a different statute of limitations and available remedies. What’s more, the statute requires that the plaintiff elect which one of the four specific statutory provisions the claim is asserted. Filing under one provision precludes a plaintiff from asserting a claim under any of the other three. This election can have a significant impact on the litigation, because it will dictate the remedies a plaintiff can seek.

If this scheme not complicated enough, federal law also requires that a plaintiff file an age discrimination charge with the EEOC as a prerequisite to filing a lawsuit alleging a violation of the ADEA. Because Ohio is a deferral state, any charges filed with the EEOC are automatically deemed dual-filed with the OCRC.

Not all Ohio state-law age discrimination claims, however, require exhaustion with the civil rights agency. In fact, R.C. 4112.99, which provides the most expansive remedies, has no exhaustion requirement at all. What happens, however, if a plaintiff files an age discrimination charge with the EEOC? Does that mean that the dual filing with the OCRC asks an election by the plaintiff to pursue an administrative claim (with limited remedies) instead of a civil lawsuit with more expansive remedies?

In Flint v. Mercy Health Partners of Southwest Ohio (S.D. Ohio 4/16/13), the district court concluded that filing first with the EEOC does not serve as an election of administrative remedies under Ohio’s age discrimination statutes:

This Court concludes that the Ohio Supreme Court would likely rule that filing a charge of age discrimination with the EEOC does not comprise an election of remedies…. Therefore, the Court holds that Plaintiffs’ pro se filing of an EEOC charge was not an election of remedies under the Ohio statute. This result acknowledges the complementary nature of federal and state employment discrimination procedures and disarms the “minefield” Ohio’s statutory scheme creates for the litigant wanting to pursue a remedy for age discrimination — something this Court finds particularly important when an employee is attempting to navigate that minefield without the assistance of legal counsel.

Ohio is contemplating expansive changes to its employment discrimination laws. The legislature should take the opportunity to disarm this "minefield" by creating one unified statute of limitations for all discrimination claims (I suggest one year to bring Ohio more in line with its federal counterpart), and eliminate the goofy and confusing election requirement that results from having four different types of age discrimination claims.

The legal and ethical issues of the class action “pick off”

Have you heard that the new owner of the Cleveland Browns has gotten himself into a bit of legal trouble? It’s alleged that Jimmy Haslem’s other business, Pilot Flying J, defrauded trucking companies of fuel rebates. In an effort to head-off a stream of civil lawsuits, Mr. Haslam has been meeting with customers to settle the alleged missing rebates. One such customer sought a temporary restraining order to stop such meetings because, according to the Wall Street Journal, Pilot was “obtaining releases, and settling claims before the potential class members even know the full extent of their claims.” Yesterday, the court denied the restraining order, permitting Haslem’s company to continue attempting to settle these claims.

Recall that just two weeks ago, the Supreme Court decided a case involving the pick-off named plaintiffs in wage and hour collective actions. In the Genesis Healthcare case, however, the employer communicated the offer to the plaintiff through her attorney. What happens, however, if the employer communicates directly with un-represented and un-named members of a yet-to-be-certified class? Is there anything prohibiting an employer from contacting them directly in an effort to obtain settlements of their potential claims? It depends.

There is nothing inherently unethical in defense counsel contacting putative class members at the pre-certification stage. According to ABA Comm. on Ethics and Prof’l Responsibility, Formal Op. 07-445 (2007) [pdf], communications between defense counsel and putative class members does not violate the Models Rules of Professional Responsibility because there is no attorney-client relationship between plaintiffs’ counsel and members of an un-certified, putative class.

Yet, a court still might limit such communications if they are designed to confuse or coerce.

In Gulf Oil v. Bernard (1981), the U.S. Supreme Court rejected the argument that defense counsel are per se prohibited from contacting putative class members before a class is certified. Instead, a court can only limit pre-certification communications to address communications that misrepresent the status or effect of the case or that have an obvious potential for confusion, and must be based on “a specific record showing by the moving party of the particular abuses by which it is threatened.”

In accordance with the Supreme Court’s Bernard decision, federal district courts have routinely refused to exercise their supervisory authority over communications with putative class members in situations where the complaining party cannot demonstrate actual abuses. Such abuses that would justify a gag order include communications that coerce putative members into excluding themselves from the class, undermine cooperation with or confidence in plaintiffs’ counsel, or suggest retaliation for participating in or assisting the class.

For example, in Parks v. Eastwood Ins. Servs. (C.D. Cal. 2002), the named plaintiffs brought a collective action against their employer for unpaid overtime under the Fair Labor Standard Act. Prior to sending a court-approved notice to putative class members, the employer sent a memorandum to its employees asking them to contact the company’s general counsel if they had any questions regarding the case. The court concluded that a curative communication was unnecessary because the at-issue memorandum was not coercive and did not suggest that any employee would be retaliated against for joining the class.

There are significant strategic decision that companies and their attorneys must make when defending class action lawsuits. Pre-certification communications with potential class members carries a big upside, albeit with the potential of significant risk.

With social media, all of your employees are brand ambassadors; train them accordingly

A Hockessin, Delaware, restaurant has gotten itself into a bit of hot water after it was discovered that its employees posted offensive photographs to the restaurant’s Facebook and Instagram pages. The photos were of receipts of bad-tipping customers, and included offensive and racist comments, including “'#deuchbag”, “#cheapass”, “#hillbillies”, “#cheap #jerk #indian”, and “#cheap #jew”.

While the accounts have been disabled, Daily Mail posted some of the screen-caps.

Whether you like it or not, social media has turned each of your employees into a brand ambassador. Can you afford to have your brand sullied by the offensive or racists rants of one of your employees? More importantly, how do you undo the damage caused? While an offending employee should be fired for the transgression, the firing won’t remove the stain left on your business. In this case, the owner posted a public apology to his customers, but that apology will not undo all of the viral damage done by a rogue employee. Additionally, the power to delete the post cannot stop others from publicizing the screencap of death. For example, this restaurant deleted the posts, but they live on in the Daily Mail story and in this post.

What is the answer?

1. Training, training, training. Employees need to understand that they will be held accountable with their jobs if they write something online that damages the reputation of your brand. Do not entrust this issue solely to your employees’ common sense. They will disappoint you.

2. Monitor your brand online. You do not want to find out about something like this for the first time with a reporter asking you for a comments. There are myriad tools available online to monitor your brand’s social presence. They are well worth the investment, especially when compared to the potential harm one disgruntled or renegade employee can cause. Google alerts are free, and are a great starting point. They will not, however, catch much of the social chatter. Two popular paid solutions (which I am not endorsing, but merely informing) are Radian6 and Wildfire.

3. Secure your IT and social media accounts. According to the owner of this restaurant, the accounts were hacked because he “left [his] iPad and stuff all around.” You need to secure your technology to ensure that employees cannot appropriate social media channel to which they should not have access.

If you want to see an example of one large scale organization trains its employees on the appropriate and responsible use of social media, specifically to address the risk of viral damage from negative or irresponsible posts, take a look at the training video Zurich Insurance has made available on YouTube:

YouTube also has available similar examples from Citrix, Sodexo, and KPMG. As with any policy or training your are considering implementing, check first with your own legal counsel.

WIRTW #271 (the “too hot to work” edition)

Do you remember the dental hygienist whom the Iowa Supreme Court declared too hot to work? Earlier this week, she attempted to “redeem” herself by appearing on a recent episode of Comedy Central’s Tosh.0 [h/t Above the Law] (NSFW):

Tosh.0

I’m happy to see that Ms. Nelson doesn’t perceive herself as a piece of meat to be inappropriately ogled by men. After Ms. Nelson lost her sex discrimination case I had sympathy for her because I thought the Iowa court made bad law. I still believe Nelson’s case is bad law; my sympathy for her, however, has gone down the drain.

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

Discrimination

• Senator Murphy: Prospects “Not Too Good” for Federal Bill Prohibiting Sexual Orientation Discrimination — from Dan Schwartz’s Connecticut Employment Law Blog
• Senate must act on gay workplace rights — from The Washington Post
• Hooter’s Waitress Alleges That Brain Surgery Resulted In Her Losing To Losing Her Job — from Workplace Prof Blog
• What Does GINA Have to Do With Employment Practices? — from The Emplawyerologist
• EEOC Checkup: Where Things Stand — from employeescreenIQ Blog
• What The Interactive Process Requires — from California Employment Law
• A Workplace Harassment Case for the Record Books — from i-Sight Investigation Software Blog
• Teach Employees about Sexual Harassment — from Mike Haberman’s Omega HR Solutions

Social Media & Workplace Technology

• Monitoring employees’ use of company trademarks in social media — from Technology for HR
• If worker social media accounts are private, how can financial firms check for trading issues? — from ABA Journal Daily News
• Breaking Bad? NM is the 6th state to pass social media workplace law — from Eric Meyer’s The Employer Handbook Blog
• Federal Court Allows Service On Foreign Defendants Through Facebook — from Trading Secrets
• The top 5 trends in mobile and BYOD security — from Consumerization Blog

HR & Employee Relations

• California Court Tosses Idea Theft Suit Over LOST Television Show Out to Sea — from Trading Secrets
• From bullying, to mobbing, to ouster: The story of Ann Curry — from Minding the Workplace
• Being Proactive May Reduce Risk for Corporate Raiding and Loss of Sensitive Company Information — from netWORKed Lawyers
• Workplace Violence: Some things an employer can do — from Robin Shea’s Employment & Labor Insider
• Lessons from Boston: Employers confront terrorism — from Michigan Employment Law Connection
• How Elevators Reveal Office Pecking Order — from Fast Company

Wage & Hour

• Department of Labor to Increase Frequency of FMLA On-Site Investigations — from Jeff Nowak’s FMLA Insights
• Can Employers Limit FMLA Leave for Married Co-Workers? — from Hiring & Firing
• Employing teens – is it ok not to pay them for “training time”? — from Warren & Associates Blog
• Are Unpaid Interns Handy Helpers or a Source of Liability? — from Labor & Employment Law Perspectives
• Do FLSA Settlements Require Court Approval? — from Phil Miles’s Lawffice Space
• Payment of Wages While on Lock-Down — from CPEhr