Minnesota Employers Must Take Action in Response to "Ban the Box" Legislation

Blog Pic - MN Capital.jpgOn May 13, 2013, Governor Dayton signed the “Ban the Box” bill into law.  Effective January 1, 2014, private employers must “Ban the Box” inquiring about criminal history on a job application. Specifically, private employers now join their public employer counterparts and are no longer allowed to “inquire into or consider or require disclosure of” an applicant’s criminal record or criminal history until after the applicant has been selected for an interview. If there is not an interview, the prohibition applies before a conditional offer of employment is made to the applicant. S.F. No. 523 (to be codified at Minn. Stat. § 364.021).

Importantly, however, employers who have a statutory duty to conduct a criminal history background check or consider such criminal history during the hiring process (i.e. applications for working at a school or as a school bus driver) do not have to remove criminal history questions from the application. In addition, employers are not prohibited from notifying applicants that “law or the employer’s policy will disqualify an individual with a particular criminal history background from employment in particular positions.”

The Commissioner of Human Rights is tasked with investigating violations of the statute. If a violation occurs prior to January 1, 2015, an employer is given a written warning to remedy the violation. If the violation is not remedied, or subsequent violations occur, the Commissioner may impose up to a $500 fine per violation, not to exceed $500 in a calendar month. For violations after December 31, 2014, the penalties are as follows:

  • Up to $100 per violation for employers with ten or fewer employees, not to exceed $100 in a calendar month;

  • Up to $500 per violation for employers with 11-20 employees, not to exceed $500 in a calendar month; and

  • Up to $500 per violation for employers with more than 20 employees, not to exceed $2,000 in a calendar month.

The remedies stated above are exclusive and an employer is not otherwise liable for complying with or failing to comply with the statute.

Bottom Line

The fix is straight-forward:

  • Employers should “Ban the Box” and remove any questions on the job application related to criminal convictions unless the employer has a statutory duty to consider such information.

  • The statute does not prohibit employers from considering an applicant’s criminal history when deciding whether to offer an applicant a job; it only determines the timing of when such information may be considered.

  • Employers should wait until the interview (or after the conditional offer is made if there is no interview) before inquiring into an applicant’s criminal convictions.

  • Employers have the right to notify applicants that either the law or the employer’s policy will disqualify an individual with a particular criminal background.

  • Employers who wish to include such notification could place it on the job application.

  • At the interview stage, an employer interested in an applicant’s criminal conviction could ask the questions that used to be on the application (i.e. have you ever been convicted of a felony?).

  • As intended by the statute, job applicants now get a chance to explain their side of the story.

U.S. Court of Appeals Invalidates Board's Posting Rule

Blog Pic - Alert Sign.jpgOn May 7, 2013, the U.S. Court of Appeals for the District of Columbia Circuit (“D.C. Circuit”) held that the new rule from the National Labor Relations Board (the “Board”) requiring employers to post a notice regarding employee rights under the National Labor Relations Act (“NLRA” or the “Act”) is invalid because it violates employers’ free speech rights. National Ass’n of Mfrs. v. NLRB, No. 12-5068 (D.C. Cir. May 7, 2013).

The D.C. Circuit’s decision does not directly address the requirement under Executive Order 13496 that covered federal contractors post a different (albeit similar) notice informing employees of the right to unionize and to engage in certain protected activities under the NLRA. While the decision suggests that requiring this posting could also violate employers' free speech rights, because the decision did not directly address the Executive Order, federal contractors should not remove the notice that they are required to post.

The Board’s Posting Rule

As we previously reported, in August 2011, the Board published a rule requiring nearly all private-sector employers to conspicuously post a notice entitled, “Notification of Employee Rights under the National Labor Relations Act.”

With regard to enforcement of the posting requirement, the Board’s posting rule set forth three consequences for an employer’s failure to post the mandated notice: (1) it may constitute an independent unfair labor practice; (2) it may be grounds for tolling the 6-month statute of limitations; and (3) the Board may consider it to be evidence of unlawful motive in a case in which motive is an issue.

D.C. Circuit Strikes Down Posting Rule

After finding that the Board had sufficient members to issue the posting rule (because the Board still had at least three lawfully appointed members at the time it promulgated the posting rule), the Court analyzed whether requiring employers to post the Employee Rights Notice violates employers’ free speech rights under the Act.

Section 8(c) of the Act protects an employer’s First Amendment right to engage in non-coercive speech about unionization and expresses a congressional intent to encourage debate on labor-related issues. Specifically, Section 8(c) provides, in relevant part:

The expressing of any views, argument, or opinion, or the dissemination thereof, whether in written, printed, graphic or visual form, shall not constitute or be evidence of any unfair labor practice under any of the provisions of this [Act], if such expression contains no threat of reprisal or force or promise of benefit.

Drawing from First Amendment case law, the court concluded that while Section 8(c) “precludes the Board from finding non-coercive employer speech to be an unfair labor practice, or evidence of an unfair labor practice, the Board’s rule does both.” That is, the Board’s rule mandates that the failure to post the Employee Rights Poster constitutes an unfair labor practice, and can also be evidence of anti-union animus to support another unfair labor practice. Thus, both of these enforcement mechanisms violated the plain language of Section 8(c) by requiring the employer to disseminate the Board’s Notice in order to avoid one or more unfair labor practice charges.

As to the tolling of the 6-month statute of limitations, the court held that Congress could not have foreseen the type of alleged equitable tolling the Board would attempt to enact into law in 2011, and thus could not have intended that equitable tolling be incorporated into the Act. As a result, the Board’s equitable tolling theory violated the Act.

Because the court concluded that the Board would not have adopted the posting rule absent any basis for enforcement, the court invalidated the posting rule as a whole.

Bottom Line

For now, employers are not required to post this notice (the Supreme Court could ultimately overrule the D.C. Circuit’s decision). As noted above, however, federal contractors are advised to continue to post the notice required by Executive Order 13496 until further notice. We will be closely following this issue. Stay tuned for further developments.

National Labor Relations Board Holds Facebook Firings Illegal

Blog Pic - Facebook on Iphone.jpgAs we have previously reported, whether employees’ social media use is considered protected activity under the law is a hot issue at the National Labor Relations Board (“the Board”).  On April 19, the Board issued a ruling that a company violated the National Labor Relations Act (“the Act”) by firing three employees who complained about work on Facebook.  Design Technology Group, LLC d/b/a/ Bettie Page Clothing, 359 NLRB No. 96 (Apr. 19, 2013).

The employees worked at a retro clothing store in San Francisco selling Bettie Page-inspired items.  Soon after the store opened for business, several employees began complaining about their manager to higher-ups in the company.  They expressed concerns about safety because the store was open later at night than other businesses in the area and they were being harassed on the street when leaving for the evening.  The manager promised to take their concerns to corporate but she never did, leading one employee to speak directly with corporate, who agreed that the store should close earlier.

The manager was upset when she learned that corporate had been contacted and she indicated that the store would return to the later closing time.  Several employees then took to Facebook to air their grievances.  One employee wrote that she needed “a new job,” she was “physically and mentally sickened,” that “Bettie Page would roll over in her grave,” and that the manager made their “lives miserable.”  Another employee responded, stating that the “manager is as immature as a person can be,” that her mother who worked at a law firm would bring a “Worker’s Rights” book to work, and that the other employees would “be surprised by all the crap that’s going on that’s in violation” of the law.  The manager found out about the Facebook activity (from a different employee) and fired the two complainers “because things were not working out.”

The Board ruled that the Facebook posts were “classic concerted protected activity, even absent prior action.”  The Board rejected the employer’s claim that there were also other reasons for the termination.  They also were unimpressed with the employer’s argument that the employees “schemed to entrap their employer into firing them” because they allegedly giggled and hugged when they were fired and later posted on Facebook “OMG the most AMAZING thing just happened!!!!” and “Muhahahahaha!!! So they’ve fallen into my crutches.”  In fact, the Board wrote that “even if the employees were acting in the hope they would be discharged for their Facebook postings, the [employer] failed to establish that the employees’ actions were not protected by the Act.”  Ultimately, the employees – who only worked at the store for a few months – were awarded reinstatement along with several years of backpay.

Bottom Line

This issue continues to evolve and employers should give careful consideration to whether they are infringing on employees’ rights if they take action against them for complaining about work.  Those gripes may reach a larger audience via Facebook but their protected nature may still remain the same.

Supreme Court Holds Employer's Settlement Offer Can "Short Circuit" FLSA Lawsuit

Blog Pic - Supreme Court.jpgIn Genesis HealthCare Corp. v. Symczyk, No. 11-1059 (April 16, 2013), the U.S. Supreme Court ruled that an employee could not continue pursuing her Fair Labor Standards Act (“FLSA”) collective action after her employer made an “offer of judgment” (a type of settlement offer) that would pay her entire claim.

Factual Background

In 2009, RN Laura Symczyk filed a lawsuit on behalf of herself and "all other persons similarly situated" claiming that her employer violated the FLSA by automatically deducting a 30-minute meal break from her daily pay.  In response, the employer made an offer of judgment under Federal Rule of Civil Procedure 68, which provides that if the offer is not accepted, and if the ultimate judgment in the case does not exceed the offer, the party rejecting the offer must pay all the subsequent costs incurred by the other side. The employer’s offer in this instance was $7,500 for alleged unpaid wages as well as "such reasonable attorneys' fees, costs, and expenses . . . as the Court may determine.”

Symczyk failed to respond to the offer one way or the other, so the employer asked the court to dismiss the case. The employer argued that the claim was now moot because the employer offered Symczyk complete relief on her individual damages claim. The trial judge agreed, noting that since no other individuals had actually joined the suit, the employer’s offer of judgment fully satisfied Symczyk's claim. The judge felt that Symczyk should not be allowed to continue litigating when she was already being offered everything she was seeking.

The Third Circuit Court of Appeals disagreed, however, noting that while Symczyk's claim might have been moot, the claims of the proposed class were not completely satisfied. The Appeals Court concluded that a defendant is not permitted to use an offer of judgment to "short-circuit the class action process." This might seem a bit odd since there were no other members of the class, but under the terms of the court’s previous rulings, there was still time for other people to “opt in” to the litigation. Therefore, technically not all of the claims were resolved by the offer of judgment.

Supreme Court Decision

The case was appealed to the U.S. Supreme Court, who agreed with the original ruling that dismissed the case. They ruled that since Symczyk’s individual case became moot, she no longer was an adequate representative of the class of persons harmed by the challenged employment practice. With nobody else able to step up and fill that role, the case had to be dismissed.

One of the questions that the Supreme Court left open was whether an offer of judgment that is not accepted by the other side should be allowed to end the litigation. It seems reasonable to say that if the lead claimant is offered everything she is seeking, she shouldn’t be allowed to reject the offer and keep suing. On the other hand, should employers be able to short circuit the entire action simply by satisfying the lead claimant's claim? Courts differ on this issue, and the Eighth Circuit (in which Minnesota sits) has not yet weighed in.

Bottom Line

The employer’s approach in this case might be useful in some instances to avoid protracted litigation. However, it is not certain whether the federal courts in Minnesota would approve such a tactic, and it is very possible that employers would not want to make such offers because they could be seen as tacit admissions that they did in fact violate the FLSA.

D.C. Court Holds Hospital Group Is a Federal Subcontractor Due to HMO Contract

Blog Pic - Hospital Sign.jpgOver the last few years, the U.S. Department of Labor’s Office of Federal Contract Compliance Programs (“OFCCP”) has taken an expansive approach as to when hospitals should be considered “federal contractors” and/or “federal subcontractors.” This enforcement trend is significant because, among other things, federal contractors and subcontractors must comply with the federal affirmative action laws (Executive Order 11246, Section 503 of the Rehabilitation Act and Section 402 of the Vietnam Era Veterans Readjustment Assistance Act of 1974).

In OFCCP v. UPMC Braddock, ARB Case No. 08-048, ALJ Case Nos. 2007-OFC-001, 2007-OFC-002, 2007-OFC-003 (May 29, 2009), the Department of Labor’s Administrative Review Board (“ARB”) found that three Pittsburg Hospitals were federal subcontractors. The Government (the Office of Personnel Management (“OPM”)) contracted with a Health Plan (UPMC) to provide HMO coverage for its federal employees. In turn, the Health Plan contracted with the Hospitals via a HMO contract. The ARB concluded that the Hospitals were federal subcontractors because:

The UPMC’s contract with OPM required UPMC to put a health maintenance organization (HMO) into operation. The contract thus depended on medical providers like the [Hospitals] to offer medical services and supplies necessary for the UPMC to meet a portion of its obligation under its contract with OPM to put an HMO into operation. Therefore, their contracts with UPMC are subcontracts under the second prong of the definition [(performing a portion of the contractor’s obligations under the contract)].

(Emphasis added).

An appeal of this decision has been pending in United States District Court, District of Columbia, for the past several years. On March 30, 2013, the D.C. Court affirmed the administrative determination. (UPMC Braddock v. Harris, D.D.C., No. 09-01210, 3/30/13).

The D.C. Court agreed with the ARB’s reasoning that the Hospitals are federal subcontractors because the services provided by the Hospitals were necessary to the performance of the HMO's prime contract with the Government (the OPM). The Court ruled that it did not matter that the prime federal contract between the Government (OPM) and the Health Plan (UPMC) specifically stated that medical providers (i.e. Hospitals) would not be considered federal subcontractors. Basically, the Court concluded that the contract could not trump the law. The Court also found it insignificant that the Hospitals had never “consented” to be federal subcontractors. Again, the Court held that the only issue is whether or not the Hospitals meet the legal definition of federal subcontractors - consent is not required.

New Form I-9 Released

Blog Pic - Passport.jpgThe United States Citizenship and Immigration Services (“USCIS”) released a new Employment Eligibility Verification Form I-9 (“Form I-9”) this month. 

The Form I-9 is used to verify both the employment authorization eligibility and the identity of employees.  Although employers should begin using this new form immediately, the USCIS acknowledges that some employers may need sufficient time to update their business processes prior to transitioning to the use of this form. As a result, if necessary, employers can continue using previously valid Forms I-9 until the use of the new form becomes mandatory on May 7, 2013.  Employers who fail to utilize the new Form I-9 as of May 7, 2013, may be subject to penalties as set forth in 8 U.S.C. § 1324(a).

Provided that re-verification does not apply, employers are not required to complete a new Form I-9 for any current employees for whom proper Forms I-9 are already on-file.

The changes are aimed at minimizing errors in form completion and include:

  • Expanded instructions;

  • Expanded length from one to two pages; and

  • New fields for e-mail addresses, phone numbers, and foreign passport information in Section 1.

The revised form includes “Rev. 03/08/13” in the lower left corner of the page and is accessible at www.uscis.gov.

Bottom Line

Employers should be aware of the new Form I-9 and begin utilizing it immediately, if possible. Failure to use this new form when it becomes mandatory on May 7, 2013, may subject employers to penalties.

More information about the new Form I-9 is available at www.uscis.gov/I-9Central.

 

Do You Need to Accommodate Your Vegan Employee? Court Rules "Maybe"

Blog Pic - Carrots.jpgIn a recent case involving the discharge of a vegan employee for her refusal to be vaccinated for the flu, a federal district court judge in Ohio ruled that the employer may have violated Title VII, refusing to dismiss the former employee’s claim. In the past, the hospital employer had permitted the former employee to forgo the vaccination due to her claim that the vaccine contained animal products and would therefore be contrary to her religious and philosophical beliefs as a vegan. However, in 2010, the employer changed its practice and terminated the employee.

The court in Chenzira v. Cincinnati Children's Hosp. Med. Ctr., No. 11-cv-00917, (S.D. Ohio Dec. 27, 2012) rejected the employer’s argument that veganism does not qualify as a religion, but is merely the employee’s dietary preference or social philosophy. It reasoned that the former employee alleged a plausible claim that she subscribes to veganism “with a sincerity equating that of traditional religious views” and the matter should go to trial. The Supreme Court and the EEOC regulations and have interpreted “religious belief” broadly, giving protection to employees with moral or ethical beliefs as to what is right and wrong which are sincerely held with the strength of religious views.

Bottom Line

The moral of the story? When your employee asks for an exception to a policy or requirement based on a “sincerely held belief,” consider whether it may be considered a religious belief subject to protection by Title VII.

Obama's Recess Appointments to the Labor Board Held Unconstitutional; Agency Rulemaking and Numerous Decisions Could Be Invalid

Blog Pic - Gavel or Justice.jpgIn a move with extremely significant implications, the U.S. Court of Appeals for the D.C. Circuit held that President Obama’s three recess appointments to the National Labor Relations Board in January of 2012 were unconstitutional. Because the three recess appointments were invalid, the Board was legitimately comprised of only two members (an insufficient number) when it issued its decision and order in the underlying case. (As we previously reported, the U.S. Supreme Court held in New Process Steel, LP v. NLRB, 130 S. Ct. 2635 (2010), that the Board must have at least three members (i.e., “quorum”) to issue decisions and orders, as well as rulemaking.) Accordingly, the D.C. Circuit in Noel Canning v. NLRB, Case No. 12-1115 (D.C. Cir. Jan. 25, 2012), vacated the Board’s unfair labor practice determination.

Generally, the President is supposed to nominate Board members, and the Senate is supposed to confirm, before they can be appointed. However, it has been recognized that when the Senate is in recess, the President may temporarily appoint a Board member without Senate approval. On January 4, 2012, President Obama, attempting to appoint Board members without Senate approval, recess appointed three individuals as Board members – Sharon Block, Richard Griffin, and Terence Flynn. If valid, this action would have properly taken the Board up to a full complement of five members (albeit only for a limited period of time).

In this case, however, the D.C. Circuit invalidated the recess appointments on two separate grounds. First, the court reviewed the text and history of the Recess Appointment Clause to the Constitution and held that a recess appointment must be made during “intersession recesses” of the Senate. The Board appointments were not made during an intersession recess because they were made on January 4, 2012, which was one day after the Senate began a new session.

Second, the court concluded that the Constitution permits the President to make a recess appointment only when the vacancy arises during the recess. Two of vacancies arose on dates when the Senate was in session, so those vacancies did not qualify for a recess appointment. The final vacancy, which was open on January 3, 2012, was similarly invalid because “the Senate did not take an intersession recess . . . .” Instead, the Senate held “pro forma” sessions every three days from December 20, 2011 through January 22, 2012.

Bottom Line

The Board has, since January of 2012, issued numerous important decisions (some of which purported to change well-established law), and the Board has also engaged in significant rulemaking. Unless the D.C. Circuit reverses itself – or the Supreme Court overturns the D.C. Circuit’s decision – all of the Board’s recent and controversial actions are in jeopardy. Undeterred, Board Chairman Mark Gaston Pearce has announced that the Board will continue issuing decisions and orders notwithstanding the D.C. Circuit’s decision.

Now that we are well into January of 2013, the President has no ability at the present time to recess appoint anyone as a Board member, and given the position of the White House that the appointments were constitutional, it seems unlikely that the President will nominate a package of Board members for Senate approval. In the meantime – while this issue continues to be reviewed by the Courts – the Board and its decisions and orders are in limbo.

Attorney Grant T. Collins also contributed to this report.

Labor Board Finds DirectTV's Handbook Policies Unlawful

Blog Pic - Employee Handbook.jpgAs we previously reported, the National Labor Relations Board (“NLRB”) continues to scrutinize whether the employee handbooks of non-union employers can reasonably be construed to violate employee rights under federal labor law.

Most recently, the NLRB ruled in DirectTV, 359 NLRB No. 54 (Jan. 25, 2013) that policies from DirectTV unlawfully infringed on employee rights to engage in concerted activity protected by the National Labor Relations Act (“NLRA”).

Limits on Third-Party Communications Must Not Be Overbroad

Specifically, the NLRB ruled that the following directives in DirectTV's employee handbook violated the NLRA:

  • “Do not contact the media.”

  • “Employees should not contact or comment to any media about the company unless pre-authorized by Public Relations.”

  • “If law enforcement wants to interview or obtain information regarding a DirectTV employee . . . the employee should contact the security department . . . .”

The Labor Board considered the first restriction overbroad because the NLRA would protect employees’ communications with the media about a labor dispute. The Board said the second rule was unlawful because “any rule that requires the employees to secure permission from their employer” to engage in protected communications is unlawful.

The NLRB found the last directive unlawful because a reasonable employee could interpret the ban on communicating with “law enforcement” to prohibit employee cooperation with NLRB investigations, which is protected by the NLRA. The Board seemed to suggest that a more limited rule, or at least one that exempted employee communication with Board agents, may be lawful.

Imprecise Definitions Are Fatal to Confidentiality Policies

The Labor Board also found two of DirectTV’s policies forbidding the disclosure of “confidential information” and “company information” unlawful because they limited employees’ ability to share “employee records” with other employees as well as “third parties such as union representatives, Board agents, or other governmental agencies concerned with workplace matters.” The NLRB concluded that a reasonable employee would construe the provision to prohibit sharing information on wages and other terms and conditions of employment.

Bottom Line

Non-union employers should be wary of handbook policies that broadly prohibit communication with other employees or third-parties because they could be read to restrict employee rights under the NLRA. Think carefully about the harms that you are trying to prevent through these policies and consider articulating them more precisely so that the Labor Board does not view them as overbroad and infringing on employee rights.

DOL Issues New Guidance on the FMLA Rule for Caring for Adult Children

Blog Pic - Adult Child with Disability.jpgOn January 14, 2013, the U.S. Department of Labor (“DOL”) issued a new Administrator’s Interpretation on who qualifies as an adult “son or daughter” under the Family and Medical Leave Act (“FMLA”) when an employee seeks protected leave to care for that individual.

FMLA entitles an eligible employee to take up to 12 workweeks of unpaid leave during a 12-month period to care for a son or daughter with a serious health condition. The definition of “son or daughter” includes individuals over the age of 18 if:

  1. the individual has a disability as defined by the ADA (as amended by the ADA Amendments Act of 2008 (ADAAA));

  2. the individual is incapable of self-care due to that disability, which means that he or she “requires active assistance or supervision to provide daily self-care in three or more of the ‘activities of daily living’ or ‘instrumental activities of daily living’”;

  3. the individual has a serious health condition; and

  4. the individual is in need of care due to the serious health condition.

Child’s Age at Onset of Disability Is Not Relevant

The Administrator’s Interpretation makes clear that FMLA leave is available even if the employee’s child developed the disability after reaching the age of 18.  In short, FMLA applies to caring for adult children if they meet the requirements set forth above.

More Adult Children Will Qualify as “Disabled” Under the Amended ADA

The Administrator’s Interpretation reminds employers that the ADA’s definition of “disability” has been substantially broadened by the ADAAA.   For example, there is no minimum duration for an impairment to be considered a disability, and an impairment that is in remission can still be considered a disability if it would substantially limit a major life activity when it is active. Even so, FMLA leave is only available if the adult child is incapable of self-care due to a disability and needs care due to a “serious health condition” under the FMLA regulations.

As an example, an employee’s 25-year old son with diabetes qualifies as having a disability under the ADA, but if he lives independently and does not need assistance with any daily activities, he will not be considered an adult “son” under FMLA. However, if he becomes unable to walk and care for himself, he will meet the definition and a parent could then take FMLA leave to care for him if such care is needed for a serious health condition.

Bottom Line

While an Administrator’s Interpretation does not carry the same weight as a regulation or judicial opinion, it does offer detailed guidance to managers applying the FMLA’s provisions in the context of employees caring for adult children.  Employers should study its contents carefully and ensure that qualifying parents are afforded FMLA leave.