Skip to content
STL Powercast

Employment restrictive covenants: non-compete, non-solicitation and confidentiality clauses, how courts test them, and how to get useful legal help

Three clauses, one signature. Which one actually follows you out the door?

Employers bundle non-compete, non-solicitation and confidentiality language into one paragraph, but courts treat the three very differently, and so should you.

Three clauses, one signature. Which one actually follows you out the door?
Most restrictive covenant clauses combine a non-compete, a non-solicitation and a confidentiality obligation in a single block of text. Courts pull them apart and judge each on its own merits.
Confidentiality rarely fails

A promise not to use or disclose company information restrains what you do, not where you work, so judges enforce it with little argument. Compliance costs you nothing but discipline.

Devices before departure

Clearing personal laptops, phones and cloud drives of company files before your last day removes the fact most likely to escalate a dispute. Keep a record of what you deleted and when.

Solicit versus accept

A clause barring you from soliciting former customers is far narrower than one barring you from accepting their business. Check which verb your agreement uses, because the difference is substantive.

01

Named accounts hold better

Non-solicitation clauses limited to customers you personally served in your final period of employment are enforced more readily than blanket bans covering an entire company client list.
02

The temporary restraining order problem

An employer can ask a court to block your start date within days of filing, long before anyone rules on whether the clause is reasonable. The practical cost is lost income during that window.
03

States that say no

California, North Dakota, Oklahoma and Minnesota have largely removed employee non-competes by statute. Where you live and where you signed can both matter to which law applies.
Federal attention is ongoing
The Federal Trade Commission oversees competition policy touching these agreements and has made non-competes a visible federal subject. The legal landscape is not static.
Advice before the offer
An opinion obtained while you can still negotiate an offer changes what you agree to. The same opinion after you resign only changes what you defend.
Colleague recruitment clauses
Employee non-solicitation language, the promise not to poach former coworkers, follows the same logic as customer clauses. Narrow versions naming people you actually worked with tend to survive review.

The paragraph you signed probably ran four or five sentences and covered three separate promises, which is exactly why it feels immovable now. Employers draft them together because it is efficient to do so, and because a single dense block reads as one indivisible obligation rather than three claims of very different strength. Courts do not read it that way. When a former employer sends a letter, or files, the three parts get pulled apart and tested separately, and the outcome usually turns on which of them your new job actually implicates.

The confidentiality promise is the one that holds

Of the three, the obligation not to use or disclose the company's confidential information is the one judges enforce with the least hesitation, in almost every state, for the simple reason that it does not stop you working anywhere. It restrains conduct, not employment. You can take the competing job, do the competing work, and comply fully by not opening the old customer pricing file you saved to a personal drive in your last week. That is why the honest answer to a confidentiality claim is almost always operational rather than legal: return the devices, delete the copies, document that you did, and the claim tends to shrink.

The cost here is rarely a court fight and usually a forensic one. Companies preserve laptop images, email logs and cloud sync records, and the expensive version of this dispute is the one where someone downloaded a folder on a Friday afternoon because it seemed easier than rebuilding a spreadsheet from scratch. An hour spent clearing personal devices before the last day is worth more than any argument you can make afterward, and it removes the single fact that turns a weak non-compete claim into a serious one.

Non-solicitation sits in the middle, and the wording matters

A promise not to solicit the customers you personally served, for a defined period, tends to survive review in states that are otherwise hostile to restraints, because it protects a relationship the employer paid to build without barring you from the trade. The fights are about scope and about verbs. A clause limited to accounts you actually handled in your final year is a different animal from one covering every client on a company-wide list, including people in states you have never visited. Courts notice that difference, and often enforce the narrow version while trimming or refusing the broad one.

The verb matters just as much. Soliciting means reaching out to move business. Accepting unsolicited business is something else, and many agreements quietly try to cover both by adding "or accept" or "or do business with," which converts a relationship-protection clause into a partial non-compete. Employee non-solicitation, the promise not to recruit former colleagues, follows similar logic and is generally enforced when it names the people you worked with rather than the entire payroll.

The non-compete is the hard case, and the expensive one

Barring you from an occupation is the restraint courts scrutinize hardest, because the burden falls on your income rather than on your discretion. Every state that enforces non-competes at all asks some version of the same questions: is there a genuine interest worth protecting beyond keeping a trained person off the market, is the duration reasonable, is the geography tied to where you actually worked, and is the definition of competitive work narrow enough to leave you a living. Two states have answered these questions in opposite directions on facts that look nearly identical, and California, North Dakota, Oklahoma and Minnesota have taken employee non-competes largely off the table by statute. The Federal Trade Commission, which oversees competition policy affecting these agreements, has made them a visible subject of federal attention, so the ground is still moving.

What makes this the costly case is not the legal standard but the timeline. A former employer seeking a temporary restraining order can put your start date in front of a judge within days, long before anyone examines whether the clause is reasonable, and the practical question becomes whether you can afford to be unemployed while that gets sorted out. Getting an early read from a non compete agreement lawyer who handles these in your state, ideally before you accept an offer rather than after you give notice, is the cheapest money in the whole sequence, because the advice changes what you negotiate rather than what you defend.

Working out which case you are in

Read the new role against the three promises separately and the picture usually resolves fast. If the job serves a different market, a different customer set and a different product line, you are probably in confidentiality territory, where compliance is a matter of housekeeping. If you are going to a direct competitor but into a function that never touches your old accounts, you are in the solicitation zone, and the useful step is a written understanding with the new employer about who routes inbound inquiries. If you are doing the same work, for the same buyers, in the same territory, you are in the hard case, and the question is no longer whether the clause is fair but what the first thirty days cost.

That distinction is worth making before you speak to anyone at the old company, because the framing you choose early tends to stick. Separating the three claims lets you concede the easy one honestly, which buys credibility, while reserving your argument for the part that actually restrains your ability to earn.

On this site