Same Non-Compete, Different State. Why the Outcome Changes Anyway

Two people sign the identical document, drafted by the same employer, printed from the same template, with the same twelve-month term and the same fifty-mile radius. One of them is bound. The other is not, and not because she hired a better attorney or negotiated harder, but because she worked out of an office in a state whose legislature decided the question years before she was hired. The clause did not change. The forum did. Understanding which of those two facts controls your situation is most of the work, and it is work you can start yourself.

The outright bans, and the near-bans that behave like them

A handful of states refuse to enforce employee non-competes as a matter of statute, with narrow carve-outs for the sale of a business or the dissolution of a partnership. California is the best known, and its rule has teeth beyond mere unenforceability, since the state has attached consequences to presenting such a clause at all. Oklahoma and North Dakota reached similar destinations by different routes. Minnesota joined more recently, with a date-of-signing cutoff that matters enormously: agreements executed before the effective date are generally untouched, which means a careful reader checks the signature date before anything else.

Blue pencil, reformation, or nothing at all

The sharper divide, and the one that decides most contested cases, is what a judge does after concluding that a clause sweeps too wide. Three approaches exist, and they produce wildly different results from identical language. A strict blue-pencil state lets the court strike offending words but not add or rewrite, so a covenant that reads as one unbroken sentence may fall entirely while a comma-separated list survives in part. A reformation state rewrites the term to whatever it considers reasonable, typically shortening the duration or shrinking the geography. An all-or-nothing state voids the whole covenant and leaves the employer with nothing.

This is why severability language repays close reading. Employers in reformation states often draft aggressively, because the downside of overreach is a judicial trim rather than total loss. The same aggressive draft, filed in a state that refuses to save overbroad restraints, hands the departing employee a complete defense. Look at whether your agreement lists restricted activities, territories, and time periods as discrete enumerated items or fuses them into a single clause, and note which state's law the document names, because those two features interact.

Wage floors, notice windows, and other procedural tripwires

Several states have moved the fight away from reasonableness and onto compliance. Washington, Colorado, Oregon, Illinois, Maine, and others condition enforceability on the employee earning above an inflation-adjusted salary threshold, measured at a specific moment that the statute defines. Others require advance notice: the agreement must be provided some fixed number of business days before the start date or before the offer is accepted, and a covenant sprung on a new hire during orientation may be void regardless of how modest its terms are. Massachusetts added a garden leave or other mutually agreed consideration requirement. These defects are objective and datable, which makes them the first thing worth reconstructing from your own emails and offer letter.

Why the choice-of-law clause may not get the last word

Most agreements name a governing state, often the employer's headquarters, and pair it with a forum selection clause sending disputes there. Neither is self-executing. Courts routinely decline to apply another state's law where doing so would offend a fundamental public policy of the state where the employee actually lived and worked, and several legislatures have written that refusal directly into statute, voiding out-of-state choice-of-law and venue provisions for resident employees. The practical consequence is a race: whoever files first, and where, shapes which body of law gets applied. That timing question is worth raising with counsel early rather than after a complaint lands.

The federal layer is unsettled, and that is a reason to check state law harder

The Federal Trade Commission is responsible for unfair methods of competition and has taken the position that employee non-competes fall within that remit, which produced a rulemaking that litigation has since kept in an uncertain posture. The sensible reading for anyone with a near-term decision is that state law remains the operative question, and that a federal change, whenever it settles, will arrive on top of protections many states already provide. Nothing about the federal picture makes the state analysis less useful.

Pull the signed copy, find the date, the state named, the salary at signing, and how the restricted activities are punctuated. Those four facts narrow the question considerably before the first consultation.