National Labor Relations Board Sets Limits on Severance Agreement Provisions

Last month, the National Labor Relations Board (NLRB) made a decision that changed the game regarding severance agreements. The ruling confirmed that overly broad confidentiality and non-disparagement clauses have a “clear chilling tendency” and that offering agreements with such provisions violates the law. However, the NLRB did not ban severance agreements outright, as long as they are narrowly tailored.

Severance agreements are still allowed, but with certain limitations as confirmed by the NLRB decision. Employers must take care to draft severance agreements that do not include overly broad confidentiality and non-disparagement provisions. These types of clauses create an environment in which employees may feel that they cannot speak out against their employer, even if they have legitimate concerns about the conditions of their employment or the workplace culture.

Overly broad confidentiality and non-disparagement provisions have a “clear chilling tendency.” The NLRB has found that confidentiality and non-disparagement provisions in severance agreements are unlawful when they prevent employees from exercising their rights under the National Labor Relations Act (NLRA). These provisions are overly restrictive and prevent employees from speaking out about legitimate concerns, which can be protected under the NLRA.

Employers should take caution when drafting severance agreements. According to the NLRB decision, offering agreements with overly broad confidentiality and non-disparagement provisions violates the law. This is because such provisions create a legally binding agreement that reinforces the employer’s efforts to restrict an employee’s protected rights.

The good news is that confidentiality and non-disparagement provisions in severance agreements are still permitted – as long as they are narrowly tailored. The NLRB decision reiterated the importance of narrowly tailoring such provisions, which should include a temporal limitation and should be conveyed as clearly as possible to avoid confusion.

According to the NLRB’s latest memo, employers should avoid using language that may interfere with their employees’ exercise of NLRA rights in any form of communication. This includes handbooks, policies, forms, and other less formal agreements such as severance agreements. It is suggested that supervisors should not discourage employees from discussing the terms of their severance agreements, nor should they retaliate against those who attempt to do so.

Employers need to be aware that the NLRB’s decision has a retroactive effect, i.e., it applies to both existing and new severance agreements. If they are found to have violated these provisions, employers may be subject to legal penalties or may be required to rewrite the provisions in question. Therefore, it is advisable for companies to review their existing severance agreements to ensure compliance with the new guidelines.

The importance of tailoring agreement language cannot be overstated. It is crucial for employers to carefully draft and tailor the language used in severance agreements. The NLRB decision serves as a reminder that boilerplate savings clauses or disclaimers will not necessarily cure overly broad provisions. Employers must reassure employees that they still have the ability to exercise their NLRA rights without fear of retaliation, censorship, or any other undue limitation.

The recent decision of the NLRB on severance agreements has established clear limits on confidentiality and non-disparagement provisions that are too broad. To avoid legal repercussions and difficulties, employers should meticulously draft the language used in severance agreements to restrict their employees’ NLRA rights as narrowly as possible. Employers should also avoid using language that could interfere with the exercise of NLRA rights in any other communications with their employees.

Explore more

Trend Analysis: African E-Commerce Strategic Expansion

The rapid reconfiguration of global trade corridors is currently forcing African retail giants to abandon their long-standing reliance on Western consumer bases in favor of a localized, intra-continental digital strategy. As traditional Western trade routes face increasing regulatory friction and the African Growth and Opportunity Act (AGOA) moves toward its 2028 expiration, the continent is witnessing a monumental pivot. Businesses

How AI Search Engines Are Reimagining Digital Marketing SEO

The era of digital discovery has transformed into a sophisticated dialogue where machines synthesize the entire web to deliver immediate answers rather than a static list of suggestions. The traditional search results page—the familiar list of ten blue links—is rapidly fading into the background of the digital landscape. With Google’s AI Overviews now serving over 2.5 billion users and platforms

Azure DevOps Faces Regional Instability and Access Issues

The Significance of Service Reliability in Modern Development The seamless operation of a cloud-based continuous integration and deployment pipeline remains the fundamental lifeblood of engineering teams who expect their tools to function with unwavering precision regardless of global traffic spikes or regional maintenance cycles. The modern software development lifecycle relies heavily on centralized platforms to manage everything from source code

Backend Developer Outlines 60-Day Pivot to DevOps and Cloud

The traditional landscape of software engineering has transformed so radically that the once-celebrated thrill of manual debugging is now frequently overshadowed by the efficiency of automated systems. For years, the allure of backend development sat squarely in the “struggle”—that deep, intellectual dive into complex algorithms and the satisfaction of unknotting a difficult bug. However, as prompt engineering begins to eclipse

Can AI Agents End War Room Fatigue in IT Operations?

Modern digital infrastructure relies on a delicate balance of thousands of microservices that can collapse into a chaotic mess of error codes at any given moment, leaving engineering teams to scramble through endless data logs. This relentless pressure on Site Reliability Engineering and DevOps teams to maintain 24/7 uptime has created a culture of perpetual “War Room” fatigue. When systems

Fill out the form below