Key takeaways
- There is no federal non-compete ban: a court set aside the FTC's rule in August 2024, and in September 2025 the FTC voted to drop its appeals[1][2].
- State law decides. Some states, such as California and Minnesota, void most employee non-competes; others enforce narrow ones or set pay thresholds[3].
- For technicians, customer non-solicitation, confidentiality rules and retention pay usually protect more and cause fewer legal fights than a broad non-compete.
- Trades hiring is tight, so any restriction that scares off candidates has a real cost; weigh it against what you are actually protecting.
- This is general information, not legal advice. Have an employment lawyer in each state draft or review your agreements.
Where the federal rule stands
In April 2024 the Federal Trade Commission issued a rule that would have banned most non-compete clauses nationwide. The FTC estimated that about 30 million workers, nearly one in five Americans, were subject to a non-compete[1]. The rule never took effect. A federal district court in Texas set it aside and blocked enforcement on August 20, 2024[1].
On September 5, 2025, the Commission voted 3-1 to dismiss its appeals in the Fifth and Eleventh Circuits and accept the court's vacatur[2]. For a home service business, the practical result is simple: no federal rule bans or allows your non-competes. State law, and the specific wording of your agreement, decide whether a court will enforce it.
State law decides, and it varies widely
States fall roughly into four groups. Check which group each of your locations is in before you put a non-compete in front of anyone:
| Approach | What it means for a tech agreement |
|---|---|
| Broad ban on employee non-competes | California and Minnesota void most employee non-competes; a few other states, such as North Dakota and Oklahoma, have long-standing restrictions too |
| Pay thresholds | Several states allow non-competes only for employees earning above a set income level, often adjusted yearly, which excludes many techs |
| Notice and procedure rules | Some states require advance notice, separate consideration or limits on length before a non-compete is valid |
| Reasonableness test | Courts enforce restrictions that are narrow in time, geography and scope and that protect a legitimate business interest |
Minnesota is a clear example of a ban. Its statute says any covenant not to compete in an employment agreement is void and unenforceable, while excluding nondisclosure agreements and nonsolicitation agreements from that definition and keeping an exception for the sale of a business[3]. That pattern, ban the non-compete but allow narrower tools, is worth copying even where non-competes are legal.
Why broad non-competes are a poor fit for technicians
Most techs do not hold trade secrets in the legal sense. They hold skills, a license and relationships with some customers. Courts in states that apply a reasonableness test often refuse to stop someone from earning a living in their trade, especially for hourly workers. Even an enforceable agreement is expensive to enforce: you pay a lawyer to sue a former employee who may have little to collect.
There is also a recruiting cost. The trades need people. About 72,700 openings for electricians[4] and 40,600 for HVAC mechanics and installers[5] are projected each year over the decade to 2035, with roughly 12,000 a year for roofers[6] and 13,700 for pest control workers[7]. US construction job openings reached 289,000 in September 2026[8]. Candidates compare offers, and a broad non-compete is a reason to sign elsewhere.
Source: U.S. Bureau of Labor Statistics, 2025-2035[4]
Show the data
| Item | Value |
|---|---|
| Electricians | 72,700 openings |
| HVAC mechanics | 40,600 openings |
| Pest control workers | 13,700 openings |
| Roofers | 12,000 openings |
What you are really trying to protect
Before choosing a tool, name the risk. For most service companies it is one of four things:
- Customer lists and maintenance agreement members being called by a departing tech or sales advisor.
- Pricing books, margins and vendor terms reaching a competitor.
- Several key people leaving together for a competitor or to start their own shop.
- Training investment walking out the door, such as paid certification or manufacturer training.
Each risk has a narrower tool that is more likely to hold up and less likely to deter hiring.
Alternatives that protect the business
| Tool | Protects against | Notes |
|---|---|---|
| Customer non-solicitation | Former employee soliciting customers they served | Limit to customers the person actually dealt with, for a defined period; enforceability still varies by state |
| Confidentiality agreement | Use of price books, customer data, vendor terms | Define confidential information specifically; pair with access controls |
| Employee non-solicitation | Recruiting coworkers away | Narrow scope; agreements between companies not to hire each other's staff raise antitrust risk |
| Retention or stay bonus | Leaving after costly training | Paid at milestones; no legal fight needed |
| Training repayment agreement | Leaving right after paid certification | Some states restrict these; keep amounts tied to real costs and prorate them |
| Return-of-property rules | Tablets, tools, customer files leaving with the person | Exit checklist and device access shut-off on the last day |
Data protection is the most practical step. If every customer record lives in your field service software and access ends at the exit interview, a departing tech takes far less with them than any contract could stop.
Drafting tips if you still use restrictions
Where state law allows them and you decide a restriction is worth it, keep it narrow and specific:
- Limit it to roles with real access to customer relationships or confidential pricing, such as service managers and comfort advisors, not every apprentice.
- Keep the time short and the geography tied to where the person actually worked.
- Give something for it: a signing bonus, a raise or a promotion, especially when adding restrictions to current employees.
- Add a clause choosing the state law and courts where the employee works; many states will not apply another state's law to their residents anyway.
- Review agreements whenever you open a location in a new state.
Put the policy and the agreements together in your employee handbook process, so new hires see them before their first day, not after.
If you already have non-competes on file
Many companies have years of signed agreements from an old template. Do not assume they work, and do not assume they are harmless. In a state that voids non-competes, an employer that keeps demanding them can face claims of its own, and some states require employers to tell current and former employees that unlawful clauses are void.
Ask your lawyer to sort existing agreements into three piles: unenforceable and to be withdrawn, enforceable but broader than needed and to be narrowed at the next review, and appropriate as written. Replace the first two piles with the narrower tools above, and give employees a clear written notice of what changed. Most techs will read it as good news, which is a small retention win in itself.
When a tech gives notice: an exit routine
The days between notice and departure are when customer data and goodwill are most at risk. A calm, consistent routine protects both without treating the person as a suspect:
Thank them and agree the last day
Decide whether they finish their notice period on the schedule or are paid out. People heading to a direct competitor are often paid out and released early.
Reassign their customers
Move open jobs, callbacks and maintenance visits to another tech, and have the service manager call key accounts personally.
Collect property
Truck, keys, fuel card, tablet, meters, uniforms and any paper customer files, checked against an exit list.
Close access
Field service software, email, shared drives, supplier accounts and the phone system, all on the last day.
Remind, do not threaten
Give a copy of any confidentiality or non-solicitation agreement they signed, with a neutral note about what it covers.
Hold an exit interview
Ask why they are leaving and what would have kept them. Track the answers over time; they are your best retention data.
Talking about restrictions with candidates
Be upfront. If an agreement is part of the job, show it before the offer is accepted, explain in plain words what it covers and why, and point out what it does not cover. A candidate who learns about a restriction on day one, buried in a stack of onboarding forms, is more likely to resent it and more likely to leave. A short, fair agreement explained honestly rarely costs you a good hire.
Example: replacing a non-compete with retention tools
Example. A fictional HVAC company in two states had every employee sign a two-year, 50-mile non-compete. Recruiters reported candidates walking away at the offer stage. With its lawyer, the company replaced the non-compete for techs with a customer non-solicitation clause limited to customers each tech served in their last year, a confidentiality agreement covering its price book and membership list, and a retention bonus paid after 12 and 24 months. Service managers and sales advisors kept narrow restrictions where state law allowed them.
The company also tightened access: membership lists stay in the field service software, and accounts close on the last day. In the following hiring season, fewer candidates declined offers, and the company spent nothing on enforcement.
Bring it to your weekly leadership meeting
Retention is the real goal. Use the time you would spend drafting restrictions on the things techs say make them stay: fair and predictable pay, a clear path to the next level, decent trucks and tools, and managers who listen. Our guides to running weekly meetings and driver safety cover two of the day-to-day signals techs notice.
A useful test: if your best tech handed in notice tomorrow, would a contract clause or the way you run the company be what changed their mind? For most shops it is the second. Spend the effort there first, then use narrow agreements to cover what remains.
Frequently asked questions
Is the FTC non-compete ban in effect?
No. A federal court set the rule aside in August 2024[1], and the FTC voted in September 2025 to dismiss its appeals and accept that ruling[2].
Can I make an HVAC tech sign a non-compete?
It depends on your state. Some states void most employee non-competes, others enforce narrow ones or only above a pay threshold. Ask an employment lawyer in your state.
Is a non-solicitation agreement the same as a non-compete?
No. A non-solicitation clause stops a former employee from soliciting your customers or staff; it does not stop them working in the trade. Minnesota, for example, bans non-competes but excludes nonsolicitation agreements from that ban[3].
What is the best way to keep techs from leaving with customers?
Keep customer data in your systems with access that ends at exit, use a narrow customer non-solicitation clause where enforceable, and give techs reasons to stay.
References
Federal Trade Commission (2024). FTC Announces Rule Banning Noncompetes (opens in a new tab) ↑
Federal Trade Commission (2025). Federal Trade Commission Files to Accede to Vacatur of Non-Compete Clause Rule (opens in a new tab) ↑
Minnesota Office of the Revisor of Statutes (2026). Minnesota Statutes 181.988: Covenants not to compete void in employment agreements (opens in a new tab) ↑
U.S. Bureau of Labor Statistics (2025-2035). Electricians: Occupational Outlook Handbook (opens in a new tab) ↑
U.S. Bureau of Labor Statistics (2025-2035). Heating, Air Conditioning, and Refrigeration Mechanics and Installers: Occupational Outlook Handbook (opens in a new tab) ↑
U.S. Bureau of Labor Statistics (2025-2035). Roofers: Occupational Outlook Handbook (opens in a new tab) ↑
U.S. Bureau of Labor Statistics (2025-2035). Pest Control Workers: Occupational Outlook Handbook (opens in a new tab) ↑
U.S. Bureau of Labor Statistics (2026). Job Openings and Labor Turnover Survey, series JTU230000000000000JOL (Construction, job openings, not seasonally adjusted) (opens in a new tab) ↑