Employers Should Fix These 8 Common Problems With Restrictive Covenants
When an employee quits, the employer might dig through its files, dust off an old noncompete agreement, and see what rights (if any) it has under the agreement. Does this scenario sound familiar?
September 19, 2019 at 12:54 PM
5 minute read
When an employee quits, the employer might dig through its files, dust off an old noncompete agreement, and see what rights (if any) it has under the agreement. Does this scenario sound familiar?
Unfortunately, by the time an employee has quit, it's too late to go back and correct an outdated or insufficient agreement. So, we recommend that each fall, employers look through their existing noncompete agreements (and other restrictive covenants, such as nonsolicitation agreements), and fix these eight common problems:
Problem No. 1: Over the years, the employee signed multiple, conflicting agreements.
Fix: When an employee signs a new agreement, it should clearly state that it replaces all previous agreements.
Problem No. 2: The employee did not receive consideration—such as a new position, raise, bonus or promise of employment for a fixed time period—in exchange for signing the agreement.
Fix: If an employer realizes that an employee may not have received adequate consideration, the employer can pay a bonus in exchange for signing a new agreement. By timing its review of restrictive covenants in the fall, an employer can prepare for employees to sign updated agreements when they receive year-end bonuses or raises.
Problem No. 3: The agreement doesn't detail what the employee is restricted from doing.
Fix: We often see agreements that prohibit an employee from going to work for a "competitor." The problem with this language is that it inevitably leads to a dispute about whether the new and old employers really compete with each other.
If an employer is concerned about employees leaving for specific companies, those companies should be named in the agreement. The employer should add that the named companies are only examples, and that the employee is also prohibited from going to work for other companies doing business in a defined industry.
Problem No. 4: The employee's position, or the employer's business, has changed since the agreement was signed.
Fix: The employer should consider the restrictions in the original agreement, and confirm they still make sense. For example: since signing the agreement, does the employee still work in the same line of business, in the same geographic area? Does the employee still hold the same position, or have they changed responsibilities or gotten a promotion?
What about the employer—has it moved, closed locations or opened new locations that now need to be protected? Has the employer entered new lines of business, or is it preparing to do so? Does it face any new competitive threats?
Problem No. 5: The agreement limits an employee's ability to compete, but it's missing other restrictions.
Fix: Employers often refer to all types of restrictive covenants as noncompete agreements. But, a restriction on an employee's ability to compete may not go far enough, so the employer should consider adding other restrictions.
Nonsolicitation provisions can restrict employees from going after customers, other employees and referral sources. The employer can even require an employee to stay away from named customers and individuals, but should add that they are only examples.
Employers should also consider including confidentiality provisions, (which do not need to be supported by consideration).
Problem No. 6: The agreement doesn't define what it means for an employee to "solicit."
Fix: To avoid any doubt, the agreement should restrict an employee from attempting to do business with any customer, other employee or referral source—even if the other person contacts the employee first. The agreement should also restrict the employee from engaging in solicitation indirectly, through another person.
Problem No. 7: The agreement contains unenforceable restrictions.
Fix: Pennsylvania courts enforce restrictive covenants, to the extent they are necessary to protect a legitimate business interest. The employer should think about whether it could explain to a future judge why it really needs the restrictions to protect its business.
Does the employee's position even require restrictive covenants? For instance, a sandwich chain infamously required its kitchen workers to sign noncompete agreements.
If an agreement is needed, does it limit the employee's activities for six months or one year? Courts in Pennsylvania generally enforce these time periods with respect to covenants not to compete and solicit. Longer time periods have also been enforced, but they can be harder for employers to justify.
Does the employer need to limit the employee's activities worldwide or nationwide, or would a narrower geographic area be sufficient? An employer could consider restricting activities within particular states, counties or cities. Restrictions could also apply for a certain number of miles from locations of the employer and employee.
We recommend that employers include a "blue pencil" provision, stating that if a judge finds the restrictions are too broad, their scope should be limited so that they can be enforced.
Problem No. 8: The agreement doesn't contain a mandatory "forum selection" provision identifying where any disputes over the agreement must be litigated.
Fix: The employer should add this provision, and identify the state and federal court that are most convenient for the employer. For a court to enforce this provision, the selected location would need to be reasonably related to the employer or employee.
By fixing these common problems, employers can put themselves in the best position to enforce noncompete agreements and other restrictive covenants in the future.
Brian D. Lipkin and Carly Loomis-Gustafson are associates with the Pittsburgh law firm of Babst, Calland, Clements and Zomnir. Their practices focus on employment and labor law and commercial litigation. Contact them at [email protected] and [email protected].
This content has been archived. It is available through our partners, LexisNexis® and Bloomberg Law.
To view this content, please continue to their sites.
Not a Lexis Subscriber?
Subscribe Now
Not a Bloomberg Law Subscriber?
Subscribe Now
NOT FOR REPRINT
© 2024 ALM Global, LLC, All Rights Reserved. Request academic re-use from www.copyright.com. All other uses, submit a request to [email protected]. For more information visit Asset & Logo Licensing.
You Might Like
View AllPa. Federal District Courts Reach Full Complement Following Latest Confirmation
The Defense Bar Is Feeling the Strain: Busy Med Mal Trial Schedules Might Be Phila.'s 'New Normal'
7 minute readFederal Judge Allows Elderly Woman's Consumer Protection Suit to Proceed Against Citizens Bank
5 minute readJudge Leaves Statute of Limitations Question in Injury Crash Suit for a Jury
4 minute readTrending Stories
- 1Alston & Bird Matches Market Rate for Associate Bonuses
- 2Commentary: Freedom's Just Another Word
- 3Former McCarter & English Associate Fired Over 'Gangsta Rap' LinkedIn Post Sues Over Discrimination, Retaliation
- 4First-of-Its-Kind Parkinson’s Patch at Center of Fight Over FDA Approval of Generic Version
- 5The end of the 'Rust' criminal case against Alec Baldwin may unlock a civil lawsuit
Who Got The Work
Michael G. Bongiorno, Andrew Scott Dulberg and Elizabeth E. Driscoll from Wilmer Cutler Pickering Hale and Dorr have stepped in to represent Symbotic Inc., an A.I.-enabled technology platform that focuses on increasing supply chain efficiency, and other defendants in a pending shareholder derivative lawsuit. The case, filed Oct. 2 in Massachusetts District Court by the Brown Law Firm on behalf of Stephen Austen, accuses certain officers and directors of misleading investors in regard to Symbotic's potential for margin growth by failing to disclose that the company was not equipped to timely deploy its systems or manage expenses through project delays. The case, assigned to U.S. District Judge Nathaniel M. Gorton, is 1:24-cv-12522, Austen v. Cohen et al.
Who Got The Work
Edmund Polubinski and Marie Killmond of Davis Polk & Wardwell have entered appearances for data platform software development company MongoDB and other defendants in a pending shareholder derivative lawsuit. The action, filed Oct. 7 in New York Southern District Court by the Brown Law Firm, accuses the company's directors and/or officers of falsely expressing confidence in the company’s restructuring of its sales incentive plan and downplaying the severity of decreases in its upfront commitments. The case is 1:24-cv-07594, Roy v. Ittycheria et al.
Who Got The Work
Amy O. Bruchs and Kurt F. Ellison of Michael Best & Friedrich have entered appearances for Epic Systems Corp. in a pending employment discrimination lawsuit. The suit was filed Sept. 7 in Wisconsin Western District Court by Levine Eisberner LLC and Siri & Glimstad on behalf of a project manager who claims that he was wrongfully terminated after applying for a religious exemption to the defendant's COVID-19 vaccine mandate. The case, assigned to U.S. Magistrate Judge Anita Marie Boor, is 3:24-cv-00630, Secker, Nathan v. Epic Systems Corporation.
Who Got The Work
David X. Sullivan, Thomas J. Finn and Gregory A. Hall from McCarter & English have entered appearances for Sunrun Installation Services in a pending civil rights lawsuit. The complaint was filed Sept. 4 in Connecticut District Court by attorney Robert M. Berke on behalf of former employee George Edward Steins, who was arrested and charged with employing an unregistered home improvement salesperson. The complaint alleges that had Sunrun informed the Connecticut Department of Consumer Protection that the plaintiff's employment had ended in 2017 and that he no longer held Sunrun's home improvement contractor license, he would not have been hit with charges, which were dismissed in May 2024. The case, assigned to U.S. District Judge Jeffrey A. Meyer, is 3:24-cv-01423, Steins v. Sunrun, Inc. et al.
Who Got The Work
Greenberg Traurig shareholder Joshua L. Raskin has entered an appearance for boohoo.com UK Ltd. in a pending patent infringement lawsuit. The suit, filed Sept. 3 in Texas Eastern District Court by Rozier Hardt McDonough on behalf of Alto Dynamics, asserts five patents related to an online shopping platform. The case, assigned to U.S. District Judge Rodney Gilstrap, is 2:24-cv-00719, Alto Dynamics, LLC v. boohoo.com UK Limited.
Featured Firms
Law Offices of Gary Martin Hays & Associates, P.C.
(470) 294-1674
Law Offices of Mark E. Salomone
(857) 444-6468
Smith & Hassler
(713) 739-1250