Skip to main content

FTC Non-Compete Rule Withdrawn: How Employers Should Adapt to the State-by-State Patchwork in 2026

· 12 min read
Mike Thrift
Mike Thrift
Marketing Manager

For about eighteen months, employers in every state braced for the same news: a near-total federal ban on post-employment non-compete agreements, sweeping aside roughly thirty million existing contracts and rewriting how American workforces are bound to their employers. Then, on February 12, 2026, the Federal Trade Commission quietly removed that rule from the Code of Federal Regulations. There is no longer a federal non-compete ban — but if you take that to mean your old templates are safe again, you are about to make an expensive mistake.

The FTC's 2024 rule is gone. The federal scrutiny is not. And while Washington stepped back, the states sprinted forward — passing wage thresholds, outright bans, choice-of-law overrides, and notice requirements that turn a single national template into a compliance hazard the moment you hire someone across a state line. This guide walks through what actually happened, where state law stands in May 2026, and the practical steps every employer with restrictive covenants should be taking this quarter.

2026-05-09-ftc-non-compete-rule-withdrawn-state-by-state-patchwork-employer-compliance-guide

What Happened to the Federal Ban

The original FTC Non-Compete Clause Rule, finalized in April 2024, would have voided nearly every existing post-employment non-compete in the country and prohibited new ones for almost all workers. Within months, federal courts in Texas and Florida enjoined the rule. In September 2025, after a change in administration, the FTC dismissed its appeals and accepted the vacatur. The formal removal from the federal regulations followed in February 2026.

Crucially, the FTC did not concede that aggressive non-competes are lawful. Chairman Andrew Ferguson made the agency's new posture explicit in a September 2025 statement: the FTC would pursue case-by-case enforcement against unreasonable restrictive covenants under Section 5 of the FTC Act, applying a common-law-style reasonableness test. The standard the FTC now uses is whether a restriction is "no greater than necessary to protect the employer's legitimate interests, and balances those interests against the hardship inflicted on the employee and any potential injury to the public."

That approach is no longer theoretical. In April 2026, the FTC entered a consent order against Rollins, Inc., the parent of Orkin and other pest-control brands, after the agency concluded the company required the vast majority of its 18,000-person workforce to sign two-year, 75-mile non-competes regardless of role or compensation. Alongside the consent order, the agency sent warning letters to thirteen additional pest-control companies. Less than a month later, a similar letter went to Mortgage Connect over broad covenants applied across employee tiers.

The pattern is clear. The FTC will not ban non-competes by rule, but it will go after employers that:

  • Apply non-competes to large fractions of a workforce regardless of role
  • Bind low-wage workers, hourly workers, or workers with no access to confidential information
  • Use unusually long durations, broad geographies, or sweeping industry definitions
  • Operate in industries with low labor mobility, where covenants compound to suppress wages

For most employers, that is a narrower compliance question than the now-defunct ban — but it is still a real one.

The State Map in May 2026

State law has always controlled non-compete enforceability in practice, and the states have not waited for federal clarity. Here is the lay of the land most multi-state employers need to internalize.

Near-Total Bans

Four states make virtually all post-employment non-competes unenforceable in standard employment relationships:

  • California — the longest-standing ban, recently strengthened to void out-of-state non-competes applied to California workers, regardless of choice-of-law clauses.
  • Minnesota — agreements entered on or after July 1, 2023 are unenforceable for nearly all workers.
  • North Dakota — broad statutory prohibition with narrow exceptions tied to sale of business or partnership dissolution.
  • Oklahoma — non-competes are barred, though limited customer non-solicitation is permitted.

A fifth state, Washington, will join this group on June 30, 2027, when its current wage-threshold rules give way to a near-total ban. Most multi-state employers should already be drafting toward the new Washington rule rather than the soon-to-expire one.

Wage-Threshold States

A growing number of states allow non-competes only for workers above a defined compensation floor, indexed annually:

  • Illinois — non-competes prohibited for employees earning $75,000 or less, with statutory penalties up to $5,000 per violation (and $10,000 for repeat violations within five years). A January 1, 2026 amendment also makes it against public policy for any employment-condition agreement to bar protected concerted activity, shorten statutes of limitation, or impose out-of-state law or venue on Illinois employees' claims.
  • Colorado — for 2026, only "highly compensated" employees earning above $130,014 may be bound by a non-compete; customer non-solicitation requires earnings of at least 60 percent of that figure ($78,008.40). Detailed pre-acceptance notice is required.
  • Massachusetts, Maine, New Hampshire, Rhode Island, Virginia, Maryland, Nevada, Oregon, and Washington — each set their own wage floors, advance-notice rules, garden-leave or consideration requirements, and duration caps.

Presumption-of-Enforceability States

A smaller group has gone the other direction, codifying that reasonable non-competes are presumptively enforceable for defined durations:

  • Florida — recent legislation creates a presumption of enforceability for covered agreements within statutory parameters.
  • Kansas — similar presumption framework.

For employers with operations in these states, the question is less "is this enforceable" and more "have we documented our legitimate business interest in case it is challenged."

Everywhere Else

Most remaining states still apply the common-law reasonableness test: a non-compete is enforceable only if it protects a legitimate business interest, is reasonable in time, geography, and scope, and is not contrary to public policy. Many of those states allow courts to "blue-pencil" or modify overbroad agreements; a few, including Virginia and Wisconsin, will not — overbreadth voids the entire covenant.

Why a Single National Template No Longer Works

If your employment agreements were drafted before 2023 and have not been touched since, three problems are quietly compounding.

Choice-of-law clauses are losing their grip. California, Washington, and several other states explicitly void out-of-state choice-of-law provisions in employment contracts. A Delaware-law non-compete signed by a California-based remote employee is unenforceable against that employee, period — and may also expose the employer to statutory penalties.

Wage thresholds move every year. Colorado's $130,014 figure is up sharply from prior years; Illinois indexes its $75,000 floor; Washington and Oregon do the same. An agreement that complied at signing may quietly fall out of compliance if the employee's pay no longer crosses the new threshold.

Notice and consideration rules vary by state. Several states require non-competes to be presented before a job offer is accepted, signed at least a defined number of days before the start date, or supported by additional consideration beyond continued employment. A signature on day one is not always enough.

The cost of getting this wrong is no longer just an unenforceable covenant. State statutes increasingly award attorneys' fees to prevailing employees, impose civil penalties on the employer, and let state attorneys general bring enforcement actions independently of the affected worker.

Five Things Every Employer Should Do This Quarter

The good news is that the work to come into compliance with the 2026 landscape is finite and largely a one-time exercise, with smaller annual updates.

1. Inventory Every Restrictive Covenant

Pull every active employment agreement, offer letter, equity grant, severance agreement, and contractor contract that contains any of the following: non-compete, non-solicitation of customers, non-solicitation of employees, non-disclosure, assignment of inventions, or "garden leave" clauses. Tag each one with the employee's primary work state, role, and current compensation. Most companies discover they have three to seven different templates in active use, often inherited from acquisitions or old counsel.

2. Right-Size to Roles

For each tagged agreement, ask whether a non-compete is genuinely necessary or whether a narrower instrument would protect the same legitimate interest:

  • A confidentiality agreement or NDA can protect trade secrets and confidential information without restricting where the worker can earn a living.
  • A non-solicitation clause (typically six months to two years) can preserve customer relationships and prevent recruiting raids on remaining staff.
  • A garden-leave clause keeps a senior employee on payroll during a notice period (commonly three to six months), giving the company time to transition relationships without forcing the employee into unpaid unemployment.
  • Trade secret protections under the federal Defend Trade Secrets Act and state UTSA equivalents already cover most of what employers actually need to protect.

The FTC's stated reasonableness test, the patchwork of state statutes, and the trend in court decisions all push in the same direction: the non-compete should be reserved for a narrow set of senior, highly compensated, or genuinely sensitive roles, and tailored to the specific competitive harm at issue.

3. Build a State-Specific Template Library

Replace the single national template with a small set of state-tailored variants. At minimum, most multi-state employers will need:

  • A "no restriction" version for California, Minnesota, North Dakota, and Oklahoma
  • A wage-threshold version for Illinois, Colorado, Washington, Oregon, Massachusetts, and similar states
  • A presumption-of-enforceability version for Florida and Kansas
  • A common-law-reasonableness version for the remaining states

Each version should include the state-specific notice language, consideration recitals, and choice-of-law and venue provisions that the relevant state will respect.

4. Document the Legitimate Business Interest

For any role that will continue to carry a non-compete, build a short file memo explaining why a less-restrictive alternative was inadequate. The memo doesn't need to be long — a few paragraphs identifying the trade secrets, customer relationships, or specialized training at issue, and explaining why an NDA and non-solicit alone do not protect them. This is the single most powerful document you can hand to a court or to FTC investigators if a covenant is later challenged. The memo also forces internal honesty: if you cannot articulate the legitimate interest, you probably should not be using a non-compete in that role.

5. Update Onboarding and Offboarding Workflows

Many of the new state requirements are procedural rather than substantive. They are easy to satisfy at hiring time and impossible to fix retroactively:

  • Provide non-competes with the offer letter, not on day one
  • Honor any state-mandated review periods (commonly seven to fourteen days)
  • Issue separate consideration where state law requires it
  • At separation, evaluate whether the post-employment restriction is being enforced; some states require employers to formally affirm or waive the covenant in writing

Build these checkpoints into your applicant tracking system and your offboarding checklist so they happen automatically, not when someone remembers.

Where Bookkeeping Quietly Matters

Restrictive covenants don't feel like an accounting topic, until something goes wrong. Then they generate real, traceable financial activity that needs to be on the books cleanly:

  • Garden-leave payroll during a notice period — distinct from severance, often subject to different tax treatment.
  • Severance payments tied to non-compete consideration, which some states require to enforce a post-employment restriction.
  • Legal fees for litigation or arbitration when a former employee or a competitor disputes a covenant.
  • Settlement payments and damages in either direction, plus statutory penalties in states like Illinois.
  • Recruitment and retraining costs when a covenant fails and a critical employee walks to a competitor.

Tracking these as discrete accounts — not buried inside generic "legal" or "payroll" lines — makes your annual review of restrictive-covenant policy a real cost-benefit exercise rather than a guess. It also matters at audit time, because non-compete-related severance and garden leave often have specific disclosure or tax-character implications that your accountant will want to see broken out.

A Word on Existing Agreements

A common question is what to do about non-competes already on file. The short answer is that the federal rule's withdrawal does not retroactively cure agreements that were never enforceable under state law. A 2019 non-compete signed by a $40,000-per-year customer-service representative in Illinois is unenforceable today regardless of what the FTC did. Quietly retiring agreements that were always weak is usually preferable to discovering their weakness mid-litigation.

For agreements that may still be enforceable, consider whether to formally release lower-priority workers (a goodwill move that often comes up at separation negotiations anyway) and reserve enforcement effort for the senior or genuinely sensitive cases where the legitimate interest is documented and clear.

Keep Your Employment Records Audit-Ready

Restrictive covenants generate financial events — garden-leave payroll, severance-for-consideration payments, legal fees, settlements, and recruitment costs after a failed covenant — that often surface years after the agreement was signed. Beancount.io provides plain-text accounting that's transparent, version-controlled, and easy to keep alongside the rest of your business records, so when an old non-compete becomes a live dispute, the financial trail behind it is still readable and reproducible. Get started for free and keep your books in a format that survives every change in legal counsel, payroll system, and federal regulation.