Are non-compete clauses enforceable?

What a non-compete clause actually restricts

A non-compete clause (also called a covenant not to compete) is a restrictive covenant in which an employee, independent contractor, or the seller of a business agrees not to work for a competitor, launch a competing venture, or serve competing customers for a defined period after the relationship ends. Its purpose is to protect something the business can legitimately protect, such as trade secrets, confidential strategy, or customer goodwill, rather than simply to shield the employer from ordinary competition.

It helps to keep the non-compete separate from its cousins in the restrictive covenant family:

• A non-solicitation clause bars a departing worker from poaching customers or employees, but usually lets them work for a competitor.
• A confidentiality clause or NDA protects specific information, without restricting where the person can work.
• A non-compete is the broadest of the three because it can keep someone out of an entire line of work for a time, which is exactly why courts scrutinize it most closely.

Because a non-compete restricts a person’s ability to earn a living, courts treat it as a disfavored restraint on trade and read it narrowly. That framing shapes almost every enforceability question that follows.

Are non-compete clauses legal? It depends on the state

Non-competes are governed almost entirely by state law, not by one national statute, so their legality ranges from “generally enforceable if reasonable” to “void and unenforceable.” A clause that a court in one state would enforce with minor edits can be thrown out entirely a state line away.

At one end, several states broadly refuse to enforce employee non-competes. California voids most of them by statute, and North Dakota and Oklahoma take a similarly hostile view; Minnesota banned new employee non-competes entered into on or after July 1, 2023. At the other end, most states will enforce a non-compete that meets a reasonableness test.

In between sits a growing group of states that allow non-competes but restrict them for lower-paid workers or add procedural requirements. States including Illinois, Washington, Oregon, Colorado, Massachusetts, and Virginia have adopted wage thresholds, advance-notice rules, or garden-leave style requirements, and the specific dollar figures and conditions change frequently. The practical lesson is that “is this non-compete legal” cannot be answered without first identifying the governing state and the worker’s role and pay.

What makes a non-compete enforceable

In states that permit non-competes, courts apply a reasonableness test that asks whether the restriction is no broader than necessary to protect a legitimate business interest, and whether it is fair to the worker and the public. A clause fails when it reaches further than the interest it is meant to guard.

Courts typically weigh the following factors:

• Legitimate business interest: trade secrets, confidential information, established customer relationships, goodwill, or specialized training, not a general wish to avoid competition.
• Reasonable duration: many enforceable clauses run from six months to two years, though what counts as reasonable varies by state, industry, and role.
• Reasonable geographic scope: the restricted territory should track where the employer actually competes, not the whole country when the business is local.
• Reasonable scope of activity: the clause should bar genuinely competitive roles, not employment “in any capacity” with any competitor.
• Adequate consideration: the worker must receive something of value, such as a job offer, a promotion, or pay, and some states require additional consideration when an existing employee signs.
• Fairness: the restriction must not impose undue hardship on the worker or harm the public, for example by creating a shortage of a needed service.

One more variable decides what happens when a clause is too broad. Some states follow a “blue pencil” or reformation approach and will narrow an overbroad term to make it enforceable, while others void the entire clause if any part reaches too far. Drafting to the strictest likely forum, rather than assuming a court will fix your language, is the safer path.

The FTC non-compete rule and the federal picture

For decades, non-competes have been a state-law question, and that remains the reality on the ground today. In 2024 the Federal Trade Commission issued a rule intended to ban most non-competes nationwide, but a federal court set the rule aside before it took effect, and its ultimate fate has continued through appeal and remains uncertain.

Other federal actors have shown interest as well, including labor regulators who have questioned whether some non-competes chill protected activity, but none of this has produced a settled national ban. Employers and reviewers should not build a strategy around the assumption that a federal rule has swept non-competes away. The dependable move is to comply with the law of the state where the worker is based, treat any federal development as a reason to revisit clauses rather than a final answer, and confirm the current status with counsel before relying on it.

Common mistakes and a pre-signing checklist

Most unenforceable non-competes fail for predictable reasons: they reach too far in time or territory, they restrict any job rather than competitive ones, they protect no real interest beyond avoiding competition, or they ignore the wage thresholds and notice rules of the governing state. Using a single template across every state is its own common error, because a clause valid in one jurisdiction can be void next door.

Before you sign or issue a non-compete, run through this checklist:

• Confirm the governing state and whether that state enforces, limits, or bans employee non-competes.
• Check any wage threshold, notice period, or garden-leave requirement that applies to the worker.
• Identify the specific legitimate business interest the clause protects, and confirm it is real.
• Test the duration, geography, and scope of activity against “no broader than necessary.”
• Verify that the worker receives adequate consideration for the promise.
• Ask whether the state uses reformation or all-or-nothing enforcement, and draft to the stricter standard.
• Read the interplay with any non-solicitation, confidentiality, and choice-of-law provisions.
• For anything high stakes, cross-border, or unusual, have counsel review the clause before signing.

Working through these points before signature is far cheaper than litigating enforceability after a dispute, and it protects both sides from an agreement that a court may simply refuse to apply.

Managing non-competes across your contract portfolio

Enforceability is not decided once at signing; it lives on across every agreement that contains a restrictive covenant, which is why disciplined contract management matters. When your non-competes are scattered across offer letters, consulting agreements, and acquisition documents, it is hard to answer basic questions such as which clauses are overbroad for their governing state or which come up for renewal. A central repository, a clause library, and consistent playbooks turn that scramble into a controlled process.

This is where a CLM platform with an AI copilot helps a reviewer without replacing counsel. PactAI can spot non-compete and other restrictive covenant clauses across a contract, extract their duration and geographic scope, and score the associated risk so a human sees the outliers first; the platform’s repository and playbooks then let a legal team apply a consistent standard and flag clauses that fall outside it. PactAI prepares the analysis, but the human, and where the stakes call for it a qualified attorney, makes the enforceability call.

General legal information, not legal advice.