If you run a business in Michigan or manage teams here, you have almost certainly wrestled with the same question: can you still rely on non-compete agreements to protect your customer relationships, confidential information, and hard-won competitive edge? The short answer is yes non-competes remain enforceable in Michigan for now, but the ground is shifting, and the smartest employers are already adapting their agreements and practices to the changing legal climate.
This article explains where Michigan law stands today, what “reasonableness” really means when a judge looks at a restrictive covenant, and how to draft, implement, and enforce agreements that actually hold up in court. It also walks through practical steps for onboarding and offboarding employees so you are positioned to prevent problems before they start and to respond quickly and credibly if they do. Finally, it flags developments on the horizon so your company can plan ahead rather than play catch-up.
Michigan permits non-compete agreements under the Michigan Antitrust Reform Act, which expressly allows “an agreement or covenant which protects an employer’s reasonable competitive business interests” so long as the restriction is reasonable in duration, geographic scope, and the type of activity restrained. Courts apply that statute case by case, asking whether the covenant goes no further than necessary to protect legitimate interests like customer goodwill, trade secrets, or investment in specialized training. If a restriction is broader than necessary, a Michigan court has authority to limit or “blue-pencil” it to a reasonable scope rather than throwing it out altogether. In practice, that means an over-broad two-year, nationwide ban might be cut down to six or twelve months in the territory where the employee actually worked, with the restrained activities narrowed to true competitive roles.
Although non-competes are legal in Michigan, they are never automatic. Judges scrutinize these agreements because they restrain employees’ ability to earn a living and limit competition. The employer bears the burden to show the restriction is reasonable and that it protects something more than simple fear of ordinary competition. Courts also consider the public interest: for example, Michigan courts have been wary when a covenant would substantially limit patients’ access to physicians in underserved communities or would muzzle employees far beyond any real risk to the employer’s business. The take-home is that enforceability depends on tailoring; generic boilerplate is not your friend.
On the national front, the Federal Trade Commission’s high-profile effort to impose a nationwide ban on most non-competes fizzled after litigation setbacks, leaving state law like Michigan’s to govern. Meanwhile, Michigan legislators have periodically floated bills that would dramatically narrow the kinds of non-competes employers can use, including proposals to prohibit such clauses for broad categories of workers or to require wage thresholds and advance notice language. None of those proposals’ changes today’s rules yet, but the trend is unmistakable: broad, untailored non-competes are increasingly disfavored, and businesses that lean instead on narrower restraints and strong confidentiality practices are better positioned for whatever comes next.
Because Michigan law turns on reasonableness, it helps to translate that legal standard into contract terms you can actually use. Start with duration. For rank-and-file sales or account roles, six to twelve months is a common, defensible window. Courts often view a year as long enough for the employer to stabilize client relationships and to leverage other protective tools like non-solicitation and confidentiality clauses. Longer durations may be defensible in narrow circumstances, say, for a senior executive with sweeping competitive intelligence but the broader the restriction, the more pressure you will face to justify every extra month.
Next, consider geography. A non-compete should align with the actual territory where the employee worked or had material influence. If a salesperson handled Michigan and northern Ohio, a covenant that bans them from working anywhere in the country will be tough to defend; a covenant focused on those states or even on the specific counties or named customers and prospects looks far more reasonable.
Scope also matters. Courts distinguish between true competitive activities and benign work that happens to be in the same industry. A clause that forbids the employee from joining any company that happens to operate in the broader market is vulnerable. By contrast, a clause that bars work in the specific role where the employee could leverage your confidential information or relationships say, “sales to accounts in the automotive tooling sector” or “pricing strategy within the XYZ product line” is much more likely to pass muster. This is where job-description-level specificity pays dividends.
A final aspect of reasonableness is consideration what the employee receives in exchange for the restriction. Michigan allows non-competes tied to an offer of employment at the start of the relationship, and continued employment can support later modifications in many settings, but the optics and fairness are far better if you offer clear, separate consideration for mid-stream covenants, such as a promotion, a raise, a bonus, or access to new trade secrets. It is also prudent to give candidates time to review any agreement before they accept the offer, and to encourage them to confer with counsel if they wish. Those process details impress courts and juries, and they reduce the risk that an employee later claims surprise or duress.
Even if your non-compete is carefully crafted, your most reliable day-to-day tools are usually non-solicitation and confidentiality provisions. Michigan courts generally view non-solicitation clauses as narrower and more targeted than non-competes, because they regulate specific behavior actively reaching out to your customers or poaching your staff without preventing a person from working altogether. A cleanly drafted customer non-solicitation clause prohibits activeoutreach to accounts the employee actually served or learned about through their job, while still allowing passive responses to inbound requests from the marketplace. You can also prohibit the use of internal pricing, playbooks, and strategic plans your soft assets to pursue business, even if the customer initiates contact. The key is to define the protected relationships with enough precision that the employee knows the limits and a court can enforce them, for example by referencing “customers or prospective customers with whom the employee had material business contact in the last twelve months of employment.”
Employee non-solicitation clauses, in turn, protect the investment you made in building a team. These clauses typically bar targeted recruiting of your people for a limited time. As with customer non-solicits, clarity and reasonableness are everything. Limit the restriction to those employees about whom the former employee learned sensitive information or with whom they worked closely, and avoid blanket language so broad that it functions like a back-door non-compete.
Confidentiality and trade-secret protections are the other pillar. Michigan’s Uniform Trade Secrets Act and the federal Defend Trade Secrets Act give you powerful remedies when someone misappropriates confidential information. But those statutes work best when your agreements and your policies are aligned. Define “confidential information” in a way that captures your real assets pricing, margins, customer lists, unreleased product roadmaps, bespoke code and models, supplier terms, process documentation and pair that definition with sensible obligations: use only for company business, share only on a need-to-know basis, store only on approved systems, and return or destroy at exit. Be sure your NDAs, employment agreements, and handbook policies say the same thing; inconsistency is ammunition for defense counsel.
The strategic benefit of leaning on non-solicitation and confidentiality is twofold. First, these provisions are more likely to be enforced nationwide even as some jurisdictions restrict non-competes. Second, they provide a story a judge can accept: you are not trying to stop someone from working the law views that as a last resort you are simply forbidding the use of your relationships and your confidential playbook against you.
With the legal standards in mind, here are the contract-drafting choices that most influence outcomes in Michigan courts. First, tailor the restriction to the role. Lift language from the real job description, memorialize the product lines and territories, and incorporate it into the covenant. Judges respond well to contracts that read like they were written for the specific hire, not copied and pasted from a generic template. When you are hiring a software engineer in Ann Arbor who will manage deployment of an internal data platform, a covenant that focuses on engineering leadership in data-platform design for automotive suppliers makes sense. A clause that bans the employee from “working for any technology company anywhere in North America” does not.
Second, define the protected interests. Spell out why the restriction is needed: exposure to pricing strategies, access to unreleased features, leadership of a small team with specialized know-how, or stewardship of long-standing customers. The more concrete you are about what needs protecting, the easier it is for a court to see why a six-month pause or a customer non-solicit is the least-restrictive means to accomplish that goal.
Third, include a reasonable modification clause that invites the court to narrow the covenant if any aspect is found over-broad. Michigan law already allows courts to modify restrictions, but an explicit contractual invitation both signals your good faith and gives a judge a clean path to a tailored injunction rather than a denial.
Fourth, avoid de-facto non-competes embedded in other covenants. For example, a non-solicitation clause that forbids contacting “any business in the industry” is simply a non-compete by another name. So is a confidentiality clause that defines virtually everything the employee knows as confidential, including publicly available information or the employee’s own general skills. Overreach in one clause can contaminate the whole agreement.
Finally, build in clean exit obligations: return of devices and data, deletion of personal copies, and a short, practical window for compliance. Require departing employees to certify compliance and to identify their next employer and role. That information often helps you decide whether to send a neutral reminder letter or to pursue a firmer response.
The best time to protect your business is before the new hire starts. Present the offer letter with any restrictive covenants attached, plainly labeled, and easy to review. Explain the purpose of the restrictions and how they are tailored to the role. Give the candidate time to read and ask questions, and avoid rushing signatures moments before orientation. If you are asking for a mid-stream covenant from a current employee, pair it with something of value an increase in compensation, a bonus, a promotion, or access to new confidential domains and give advance notice and time to consult counsel.
At onboarding, walk the new employee through your trade-secret and information-security policies so they understand exactly how to handle confidential materials. Have them acknowledge the policies in writing and complete any technical steps needed to enroll in secure systems, multifactor authentication, and access-control protocols. Make clear that they must not bring or use any confidential information from a prior employer. That message does more than keep you out of trouble; it also shows courts you operate in good faith and respect others’ information, which pays dividends if litigation ever arises.
It is also wise to calibrate the scope of access during the first months in role. Provide what the employee actually needs to do the job, resist the urge to add them reflexively to every repository “just in case,” and document decisions about who has access to which datasets, codebases, and pricing folders. Courts regularly consider whether the employer took reasonable steps to protect information; thoughtful access control is one of those steps.
When an employee gives notice or when you decide to terminate move through a scripted exit process. Recover all devices, credentials, and physical materials. Revoke access to systems promptly but gracefully; the tone matters, especially when you later ask a judge to view you as the reasonable party. Conduct a focused exit interview that confirms where the employee is heading, what their role will be, and whether any of your trade secrets will overlap with their new responsibilities. Ask the employee to reaffirm that they have returned all information and will honor their post-employment obligations.
A courteous, neutral reminder letter mailed to the employee and their new employer can be tremendously effective. Rather than threatening litigation, summarize the obligations confidentiality, return of information, and any non-solicitation or non-compete explain the limited duration, and ask for written confirmation that the new role will not require or encourage misuse of confidential information. Most good-faith employers will cooperate, clarify responsibilities internally, and help the employee steer clear of restricted activities. If, however, you receive a hostile response or credible evidence of misconduct, your documented, measured approach becomes powerful evidence when you ask a court for an injunction.
Not every concern warrants a lawsuit. Start with fact-gathering: review access logs, email and file-transfer histories, and any unusual downloads in the weeks before departure. Interview team members who worked closely with the employee. Preserve devices and cloud logs in case forensic review is necessary. If the facts support it, send a second, firmer letter that identifies the specific conduct at issue and demands corrective action return of files, deletion and certification, or adjustments to the employee’s new role to avoid restricted activity. Many disputes resolve at this step.
When litigation is necessary, timing and narrowness matter. Michigan courts often grant temporary restraining orders or preliminary injunctions to stop active misappropriation or solicitation while the case proceeds. Judges prefer targeted remedies: forbidding contact with named customers for a defined period, requiring forensic return and deletion of specific files, or barring work on a competing product line until confidential projects you launched go to market. You are far more likely to win those targeted orders if your own contract language and your requested relief are tailored to the risk.
Remember that enforcement is not only about punishment it is about restoring a level playing field. Courts are more receptive when you explain concretely how the former employee’s new role would allow the use of your information in ways that cannot practically be monitored. For example, if a departing pricing analyst knows your unreleased Q4 discounting plan, a short-term bar on pricing responsibilities for a competitor may be the least-restrictive way to neutralize that edge. That kind of story, grounded in real facts, outperforms abstract appeals to “fairness” every time. Because Michigan does not mandate a wage threshold or paid garden leave for non-competes, employers sometimes conclude that they can impose the same restrictions on every employee regardless of role or pay. That approach is risky. A covenant that restrains an entry-level coordinator will face far more skepticism than one limited to a senior salesperson or engineer with significant exposure to confidential information and customer strategy. Use non-competes sparingly, and only when a narrower non-solicitation and strong confidentiality cannot adequately protect the interest at stake.
Likewise, be thoughtful about notice language and timing. If you require employees to disclose prospective employers and roles during their notice period, keep the requirement reasonable and consistent with privacy and labor-law considerations. When you ask for a certification that they are not taking data, provide a specific, practical checklist rather than vague generalities. Courts reward employers who look like problem-solvers, not bullies.
Even though Michigan law continues to permit reasonable non-competes, reform proposals surface regularly. Some would limit non-competes to highly compensated employees, others would ban them outright for broad categories of workers, and still others would require specific, conspicuous notice language at the time of the job offer. Nationally, the trend is similar: many states have narrowed or banned non-competes for low-wage workers, and the federal conversation despite the FTC’s retreat continues to cast doubt on blanket restrictions. The upshot for Michigan employers is not panic, but preparation.
Begin by auditing your current agreements and templates. If you rely heavily on non-competes, consider re-balancing toward non-solicitation, confidentiality, and invention-assignment clauses, and make sure your trade-secret and information-security practices are strong enough to persuade a court that your information truly is confidential. For roles where a non-compete remains justified, shorten the duration, tighten the geography, and tie the restriction to the exact competitive activity that creates the risk. These moves will improve your position under today’s law and will leave you far less exposed if tomorrow’s rules become narrower.
Certain roles heighten both business risk and judicial skepticism, and employers should adjust accordingly.
Sales and account management present the classic non-compete scenario: a popular salesperson with deep customer relationships leaves and immediately begins soliciting the same book of business. Michigan judges often prefer customer non-solicitation for those roles because the harm is about relationships, not about general employment. You may still justify a short non-compete when a salesperson had unusual access to pricing strategy or when the industry’s sales cycle is so brief that a non-solicit alone cannot prevent the unfair head start. Either way, name the protected customers or define them by concrete criteria and keep the duration tight.
Technology and product roles involve different risks source code, data models, unreleased roadmaps, and platform architecture. Here, non-competes can be defensible if the employee’s knowledge would allow them to shortcut years of R&D, but confidentiality and invention-assignment agreements, robust access controls, and careful exit procedures usually do most of the work. Courts understand that engineers cannot “un-know” core design choices, but they also resist restraints that limit an engineer’s ability to ply their trade when confidentiality controls could address the concern.
Healthcare provokes strong public-interest considerations. Michigan has enforced physician non-competes in some settings but has trimmed or rejected them when they would meaningfully reduce patient access. If you operate in a rural or specialty area with limited providers, expect close scrutiny. Tight geographic limits, short durations, and a focus on practice areas where the doctor actually worked are essential.
Finally, mergers and acquisitions often involve non-competes tied to the sale of a business. Courts treat these differently from employment non-competes because the seller receives significant consideration and the buyer is protecting the goodwill it purchased. Even so, reasonableness still matters. Calibrate duration and geography to the market realities of the business being sold, and avoid one-size-fits-all templates that ignore the specific industry and competitive landscape.
To summarize what Michigan employers should do now, think in terms of tightening, substituting, and operationalizing. Tighten your remaining non-competes shorten terms, narrow territories, and define competitive activities with job-level precision. Substitute where you can: rely on customer and employee non-solicitation, confidentiality and trade-secret protections, and clean invention-assignment clauses to accomplish most of your goals with less legal risk. Operationalize your protection: maintain disciplined onboarding and offboarding routines, control access to sensitive assets, and train managers to spot red flags early. These are not academic suggestions; they are the habits that win credibility with judges and deter problems before they escalate.
Michigan law remains hospitable to reasonable restrictive covenants, and courts are willing to enforce them when an employer acts like a responsible steward of legitimate interests rather than an overreacher. But the direction of policy and the expectations of courts reward employers who right-size their contracts and their practices now. If you have not revisited your agreements in the last year, do not wait for a headline-grabbing case to force your hand. Review them with experienced counsel, align them with the roles you actually have, and build the surrounding policies that make enforcement straightforward rather than combative.
Disclaimer
This article provides general information about Michigan law and is not legal advice. The facts of each situation matter, and laws and regulations can change. If you need advice for a specific matter, consult an attorney licensed in Michigan.
Contact Tishkoff
Tishkoff PLC specializes in business law and litigation. For inquiries, contact us at www.tish.law/contact/. & check out Tishkoff PLC’s Website (www.tish.law/), eBooks (www.tish.law/e-books), Blogs (www.tish.law/blog) and References (www.tish.law/resources).
Sources
- Michigan Antitrust Reform Act, MCL 445.774a (reasonableness of employee non-compete agreements). https://www.legislature.mi.gov/Laws/MCL?objectName=MCL-445-774A
- Michigan Uniform Trade Secrets Act, MCL 445.1901 et seq., and Defend Trade Secrets Act, 18 U.S.C. § 1836 et seq. (trade-secret definitions and remedies). https://libguides.law.umich.edu/c.php?g=1337978
- St. Clair Medical, P.C. v. Borgiel, Michigan Court of Appeals (reasonableness and public-interest considerations in physician covenants). www.michbar.org/file/barjournal/article/documents/pdf4article1139.pdf
- Certified Restoration Dry Cleaning Network, L.L.C. v. Tenke Corp., 511 F.3d 535 (6th Cir. 2007) (injunctive relief and enforcement of restrictive covenants under Michigan law). www.govinfo.gov/content/pkg/USCOURTS-miwd-1_25-cv-00579/pdf/USCOURTS-miwd-1_25-cv-00579-1.pdf
- Federal Trade Commission, Non-Compete Clause Rule rulemaking record (withdrawn), and Michigan House Bill 4040 (2025 session) (policy developments affecting non-competes). https://www.ftc.gov/news-events/news/press-releases/2024/04/ftc-announces-rule-banning-noncompetes
Prepared by Tishkoff PLC — Ann Arbor business attorneys counseling Michigan employers on restrictive covenants, trade-secret protection, and fair competition.