When engineer Anthony Levandowski announced in January 2016 that he was leaving Google for Uber, his employer was not happy. Levandowski was not just any engineer. As the head of Google’s efforts to develop a self-driving car, he was a Silicon Valley superstar, and now he was taking his considerable talents to Google’s chief rival in the race to develop a truly autonomous automobile.

Google was not going to take the defection lying down. Not long after Levandowski departed, Google sued Uber seeking $1.85 billion in damages and an injunction that would severely limit the work Levandowski would be able to do for Uber. Although the case eventually settled (during trial) for just a fraction of what Google originally sought, the wreckage was widespread: Levandowski was left unemployed, Google received $250 million worth of Uber stock, and both parties owed their attorneys tens of millions of dollars in legal fees.

The remarkable thing about Levandowski’s case is that Google never alleged that Levandowski had breached a non-compete agreement. They couldn’t, because he never had one. Non-competes are completely unenforceable in California.

The Levandowski case serves as a reminder that an employee and his future employers are bound by a web of legal obligations even when the employee is otherwise free to leave his current employment and go to another employer of his choosing.

The Duty of Loyalty and Other Limits on the Privilege to Compete

Most businesses are familiar with the doctrine of at-will employment. It provides that, generally, an employer can terminate an employee at almost any time and for almost any reason. (There are notable exceptions, such as terminating for an illegal or discriminatory reason.) The principle goes both ways. Employees are generally free to leave for greener pastures wherever they can find them. On top of that is the “privilege to compete,” which allows a company to compete against others in the open market for scarce customers, resources, and even talented employees. These doctrines are reinforced by states’ longstanding public policies against non-compete agreements and other “restrictive covenants.” This animosity toward limiting competition often renders any attempt to contractually bind an employee from jumping ship substantially – or even completely – unenforceable. Together, these doctrines help create an economy where the competition among companies for good employees is just as stiff as the competition for good customers.

But even against that background, neither the at-will employment doctrine nor the privilege to compete are unlimited. Both are restricted in ways that create potential risks for employers and the talent they seek to recruit.

As an initial matter, all workers – even the rank and file – have a “duty of loyalty” to their employers. The duty of loyalty is not as restrictive as the “fiduciary duty” that binds officers, directors, and other essential personnel, but it has “teeth” nonetheless. At its core, the duty of loyalty means an employee cannot compete against her employer or otherwise actively work against her employer’s interests. In practice, this typically means that an employee can plan to compete against her employer, but she cannot in fact compete against her employer while she is still employed.

To illustrate: George works for an advertising agency, but he dreams of having his own agency one day. While he is still working for his current agency, can he form an LLC, rent office space, and print business cards in anticipation of the day he finally strikes out on his own? He can. But can he take his clients out to lunch to discreetly inform them of his plans and solicit their business for his future agency? He cannot. The former is merely planning to compete against his current employer. The latter is actually competing against his current employer, and that is forbidden by the duty of loyalty.

Hiring a Competitor’s Employees – “Wrongful Means” and Employee Raiding

In addition to the duty of loyalty, the law recognizes that a business has a legally-protectible interest in an existing relationship between it and its employee, even when the relationship is at will, and the law will punish a third party’s attempts to induce a breach of loyalty or wrongfully interfere with that relationship. As a result, these obligations create some risk for the prospective employer, who must take care not to contribute to an employee’s breach of his duty of loyalty or otherwise interfere with the current employer’s rights.

So what can you do to hire away employees from another business? In Georgia and many other states, a prospective employer (Employer B) will be protected from liability when recruiting from a competitor (Employer A) if the following conditions are met:

• The relationship between the employee and Employer A concerns a matter involved in the competition between Employer A and Employer B;
• Employer B does not use any “wrongful means” to recruit the employee;
• Employer B’s actions don’t create or continue an “unlawful restraint of trade” (that is, they are not intended to help Employer B create a monopoly for its goods or services); and
• Employer B’s purpose is at least in part to advance its own interest in competing with Employer A.

It’s the second prong – the use of “wrongful means” – that most commonly causes issues. What exactly are wrongful means? They are often described as actions that are wrong on their own, even outside the context of recruiting – such as using fraud or defamation. But cases involving such obviously wrongful means are not particularly common. The following scenario is both more common and less obvious.

Imagine that our adman George has decided he would rather not go out on his own after all. What he really wants to do is join a better agency, and his valuable book of business has landed him an offer with his current agency’s biggest rival. Of course, both George and the new agency expect George to bring his clients with him when he leaves. But George can’t serve those clients all on his own, and he would like to bring some additional talent with him to the new agency. So after putting in his two weeks’ notice – but before he actually leaves his employment with the company – he sets about recruiting some key members of his team to come with him and, with the new agency’s permission, extends formal offers of employment.

Is this allowed? Usually not. George is still an employee of the first agency, and by recruiting the first agency’s talent he is benefitting the new agency at the expense of his own employer. In short, George is violating his duty of loyalty to the first agency. But the new agency’s hands are not clean either. It has knowingly used George as a double agent to recruit talent from a competitor. This is the kind of “wrongful means” that the law forbids.

A special situation arises when one company “raids” another by hiring away a large portion of its employees at one time. As in a case where only one employee is hired, the central question is usually whether the hiring company used any wrongful means in its efforts to recruit. The problem in a case of mass hiring comes when the hiring party’s efforts are so successful that the mass defection leaves the competitor unable to function. In these cases, some courts have found that the crippling of the competitor is itself wrongful and therefore prevents the hiring company from claiming the protection of the privilege to compete.

It is often remarked that this is especially true if “other circumstances are present.” Unfortunately, few courts explain what those other circumstances may be, creating a zone of uncertainty for companies that aggressively recruit from their competitors. In the end, special care must be taken before recruiting a group of employees to leave a competitor en masse.

The Trade Secrets Trap

The special knowledge that makes a recruit highly desirable often includes special knowledge about his employer. For this reason, claims that a company used wrongful means to hire from a competitor are often accompanied by accusations that the competitor’s trade secrets have been stolen. These claims often directly implicate the hiring company as a co-conspirator. Google’s lawsuit against Uber, for example, turned largely on allegations that Uber used Levandowski to steal Google’s trade secrets.

A trade secret is generally defined as having four qualities: One, it must be information. Two, the information must derive economic value from the fact it is secret. Three, the information must not be generally known. And four, the information must be the subject of reasonable efforts to maintain its secrecy.

The subject of what is and is not a trade secret could never be adequately covered in a single article. But for the purposes of hiring from a competitor, one characteristic should always be remembered: Trade secrets may or may not be the subject of a confidentiality agreement. Trade secrets are protected by state and federal law, so the fact that a new hire is not bound by a confidentiality agreement with her former employer does not, by itself, mean she does not possess any trade secrets that could create liability for the new employer.

Furthermore, liability for the theft (or misappropriation) of trade secrets is not limited just to the individual who actually pilfered the information. It also extends to any person who acquires or uses the information knowing that it was wrongfully obtained in the first place – or even simply having reason to know that the source of the information (i.e., the new hire) had a duty to a third party (i.e., the former employer) to keep it secret. This principle creates some measure of risk when hiring an employee who may possess sensitive information.

Difficult problems arise when a departing employee does not actively “take” his former employer’s trade secrets but, rather, simply possesses his former employer’s trade secrets only in his memory. It’s fair to say, though, that the typical suit over trade secrets involves much more concrete claims. The jilted employer often alleges that the former employee left with copies of his former employer’s files. These days, it is not uncommon to read allegations that, prior to his departure, the employee downloaded valuable files to a thumb-drive, sent them as attachments to a personal email account, or even photographed files with a smart phone.

Not all files contain trade secrets, of course. Nevertheless, an employer should never encourage or facilitate a new hire’s removal of files from his former employer.

Conclusion

Non-compete agreements and other restrictive covenants are often a concern when hiring new employees, especially those with specialized skills and abilities. Even in the absence of a restrictive covenant, however, employees and their suitors are still bound by rules that arise solely from the law. Employers must be mindful of these non-contractual restrictions when recruiting potential employees.  If you have any questions about this article or need assistance in assessing your business’s rights with respect to a prospective employee or a departing employee, please contact Ben Byrd at bbyrd@fh2.com or (770) 399-9500 to discuss further.

You have finally found a prospective employee who meets all of your search criteria and is a superstar (or prospective superstar) in the field.  You want to move forward with the hiring process on an expedited basis.  You extend a generous offer, which is promptly accepted.  And then you discover, one way or another, that this individual has a restrictive covenant agreement (a “Covenant Agreement”) with a prior employer.  What should you do?  What if you don’t find out about the Covenant Agreement until after you have hired the individual?

Covenant Agreements are becoming ever more common and they come in many forms.  This article will familiarize you with Covenant Agreements generally and will provide you with guidance regarding what you can do to protect yourself from legal liability and business disruption.

I.  LIABILITY AND DISRUPTION: RISKS TO YOUR BUSINESS

A.  What is a Covenant Agreement? Let’s be clear about what we are talking about.  For purposes of this article, a Covenant Agreement is a contract between your (prospective) employee and a current or prior employer that restricts the activities of the employee after the employment relationship terminates.  The restrictions can take many forms and the terms vary significantly from one Covenant Agreement to another.

Covenant Agreements are often referred to as “non-competes” or NDAs (short for “non-disclosure agreement”) and some are indeed just that.  Non-competes include terms that restrict an employee from engaging in activities that compete with the prior employer.  NDAs restrict the use of the former employer’s confidential information and trade secrets.  In most cases, however, Covenant Agreements include a number of different restrictive covenants so, if a prospective employee tells you he or she has an NDA with a prior employer, do not assume the document is indeed “just” a non-disclosure agreement.

Indeed, the majority of Covenant Agreements include at least two and often several different post-employment restrictions on conduct, such as provisions restricting the employee from:

• contacting customers, suppliers, and/or employees of the prior employer;
• saying or otherwise communicating damaging or negative information about the prior employer;
• using materials that the employee developed with the prior employer;
• keeping information or documents acquired in connection with the prior employment; and
• using information acquired in connection with the prior employment.

Also, Covenant Agreements are not necessarily separate, stand-alone agreements.  They may be included in the terms of another, broader agreement, such as an employment agreement or a separation agreement.  Covenant Agreements may also be embedded in equity and bonus award agreements, transaction agreements, and deferred compensation agreements.  In short:  when assessing whether a prospective new hire is bound by a Covenant Agreement—and, if so, what restrictions apply to the new hire—do not depend on the “label”; review the document itself.

B.  Why Do I Need to be Concerned? I’m Not a Party to the Covenant Agreement.  It is basic contract law that a party to a contract can pursue its remedies against the other party to the contract in the event the other party breaches the agreement.  Clearly, a former employee who breaches a Covenant Agreement is liable for whatever damages are imposed by law or contract.  But how can a Covenant Agreement impact a subsequent employer who isn’t a party to the Covenant Agreement?  The answer is:  it depends on a number of factors, but the following is a brief summary of the possible ways a Covenant Agreement can disrupt the business of—or even create legal liability for—the subsequent employer.

Injunctions Against the Employee.  Practically without exception, Covenant Agreements permit the former employer to seek an injunction.  An injunction is a court order preventing the former employee from engaging—either temporarily or permanently—in the conduct that the former employer alleges is a breach of the Covenant Agreement at issue.  For example, if the employee has allegedly breached the Covenant Agreement by working for his or her current employer, the injunction can bar the employee from continuing such employment.  If an employer is relying on the skills and contribution of that employee, an injunction can be very disruptive.

Legal Claims Against the Current Employer.  A former employer that is a party to a Covenant Agreement has many causes of action that it might allege against the current or future employers even though there is no contract between the two employers.  These include: tortious interference with a contractual relationship; intentional interference with business relations; inducement to breach; civil conspiracy; misappropriation of trade secrets and proprietary information; conversion; and unfair competition.

It is important to note that, in some instances a candidate’s behavior may be actionable even in the absence of any Covenant Agreement. In most jurisdictions, employees have a common law duty of loyalty (and often a fiduciary duty) to act in the best interest of their current employer, even after tendering a notice of resignation. Violation of this duty of loyalty can result in substantial damages against the employee and, to the extent a subsequent employer is found to have assisted the employee in breaching his duty of loyalty, there is potential exposure to the new employer for aiding and abetting the employee’s breach.

C.  What Can an Employer Do? Whether the hiring employer will be directly liable to the former employer is largely predicated on the hiring employer’s intent and good faith, and whether it actually benefitted from the new hire’s unlawful conduct. Being able to show the following can provide a powerful defense for the hiring employer against this liability:

• The hiring employer took diligent steps to determine at the pre-hire stage whether the employee was subject to post-employment restrictions.
• The hiring employer was advised by legal counsel that, by hiring the employee, it would not interfere with an existing contractual restriction.
• The hiring employer instructed the new hire that he or she was not expected or permitted to (1) use or disclose any trade secrets or confidential information belonging to his or her former employer, (2) improperly divert business opportunities belonging to the former employer, or (3) engage in any other conduct that would breach his or her Covenant Agreement.
• The hiring employer instituted internal protocols to ensure against the inadvertent use or disclosure of the former employer’s trade secrets or confidential information.
• The hiring employer continued to monitor the new hire’s conduct to ensure continued compliance with any post-employment restrictions that the former employer imposed.
• The hiring employer used due diligence to ensure that it did not benefit from the new hire’s use or disclosure of the former employer’s trade secrets or confidential information.

II.  INVESTIGATE COVENANT AGREEMENT ISSUES DURING THE INTERVIEW PROCESS

Ask the Candidate If He or She Is Subject to Any Covenant Agreements.  The first thing an employer should do is ask a prospective employee whether he or she is subject to any Covenant Agreement.  This should be thoroughly vetted well before a decision is made regarding hiring the individual.  If the employer engages in adequate due diligence before it hires a candidate who is subject to a Covenant Agreement and makes a reasonable hiring decision based upon such due diligence, it would be very difficult for the former employer to assert any of the causes of action indicated above against the new employer.  (This, however, would not allay the possibility that the candidate would be enjoined from working for the new employer, in whole or in part, temporarily or permanently.)

Keep in mind that, as a general rule, restrictions imposed by Covenant Agreements may extend for a period of two years after employment terminates and in certain cases even longer.  Therefore, you should inquire not only about a candidate’s current or immediately prior employer, but also about earlier employers. The take away here is that when you endeavor to determine whether a candidate is a party to a Covenant Agreement, be sure to ask the right questions and review all agreements between the candidate and its prior employers.

If the Answer is “No” – “I Don’t Have A Covenant Agreement” and Other Tall Tales.

Going back to the facts described in the first paragraph of the introduction above, let’s assume that you asked the prospective superstar-employee whether he or she is subject to a Covenant Agreement and he or she says, “no.”  That should not be the end of your inquiry for a number of reasons.  First, strange as it may seem, employees often forget that they have signed Covenant Agreements.  Second, if the Covenant Agreement is embedded in another agreement, they might not realize that they are subject to one.  Third, the employee may unilaterally decide that although he or she has a Covenant Agreement, employment with you would not breach it and that therefore not disclosing it to you would do no harm.  Fourth, the prospective employee may want the job you are offering badly enough or believe the risk of enforcement is low enough that he or she decides to not disclose the fact that he or she is a party to a Covenant Agreement with a prior employer.

If the candidate affirms that he or she is not subject to any Covenant Agreement and you decide to hire him or her, then, as a pre-requisite to employment, require him or her to sign a notarized statement verifying that he or she is not subject to any Covenant Agreement with any current or former employer and stating that this verification is a pre-condition to the hiring decision, and that if the foregoing proves to be false for any reason, he or she would be subject to immediate termination of employment and be solely liable for any costs and expenses you incur if any action is brought against you because of it.

If the Answer is “Yes.”

Ask for a copy of the Covenant Agreement and have it reviewed by legal counsel who is knowledgeable about Covenant Agreements and the law implicated by them.  Your legal counsel should provide you with an assessment of whether the Covenant Agreement is enforceable, along with a plain English translation of what the Covenant Agreement prohibits, including the time limits, geographic scope, and the precise activities prohibited if the Covenant Agreement is enforceable and enforced.  Be sure to give your attorney enough specific information about what activities the prospective employee would perform for your company, if hired by you, so your attorney can advise you as to whether the prospective employee would violate the Covenant Agreement by working for you.

If you and your attorney determine that a candidate would be in breach of a Covenant Agreement by working for you and that the former employer is likely to sue, you can avoid that liability completely by not hiring the individual.  However, the issues are most often not so black-and-white.  In this case, you would need to consult with your attorney to weigh various factors to arrive at the decision as to whether to hire the candidate, including, for example: (i) the risk (and potential cost) of litigation and the potential disruption to your business (including the risk that your new hire will be enjoined from working for you, either temporarily or permanently); (ii) the likelihood that the former employer will be successful in enforcing the Covenant Agreement and your business’s potential liability for money damages; and (iii) any steps you can take to minimize or avoid a claim that the new hire is violating the Covenant Agreement.

III.        MANAGING COVENANT AGREEMENT ISSUES

Because Covenant Agreements are so common these days, there is a high likelihood that any new hire will be subject to a Covenant Agreement.  Even if you have determined that the anticipated scope of duties the candidate will perform for your business isn’t likely to violate a Covenant Agreement, you should still implement policies—whether in your standard employee manuals, offer letters, and/or employment agreements—to demonstrate your expectation that your employees will comply with their obligations to prior employers, such as a prohibition on the unauthorized use or distribution of property, confidential information, or trade secrets of a third party.

However, if you and your legal counsel determine that a candidate is subject to an enforceable Covenant Agreement, and that the position for which the candidate is being considered might be construed as requiring the candidate to violate the terms of that Covenant Agreement, there are a number of things you can do to minimize the risk of litigation if you decide to proceed with hiring the individual.  Possibilities include: (i) if feasible, restructuring the position so that the duties and responsibilities do not run afoul of the Covenant Agreement (or at a minimum), placing the new hire in a temporary position that does not violate the Covenant Agreement for the duration of any contractual restriction period; (ii) asking the former employer to waive the restrictions or negotiate restrictions that both of you can live with; or (iii) structuring the new hire’s work to insulate him or her from departments or projects involving confidential information or clients for which the new hire might possess competitively valuable information belonging to his or her former employer.  Also, the hiring employer should consider whether it should leave itself an “out” by requiring the candidate to acknowledge and agree that if litigation is threatened or arises over any Covenant Agreement, it reserves the right to terminate the candidate or alter the candidate’s job requirements.

Lastly—and regardless of the steps you may have taken to avoid or minimize the risk that your new hire is violating a Covenant Agreement—there is always a risk that the prior employer will nonetheless suspect a violation or threaten legal action against you.  As such, there are actions you should take after hiring an employee who is subject to a Covenant Agreement if you receive a “cease and desist” letter or any other communication regarding the terms of the Covenant Agreement from the former employer.  Proper management of this situation can reduce, limit, or eliminate your potential liability in connection with an employee’s Covenant Agreement with a prior employer.  You should contact your attorney immediately, both to formulate a strategy for responding to the prior employer and to ensure that you are taking the proper internal steps to preserve evidence that may become important if the matter proceeds to litigation.

If you have any questions or would like additional guidance regarding restrictive covenant agreements or other employment law issues, please contact Suzanne Arpin at SArpin@fh2.com or (770) 399-9500.

Many employers require employees to sign arbitration agreements as a condition of their employment.  Under those agreements the employee gives up his/her right to sue in court over job-related issues such as wrongful termination, breach of contract, and discrimination, and agrees to pursue such legal claims against the employer through arbitration.  These agreements often go further to provide for individualized arbitration proceedings, which means that claims pertaining to different employees will be heard in separate arbitration hearings – thereby precluding employees from bringing collective or class actions regarding workplace claims.  The use of mandatory, pre-dispute arbitration agreements has increased significantly over the past two decades.  A 2017 survey by the Economic Policy Institute showed that approximately 60 million private-sector, nonunion employees in the United States are subject to mandatory arbitration in their employment agreements, and almost 25 million of those agreements include a class action waiver.

The issue of whether these class action waivers are enforceable has been a contentious issue.  Although the Federal Arbitration Act (“FAA” or “Arbitration Act”) generally requires courts to enforce arbitration agreements as written, the FAA contains a so-called “saving clause” that permits courts to refuse to enforce arbitration agreements “upon such grounds as exist at law or in equity for the revocation of any contract.”  Employees have argued that the FAA’s “saving clause” nullifies the enforceability of an arbitration agreement if that agreement violates some other federal law.  Specifically, until the United States Supreme Court decision discussed below, federal courts disagreed whether arbitration agreements containing a class action waiver violate the National Labor Relations Act (“NLRA”), thus rendering them invalid and unenforceable.  On May 21, 2018, the Supreme Court resolved this issue, holding that agreements requiring employees to arbitrate claims on an individual basis are enforceable.  Here’s what you need to know.

Some Differences Between Arbitration and a Court Case

An arbitration differs from a court case in a number of ways, including:

• An arbitration is not heard and decided by a judge or jury, but by a neutral and independent “arbitrator” agreed to by the parties, and who is paid by one or both sides to listen to the evidence and witnesses, and issue a decision, which is called an “award.”
• The arbitration process generally limits the amount of information each side can get from the other, which oftentimes gives the employer an advantage because the employer is usually the one in possession of most of the documents and information relating to the employee’s case.
• Arbitrations are less formal than court trials, which can make the process easier for all involved, especially employees who are not used to litigation.
• Arbitration cases are generally heard and decided much more quickly than court cases, which can take several years from start to finish, and arbitration is usually less expensive.

How We Got Here

Until a few years ago, both courts and the National Labor Relations Board (the “NLRB”) seemed to be generally in agreement that arbitration agreements (including ones that required individualized proceedings) were to be enforced according to their terms.  However, in 2012 the NLRB ruled in D.R. Horton, Inc., 357 N.L.R.B. 2277 (2012), that arbitration agreements containing class action waivers violated Section 7 of the NLRA, which guarantees workers the rights to self-organize, to form labor organizations, to bargain collectively, and to “engage in other concerted activities for the purpose of collective bargaining or other mutual aid or protection.”  In its ruling, the NLRB found that agreements requiring employees to arbitrate their claims on an individual basis violated the NLRA, rendering these agreements invalid and unenforceable.

Since the NLRB’s decision, federal appellate courts have split on the issue.  Some circuit courts, including the Seventh and Ninth Circuits, agreed with the NLRB, while other circuit courts, including the Fifth Circuit, found such class action waivers to be enforceable and not in violation of the NLRA.

The Epic Systems Case

Against this background of conflicting decisions by various federal courts and the NLRB, on May 21, 2018, the United States Supreme Court held, in a 5-4 decision, that agreements requiring employees to arbitrate claims on an individual basis are enforceable.

The case, Epic Systems Corp. v. Lewis, 584 U.S. ____ (2018), consolidated three different cases on appeal from the Fifth, Seventh and Ninth Circuits.  In each of these cases, an employer and employee had entered into a contract providing for individualized arbitration proceedings to resolve employment disputes between the parties.  Nevertheless, the employee plaintiffs in each of these cases sought to litigate Fair Labor Standards Act and related state law claims through class or collective actions in federal court.  To avoid enforcement of the class action waivers under the FAA, the employees argued that, by requiring individualized proceedings, the arbitration agreements at issue violated Section 7 of the NLRA, which under the FAA’s saving clause rendered the arbitration agreements unenforceable.  The employer defendants, on the other hand, argued that the FAA protects agreements requiring arbitration from judicial interference, and that neither the FAA’s saving clause nor the NLRA demands a different conclusion.  A majority of the Supreme Court agreed with the employers.

The FAA’s Saving Clause Did Not Apply to the Employees’ Claims 

The FAA “requires courts ‘rigorously’ to ‘enforce arbitration agreements according to their terms, including terms that specify with whom the parties choose to arbitrate their disputes and the rules under which that arbitration will be conducted.’”  Nonetheless, the Court noted that the FAA’s saving clause, by its terms, “allows courts to refuse to enforce arbitration agreements ‘upon such grounds as exist at law or in equity for the revocation of any contract.’”

The employee plaintiffs in Epic Systems argued that the FAA’s saving clause creates an exception for cases like theirs, where the arbitration agreement (arguably) violates some other federal law.  In its Horton decision the NLRB found that requiring employees to arbitrate their claims on an individual basis was a violation of the NLRA.  The employees in Epic Systems argued that the saving clause applied because the NLRA renders their class and collective action waivers illegal, and in their view, “illegality under the NLRA is a ‘ground’ that ‘exists at law … for the revocation’ of their arbitration agreements, at least to the extent those agreements prohibit class or collective action proceedings.”  The Court rejected this argument, holding that in permitting courts to refuse to enforce arbitration agreements “upon such grounds as exist at law or in equity for the revocation of any contract . . . ”, the FAA’s use of “any contract” limits the saving clause only to generally applicable contract defenses, such as fraud, duress, or unconscionability, and not to defenses specific to arbitration contracts (such as the employees’ claims that arbitration agreements requiring individualized proceedings are unlawful under the NLRA).

 The NLRA Does Not Conflict with the FAA

But the employees were not done yet.  Following the NLRB’s decision in Horton, they argued that Congress nonetheless intended Section 7 of the NLRA to render employee class action waivers in arbitration agreements unlawful, even though such class action waivers would otherwise be enforceable under the FAA.  That is, in cases like theirs, the NLRA overrides the FAA.  The Court noted that when confronted with two Acts of Congress allegedly touching on the same topic, the Court must strive to give effect to both.  To prevail in this case, the employees must show a “clear and manifest” congressional intent to displace one Act with another.

After a lengthy and comprehensive analysis of Congress’ intent, the Court held that there is no conflict between the NLRA and the FAA.  The NLRA “secures to employees rights to organize unions and bargain collectively, but … says nothing about how judges and arbitrators must try legal disputes that leave the workplace and enter the courtroom or arbitral forum.”  Focusing specifically on the language of Section 7 of the NLRA, the Court found that “the term ‘other concerted activities’ should, like the terms that precede it, serve to protect things employees ‘just do’ for themselves in the course of exercising their right to free association in the workplace, rather than ‘the highly regulated, courtroom-bound ‘activities’ of class and joint litigation.’” (Emphasis added.)  Moreover, the Court noted that Congress has shown it knows exactly how to specify certain dispute resolution procedures, or to override the FAA; however, Congress has done nothing like that in the NLRA, which is further evidence that Section 7 does nothing to address the question of class and collective actions.

In short, the Court found that Congress intended Section 7 of the NLRA to grant employees certain rights to act together in the workplace – but did not intend to extend those rights to judicial or arbitral proceedings already governed by the FAA.  As such, the Court held that the NLRA does not “override” the FAA or render employee class action waivers in arbitration agreements illegal or unenforceable.  Justice Gorsuch concluded:

The policy may be debatable but the law is clear: Congress has instructed that arbitration agreements like those before us must be enforced as written.  While Congress is of course always free to amend this judgment, we see nothing suggesting it did so in the NLRA – much less that it manifested a clear intention to displace the Arbitration Act.  Because we can easily read [the FAA and the NLRA] to work in harmony, that is where our duty lies.

What Does This Mean for Employers? – The Pros and Cons of Class-Action Waivers

An employer that does not already utilize mandatory arbitration agreements with class and collective action waivers should consider whether implementing this type of agreement makes sense for its business.  While the Epic Systems decision made it clear that mandatory arbitration agreements with class and collective action waivers are enforceable (at least in the context of federal law), employers still must weigh various factors to decide if such agreements are right for them.

• From a cost standpoint, for most employers the ability to prevent class and collective actions has a lot of appeal.
  • For wage and hour claims, the purported class can be extensive, the time and cost to defend against such claims can be substantial, and if the employees are successful the employer is required to pay the employees’ reasonable attorneys’ fees.
  • And even if the underlying claims are not strong, employees may use the class or collective action procedure as a vehicle to increase costs and try to force settlement with the employer.
• However, the cost of defending dozens of individual arbitrations, each likely based on the same theory, can also be substantial.
  • The Supreme Court has held that employees may not be required to pay “prohibitive” costs in pursuing their federal employment rights, which often means that the employer will bear most of the burden of the arbitration costs, such as the filing fees, administrative fees, and the arbitrator’s fee. The employer would be required to pay these fees for each individual claim filed by an employee covered by a class or collective action waiver.
  • In addition, under the American Arbitration Association’s Employment Arbitration Rules and Mediation Procedures, with the exception of a $200 capped filing fee, the employer is responsible for all costs associated with an arbitration arising from an employer-promulgated arbitration plan.
• Employers should also consider the impact on employee morale of requiring arbitration agreements with class and collective action waivers. Many employee-side commentators have decried the Epic Systems decision as undermining employee rights.
• It should be noted that employers may face some uncertainty concerning state statutory and common law contract interpretations that may invalidate the terms of arbitration agreements, despite Epic Systems.
  • For example, several states have recently enacted limits on arbitration agreements that relate to sexual harassment claims, and some state courts have imposed exacting contractual wording requirements before enforcing arbitration clauses that waive the right to proceed with a court action.
  • Because of the uncertainty regarding whether a nonfederal law can override the FAA, employers should consider back-up contractual jury trial waivers in their arbitration agreements, if the governing state law permits pre-litigation jury trial waivers.
• It should also be noted that the Epic Systems decision does not preclude lawsuits challenging arbitration agreements on general contract grounds, such as fraud, duress, or unconscionability, so employers should continue to be diligent about the general enforceability of their arbitration agreements.
  • In particular, employers should ensure that their arbitration agreements provide for due process and are not subject to claims that the terms are unconscionable and therefore unenforceable.

If you have further questions regarding the topic of this article or need help implementing the right dispute resolution mechanism for your business, please contact Patrick Jones at pjones@fh2.com or (770) 399-9500.