ForHosting KIT · Documents & PDF

Generate a Non-Compete Clause Reasonableness Checklist

A non-compete clause is rarely evaluated by duration alone. This generator turns a proposed duration, geographic scope, and worker role into a structured checklist of the reasonableness factors commonly examined when a restriction is reviewed.

● BetaFree · in your browser
Use it from WebAPIEmailTelegramApp soon

It highlights the business interest, fit between the role and prohibited work, territorial reach, worker burden, public effects, drafting clarity, and narrower alternatives. The result is a jurisdiction-neutral issue-spotting aid, not legal advice or a conclusion that a clause is valid, enforceable, or suitable under any particular law.

Start with the interest, not the prohibition

A useful review begins by stating the business interest that the clause is intended to protect. That might be customer goodwill developed through a sales relationship, confidential pricing available to a commercial leader, sensitive product plans, or genuine trade secrets. The role description matters because a restriction should connect to what the particular worker actually did, knew, influenced, or could use competitively. A generic job title is weak evidence by itself. Record concrete duties, customer contact, decision-making authority, information access, and how long any sensitive advantage remains useful. Then compare those facts with the work the clause prohibits. If a person handled one product line in one territory, a ban covering unrelated jobs, products, and customers needs a specific explanation. The generated checklist surfaces likely interests from the role wording, but those signals are prompts for evidence rather than findings. It does not assume that confidential information exists simply because a role sounds senior, technical, or commercial. The reviewer should verify each claimed interest and remove any restriction that cannot be tied to a legitimate, documented risk.

Test duration, territory, and activities together

Duration, geography, and prohibited activities interact. A short clause can still be broad if it prevents almost every form of work across a large market, while a longer period may require especially strong evidence about the lifespan of relationships or confidential material. Enter the duration in months and describe the geographic scope in practical language, such as named accounts, a sales territory, a city radius, nationwide operations, or remote clients served. The output categorizes those inputs only to focus review; the labels are not legal thresholds. Compare the proposed territory with where the worker actually operated and where the employer has a protectable market. For borderless or remote work, consider whether accounts, customers, products, or activities define the risk more accurately than a map. Separately list the competitive duties that are barred. Ask whether the clause prevents only the work capable of exploiting the identified interest or blocks employment with a competitor in any capacity. Finally, document why the chosen period matches the time needed for information to age, customer influence to diminish, or a transition measure to work.

Check burden, alternatives, and applicable law

Reasonableness review also looks beyond the employer's preferred protection. Evaluate what the clause would mean in practice for the worker: available jobs, use of general skills, income, relocation, career continuity, and the ability to remain in the occupation. Consider effects on customers and the public, particularly where the work involves scarce expertise, essential services, or professional choice. Then compare narrower tools. Confidentiality and trade-secret obligations may address information risk; targeted customer or employee non-solicitation terms may address relationships; notice, garden leave, or account-specific limits may reduce disruption. The checklist asks for this comparison because a broad non-compete can appear less necessary when a focused measure protects the same interest. Drafting details also deserve attention: definitions, covered entities, competing services, exceptions, start and end dates, triggering events, and the relationship between the chosen law and forum. Most importantly, obtain current advice for every law that may apply. Jurisdictions differ on prohibited worker categories, compensation thresholds, notice, consideration, modification, and available remedies, and those rules can change. This tool organizes questions; it cannot decide enforceability.

Prepare a drafting review

Turn the proposed duration, territory, and role into a consistent set of questions before counsel reviews clause language.

Compare alternative scopes

Run different durations or geographic descriptions and compare which assumptions and tailoring questions each version raises.

Organize negotiation notes

Use the checklist to document claimed interests, practical worker burden, and narrower protections that the parties can discuss.

Does this tool determine whether a non-compete is enforceable?

No. It provides a jurisdiction-neutral issue-spotting checklist. Enforceability depends on current applicable law and the specific facts, so qualified local legal advice is necessary.

Why must the duration be positive?

The duration represents an actual restriction period. Zero, negative, nonnumeric, and non-finite values do not describe a usable period and are rejected as invalid input.

Is a shorter duration automatically reasonable?

No. Duration is considered alongside geography, prohibited activities, the worker's role, the protected interest, hardship, public impact, and applicable legal rules.

How should remote or online work be described?

Describe the actual clients, accounts, products, markets, or territories served. The checklist will prompt consideration of activity-based or relationship-based limits where map boundaries are less informative.

What does an API request cost?

Each API request costs $0.002. The calculation is deterministic and also suitable for the free browser experience.

Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.

POSThttps://api.kit.forhosting.com/doc/non-compete-checklist

Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.

curl -X POST https://api.kit.forhosting.com/doc/non-compete-checklist \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"duration_months":12,"geographic_scope":"Named accounts in the Northeast sales territory","role":"Regional sales director with customer relationships and access to pricing strategy"}'
{
  "duration_months": 12,
  "geographic_scope": "Named accounts in the Northeast sales territory",
  "role": "Regional sales director with customer relationships and access to pricing strategy"
}
{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "doc.non_compete_checklist",
  "status": "queued",
  "_links": {
    "result": "/tasks/tsk_…/result"
  }
}

The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.

Per request$0.002

Published price — no tokens, no invented credits. A failed task is never charged.

max_mb25
max_pages200
HTTPCodeMeaning
401unauthorizedMissing or invalid API key.
402insufficient_balanceYour balance doesn't cover the task price.
404unknown_typeThat task type doesn't exist.
429rate_limitedToo many requests. Use the webhook instead of polling.

Read the full KIT documentation →