A Key Employee Left. What Can a Wisconsin Employer Protect?

Start Here

What Is Happening?

The right first move depends on what you are actually dealing with. Start with the line that matches.

An employee announced their departure. → An employee joined a competitor. → Our customers are being contacted. → Our employees are being recruited. → Files or data may have been taken. → A former employee started a competing company. → We need emergency relief. →

Preserve First

The First 24 to 48 Hours

Almost everything that decides a departure case is created or destroyed in the first two days, usually by people acting in good faith. IT reimages a laptop. A mailbox is closed to save a license. Logs roll over. Do this before you do anything else — including before you decide whether you have a case at all.

1

Preserve the laptop. Do not reissue it.

Image it, or set it aside untouched. A wiped and reassigned device is the single most common way employers destroy their own best evidence.
2

Preserve the email account.

Do not delete the mailbox to reclaim a license. Put it on hold. Forwarded mail to a personal address is frequently the clearest part of the record.
3

Preserve cloud and file-share activity logs.

Download, sync, and share events often age out on a retention schedule measured in weeks. Export them now rather than discovering the window closed.
4

Identify downloads and external device activity.

USB connections, bulk downloads, personal cloud syncing, and mass printing in the final weeks. The pattern matters as much as any single event.
5

Secure accounts and access — carefully.

Cut off access to systems, but coordinate with whoever is preserving evidence so that locking an account does not destroy what is in it.
6

Pull the customer communication record.

What the employee sent, and to whom, in the last 60 to 90 days. Then check which accounts have gone quiet since.
7

Locate every agreement the employee signed.

Offer letter, employment agreement, confidentiality, IP assignment, handbook acknowledgments, and anything signed at a promotion or with equity.
8

Find out where they went, and in what role.

A competitor, a customer, a supplier, or their own new entity — and what they will actually be doing. This drives whether your restriction even reaches the conduct.
9

Write down the timeline while it is fresh.

When they gave notice, what they said, who they spoke to, what changed in the weeks before. Contemporaneous notes are worth far more than a reconstruction later.

Preservation is not an admission that you are going to sue. It costs very little and it is not recoverable once lost. Decide on the claim afterward.

An Honest Grid

What Can an Employer Actually Protect?

Employers routinely assume the protectable category is broader than it is, and that assumption is how overbroad agreements get drafted and then voided. Under § 103.465 a restriction has to be reasonably necessary to protect a legitimate interest — not simply useful to you.

Potentially protectable

With the right facts

Trade secrets under the statute
Genuinely confidential business information
Customer relationships you paid to build
Substantial investment in specialized training
Pricing methodology that is not public
Goodwill purchased in a business sale

Usually not enough by itself

Ordinary competition

Not wanting a competitor to improve
General skill and experience the employee developed
Industry knowledge anyone in the field has
Information you never treated as confidential
Publicly available customer identities
The employee's own pre-existing relationships

Depends on the facts

The real fight

Customer lists — how they were built and guarded
Pricing sheets and quotes
Whether information was actually kept secret
How long the interest stays current
Territory versus named-account scope
Whether the clauses are divisible

The middle column is where cases are lost before they start. A customer list is not automatically a trade secret in Wisconsin, and pricing is not automatically confidential. Whether either qualifies depends on how the information was built, whether it is readily ascertainable elsewhere, and — critically — what you actually did to keep it secret.

Two Independent Cases

The Agreement and the Conduct Are Separate Questions

This is the most useful thing an employer can understand early, and it cuts both ways.

Whether your noncompete is enforceable under § 103.465 is one question. What the employee actually did is an entirely different one. An employer with a vulnerable agreement is not without remedies, and an employer with a beautifully drafted agreement and no evidence of misconduct may have less than it thinks.

Claims that do not depend on the covenant

Misappropriation of trade secrets under Wisconsin's Uniform Trade Secrets Act, Wis. Stat. § 134.90, and the federal Defend Trade Secrets Act.
Misuse of confidential information that falls outside the statutory trade secret definition. Wisconsin's Supreme Court has held that the trade secrets act does not displace claims built on information outside that definition — which makes this a meaningfully broader path here than in many states.
Breach of the duty of loyalty for what happened while the employee was still on your payroll.
Computer crime claims under Wis. Stat. § 943.70, with a civil remedy under § 895.446, where data was taken or destroyed.
Conversion and civil theft of company property.
Tortious interference where a competitor induced the conduct.

The practical consequence: the evidence of what happened is usually worth more than the strength of the clause. That is exactly why the preservation checklist above comes first, and why sending a demand letter that rests entirely on an overbroad restriction can be the weakest available move.

Before You Assert Anything

What Agreements Do You Have?

Pull the actual signed documents before you send anything. Asserting a restriction you cannot produce, or quoting a clause the employee never signed, is a bad beginning — and in Wisconsin, waving an unenforceable restriction can cost you credibility on the claims that would have worked.

Noncompete

Check the scope against the job actually held. A restriction drafted for a national sales leader rarely survives when applied to a regional technician.

Customer nonsolicitation

Note whether it bars soliciting only, or also accepting business. The broader version is more useful if enforceable and more vulnerable if challenged.

Employee nonsolicitation

Wisconsin applies § 103.465 to these, and the Supreme Court has struck down a clause covering all employees regardless of whether the departing employee ever worked with them.

Confidentiality and NDA

Often your most durable instrument. It can bind even where the noncompete does not, and it does not require you to prove a trade secret.

Return of property

Simple, enforceable, and useful early — a documented demand for return creates a clean record and often produces admissions.

IP and invention assignment

Relevant where the departing employee is launching a product rather than selling a competing one.

Choice of law and venue

Worth checking before you file. A clause pointing somewhere else, or a remote employee in another state, changes the map.

How Wisconsin judges these restrictions →

Duty of Loyalty

What Happened While They Were Still on Your Payroll

Employees in Wisconsin owe a duty of loyalty during employment. They are permitted to prepare to compete — to interview, to plan, even to form an entity they do not yet operate — but they are not permitted to compete with you while you are paying them.

This claim matters disproportionately, because it does not depend on your restrictive covenant being enforceable at all. It also tends to be where the most damaging facts live.

What to look for in the final months of employment:

Customers told about the departure before notice was given
Coworkers recruited while still employed
An entity registered with the state before resignation
Opportunities that arrived at your company and went somewhere else
Quotes or bids prepared for the new venture on your time
Suppliers or vendors approached about the new business
A drop in the employee's own production in the final quarter

The state's corporate registry is public and takes minutes to search. The formation date of a competing entity, set against the resignation date, is frequently the most persuasive single fact in the case.

What the employee side is being told →

Proving It

Confidential Information and Trade Secrets

Employers tend to state this category too confidently — “they took our customer list, that is a trade secret” — and Wisconsin courts do not accept the label without the underlying facts.

What the statute requires

Under Wis. Stat. § 134.90, information qualifies as a trade secret only if it derives independent economic value from not being generally known or readily ascertainable by proper means, and is the subject of efforts that are reasonable under the circumstances to maintain its secrecy. Both halves are contested in almost every case.

The second half is where employers most often lose. If the customer list was emailed around without restriction, stored on an open share, printed and left on desks, or handed to every new sales hire on day one, the reasonable-efforts element becomes very hard to carry — regardless of how genuinely valuable the information was.

The broader path Wisconsin leaves open

Information that does not meet the statutory definition is not necessarily unprotected. Wisconsin's Supreme Court has held that the trade secrets act does not displace claims based on confidential information falling outside the statute. Combined with a signed confidentiality agreement, that is often the more practical route — and it does not require you to win the trade secret fight first.

What to establish early

What specifically was taken, identified with precision rather than by category
How it was created, and what it cost you to build
Who had access, and under what restrictions
What security measures actually existed, in practice and not just in the handbook
Whether the same information could be assembled from public sources
What the employee did with it after leaving

One drafting note for the future: the federal Defend Trade Secrets Act conditions exemplary damages and attorney fees on including a whistleblower immunity notice in agreements governing trade secrets. Many older Wisconsin agreements do not have it.

The Accounts

Customer Relationships and What Was Said

The claim an employer usually cares most about is the one about customers, and it has two independent halves that are worth keeping separate.

The clause. What does your nonsolicitation provision actually prohibit? A restriction on soliciting is narrower than one on accepting business. A restriction covering every customer of the company is far more vulnerable under § 103.465 than one limited to accounts the employee personally served in a defined recent period. Read your own clause with an unfriendly eye before you assert it.

The conduct. Independent of the clause, what happened? Contact made before the resignation was effective, outreach using information taken from your systems, or misstatements about your company's ability to keep serving the account are problems on their own terms.

The distinction that decides many of these disputes is who initiated contact. A customer that calls a departed salesperson on its own is a materially different fact than a departed salesperson working through an exported list. Your own account records, call logs, and the customers themselves are usually the fastest way to find out which one you have.

A practical caution: customers talk. An aggressive campaign of calls and letters to accounts about a former employee can do more commercial damage than the departure did, and it can generate claims against you. Gather the facts before you broadcast the dispute.

Employee Solicitation

They Are Recruiting Your People

A single departure is a problem. A departure followed by three more from the same team is a different kind of problem, and it is frequently the one that pushes an employer toward emergency relief.

Wisconsin subjects employee nonsolicitation clauses to § 103.465, the same statute that governs noncompetes. The Wisconsin Supreme Court has invalidated a no-solicit clause that reached every employee of the company, including people the departing employee had never worked with — a useful warning about what your own clause may be worth if it was drafted to be maximally broad.

What tends to matter in practice:

Whether the clause is limited to employees the departing person actually worked with
Whether recruiting began while the employee was still employed, which raises duty of loyalty independent of any clause
Whether confidential compensation or performance data was used to target people
Whether the new employer coordinated the departures, which raises interference

Exit interviews with the employees who left, done promptly and carefully documented, are often the most valuable evidence available here — and the window for them is short.

Before You Send It

Should You Send a Cease-and-Desist Letter?

The demand letter is the default first move, and it is not always the right one. In Wisconsin it carries a specific risk: a letter resting on an overbroad restriction can invite a declaratory judgment action and hand the other side the choice of forum.

What does it accomplish when it works?

It stops the conduct without litigation, creates a record that you objected promptly, puts the new employer on notice — which matters for interference claims and for arguing knowing conduct later — and preserves the argument that you acted quickly when irreparable harm is assessed.

What is the risk of sending one too early?

Asserting a restriction that will not survive § 103.465 can be answered with a suit for declaratory judgment, filed where the employee chooses, putting you on the defensive in a forum you did not pick. It also tips off the other side to preserve and prepare before you have gathered your own evidence.

What should be established first?

What the agreement actually says, whether the restrictions are divisible, what your forensic record shows, whether the conduct claims stand on their own, and where you would file if the letter fails. A letter written after that work reads very differently from one written on day two.

Does waiting hurt us?

Yes, and this is the genuine tension. Delay undercuts the irreparable harm argument that emergency relief depends on. The answer is not to wait — it is to move quickly on preservation and analysis so that the letter, if you send one, is aimed at something that will hold.

Should the new employer get a copy?

Often yes, but it is a decision with consequences rather than a formality. It can resolve the problem quickly, and it can also escalate a manageable dispute into a two-defendant case.

Emergency Relief

When Does an Injunction Make Sense?

Emergency relief is the center of gravity in noncompete litigation. In most of these disputes the injunction hearing effectively decides the outcome, whatever happens to the merits afterward.

The two instruments

A temporary restraining order is short-term, sometimes sought with limited notice, and meant to hold the position until a hearing can be held. A temporary injunction follows a hearing and can last through the case.

What you generally have to show

A reasonable probability of success on the merits
Irreparable harm if relief is not granted
No adequate remedy at law
That the balance of equities favors an order

The practical threshold

Emergency relief is realistic when you can point to concrete, ongoing harm and specific evidence: a forensic report showing what was taken, named accounts that moved, identified employees recruited, a competing entity formed before resignation. It is much harder when the case is a suspicion about a resignation and a broad restriction, with the actual conduct still unknown.

Two things defeat otherwise good motions. The first is delay — every week between discovery of the conduct and the filing is used to argue that the harm cannot be irreparable if you could live with it that long. The second is overreach: asking a court to enforce a restriction that plainly fails § 103.465, when a narrower and better-supported request would have been granted.

There is also a cost worth naming. Injunctions typically require a bond, the process is expensive and fast-moving, and losing one publicly can embolden the conduct you were trying to stop. It is a strong tool and it is not a free one.

The full dispute timeline, stage by stage →

Case Study

An Employee Built a Competitor On Your Payroll

This is a real Wisconsin matter, anonymized to role and industry. It is here because the shape of it is ordinary — the facts are not exotic, and the employer recovered its position only because the laptop still existed.

A 2025 Wisconsin case between an industrial parts and services company and a former technical sales employee, filed in Brown County Circuit Court. Anonymized to role, industry, county and year.

Before departure

Spent more than a year emailing the employer's customer lists, pricing sheets and technical specifications to his own and his spouse's personal accounts
Registered a competing company with the state weeks before resigning
Began quietly redirecting vendor leads to the new entity

At departure

Connected a thumb drive in his final two weeks and downloaded a large volume of additional files
Deleted records in an attempt to cover the activity
Resigned shortly after the competing entity was formed

After departure

Performed substantially similar work for the competing company
Solicited the employer's customers
Used the confidential information that had been taken

What the employer did

Preserved and forensically imaged the company laptop rather than reissuing it
Reconstructed the email, download and external-device record
Moved for a temporary injunction under the agreement and the trade secrets statute

The court found a reasonable likelihood of success on the merits, irreparable harm absent relief, and no adequate remedy at law. It granted the injunction — barring the former employee from performing similar work for the competing company, from soliciting the employer's customers, and from using any of the confidential information taken — and ordered everything returned.

The lesson is not that employers win these. It is that this employer had a forensic record because it preserved the laptop, and a formation date it could set against a resignation date. Without the device, the same facts would have been an unprovable suspicion.

From the Field

Articles for Employers

I'm Leaving

I Work Remotely for an Out-of-State Company. Which State's Noncompete Law Applies?

Less settled than you would hope, and often decided by a venue motion rather than by where you live. Because a covenant void in one state can be enforceable in another, the court that hears the case frequently decides the outcome.

A Former Employee Took Our Customer List. What Can We Actually Sue For?

Breach of the covenant, breach of the duty of loyalty, trade secrets, and unauthorized computer access — those fit the conduct and survive. Federal racketeering and false-advertising claims get dismissed, and asking for them invites the court to read the whole complaint as rhetoric.

My Best Salesperson Left Friday and Contacted Our Largest Customer Monday. What Should I Do?

Preserve the laptop before IT wipes it, pull a year of logs rather than a week, and read your own agreement before you assert it. An overbroad clause is void in Wisconsin, not narrowed — so the letter you send matters as much as the timing.

Questions We Hear in This Situation

Quickly — think days and weeks, not months. Injunctive relief requires showing irreparable harm and that legal remedies are inadequate, and delay after discovering a violation undercuts both. Preserve the employee's devices and access logs immediately, because forensic evidence of what was copied is usually what carries the motion.

Before anything else: the laptop, unwiped and unreissued; the email account, on hold rather than deleted; and cloud, file-share and device-connection logs, which often age out in weeks. Employers routinely destroy their own best evidence in the first 48 hours through ordinary IT hygiene — reimaging a device, closing a mailbox to reclaim a license. Preservation is cheap, is not an admission that you intend to sue, and is not recoverable once lost.

Not automatically. Under Wis. Stat. § 134.90 information qualifies only if it derives independent economic value from not being generally known or readily ascertainable, and is the subject of reasonable efforts to keep it secret. Employers most often lose on the second half: a list emailed around freely, stored on an open share, or handed to every new hire is hard to defend as secret. Wisconsin does leave a broader path — claims based on confidential information outside the statutory definition are not displaced by the trade secrets act, which paired with a confidentiality agreement is often the more practical route.

Often yes, because the agreement and the conduct are separate questions. Claims for misappropriation of trade secrets, misuse of confidential information, breach of the duty of loyalty for what happened while the employee was still on your payroll, computer crime claims where data was taken or destroyed, and tortious interference do not depend on the restrictive covenant being enforceable. In practice the evidence of what actually happened is worth more than the strength of the clause — which is why preservation comes before the demand letter.

Not reflexively. A letter resting on a restriction that will not survive § 103.465 can be answered with a declaratory judgment action filed where the employee chooses, putting you on the defensive in a forum you did not pick, and it tips off the other side before you have gathered your evidence. The tension is real, because delay undercuts the irreparable harm argument emergency relief depends on. The answer is to move fast on preservation and analysis, then send a letter aimed at something that will hold.

It depends on how it is drawn. Wisconsin applies § 103.465 to employee nonsolicitation clauses, and the Wisconsin Supreme Court has invalidated one that reached every employee of the company regardless of whether the departing employee had ever worked with them. A clause limited to colleagues the person actually worked with is a much stronger position. Separately, recruiting that began while the employee was still employed raises a duty of loyalty claim that does not depend on the clause at all.

A Key Employee Left. What Can You Protect?