SubscribeAdd blog to your RSS feed
FeedbackWe'd like to hear from you
- Can an Employer Back out of a Promise to Provide Advancement by Claiming That the Employee Committed Fraud?
- Suits by Suits Named to Blawg 100
- “Change of Control” Case Isn’t Governed By ERISA, Court Rules
- Court Nullifies CFO’s Employment Because of Prior Extortion Conviction
- The Yates Memo’s Illusory “Extraordinary Circumstances” Exception
- Kiss Your Retaliation Suit Hello: Company Faces Trial after Changing Explanation for Firing
- Federal Whistleblower Statutes Aren’t a Cure-All
- Hold on to Your (Top) Hat: ERISA Section 502(a)(3) May Be Used to Enforce the Terms of a “Top-Hat” Benefits Plan
- A Bitter Pill for Ex-Rite Aid GC: Delaware Court Finds His 2015 Suit for Indemnification Untimely
- A Funny Thing Happened to the Forum Selection Clause
- "Key Man" Provisions
- After-Acquired Evidence
- Age Discrimination
- Arbitration and ADR
- Breach of Contract
- Campaign Finance
- Change-in-Control Provisions
- Civil Litigation
- Data Security
- Dodd-Frank Act
- Equal Pay
- Executive Compensation
- Family Medical Leave
- Fiduciary Duties
- Fifth Amendment
- First Amendment
- Government Employers and Employees
- Indemnification and Advancement
- Intellectual Property
- Monthly Roundup
- Motions to Dismiss
- Noncompete Agreements
- Pregnancy Discrimination
- Preliminary Injunction
- Religious Discrimination
- Sarbanes-Oxley Act
- Section 1983
- Severance Agreements
- Social Media
- Statutes of limitations
- Summary Judgment
- Termination With or Without Cause
- The Basics
- The Inbox
- The Yates Memo
- Title VII
- Trade Secrets
- Vicarious Liability
- Wage and Hour
- White Collar Crime
- Workplace Conditions (Occupational Safety and Health)
- Wrongful Termination
Blogs We Like:
The AmLaw Daily
The BLT: The Blog of LegalTimes
Connecticut Employment Law Blog
The D&O Diary
Delaware Employment Law Blog
DeNovo: A Virginia Appellate Law Blog
The Employer Handbook
Executive Pay Matters
The Federal Criminal Appeals Blog
Grand Jury Target
Screw You Guys, I’m Going Home: What You Need To Know Before You Scream “I Quit,” Get Fired, Or Decide to Sue the Bastards
Trade Secrets & Noncompete Blog
Virginia Appellate News & Analysis
WSJ Law Blog
More on Covenants Not To Compete: A Proposed Massachusetts Law Gets A Big Endorsement
If you’re a regular Suits by Suits reader – and if you aren’t, why not? – you know that we think California’s first-in-the-nation law prohibiting essentially all covenants not to compete in employment contracts is going to be a major factor in future executive employment agreements and disputes across the country. Indeed, we’ve been keeping track as other states respond in various ways to the California law. (For details on the California law and its implications, see our prior piece, the “State by State Smackdown.”)
In our March 1 Inbox, we flagged a bill under consideration by the Massachusetts state legislature, House Bill No. 1715, which would establish that noncompete clauses of six months or less are presumptively reasonable, and clauses exceeding six months can be enforced if the court finds that the employee has (a) breached a fiduciary duty, (b) taken company property, or (c) earned at least $250,000 per year in annualized compensation.
The status quo in Massachusetts (and the majority of states) permits covenants not to compete, subject to a case-by-case judicial balancing test that considers the interests of the former employer against the hardships to the employee and the public.
It is tempting, then, to view House Bill No. 1715 as a “halfway point” between the existing law in Massachusetts and California’s outright ban. Under this view, the new proposed legislation would be seen, politically, as moving Massachusetts in the direction of California and away from upholding noncompete agreements. And indeed, thanks to some excellent reporting by Don Seiffert, an Associate Editor at the Boston Business Journal, we’ve discovered that’s precisely the view of Massachusetts Governor Deval Patrick (D).
Yesterday, in a question-and-answer session following his keynote address to the Massachusetts Technology Leadership Council, Gov. Patrick weighed in on the proposed measure, saying that there’s “a pretty compelling case” that the current Massachusetts law permitting covenants not to compete has led technology start-up companies to flee Massachusetts for California, knowing that the high-tech workforce would be legally available for new jobs. The implication is that by curtailing noncompete clauses, Massachusetts could staunch the flow of technology (and presumably, other) startups out-of-state and preserve those jobs.
Regardless as to whether this political argument has merit, we wish to caution proponents of Massachusetts House Bill No. 1715 that they may be misjudging the legal impact the proposed law ultimately might have. Although Gov. Patrick (and others) have focused on subsection (b) of the legislation that declares covenants not to compete of longer than six months “presumptively unreasonable,” in our view, subsection (a) is equally significant. That provision establishes that covenants not to compete of six months or less are presumptively reasonable.
This would be a significant change in the law. Under the present case-by-case regime in Massachusetts (and most of the rest of the country), time is just one factor the courts consider in determining whether a noncompete agreement is enforceable; other factors include the geographic area to which the employee is subject, as well as the scope of prohibited employment. Consider the following hypotheticals:
- Amalgamated Computers hires Jane Doe as a programmer, and, as a condition of her employment, requires that upon termination she not take any job (a) in “the computer industry,” (b) “anywhere in the United States,” (c) for a period of six months after her termination.
- Consolidated Computers hires John Doe as a programmer, and, as a condition of his employment, requires that upon termination he may not take any job (a) as a programmer, (b) for any company within 10 miles of Consolidated Computers, (c) for a period of two years after his termination.
Obviously, even though Consolidated’s noncompete clause runs for four times as long as Amalgamated’s, it is considerably less onerous – and, under the general case-by-case method, much more likely to be upheld by a court in Massachsuetts today. Under House Bill No. 1715 as currently written, that situation would be reversed. Because of subsection (a), the first covenant would be considered presumptively valid and enforceable. (Courts might still strike down something as broad as Amalgamated’s noncompete clause by holding that the employee successfully rebutted the presumption of validity; that’s a discussion for another day.)
In other words: House Bill No. 1715 shouldn’t really be viewed as the midpoint between the existing law and California’s ban; rather, it is an entirely different regime that replaces a more subjective, case-by-case analysis with a more objective, single-variable test. Such a move would increase the predictability of the law in Massachusetts with respect to noncompete agreements, but would not necessarily result in fewer or less onerous restrictions on employee mobility overall.
We’ll continue to monitor and comment.