When drafting non-compete agreements in states with increasing restrictions, I approach them with precision and separation of concerns. Many agreements fail because they try to do too much in one provision, or lump together non-compete obligations with other important protections like confidentiality or intellectual property. We separate agreements into distinct sections: Confidentiality obligations - protecting sensitive company information and trade secrets. Intellectual property - ensuring that anything created during employment remains the company's property. Non-solicitation - limiting outreach to clients, customers, or employees without restricting broader employment. Non-competition - narrowly tailored restrictions on working for competitors, respecting the state's enforceability limits. By keeping these obligations separate, each can stand on its own if a court decides to modify or "blue pencil" a portion. This structure preserves enforceable protections without risking the entire agreement being struck down. One technique that consistently helps maintain enforceability is narrow tailoring: limit the duration, geographic scope, and scope of restricted activities to what is reasonably necessary to protect legitimate business interests. This demonstrates both good faith and compliance with evolving state restrictions, while still giving the company real protection. The key is not to eliminate all protections, but to draft restrictive and protective covenants in a modular way that balances enforceability with the legal realities of the state.
At FasterDraft.com, we approach the drafting of non-compete agreements with a state-specific, compliance-first mindset, especially as more jurisdictions move to restrict or outright ban their enforceability. Rather than relying on one-size-fits-all templates, our platform tailors non-compete clauses based on the user's jurisdiction, seniority of the employee, and the legitimate business interests at stake—such as protection of trade secrets or client relationships. One technique that consistently helps maintain enforceability is narrowing the scope of the restriction to focus on non-solicitation and confidentiality, rather than blanket prohibitions on working for a competitor. In many states, particularly those tightening non-compete laws like California, Washington, or Minnesota, courts are far more likely to uphold narrowly tailored non-solicits or NDAs that protect specific interests, without overreaching into a worker's ability to earn a living.
When I'm drafting a non-compete agreement, I operate with one guiding principle: if it won't hold up in court, it's not worth the paper it's printed on. The days of cookie-cutter, one-size-fits-all restrictions are gone. With states and even cities placing tight limits, or outright bans, on these agreements, every single clause has to be narrowly tailored to protect a legitimate business interest. Anything less, and you're just inviting a legal challenge. The most critical factor is narrow tailoring. Courts are almost always going to strike down an overbroad non-compete. So, instead of trying to stop a software engineer from working in the entire tech industry, we'll define the specific competitors they can't join or the precise products they can't work on. The geographic scope has to be limited to the markets where the employee actually built relationships or accessed sensitive information. As for the time limit, the shorter the better, we typically aim for six to twelve months, and it's rare to see anything enforceable beyond two years. Timing and consideration are just as important. A non-compete that's part of the original job offer is far stronger than one we try to introduce later. That's because it avoids the argument that the employee was pressured into signing it once they were already on the payroll. If we do need to introduce it mid-employment, it has to be supported by valuable consideration, a real benefit like a pay raise, a promotion, or additional training. Without a clear benefit to the employee, the non-compete could be challenged as void. Finally, the definition of "competition" itself can change depending on where you are. Some jurisdictions will only enforce a non-compete if the employee starts their own competing business, while others will extend it to simply joining an established competitor. But the ultimate test remains the same everywhere: is the restriction the absolute minimum necessary to protect the business's legitimate interests? We're talking about things like trade secrets, confidential information, and customer goodwill. My goal isn't to draft something that just looks tough on paper. It's to build a clause that will withstand judicial scrutiny. In today's legal landscape, enforceability is all about careful tailoring, real consideration, and full compliance with the law. Anything else is just a waste of time and money.
I approach drafting non-compete agreements in states with increasing restrictions by focusing on specificity and reasonableness. Instead of broad, sweeping clauses, I tailor the agreement to the employee's role, defining precise activities, geographic boundaries, and time frames. One technique that has proven effective is emphasizing the protection of legitimate business interests, such as trade secrets or client relationships, rather than attempting to restrict general employment opportunities. For example, in a recent hire for a sales role, I limited the non-compete to six months and only within the specific regional territory the employee actively managed. By keeping the agreement narrowly targeted and tied to real business concerns, it becomes more likely to be enforceable while respecting state limitations. This approach not only protects the company but also demonstrates fairness to employees, which helps maintain trust and reduces the risk of disputes down the line.
In recent years, there has been a clear trend towards narrowing the scope of non-compete and other restrictive covenants in employment contracts, especially in jurisdictions that prioritize labor mobility, data protection, and start-up innovation. Many courts and regulatory authorities—particularly in the EU and some U.S. states—are increasingly scrutinizing broad, overly restrictive clauses, especially where the employer cannot demonstrate a legitimate business interest such as the protection of trade secrets or client relationships. For example, blanket non-compete clauses that apply to all employees, regardless of their access to sensitive information or strategic positions, are frequently deemed unenforceable. Similarly, non-solicitation clauses that attempt to prohibit normal client movement in competitive markets may be struck down if not appropriately limited in time, geography, and subject matter. Best Practices: Tailor the clause to the role: Ensure the restrictive covenant applies only to employees with genuine access to confidential business information or key client connections. Define legitimate interests: Clearly specify what is being protected—whether it's trade secrets, know-how, or goodwill—and how the clause is necessary for that protection. Limit duration and geography: Reasonable time limits (typically 6-12 months) and geographic scope will increase enforceability. Provide compensation when required: In many civil law jurisdictions (e.g., Germany, France), post-contractual non-compete clauses are only enforceable if the employer pays adequate compensation. Regularly review templates: Update contracts in line with the latest case law and regulatory guidance to avoid exposure. As regulatory and cultural attitudes evolve, particularly with the rise of remote work and cross-border teams, employers should resist a one-size-fits-all approach and focus on proportionate, justifiable restrictions that courts are more likely to uphold.
"The key to drafting non-compete agreements today isn't about how restrictive they can be, but how reasonable and fair they appear in the eyes of both the law and the employee." I approach non-compete agreements by focusing on narrow scope and clear intent. With states increasingly restricting overly broad clauses, the goal is to protect legitimate business interests such as safeguarding intellectual property and client relationships without overreaching. One effective technique is to tie the restriction directly to specific roles or access levels rather than applying blanket terms. This way, the agreement demonstrates fairness, increases enforceability, and builds employee trust while still shielding the company's competitive edge.
We focus on tailoring non-compete agreements to be narrowly scoped, specifying limited geographic regions, defined timeframes, and clearly identified roles or functions. This precision ensures the agreement addresses legitimate business interests, such as protection of trade secrets, without overreaching into general employment restrictions. One effective technique is incorporating a reasonable garden leave or non-solicitation clause as an alternative to broader restrictions. This allows the company to safeguard sensitive information while aligning with evolving state laws that often favor mobility and limit enforceability of traditional non-competes. By emphasizing specificity and proportionality, agreements remain legally defensible and enforceable while respecting the employee's right to pursue future opportunities.
Drafting non-compete agreements in restrictive jurisdictions requires a focus on precision, clarity, and proportionality. One effective technique is to narrowly tailor the agreement's scope, limiting it to specific roles, responsibilities, or regions directly tied to legitimate business interests. Avoiding broad or overly vague restrictions increases the likelihood that a court will uphold the agreement if challenged. Additionally, including well-defined time limits and reasonable geographic boundaries ensures the agreement aligns with state statutes and recent case law. Framing the restriction around protecting trade secrets or client relationships rather than general competition also strengthens enforceability. This approach balances protection of business interests with respect for employee mobility, providing legal defensibility while minimizing the risk of the agreement being deemed overreaching or invalid.