The Ban Is Gone. The Risk Isn't.
For about eighteen months, small business owners had a straightforward, if unwelcome, story to tell themselves about noncompete agreements: the Federal Trade Commission had banned them nationwide, courts were fighting over whether that was legal, and eventually someone else would sort it out. That story ended in February 2026, when the FTC formally withdrew its Non-Compete Clause Rule from the Code of Federal Regulations, closing the book on the most sweeping labor-mobility regulation the agency has ever attempted.
If you run a business and breathed a sigh of relief when you heard "the noncompete ban is dead," pump the brakes. The FTC didn't walk away from noncompetes — it changed tactics. And the new tactic, case-by-case enforcement against specific companies, is arguably more dangerous for a small employer than a blanket rule ever was, because you can't tell in advance whether your agreement is the one that draws a warning letter.
This guide walks through what actually happened, what enforcement looks like now, which states still restrict or ban noncompetes on their own, and what a small business should actually put in an employment agreement in 2026.
What Happened to the FTC's Noncompete Rule
In April 2024, the FTC voted to ban nearly all noncompete agreements between employers and workers, arguing they suppressed wages and blocked competition. The rule was immediately challenged in federal court, and a Texas district court vacated it nationwide before it ever took effect. The FTC appealed.
Then the political winds shifted. A new administration took over the agency, and in September 2025 the FTC formally withdrew its appeals in the two pivotal cases challenging the rule, Ryan LLC v. FTC and Properties of the Villages v. FTC — effectively abandoning any path back to a blanket ban. On February 12, 2026, the agency made it official, publishing a final action in the Federal Register that removed the Non-Compete Clause Rule from the Code of Federal Regulations entirely.
Practically, that means the rule never took legal effect and now formally doesn't exist. The regulatory landscape has reverted to where it stood before 2024: noncompete enforceability is governed by state law, state by state, with no federal ceiling.
The New Playbook: Enforcement, Not Rulemaking
Here's the part small employers tend to miss. FTC Chairman Andrew Ferguson has been explicit that abandoning the rule does not mean abandoning the underlying policy goal. Instead of one regulation covering every employer, the agency is now using Section 5 of the FTC Act — its general authority to police "unfair methods of competition" — to go after specific companies and specific industries whose noncompete practices it considers overreaching.
The clearest example: on April 15, 2026, the FTC ordered Rollins, Inc., one of the largest pest-control companies in the country, to stop enforcing noncompete agreements against more than 18,000 employees. Rollins had required noncompetes company-wide, typically barring departing workers from the pest-control industry for two years within a 75-mile radius of any of its 700-plus locations — regardless of whether the employee was a technician, a sales rep, or an executive with access to trade secrets. The FTC found that blanket, one-size-fits-all approach violated Section 5.
Alongside the Rollins order, the FTC sent warning letters to 13 additional pest-control companies, telling them to review their own agreements for the same problem. That's the pattern to watch: the agency picks an industry, makes an example of the biggest or most visible offender, and then puts every other company in that industry on notice with a form warning letter. Pest control was the first target in 2026; there's no reason to assume it will be the last.
The common thread in every action so far is the same: broad, non-tailored restrictions applied to workers regardless of seniority, pay, or actual access to sensitive information. A blanket noncompete clause copied into every offer letter — for the warehouse associate and the VP of sales alike — is exactly the profile the FTC is targeting.
State Law Is Still the Main Event
Even with the federal rule gone, most of the legal risk around noncompetes for a small business was always going to come from state law, and 2026 is no exception. The patchwork looks like this:
- Outright bans. California, Minnesota, North Dakota, and Oklahoma prohibit noncompete agreements for employees in nearly all circumstances. California's ban is particularly aggressive — it reaches agreements signed anywhere, including ones a California-based employee signed for an out-of-state employer.
- Heavily restricted. Colorado allows noncompetes only to protect trade secrets or in connection with a business sale, and only above a compensation threshold — $130,014 as of January 1, 2026.
- Salary-threshold states. A growing group of states allow noncompetes only for workers earning above a set income floor: Washington ($126,858.83 for employees), Oregon ($119,541), Illinois ($75,000), and Tennessee ($70,000, effective July 1, 2026), among others. Below the threshold, the agreement is void regardless of what it says.
- Moving targets. Washington has already passed a follow-on law (SB 1155) that phases out the threshold approach entirely in favor of a near-total ban, effective June 30, 2027 — and it applies retroactively to agreements signed before that date.
The practical takeaway: if you have even one remote employee, or a multi-state footprint, "our standard employment agreement" is not a single document — it's a compliance question you need to answer state by state, and the answer changes yearly.
A Worked Example: The 12-Person Landscaping Company
Consider a hypothetical company much smaller than Rollins: a 12-employee landscaping business operating in one metro area. When the owner hired their first office manager five years ago, a lawyer friend supplied a "standard" employment agreement template that included a two-year, statewide noncompete clause. Since then, every new hire — from the crew lead pulling weeds to the part-time bookkeeper — has signed the identical document.
That's precisely the pattern the FTC flagged in Rollins, just at a fraction of the scale. None of the individual crew members has access to trade secrets or a proprietary customer list; the noncompete does nothing to protect the business and everything to make it harder for a laid-off worker to find the next job in town. If a competitor complains, or a departing employee's new employer pushes back, that boilerplate clause is now the visible symptom of exactly the "unfair method of competition" the agency is hunting for — regardless of whether the FTC ever specifically targets landscaping.
The fix costs almost nothing: keep a genuine noncompete (if the state allows it) for the general manager who sets pricing and holds the client list, and swap everyone else to a simple confidentiality agreement plus, if solicitation is a real concern, a narrow non-solicit for departing employees. The business loses no real protection and removes nearly all of the regulatory exposure.
Noncompete vs. Non-Solicit vs. NDA: Picking the Right Tool
Not every restrictive covenant is created equal, and conflating them is how "standard template" problems happen in the first place:
- A noncompete stops a former employee from working for a competitor, or starting one, for a set time and geography. It's the most restrictive tool, the most likely to draw regulatory or judicial scrutiny, and — outside a handful of genuinely sensitive roles — the least likely to survive a challenge in 2026.
- A non-solicitation agreement doesn't stop someone from taking a new job at all; it only stops them from actively poaching your clients or coworkers once they've left. Courts and regulators generally view this as a narrower, more reasonable restriction, which is why it tends to hold up better.
- A nondisclosure/confidentiality agreement doesn't restrict where someone works — it restricts what they can say or use once they get there. It protects your actual trade secrets and proprietary processes without touching the employee's ability to earn a living.
For the great majority of small-business roles, an NDA plus a non-solicit accomplishes almost everything a noncompete was meant to do, with a fraction of the legal exposure. Save the noncompete itself for the rare role where someone genuinely holds the keys to the business — and even then, keep the geography and duration as narrow as the actual risk justifies.
Frequently Asked Questions
Do I need to rip up every noncompete I've already signed? Not necessarily, but you should review them. Agreements signed under a state's existing law remain subject to that state's rules regardless of what happened at the federal level. The FTC's enforcement actions target companies that keep using overbroad agreements going forward, so an audit — not a bonfire — is the right first step.
What if my own employees signed noncompetes with a previous employer? That's the mirror image of this problem, and it matters when you're hiring, not just when you're the employer writing the agreement. Ask candidates about existing restrictive covenants before you extend an offer; inheriting a lawsuit from a new hire's old employer is a real and growing risk as more companies get aggressive about enforcement.
Does any of this apply to independent contractors? Some state salary thresholds explicitly cover contractors at a different (usually higher) income floor — Washington's rule is one example. Don't assume a 1099 relationship puts you outside the reach of state noncompete law.
What Small Employers Should Actually Do in 2026
1. Audit before you're the warning letter. Pull every current noncompete in your files and ask: does this employee actually have access to trade secrets, key customer relationships, or competitively sensitive information? If the honest answer is no, the agreement is legal exposure with no offsetting benefit — the exact profile the FTC has been targeting.
2. Tailor by role, not by template. A single noncompete clause pasted into every offer letter is the pattern regulators keep flagging. Reserve noncompetes for the handful of roles where they're genuinely justified (senior leadership, R&D, client-facing roles with proprietary relationships), and drop them everywhere else.
3. Lean on alternatives that are easier to enforce anyway. Non-solicitation agreements (barring a departing employee from poaching clients or coworkers) and confidentiality/NDA agreements protect most of what a noncompete was meant to protect, with far less legal risk and, in many states, far better odds of holding up in court. A clawback clause for paid training or certification costs can address the "we invested in this person" concern without restricting where they can work at all.
4. Check your state — and every state you have employees in — before you write anything. A noncompete that's standard in Texas may be void on arrival in Illinois and outright illegal in California. If you employ remote workers, this isn't optional homework.
5. Don't assume "the ban is dead" means "no risk." The FTC's own actions in 2026 show it's still actively hunting for noncompete cases — just one company and one industry at a time instead of one rule for everyone.
Keep Your Compliance Costs Where You Can See Them
Legal reviews, updated agreement templates, and multi-state compliance work all cost money — and if you're not tracking those costs against the departments or projects that generated them, they quietly erode your margins. Beancount.io provides plain-text accounting that gives you complete transparency into where every dollar of legal, HR, and compliance spend actually goes, with no black boxes and no vendor lock-in. Get started for free and see why developers and finance-minded owners are switching to plain-text accounting.