In Ohio, you can enforce non-competes and non-solicits if you show a legitimate business interest, real harm, and a restraint no broader than necessary under *Raimonde v. Van Vlerah*. You’ll win more often with limits tied to actual sales cycles, the territory the employee worked, and specific risky functions—not “any job in the industry.” Courts may narrow overbroad terms and enforce what’s reasonable. You’ll also need clean consideration and consistent paperwork to see how judges trim.
Most Ohio non-compete disputes turn on the same core question: is the restriction reasonable in light of the facts? You should expect courts to run a familiar checklist from Raimonde v. Van Vlerah: you must show a legitimate business interest, actual or threatened harm, and a restraint no broader than necessary. You’ll also face Ohio’s blue-pencil power—courts can modify and enforce what’s supportable, so draft with that in mind to avoid non-compete pitfalls. You should document access to trade secrets, customer relationships, and specialized training, and tie them to the role rather than to a generic fear of competition. When you seek an injunction, you’ll need clear evidence, prompt action, and consistency across agreements to sidestep non-solicitation traps and defeat waiver arguments.
Ohio courts apply that Raimonde checklist by testing the contract’s actual terms—how long the restriction lasts, where it applies, and what work it bars—and they’ll narrow any piece that overshoots. You’ll usually defend time limits tied to real ramp-up or sales cycles; open-ended or multi-year bans invite judicial trimming. For territory, don’t default to “anywhere we do business.” Define the market scope to where you actually compete or where the employee worked; overbroad geography is a classic drafting pitfall. For the scope of activity, bar only the specific functions that create competitive risk; “any job in the industry” looks punitive. Build modular definitions and severability so a court can blue-pencil cleanly and preserve the core restraint.
Why do Ohio courts enforce a restraint at all? Because under *Raimonde v. Van Vlerah*, you can protect legitimate competitive value, not punish mobility. When you draft non-compete basics and non-solicit nuances, anchor them to interests a judge can see, measure, and tie to your market-facing innovation.
Show evidence: access logs, role-based permissions, customer assignment history, and training records.
Even when you can point to trade secrets, customer goodwill, or specialized training, a non-compete still fails in Ohio if the paperwork and the deal mechanics don’t hold up. Courts start with contract basics and the reasonableness framework in *Raimonde v. Van Vlerah*, but they’ll never reach the merits if your document shows unenforceable drafting.
Watch for red flags. If you add restrictions after hire, you need fresh consideration—raise, bonus, promotion, equity, or other bargained-for benefit. Don’t rely on “continued employment” language unless your facts support a real exchange. Confirm signatures, dates, and entity names match the employer and the worker. Tie definitions to actual products, roles, and customers, and keep the agreement consistent with your policies and offer letters.
When a non-compete sweeps too far, what do you actually get in court—an all-or-nothing loss, or a narrowed order you can live with? In Ohio, you’ll often see courts reform, not void, restrictions under *Raimonde v. Van Vlerah*, aiming for terms no greater than needed to protect legitimate business interests. Those blue pencil outcomes can save a deal, but they also inject uncertainty: you’re litigating the rewrite.
If you draft overly broad noncompetes, expect judicial tailoring—not innovation-friendly predictability.
If you want your Ohio non-compete or non-solicit to survive, you can’t ask for the moon. Courts apply the *Raimonde* reasonableness test and will protect only legitimate interests, such as customer relationships, confidential information, and key training. If your terms wander into “overly ambitious” territory—too long, too broad, or unsupported by real consideration—judges may trim them under Ohio’s blue‑pencil power, or quietly send them packing altogether. Draft like you expect litigation.
