Compare Non Compete Agreements Against State Law

Skill: Compare Non-Compete Agreements Against State Enforceability Standards

2. Failure modes the skill is correcting

• Analyst applies one state’s rule set to a covenant that must be tested under multiple potentially governing jurisdictions, missing conflicts-of-law issues and jurisdiction-specific defects.
• Analyst treats enforceability as only a reasonableness question and overlooks notice, consideration, compensation, timing, or termination-trigger conditions that can defeat enforcement independently.
• Analyst analyzes the agreement in the abstract instead of testing the actual employee relationship, work location, post-termination posture, and any employer-initiated separation facts that constrain relief.
• Analyst fails to separate a true enforceability analysis from a critique of the demand letter, allowing overstated legal claims to go unflagged.
• Analyst gives conclusions without tying them to the governing authority, making the memo sound plausible but legally unsupported.

3. Legal frameworks / domain conventions that apply

• Multi-jurisdiction restrictive-covenant analysis: identify each potentially governing state before applying its own statutory and common-law test; do not assume a single forum controls.
• Reasonableness of restraint: assess duration, geographic reach, and activity scope against the legitimate business-interest standard used in the applicable jurisdiction.
• Statutory and common-law prerequisites: check whether the jurisdiction requires advance notice, signed acknowledgments, garden-leave or compensation thresholds, cooling-off periods, or other formation conditions.
• Termination and separation limits: determine whether employer-initiated termination, lack of cause, involuntary resignation, or other trigger facts limit or void enforcement under the governing law.
• Partial enforcement rules: determine whether the state permits blue-penciling, reformation, or only strict enforcement; that rule changes both litigation risk and settlement leverage.
• Claims-based critique of demand letters: test each asserted proposition against the cited authority and flag missing elements, overbroad statements, and mismatched jurisdictional citations.
• Controlling authority discipline: every legal proposition should be anchored to the relevant statute, regulation, case, or rule; unsupported conclusions should be treated as incomplete analysis.

4. Analytical scaffolds

• Jurisdiction inventory first: list every state that may govern based on employee location, performance location, solicitation targets, or contract choice-of-law language; if only one state is realistically in play, say so and explain why.
• State-by-state pass: for each jurisdiction, analyze in one place:
  • duration,
  • geographic scope,
  • activity restriction,
  • formation/procedural prerequisites,
  • compensation or consideration threshold,
  • termination-related bars,
  • available equitable remedies,
  • reformation or severability rules.
• Governing-authority pass: for each rule relied on, cite the controlling statute or leading case and state the proposition it supports before drawing the conclusion.
• Fact-to-rule linkage: tie each defect to the actual contract language and the actual employee facts, not to generic non-compete doctrine.
• Comparison pass: compare jurisdictions on strictness, likelihood of reformation, and the practical enforceability posture of the covenant.
• Demand-letter critique pass: isolate each legal claim in the letter, identify the cited authority, then state whether the claim is accurate, overstated, incomplete, or inapplicable.
• Consequence pass: for each issue, state the downstream litigation, negotiation, or operational effect of the defect.
• Synthesis pass: end with the most vulnerable jurisdictions, the strongest enforceability arguments, and the best forum or settlement posture.

5. Vertical / structural / temporal relationships

• Analyze the relationship between contract formation facts and enforcement facts: when the covenant was signed, when employment began, when the employee moved, and when separation occurred.
• Distinguish pre-employment, during-employment, and post-termination rules, because the enforceability analysis can change across those temporal stages.
• Track vertical relationships among the agreement, any offer letter or policy acknowledgment, any choice-of-law provision, and the demand letter’s cited authorities.
• If the contract contains multiple restrictive provisions, analyze each restriction separately and then state how they interact.
• If the covenant spans more than one state, do not merge the analyses; resolve each state on its own terms and then compare the outcome.

6. Output structure conventions

• Format the output as a multi-jurisdiction enforceability memorandum.
• Begin with a short issue map identifying the potentially governing jurisdictions and the controlling documents reviewed.
• Use conventional memo headings by jurisdiction rather than a rigid rubric checklist.
• Include a comparative summary table or matrix covering, at minimum, duration, scope, procedural compliance, threshold requirements, termination limits, and overall enforceability posture.
• For each jurisdiction, include:
  • controlling authority,
  • rule statement,
  • application to the covenant,
  • practical effect if challenged.
• Give each material issue a clear severity label using a consistent ordinal scale defined once at the top of the memo.
• Close with a concise demand-letter critique that separates strong points from weak points.
• End with a Recommended Actions section that assigns each action to a responsible role and a timing anchor tied to the litigation or negotiation posture.
• Keep the memorandum focused on operative analysis; avoid generic background law unless it changes the outcome.