Talk to an Attorney →
Resource Library

Wisconsin Noncompete Reference

Everything the site knows, in one place: the vocabulary, the statutes, how a contested dispute actually unfolds, and every question we are asked — for employees, employers, and companies hiring someone who is restricted. Ask the assistant on the right, or read below.

Plain-English definitions of the terms that come up most often in Wisconsin noncompete disputes.

Non-compete agreement — A contract term barring an employee from working for a competitor, or in a competing capacity, for a set period after leaving. In Wisconsin these are governed by Wis. Stat. § 103.465 and are enforceable only if reasonably necessary to protect the employer, limited in time and territory, and not harsh or oppressive to the employee.
Restrictive covenant — The umbrella term for any post-employment restraint: non-competes, customer and employee non-solicits, confidentiality clauses, and no-hire provisions. Wisconsin's § 103.465 applies to all of them, not just the clause labeled "non-compete."
Non-solicitation clause — A promise not to approach the employer's customers, or not to recruit its employees, for a defined period. Customer non-solicits limited to accounts the employee actually serviced are among the most likely restraints to survive Wisconsin scrutiny, because they protect a real relationship rather than blocking competition outright.
Wis. Stat. § 103.465 — Wisconsin's restrictive covenant statute, and the single most important rule in this area. It requires a restraint to be reasonably necessary to protect the employer — and if it is not, the covenant is void in its entirety. Wisconsin courts do not narrow overbroad restraints to save them.
Blue pencil doctrine — No. "Blue penciling" is the practice, allowed in some states, of trimming an overbroad restraint down to a reasonable one. Wisconsin rejects it. Under § 103.465 an unreasonable covenant is unenforceable as written, which means aggressive drafting risks losing the protection entirely.
Per se invalid — That the clause fails as a matter of law from its text alone, with no discovery or factual record needed. Wisconsin courts apply this clause by clause: a flat non-compete or a supplier restriction can be void per se while a narrower non-solicit in the same agreement survives and proceeds to the facts.
Trade secret — Under Wis. Stat. § 134.90, information — a formula, pattern, compilation, program, method, or technique — that derives independent economic value from not being generally known or readily ascertainable, and that the owner took reasonable measures to keep secret. Customer lists, pricing models, and technical drawings routinely qualify.
Confidential information — Confidential information is the broader category, defined by the contract rather than by statute — customer data, pricing, margins, business plans, supplier terms. A confidentiality clause can protect material that would not meet the stricter statutory trade secret test, which is why it is often an employer's most useful claim.
Injunctive relief — A court order requiring someone to stop doing something — competing, soliciting, or using confidential information — while the case proceeds. It is the remedy that usually matters most, because money damages rarely repair a lost customer relationship. Obtaining it requires showing likelihood of success, irreparable harm, and no adequate remedy at law.
Temporary injunction — Often within weeks of filing. A temporary injunction preserves the status quo pending trial, and courts can grant interim relief before a full evidentiary hearing. Because the standard requires irreparable harm, delay in seeking relief after discovering a violation can undercut the request.
Choice of law clause — It is influential but not automatically controlling. Courts weigh it alongside where the employee worked and lived, and a separate fight over venue often comes first. Because a covenant void in California may be enforceable in Wisconsin, which court hears the case frequently determines the outcome.
Declaratory judgment — Yes. A declaratory judgment action asks a court to rule that the restraint is unenforceable. Where the agreement is overbroad on its face, this can be resolved on the pleadings without full discovery — and it removes the uncertainty that makes a new employer hesitate to hire.
Cease and desist letter — Do not respond substantively before someone reviews the actual agreement. Many letters assert restraints that would not survive § 103.465. Note also that asserting an unenforceable covenant can itself expose the employer to a damages claim, so the letter is not automatically the strong position it appears to be.
Garden leave — An arrangement where the employer keeps paying the departing employee through the restricted period instead of simply barring them from working. Paid consideration during the restraint strengthens the employer's reasonableness argument, because the employee is not left without income.
Sale-of-business covenant — Genuine sale-of-business covenants are reviewed more leniently than employment restraints. But the label does not control: if signing the covenant was a condition of employment, Wisconsin courts apply § 103.465 regardless of what the document is titled.

The statutes that come up most often in Wisconsin noncompete disputes, translated out of legal language.

Restrictive covenants in employmentThe controlling statute for every restraint on this site. A covenant is enforceable only if it is reasonably necessary to protect the employer, reasonable in duration and territory, and not harsh or oppressive to the employee or contrary to public policy. Critically, a covenant that fails is void in its entirety — Wisconsin courts will not narrow it. The statute reaches non-solicitation and confidentiality provisions too, not just the clause titled "non-compete."
Wisconsin's Uniform Trade Secrets ActDefines a trade secret as information deriving independent economic value from not being generally known or readily ascertainable, which the owner took reasonable measures to keep secret. It authorizes injunctions against actual or threatened misappropriation, damages, and — where the misappropriation was willful and malicious — up to twice actual damages plus attorney's fees.
Computer crimesIt can be. The statute makes it an offense to willfully, knowingly, and without authorization modify, destroy, access, take possession of, or copy data, programs, or supporting documentation. Where an employment agreement limits computer use to the employer's business purposes, accessing systems to benefit a competing venture can fall outside authorized use. Section 895.446 turns a violation into a private civil claim.
Civil claim for property crimesYes. This section creates a private cause of action for anyone damaged by an intentional violation of several criminal statutes, including theft (§ 943.20), identity theft (§ 943.203), and computer crimes (§ 943.70). Remedies include actual damages, costs, and attorney's fees — which is why these claims often outperform more exotic federal theories.
Defend Trade Secrets Act (federal)Yes. The DTSA creates a federal civil claim for trade secret misappropriation, which allows a case to be filed in federal court. Its definition of a trade secret differs in wording from Wisconsin's, but the same facts frequently support claims under both. The DTSA also contains whistleblower immunity for disclosures made in confidence to a government official or attorney.
Transfer of venueYes. A federal court may transfer a case, for the convenience of parties and witnesses and in the interest of justice, to any district where it could have been brought. Courts weigh the plaintiff's chosen forum, party and witness convenience, access to evidence, familiarity with the governing law, local interest, and docket congestion. Witness convenience is typically the most important factor — and for remote employees, this motion often decides which state's law governs.

Contested noncompete disputes in Wisconsin tend to move through the same stages. Here's what's ahead.

Days 1–7Locate the actual signed agreement — not what anyone remembers it saying — along with the offer letter and any handbook or amendments. Employees should avoid discussing plans with colleagues. Employers should immediately preserve the departing employee's laptop, email, and system logs before any device is wiped and reissued, since that evidence is what later proves or disproves a violation.
Weeks 1–3The employer sends a letter identifying the restraints it intends to enforce; the employee responds, often disputing enforceability. Many disputes end here. A letter overstating a covenant that would not survive § 103.465 can weaken the employer's position — and, if it interferes with the employee's new work, can support a damages claim against the employer.
Weeks 2–8Faster than most civil litigation, because injunctive relief is time-sensitive. An employer seeking a temporary injunction files with supporting declarations and exhibits; an employee may instead file first for a declaratory judgment that the covenant is void. Courts often grant interim relief before a full evidentiary hearing to preserve the status quo.
Months 2–6Frequently, yes — at least in part. Because § 103.465 operates on the text, an employee can win on the pleadings where a restraint is facially overbroad, and courts routinely rule clause by clause: voiding some provisions per se while sending others to discovery. Employers also lose overreaching claims at this stage, particularly federal racketeering and false advertising theories that do not fit the conduct.
Months 4–12The clauses that survived: what the employee actually did, which customers they had real contact with, what information was taken and whether it was genuinely confidential, and what the employer's protectable interest was. Forensic examination of devices and email is common, and protective orders are typically entered to shield customer data from the public record.
Months 6–18Most settle, commonly on negotiated terms narrower than the original covenant — a shortened restricted period, a defined customer carve-out, or return-and-certify obligations for confidential information. Cases that reach trial are the exception, usually where damages are large or the parties genuinely dispute what was taken.

Every question on the site, for all three sides of these disputes.

It depends on the specific clauses, and the honest answer usually requires reading the agreement. Wisconsin is one of the strictest states: under § 103.465, a restraint must be reasonably necessary to protect the employer and reasonable in time and territory, and if it is not, it is void entirely rather than narrowed. In practice, broad flat noncompetes often fail while narrower customer non-solicits and confidentiality clauses often survive — which is why the analysis has to go clause by clause rather than agreement by agreement.
Wisconsin sets no fixed limit, and there is no duration that is automatically safe. The test is functional: a restriction lasts only as long as is reasonably necessary to protect a legitimate interest. Where customer relationships turn over quickly or pricing information goes stale in months, a long restriction is difficult to justify. Because an unreasonable indivisible restraint is void entirely rather than shortened, an employer that reaches for an extra year can end up with nothing.
Generally no, and this is the most important single fact about Wisconsin noncompete law. Wis. Stat. § 103.465 provides that a covenant imposing an unreasonable restraint is void and unenforceable even as to any part of it that would have been reasonable. Wisconsin does not blue-pencil. There is one significant qualification: where restrictions are genuinely separate and divisible, Wisconsin courts have held they may be analyzed independently, so one invalid clause does not automatically void a separately drafted one.
Not necessarily a map-based one. Many modern agreements replace a geographic territory with a customer-based scope — restricting the accounts the employee actually served rather than an area — and a well-drawn customer limitation is often more defensible than a broad territory. What matters is that the scope tracks the employee's real working footprint. A statewide restriction for someone who covered three counties is a standard point of attack, and so is a restriction covering every customer of a company the employee served a slice of.
It is genuinely unsettled and often decided procedurally rather than substantively. Courts weigh the agreement's choice-of-law clause, where you worked and lived, and where the employer and its witnesses sit. A separate fight over venue frequently comes first, and because a covenant that is void in one state may be enforceable in another, the court that hears the case often determines the result.
The federal rule never took effect. The Federal Trade Commission issued a final rule in April 2024 that would have banned most noncompetes nationwide, but a federal court in Texas set it aside on a nationwide basis in August 2024 before its effective date, and the agency later moved to dismiss its appeals in favor of case-by-case enforcement. Wisconsin agreements continue to be governed by state law under § 103.465 — which is already among the strictest in the country. Federal activity here has moved repeatedly, so confirm the current position before relying on it.
It varies widely with how far the case goes. A review of the agreement and a response to a cease-and-desist letter is a contained expense, and many disputes end there. Contested injunction proceedings with forensic analysis and expert involvement cost substantially more. Note that many agreements include fee-shifting provisions favoring the employer if it prevails, which is a real factor in deciding how to respond.
Possibly not as written. A covenant drafted around a role you no longer hold may no longer be reasonably necessary to protect the employer with respect to your current duties, and reasonableness is judged against the interest actually being protected. Significant changes in role, territory, or customer responsibility are all worth reviewing — as is whether a later agreement superseded the original.
Only if the restraint is enforceable and actually covers the new role. Employers frequently assert more than the agreement supports. Even where a covenant is valid, it may restrict only duties substantially similar to what you performed in your final months, within a defined geography — leaving room for a different role at the same competitor. Get the agreement reviewed before accepting or declining an offer.
You risk a lawsuit and, more immediately, a temporary injunction that can force you out of the new job while the case proceeds. You may also owe the employer's attorney's fees if the agreement shifts costs on successful enforcement. The better path is determining whether the restraint is enforceable before you act, not after your employer has moved for relief.
Often yes — being terminated does not automatically void a restraint. But the circumstances matter. Where the employer breached first, or where termination was without cause, that strengthens arguments that enforcement is harsh or oppressive and that the employer lacks a protectable interest worth restraining. If your exit involved a severance agreement, that document may also have modified the covenant.
Yes, potentially. Wisconsin applies § 103.465 clause by clause, so a void noncompete does not take the rest of the agreement with it. A confidentiality clause covering genuinely confidential information can remain fully enforceable — and independent of any contract, Wisconsin's trade secrets statute protects the employer's information regardless of what you signed.
Your general skills, knowledge, and professional experience are yours. What is not yours: customer lists, pricing sheets, technical drawings, quotes, forms the company created, and anything else the company built and protected. Emailing documents to a personal account or copying files to a drive before resigning is the single most common fact pattern in these cases, and forensic review reliably surfaces it.
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.
Often yes. A restriction does not make a candidate untouchable — but the diligence belongs before the offer, not after a letter arrives. Get the actual agreements rather than the candidate's description of them, have someone read them against the role you are offering, and consider whether territory, accounts, product line or duties can be designed so the job does not conflict with what the restriction actually covers. If the whole value of the hire is the accounts they are restricted from touching, structuring will not fix that.
You can be named, and in Wisconsin departures that reach litigation new employers frequently are. Being named is not the same as being liable. Tortious interference requires proof of an existing contract, intentional interference, causation, damages and a lack of justification — and a claim built on a restriction that is void under § 103.465 has a serious problem. The more dangerous exposure is trade secret and confidential information claims, because those do not depend on the covenant. That risk is almost entirely self-inflicted: it comes from letting the new hire's former-employer files onto your systems.
Anything belonging to the former employer: customer lists and CRM exports, pricing sheets and quotes, internal presentations and strategy documents, downloaded files of any kind, product or technical material, and former-employer laptops, phones or drives. Put the instruction in the offer letter, repeat it on day one, and have the employee confirm in writing that they brought nothing. Brief the hiring manager too — managers create exposure by asking reasonable-sounding questions about a competitor's pricing or pipeline.
It depends on the specific hire rather than on a general rule. Indemnification can close a strong candidate who is otherwise afraid to move. It also transfers risk you may not have priced, can complicate your own defense, and in some circumstances is read as evidence that the company knew the hire was contested. Scope is everything — defense costs only or judgments too, capped or uncapped, conditioned on the employee's compliance or not. Work it out before the offer letter goes out.
Your company needs its own response strategy rather than relying on the employee's lawyer. Your interests overlap but are not identical: the employee's priority is keeping the job, yours includes limiting corporate exposure. Preserve everything including onboarding records and systems logs, verify what actually arrived on your systems and be certain of the answer, read the specific provision being asserted, and never instruct the employee to delete anything. Many of these resolve into a narrow, time-limited accommodation on named accounts.
Ask a Noncompete Question
Ask me anything about Wisconsin noncompete law, or tap a term, statute, stage, or question on the left to get a straight answer.
What to Expect

The Noncompete Dispute Timeline in Wisconsin

Every case is different, but contested noncompete disputes in Wisconsin tend to move through the same stages. Knowing what is ahead makes it easier to make good decisions at each step.

Stage 1Days 1–7
Read the agreement and preserve everything
Locate the actual signed agreement — not what anyone remembers it saying — along with the offer letter and any handbook or amendments. Employees should avoid discussing plans with colleagues. Employers should immediately preserve the departing employee's laptop, email, and system logs before any device is wiped and reissued, since that evidence is what later proves or disproves a violation.
Stage 2Weeks 1–3
Cease and desist and response
The employer sends a letter identifying the restraints it intends to enforce; the employee responds, often disputing enforceability. Many disputes end here. A letter overstating a covenant that would not survive § 103.465 can weaken the employer's position — and, if it interferes with the employee's new work, can support a damages claim against the employer.
Stage 3Weeks 2–8
Filing and the race for interim relief
Faster than most civil litigation, because injunctive relief is time-sensitive. An employer seeking a temporary injunction files with supporting declarations and exhibits; an employee may instead file first for a declaratory judgment that the covenant is void. Courts often grant interim relief before a full evidentiary hearing to preserve the status quo.
Stage 4Months 2–6
Threshold motions
Frequently, yes — at least in part. Because § 103.465 operates on the text, an employee can win on the pleadings where a restraint is facially overbroad, and courts routinely rule clause by clause: voiding some provisions per se while sending others to discovery. Employers also lose overreaching claims at this stage, particularly federal racketeering and false advertising theories that do not fit the conduct.
Stage 5Months 4–12
Discovery on the surviving restraints
The clauses that survived: what the employee actually did, which customers they had real contact with, what information was taken and whether it was genuinely confidential, and what the employer's protectable interest was. Forensic examination of devices and email is common, and protective orders are typically entered to shield customer data from the public record.
Stage 6Months 6–18
Resolution
Most settle, commonly on negotiated terms narrower than the original covenant — a shortened restricted period, a defined customer carve-out, or return-and-certify obligations for confidential information. Cases that reach trial are the exception, usually where damages are large or the parties genuinely dispute what was taken.
Glossary

Noncompete Terms, Defined

Non-compete agreement
A contract term barring an employee from working for a competitor, or in a competing capacity, for a set period after leaving. In Wisconsin these are governed by Wis. Stat. § 103.465 and are enforceable only if reasonably necessary to protect the employer, limited in time and territory, and not harsh or oppressive to the employee.
Restrictive covenant
The umbrella term for any post-employment restraint: non-competes, customer and employee non-solicits, confidentiality clauses, and no-hire provisions. Wisconsin's § 103.465 applies to all of them, not just the clause labeled "non-compete."
Non-solicitation clause
A promise not to approach the employer's customers, or not to recruit its employees, for a defined period. Customer non-solicits limited to accounts the employee actually serviced are among the most likely restraints to survive Wisconsin scrutiny, because they protect a real relationship rather than blocking competition outright.
Wis. Stat. § 103.465
Wisconsin's restrictive covenant statute, and the single most important rule in this area. It requires a restraint to be reasonably necessary to protect the employer — and if it is not, the covenant is void in its entirety. Wisconsin courts do not narrow overbroad restraints to save them.
Blue pencil doctrine
No. "Blue penciling" is the practice, allowed in some states, of trimming an overbroad restraint down to a reasonable one. Wisconsin rejects it. Under § 103.465 an unreasonable covenant is unenforceable as written, which means aggressive drafting risks losing the protection entirely.
Per se invalid
That the clause fails as a matter of law from its text alone, with no discovery or factual record needed. Wisconsin courts apply this clause by clause: a flat non-compete or a supplier restriction can be void per se while a narrower non-solicit in the same agreement survives and proceeds to the facts.
Trade secret
Under Wis. Stat. § 134.90, information — a formula, pattern, compilation, program, method, or technique — that derives independent economic value from not being generally known or readily ascertainable, and that the owner took reasonable measures to keep secret. Customer lists, pricing models, and technical drawings routinely qualify.
Confidential information
Confidential information is the broader category, defined by the contract rather than by statute — customer data, pricing, margins, business plans, supplier terms. A confidentiality clause can protect material that would not meet the stricter statutory trade secret test, which is why it is often an employer's most useful claim.
Injunctive relief
A court order requiring someone to stop doing something — competing, soliciting, or using confidential information — while the case proceeds. It is the remedy that usually matters most, because money damages rarely repair a lost customer relationship. Obtaining it requires showing likelihood of success, irreparable harm, and no adequate remedy at law.
Temporary injunction
Often within weeks of filing. A temporary injunction preserves the status quo pending trial, and courts can grant interim relief before a full evidentiary hearing. Because the standard requires irreparable harm, delay in seeking relief after discovering a violation can undercut the request.
Choice of law clause
It is influential but not automatically controlling. Courts weigh it alongside where the employee worked and lived, and a separate fight over venue often comes first. Because a covenant void in California may be enforceable in Wisconsin, which court hears the case frequently determines the outcome.
Declaratory judgment
Yes. A declaratory judgment action asks a court to rule that the restraint is unenforceable. Where the agreement is overbroad on its face, this can be resolved on the pleadings without full discovery — and it removes the uncertainty that makes a new employer hesitate to hire.
Cease and desist letter
Do not respond substantively before someone reviews the actual agreement. Many letters assert restraints that would not survive § 103.465. Note also that asserting an unenforceable covenant can itself expose the employer to a damages claim, so the letter is not automatically the strong position it appears to be.
Garden leave
An arrangement where the employer keeps paying the departing employee through the restricted period instead of simply barring them from working. Paid consideration during the restraint strengthens the employer's reasonableness argument, because the employee is not left without income.
Sale-of-business covenant
Genuine sale-of-business covenants are reviewed more leniently than employment restraints. But the label does not control: if signing the covenant was a condition of employment, Wisconsin courts apply § 103.465 regardless of what the document is titled.
The Law, Plain English

Wisconsin Statutes That Govern Noncompetes

The statutes that come up most often, translated out of legal language. The full analysis of how § 103.465 is applied lives on the Wisconsin law page.

Wis. Stat. § 103.465
Restrictive covenants in employment
The controlling statute for every restraint on this site. A covenant is enforceable only if it is reasonably necessary to protect the employer, reasonable in duration and territory, and not harsh or oppressive to the employee or contrary to public policy. Critically, a covenant that fails is void in its entirety — Wisconsin courts will not narrow it. The statute reaches non-solicitation and confidentiality provisions too, not just the clause titled "non-compete."
Wis. Stat. § 134.90
Wisconsin's Uniform Trade Secrets Act
Defines a trade secret as information deriving independent economic value from not being generally known or readily ascertainable, which the owner took reasonable measures to keep secret. It authorizes injunctions against actual or threatened misappropriation, damages, and — where the misappropriation was willful and malicious — up to twice actual damages plus attorney's fees.
Wis. Stat. § 943.70
Computer crimes
It can be. The statute makes it an offense to willfully, knowingly, and without authorization modify, destroy, access, take possession of, or copy data, programs, or supporting documentation. Where an employment agreement limits computer use to the employer's business purposes, accessing systems to benefit a competing venture can fall outside authorized use. Section 895.446 turns a violation into a private civil claim.
Wis. Stat. § 895.446
Civil claim for property crimes
Yes. This section creates a private cause of action for anyone damaged by an intentional violation of several criminal statutes, including theft (§ 943.20), identity theft (§ 943.203), and computer crimes (§ 943.70). Remedies include actual damages, costs, and attorney's fees — which is why these claims often outperform more exotic federal theories.
18 U.S.C. §§ 1836 et seq.
Defend Trade Secrets Act (federal)
Yes. The DTSA creates a federal civil claim for trade secret misappropriation, which allows a case to be filed in federal court. Its definition of a trade secret differs in wording from Wisconsin's, but the same facts frequently support claims under both. The DTSA also contains whistleblower immunity for disclosures made in confidence to a government official or attorney.
28 U.S.C. § 1404(a)
Transfer of venue
Yes. A federal court may transfer a case, for the convenience of parties and witnesses and in the interest of justice, to any district where it could have been brought. Courts weigh the plaintiff's chosen forum, party and witness convenience, access to evidence, familiarity with the governing law, local interest, and docket congestion. Witness convenience is typically the most important factor — and for remote employees, this motion often decides which state's law governs.
Frequently Asked Questions

Every Question, All Three Sides

General Questions

It depends on the specific clauses, and the honest answer usually requires reading the agreement. Wisconsin is one of the strictest states: under § 103.465, a restraint must be reasonably necessary to protect the employer and reasonable in time and territory, and if it is not, it is void entirely rather than narrowed. In practice, broad flat noncompetes often fail while narrower customer non-solicits and confidentiality clauses often survive — which is why the analysis has to go clause by clause rather than agreement by agreement.

Wisconsin sets no fixed limit, and there is no duration that is automatically safe. The test is functional: a restriction lasts only as long as is reasonably necessary to protect a legitimate interest. Where customer relationships turn over quickly or pricing information goes stale in months, a long restriction is difficult to justify. Because an unreasonable indivisible restraint is void entirely rather than shortened, an employer that reaches for an extra year can end up with nothing.

Generally no, and this is the most important single fact about Wisconsin noncompete law. Wis. Stat. § 103.465 provides that a covenant imposing an unreasonable restraint is void and unenforceable even as to any part of it that would have been reasonable. Wisconsin does not blue-pencil. There is one significant qualification: where restrictions are genuinely separate and divisible, Wisconsin courts have held they may be analyzed independently, so one invalid clause does not automatically void a separately drafted one.

Not necessarily a map-based one. Many modern agreements replace a geographic territory with a customer-based scope — restricting the accounts the employee actually served rather than an area — and a well-drawn customer limitation is often more defensible than a broad territory. What matters is that the scope tracks the employee's real working footprint. A statewide restriction for someone who covered three counties is a standard point of attack, and so is a restriction covering every customer of a company the employee served a slice of.

It is genuinely unsettled and often decided procedurally rather than substantively. Courts weigh the agreement's choice-of-law clause, where you worked and lived, and where the employer and its witnesses sit. A separate fight over venue frequently comes first, and because a covenant that is void in one state may be enforceable in another, the court that hears the case often determines the result.

The federal rule never took effect. The Federal Trade Commission issued a final rule in April 2024 that would have banned most noncompetes nationwide, but a federal court in Texas set it aside on a nationwide basis in August 2024 before its effective date, and the agency later moved to dismiss its appeals in favor of case-by-case enforcement. Wisconsin agreements continue to be governed by state law under § 103.465 — which is already among the strictest in the country. Federal activity here has moved repeatedly, so confirm the current position before relying on it.

It varies widely with how far the case goes. A review of the agreement and a response to a cease-and-desist letter is a contained expense, and many disputes end there. Contested injunction proceedings with forensic analysis and expert involvement cost substantially more. Note that many agreements include fee-shifting provisions favoring the employer if it prevails, which is a real factor in deciding how to respond.

For Employees

Possibly not as written. A covenant drafted around a role you no longer hold may no longer be reasonably necessary to protect the employer with respect to your current duties, and reasonableness is judged against the interest actually being protected. Significant changes in role, territory, or customer responsibility are all worth reviewing — as is whether a later agreement superseded the original.

Only if the restraint is enforceable and actually covers the new role. Employers frequently assert more than the agreement supports. Even where a covenant is valid, it may restrict only duties substantially similar to what you performed in your final months, within a defined geography — leaving room for a different role at the same competitor. Get the agreement reviewed before accepting or declining an offer.

You risk a lawsuit and, more immediately, a temporary injunction that can force you out of the new job while the case proceeds. You may also owe the employer's attorney's fees if the agreement shifts costs on successful enforcement. The better path is determining whether the restraint is enforceable before you act, not after your employer has moved for relief.

Often yes — being terminated does not automatically void a restraint. But the circumstances matter. Where the employer breached first, or where termination was without cause, that strengthens arguments that enforcement is harsh or oppressive and that the employer lacks a protectable interest worth restraining. If your exit involved a severance agreement, that document may also have modified the covenant.

Yes, potentially. Wisconsin applies § 103.465 clause by clause, so a void noncompete does not take the rest of the agreement with it. A confidentiality clause covering genuinely confidential information can remain fully enforceable — and independent of any contract, Wisconsin's trade secrets statute protects the employer's information regardless of what you signed.

Your general skills, knowledge, and professional experience are yours. What is not yours: customer lists, pricing sheets, technical drawings, quotes, forms the company created, and anything else the company built and protected. Emailing documents to a personal account or copying files to a drive before resigning is the single most common fact pattern in these cases, and forensic review reliably surfaces it.

For Employers

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.

For Employers Hiring Someone Restricted

Often yes. A restriction does not make a candidate untouchable — but the diligence belongs before the offer, not after a letter arrives. Get the actual agreements rather than the candidate's description of them, have someone read them against the role you are offering, and consider whether territory, accounts, product line or duties can be designed so the job does not conflict with what the restriction actually covers. If the whole value of the hire is the accounts they are restricted from touching, structuring will not fix that.

You can be named, and in Wisconsin departures that reach litigation new employers frequently are. Being named is not the same as being liable. Tortious interference requires proof of an existing contract, intentional interference, causation, damages and a lack of justification — and a claim built on a restriction that is void under § 103.465 has a serious problem. The more dangerous exposure is trade secret and confidential information claims, because those do not depend on the covenant. That risk is almost entirely self-inflicted: it comes from letting the new hire's former-employer files onto your systems.

Anything belonging to the former employer: customer lists and CRM exports, pricing sheets and quotes, internal presentations and strategy documents, downloaded files of any kind, product or technical material, and former-employer laptops, phones or drives. Put the instruction in the offer letter, repeat it on day one, and have the employee confirm in writing that they brought nothing. Brief the hiring manager too — managers create exposure by asking reasonable-sounding questions about a competitor's pricing or pipeline.

It depends on the specific hire rather than on a general rule. Indemnification can close a strong candidate who is otherwise afraid to move. It also transfers risk you may not have priced, can complicate your own defense, and in some circumstances is read as evidence that the company knew the hire was contested. Scope is everything — defense costs only or judgments too, capped or uncapped, conditioned on the employee's compliance or not. Work it out before the offer letter goes out.

Your company needs its own response strategy rather than relying on the employee's lawyer. Your interests overlap but are not identical: the employee's priority is keeping the job, yours includes limiting corporate exposure. Preserve everything including onboarding records and systems logs, verify what actually arrived on your systems and be certain of the answer, read the specific provision being asserted, and never instruct the employee to delete anything. Many of these resolve into a narrow, time-limited accommodation on named accounts.

Before You Hire

Questions to Ask a Noncompete Attorney

Noncompete and restrictive covenant law is a narrow specialty inside employment and business litigation. These are the questions worth asking before you retain anyone.

Have you litigated noncompete cases in Wisconsin specifically?
Wisconsin's § 103.465 is unusually strict, and counsel from other states routinely assumes a court can narrow an overbroad clause. Wisconsin cannot.
Do you handle both sides of these disputes?
It matters more than it sounds. A firm that only sues employees, or only defends them, has seen half the playbook. Knowing how the other side prepares is most of the value early on.
Is emergency relief realistic here, and how fast would we need to move?
Injunctions turn on irreparable harm, and delay undercuts it. An honest answer about whether relief is achievable is worth more than an aggressive letter.
What should I preserve right now, before anything else?
Devices, logs, and the agreement itself. Any lawyer who does not raise preservation in the first conversation is not thinking about how these cases are actually won.