Employers often maintain policies prohibiting off-duty employees from accessing their facilities.  The NLRB has maintained its “Tri-County Medical” rule for nearly 40 years:  an employer’s rule barring off-duty employee access to a facility is valid only if it (1) limits access solely to the interior of the facility, (2) is clearly disseminated to all employees, and (3) applies to off-duty access for all purposes, not just for union activity.  In two recent decisions, the Board interpreted the third prong of Tri-County Medical to significantly limit employers’ ability to prohibit off-duty access by employees.

In St. John’s Health Center, 357 NLRB No. 170 (2011), the Board invalidated a hospital’s policy that permitted employees to come onto hospital property “to attend Health center sponsored events, such as retirement parties and baby showers.”  And in Sodexo, 358 NLRB No. 79 (2012), the Board invalidated a hospital’s rule that permitted off-duty employees access for “hospital related business,” which was defined as “the pursuit of the employee’s normal duties or duties as specifically directed by management.”  The 2012 Board majority disallowed this rule because it gave the hospital “free rein to set the terms of off-duty employee access.”  Former Member Hayes dissented in both decisions, stating that, under the majority view, an employer cannot maintain a valid off-duty access policy if it permits activities “as innocuous as allowing employees to pick up paychecks or complete employment-related paperwork.”Continue Reading NLRB Reverses Sodexo Off Duty Access Decision – a Crack in the Door After Noel Canning…Or Not?

pharmacistEmployers like separation agreements.  Separation agreements, of course, are contracts that employees sign when their employment is terminated that allows them to be paid severance and in exchange they usually give up the right to sue their employer.  Separation agreements provide finality to employment terminations by offering employers protection from claims and potential claims.  The agreements many employers use are often standardized and have served them well for years.  But now might be the time to take another look at those documents, lest the Equal Employment Opportunity Commission (“EEOC”) looks first.

Recently, the EEOC has aggressively asserted its (re)interpretation of the law regarding the enforceability of separation (severance) agreements, suing several companies for using what it perceived to be overly broad agreements.  See, EEOC v. CVS Pharmacy, Inc. no. 1:14-cv-00863 (N.D. Ill. 2014); see also, EEOC v. CollegeAmerica Denver, Inc., no. 14-cv-01232-LTB (E.D. Co. 2014).  The EEOC doesn’t like separation agreements that do not make it sufficiently clear (in the EEOC’s opinion) that employees do not waive the right to file charges with the EEOC or participate in agency investigations, even though the employee can waive claims for damages under the statutes the EEOC enforces like Title VII or the Americans with Disabilities Act (“ADA”).  In the CVS Pharmacy and CollegeAmerica cases, the EEOC alleged the employers’ separation agreement forms constituted a “pattern or practice” of denying employees their statutory rights.  (“Pattern or practice” is significant because such cases can carry much higher penalties than a run-of-the-mill lawsuit; they can also inspire class-action lawyers to start snooping around.)Continue Reading EEOC’s Tough Stance on Employee Separation Agreements

Last month, the White House released a comprehensive report on the use of “big data” in the public and private sectors. Employers should pay particular attention to one of its central forecasts: the EEOC and other federal antidiscrimination agencies may begin scrutinizing how employers collect and use big data in managing their workforces.

The concept of “big data” is difficult to define. The report observed that big data generally “reflect[s] the growing technological ability to capture, aggregate, and process an ever-greater volume, velocity, and variety of data.” “Big data” describes the process by which an entity gathers massive amounts of information from social media, the internet, and other (typically electronic) sources. Websites use big data to deliver user-specific advertisements. Medical researchers and healthcare providers use it to develop targeted disease prevention methods. Financial institutions use it to better detect cyber fraud. The CIA even used big data to track down Osama Bin Laden.Continue Reading Does Data Discriminate? Perspectives for Employers on the White House’s Recent “Big Data” Report

Here’s something that should be at the top of your to do list on this Monday morning:  make sure your benefits and other employee policies are in compliance with new guidance from the IRS that becomes effective today relating to federal tax treatment of same-sex marriages under the U.S. Supreme Court’s decision in U.S. v. Windsor.  In Windsor, the Supreme Court struck down provisions of the Defense of Marriage Act (“DOMA”), which had prohibited recognition of same-sex marriages under federal law. That decision has several implications for employers, including application of employee leave laws such as the Family Medical Leave Act (“FMLA”), which we blogged about recently.

Since the Windsor ruling, federal agencies have been busy carrying out President Obama’s directive to update regulations and guidance accordingly.  On August 29, the IRS issued Revenue Ruling 2013-17 and two sets of FAQs (here and here), advising how the IRS will treat same-sex marriages for federal tax purposes. (Windsor was, after all, a tax case, in which the issue was whether the IRS was allowed to disregard a same-sex marriage for federal estate tax purposes).  The guidance becomes effective today, September 16, 2013.

Under that new guidance, the IRS will apply the marriage laws of the state or country in which the marriage was celebrated (‘state of celebration”) to determine if the couple is validly married for federal tax purposes, including tax and other issues relating to employee benefits.  Under the new IRS guidance, any same-sex marriage validly entered into in any state or foreign country that allows same-sex marriage will be recognized by the IRS for income, estate, and other tax purposes, even if the couple does not live or work in a state that recognizes the marriage.  For example, if a same-sex couple is married in Washington (or Canada), which recognizes same-sex marriage, and then moves to Oregon, which currently does not, the couple will still be considered married for federal tax purposes.Continue Reading Employers Should Review Benefits Plans And Other Policies Affecting Employees In Same-Sex Marriages As New IRS Guidance Implementing U.S. Supreme Court’s Windsor Decision Becomes Effective Today, September 16, 2013

As we’ve blogged about before, the EEOC has become more aggressive over the past few years in scrutinizing employer use of criminal background and credit checks.  While federal anti-discrimination laws do not expressly prohibit employers from performing background checks or similar screening methods on employees or applicants, their use can be unlawful where the practice has a “disparate impact” on protected classes of employees under Title VII.  Recently, the EEOC has issued Guidance documents focusing on disparate impact cases involving criminal history and credit checks, all as part of its interest in “systemic” forms of discrimination.  In addition to issuing guidance limiting when and how employers can use criminal and credit history background checks in employment, the EEOC has been actively investigating specific employers, as some readers of this blog are undoubtedly all too aware.  In some cases, the EEOC has even initiated lawsuits challenging employers’ use of background checks.  For example, the EEOC has filed suit just a few weeks ago against Dollar General (EEOC v. Dollar General, No. 1:13-cv-04307, Illinois) and BMW (EEOC v. BMW Manufacturing Co., LLC, No. 7:13-cv-01583-HMH-JDA, South Carolina).

Many employers and employment attorneys who have argued that appropriate use of background checks can be important and necessary believe the EEOC is going too far.  Those employers have complained that the EEOC’s aggressive position presumes the use of criminal or credit background checks is per se unlawful and amounts to a de facto ban on their use under any circumstances, regardless of whether or not they result in an unlawful disparate impact.  If you are one of those raising such concerns, federal judges may be listening.  A few weeks ago, a federal  judge in the U.S. District Court in Maryland issued an opinion granting summary judgment dismissal in another of the EEOC’s enforcement lawsuits, EEOC v. Freeman (No. 1:10-cv-2882, Maryland).  The scathing opinion by U. S. District Court Judge Roger Titus held that the EEOC’s evidence was unreliable and failed to raise a question of fact or show Freeman’s background check policies created a disparate impact in violation of Title VII.Continue Reading Maryland Federal District Court’s Dismissal of EEOC v. Freeman Provides Guidance for Employers on Background Check Rules

The National Labor Relations Board (“NLRB”) continues to closely scrutinize employers’ social media policies and practices. As employers struggle to craft policies that promote productivity while at the same time protect employees’ rights, both unionized and non-unionized employers need to be aware of recent NLRB decisions and their impact on employer policies:

Social-Media Based Termination Can Be Acceptable, But Rule Requiring “Courtesy” Is Not

On September 28, 2012, a three-member panel of the NLRB affirmed the termination of a car salesman who posted photographs on Facebook ridiculing his employer, but it rejected the employer’s rule requiring courteous behavior. (Karl Knauz Motors Inc., 358 N.L.R.B. No. 164, Sept. 28, 2012 [released Oct. 1, 2012]). Knauz marked the first time a panel of the NLRB decided a case involving social media; previously, all NLRB guidance in this area came from ALJ decisions or the Board’s General Counsel Memoranda. In Knauz, a sales employee had complained on his Facebook page about his employer, a BMW car dealership, posting photos and criticizing bad food the dealer offered at a sales event; he had also discussed those concerns with other coworkers. He also posted critical comments and photos about an accident during a test drive at the dealership. The employer terminated the employee for his Facebook postings and for violating the employer’s courtesy policy. That policy stated that “[e]veryone is expected to be courteous, polite and friendly to our customers, vendors and suppliers, as well as to their fellow employees,” and that “[n]o one should be disrespectful or use profanity or any other language which injures the image or reputation of the Dealership.”

The NLRB ultimately declined to decide whether the employee’s complaints about the food were protected activity under the NLRA. The ALJ below had held the food complaints were protected because the employee and his coworkers conceivably were concerned that the low-quality food offered at the sales event would deter customers from coming, thus leading to lower sales commissions for the employees. Instead, the NLRB upheld the employee’s termination, agreeing with the ALJ that the employee’s Facebook postings relating to the on-site accident were not related to any employees’ terms or conditions of employment. 

Continue Reading NLRB Puts Kibosh On Some Employer Social Media Policies

As many of you know, the Equal Employment Opportunity Commission (EEOC) has been on an aggressive tear of late on a broad range of issues.  In addition to upping its investigations of charges of individual “disparate treatment” discrimination, it is undertaking a number of new initiatives that show a renewed focus on facially neutral employer

On Friday, April 20, 2012, the EEOC issued a landmark ruling that intentional discrimination against a transgender individual is discrimination “based on … sex” and thus violates Title VII. Prior to this ruling, the EEOC generally declined to pursue discrimination claims that arose from transgender status or gender identity issues.

What does this mean for