No-Hire and No-Solicitation Clauses: Drafting the Difference Between a Restriction That Holds and One Courts Void

Your agency just lost three senior developers to a client you introduced them to last year. The exit interviews mention "better opportunities," but the client's LinkedIn page now shows all three as new hires starting Monday. You pull out the service agreement and find a single sentence: "The parties agree not to solicit each other's employees during the term of this Agreement." The clause exists. It's just toothless — no definition of "solicit," no time limit, no remedy, and the agreement expired six months ago. A judge will dismiss that claim before you finish your opening paragraph.

No-hire and no-solicitation provisions are among the most commonly misunderstood restrictions in commercial contracts. Business owners often treat them as interchangeable boilerplate, dropping a standard line into agreements without realizing that courts apply distinct legal tests to each type. The difference between a clause that holds and one that gets voided frequently comes down to five or six words — and which state law governs. This article walks through the legal rules, the drafting mechanics, and the failure points for both types of restrictions, whether you are placing them in a service agreement, a subcontractor deal, or a B2B arrangement between legal entities. You can also explore our full template catalog at /docs for starting-point documents across all of these agreement types.

What Is a No-Hire Clause and How Does It Differ from No-Solicitation?

A no-hire clause prohibits one party from hiring — or even offering to hire — specified individuals, regardless of who initiated the contact. If your former contractor applies directly to your client without any encouragement and the client extends an offer, a no-hire clause blocks that transaction entirely. The operative verb is "hire," and the restriction attaches to the act of employment, not the act of recruiting.

A no-solicitation clause is narrower: it prohibits active recruiting, approaching, or inducing employees or clients to leave. If the employee sends an unsolicited application — found the job posting independently, applied without prompting — a pure no-solicitation clause may not cover that scenario at all. Courts have split on this. Some hold that responding to an unsolicited application is not "solicitation." Others look at whether there was any indirect targeting. Without a clear definition in the contract, you are litigating dictionary definitions, which is expensive and unpredictable.

This is why sophisticated drafters often combine both restrictions in a single clause, using "solicit, recruit, induce, encourage, or hire" as the operative verbs. The sample language below incorporates this approach. If your current service agreement template uses only the word "solicit," you may have a gap that a determined counterparty can drive a truck through.

The Legal Framework: Why These Clauses Get Scrutinized

No-hire and no-solicitation clauses restrict trade. Every state applies a reasonableness test before enforcing them, and the underlying federal doctrine derives from Section 1 of the Sherman Antitrust Act (15 U.S.C. § 1), which prohibits contracts that unreasonably restrain trade. The DOJ has, in recent years, signaled clearly that naked no-hire agreements between competing employers — those not ancillary to a legitimate business transaction — can constitute per se antitrust violations.

The DOJ/FTC joint guidance on human resources practices, first published in 2016 and reinforced through subsequent enforcement actions, distinguishes "naked" restraints from "ancillary" ones. A no-hire clause in a genuine service contract, tied to a real commercial relationship, is analyzed under the rule of reason and generally survives scrutiny if the scope is reasonable. A mutual no-hire clause between two competing staffing firms with no underlying transaction is a different matter — the agencies have stated publicly that such arrangements can trigger criminal exposure, not just civil liability.

For clauses between individuals — a solo consultant agreeing not to hire your staff after a project ends — state contract law governs entirely. Courts focus on whether the restriction is reasonably necessary to protect a legitimate business interest such as trade secrets, client relationships, or specialized training investment. Unlike non-competes, most states do not require no-hire or no-solicitation clauses to be supported by independent consideration beyond the underlying contract itself. But overbroad provisions will still be voided or narrowed.

No-Solicitation of Employees: What Courts Actually Require

Employee no-solicitation clauses in service agreements are generally treated more favorably than employee non-competes, because they restrict the other party's recruiting behavior rather than an employee's freedom to work elsewhere. Courts still require, at minimum, three elements for the clause to be enforceable:

• A defined class of protected employees. Broad provisions covering "all employees" or "all personnel" regularly fail. Courts expect you to identify the employees who were actually exposed to confidential information or who represent meaningful competitive value — "employees who directly participated in the performance of services under this Agreement," not "all current and future employees of Service Provider."
• A defined time period. Perpetual no-solicitation clauses are void in virtually every jurisdiction. Courts consistently accept twelve to twenty-four months measured from the date of expiration or termination of the agreement. Restrictions measured from the date of first contact, or that run indefinitely "during any ongoing business relationship," are routinely voided.
• A defined scope of prohibited conduct. "Solicit, recruit, induce, or encourage" covers active recruiting. If you want to prevent passive hiring as well, you must add "or hire" to the list. If you want to prevent referrals through third parties, say so explicitly — courts will not read that in.

Here is sample language that has survived judicial scrutiny in multiple jurisdictions:

"During the term of this Agreement and for a period of twenty-four (24) months following its expiration or termination for any reason, neither party shall directly solicit, recruit, induce, encourage, or hire any employee or independent contractor of the other party who was personally involved in the performance of services under this Agreement. This restriction shall not apply to employees or contractors who respond to general public employment advertisements not directed specifically at the other party's personnel, or to any individual who was separated from the other party's employ or engagement more than ninety (90) days prior to any contact."

The ninety-day separation carve-out and the general advertising carve-out are both essential. Courts in Delaware, New York, and Illinois have voided otherwise reasonable no-solicitation clauses that would have prevented a company from hiring someone who applied through a standard job board, or who had already been let go weeks before the other party made contact. Include both carve-outs in your draft from the start.

No-Solicitation of Clients: The Pre-Existing Relationship Problem

Client no-solicitation clauses raise a separate set of issues. The most common drafting error is restricting solicitation of "any client" of the other party — including clients the restricted party introduced to the deal, or clients they had a relationship with before the contract began. Courts in New York, Texas, and California have consistently blue-penciled or voided provisions that reach clients the restricted party brought to the relationship.

The practical rule: limit the restriction to clients who (a) were introduced through the specific business relationship, and (b) with whom the restricting party does not have a pre-existing, documented relationship. "Client" alone is not a definition — specify whether it includes prospects, referral sources, or only parties who actually executed agreements.

The consulting agreement template we recommend as a starting point includes a client no-solicitation provision with this structure:

"For a period of eighteen (18) months following expiration or termination of this Agreement, Contractor shall not directly solicit any client of Company whose identity or business relationship Contractor learned solely through its engagement under this Agreement. This restriction does not apply to any client or prospect with whom Contractor maintained a documented business relationship prior to the Effective Date of this Agreement, as identified in Exhibit A (Pre-Existing Relationships), or to any client who independently contacts Contractor without any encouragement by Contractor."

The Exhibit A reference is not just formality — it is your evidence if the restriction is ever disputed. Pre-existing client relationships should be listed at signing with enough specificity (company name, nature of relationship, approximate start date) to be useful in litigation. If they are not documented at execution, both parties will spend money reconstructing intent from emails two years later.

No-Hire Clauses Between Legal Entities: The Antitrust Dimension

When two businesses — not just individuals — agree mutually not to hire each other's employees, the antitrust analysis becomes more significant than most drafters appreciate. The DOJ has secured criminal convictions against executives who entered naked no-hire agreements even when those arrangements were embedded in written documents rather than purely oral agreements.

The key test remains whether the no-hire clause is "ancillary" to a legitimate commercial transaction. If Company A is outsourcing its IT infrastructure to Company B, a clause preventing B from hiring A's in-house IT team during and after the engagement is ancillary and generally lawful. If A and B are both technology staffing firms and insert a mutual no-hire with no underlying services relationship, that looks much more like a naked restraint on labor market competition.

No-hire clauses between legal entities should always:

• Be tied to a specific contract and described business purpose, not inserted as standalone agreements
• Identify specific categories of personnel (senior engineers, account managers) rather than covering all employees of both organizations
• Include a time limit matching the engagement duration plus a reasonable tail (twelve to twenty-four months)
• Include a severability clause in case the restriction is found overbroad under the law of any relevant jurisdiction
• Be reviewed for antitrust implications when both parties compete for the same labor pool

If you draft or create this type of clause in a B2B agreement without thinking through the antitrust implications, you risk not just having the clause voided — you risk a government investigation. That is an unusual outcome but a real one, and the cost of prevention is a thirty-minute conversation with antitrust counsel.

The FTC Rule and Its Aftermath: What the 2025–2026 Landscape Means

In April 2024, the FTC published a final rule purporting to ban most non-compete clauses nationwide (16 C.F.R. Part 910). A federal district court in Texas vacated the rule in August 2024 in Ryan LLC v. FTC (N.D. Tex., No. 3:24-cv-986), and as of mid-2026 the nationwide ban is not in effect. However, the FTC's enforcement posture and several state legislative responses have had a demonstrable ripple effect on how courts and practitioners view related restrictions, including no-hire and no-solicitation clauses.

Minnesota enacted Minn. Stat. § 181.988, effective January 1, 2023, voiding all post-employment non-compete clauses for Minnesota-based employees. Several practitioners and at least one Minnesota trial court have extended the reasoning of this statute to employee no-solicitation provisions that function as de facto non-competes — broadly restricting where employees can work rather than merely preventing targeted recruiting. The outcome of this interpretation is still developing, and businesses with Minnesota employees should verify with local counsel before relying on standard no-solicitation language.

California remains the most restrictive jurisdiction, with Business and Professions Code § 16600 voiding virtually all post-employment restrictions. Courts have held consistently that a Delaware governing law clause does not override § 16600 when a California employee is the restricted party. The same logic applies in North Dakota and Oklahoma, both of which have categorical restrictions on post-employment agreements. If you are using an online template generator to create agreements for a multistate workforce, check that the generated clause is conditioned on the employee's state of employment, not just the company's state of incorporation. The independent contractor agreement template includes a state-specific governance note for this reason.

Drafting the Scope: What "Solicit" Means When You Don't Define It

Absent a contractual definition, courts in different states have reached opposite conclusions about what constitutes "solicitation." The majority view holds that posting a general job listing is not a solicitation — even if an employee who happened to see it was covered by a no-solicitation clause. A minority of courts have found that posting a listing in a niche forum frequented primarily by the other party's employees can constitute indirect solicitation when the surrounding facts show intent.

Courts have also split on whether responding to a LinkedIn connection request, agreeing to a coffee meeting initiated by the other party's employee, or mentioning an opening in casual conversation qualifies as solicitation. Each of these scenarios produces different outcomes depending on the jurisdiction and the specific clause language.

The safest approach is to define "solicit" in the contract itself, so courts do not have to interpret the word in a vacuum. Here is a working definition to include in the standard clause:

"As used in this Agreement, 'solicit' means to directly contact, approach, call, email, message, or communicate with an identified individual with the purpose of inducing that individual to enter into an employment, engagement, or business relationship with the soliciting party, whether such contact is initiated by the soliciting party or in response to an inquiry that the soliciting party itself generated or encouraged through targeted outreach, referrals, or communications directed at the other party's personnel or client base."

The phrase "in response to an inquiry that the soliciting party itself generated or encouraged" closes the indirect-solicitation loophole. It prevents the other party from running a subtle targeting campaign — posting on a niche forum, asking mutual contacts to pass along the word — and then arguing that all resulting applications were unsolicited. This definition is substantialy more protective than the one-word version most agreements contain.

Time and Geography: How Courts Calibrate "Reasonable" Restrictions

Courts applying the reasonableness standard look at two variables for time and one for geography.

On time, the zone of safety for most jurisdictions is twelve to twenty-four months measured from a clearly defined trigger — contract termination, project completion, or the last date of services. Courts have upheld thirty-six-month restrictions in high-value B2B agreements where the client relationships being protected took years to develop. Courts have voided restrictions measured from ambiguous dates, restrictions that reset each time the parties interact, and restrictions without any stated time limit. The latter are treated as perpetual and voided automatically in most states.

On geography, client no-solicitation clauses generally do not need geographic limits — the restriction attaches to specific named persons or defined categories of clients, not to a territory. Employee no-solicitation clauses also rarely require geographic limits; the protected class is defined by the employment or project relationship, not by location. If you add a geographic restriction, make sure it is consistent with the actual scope of the business relationship. Courts read an unnecessarily broad geographic term as evidence that the restriction was not tailored to protect a legitimate interest, and will use it as grounds to narrow or void the whole provision.

No-Hire Provisions in Contractor Agreements vs. Employment Agreements

The same no-hire or no-solicitation language can appear in very different documents, and the enforceability analysis differs meaningfully by document type.

In an at-will employment agreement, the restriction typically runs from the employee to the employer — preventing the employee from soliciting colleagues or clients after departure. Courts in several states apply stricter scrutiny here because the power imbalance between employer and employee is greater than in an arm's-length commercial contract. California, North Dakota, and Oklahoma effectively void all post-employment restrictions regardless of how narrowly they are drafted, while Illinois requires independent consideration when the restriction is added after the initial hire date.

In a service or independent contractor agreement, the restriction usually runs between two businesses — preventing either party from recruiting the other's key personnel or approaching the other's clients. Courts treat these as commercial contract restrictions subject to the rule of reason, and are generally more willing to enforce them if the scope is proportionate. The power imbalance rationale that weakens employer-side employee restrictions does not apply to the same degree in a B2B context.

The practical implication: do not copy the no-solicitation language from your non-compete agreement template into your service contract, or vice versa. The contexts are different, the legal tests are different, and a clause drafted for one setting may be overbroad or legally mischaracterized in another. Use seperate, specifically tailored provisions in each document, and check that the language matches the legal relationship it is actually governing.

Enforcement Remedies: Building a Clause That Is Worth Enforcing

A no-hire or no-solicitation clause without an enforcement mechanism is a polite request. Three remedies should be addressed explicitly in the clause or an adjacent provision.

Injunctive relief. Courts can enjoin ongoing violations — ordering a company to stop employing a wrongfully hired person or to cease client solicitation. But injunctions require a showing of irreparable harm, and courts differ on whether the loss of a single employee constitutes irreparable harm absent proof that the employee had access to specific trade secrets or uniquely valuable client relationships. The argument is most persuasive when you can point to a non-disclosure agreement the employee signed and specific confidential information they carry.

Liquidated damages. Specifying a per-hire or per-solicitation liquidated damages amount is often the most practical approach for a small business. Courts enforce these provisions when they represent a reasonable pre-estimate of harm — not an arbitrary penalty. Common formulations include "a sum equal to the gross annual compensation of the solicited employee during the twelve months preceding the breach" or "an amount equal to twelve months of projected annual revenue from the solicited client based on the most recent contract value." These standards are calibrated to actual loss, which courts require.

Fee-shifting. In the absence of a fee-shifting clause, each party pays its own legal costs even if it wins. For a small business enforcing a no-solicitation clause, litigation costs may exceed recoverable damages unless fees are shifted. Including "the prevailing party in any action to enforce this Section shall be entitled to recover its reasonable attorneys' fees and costs" materially changes the risk calculation for a counterparty considering a violation. The online template standard often omits this; add it manually.

Common Drafting Mistakes That Make These Clauses Unenforceable

After reviewing numerous service agreements and contractor documents, the same errors appear repeatedly:

• Using "non-compete" language to accomplish a no-solicitation goal. Courts apply non-compete doctrine — including state-specific categorical bans — to provisions labeled as or functioning like non-competes. A restriction that prevents someone from working in an industry is a non-compete. A restriction that prevents them from approaching specific identified persons is a no-solicitation clause. Keep the language and label accurate.
• Failing to define the restricted class of employees or clients. "All employees" or "any client" is almost never enforceable. Courts expect a defined, justified class tied to the specific relationship between the parties.
• No independent consideration for mid-contract amendments. If the no-hire clause is added by amendment after the original contract is signed, courts in Illinois, Georgia, and several other states require independent consideration — not just the original contract's value — to support the new restriction. Adding an extended payment term, a cash payment, or any other new benefit at the time of amendment usually satisfies this requirement.
• No duration. Perpetual restrictions fail universally. Always include a specific period measured from a defined termination or expiration event.
• Relying on governing law without checking the employee's or contractor's state. California § 16600, Minnesota Stat. § 181.988, and similar statutes apply based on where the restricted party works, not where the agreement was signed or what governing law it selects. A Delaware clause does not fix a California employee situation.

For NDA-adjacent restrictions — situations where the no-solicitation clause is tied to confidentiality protections — verify that the non-disclosure agreement template and the service contract are consistent. Conflicting definitions of "confidential information" between a standalone NDA and a service agreement have been used by courts as grounds to narrow the scope of both.

What to Do If You Are on the Receiving End of a No-Hire Clause

If you are the party signing a contract with a no-hire or no-solicitation provision directed at you, the review checklist is essentially the reverse of the drafter's checklist. Before you sign, verify:

• What conduct is actually prohibited? If the clause covers "solicit or hire," you cannot hire someone who applies to you unsolicited if they were involved in the covered project — period. Know what you are agreeing to.
• How long does the restriction run? A twenty-four-month tail on a six-month project is arguably disproportionate. Negotiate the duration down if the restriction is longer than the relationship.
• Does the restriction apply to your entire organization, or only to the personnel who worked on this engagement? An enterprise-wide restriction may be unenforceable if the other party has no legitimate interest in restricting departments that had no exposure to their employees or clients.
• Is there a general advertising carve-out? If not, negotiate one in. Without it, you could technically be in breach any time a covered employee applies through a public posting on your website.
• What remedies does the clause provide? If it includes liquidated damages, calculate whether the per-hire amount is commercially reasonable given the size of the deal. Liquidated damages that are grossly disproportionate may be voided as penalties, but that outcome requires litigation to establish.

Final Checklist — Pre-Signing Audit for No-Hire and No-Solicitation Clauses

Before signing or sending any agreement that includes these provisions, work through this list on both sides of the transaction:

• Is the clause labeled accurately? Does it say "no-hire" if it covers unsolicited applications, or "no-solicitation" if it covers only active recruiting?
• Are the protected classes of employees and clients specifically defined — not "all personnel" or "all clients"?
• Is the time period stated and measured from a clear, defined event (contract termination, project completion)?
• Is "solicit" defined in the contract, not just used as an undefined verb?
• Is there a general public advertising carve-out for employees?
• Is there an Exhibit documenting pre-existing client relationships for the client no-solicitation provision?
• For B2B (between legal entities): is the clause ancillary to a real commercial transaction, not a standalone mutual agreement between competitors?
• What state law governs? Is that state permissive or restrictive toward these clauses? Does the restricted party work in a more restrictive state?
• Does the clause include liquidated damages, injunctive relief authorization, and a fee-shifting provision?
• Is there a severability clause so that an overbroad provision does not void the entire agreement?

The create process for these clauses takes less than an hour if you work from a properly structured template. The litigation process, if you skip the checklist, takes considerably longer and costs considerably more. A well-drafted no-hire provision is not impressive legal architecture — it is a practical business protection that works exactly as long as you need it to and no longer.

Article reviewed by: Maya S. (Attorney)