Protecting a Customer List Without a Non-Compete

Why this matters

The thing a shop is actually afraid of when a tech leaves is not that they will work in the trade. It is that two hundred maintenance agreements will follow them across town. Owners reach for a non-compete because it is the document they have heard of, and it is the wrong tool for that fear: it tries to restrain the person, which is what courts resist, instead of protecting the relationships and the records, which is what courts protect. The tools that actually work are narrower, cheaper and far more likely to hold, and the sharpest one is not a document at all.

This is orientation, not legal advice on your own agreements. Whether any covenant below is enforceable is a question of your state's law and belongs with your own attorney; the enforceability framework for employee restrictive covenants is derived in the non-compete card in the References rather than repeated here.

What you actually own, and what you do not

You do not own the customer. A homeowner can hire whoever they like for any reason, and no agreement between you and a former employee changes that.

What you may own is the compilation: the list together with the service history, the equipment records and model and serial numbers, the pricing you quoted each account, the renewal dates, the contact preferences, and the notes about which basement floods. Customer identities on their own are weak, because anyone can drive the street or buy a mailing list. The operational detail behind the names is what has value precisely because it is not generally known, and that is the thing to defend.

You may also own goodwill in specific substantial customer relationships, which is the interest a non-solicitation agreement exists to protect and the reason it is treated more gently than a non-compete.

The non-solicitation agreement, and the line between soliciting and accepting

A non-solicit bars the former employee from pursuing your customers. It is narrower than a non-compete because it leaves them free to work the trade, and because it leaves them free to work, more states enforce it and courts cut it back less. It is still a restrictive covenant, still measured for reasonableness in most states, and still void in a few: California treats a customer non-solicit for an employee as a restraint under the same Business and Professions Code section that voids non-competes, while Oklahoma's statute voids the non-compete and expressly preserves a narrow customer non-solicit.

Three drafting points decide whether yours is worth anything.

Solicit, not accept. A clause barring the former employee from accepting business from a customer who approaches them unprompted is broader than a non-solicit, and many courts read it as a non-compete in disguise, which drags the whole clause into the harsher test. Write it to bar initiating contact. Accept the consequence honestly: a customer who chooses to follow a person is going to follow them, and no enforceable clause stops that.

Name the customers by relationship, not by ownership. "Any customer of the Company" sweeps in accounts the person never knew existed. Limit it to customers the employee actually served, or whose confidential information they had access to, within a defined lookback; twelve months is a common and defensible window and it maps to what a maintenance book actually is.

Set a duration against the interest. The same measure as a non-compete: how long it takes you to re-establish the relationship, not how long you would like.

Trade secret protection, and the element most shops destroy themselves

Trade secret law gives you a claim against the taking of the list itself, independent of any agreement. Two elements have to hold: the information derives independent economic value from not being generally known or readily ascertainable, and the owner took reasonable measures to keep it secret.

The first element is usually satisfiable for a real service book. The second is where shops lose, and they lose it themselves, through ordinary sloppiness rather than through anything a competitor did. A customer list that every technician can export to a spreadsheet from their phone is not a list you treated as secret, and that is the first question asked.

Reasonable measures that a small shop can actually maintain: access on a need-to-know basis rather than all-techs-see-everything; export and full-list report permissions restricted to office roles; the system logging who exported what and when; the file marked confidential and the agreement saying so; and an offboarding step that revokes access the same day rather than the following month. The mechanics of the last two live in the customer-data and account-offboarding cards in the References.

The legal homes are the Uniform Trade Secrets Act as enacted by your state, which is nearly everywhere, with New York the notable common-law holdout, and the federal Defend Trade Secrets Act at 18 U.S.C. 1836, which since 2016 has given a civil cause of action in federal court.

One procedural trap with real teeth: 18 U.S.C. 1833(b) requires an employer to include a notice of the whistleblower immunity in any contract or agreement with an employee that governs the use of a trade secret or other confidential information, entered into or updated after the DTSA's May 2016 enactment. Without that notice the employer cannot recover exemplary damages or attorney fees under the DTSA against that employee. It is one paragraph, it costs nothing, and its absence is found at the worst possible moment.

The confidentiality agreement, and what it cannot reach

A confidentiality agreement can cover material broader than trade secrets, including information that would not meet the secrecy test on its own, and it is the right home for pricing structure, margins, supplier terms and account notes. What it cannot do is convert the employee's general skill or publicly available information into your property, and a definition reading "all information relating to the Company" is routinely narrowed or disregarded, with some courts treating a sufficiently broad confidentiality clause as a disguised non-compete. Define the categories. A definition a tech could apply on their own is a definition a court can enforce.

Worked case: a lead tech leaves with the maintenance book

A residential HVAC shop, nine techs, 620 active maintenance agreements. A lead tech whose route carried 140 of them resigns and starts at a competitor. Within 60 days, 31 of those 140 accounts have moved.

What that is. 31 of the 140 on his route is 22 percent of that route's agreements, and 31 of the shop's 620 total agreements is 5 percent of the recurring base. Both numbers matter and they are not the same number; the route figure is the one that tells you what happened, the book figure is the one that tells you whether the shop is in trouble.

What the shop had, tested one by one. The non-compete was broad and the shop is in a state that voids an unreasonable covenant entirely rather than trimming it, so it produced nothing. The non-solicit barred "soliciting or accepting business from any customer of the Company," and counsel's read was that the solicit half was defensible while the accept half and the any-customer scope were the exposure. The confidentiality agreement was signed at hire in 2019 and carried no DTSA immunity notice, so the federal exemplary-damages and fee remedies were off the table before anyone looked at the facts.

The fact that actually moved it. The field software logged that the lead had exported the full customer list to a spreadsheet twice in his final month, outside any job. That log is the strongest document in the file, and it exists only because the platform records exports. It is also the shop's weakest point on the second trade-secret element, because all nine techs held the same export permission, which is hard to square with having treated the book as confidential.

What happened. The shop sent a demand letter naming the 31 accounts and the two export events specifically, rather than a general warning, and the movement stopped. No suit was filed. The lever that worked was a record of a specific act, not a covenant.

The pattern in the 31. Of the 140 accounts on the route, 60 had been served by that tech on every visit and 80 had seen at least one other tech. Twenty-one of the 60 single-tech accounts moved, which is 35 percent of that group. Ten of the 80 multi-tech accounts moved, which is 12.5 percent of that group. Same route, same tech, same competitor, and the accounts that only ever met one person left at nearly three times the rate. That is the finding, and it is not a legal one.

The operational levers that beat all three documents

• Rotate the route enough that more than one person has been to the house. The single-tech accounts in the case above are the exposure, and the fix costs nothing but scheduling discipline.
• The shop's number is the number. On the invoice, on the truck, on the sticker on the equipment, in the confirmation text. If the customer's phone holds the tech's mobile, the relationship is already in the wrong place.
• The service history lives in the system, not in a notebook. A customer who calls the office and hears their equipment's model, its last capacitor change and its filter size is talking to a shop that knows them.
• The follow-up comes from the office. The renewal notice, the seasonal reminder and the review request are the shop speaking, and they are the touches between visits.
• Revoke access the day the person leaves, including the phone app, the shared drive and any list they could pull. Same-day, on a checklist, before the exit conversation ends.

How to verify you got this right

Name everyone in your shop who can export the full customer list today, and check whether your system records that they did. Open your offboarding checklist and find the same-day access revocation step, or add it. Read your non-solicit and confirm it is limited to customers the person actually served in a defined window and that it bars soliciting rather than accepting. Pull any confidentiality or trade-secret agreement signed or updated since May 2016 and look for the whistleblower immunity notice. Then run one report: what share of your recurring accounts have seen exactly one technician in the last two years. That number is your real exposure, and it is the only one on this list you can fix without a lawyer.

References

• Defend Trade Secrets Act, 18 U.S.C. 1836, and the whistleblower immunity notice requirement at 18 U.S.C. 1833(b)
• Uniform Trade Secrets Act as enacted in your state, including the reasonable-measures element
• Cal. Bus. & Prof. Code 16600; 15 Okla. Stat. 219A
• See related: The Employee Non-Compete and Why Most of Them Fail; Keeping Your Customer Data Backed Up and Secure; The Customer Data You Store: Protecting It; The Account Offboarding When an Employee Leaves SOP