When a key hire walks out the door with a customer list and joins a competitor, a Minnesota CEO no longer has the noncompete tool that once made the answer simple. The good news: three statutory tools survived the 2023 ban, and a fourth (assignment of inventions) was never threatened. Under Minn. Stat. § 181.988, the same statute that voided employee noncompetes expressly preserved nondisclosure agreements, nonsolicitation agreements, agreements designed to protect trade secrets or confidential information, and the limited sale-of-business carve-out. The mistake most employers made after the ban was assuming everything restrictive was gone. What changed is one tool. The infrastructure for protecting confidential information is still there, and our Minnesota employment law practice sees it most often when the policies, agreements, and exit procedures were never lined up before the departure.
Minnesota remains an at-will state by common-law default, but layered statutory protections make it one of the more employee-protective states in the country. The post-2023 picture for confidential information is consistent with that: the law lets you protect what is genuinely yours, but it polices the agreements you use to do it.
What did Minnesota’s noncompete ban actually do?
Minnesota’s 2023 noncompete ban voided employee noncompetes outright but expressly preserved the tools most employers actually need. Section 181.988 subdivision 2(a) declares that “any covenant not to compete contained in a contract or agreement is void and unenforceable.” Subdivision 1(a) defines what counts as a covenant not to compete and, in the same breath, lists what does not: “A covenant not to compete does not include a nondisclosure agreement, or agreement designed to protect trade secrets or confidential information. A covenant not to compete does not include a nonsolicitation agreement, or agreement restricting the ability to use client or contact lists, or solicit customers of the employer.”
The carve-out is the answer. An employer can still require an NDA, a customer-nonsolicit, an employee-nonsolicit, and a trade-secret protection agreement. What an employer cannot do is restrict where the employee works next or in what role. There is a narrow sale-of-business exception (the seller of a business and its principals can agree to a temporary, geographically limited noncompete) and an anticipated-dissolution exception, but neither applies to ordinary employment. For more on how the ban reshaped the trade-secret landscape from the protection side, see our companion piece on what still protects your trade secrets after the ban.
What can a Minnesota NDA actually cover after 2023?
A Minnesota NDA can cover information that is genuinely confidential, identified with enough specificity that the employee knows what is restricted, and reasonable in duration and scope. The 2023 noncompete ban did not change NDA standards; it left them governed by Minnesota common-law contract construction. What the legislature did do is keep one rule loud: an NDA cannot reach the employee’s own wages.
Under § 181.172, an employer cannot require an employee to sign a document waiving disclosure rights for the employee’s own wages, but § 181.172(b)(2) preserves the employer’s protection of proprietary, trade-secret, and privileged information. The wage carve-out is narrow but absolute. A standard NDA that says nothing about wages is fine; an NDA that defines “confidential information” so broadly that it sweeps in compensation creates a § 181.172 problem. For drafting standards Minnesota courts apply when an NDA gets challenged, our NDA enforceability guide and the deeper drafting standards in what Minnesota courts require of NDAs that hold up cover the practical drafting points.
The recurring drafting pattern I see is overreach: definitions written to capture everything the employee touches at work. Minnesota courts read those clauses narrowly and, where appropriate, equitably modify them to a reasonable scope rather than blue-penciling individual words. An overbroad NDA produces less protection than a well-targeted one.
How do nonsolicitation agreements differ from noncompetes?
A nonsolicit restricts the former employee from contacting customers, prospects, or coworkers; a noncompete restricts the employee from working for a competitor at all. Section 181.988 subdivision 1(a) draws this line in the statute itself: a covenant not to compete “does not include a nonsolicitation agreement, or agreement restricting the ability to use client or contact lists, or solicit customers of the employer.” Both customer nonsolicits and employee nonsolicits remain available, subject to common-law reasonableness review.
Reasonable in Minnesota generally means tied to actual customer relationships the employee built or had access to, limited in duration to the period the relationship retains commercial value, and not so broad that it functions as a noncompete in disguise. A nonsolicit that bars the former employee from “any” potential customer in the industry is the kind of clause courts narrow to identifiable accounts. The cleanest nonsolicits identify customer types or accounts the employee actually serviced and time-limit the restriction to the period during which that customer relationship would otherwise atrophy on its own. For drafting language Minnesota employers commonly use, our sample employment agreement template shows the pattern.
A separate Minnesota statute, Minn. Stat. § 181.9881 subd. 2(a), voids no-poach restrictions imposed by service-provider businesses on their customers (“No service provider may restrict, restrain, or prohibit in any way a customer from directly or indirectly soliciting or hiring an employee of a service provider”). If you run a staffing, consulting, or contract-services firm, the no-hire clauses you may have used in customer agreements no longer survive.
Does the Minnesota Uniform Trade Secrets Act protect us when there’s no noncompete?
Yes. The Minnesota Uniform Trade Secrets Act (“MUTSA”) protects information that meets a two-part test, and the protection runs in parallel to whatever NDA you have in place. Under Minn. Stat. § 325C.01 subdivision 5, a trade secret is information that “derives independent economic value, actual or potential, from not being generally known to, and not being readily ascertainable by proper means by, other persons who can obtain economic value from its disclosure or use,” and “is the subject of efforts that are reasonable under the circumstances to maintain its secrecy.”
Misappropriation under § 325C.01 subdivision 3 covers acquisition by improper means, and disclosure or use without consent by someone who knew or should have known the information came through improper means or carried a duty of secrecy. Remedies sit in the rest of chapter 325C. Minn. Stat. § 325C.02 authorizes injunctions against actual or threatened misappropriation. Minn. Stat. § 325C.03 provides damages: actual loss plus unjust enrichment, or alternatively a reasonable royalty, with exemplary damages of up to twice the compensatory award available for willful and malicious misappropriation. The result is that an employer with a real trade secret and reasonable protective measures already has the most powerful single tool in the post-noncompete toolkit. Our MUTSA primer for business owners covers the litigation mechanics in more depth.
What “reasonable measures” must we take to keep trade-secret status?
Information loses trade-secret status if the employer didn’t actually treat it as a secret. This is the second prong of the § 325C.01 definition, and in my practice it is where most trade-secret claims wobble at the threshold. The employer has a real secret. The employer just never confirmed it that way in writing.
Reasonable measures means a layered set of practices: identifying which categories of information are confidential, marking documents accordingly, restricting electronic access on a need-to-know basis, requiring an NDA at hire, training employees on what is confidential, conducting exit interviews that require return of materials and electronic deactivation, and maintaining a written confidentiality policy in the handbook. Not every measure is required for every business; what counts as reasonable scales with the value of the information and the size of the workforce. A two-person consulting firm and a 200-person manufacturer can both meet the standard with appropriate measures, but neither can meet it with no measures. For the post-termination piece (which is where most disputes surface), our article on former-employee data access boundaries covers the practical exit playbook.
The single most common gap I see is in the exit step: the employee leaves, the laptop comes back, and nobody confirms in writing what was returned, what was deleted, and what continues to be confidential.
Who owns inventions and work product an employee creates?
An invention assignment clause is enforceable under Minnesota law when the invention used employer resources or relates to employer business, with a statutory carve-out for purely personal inventions. Minn. Stat. § 181.78 subdivision 1 says an assignment provision “shall not apply to an invention for which no equipment, supplies, facility or trade secret information of the employer was used and which was developed entirely on the employee’s own time” if the invention either does not relate to the employer’s business or anticipated research and development, or does not result from any work performed for the employer.
Read against that text: anything an employee invents on company time, using company equipment, or that relates to the employer’s business or planned research, can be assigned. What cannot be assigned is the side project an employee builds at home on a personal laptop, with no relation to what the employer does. Subdivision 3 also requires written notice of the carve-out when the agreement contains an assignment clause, which is the drafting detail most agreements miss. For the broader contractual treatment of invention disclosure in employment agreements, see our piece on invention disclosure requirements in employment contracts.
How does federal trade-secret law (DTSA) work alongside Minnesota’s protections?
The federal Defend Trade Secrets Act (“DTSA”) gives employers a parallel federal claim for trade secrets used in interstate commerce, on top of the MUTSA claim. Under 18 U.S.C. § 1836, the owner of a trade secret related to a product or service used in interstate or foreign commerce may sue in federal court. Remedies parallel MUTSA: injunctive relief, actual damages plus unjust enrichment, reasonable royalty as an alternative, exemplary damages up to twice the compensatory amount for willful and malicious misappropriation, and attorney fees in defined cases.
One DTSA detail matters for Minnesota employers specifically: the statute expressly bars federal injunctions that “prevent a person from entering into an employment relationship” based on knowledge alone, requiring instead “evidence of threatened misappropriation and not merely on the information the person knows.” That language confirms that the federal track does not reintroduce a noncompete by the back door. A federal trade-secret injunction has to be tied to threatened misappropriation, just like the state-law version. The practical use of the DTSA option is jurisdictional: federal court may be preferable for diverse parties, multistate operations, or cases where federal procedural tools (ex parte seizure under § 1836(b)(2), available in extraordinary circumstances) match the facts.
What infrastructure has to be in place for any of this to work?
Statutes provide the remedies. Internal infrastructure determines whether you can use them. The four legal tools above presume an employer that has done the underlying work: a confidentiality policy in the handbook, a signed NDA at hire (with consideration if mid-employment), identification of what counts as a trade secret, access controls that match the identification, an invention-assignment clause with the § 181.78 notice, and an exit checklist that returns devices, deactivates accounts, and documents what the employee took with them and what the employer recovered.
In a typical post-departure dispute, the legal question is rarely whether the employer had a tool. It is whether the employer used the tool before the departure happened. The employee who signed an NDA on day one, was reminded of the obligation at termination, and was offboarded on a documented checklist creates a defensible record. The employee who had no NDA, no exit interview, and no written confirmation of what was returned creates the opposite. For the severance-stage version of these issues, see our discussion of NDA implications in severance agreements and the related questions in wrongful termination and NDAs.
The cleanest pattern I see in companies that handle departures well is that the agreements, the handbook, the access controls, and the exit checklist were all built before the company had a problem. The companies that get caught short are the ones where each piece was added after a different incident, and the pieces never quite line up. The broader picture for these protections sits within our Minnesota employment law practice materials.
Can I require an NDA from an existing employee without giving new consideration?
Minnesota courts have treated mid-employment restrictive covenants as requiring some independent consideration beyond continued at-will employment in most fact patterns; the safer practice is to pair the NDA with a documented benefit such as a raise, a bonus, equity, or a real change in duties, signed and dated. The 2023 noncompete ban left this common-law contract rule untouched.
Does a confidentiality clause stop a former employee from discussing wages?
No. Minnesota law expressly forbids employers from gagging wage discussions, regardless of NDA language. Treat wage information as a carve-out in every NDA. Proprietary information, trade-secret information, and privileged material remain protectable; pay rates, even your own, do not.
Is a noncompete signed before August 1, 2023, still enforceable?
In principle, yes. The 2023 ban applied to noncompetes agreed to on or after the effective date; pre-existing covenants remain governed by Minnesota common-law reasonableness review. Some courts may also apply Minnesota choice-of-law and venue limits when an employer seeks to enforce a pre-existing covenant against a current Minnesota employee, but that question is unsettled.
Can I sue under MUTSA if I cannot prove the employee actually used the information yet?
Yes. The Minnesota Uniform Trade Secrets Act authorizes injunctions for actual or threatened misappropriation. Threatened misappropriation, typically shown by the employee taking files to a direct competitor in a matching role, is independently enjoinable. You do not have to wait for measurable harm to file.
Do I owe attorney fees if I sue to enforce a noncompete that turns out to be void?
You may. Minnesota’s noncompete ban authorizes courts to award reasonable attorney fees to an employee enforcing rights under the statute. The trade-secret act has its own two-way fee-shifting if a misappropriation claim is brought in bad faith. Filing a void noncompete claim carries real downside.
For Minnesota employers, the post-2023 picture is more workable than the headline suggests. The noncompete tool is gone, but the tools that actually protect confidential information (NDAs, nonsolicits, MUTSA trade-secret protection, invention assignment, and the federal DTSA layer) remain available and, used together, cover the same practical ground for most businesses. What changed is the discipline required: agreements have to be drafted within statutory limits, infrastructure has to be in place before a key departure, and exit procedures have to actually run. If you are weighing how your current employment agreements, handbook, and offboarding procedures hold up against Minnesota’s employment law framework, email [email protected] with a short description of the situation and the relevant documents.
