Prioritize a targeted non-solicitation clause when the risk is client poaching, and use a non-compete only for clearly defined competition risk. For U.S.-linked contracts, treat new non-compete language as a major redline point given FTC materials around September 4, 2024 and later updates that the rule is not currently in effect. In non-solicitation vs non-compete decisions, pressure-test four items before signing: covered parties, restricted conduct, duration, and geography. Save the dated redline, pre-acceptance disclosures, and executed version together.
Choose the narrowest restrictive covenant that protects a real risk and still lets you keep earning. For freelancers and consultants with multiple engagements, broad restrictions can cut off pipeline long before any dispute starts.
Start with a practical question: what risk is the hiring party actually trying to control? A non-compete agreement can restrict where you work or what similar business you run for a period and area. A non-solicitation agreement usually allows work elsewhere but limits outreach to the other party's customers or limits recruiting.
| Decision lens | Non-compete agreement | Non-solicitation agreement | Better fit when... |
|---|---|---|---|
| Main restriction | Working for a competitor or starting similar work can be restricted for a time and area. | Working elsewhere is usually allowed, but contacting certain customers or recruiting team members is restricted. | You need to protect relationships, not block a provider's broader market activity. |
| Impact on future work | Can block new deals in your core service lane. | Usually allows continued work for new buyers outside protected relationships. | The provider depends on a multi-client income model. |
| Current FTC signal for US contracts | FTC materials list September 4, 2024 as an effective date and also direct businesses not to include new noncompetes in future contracts, paperwork, or websites. | Not the same clause type, but wording should still be narrow and tied to a real business interest. | You want targeted protection without a broad work ban. |
| Common failure mode | Broad terms not tied to legitimate interests are often challenged. | Vague contact limits can still create accidental breach risk. | You can clearly define who and what is actually protected. |
For US-facing agreements, treat any new non-compete request as a major negotiation point, not a minor tweak. FTC guidance also frames the rule as covering workers, including independent contractors, and discusses notice duties tied to existing noncompetes for workers other than senior executives.
Use these checkpoints before you sign a freelance contract:
Keep the standard simple: protect a legitimate business interest without signing away your next source of work.
Use this table when a draft includes both clause types and you need a quick read. The practical split is work restrictions versus contact restrictions.
| Criteria | Non-compete agreement | Non-solicitation agreement | Best use case |
|---|---|---|---|
| Geographic scope | Can be tied to a territory; courts examine geographic scope, duration, and industry scope. | Usually tied to defined clients, customers, or employees. | Specialist consultant with true regional exclusivity concerns, with territory narrowed to actual business reach. |
| Restricted activities | Can restrict work for a competitor or similar self-employment in the same field. | Restricts soliciting former clients, customers, or employees after departure, including when someone starts their own company. | Niche freelancer who needs to keep delivering services but can accept targeted outreach limits. |
| Duration | Courts examine duration alongside geography and industry scope. | Must still be reasonable in how long and how broadly it restricts solicitation behavior. | Multi-client provider who needs continuity and should avoid role-wide work bans. |
| Business impact | Can block categories of new work. | Can limit follow-on business from protected relationships. | When the goal is relationship protection without freezing your ability to practice your trade. |
| Enforceability risk | Risk rises when terms are broad and not tied to a legitimate business interest; U.S. federal noncompete rule status has been unsettled, and FTC updates state the rule is not currently in effect. | Enforced only if reasonable; may fail if it creates an undue burden on ability to work. | Better fit when you can name exactly who is protected and keep limits proportionate. |
Before you accept wording, check the draft for:
competitor, client, customer, and employee, not open-ended buckets.Treat these clauses as separate tools for separate risks. Non-compete language generally sets work limits, non-solicitation language generally sets contact limits, and NDA language sets information limits.
From the hiring side, the concern is usually relationships and information. From your side, it is staying able to work while keeping clear boundaries. Drafts are usually strongest when each clause covers one specific risk and avoids overlap.
| Restriction bucket | Primary clause | What it restricts in practice | What stays open when drafted narrowly |
|---|---|---|---|
| Contact limits | Non-solicitation agreement | Depending on the wording, certain client-contact or outreach activity. | Taking new work outside the restricted contact activity. |
| Work limits | Non-compete agreement | Depending on the wording, certain competing work stated in the clause. | Work outside that stated scope. |
| Information limits | Nondisclosure agreement | Use or disclosure of confidential information. | Working elsewhere, as long as confidential information is used only for permitted purposes. |
If you sell a specialized service to many similar buyers, a broad non-compete can be deal-breaking if it blocks too much of your pipeline. A targeted non-solicitation term may be more workable when the real concern is relationship protection, not stopping the service itself.
Check restriction language closely. Broad wording can quietly expand what a clause covers. Before you sign, make sure the NDA defines confidential information and permitted use clearly, and remove overlap where multiple clauses repeat the same restriction.
Enforceability often turns on reasonableness and drafting quality, not just the clause label.
| Practical screen | What to check in the draft | Typical failure mode |
|---|---|---|
| Reasonableness standard | Read scope, duration, and purpose together. If one is broad, the others should be tighter. | In jurisdictions that take a cautious approach, broad language can fail even when the clause title looks standard. |
| Legitimate business interests | Tie each restriction to a specific interest, such as current customer relationships or related business investment. | Language that blocks normal competition without a clearly defined interest is easier to challenge. |
Jurisdiction is a core variable. In Alberta, the provided material frames enforceability around reasonableness and clear drafting, not clause name alone. In Washington, the cited updates narrow non-solicitation scope and also highlight proof and process issues that can affect outcomes early.
If your contract relies on jurisdiction-specific statutory language outside these examples, treat that as a local legal review trigger. Do not treat one jurisdiction's rule as a portable rule for every deal.
Hard redline rule: if time, geographic scope, and restricted activities are all broad at once, expect enforceability to be contested and narrow at least two before you sign.
Before you sign, keep a short record:
Choose the smallest restriction that matches the actual risk, then test it against how you actually earn.
| Risk | Start with | Drafting focus |
|---|---|---|
| Account poaching | Non-solicitation agreement | Tie it to defined customers or accounts, not market-wide wording |
| Confidential methods or internal information | Nondisclosure agreement | Tighten confidential information definitions and permitted-use language |
| Direct competition | Non-compete agreement | Use a narrow competitor definition, limited geographic scope, and restricted activities matched to your role |
If the risk is account poaching, start with a non-solicitation agreement tied to defined customers or accounts, not market-wide wording. This can still limit your ability to freelance with former employer clients after you leave and can also limit inviting former co-workers into a new venture.
If the risk is confidential methods or internal information, start with a non-disclosure agreement and tighten confidential information definitions. Clear boundaries on what is protected and how it can be used are more practical than vague "all business information" language.
If the hiring party asks for a non-compete agreement, negotiate scope first. Ask for a narrow competitor definition, a limited geographic scope, and restricted activities matched to your role. Courts often require non-compete provisions to be narrow. These terms are often negotiable, and risk can vary by where you work, where the employer is located, and your role.
Treat terms that block work with broad "similar buyer" categories as a renegotiation trigger. Broad language is not automatically invalid everywhere, and non-compete enforceability can depend heavily on location and role.
Use this one-page checkpoint before you sign.
Then apply a few simple controls.
If you want a first-pass agreement before redlining, use Create a freelance contract draft.
Broad or vague scope is a common driver of expensive disputes.
| Red flag | Why it creates risk | Safer direction before signing |
|---|---|---|
| Catch-all protected parties | If protected customers or accounts are not clearly bounded, normal outreach may be treated as a breach. | Tie protection to specific accounts or customer groups connected to real business relationships. |
| Open-ended restricted activities | Undefined activity scope can be stretched beyond the work you expected to restrict. | Define restricted activities by role and concrete competitive risk. |
| Duration stacking in a non-compete agreement | Long duration, wide geography, and broad activity limits increase enforceability risk and may draw closer scrutiny in some jurisdictions. | Narrow time, geography, and activity scope to the real risk. |
| One-size-fits-all template terms | Generic restrictions that are not tailored to role and scope are easier to challenge. | Tailor restrictions to the person's role, scope, and actual competitive risk. |
| Proof blind spots in a non-solicitation agreement | Vague terms are hard to apply in practice, and small missteps can escalate into legal fees, injunctions, and damaged business relationships. | State what conduct is restricted and which customer or employee groups are covered. |
The main warning sign is overbroad drafting. Restrictions are generally judged on reasonableness in time, geography, and activity scope, and enforceability varies by jurisdiction, so overreach should be narrowed or rejected before signature.
Use this quick pre-sign check:
Negotiations go more smoothly when each ask is specific, written, and easy to compare against fallback text.
| Pressure point | Preferred ask | Fallback language if pushed back | Why this helps |
|---|---|---|---|
| Who is protected | Define protected parties in specific, engagement-linked terms | If narrower definitions are rejected, use the clearest limited definition both sides can operationalize in an exhibit | Can reduce ambiguity from broad catch-all wording |
| Who counts as a competitor | Use objective, written scope language tied to the engagement context | If scope language is disputed, use a short written list with a defined amendment process | Can make disputed scope easier to compare in redlines |
| What conduct is restricted | Describe restricted conduct in concrete, activity-based terms | If broader wording is requested, narrow it with explicit exclusions for out-of-scope activity | Can keep restrictions aligned to the risk being addressed |
| Covered persons in non-solicitation | Remove blanket formulations such as all employees | Replace with clearly defined, engagement-linked groups | Broad covered-person definitions are commonly contested |
Run concessions in a fixed order:
Use relationship-safe language in your redline note: "I understand your legitimate business interests and can accept targeted limits tied to this engagement. I need clear boundaries so normal business activity outside that scope is not unintentionally restricted."
Documentation helps prevent backsliding. Keep tracked redlines and a plain-English issue list. Tag unresolved items by risk tier and plain-English action items. Confirm every accepted change appears in the final signed contract or exhibit, not only in email.
In an M&A NDA study, initial draft positions had minimal effect on final outcomes. In that setting, departures from market norms were often a time sink, so scoped edits aligned with norms were often the stronger path.
Read restrictive covenants, indemnification, and limitation of liability as one package. If you narrow one clause but ignore the others, you can still carry much of the financial downside when a dispute starts.
Reviewing these clauses one by one can hide how remedies connect across the contract. Indemnification can shift losses, damages, or legal fees, while limitation language sets, or weakens, the exposure ceiling. Read all three together so conduct triggers, payment triggers, and caps stay aligned.
| Review point | If reviewed in isolation | If reviewed together | Practical redline move |
|---|---|---|---|
| Competition trigger | You confirm restricted conduct | You see whether the same conduct also triggers indemnity | Tie indemnity triggers to the same defined acts |
| Financial transfer | You see duty language | You see who actually carries dispute costs | Remove catch-all language that shifts all liability to one side |
| Damages ceiling | You see a cap exists | You test whether the cap is meaningful in practice | Make the cap and responsibility limits explicit |
| Restricted-conduct scope | Language can look standard | You test whether restrictions and remedies are clearly bounded | Define restricted conduct and permitted activity boundaries clearly |
The tradeoff is direct: broad restrictions plus broad indemnity can increase your downside exposure even when a claim is disputed. Documented failure modes include one party unknowingly taking most liability and agreements with no meaningful cap.
Use a cap strategy tied to clear risk allocation. If limits are unclear or missing, negotiate clearer responsibility limits before you sign.
Duration and survival language also need a consistency check. One SEC-filed restrictive covenant example runs for two years after termination. Use it as a reminder to verify timeline consistency across restrictive covenants, indemnity, and remedies, rather than copying employee-oriented language into a freelance agreement.
Run this verification checkpoint before you sign:
If scope is narrow but indemnity is broad and the cap is weak, keep negotiating until scope, indemnity triggers, and liability limits are internally consistent.
Set Governing Law, Jurisdiction, and Dispute Resolution before you sign. If those terms stay vague, restrictive-covenant enforceability analysis becomes less predictable.
| Setup item | What to state | Why it matters |
|---|---|---|
| Governing Law | Name it in clear text | Restrictive-covenant definitions should still function under the chosen law |
| Jurisdiction | Name it in clear text | Choose a forum you can realistically access and afford |
| Dispute Resolution | State court, arbitration, or a split path by claim type | Keeps scope, liability, and enforcement planning aligned |
| Forum access and cost | Record why the selected forum is realistically accessible and affordable | Do not leave forum terms vague before signature |
When work and payment run across countries, choose a forum you can realistically access and afford. Keep that decision in the same redline pass as the restrictive text so scope, liability, and enforcement planning stay aligned.
| Decision lens | Court venue under chosen Jurisdiction | Arbitration-style Dispute Resolution | Contract checkpoint |
|---|---|---|---|
| Cost planning | Define budget assumptions for the selected venue and procedure | Define budget assumptions for the selected rules and provider | Request a side-by-side budget scenario before signing |
| Speed planning | Define timeline assumptions for the selected court process | Define timeline assumptions for the selected arbitral process | Write timeline assumptions into the issue list |
| Enforceability planning | For US-linked non-competes, state law and forum choice can affect outcomes | For US-linked non-competes, chosen law and forum terms can affect outcomes | Map where enforcement would actually be pursued |
| Restrictive-covenant fit | State law treatment can affect outcomes | Chosen law and definitions still need to work in the selected process | Verify definitions are workable under the selected law |
For US-linked deals, forum choice affects enforceability risk because non-compete treatment varies by state law. A practical checkpoint is a 50-state comparison before signing.
The same source set notes that approximately fifteen states and Washington, DC have enacted limits on employee non-competes. It also notes one DC rule that references a more-than-50-percent work-time threshold. That is a reminder that one-size-fits-all drafting is risky.
Template selection also matters. One referenced multi-state form is jurisdiction neutral, drafted in favor of the employer, and bundles non-compete, customer and employee non-solicitation, confidentiality, and non-disparagement terms. Use forms like that only as a starting point, then adapt them with state-specific clauses.
Pre-sign check:
Governing Law and Jurisdiction in clear text.Do not rely on hoped-for federal non-compete outcomes when forum terms remain unresolved. If forum language is still open, consider pausing signature until those terms are clear.
Before you sign, verify that restrictive clauses and termination terms are internally consistent. If they are not, pause and fix the draft, then run one checklist for the Non-compete agreement, Non-solicitation agreement, and Nondisclosure agreement.
| Illinois-linked check | Detail | Applies to |
|---|---|---|
| Pre-start delivery | Restrictive terms delivered 14 days before start | Illinois-linked employment agreements |
| Attorney advice | Written advice to consult an attorney | Illinois-linked employment agreements |
| Non-compete threshold | $75,000 annual threshold for non-compete enforceability | Non-compete |
| Non-solicitation threshold | $45,000 annual threshold for non-solicitation restrictions | Non-solicitation |
| Clause | Pre-sign consistency check | Termination check | Internal records to retain |
|---|---|---|---|
| Non-compete agreement | Confirm duration, geographic scope, and restricted activities match the negotiated redline text | List the post-termination period stated in the contract and any territory limits | Signed redlines, approved carve-outs, final signed clause version |
| Non-solicitation agreement | Confirm who is covered, what contact is restricted, and any exclusions for existing relationships | Identify which account or contact actions remain restricted after offboarding | Account list snapshot used at signing, communication logs on carve-out approvals |
| Nondisclosure agreement | Confirm protected information definitions and permitted-use exceptions are clear | Confirm which confidentiality duties survive termination and for how long under the draft | Final definitions exhibit, message trail confirming agreed edits |
For Illinois-linked employment agreements, add a jurisdiction-specific gate before signature. The Illinois Freedom to Work Act amendment took effect on January 1, 2022.
The excerpted checks include 14-day pre-start delivery of restrictive terms, written advice to consult an attorney, a $75,000 annual threshold for non-compete enforceability, and a $45,000 annual threshold for non-solicitation restrictions, with scheduled increases over time. Treat these as Illinois checks, not universal rules.
Termination planning should be evidence-ready because non-compete disputes are often fast-paced and expensive, and weak records can backfire. Build the file before conflict starts:
After signature, run an early operating check as an internal control:
Sign only when clause language, termination duties, and evidence records are consistent for the governing jurisdiction. If any one of those three is incomplete, keep negotiating before work begins.
Make the final call based on practical risk: sign only terms you can explain clearly and still live with after exit.
Here, the clearest risk is the non-compete. The January 27, 2026 FTC workshop transcript describes non-competes in employment agreements as terms that can block similar work, or work in a defined geography, for months or even years after exit.
In the same discussion, anti-competitive non-competes are described as harmful to wages, job opportunities, and bargaining power. The discussion also notes that a prior nationwide ban attempt had been blocked by courts.
| Decision point | Keep moving | Stop and renegotiate |
|---|---|---|
| Scope clarity | Limits are specific and easy to explain | Wording reads broad or open-ended |
| Post-exit workability | You can still identify realistic next work options | The clause could block most similar work |
| Duration and geography | Both are clearly stated in final text | Duration or geography is unclear or overly expansive |
| Document control | Redlines and signed terms match | Side promises are not in the executed contract |
Execution matters more than theory. Keep restrictive text and related terms internally consistent in signed documents, and do not rely on verbal assurances that are not written into the contract.
Before accepting a start date, run one final check:
If a non-compete later appears to be blocking a new job, the FTC transcript notes an anonymous complaint channel at [email protected]. Before you sign, pair your restrictive-covenant edits with a clean confidentiality baseline: Generate an NDA draft.
The practical split is contact limits versus work limits. A non-solicitation clause focuses on stopping contact or recruitment of clients, customers, or staff after the relationship ends. A non-compete can go further by limiting work for a competitor, or similar work for yourself, for a defined period.
Often yes, because non-solicitation usually targets who you approach, not every role you can take. That duty can still apply if you join a competitor or start your own company. The key check is drafting: confirm exactly who is covered, what conduct counts as solicitation, and how local rules apply.
A common reason they are challenged is that they can burden someone’s ability to keep working in their field. Enforceability is commonly tested for reasonableness in scope, duration, and purpose, and courts may also look at geography and industry fit. If those limits are broad at the same time, dispute risk can rise.
In many cases, a targeted non-solicitation clause can be less restrictive than a broad non-compete. It is generally framed as enforceable only when it is no broader than necessary to protect a legitimate business interest. The final result still depends on how clearly and narrowly it is drafted.
Start by narrowing scope before anything else. Restrictive terms can operate across time, industry, and geography, so those limits should be clear and proportionate. Push for precise drafting and make sure final limits are in the signed contract text.
They can matter, but the effect is jurisdiction-specific. There is no single enforceability rule you can safely apply everywhere. Treat local reasonableness and drafting standards as key checkpoints.
These clauses are designed to control post-exit conduct, so contract language after termination matters. Read what restrictions continue after the relationship ends and align outreach and hiring behavior to that text. If wording is broad or unclear, narrow it before signing.
An international business lawyer by trade, Elena breaks down the complexities of freelance contracts, corporate structures, and international liability. Her goal is to empower freelancers with the legal knowledge to operate confidently.
Priya specializes in international contract law for independent contractors. She ensures that the legal advice provided is accurate, actionable, and up-to-date with current regulations.
Educational content only. Not legal, tax, or financial advice.
The real problem is a two-system conflict. U.S. tax treatment can punish the wrong fund choice, while local product-access constraints can block the funds you want to buy in the first place. For **us expat ucits etfs**, the practical question is not "Which product is best?" It is "What can I access, report, and keep doing every year without guessing?" Use this four-part filter before any trade:
Stop collecting more PDFs. The lower-risk move is to lock your route, keep one control sheet, validate each evidence lane in order, and finish with a strict consistency check. If you cannot explain your file on one page, the pack is still too loose.
If you treat payout speed like a front-end widget, you can overpromise. The real job is narrower and more useful: set realistic timing expectations, then turn them into product rules, contractor messaging, and internal controls that support, finance, and engineering can actually use.