Clause Labs

Category: Contract Clauses

  • The Solo Lawyer’s Guide to Reviewing Commercial Leases with AI

    The Solo Lawyer’s Guide to Reviewing Commercial Leases with AI

    The Solo Lawyer’s Guide to Reviewing Commercial Leases with AI

    A single missed clause in a commercial lease cost a restaurant owner in Phoenix $340,000 in unexpected CAM charges over five years. The lease looked standard. The landlord’s attorney knew it wasn’t. The tenant’s lawyer — a solo practitioner juggling 30 other matters that month — missed a capital expenditure pass-through buried in the operating expenses definition. That one oversight wiped out the client’s entire first-year profit.

    Commercial leases are the trickiest “routine” contract most solo lawyers encounter. They combine real estate law, contract law, and business operations into documents that routinely run 40-80 pages. Unlike an NDA you can review in 20 minutes, a commercial lease demands attention to financial calculations, operational obligations, and landlord remedies that can follow your client for a decade or more. According to World Commerce & Contracting, poor contract management erodes an average of 9.2% of annual revenue — and commercial leases are among the highest-stakes contracts most small businesses sign.

    This guide covers the 15 clauses you must review in every commercial lease, the financial traps hiding in NNN and CAM provisions, and how AI-assisted review can help you catch what manual review misses. Try Clause Labs’s free analyzer on your next lease — upload any contract and get a risk score in under 60 seconds.

    The 15 Commercial Lease Clauses Every Lawyer Must Review

    For each clause below: what it is, what to look for, and the red flag language that should stop you cold.

    1. Premises Description and Permitted Use

    The premises clause defines the exact space being leased — and the permitted use clause determines what your client can do in it. A vague premises description creates boundary disputes. A narrow permitted use clause prevents your client from pivoting their business.

    Red flag: “Tenant shall use the premises solely for [specific use] and no other purpose.” This locks your client into a single business model. Negotiate for broader language: “Tenant may use the premises for any lawful commercial purpose consistent with the character of the building.”

    2. Rent Structure: Base Rent, Percentage Rent, and Beyond

    Rent is never just rent in a commercial lease. Your client may owe base rent, percentage rent (common in retail — a percentage of gross sales above a breakpoint), and additional rent (taxes, insurance, CAM). The base rent number your client sees first is often less than half the total occupancy cost.

    Red flag: Percentage rent with no natural breakpoint or with a definition of “gross sales” that includes online sales, returns, and inter-company transfers.

    3. CAM Charges: The Hidden Cost Bomb

    Common Area Maintenance charges are where landlords win or lose net operating income — and where tenants get burned. CAM covers landscaping, parking lot maintenance, security, common utilities, and building management. The problem: landlords can define “common area” to include almost anything.

    Red flag: CAM definitions that include capital expenditures, management fees exceeding 5% of total CAM, or no annual cap on increases. According to the Association of Corporate Counsel, tenants in NNN leases should negotiate expense caps, audit rights, and explicit exclusions from operating expenses.

    4. Rent Escalation

    Rent escalation clauses set scheduled increases over the lease term. The three common types: fixed percentage (3-5% annually), CPI-indexed, or fair market value reset. Each carries different risk.

    Red flag: CPI escalation with no cap. During inflationary periods, this can produce 8-10% annual increases. Negotiate a CPI escalation with a floor (2%) and cap (4-5%).

    5. Lease Term and Renewal Options

    The initial term determines your client’s commitment. Renewal options determine their flexibility. A 10-year lease with no renewal option gives the landlord all the leverage at year 10 — your client either accepts whatever the landlord demands or relocates.

    Red flag: Renewal options that require rent at “fair market value as determined by landlord.” Negotiate for third-party appraisal or arbitration if the parties can’t agree.

    6. Tenant Improvement Allowance (TI)

    The TI allowance is the landlord’s contribution toward build-out costs. Typical ranges vary wildly — $15/sf for basic office space to $80+/sf for restaurant build-outs. The key issues: when TI is disbursed, what it covers, and what happens to unused TI.

    Red flag: TI disbursed only upon completion (your client fronts all costs), or TI that reverts to landlord if not used within a tight window.

    7. Assignment and Subletting Rights

    Assignment and subletting clauses determine whether your client can transfer the lease or sublease space. This is critical for businesses that might be sold, restructured, or need to downsize. For a deeper analysis of assignment provisions, see our guide to contract red flags.

    Red flag: Landlord consent required for any assignment “in landlord’s sole and absolute discretion” with no recapture right. Push for “consent not to be unreasonably withheld” and define what constitutes reasonable grounds for refusal.

    8. Maintenance and Repair Obligations

    Who fixes what — and who pays for it — is one of the most litigated lease provisions. In a NNN lease, tenants typically handle routine maintenance while landlords retain structural and roof obligations. The devil is in the definitions.

    Red flag: Tenant responsible for “all repairs and replacements, including structural elements, roof, and HVAC systems.” This can expose your client to six-figure capital expenditures. Negotiate to exclude structural repairs and HVAC replacement (vs. routine maintenance).

    9. Insurance Requirements

    Landlords require tenants to carry commercial general liability, property insurance, and often additional coverages. The amounts must be reasonable for the business type. More importantly, check for additional insured requirements and waiver of subrogation clauses.

    Red flag: Insurance requirements that exceed industry norms (e.g., $5M umbrella for a small retail tenant) or that require coverage for risks the tenant doesn’t control.

    10. Indemnification and Liability

    Commercial lease indemnification provisions are often aggressively one-sided. Landlords draft broad indemnification requiring tenants to hold the landlord harmless for almost anything that happens on the premises — including the landlord’s own negligence. For a thorough breakdown, see our indemnification clause analysis.

    Red flag: Tenant indemnifies landlord for “any and all claims arising from the premises” without exception for landlord’s negligence or willful misconduct.

    11. Default and Cure Provisions

    Default provisions define what constitutes a breach and how much time the tenant has to fix it. Monetary defaults (unpaid rent) typically require 5-10 days’ notice. Non-monetary defaults (operational violations) typically require 30 days. The cure period is your client’s safety net.

    Red flag: Cure period under 5 days for monetary default, or no cure period for non-monetary defaults.

    12. Landlord’s Remedies: Acceleration, Lockout, Personal Guarantee

    This is where landlords can inflict maximum financial damage. According to Bean, Kinney & Korman, rent acceleration provisions require the tenant to pay all remaining rent for the entire lease term immediately upon default — potentially hundreds of thousands of dollars overnight. Courts in many jurisdictions find acceleration clauses unenforceable when they result in damages disproportionate to actual loss, but your client doesn’t want to litigate that question.

    Red flag: Acceleration of all remaining rent with no duty to mitigate, combined with a personal guarantee from the business owner. Personal guarantees put your client’s personal assets at risk — negotiate a cap, a time limit (the first 2 years), or a “good guy guaranty” that releases the guarantor upon vacancy.

    13. Options: Renewal, Expansion, Right of First Refusal

    Options give your client future flexibility. Renewal options prevent relocation risk. Expansion options let growing businesses take adjacent space. Right of first refusal on contiguous space provides a safety valve.

    Red flag: No options at all in a lease longer than 5 years. Your client builds their business at this location and has zero leverage at lease end.

    14. Co-Tenancy and Exclusivity Clauses

    Critical for retail tenants. Co-tenancy clauses give your client rights if an anchor tenant leaves (reduced rent or termination right). Exclusivity clauses prevent the landlord from leasing to a competitor in the same property.

    Red flag: No exclusivity clause in a retail lease, or a co-tenancy clause that requires multiple anchors to leave before triggering any remedy.

    15. Force Majeure and Casualty/Condemnation

    Force majeure determines what happens when performance becomes impossible (pandemic, natural disaster). Casualty provisions address what happens if the building is damaged. Condemnation provisions address government taking. Post-2020, these provisions carry real weight. For more context on force majeure provisions, read our force majeure clause guide.

    Red flag: Force majeure excuses only the landlord’s obligations (not the tenant’s), or casualty provisions that give the landlord unlimited time to rebuild while the tenant continues paying rent.

    NNN vs. Gross vs. Modified Gross: What Your Client Must Understand

    The lease type determines who bears operating costs — and the difference can be staggering.

    Lease Type Tenant Pays Landlord Pays Total Cost Predictability
    Triple Net (NNN) Base rent + taxes + insurance + CAM Structural repairs only Low — expenses fluctuate annually
    Gross/Full Service Flat monthly rent All operating expenses High — fixed monthly obligation
    Modified Gross Base rent + some expenses Remaining expenses Medium — negotiated split

    The real cost of a NNN lease: If your client sees base rent of $25/sf NNN, the actual occupancy cost is base rent ($25) plus estimated taxes ($4-8/sf) plus insurance ($1-3/sf) plus CAM ($3-8/sf). That $25/sf lease is actually $33-44/sf. According to Visual Lease, tenants in NNN leases must account for estimate-and-true-up reconciliation cycles where actual costs can exceed estimates by 15-20%.

    Always calculate the total occupancy cost — not just base rent — before your client signs.

    The CAM Charge Trap: Where Landlords Win and Tenants Lose

    CAM charges deserve special attention because they’re the most common source of commercial lease disputes.

    What landlords include in CAM (and shouldn’t):

    • Capital expenditures (roof replacement, parking lot resurfacing) — these are landlord improvements, not maintenance
    • Management fees exceeding 3-5% of total operating expenses
    • Costs of vacant space (the occupied tenants subsidize empty units)
    • Landlord’s legal and accounting fees
    • Marketing and leasing commissions
    • Costs attributable to landlord’s negligence

    Negotiate these protections:

    • Annual CAM cap: Limit increases to 3-5% per year over the base year
    • Exclusion list: Explicitly exclude capital expenditures, management fees above 5%, leasing costs, and landlord negligence costs
    • Audit rights: Right to audit landlord’s books annually with a fee-shifting provision (landlord pays audit costs if overcharges exceed 3-5%)
    • Base year vs. estimated CAM: Base year approaches are generally more favorable to tenants
    • Pro rata share calculation: Verify the denominator — is it total leasable area or total leased area?

    Commercial Lease Red Flags That Should Stop Any Deal

    These provisions put your client’s business — and sometimes personal assets — at serious risk:

    • Personal guarantee with no cap or sunset. If your client’s LLC provides no liability protection, the corporate form is meaningless. Negotiate a cap equal to 6-12 months’ rent and a sunset after 24 months of timely payments.
    • Continuous operating covenant. The client must keep the space open and operating even if the business is losing money. This prevents a controlled wind-down.
    • Demolition clause. The landlord can terminate the lease for redevelopment with minimal notice and no relocation assistance.
    • Relocation clause. The landlord can move the tenant to a different space in the property. Negotiate limits on frequency, distance, and cost.
    • Excessive landlord remedies. Acceleration of all future rent, lockout without court order, and seizure of tenant’s property. Review against ABA Model Rule 1.1 — competent representation requires understanding these provisions and their impact.
    • No cap on CAM increases. In a 10-year lease, uncapped CAM can double the total occupancy cost.

    How AI Assists with Commercial Lease Review

    AI-powered contract review tools are particularly useful for commercial leases because of the sheer volume of provisions to check. Here’s where AI adds the most value:

    What AI does well:
    – Identifies all 15 critical lease provisions and flags missing ones
    – Detects one-sided indemnification, excessive remedies, and missing tenant protections
    – Flags CAM provisions that include capital expenditures or lack annual caps
    – Catches rent escalation clauses without reasonable limits
    – Identifies personal guarantee provisions and their scope

    What still requires the lawyer:
    – Market analysis (is $30/sf NNN reasonable for this submarket?)
    – Negotiation strategy (which concessions to prioritize)
    – Client-specific risk assessment (what risk tolerance does this client have?)
    – Local market customs (what’s standard in this jurisdiction vs. what’s unusual)
    – Zoning and land use verification

    Clause Labs’s AI analyzer can process a 60-page commercial lease in under 60 seconds, flagging the clauses that need your attention so you can focus your time on market analysis and negotiation strategy rather than page-by-page reading. The Solo plan ($49/month for 25 reviews) handles the volume most solo practitioners need.

    As Clio’s 2025 Legal Trends Report found, 71% of solo law firms now use AI in their practice, with the fastest-growing adoption in document review tasks. For a deeper look at how AI compares to manual review, see our guide to reviewing contracts in 10 minutes.

    Frequently Asked Questions

    How long should a commercial lease review take?

    A thorough manual review of a standard commercial lease takes 3-5 hours, depending on length and complexity. With AI-assisted first-pass review, you can reduce that to 1-2 hours by focusing your manual attention on the flagged provisions and financial calculations. At $350/hour, the time savings from AI review pays for itself on the first lease.

    What’s the most important clause in a commercial lease?

    There’s no single answer — it depends on the client. For a startup tenant, the personal guarantee and termination provisions matter most (limiting downside risk). For an established retailer, the renewal option and exclusivity clause drive long-term value. For any tenant, the total occupancy cost (base rent + additional rent) is the number that determines whether the deal makes financial sense.

    Should I negotiate a personal guarantee out of a lease?

    Always try. Landlords expect pushback on personal guarantees. If the landlord won’t eliminate it entirely, negotiate: (a) a cap at 6-12 months’ rent, (b) a time-limited guarantee (first 24 months only), (c) a “burn-off” that reduces the guarantee over time as the tenant builds a payment history, or (d) a “good guy” guarantee that releases upon lease surrender and vacancy.

    Can AI review a lease as well as a real estate attorney?

    No. AI handles clause identification, risk flagging, and completeness checking. It doesn’t understand local market conditions, negotiate deal terms, or assess client-specific risk tolerance. Think of AI as a highly thorough first-pass reviewer that ensures you don’t miss anything — you still apply the judgment. The combination of AI efficiency and lawyer expertise is stronger than either alone.

    Join 500+ lawyers who use AI to catch what manual review misses. Start free with Clause Labs — upload any commercial lease and get an instant risk analysis. No credit card required.

    This article is for informational purposes only and does not constitute legal advice. Commercial lease terms vary significantly by jurisdiction and market. Consult a qualified attorney for advice specific to your situation.

  • Assignment and Change of Control Clauses: Protecting Clients in M&A

    Assignment and Change of Control Clauses: Protecting Clients in M&A

    Assignment and Change of Control Clauses: Protecting Clients in M&A

    An overlooked assignment restriction in a $12 million asset purchase nearly killed the deal three days before closing. The seller’s largest customer contract — representing 40% of the business’s revenue — contained a standard anti-assignment clause requiring the customer’s “prior written consent in its sole discretion.” The customer refused consent. Without that contract, the buyer’s revenue projections collapsed, the lender pulled financing, and the deal died. The clause was four lines long. Nobody flagged it during due diligence until the buyer’s junior associate ran a final checklist.

    According to the Association of Corporate Counsel, assignment provisions are among the most frequently overlooked clauses in M&A due diligence — and among the most consequential when they surface at the wrong moment. Try Clause Labs Free to see how AI identifies assignment restrictions and change of control provisions across your contract portfolio in minutes instead of days.

    Why Assignment Clauses Matter More Than You Think

    Assignment clauses determine whether a contract can be transferred to a third party. They sound straightforward. In practice, they create three distinct problems:

    In M&A transactions: If key contracts can’t be assigned, the deal may collapse or require significant price reductions. Buyers conducting “contract portability” analysis routinely discover that 20-30% of a target’s material contracts have assignment restrictions that weren’t identified earlier in due diligence.

    In financing: Lenders often require assignment of contract rights (specifically, accounts receivable) as collateral. Under UCC Section 9-406, anti-assignment clauses are generally overridden for assignments of payment rights — but the analysis is more complex than most transactional lawyers realize, and other contract rights may still be restricted.

    In business reorganizations: Companies that can’t assign contracts to affiliates or subsidiaries face obstacles during internal restructuring, tax-driven entity changes, and corporate reorganizations.

    As our contract review red flags checklist notes, assignment provisions are one of the most commonly missed red flags in routine contract review because they appear in the “boilerplate” section that gets the least attorney attention.

    Types of Assignment Restrictions

    Not all anti-assignment provisions are created equal. The differences in language create dramatically different consequences.

    The most common formulation:

    Neither party may assign this Agreement without the prior written consent
of the other party.

    The critical question is the consent standard. Two options dominate:

    “Not to be unreasonably withheld, conditioned, or delayed” — This is the borrower-friendly standard. The non-assigning party must have a legitimate business reason to refuse consent. Courts will evaluate whether the refusal was reasonable under the circumstances. If you’re the party who might need to assign the contract, fight for this language.

    “In its sole discretion” — This is effectively a veto. The non-assigning party can refuse for any reason or no reason. If you’re reviewing a contract that restricts assignment to “sole discretion” consent, understand that this clause may block a future sale of your client’s business entirely.

    The difference between these two standards has been described by practitioners as the difference between a speed bump and a brick wall. Negotiate accordingly.

    No Assignment At All

    This Agreement may not be assigned by either party under any circumstances.

    The strictest form. Even with consent, no assignment is permitted. In practice, courts sometimes refuse to enforce absolute prohibitions — particularly when the assignment occurs by operation of law (e.g., a merger). But drafting this language into a contract creates substantial risk for any party contemplating a future transaction.

    Assignment Permitted to Affiliates

    A standard carve-out:

    Either party may assign this Agreement to any affiliate without the other
party's consent, provided that the assigning party remains liable for
performance hereunder.

    This language permits internal reorganizations, subsidiary transfers, and corporate restructuring without triggering consent requirements. Two drafting issues to watch:

    1. Definition of “affiliate”: Does it require majority ownership (50%+)? Any ownership? Common control? The definition matters when a parent company reduces its stake in a subsidiary below the control threshold.

    2. Continuing liability: The “remains liable” language protects the non-assigning party if the affiliate fails to perform. Without it, the assignment could effectively transfer the obligation to an entity with fewer resources.

    Change of Control Triggers

    The provision that creates the most M&A friction:

    A change of control of either party shall be deemed an assignment for
purposes of this Section, and shall require the prior written consent
of the other party.

    This language captures transactions that don’t technically involve assignment — mergers, acquisitions, majority ownership changes — and subjects them to the same consent requirements. We’ll cover this in depth below.

    Assignment in M&A Transactions

    The treatment of assignment varies dramatically depending on the transaction structure.

    Asset Sales

    In an asset sale, the buyer acquires specific assets of the seller — including contracts. Each contract must be explicitly assigned from seller to buyer. Anti-assignment clauses are the primary obstacle.

    The due diligence imperative: Buyers should identify every material contract, categorize the assignment restriction in each, and determine whether consent is required. This “contract portability analysis” should happen early in due diligence — not three days before closing.

    Third-party consent process: For contracts requiring consent, the consent solicitation process typically involves:
    1. Identifying all contracts requiring consent
    2. Drafting consent request letters
    3. Sending requests with sufficient lead time before closing
    4. Negotiating with reluctant counterparties
    5. Determining which consents are conditions to closing

    Deal risk: If a material contract’s counterparty refuses consent, the deal structure may need to change. Options include converting to a stock sale (which avoids assignment), using an intermediary entity, or accepting the contract won’t transfer and adjusting the purchase price.

    Stock and Equity Sales

    In a stock or equity sale, the buyer acquires the equity of the target entity. The entity itself continues to exist — it just has a new owner. Since the contracts stay with the entity, no “assignment” occurs in the technical sense.

    But here’s the trap: change of control provisions may trigger consent requirements anyway. A well-drafted anti-assignment clause often includes “whether by merger, consolidation, change of control, operation of law, or otherwise.” This language captures stock sales, merging the assignment and change of control concepts.

    Buyers in stock transactions must review anti-assignment clauses just as carefully as in asset deals. The question isn’t “Is there an assignment?” — it’s “Does the clause define this transaction as an assignment?”

    Mergers

    In a merger, the target entity merges into the buyer (or a subsidiary), and the contracts transfer by operation of law. The general rule is that contracts survive a merger.

    However, as noted by contract drafting experts, many anti-assignment clauses specifically address mergers: “This Agreement may not be assigned, whether by merger, operation of law, or otherwise, without prior written consent.” If the clause includes “operation of law” or specifically references mergers, consent may be required even in a statutory merger.

    Courts are split on whether a standard anti-assignment clause (without the “operation of law” language) prohibits transfer by merger. The safest practice: assume it does, and plan accordingly.

    The Change of Control Clause

    Change of control provisions deserve separate analysis because they capture transactions that don’t technically involve assignment.

    What Triggers Change of Control

    A typical change of control definition includes:

    • Acquisition of majority voting power (50%+ of outstanding shares)
    • Merger or consolidation with another entity
    • Sale of all or substantially all assets (which overlaps with assignment)
    • Change in board composition (a majority of directors replaced)
    • IPO (sometimes included, though less common)

    The definition matters enormously. A narrow definition capturing only majority ownership changes leaves room for a 49% stake acquisition that gives effective control without triggering the clause. A broad definition capturing any “change in management or control” could be triggered by an executive departure.

    What Happens Upon Change of Control

    The consequences range from manageable to deal-breaking:

    Consequence Impact Negotiability
    Nothing (no provision) Contract continues undisturbed N/A
    Notice required Other party must be informed Low friction
    Consent required Other party can refuse High friction
    Termination right Other party can exit the contract High risk
    Renegotiation right Other party can demand new terms Moderate risk
    Acceleration Payments or obligations accelerate Financial risk

    In M&A, the termination right is the most dangerous outcome. If a material customer contract gives the customer the right to terminate upon change of control — with no compensation and no cure period — that contract’s value to the buyer drops substantially.

    Assignment and Change of Control Red Flags

    When reviewing contracts, flag these issues. For a comprehensive approach to identifying contract red flags, combine manual review with AI-assisted analysis.

    Red Flag 1: No Anti-Assignment Clause

    A contract with no assignment restriction can be freely assigned to anyone. This means your client’s counterparty could transfer the contract to a competitor, a company with fewer resources, or an entity in a less favorable jurisdiction. For service contracts where the identity of the performing party matters, this is a serious gap.

    As discussed above, “sole discretion” is effectively a veto. If your client might ever sell their business, this clause blocks the transaction unless the counterparty cooperates — and the counterparty has no obligation to cooperate.

    Red Flag 3: Change of Control Treated as Assignment

    If the clause deems a change of control to be an assignment, every potential acquisition, merger, or significant equity investment requires the counterparty’s consent. This can make your client’s business unsaleable or significantly reduce its value.

    Red Flag 4: No Affiliate Carve-Out

    Without an affiliate assignment exception, your client can’t reorganize internally. Moving a contract from a parent to a subsidiary, from one subsidiary to another, or consolidating entities all require consent. For growing companies, this is an unnecessary friction point.

    Red Flag 5: “By Operation of Law” Language

    The phrase “whether by merger, operation of law, or otherwise” is designed to capture every possible form of transfer — including statutory mergers. If this language appears in a contract, there is no transaction structure that avoids the consent requirement.

    Red Flag 6: Termination Right Upon Change of Control with No Compensation

    Some contracts give the non-assigning party the right to terminate immediately upon change of control, with no cure period and no termination fee. This puts the counterparty in a position to extract concessions during M&A negotiations: “I’ll consent to the change of control, but I want a 20% price reduction on the contract.”

    Red Flag 7: One-Sided Assignment Rights

    Watch for contracts where only one party’s assignment is restricted. If the vendor can freely assign the contract (including to an entity that provides inferior service) but your client cannot, the provision is fundamentally unbalanced.

    Negotiation Strategies

    When you encounter problematic assignment provisions, here are the most effective negotiation approaches.

    Push for “consent not to be unreasonably withheld.” This is the single most valuable edit you can make to an anti-assignment clause. It converts a potential veto into a reasonableness standard that courts can evaluate.

    Carve out affiliate assignments and internal reorganizations. Most counterparties will agree that internal corporate restructuring shouldn’t require consent, especially if the assigning party remains liable for performance.

    Limit the change of control definition to actual third-party acquisitions. Exclude internal reorganizations, IPOs, and changes in board composition from the change of control trigger. Narrow it to: acquisition of 50%+ of voting power by a third party that is not an affiliate.

    Add cure periods. If a change of control triggers a consent requirement, include a cure period (30-60 days) during which the assigning party can obtain consent before any termination right arises.

    Negotiate a termination fee as an alternative to consent. If the counterparty insists on a termination right upon change of control, negotiate a termination fee that compensates your client for the early termination. This removes the counterparty’s incentive to use the termination right as negotiating leverage.

    Include assignment rights in connection with a sale of the business. Specifically permit assignment in connection with a sale of all or substantially all of the assigning party’s assets, or in connection with a merger or consolidation. This directly addresses the M&A scenario.

    For detailed guidance on limitation of liability provisions that interact with assignment clauses — particularly in the context of successor liability — see our deep-dive guide. And if you’re reviewing vendor agreements where assignment is just one of many risk areas, our vendor agreement red flags guide covers the full picture.

    Want to check assignment provisions across multiple contracts before a transaction? Upload your first contract to Clause Labs for a free AI risk analysis — the Solo plan at $49/month handles 25 reviews for ongoing due diligence needs.

    How Clause Labs Reviews Assignment Provisions

    Clause Labs’s AI identifies assignment restrictions, change of control provisions, and consent requirements across every contract you upload. Specifically, it:

    • Flags missing anti-assignment clauses (open-ended transferability risk)
    • Detects one-sided assignment rights
    • Identifies the consent standard (“sole discretion” vs. “not unreasonably withheld”)
    • Checks for change of control treatment and M&A implications
    • Flags “operation of law” language that captures mergers
    • Detects missing affiliate carve-outs
    • Identifies termination rights triggered by assignment or change of control

    For M&A due diligence involving multiple contracts, the Professional plan ($149/month for up to 100 reviews) or the Team plan ($299/month with batch review for up to 10 contracts at once) can process an entire contract portfolio in hours instead of weeks.

    Frequently Asked Questions

    It depends on the contract language. If there’s no anti-assignment clause, contracts are generally freely assignable. If the clause says “no assignment without consent,” assignment without consent is a breach — but courts are split on whether the assignment is void (no effect) or merely voidable (effective until challenged). UCC Section 9-406 overrides anti-assignment clauses for assignments of accounts receivable and payment rights as security interests, regardless of what the contract says.

    Does a merger trigger anti-assignment clauses?

    It depends on the clause’s language. A standard “no assignment without consent” clause, without more, may or may not cover mergers — courts are divided. But clauses that include “whether by merger, operation of law, or otherwise” unambiguously capture mergers. OlenderFeldman LLP’s analysis of this issue notes that careful drafting is essential to resolve the ambiguity. Review every material contract’s specific language; don’t rely on general rules.

    What’s the difference between assignment and change of control?

    Assignment transfers the contract itself from one party to a new party. Change of control changes who owns or controls the contracting party, but the contracting party itself remains the same. A stock sale changes control; an asset sale requires assignment. Many contracts treat a change of control as if it were an assignment, but they are legally distinct concepts with different implications for SaaS agreements and other recurring-revenue contracts.

    Can I assign contract rights but not obligations?

    Technically yes — rights are assignable, obligations are delegable. You can assign the right to receive payment under a contract without delegating the obligation to perform. However, most anti-assignment clauses prohibit both assignment of rights and delegation of duties. And the non-assigning party is rarely willing to accept a new obligor without some say in the matter. The practical reality: most assignments involve both rights and obligations.

    How do assignment clauses affect M&A due diligence?

    They are a critical component of the “contract portability” analysis in any deal. Buyers should: (1) identify all material contracts, (2) categorize the assignment restriction in each, (3) determine which require consent and under what standard, (4) assess the likelihood of obtaining consent from each counterparty, and (5) build the consent timeline into the closing schedule. Contracts where consent is unlikely should be flagged as deal risks and reflected in the purchase price negotiation.

    This article is for informational purposes only and does not constitute legal advice. Assignment and change of control provisions have significant implications for M&A transactions, financing, and business operations. Consult a qualified attorney for advice specific to your situation.

    Need to review assignment provisions across a portfolio of contracts? Clause Labs’s batch review processes up to 10 contracts simultaneously, flagging assignment restrictions, change of control triggers, and consent requirements — so your due diligence team can focus on negotiation strategy instead of document review.

  • Governing Law and Jurisdiction Clauses: How to Choose (and Why It Matters)

    Governing Law and Jurisdiction Clauses: How to Choose (and Why It Matters)

    Governing Law and Jurisdiction Clauses: How to Choose (and Why It Matters)

    Most lawyers copy-paste their governing law clause from the last deal they closed. According to Clio’s 2025 Legal Trends Report, solo and small firm attorneys handle an average of 38% utilization rate across a packed day — which means the “boilerplate” sections of contracts get the least attention. The governing law clause is almost always one of them. That’s a mistake that can cost your client six figures in litigation expenses when a dispute lands in the wrong court, under the wrong state’s laws, with the wrong procedural rules.

    A governing law clause determines which state or country’s laws interpret the contract. A jurisdiction clause determines where disputes get litigated. These are different provisions that serve different functions, and getting either one wrong creates problems that compound the moment a dispute arises. Try Clause Labs Free to see how AI flags governing law mismatches and missing venue provisions in seconds.

    Two Clauses, Two Different Questions

    The governing law clause answers: “Which legal framework applies to this contract?” The jurisdiction (or venue) clause answers: “Where do the parties resolve disputes?”

    They often appear in the same paragraph, which leads many attorneys to treat them as a single provision. They aren’t. You can have New York governing law with California jurisdiction — a California court applying New York law. Whether that’s wise is a different question entirely.

    Governing law determines:
    – How courts interpret ambiguous contract language
    – Which default rules fill gaps the contract doesn’t address
    – What remedies are available for breach
    – Which statute of limitations applies
    – Whether specific performance is available

    Jurisdiction and venue determine:
    – Which court hears the dispute
    – What procedural rules apply
    – Whether a jury trial is available
    – How fast the case moves through litigation
    – What discovery rules apply

    Treating these as afterthought provisions is the contractual equivalent of letting your opponent choose the playing field and the rulebook.

    How to Choose Governing Law

    The choice of governing law should be a strategic decision, not a default. Here are the factors that should drive it.

    Where the Parties Are Located

    If both parties are in the same state, that state’s law is the natural choice. Courts are most comfortable applying their own law, and both sides’ attorneys presumably know it. The calculus gets more complex when parties are in different states — or different countries.

    Which State’s Laws Favor Your Client

    This is the factor most lawyers skip. Different states reach different conclusions on the same contractual issues. Non-compete enforceability, for example, varies dramatically: California Bus. & Prof. Code Section 16600 voids most non-competes, while Florida Statute Section 542.335 enforces them with specific requirements.

    Before defaulting to your home state, ask: On the issues most likely to be disputed in this contract, which state’s law produces the best outcome for my client?

    Industry Conventions

    Certain states have earned their role as default choices for specific transaction types:

    State Preferred For Why
    Delaware Corporate agreements, LLC operating agreements, M&A Most developed body of corporate law; Court of Chancery specializes in business disputes; extensive case law on fiduciary duties
    New York Financial contracts, complex commercial deals, licensing Sophisticated commercial law; GOB Section 5-1401 honors choice of New York law for transactions exceeding $250,000 even without a nexus to the state
    California Technology contracts, employment agreements Strong employee protections; developed IP and trade secret law; tech industry precedents
    Texas Energy, oil and gas, natural resources Favorable business law; developed body of energy contract precedent
    England & Wales International commercial contracts Well-developed common law; perceived as neutral for cross-border deals; extensive arbitration infrastructure in London

    The UCC Reasonable Relation Test

    For contracts involving the sale of goods, UCC Section 1-301 requires a “reasonable relation” between the transaction and the chosen state’s law. A transaction has a reasonable relation to a state when a significant enough portion of the making or performance of the contract occurs there. Choosing a state with no connection to the deal may result in a court refusing to honor the choice.

    For non-UCC contracts, courts apply a similar but less codified analysis under the Restatement (Second) of Conflict of Laws. The general rule: choice of law clauses are enforceable unless they violate fundamental public policy of the state whose law would otherwise apply, or the chosen state has no substantial relationship to the parties or transaction.

    The New York exception: New York GOB Section 5-1401 allows parties to choose New York law for any commercial transaction valued at $250,000 or more, regardless of whether the transaction has any connection to New York. This is why New York law appears in so many financial contracts — the parties don’t need a nexus to the state.

    How to Choose Jurisdiction and Venue

    Jurisdiction and venue decisions involve a different set of considerations than governing law.

    Exclusive vs. Non-Exclusive Jurisdiction

    This is often the most consequential drafting choice in the entire provision.

    Exclusive jurisdiction: Disputes must be litigated in the designated forum. No other court will hear the case (assuming the clause is enforceable). This gives you predictability — you know exactly where you’ll litigate.

    Non-exclusive jurisdiction: Disputes may be litigated in the designated forum, but other forums are also available. This gives flexibility but less certainty.

    When to push for exclusive jurisdiction:
    – Your client is the likely defendant (you want to litigate at home)
    – You want to prevent forum shopping by the other party
    – The designated court has subject matter expertise (e.g., Delaware Chancery for corporate disputes)

    When to accept non-exclusive jurisdiction:
    – Your client might need to sue in the other party’s jurisdiction to reach their assets
    – You want to preserve the option of filing where the harm occurred
    – The other side won’t agree to exclusive jurisdiction in your forum

    Factors That Matter

    Court sophistication. Not all courts handle commercial disputes equally well. Delaware’s Court of Chancery, New York’s Commercial Division, and the federal courts in the Southern District of New York are known for judges with deep commercial experience.

    Speed of resolution. Some jurisdictions move faster than others. If your client needs a quick resolution (e.g., trade secret injunction), choose a forum known for efficient case management.

    Cost of litigation. Litigating in New York City or San Francisco is materially more expensive than litigating in smaller markets. Factor in travel costs, local counsel fees, and the general cost of doing business in that jurisdiction.

    Jury trial availability. Some contracts include jury trial waivers. If you can’t get a waiver, consider that some jurisdictions and judge pools are more favorable to plaintiffs or defendants.

    The Mismatch Problem

    Governing law and jurisdiction don’t have to match — but mismatches create real costs.

    Consider this scenario: A contract specifies New York governing law with venue in California state court. A dispute arises. Now you have a California judge applying New York law. The practical consequences:

    • Expert testimony costs: The California court may need expert testimony on New York law (yes, this happens — judges aren’t presumed to know other states’ law)
    • Interpretive risk: The California court may apply New York statutory language through a California jurisprudential lens, reaching a result that no New York court would reach
    • Appellate uncertainty: California appellate courts review New York law questions de novo, but may lack the institutional expertise to get it right

    The Holland & Knight guide on drafting choice of law provisions recommends aligning governing law and jurisdiction whenever possible. The only common exception: Delaware governing law with New York venue, which works because New York courts routinely apply Delaware corporate law and have deep familiarity with it.

    Practice tip: If your client insists on their home state for jurisdiction but the other side insists on a different state for governing law, the mismatch is usually not worth the compromise. Push to align them, or agree on a neutral third state for both.

    Governing Law Red Flags

    When reviewing contracts — especially those drafted by the other side — watch for these issues. If you want a fast first pass, upload the contract to Clause Labs and the AI will flag governing law and jurisdiction issues automatically.

    No Governing Law Clause At All

    Without a choice of law provision, courts apply their own conflict-of-laws rules to determine which state’s law governs. This is unpredictable, expensive to litigate, and gives the party who files first an advantage (they choose the forum, which influences the conflict-of-laws analysis). As our complete contract review checklist explains, a missing governing law clause is a red flag in any commercial agreement.

    Governing Law With No Connection to Either Party

    If neither party is located in the chosen state, no performance occurs there, and the state wasn’t chosen for its favorable legal framework, courts may refuse to honor the choice. Under the Restatement approach, there must be a “substantial relationship” between the parties/transaction and the chosen state, or another reasonable basis for the choice.

    Mandatory Local Laws That Override the Choice

    Certain laws can’t be contracted around, regardless of what the governing law clause says:

    • Employment laws: You can’t use a Texas governing law clause to avoid California wage and hour requirements for a California employee
    • Consumer protection statutes: Many states prohibit choice of law clauses in consumer contracts that would strip consumers of their home state protections
    • Insurance regulations: Some states require their own insurance laws to apply to policies issued or delivered in-state
    • Real property: The law of the state where real property is located generally governs real property transactions, regardless of contractual choice

    Multiple Conflicting Provisions

    In long contracts — especially those assembled from multiple precedents — governing law provisions sometimes appear in more than one place and contradict each other. Section 18 says “New York law,” but the arbitration clause in Section 22 says “the arbitration shall be governed by California law.” This ambiguity is litigated more often than you’d expect. If you’re reviewing vendor agreements for red flags, contradictory governing law provisions should be near the top of your checklist.

    Special Considerations by Contract Type

    International Contracts

    Cross-border deals raise additional layers of complexity.

    The CISG trap: If you choose “the laws of the State of New York” as governing law in an international sale of goods, you may inadvertently invoke the United Nations Convention on Contracts for the International Sale of Goods (CISG) — which is part of federal law in the United States and automatically applies to international goods sales unless explicitly excluded. A standard choice of law clause does not opt out of CISG. You must specifically state: “The parties agree that the CISG shall not apply to this agreement.”

    Arbitration in international disputes: For international contracts, arbitration is often preferable to litigation because of the New York Convention, which makes arbitral awards enforceable in 172 countries. Foreign court judgments, by contrast, have no equivalent enforcement mechanism.

    Seat of arbitration: In international arbitration, the “seat” determines the procedural law governing the arbitration and the courts with supervisory jurisdiction. Common seats include London, Singapore, Paris, and New York. The seat should be in a jurisdiction that supports arbitration and has acceded to the New York Convention.

    Employment Contracts

    Employment law creates some of the most rigid constraints on governing law choices.

    You generally cannot use a choice of law clause to avoid the mandatory employment protections of the state where the employee works. A Delaware governing law clause in an employment agreement for a California-based employee won’t prevent California courts from applying California’s prohibition on non-competes, its overtime rules, or its meal and rest break requirements.

    ABA Model Rule 1.1 requires competence in understanding these jurisdiction-specific limitations. A limitation of liability clause might be enforceable under the chosen governing law but unenforceable for certain employment claims under the employee’s local law.

    SaaS and Technology Agreements

    SaaS agreements commonly specify California or Delaware governing law, reflecting the vendor’s home jurisdiction. As discussed in our SaaS agreement review guide, the governing law choice in a SaaS contract can affect:

    • Whether SLA credits constitute an adequate remedy
    • Data breach notification requirements and timing
    • Whether automatic renewal provisions are enforceable
    • Which privacy and data protection laws apply to the vendor’s data processing

    Sample Governing Law and Jurisdiction Clauses

    Basic Governing Law with Exclusive Jurisdiction

    Governing Law. This Agreement shall be governed by and construed in accordance
with the laws of the State of [State], without regard to its conflict of laws
principles.

Jurisdiction. Each party irrevocably submits to the exclusive jurisdiction of
the state and federal courts located in [County], [State] for the purpose of
any suit, action, or proceeding arising out of or relating to this Agreement.

    Note: The “without regard to conflict of laws principles” language is critical. Without it, a court might apply the chosen state’s conflict-of-laws rules, which could point to a different state’s substantive law — defeating the entire purpose of the clause.

    Governing Law with Jury Trial Waiver

    EACH PARTY HEREBY IRREVOCABLY WAIVES ALL RIGHT TO TRIAL BY JURY IN ANY
ACTION, PROCEEDING, OR COUNTERCLAIM ARISING OUT OF OR RELATING TO THIS
AGREEMENT.

    Jury trial waivers are enforceable in most (but not all) jurisdictions. They are standard in financial contracts and increasingly common in commercial agreements. Courts generally require that waivers be conspicuous — hence the all-caps formatting.

    International Contract with Arbitration

    Governing Law. This Agreement shall be governed by the laws of England and
Wales. The parties expressly agree that the United Nations Convention on
Contracts for the International Sale of Goods (CISG) shall not apply to
this Agreement.

Dispute Resolution. Any dispute arising out of or in connection with this
Agreement shall be finally resolved by arbitration under the Rules of the
London Court of International Arbitration (LCIA). The seat of arbitration
shall be London. The language of the arbitration shall be English.

    How Clause Labs Reviews Governing Law and Jurisdiction Provisions

    Clause Labs’s AI analysis identifies governing law and jurisdiction provisions and checks for:

    • Missing governing law clause (flagged as a Critical risk)
    • Mismatch between governing law and jurisdiction
    • Exclusive vs. non-exclusive jurisdiction designation
    • Missing “without regard to conflict of laws principles” language
    • Jury trial waivers (flagged for awareness)
    • CISG opt-out in international sale of goods contracts
    • Multiple conflicting governing law provisions

    The AI doesn’t replace your judgment about which governing law is best for your client — that requires understanding the specific deal, the parties’ relative positions, and the substantive issues most likely to be disputed. But it catches the structural issues that many lawyers miss in the boilerplate sections — the same issues that create problems with assignment and change of control clauses when deals move to due diligence.

    Frequently Asked Questions

    Does governing law have to be where one of the parties is located?

    No. Parties can generally choose any state’s law, subject to limitations. Under UCC 1-301, the transaction must bear a “reasonable relation” to the chosen state for goods contracts. For non-UCC contracts, courts require a “substantial relationship” or “reasonable basis” for the choice. The major exception is New York, where GOB Section 5-1401 allows parties to choose New York law for any commercial transaction over $250,000 regardless of nexus.

    What’s the difference between jurisdiction and venue?

    Jurisdiction refers to a court’s authority to hear a case — whether the court has power over the parties and the subject matter. Venue refers to the specific geographic location within a jurisdiction where the case is filed. A clause might specify “the federal courts of the State of New York” (jurisdiction) and “the Southern District of New York” (venue). Both are important; specifying only jurisdiction leaves the question of which specific courthouse open to the filing party.

    Should I always push for my client’s home state?

    Not necessarily. Your client’s home state might have unfavorable law on the most contentious issues. A vendor in California selling SaaS to enterprise customers might prefer Delaware governing law because Delaware enforces limitation of liability provisions more predictably than California. Analyze the substantive issues first, then choose the governing law that best serves your client’s interests.

    Can governing law clauses be challenged?

    Yes. Courts may refuse to enforce a choice of law clause if: (1) the chosen state has no substantial relationship to the transaction and there’s no reasonable basis for the choice; (2) application of the chosen law would violate a fundamental policy of the state whose law would otherwise apply; or (3) mandatory local laws override the contractual choice (employment, consumer protection, insurance). The party challenging the clause bears the burden of showing why it shouldn’t be enforced.

    Can I choose different governing law for different parts of the contract?

    Yes, this is called “depecage.” You might specify Delaware law for corporate governance provisions and New York law for the commercial terms. It’s uncommon outside complex M&A transactions, and it creates interpretive challenges at the boundary between provisions. Unless there’s a compelling reason, stick with a single governing law for the entire agreement.

    This article is for informational purposes only and does not constitute legal advice. Governing law and jurisdiction choices have significant legal consequences. Consult a qualified attorney licensed in the relevant jurisdictions for advice specific to your situation.

    Ready to check your contracts for governing law and jurisdiction issues? Upload any contract to Clause Labs — free for 3 reviews per month, no credit card required — and get an AI-powered risk analysis in under 60 seconds.

  • Most Favored Nation Clauses: A Plain English Guide for Transactional Lawyers

    Most Favored Nation Clauses: A Plain English Guide for Transactional Lawyers

    Most Favored Nation Clauses: A Plain English Guide for Transactional Lawyers

    A SaaS vendor signed an MFN clause with Client A guaranteeing “the most favorable pricing offered to any similarly situated customer.” Eighteen months later, the vendor offered Client B a 40% discount to close an end-of-quarter deal. Client A’s procurement team audited, found the discount, and demanded retroactive price matching across 18 months of invoices. The bill: $380,000 in credits. The vendor’s sales team had no idea the MFN clause existed when they approved Client B’s discount.

    Most Favored Nation clauses — also called “best pricing,” “price parity,” or “most favored customer” provisions — create obligations that ripple across every future deal. Yet they’re often treated as boilerplate, buried in a pricing appendix, and forgotten until an audit surfaces a trigger event. According to World Commerce & Contracting, contract-related value leakage costs businesses an average of 9% of annual revenue, and MFN clauses are a significant contributor because their implications compound as the business grows.

    This article explains how MFN clauses work, the different types, the antitrust risks, and the specific drafting choices that determine whether an MFN protects your client or constrains every future transaction. If you’re reviewing a contract with an MFN provision right now, upload it to Clause Labs’s free analyzer to flag scope issues, missing exclusions, and retroactive triggers in under 60 seconds.

    What Is a Most Favored Nation Clause?

    In plain terms: “If you give someone else a better deal, you have to give me the same deal.”

    The concept originates in international trade law — trade treaties where one nation guarantees another the best tariff rates offered to any trading partner. In commercial contracts, an MFN clause guarantees that one party (the beneficiary) will receive terms at least as favorable as those offered to any comparable customer, partner, or counterpart.

    A basic MFN provision looks like this:

    “Vendor shall not charge Customer fees in excess of the lowest fees charged by Vendor to any other customer for substantially similar services during the term of this Agreement.”

    Simple to read. Extraordinarily complex in practice.

    The core variables that determine how an MFN actually operates:

    • Scope: Does the MFN cover pricing only, or all terms (SLAs, payment terms, support levels)?
    • Comparator: What constitutes “similarly situated” or “comparable”? Same volume? Same contract length? Same industry?
    • Direction: One-way (protects only the beneficiary) or mutual?
    • Trigger: Automatic adjustment, adjustment upon request, or adjustment upon audit?
    • Timing: Retroactive (credits for past overcharges) or prospective (better terms going forward only)?

    Each variable dramatically changes the clause’s practical impact.

    Types of MFN Clauses

    Pricing MFN

    The most common form. The vendor guarantees the beneficiary pricing that is at least as favorable as the best pricing offered to any comparable customer.

    Vendor represents that the fees set forth herein are no higher than the lowest
fees charged by Vendor to any other customer for substantially similar services
in similar quantities. If Vendor offers lower fees to any such customer during
the term of this Agreement, Vendor shall reduce Customer's fees accordingly.

    Key issues: What constitutes “substantially similar services”? What does “similar quantities” mean? If Client A buys 100 licenses and Client B gets a discount for buying 10,000, does the MFN trigger? Without precise definitions, these questions become disputes.

    Terms MFN

    Broader and more aggressive. The beneficiary is entitled not just to the best pricing but to the best overall terms — SLAs, payment terms, support response times, warranty periods, anything.

    If Vendor offers to any customer more favorable terms and conditions than those
set forth in this Agreement for comparable services, Vendor shall promptly
notify Customer and extend such more favorable terms to Customer upon request.

    Why it’s dangerous for the grantor: Every negotiation with every other customer is constrained. A vendor who agrees to a 99.99% SLA with one customer may be obligated to provide that same SLA to the MFN beneficiary — even if the MFN beneficiary is paying a fraction of the price.

    Retroactive vs. Prospective

    Retroactive MFN: If the vendor offers Client B a lower price today, Client A receives credits retroactive to the start of the agreement (or the start of the current term). This is the most expensive version for the grantor. The SaaS vendor in the opening example faced $380,000 in credits because the MFN was retroactive.

    Prospective MFN: Better terms apply going forward only, from the date the trigger event occurs. The beneficiary doesn’t receive credits for historical overcharges. This is significantly less costly and more commercially reasonable.

    The difference between retroactive and prospective application can represent hundreds of thousands of dollars. This single word in the drafting — “retroactively” vs. “prospectively” — is worth more negotiation time than most lawyers give it.

    Audit-Based vs. Automatic

    Audit-based MFN: The beneficiary has the right to audit the grantor’s records to determine whether better terms have been offered elsewhere. If the audit reveals a trigger, the beneficiary receives an adjustment.

    Automatic MFN: The grantor must proactively notify the beneficiary and adjust terms whenever a trigger event occurs, without waiting for an audit.

    Practical reality: Audit-based MFNs are more common because they shift the enforcement burden to the beneficiary. But they also create friction — audits are expensive, time-consuming, and can damage the commercial relationship. Automatic MFNs are more protective but require the grantor to build compliance monitoring into every pricing decision.

    MFN Clause Risks and Traps

    Risks for the Grantor (Vendor/Supplier)

    Every future deal is constrained. Once you grant an MFN, your sales team can’t offer a discount, promotional price, or custom deal structure to any customer without potentially triggering obligations to the MFN beneficiary.

    Volume discounts trigger MFN for small customers. If Client B gets a 30% discount for committing to 10x the volume of Client A, the MFN beneficiary may argue they’re entitled to the same 30% discount at their smaller volume — unless the clause explicitly excludes volume-based pricing.

    Promotional pricing creates cascading obligations. End-of-quarter discounts, launch promotions, and competitive displacement pricing all potentially trigger MFN adjustments.

    Stacking problem. If multiple customers have MFN clauses, any discount offered to one customer triggers adjustments for all MFN holders. The result is a “race to the bottom” where the vendor’s best discount becomes the price floor for every MFN customer.

    Custom deal structures become nearly impossible. Creative pricing — bundled services, tiered commitments, value-based pricing — gets flattened into commodity pricing because any variation could trigger an MFN claim.

    Risks for the Beneficiary (Customer/Buyer)

    Enforcement is difficult. How does the beneficiary know the vendor offered someone else a better deal? Unless the MFN includes audit rights, the beneficiary is relying on the vendor’s voluntary compliance.

    “Comparable” loophole. Vendors learn to structure deals to avoid MFN triggers. Different service tiers, different packaging, different payment structures — all designed to make each deal “not comparable” to the MFN baseline.

    Bespoke SOW pricing. If pricing adjustments are buried in statements of work rather than the master agreement, the MFN may not capture them. This is particularly common in MSA/SOW structures — see our guide on reviewing contracts for red flags for related patterns.

    Audit costs. Exercising audit rights — hiring accountants, reviewing records, traveling to the vendor’s offices — can cost more than the expected recovery. According to the ABA Business Law Today analysis of MFN enforcement challenges, the cost of enforcement often exceeds the benefit for small or mid-size contracts.

    The Antitrust Dimension

    MFN clauses aren’t just a contract drafting issue — they carry significant antitrust risk.

    The DOJ and FTC Perspective

    The Department of Justice has studied MFN clauses extensively. In a public workshop on MFN clauses and antitrust enforcement, the DOJ’s Antitrust Division examined how MFNs can reduce price competition, facilitate coordinated pricing, and create barriers to entry.

    According to Winston & Strawn’s antitrust analysis, the primary antitrust concerns with MFN clauses are:

    • Reduced price competition. If a vendor can’t offer lower prices to new customers without triggering MFN adjustments across existing contracts, the incentive to compete on price diminishes.
    • Facilitated tacit collusion. MFN clauses make price floors more transparent and stable, reducing the incentive for vendors to cut prices.
    • Barriers to entry. New market entrants who would normally compete on price are disadvantaged because existing vendors’ MFN obligations prevent competitive responses.

    The Amazon Example

    The most high-profile MFN enforcement action involves Amazon. The FTC and 17 state attorneys general filed a complaint alleging that Amazon’s “fair pricing” policies function as de facto MFN clauses — requiring sellers to maintain the lowest prices on Amazon or face suppression in search results and removal from the Buy Box. According to Bona Law’s analysis, no U.S. court has yet found that an MFN provision, standing alone, violates antitrust law — but courts have approved consent decrees that enjoined MFN use.

    Practical Takeaway

    MFN clauses in contracts with significant market power deserve antitrust scrutiny. For typical B2B contracts between non-dominant parties, antitrust risk is low but not zero. If your client is the dominant player in their market, consult antitrust counsel before granting or requiring broad MFN provisions.

    Whether you’re granting or receiving an MFN, Clause Labs’s Professional tier ($149/month) lets you compare MFN language across contracts side by side using the contract comparison feature — so you can spot scope variations and inconsistencies before they create cascading obligations.

    Drafting and Negotiating MFN Clauses

    For the Grantor: Limiting MFN Exposure

    If you must agree to an MFN, negotiate these limitations:

    Narrow the scope to pricing only. Don’t agree to a terms MFN if a pricing MFN will satisfy the beneficiary. SLA commitments, support levels, and payment terms should remain individually negotiated.

    Define “comparable” precisely. Specify the comparators: same service tier, same volume range, same contract term, same payment structure. The more specific, the fewer trigger events.

    Exclude volume discounts and promotional pricing. Carve out pricing offered in connection with volume commitments exceeding X units, time-limited promotional offers, competitive displacement deals, and strategic partnership pricing.

    Make it prospective, not retroactive. If better pricing is offered elsewhere, the adjustment applies going forward from the date of discovery — not retroactively to the start of the agreement.

    Limit the audit right. Allow one audit per 12-month period, at the beneficiary’s expense (unless the audit reveals a material discrepancy, in which case the grantor pays). Restrict audit scope to pricing records, not all commercial terms.

    Cap the remedy. If the MFN triggers, the remedy is a price adjustment and, if retroactive, a credit for the difference. The MFN should not give the beneficiary a termination right or damages claim.

    For the Beneficiary: Strengthening MFN Protection

    If you’re seeking MFN protection for your client:

    Broaden the comparator. Push for “any customer” rather than “similarly situated customer.” The broader the comparator group, the more trigger events the MFN captures.

    Make it automatic with notification. The grantor must proactively notify the beneficiary and adjust pricing whenever better terms are offered elsewhere — don’t rely on audits to discover triggers.

    Include retroactive adjustment. If the grantor offered better pricing six months ago and didn’t notify, the beneficiary should receive credits back to the date of the trigger event.

    Secure audit rights. Annual audit right at grantor’s expense if material discrepancies are found. Include access to pricing records, customer lists (redacted as needed), and discount approvals.

    Add a termination right. If the grantor fails to honor the MFN after notification, the beneficiary can terminate for cause without a cure period — this creates real enforcement teeth.

    MFN by Contract Type

    SaaS Agreements

    What’s typical: Pricing MFN, prospective, audit-based. “Vendor will not charge Customer more than the lowest published list price for the same service tier and usage level.”

    What’s negotiable: Published list price vs. actual transaction price (major difference — discounts aren’t reflected in list prices). Audit rights. Whether custom enterprise pricing triggers the MFN.

    Red flag: MFN tied to “list price” only. Vendors can offer 50% off list to other customers and argue the MFN only benchmarks against the undiscounted price. For a deeper analysis of SaaS-specific provisions, see our guide on reviewing SaaS agreements.

    Licensing Agreements

    What’s typical: Royalty MFN. “Licensor shall not grant a license for the Licensed Technology to any third party at a royalty rate lower than Customer’s rate.”

    Key issue: Do different license scopes (exclusive vs. non-exclusive, territory-limited vs. worldwide) qualify as “comparable”? They usually shouldn’t, and the clause should say so explicitly.

    Supply and Distribution Agreements

    What’s typical: Pricing and territory MFN. “Supplier shall not sell Product to any other distributor in the Territory at a price below the price charged to Distributor.”

    Key issue: Whether the MFN extends to direct sales by the supplier (competing with its own distributor). A well-drafted MFN in a distribution agreement covers both third-party and direct-sale pricing.

    Insurance Contracts

    What’s typical: Coverage MFN. “Insurer shall provide Insured with coverage terms no less favorable than those offered to any other insured with a comparable risk profile.”

    Key issue: “Comparable risk profile” is inherently subjective and frequently disputed. The clause should specify the risk factors that define comparability.

    MFN Red Flags to Catch in Review

    When reviewing any contract with an MFN provision, flag these issues:

    • One-sided MFN without reciprocal obligations. Only one party is constrained. The other can negotiate freely.
    • No exclusions for volume discounts, promotional pricing, or strategic deals. Every pricing decision becomes an MFN trigger.
    • Retroactive adjustment without cap. Credits could extend back to the start of the agreement — potentially years of pricing differential.
    • “All terms” scope without limitation. The beneficiary can cherry-pick the best individual terms from different contracts, creating a Frankenstein agreement no real customer has.
    • No audit frequency limitation. The beneficiary could audit continuously, creating administrative burden and relationship friction.
    • No definition of “comparable” or “similarly situated.” Everything is comparable until the grantor proves otherwise — and the burden of proof is on the wrong party.
    • Interaction with limitation of liability. MFN credits and adjustments should be covered by (not excluded from) the contract’s liability cap.

    How Clause Labs Handles MFN Clauses

    MFN provisions are notoriously easy to miss during review — they’re often buried in pricing schedules, general terms sections, or appendices rather than called out in a dedicated section. Clause Labs’s AI identifies MFN provisions regardless of where they appear and flags:

    • One-sided MFN with no reciprocal obligations
    • Missing exclusions for volume, promotional, and strategic pricing
    • Retroactive trigger mechanisms
    • Absent audit-right limitations
    • Interaction between MFN obligations and other contract provisions (pricing, termination, limitation of liability)

    Frequently Asked Questions

    Are MFN clauses enforceable?

    Yes — MFN clauses are generally enforceable as standard contract provisions. Courts treat them like any other pricing or commercial term, applying standard contract interpretation principles. The primary enforceability challenge isn’t the clause itself but proving that a trigger event occurred (i.e., that the grantor offered better terms elsewhere). This is why audit rights are essential for MFN beneficiaries.

    Can I have an MFN clause in a SaaS agreement?

    Yes, and they’re increasingly common — particularly in enterprise SaaS contracts where the customer has significant negotiating leverage. The SaaS vendor will typically push for a narrow MFN limited to published list pricing for the same service tier, while the customer will push for a broader MFN covering actual transaction pricing. The final MFN scope depends on leverage and competitive dynamics.

    How do I enforce an MFN clause?

    Enforcement typically requires: (1) discovering that better terms were offered elsewhere (through audit rights, market intelligence, or the grantor’s notification obligation), (2) demonstrating that the comparator deal involves “comparable” or “similarly situated” customers (as defined in the clause), and (3) demanding the adjustment (price credit, go-forward reduction, or both). If the grantor refuses, the remedy depends on the contract — it may be a breach-of-contract claim, a termination right, or both.

    Should I accept an MFN clause from my vendor?

    As the beneficiary, an MFN clause protects your client against preferential pricing — so yes, seek it when you have leverage. But understand its limitations: enforcement is expensive, “comparable” is easy to argue around, and the vendor will likely structure future deals to avoid triggering the MFN. An MFN is better than nothing, but it’s not a guarantee of the best price — it’s a contractual tool that requires monitoring and enforcement.

    Do MFN clauses create antitrust issues?

    They can, particularly when imposed by a dominant market player. The DOJ and FTC have scrutinized MFN clauses in contexts where they reduce price competition, facilitate collusion, or create barriers to market entry. For contracts between non-dominant parties in competitive markets, antitrust risk is low. For contracts involving platforms, dominant suppliers, or industry-wide pricing standards, consult antitrust counsel. As noted in Secretariat’s competition analysis, platform MFN clauses (PMFNs) receive the highest level of regulatory scrutiny.

    This article is for informational purposes only and does not constitute legal advice. Consult a qualified attorney for advice specific to your situation.

    MFN clauses create obligations that compound across every future deal. If you’re reviewing a contract with pricing parity, best-pricing, or MFN language, upload it to Clause Labs to check the scope, exclusions, and trigger mechanisms before your client signs. Free tier: 3 reviews/month, no credit card required.

  • Confidentiality Clauses vs NDAs: When to Use Which (and Why It Matters)

    Confidentiality Clauses vs NDAs: When to Use Which (and Why It Matters)

    Confidentiality Clauses vs NDAs: When to Use Which (and Why It Matters)

    A confidentiality clause buried in Section 14 of your MSA is not the same thing as a standalone NDA signed before the first meeting. Yet lawyers and business professionals use these terms interchangeably every day, and the confusion creates real gaps in protection. According to Clio’s 2025 Legal Trends Report, contract review remains one of the highest-volume tasks for solo and small firm lawyers — and confidentiality provisions appear in virtually every agreement that crosses your desk.

    The distinction matters because choosing the wrong instrument at the wrong time can leave your client’s trade secrets, financial data, or proprietary processes exposed. Here’s how to decide which one fits, when you need both, and the drafting differences that actually affect enforceability.

    Upload your NDA or agreement now and get an AI-powered confidentiality analysis in under 60 seconds — free, no signup required.

    They Solve Different Problems

    A standalone NDA (non-disclosure agreement) is a self-contained contract whose entire purpose is governing the exchange of confidential information between parties. It typically runs 2-5 pages, defines confidential information in detail, lists standard exclusions, specifies duration, addresses remedies, and includes provisions for return or destruction of materials.

    A confidentiality clause is a provision embedded within a larger agreement — an MSA, employment contract, vendor agreement, or partnership agreement. It usually occupies 1-3 paragraphs and relies on the host agreement’s broader framework for remedies, termination, and dispute resolution.

    The core question is timing and context:

    • NDAs govern the sharing of sensitive information before a broader agreement exists
    • Confidentiality clauses govern information exchanged during an existing contractual relationship

    This distinction drives everything else: scope, enforceability, duration, and remedies.

    When a Standalone NDA Is the Right Choice

    Use a standalone NDA when no other agreement governs the relationship between the parties. The most common scenarios:

    Pre-deal discussions. Before an acquisition, investment round, or strategic partnership, parties need to share financial data, customer lists, technology specifications, and business strategies. No MSA or operating agreement exists yet. An NDA is the only protection. According to the ABA’s guidance on confidentiality obligations, lawyers have an independent duty under Model Rule 1.6 to protect client information — but that doesn’t extend to the other party’s obligations. You need a contract.

    Due diligence periods. M&A due diligence involves reviewing financials, litigation history, IP portfolios, and operational data. A standalone NDA typically includes specific provisions for data room access, permitted disclosures to advisors, and post-termination data destruction obligations that wouldn’t fit in a confidentiality clause.

    No existing contract. Two companies exploring a potential vendor relationship need to share technical requirements and pricing models. No purchase agreement or MSA exists yet. A standalone NDA fills the gap.

    Employee onboarding (combined with invention assignment). Many companies use a CIIA — Confidential Information and Inventions Assignment Agreement — which functions as a standalone NDA combined with IP assignment provisions. This is a better approach than embedding confidentiality in the employment agreement alone, because the CIIA can survive employment termination with its own specific terms.

    Detailed terms required. When you need comprehensive definitions, specific exclusion carve-outs, detailed remedies (including injunctive relief), and specific return/destruction procedures, a standalone NDA provides the space and structure to address each element properly.

    When a Confidentiality Clause Is Sufficient

    A confidentiality clause works within an existing agreement that already governs the relationship. Common situations:

    MSAs and vendor agreements. The MSA already includes provisions for term, termination, remedies, governing law, and dispute resolution. A confidentiality clause leverages these existing provisions rather than creating a parallel framework. As noted in Bloomberg Law’s analysis of confidentiality agreements, the choice between standalone and embedded protections often depends on the complexity of the broader relationship.

    Employment agreements. Confidentiality is one of several employment terms alongside compensation, duties, termination, and benefits. A well-drafted confidentiality section within the employment agreement covers the basics. But note: many practitioners recommend a standalone CIIA in addition to (or instead of) the employment agreement’s confidentiality section, because it survives on its own terms.

    Standard commercial transactions. When confidentiality is not the primary concern of the agreement — it’s just one of many provisions — a clause is more proportionate and practical.

    Short-term engagements. For a 30-day consulting project with limited information sharing, a standalone NDA may be overkill. A confidentiality clause within the consulting agreement handles it efficiently.

    The test: if the broader agreement’s termination, remedies, and survival provisions adequately cover confidentiality, a clause is sufficient. If you need confidentiality protections that differ from or extend beyond the host agreement’s framework, use a standalone NDA.

    When You Need Both

    The answer is often “both, in sequence.” Here’s the typical pattern:

    1. Pre-deal NDA governs disclosures during negotiations, due diligence, and deal evaluation
    2. MSA with confidentiality clause replaces or supplements the NDA once the deal closes

    The critical issue: what happens to the NDA when the MSA takes effect? If you don’t address this explicitly, you create ambiguity about which document controls. The MSA’s integration clause (“this agreement constitutes the entire agreement between the parties”) may inadvertently terminate the NDA — including protections that applied to pre-signing disclosures.

    Best practice: address the transition explicitly. Include language in the MSA such as:

    “The Mutual Non-Disclosure Agreement dated [date] between the parties shall survive execution of this Agreement with respect to Confidential Information disclosed prior to the Effective Date. For Confidential Information disclosed on or after the Effective Date, Section [X] of this Agreement shall govern.”

    Without this, you’ll have a dispute about which protections apply to which disclosures — and your client’s pre-deal disclosures may end up with less protection than intended.

    Key Drafting Differences

    The structural differences between NDAs and confidentiality clauses aren’t just about length. They reflect different levels of detail, different default assumptions, and different enforcement mechanisms.

    Element Standalone NDA Confidentiality Clause
    Length 2-5 pages 1-3 paragraphs
    Definition of “Confidential Information” Detailed, often 1-2 pages with categories, markings requirements, and oral disclosure protocols Abbreviated — often a single sentence or brief paragraph
    Standard exclusions All 5 standard exclusions typically listed (publicly available, independently developed, previously known, received from third party, required by law) Sometimes truncated to 2-3 exclusions
    Duration Specified independently (typically 2-5 years, sometimes indefinite for trade secrets) Often tied to the host agreement’s term plus a survival period
    Remedies Detailed — injunctive relief, specific performance, prevailing party attorneys’ fees References the host agreement’s general remedies section
    Return/destruction of materials Detailed procedures, certification requirements, timeline Often absent or addressed in 1 sentence
    Non-solicitation Sometimes included as a companion provision Rarely included within a confidentiality clause
    Survival Explicit survival terms independent of any other agreement May or may not survive host agreement termination — check carefully

    The practical takeaway: a confidentiality clause that omits standard exclusions, lacks an independent survival period, or doesn’t address remedies is significantly weaker than a standalone NDA. If you’re drafting a clause, make sure it covers at least the exclusions, duration, and survival — don’t assume the host agreement fills those gaps automatically.

    The 5 Mistakes That Create Exposure

    Mistake 1: Using only a confidentiality clause when a standalone NDA is needed. If you’re sharing sensitive information before any agreement exists, a clause inside a not-yet-signed contract provides zero protection. The NDA must be signed first.

    Mistake 2: Having both an NDA and a confidentiality clause that conflict. The NDA says confidential information means “all information disclosed in writing.” The MSA clause says “all information, whether oral or written.” Which controls? If the MSA’s integration clause supersedes the NDA, the more restrictive definition may apply to pre-deal disclosures — shrinking your protection.

    Mistake 3: Forgetting to address supersession. The most common mistake. The ABA’s Model Rules on competence (Rule 1.1) require lawyers to apply thorough and adequate preparation to every representation. Failing to address the NDA-to-agreement transition is a preparation gap.

    Mistake 4: Confidentiality clause that’s too short. A single sentence — “Both parties agree to keep the other’s information confidential” — is technically enforceable but practically useless. No definition, no exclusions, no duration, no remedies. If challenged, you’ll spend more litigating what the clause means than the information was worth.

    Mistake 5: NDA that’s too broad. An NDA that defines confidential information as “all information of any kind” with no exclusions is likely unenforceable in many jurisdictions. Courts have struck down overly broad NDAs as unreasonable restraints. Specificity matters.

    For a deeper look at NDA-specific pitfalls, see our analysis of common NDA mistakes across 1,000 agreements.

    How Duration and Survival Differ

    Duration is where standalone NDAs and confidentiality clauses diverge most significantly in practice.

    Standalone NDA duration is typically set independently: 2-3 years for general business information, 5 years for technology or financial data, and indefinite for trade secrets. The duration runs from the date of disclosure, not the date of the agreement.

    Confidentiality clause duration is usually tied to the host agreement: “during the term of this Agreement and for [X] years thereafter.” This creates a problem: if the MSA runs for 3 years and the confidentiality survival is 2 years, information disclosed in Year 1 is only protected for 4 more years after disclosure. Information disclosed in Year 3 gets the full 2-year survival. The protection is inconsistent.

    Best practice for clauses: Specify that the confidentiality obligation survives for a fixed period from the date of each disclosure, not from termination of the host agreement. This provides consistent protection regardless of when the information was shared.

    How Clause Labs Reviews Both

    Whether you’re reviewing a standalone NDA or a contract with an embedded confidentiality clause, Clause Labs’s AI analysis identifies the key provisions and flags gaps:

    • Detects whether confidentiality protections exist (standalone, embedded, or both)
    • Flags missing standard exclusions in either format
    • Identifies when duration is too short or absent
    • Checks for adequate remedies provisions
    • Detects potential conflicts between an existing NDA and a new agreement’s confidentiality terms
    • Flags missing return/destruction obligations

    For lawyers who review NDAs regularly, our guide to reviewing NDAs in 10 minutes provides a structured workflow that pairs well with AI-assisted review.

    Frequently Asked Questions

    Can a confidentiality clause fully replace an NDA?

    Yes — but only if the clause is comprehensive enough and the host agreement is already signed before any confidential information changes hands. If information is being shared before the agreement is executed, you need a standalone NDA for the interim period. A well-drafted confidentiality clause within a signed MSA can provide equivalent protection to a standalone NDA, but most clauses in practice are far less detailed and therefore provide weaker protection.

    Should I sign an NDA before every business meeting?

    No. NDAs should be reserved for situations involving genuinely sensitive information: proprietary technology, financial data, customer lists, strategic plans, or trade secrets. Routine business discussions about potential partnerships, general pricing conversations, or publicly available information don’t warrant NDAs. Over-using NDAs creates “NDA fatigue” — where parties start treating them as formalities and stop reading them carefully. That’s worse than having no NDA at all.

    What happens if my NDA and my MSA have different confidentiality terms?

    The MSA’s integration clause will likely control, meaning the NDA may be superseded entirely — including its protections for pre-signing disclosures. This is why addressing the transition explicitly is critical. Without a carve-out preserving the NDA for pre-deal disclosures, you may lose protections you assumed were still in place.

    Is a verbal NDA enforceable?

    In theory, oral agreements can be binding under general contract law principles. In practice, a verbal NDA is nearly impossible to enforce because you can’t prove what information was designated as confidential, what obligations were agreed to, or what the duration was. Always use a written agreement. The Statute of Frauds may not specifically require NDAs to be in writing in most states, but proving the terms of an oral NDA in litigation is prohibitively difficult.

    How long should confidentiality obligations last?

    It depends on the type of information. General business information: 2-3 years. Technology specifications, financial data, or strategic plans: 3-5 years. Trade secrets: indefinite (as long as the information qualifies as a trade secret under applicable state law, such as the Uniform Trade Secrets Act). The key is matching the duration to the shelf life of the information’s competitive value. A 1-year NDA protecting a 5-year product roadmap is inadequate.

    This article is for informational purposes only and does not constitute legal advice. Consult a qualified attorney for advice specific to your situation.

    Wondering whether your NDA or confidentiality clause has gaps? Upload any agreement to Clause Labs’s free analyzer — no signup required — and get an instant risk analysis identifying missing exclusions, weak duration terms, and remedies gaps. Solo practitioners reviewing 25+ agreements monthly can upgrade to the Solo plan at $49/month for full redline suggestions and DOCX export with tracked changes.

  • Auto-Renewal Clauses: How to Protect Your Clients from Silent Lock-Ins

    Auto-Renewal Clauses: How to Protect Your Clients from Silent Lock-Ins

    Auto-Renewal Clauses: How to Protect Your Clients from Silent Lock-Ins

    Your client signed a three-year software contract with a 90-day notice window for non-renewal. Nobody calendared the deadline. The contract auto-renewed for another three years at a 12% price increase. Total cost of missing that window: $216,000 in unwanted fees for software the client stopped using eight months ago.

    This happens constantly. According to a Kaplan Group analysis, an estimated 99% of B2B auto-renewal clauses are not written in compliance with current state and federal regulations — which means both sides of the table are exposed. Auto-renewal clauses are designed to exploit a predictable human behavior: we forget. The vendor counts on it. Your job as the reviewing lawyer is to make sure the clause is fair, the deadline is calendared, and your client has a real exit option.

    This article breaks down the mechanics, the red flags, the rapidly expanding state regulatory landscape, and six specific negotiation strategies you can use in your next contract. If you want to check whether a contract’s auto-renewal provisions create a trap, upload it to Clause Labs’s free analyzer — it flags long notice periods, one-sided renewal terms, and buried price escalation in under 60 seconds.

    How Auto-Renewal Clauses Work

    The mechanics are straightforward. An auto-renewal clause provides that the contract automatically extends for successive periods — usually one year — unless one or both parties provide written notice of non-renewal within a specified window before the current term expires.

    The three moving parts:

    The notice window. The period during which you must send your non-renewal notice. Typically 30-90 days before the renewal date. Miss this window by even one day and the contract auto-renews.

    The renewal term. How long the contract renews for. This can match the initial term (a three-year contract renewing for another three years) or default to a shorter period (a three-year contract renewing for successive one-year terms). The difference is enormous.

    The renewal terms. Does the contract renew on the same terms, or can one party change pricing, SLAs, or other conditions upon renewal? A clause that says “renews at Vendor’s then-current rates” is an open-ended price escalation mechanism.

    Here is what a typical auto-renewal looks like in practice:

    “This Agreement shall automatically renew for successive one (1) year terms unless either party provides written notice of non-renewal at least sixty (60) days prior to the expiration of the then-current term.”

    Looks reasonable. But consider: if your client’s three-year initial term expires on March 31, the non-renewal notice must be sent by January 30. If the lawyer reviewing the contract in April of year one doesn’t calendar that date, no one will remember it 33 months later.

    Auto-Renewal Red Flags

    Flag these immediately during any contract review:

    Notice Period Over 60 Days

    A 90-day notice window means your client must decide whether to renew three full months before the renewal date. For a complex vendor relationship, the client may not have the data to make that decision 90 days out — they’re still evaluating the current year’s performance.

    Some contracts push this to 120 or even 180 days. A six-month notice window on a one-year contract means the client effectively has six months to evaluate before they must decide. That’s barely half the contract term.

    Notice Sent to a Specific Person or Address

    If the clause requires notice to “the attention of [Name], Director of Contract Administration, at [specific address],” your client now has an additional trap: the notice must reach the right person at the right place. If that person has left the company or the address has changed, the notice may be argued as defective.

    Renewal Term Equals Initial Term

    A three-year initial term that auto-renews for another three years creates a six-year commitment from a single missed deadline. Market-standard practice for multi-year contracts is to auto-renew for successive one-year terms, not for the full initial term length.

    Price Increases Without a Cap

    “Services shall renew at Vendor’s then-current pricing” gives the vendor unlimited discretion to raise prices at renewal. Without a cap (e.g., “not to exceed 5% per annum” or “not to exceed CPI increase”), your client’s costs could spike dramatically on renewal.

    No Termination for Convenience During Renewal Term

    If the contract includes termination for convenience during the initial term but removes that right during renewal terms, your client is more locked in after renewal than before.

    Auto-Renewal Buried in Dense Text

    Auto-renewal language should appear in a clearly labeled section — “Term and Renewal” or equivalent. When auto-renewal language is buried in the middle of a paragraph in a miscellaneous section, the drafter may be counting on nobody reading it. Our guide on reviewing contracts for red flags covers this pattern and 24 others.

    No Notification Before Renewal

    The most client-hostile version: the contract auto-renews silently with no obligation for the vendor to remind the client that the renewal date is approaching. Several states now require affirmative notification before auto-renewal takes effect.

    State Auto-Renewal Laws: A Rapidly Expanding Landscape

    Auto-renewal regulation has accelerated significantly in the past three years. What started as consumer protection legislation is increasingly extending to B2B contracts.

    California

    California’s Automatic Renewal Law (CARL), codified in Business and Professions Code §§ 17600-17606, was strengthened by amendments that took effect July 1, 2025. Key requirements:

    • Clear and conspicuous disclosure of auto-renewal terms before the consumer agrees
    • Affirmative consent to the auto-renewal terms (not just the overall agreement)
    • Easy cancellation in the same medium used to enroll
    • Records of consent maintained for at least three years

    CARL applies primarily to B2C relationships, but according to analysis by Upcounsel, the law can affect B2B agreements when one side is deemed a small business or “consumer-like” entity.

    New York

    New York General Obligations Law § 5-903 applies directly to auto-renewal provisions in B2B service contracts. It requires that the auto-renewal provision be “clear and conspicuous” and that the service provider give notice of the renewal terms between 15 and 30 days before the renewal date. Non-compliant auto-renewals are unenforceable.

    Virginia

    Virginia amended its consumer protection law effective July 1, 2024, creating requirements for both B2C and B2B auto-renewal contracts. Notably, Virginia treats “small businesses” as consumers under the auto-renewal statute, extending B2C protections to qualifying B2B relationships. Virginia also allows a private right of action for violations.

    Illinois

    Illinois’s enhanced auto-renewal law, effective January 1, 2022, requires cancellation instructions in renewal notices and an online cancellation option for consumers who subscribed online. However, Illinois explicitly excludes B2B contracts from its auto-renewal regulations.

    Federal (FTC)

    The FTC’s “Click-to-Cancel” amendments to the Negative Option Rule were initially set to take effect in May 2025 but were delayed to July 14, 2025. The Eighth Circuit subsequently vacated the rule in July 2025. However, the FTC retains enforcement authority under ROSCA (Restore Online Shoppers’ Confidence Act) and the FTC Act, and restarted rulemaking in January 2026. The key takeaway for practitioners: even without the specific rule, aggressive enforcement of auto-renewal practices continues.

    Summary Table

    State Applies to B2B? Pre-Renewal Notice Required? Key Requirement
    California Limited (consumer-like entities) Yes Affirmative consent, easy cancellation
    New York Yes Yes (15-30 days before renewal) Clear and conspicuous disclosure
    Virginia Yes (small businesses) Yes Private right of action
    Illinois No (B2B excluded) Yes (B2C only) Online cancellation option
    Federal (FTC) Rule vacated; enforcement continues Per ROSCA standards ANPRM pending (2026)

    For a comprehensive breakdown by state, see Faegre Drinker’s auto-renewal state law charts.

    6 Strategies to Negotiate Auto-Renewal Provisions

    Strategy 1: Remove Auto-Renewal Entirely

    Replace auto-renewal with affirmative renewal — the contract expires at the end of the term unless both parties agree in writing to extend. This eliminates the missed-deadline risk entirely.

    When it works: When your client has leverage (they’re the customer, they have alternatives), or when the contract value is high enough that both sides should consciously decide to continue.

    Sample language:

    This Agreement shall expire at the end of the Initial Term. The parties may
extend this Agreement for successive one (1) year Renewal Terms by mutual
written agreement executed at least thirty (30) days prior to the expiration
of the then-current term.

    Strategy 2: Reduce the Notice Period

    If auto-renewal stays, shorten the notice period. Push 90-day windows down to 30 days. Push 60-day windows to 30.

    Market justification: A 30-day notice period is sufficient for most commercial contracts and is the standard in many SaaS agreements. Anything over 60 days benefits only the party who drafted the clause.

    Strategy 3: Shorten the Renewal Term

    If the initial term is three years, negotiate for one-year renewal terms. This limits the exposure from a missed deadline to one additional year rather than three.

    This Agreement shall automatically renew for successive one (1) year terms
(each a "Renewal Term") unless either party provides written notice of
non-renewal at least thirty (30) days prior to the end of the then-current term.

    Strategy 4: Cap Price Increases

    Add a ceiling on any price increase at renewal.

    Upon each Renewal Term, Vendor may increase the fees by no more than the
greater of (i) 3% or (ii) the percentage increase in the Consumer Price Index
(CPI-U) for the twelve-month period ending on the date sixty (60) days prior
to the renewal date.

    Without this cap, a renewal clause is a blank check for the vendor.

    Strategy 5: Require Vendor Notification Before Renewal

    Add a mandatory reminder obligation:

    Vendor shall provide Customer with written notice at least forty-five (45) days
prior to the renewal date, identifying the upcoming renewal date, the applicable
renewal term, and any changes to fees or terms. Failure to provide such notice
shall extend the non-renewal notice period by thirty (30) days from the date
Vendor provides the required notice.

    This shifts the calendar-management burden to the party that benefits from the auto-renewal.

    Strategy 6: Add Termination for Convenience During Renewal Terms

    If the contract includes auto-renewal, include a termination for convenience right during renewal terms with a reasonable notice period (30-60 days). This functions as a safety valve — even if the client misses the non-renewal window, they can still exit during the renewal term.

    Auto-Renewal Calendar Management

    Even the best-drafted auto-renewal clause is useless if nobody tracks the dates. Practical advice for lawyers managing client contracts:

    Create a centralized renewal calendar. Use your practice management system (Clio, MyCase, PracticePanther), a shared Google Calendar, or a dedicated contract management tool. The specific tool matters less than consistency. For a broader framework on building contract review into your workflow, see our guide on how to set up AI contract review.

    Set three reminders per contract:
    – 90 days before renewal: Initial alert — begin client discussion about whether to renew
    – 60 days before renewal: Decision deadline — get client’s written direction
    – 30 days before renewal: Final notice deadline — send non-renewal notice if client has decided to exit

    Designate a responsible person. For each contract, someone specific — not “the firm” or “the team” — owns the renewal date. If that person leaves, the responsibility must transfer explicitly.

    Annual contract audit. Once per year, review all active contracts with auto-renewal provisions. Verify that every renewal date is calendared and every contract is still meeting client needs. This audit prevents the “we forgot about that contract” scenario.

    Clause Labs’s Team tier ($299/month) includes obligation tracking with due date reminders and daily digests — purpose-built for tracking renewal dates, notice periods, and other critical contract deadlines across your entire portfolio.

    How Clause Labs Flags Auto-Renewal Traps

    Clause Labs’s AI identifies auto-renewal provisions automatically during contract review and flags:

    • Notice periods over 60 days
    • Renewal terms that match or exceed the initial term length
    • One-sided auto-renewal (only one party can prevent renewal)
    • Price escalation language without caps
    • Missing vendor notification obligations
    • Interaction between auto-renewal and termination provisions
    • Auto-renewal language buried in non-obvious sections

    The analysis highlights the exact notice deadline language so you know precisely what dates to calendar.

    Frequently Asked Questions

    Can I get out of an auto-renewed contract?

    It depends on the contract terms and applicable state law. If the auto-renewal provision complies with all applicable legal requirements and you missed the notice window, you’re generally bound for the renewal term — unless the contract includes a termination for convenience provision that allows mid-term exit, the auto-renewal clause violates a state auto-renewal statute (making it unenforceable), or you can show the clause was unconscionable. Prevention is far easier than cure: calendar the dates and don’t miss the window.

    Are auto-renewal clauses enforceable?

    Yes, in most jurisdictions, provided they comply with applicable disclosure and notice requirements. States with auto-renewal laws (California, New York, Virginia, and others) impose specific requirements — failure to comply can render the auto-renewal unenforceable. For B2B contracts in states without specific auto-renewal statutes, courts generally enforce auto-renewal provisions as written. The trend, however, is toward greater regulation, as noted in the National Law Review’s analysis of automatic renewal law updates.

    Do auto-renewal laws apply to B2B contracts?

    Increasingly, yes — though coverage varies significantly by state. New York’s auto-renewal statute (GBL § 5-903) explicitly covers B2B service contracts. Virginia extends consumer protections to small businesses. California’s CARL focuses on B2C but can apply to consumer-like business relationships. Illinois excludes B2B entirely. At the federal level, the FTC’s enforcement actions under ROSCA and the FTC Act can reach B2B practices. Check the specific laws in your jurisdiction.

    What’s a reasonable auto-renewal notice period?

    For most commercial contracts, 30 days is sufficient and reasonable. 60 days is common in enterprise agreements and generally acceptable. Anything over 90 days disproportionately benefits the party that drafted the clause. The notice period should reflect the realistic time needed to evaluate the relationship and make a renewal decision — not the drafter’s desire to create a narrow exit window.

    Should I always negotiate out auto-renewal?

    Not necessarily. Auto-renewal provides convenience for both parties in ongoing relationships — neither side has to remember to affirmatively extend. The goal isn’t to eliminate auto-renewal but to make it fair: reasonable notice periods, capped price increases, vendor notification obligations, and termination for convenience as a safety valve. A well-negotiated auto-renewal clause with a 30-day notice period and annual renewal terms is better than a fixed term with no renewal option at all.

    This article is for informational purposes only and does not constitute legal advice. Consult a qualified attorney for advice specific to your situation.

    Auto-renewal traps are among the most common — and most preventable — contract risks. If you’re reviewing a SaaS agreement, vendor contract, or MSA with auto-renewal provisions, upload it to Clause Labs and check whether the renewal terms are fair before your client signs. Free tier: 3 reviews/month, no credit card required.

  • IP Assignment Clauses: The Clause That Destroys Startups (and How to Fix It)

    IP Assignment Clauses: The Clause That Destroys Startups (and How to Fix It)

    IP Assignment Clauses: The Clause That Destroys Startups (and How to Fix It)

    A Series A round dies in due diligence because the lead developer — a contractor who built the MVP — never assigned the IP to the company. The investor’s counsel finds no CIIA, no IP assignment clause, and no work-for-hire agreement. The contractor left eight months ago. Now the company’s entire codebase belongs, legally, to someone who isn’t answering emails.

    This isn’t a hypothetical. According to Jones Day’s analysis of IP due diligence in venture capital, IP chain-of-title failures are among the most common diligence killers in early-stage financings and acquisitions. With 85% of VC-backed exits occurring through acquisitions — where the buyer is literally paying for the company’s IP — a missing assignment clause doesn’t just create legal risk. It destroys the entire value proposition.

    If you advise startups, review contractor agreements, or handle employment contracts, this article covers the five IP assignment mistakes that cause the most damage and how to prevent each one. Upload any contractor or employment agreement to Clause Labs to check whether the IP provisions actually protect the company — the free analyzer flags missing assignments, overly broad language, and absent prior inventions carve-outs in under 60 seconds.

    What Is an IP Assignment Clause?

    An IP assignment clause is a contractual provision that transfers ownership of intellectual property from the creator (employee, contractor, co-founder) to the company. Without one, the default rules of copyright, patent, and trade secret law determine ownership — and those defaults rarely favor the company.

    The key concepts:

    Assignment vs. license. An assignment permanently transfers ownership. A license grants permission to use. If your client needs to own the IP outright — and in most startup contexts, they do — a license isn’t sufficient. Investors and acquirers want clean title, not a license that could be revoked.

    Types of IP covered. A comprehensive assignment covers patents, copyrights, trade secrets, trademarks, and moral rights (relevant in Canada and the EU). Narrow assignments that cover only “inventions” may miss copyrightable code, designs, or written content.

    Work-for-hire vs. assignment. Under 17 U.S.C. § 101, a “work made for hire” is automatically owned by the employer. But the work-for-hire doctrine only applies to employees creating within the scope of employment, or to independent contractors creating works in nine specific statutory categories (and only with a written agreement). For most contractor-created work, work-for-hire doesn’t apply — explicit assignment is required.

    The 5 IP Assignment Mistakes That Destroy Startups

    Mistake 1: No IP Assignment from Founders

    The problem. Two founders build a product for six months before incorporating. They form the company, issue stock, hire employees, and raise a seed round. But neither founder ever assigned the IP they created — the code, the algorithms, the designs, the brand — to the company.

    The legal reality. Each founder personally owns their contributions. The company has, at best, an implied license to use the IP. If one founder leaves, they can argue they own “their” portion of the codebase. If the company is acquired, the buyer’s counsel will find the gap in due diligence.

    The fix. Every founder should sign a Confidential Information and Inventions Assignment Agreement (CIIA) at incorporation — or ideally, before. According to Cooley GO’s guidance on CIIAs, the CIIA should assign all IP created for the company, include a prior inventions schedule, and cover confidentiality obligations. This is standard Silicon Valley practice, and investors expect it.

    What the CIIA should include:
    – Assignment of all IP created for or related to the company’s business
    – Prior inventions schedule (Exhibit A) listing excluded pre-existing IP
    – Confidentiality obligations
    – Cooperation clause (founder will sign additional documents to perfect assignment)
    – Representations that the founder has the right to assign

    Mistake 2: Contractor Work Without IP Assignment

    The problem. A startup hires a freelance developer to build the MVP. The contractor agreement covers scope, timeline, and payment — but says nothing about who owns the resulting code. Six months later, the contractor is building a competing product using “their” code.

    The legal reality. Unlike employees, contractors own what they create by default. As California’s IP assignment framework makes clear, the statutory protections for employee inventions (Labor Code § 2870) don’t extend to independent contractors. There’s no statutory scheme governing contractor IP assignment — the parties must contractually address it. If the contract doesn’t include an explicit IP assignment, the contractor retains all rights.

    Work-for-hire won’t save you in most cases. The work-for-hire doctrine under copyright law only applies to independent contractors in nine specific categories — including contributions to collective works, parts of a motion picture, and compilations — and requires a written agreement. Custom software development generally doesn’t qualify.

    The fix. Every contractor agreement must include:
    – Explicit IP assignment (not just work-for-hire language)
    – Scope definition covering all deliverables and work product
    – Representations that the contractor has the right to assign and hasn’t used third-party IP without authorization
    – A cooperation clause for perfecting the assignment

    Mistake 3: Overly Broad IP Assignment in Employment Agreements

    The problem. An employment agreement states: “Employee assigns to Company all inventions, works of authorship, and intellectual property created during the term of employment.” The employee’s weekend side project — an app completely unrelated to the employer’s business, built on the employee’s personal laptop, on personal time — is now arguably company property.

    The legal reality. Overbroad assignment clauses create three risks. First, they may be unenforceable in states with employee invention protection statutes. California Labor Code § 2870 explicitly protects inventions developed entirely on personal time without employer resources, provided they don’t relate to the employer’s business. Similar statutes exist in Delaware, Illinois, Minnesota, North Carolina, Washington, and several other states. Second, overbroad clauses generate employee resentment and departures. Third, if the employee’s personal invention has third-party encumbrances (like an open-source license), those encumbrances now affect the company.

    The fix. Narrow the assignment to IP that is:
    – Created within the scope of employment, OR
    – Created using company resources, equipment, or information, OR
    – Related to the company’s current or reasonably anticipated business

    And explicitly exclude inventions covered by California Labor Code § 2870 or equivalent state protections. The agreement should include a written notice that the assignment doesn’t cover protected personal inventions.

    Mistake 4: No Prior Inventions Carve-Out

    The problem. A senior engineer joins a startup and signs a standard IP assignment. The engineer previously developed a machine learning framework on their own time — a framework they now use (with modifications) in their work for the startup. Without a prior inventions carve-out, that framework is now arguably assigned to the company.

    The legal reality. If the prior invention has encumbrances — an existing license to another company, open-source obligations, or a co-ownership arrangement — those encumbrances now affect the startup’s IP portfolio. During due diligence, an acquirer or investor will discover the clouded title and demand indemnification, escrow, or a price reduction.

    The fix. Every CIIA and employment agreement should include a prior inventions schedule — typically Exhibit A — where the employee or contractor lists all pre-existing IP that is excluded from the assignment. The schedule should include:
    – Description of the prior invention
    – Date of creation
    – Any existing licenses or encumbrances
    – Whether the employee intends to use it in company work (and if so, a separate license grant)

    If the employee states “none” on the prior inventions schedule, that’s a representation the company can rely on.

    Mistake 5: Missing License-Back After Assignment

    The problem. A contractor builds a web application using their proprietary framework — a toolkit they’ve developed over years and use across multiple client projects. The contractor agreement assigns “all IP created in connection with the Services” to the client. Technically, the contractor can no longer use their own general-purpose framework for other clients.

    The legal reality. This creates an unenforceable or unworkable provision. No contractor will actually stop using their own development tools. But if the assignment is drafted broadly enough, the client could theoretically enforce it — or at minimum, it creates a dispute.

    The fix. Include a license-back clause:

    Contractor assigns to Company all right, title, and interest in Deliverable IP
(defined as intellectual property created specifically for Company under this
Agreement). Company grants Contractor a non-exclusive, perpetual, royalty-free
license to use, modify, and distribute Background IP (defined as pre-existing
tools, frameworks, and methodologies owned by Contractor prior to or independent
of this engagement) for any purpose, including for other clients.

    This structure gives the company clean ownership of the custom work while letting the contractor continue using their general-purpose tools.

    If you’re reviewing a contractor agreement right now, Clause Labs’s Solo tier ($49/month for 25 reviews) catches all five of these IP assignment mistakes — including missing prior inventions carve-outs and work-for-hire misapplication — across every contract type.

    IP Assignment Clause Elements: The Complete Checklist

    A well-drafted IP assignment clause should address each of these elements:

    Scope of assignment. What specific IP is being assigned? “All intellectual property” is common but can be overbroad. Better: “All Deliverable IP, including inventions, works of authorship, designs, and trade secrets created in the performance of Services under this Agreement.”

    Timing of assignment. When does the assignment occur? Options include upon creation (strongest for the company), upon delivery, or upon final payment. Assignment upon creation is the standard approach in CIIAs and employment agreements.

    Territory. Worldwide assignment is standard and necessary for companies operating across jurisdictions.

    Consideration. What does the assignor receive in exchange? For employees, it’s bundled into compensation. For contractors, it’s typically bundled into the service fees. Make sure the consideration is clearly stated — assignment without consideration can be challenged.

    Moral rights waiver. Required in jurisdictions that recognize moral rights (Canada, EU member states, Australia). In the US, moral rights are limited to visual art under VARA (17 U.S.C. § 106A), but international assignments should include a waiver.

    Cooperation clause. The assignor agrees to execute additional documents (patent applications, copyright registrations) necessary to perfect the assignment. Include a power of attorney as a backstop.

    Representations. The assignor represents they have the right to assign, haven’t previously assigned the IP to anyone else, and haven’t incorporated third-party IP without authorization.

    Work-for-hire declaration. For copyrightable works that fall within the nine statutory categories, include a work-for-hire declaration as a belt-and-suspenders approach alongside the assignment.

    IP Assignment by Agreement Type

    Founder and Co-Founder Agreements

    All IP created for the company is assigned to the company at incorporation via CIIA. Prior inventions are excluded. The critical question: what happens to assigned IP if a founder is terminated or leaves? Standard approach: the IP stays with the company (it was assigned, not licensed), but unvested stock is forfeited under the vesting schedule.

    Employment Agreements

    The assignment covers inventions and works created during employment, using company resources, or related to the company’s business. State-specific notice requirements apply — California, Delaware (19 Del. C. § 805), Illinois (765 ILCS 1060/2), Minnesota (Minn. Stat. § 181.78), and Washington (RCW 49.44.140) all have statutes protecting employee personal inventions. Failure to include the required statutory notice can render the assignment provision unenforceable. For guidance on related employment agreement issues, see our article on how to review contracts for red flags.

    Independent Contractor Agreements

    No automatic assignment exists. The contract must explicitly assign IP, and the work-for-hire doctrine has narrow applicability for contractors. Every contractor agreement should include: explicit IP assignment, background IP definition and license, prior inventions schedule, cooperation clause, and representations about third-party IP. For a more comprehensive review framework, see our guide on reviewing contractor agreements for misclassification risk.

    Development and Software Contracts

    The standard structure separates deliverable IP (assigned to the client) from background IP (retained by the developer with a license to the client to use it within the deliverables). Open-source components require special attention — if the developer incorporates GPL-licensed code, the copyleft obligations may affect the client’s proprietary code. The contract should require disclosure of all open-source components and compliance with their respective licenses. For SaaS-specific IP considerations, see our analysis of SaaS agreement review issues.

    IP Assignment Red Flags

    When reviewing any contract, flag these immediately:

    No IP assignment clause in a development contract. The contractor owns everything by default. This is the single most common and most expensive IP mistake in startup law.

    “All IP ever created” scope. Assignments covering all intellectual property created by the assignor, regardless of context, are overbroad and potentially unenforceable under state invention protection statutes.

    No prior inventions schedule. Without a carve-out, pre-existing IP with encumbrances gets swept into the assignment, creating title problems.

    Assignment conditioned on payment. If IP assignment only occurs upon full payment, a payment dispute means the company doesn’t own its own product. Standard practice: assignment upon creation, with a security interest or license-back if payment protection is needed.

    No cooperation clause. Without one, perfecting the assignment (filing patent applications, registering copyrights) requires the assignor’s voluntary cooperation — which may not be forthcoming after the relationship ends.

    Work-for-hire misapplication. Using work-for-hire language for contractor work that doesn’t fall within the nine statutory categories creates a false sense of security. The company thinks it owns the IP. It doesn’t. According to Farella Braun + Martel’s analysis, misapplying work-for-hire in contractor agreements can also create employment classification risk — if the IRS or a court determines that calling the relationship “work-for-hire” implies an employment relationship rather than an independent contractor arrangement.

    No representations about right to assign. The assignor may not own what they’re assigning — they may have used code from a previous employer, incorporated open-source components with restrictive licenses, or already assigned rights to someone else. IP assignment issues often interact with limitation of liability provisions — if the assignor breaches a representation about IP ownership, the damages may exceed the contract’s liability cap.

    How Clause Labs Handles IP Provisions

    Clause Labs’s AI identifies IP assignment, license, and work-for-hire clauses in any contract and flags:

    • Missing IP assignment in contractor and development agreements
    • Overly broad assignment language that may conflict with state employee invention protections
    • Absent prior inventions carve-outs
    • Missing cooperation clauses
    • Interactions between IP provisions and termination clauses (does IP assignment survive termination?)
    • Work-for-hire declarations used outside their statutory scope

    The analysis takes under 60 seconds and provides a clause-by-clause breakdown with risk ratings and suggested edits.

    Frequently Asked Questions

    Who owns IP by default without a contract?

    It depends on the relationship. For employees creating within the scope of employment, the employer generally owns copyrightable works under the work-for-hire doctrine, and many states have “hired to invent” doctrines for patentable inventions. For independent contractors, the contractor owns everything they create unless a written agreement says otherwise. For co-founders without a CIIA, each founder personally owns their individual contributions. These defaults are why written IP assignment agreements are essential.

    Can I assign IP verbally?

    Patent rights can potentially be assigned verbally, but copyright assignments require a written instrument signed by the owner under 17 U.S.C. § 204. In practice, verbal IP assignments are virtually impossible to enforce because they’re impossible to prove. Always get IP assignments in writing.

    What’s the difference between IP assignment and work-for-hire?

    Work-for-hire means the hiring party is considered the author and original owner — the creator never owned the IP at all. Assignment means the creator owned the IP and then transferred it to the company. The practical difference: assignment can theoretically be terminated by the author after 35 years under 17 U.S.C. § 203, while work-for-hire cannot. For most startup purposes, both achieve the same practical result — company ownership — but using both approaches (work-for-hire declaration plus assignment as backup) provides the strongest protection.

    Do I need IP assignment for every contractor?

    Yes, if the contractor is creating anything that could constitute intellectual property — code, designs, written content, inventions, processes. The only exception is contractors performing purely mechanical tasks with no creative component (e.g., data entry using your templates). When in doubt, include the clause. The cost of including an unnecessary IP assignment clause is zero. The cost of omitting a necessary one can be the entire company.

    What happens if an IP assignment is invalid?

    The company doesn’t own the IP it thought it owned. In an acquisition, this can reduce the purchase price, require escrow holdbacks, or kill the deal entirely. In a financing, investors may demand that IP issues be resolved before closing. In operations, the actual IP owner could demand license fees, seek an injunction, or start competing using “your” technology. The fix is to obtain a valid assignment as soon as possible — but if the assignor is uncooperative, it may require litigation.

    This article is for informational purposes only and does not constitute legal advice. Consult a qualified attorney for advice specific to your situation.

    IP assignment issues are among the most expensive mistakes in startup law. If you’re reviewing a contractor agreement, employment contract, or founder CIIA, upload it to Clause Labs to check whether the IP provisions actually protect the company. The free tier includes 3 reviews per month — no credit card required.

  • Termination for Convenience Clauses: Why They’re Dangerous and How to Limit Them

    Termination for Convenience Clauses: Why They’re Dangerous and How to Limit Them

    Termination for Convenience Clauses: Why They’re Dangerous and How to Limit Them

    Your client just signed a three-year MSA worth $1.2 million. Six months in, the other side sends a one-paragraph notice: they’re terminating for convenience, effective in 30 days. No breach. No explanation. No compensation for the $180,000 your client invested in onboarding, infrastructure, and staffing up to deliver. The termination for convenience clause on page 19 gave them that right, and your client’s lawyer — who copy-pasted the termination section from the last deal — never flagged it.

    Termination for convenience is one of the most powerful rights in any commercial contract. According to World Commerce & Contracting, poor contract management erodes an average of 9% of annual revenue, and poorly drafted termination provisions are among the top five contract terms that drive disputes and value leakage. Yet most lawyers negotiate the indemnification clause for hours and barely glance at the termination section.

    This article covers the seven specific issues you should negotiate in every termination for convenience clause, the red flags that signal danger, and sample language you can adapt for your next deal. If you want a faster way to catch termination traps, upload any contract to Clause Labs’s free analyzer and get a clause-by-clause risk breakdown in under 60 seconds.

    Termination for Convenience vs. Termination for Cause

    Before negotiating either provision, you need to understand what each one does — because most contracts should include both, and the absence of one creates problems.

    Termination for convenience allows one or both parties to end the contract at any time, for any reason, without the other side committing a breach. The terminating party simply provides notice — typically 30 to 90 days — and the contract winds down. No cure period. No default required. Just a decision.

    Termination for cause requires a material breach. The non-breaching party provides notice identifying the breach, the breaching party gets a cure period (typically 15-30 days), and if the breach isn’t cured, the contract terminates. Cause-based termination often triggers different consequences than convenience-based termination — including indemnification obligations and potentially different payment terms.

    Element For Convenience For Cause
    Trigger Decision — no reason needed Material breach by the other party
    Cure period None Typically 15-30 days
    Notice Required (30-90 days typical) Required (specifying the breach)
    Compensation Varies — often negotiated May include damages for breach
    Fault No fault assigned Fault assigned to breaching party
    Frequency in disputes Common Very common

    The risk of having only termination for cause: if the relationship deteriorates but nobody technically breaches, neither party has a clean exit. The risk of having only termination for convenience: a party can exit a multi-year commitment at will, turning a long-term contract into something closer to a month-to-month arrangement.

    Most well-drafted commercial contracts include both provisions with different consequences for each.

    Where Termination for Convenience Comes From

    Termination for convenience originated in federal government contracting under the Federal Acquisition Regulation (FAR). Under FAR Part 12, the government can terminate virtually any contract for its convenience — a power rooted in the sovereign’s right to change policy priorities. Contractors receive equitable compensation for work performed, but they cannot sue for lost profits on unperformed work.

    This government-contract concept has migrated into commercial contracts over the past two decades, particularly in SaaS agreements, professional services MSAs, and vendor relationships. But there is a critical difference: in government contracting, a detailed regulatory framework governs compensation after termination. In commercial contracts, you get whatever the contract says — nothing more.

    That’s why the negotiation matters so much.

    The 7 Issues to Negotiate in Every Termination for Convenience Clause

    1. Who Has the Right?

    The most fundamental question: is termination for convenience mutual, or does only one party have it?

    Mutual termination means either side can walk away. This is the balanced approach and the starting position for most negotiations.

    One-sided termination gives only one party — usually the buyer, client, or larger company — the right to exit at will. The service provider or vendor is locked in for the full term while the other side can leave whenever it wants.

    If the other side insists on one-sided termination for convenience, the trade-off should be compensation. You’re essentially giving them an option, and options have value. A termination fee, extended notice period, or payment for work in progress offsets the asymmetry.

    2. Notice Period

    How much warning does the terminating party need to provide?

    Market ranges:
    – Short-term contracts (under 1 year): 30 days is standard
    – Multi-year contracts: 60-90 days is common
    – Large-scale engagements with significant staffing: 90-180 days is reasonable

    Red flag: Immediate termination with no notice period. This means the other side can pull the plug tomorrow with zero warning, leaving your client scrambling to reallocate resources and find replacement revenue.

    Negotiation principle: The notice period should reflect the time your client realistically needs to wind down operations, reassign staff, and find alternative arrangements. If your client needs to hire 10 people to perform this contract, a 30-day notice period is inadequate.

    3. Termination Fee (Kill Fee)

    A kill fee compensates the non-terminating party for the early exit. Common structures include:

    • Percentage of remaining value: 25-50% of fees that would have been payable for the remainder of the term
    • Fixed fee: A predetermined amount, often calculated as X months of fees
    • Declining fee: The kill fee decreases over time (e.g., 50% in year one, 25% in year two, 0% in year three)
    • Actual costs plus margin: Reimbursement for actual costs incurred plus a reasonable profit margin

    Kill fees are particularly important in contracts where the service provider makes upfront investments — hiring, equipment purchases, software licenses, facility buildouts — that can’t be easily recouped if the contract ends early.

    4. Wind-Down Obligations

    What happens between the termination notice and the effective date? A well-drafted clause addresses:

    • Transition assistance: Is the terminating party entitled to help migrating to a new provider? For how long? At what cost?
    • Data export and migration: Who handles data transfer? In what format? Within what timeframe?
    • Return of materials and IP: All confidential information, work product, and proprietary materials returned or destroyed
    • Final deliverables: Are partially completed deliverables owed? In what state of completion?

    Without wind-down obligations, the terminating party sends a notice and walks away. The other side is left holding half-finished work product, client data they can’t access, and no transition support.

    5. Payment for Work in Progress

    This is where the real money is. Upon termination for convenience:

    • Completed work: Payment for all work performed through the termination date should be non-negotiable
    • Non-cancellable commitments: If the service provider entered subcontracts or purchased materials that can’t be returned, who bears that cost?
    • Pre-paid amounts: If the terminating party pre-paid for a year of service and terminates at month six, is there a refund?
    • Expenses incurred: Reasonable expenses related to wind-down activities

    According to Holland & Knight’s analysis of convenience terminations, contractors in government and commercial contexts can typically recover direct costs for completed work, settlement expenses, and in some cases a proportional share of profit. But in commercial contracts, that recovery depends entirely on what the termination clause says.

    6. Survival Clauses

    Termination for convenience ends the contract, but it shouldn’t end everything. Certain provisions must survive:

    • Confidentiality: Survives (typically 2-5 years or indefinitely for trade secrets)
    • Indemnification: Survives for claims arising before termination
    • Limitation of liability: Survives — if it doesn’t, there’s no cap on post-termination claims
    • IP ownership: Survives — assignment of work product shouldn’t evaporate upon termination
    • Non-solicitation: Survives for stated period (if applicable)
    • Payment obligations: Survives for amounts accrued before termination

    The interaction between termination provisions and survival clauses is often overlooked. For a deeper analysis of how limitation of liability clauses interact with termination, see our clause-by-clause guide.

    7. Effective Date

    When does termination actually take effect?

    • Upon notice: The contract ends the moment notice is delivered. This is aggressive and leaves no transition time.
    • End of notice period: The contract continues through the notice period, then ends. This is the most common and most practical approach.
    • End of current billing cycle: Aligns termination with payment periods, reducing proration disputes.
    • Phased wind-down: Different obligations terminate at different times (e.g., new work stops immediately, but transition assistance continues for 60 days).

    Termination for Convenience by Contract Type

    SaaS Agreements

    SaaS termination provisions are among the most contentious. From the vendor’s perspective, annual or multi-year commitments fund product development and infrastructure — early termination undermines the business model. From the customer’s perspective, being locked into software that doesn’t work is unacceptable.

    Market standard: The customer can typically terminate at the end of any annual term with 30-60 days’ notice. Mid-term termination for convenience usually requires paying the remaining fees for the current term.

    Red flags to watch:
    – No termination right at all during the initial term (complete lock-in)
    – Only the vendor can terminate for convenience (one-sided)
    – Auto-renewal provisions paired with narrow cancellation windows that effectively eliminate exit rights

    MSAs and Professional Services

    Market standard: Mutual termination for convenience with 30-60 days’ notice. The critical issue is payment for work in progress, particularly for milestone-based engagements where work is partially completed.

    Key considerations:
    – Transition assistance is critical — the client needs to bring in a replacement provider without a gap
    – Work product delivered to date should be clearly owned by the client (check the IP assignment provisions)
    – Outstanding invoices remain payable regardless of termination

    Employment Agreements

    At-will employment is, in practical terms, termination for convenience by either party at any time. The key employment-specific issues are:

    • Severance triggers: Does termination without cause trigger severance payments?
    • Notice periods: Are there contractual notice requirements beyond at-will?
    • Garden leave: Does the employer pay the employee during a post-termination non-compete period?

    Government Contracts

    Government terminations for convenience operate under a different regulatory framework entirely. FAR 52.249-2 provides detailed procedures for settlement proposals, cost recovery, and dispute resolution. According to NCMA’s analysis, convenience terminations have surged in the current regulatory environment, making familiarity with FAR procedures essential for government contractors.

    Commercial contracts don’t have this safety net. Everything depends on what the parties negotiated.

    Termination for Convenience Red Flags

    When reviewing any contract, flag these issues immediately:

    One-sided termination rights. If only the other party can terminate for convenience, your client is locked in while the other side can leave at will. This is the most common and most dangerous red flag.

    No notice period. Immediate termination with zero warning leaves your client with no time to wind down operations, reassign staff, or find alternative arrangements.

    No payment for work in progress. If the clause is silent on payment for partially completed work, your client may have no contractual right to compensation for work already performed.

    No wind-down or transition period. Particularly dangerous in services contracts where the client depends on ongoing support.

    Forfeiture of pre-paid amounts. If the terminating party pre-paid for a year and terminates at month three, do they forfeit nine months of prepayment? Some contracts say yes.

    Disguised termination for cause. Watch for termination-for-convenience clauses that effectively avoid cure-period obligations. If the other side can terminate for convenience the day after a dispute arises, they’ll never need to provide a cure period.

    Auto-renewal paired with narrow termination window. A 30-day termination window on a three-year auto-renewing contract means your client has one chance per three years to exit. Miss it by a day, and they’re locked in again. Our guide on how to review contracts for red flags covers this pattern in detail.

    Sample Termination for Convenience Clauses

    Balanced Mutual Termination

    Either party may terminate this Agreement for convenience upon ninety (90) days'
prior written notice to the other party. Upon such termination, Client shall pay
Provider for (i) all Services performed through the effective date of termination,
(ii) all non-cancellable expenses reasonably incurred by Provider in connection
with the Services, and (iii) a wind-down fee equal to one month's average
monthly fees. Provider shall provide reasonable transition assistance for a
period of thirty (30) days following the effective date of termination.

    When to use: Standard MSAs and professional services agreements where both parties want flexibility. The wind-down fee compensates the provider for the early exit without creating an excessive penalty.

    One-Sided Termination with Kill Fee

    Client may terminate this Agreement for convenience upon sixty (60) days' prior
written notice. Upon such termination, Client shall pay Provider (i) all fees
for Services performed through the termination date, (ii) a termination fee
equal to 25% of the fees that would have been payable for the remainder of
the then-current term, and (iii) all non-cancellable third-party costs incurred
by Provider. Provider may not terminate this Agreement for convenience.

    When to use: When the client insists on one-sided termination rights and the provider needs protection for its upfront investment. The 25% kill fee is a reasonable middle ground.

    Termination with Transition Period

    Either party may terminate this Agreement for convenience upon thirty (30) days'
prior written notice. Following the effective date of termination, Provider shall
continue to perform transition assistance services for up to sixty (60) days at
Provider's then-current hourly rates. Provider shall cooperate in the orderly
transition of Services to Client or Client's designee, including data export in
commercially standard formats within ten (10) business days.

    When to use: Technology and managed services contracts where a smooth transition is critical to the client’s operations.

    How AI Assists with Termination Clause Review

    Clause Labs identifies all termination provisions in a contract — for cause, for convenience, auto-renewal, and expiration — and analyzes them in context. Specifically, the AI flags:

    • One-sided termination rights where only one party can exit
    • Missing notice periods or notice periods under 30 days
    • Absent wind-down and transition obligations
    • No payment provisions for work in progress upon termination
    • Interactions between termination and payment, survival, and limitation of liability clauses

    A manual review of termination provisions in a 30-page MSA typically takes 15-20 minutes to trace all the cross-references. Clause Labs’s analysis highlights every termination-related clause and its interactions in under 60 seconds, giving you a starting point for deeper review and negotiation.

    Frequently Asked Questions

    Can a party terminate for convenience without giving any reason?

    Yes — that’s the entire point of a termination-for-convenience clause. Unlike termination for cause, which requires a material breach, termination for convenience allows a party to exit for any reason or no reason at all. The only constraints are whatever notice period, payment obligations, and wind-down requirements the contract specifies. If the contract doesn’t specify any constraints, the terminating party can simply walk away.

    Is a termination fee enforceable?

    Generally yes, provided the fee is reasonable and not a penalty. Courts apply similar logic to termination fees as they do to liquidated damages provisions — the amount should reflect a reasonable estimate of the non-terminating party’s actual losses, not a punishment for exercising a contractual right. A termination fee equal to 25-50% of remaining contract value is typically defensible. A fee equal to 100% of remaining value looks more like a penalty and may face enforceability challenges.

    What’s the difference between termination for convenience and cancellation?

    In practice, the terms are often used interchangeably, but they can have different legal meanings depending on jurisdiction and context. Under the UCC (Uniform Commercial Code), “cancellation” occurs when one party terminates due to the other party’s breach, while “termination” can occur for any reason authorized by the contract. In non-UCC contracts, the distinction depends on how the agreement defines each term. Always check definitions.

    Can I negotiate termination for convenience out of a contract?

    You can try, and it sometimes works — particularly if you’re the party the other side wants locked in. If the counterparty depends on your long-term commitment (as a customer, partner, or key supplier), you have leverage to remove or significantly limit the termination-for-convenience right. The more common approach is to keep the right but add protections: longer notice periods, kill fees, payment for work in progress, and mandatory transition assistance.

    What happens to warranties after termination?

    It depends on whether the contract’s survival clause covers warranties. If warranties survive termination (they should), the warranting party remains liable for defects in work performed before termination. If the survival clause is silent on warranties, you may lose warranty protection on the moment the contract terminates. Always check — and negotiate — the survival clause alongside the termination provisions.

    This article is for informational purposes only and does not constitute legal advice. Consult a qualified attorney for advice specific to your situation.

    Termination provisions are one of the most negotiated — and most overlooked — areas of commercial contracts. If you’re reviewing a contract right now and want to check whether the termination clause protects your client, upload it to Clause Labs for a free AI risk analysis. The free tier includes 3 contract reviews per month with no credit card required.

  • Liquidated Damages vs. Actual Damages: What Your Contract Should Say

    Liquidated Damages vs. Actual Damages: What Your Contract Should Say

    Liquidated Damages vs. Actual Damages: What Your Contract Should Say

    A construction contractor missed a project deadline by 47 days. The contract specified liquidated damages of $2,500 per day — a total exposure of $117,500. The contractor argued the clause was an unenforceable penalty. The court disagreed, finding the per diem rate was a reasonable estimate of the owner’s daily losses from delayed occupancy. The clause held.

    Now consider the opposite scenario. A software vendor’s agreement set liquidated damages at $500,000 for any breach of the SLA — regardless of severity. The customer experienced 45 minutes of downtime. The court struck the clause as a penalty: the amount bore no reasonable relationship to the actual harm.

    The difference between these outcomes comes down to a single legal concept: reasonableness at the time of contracting. Get it right, and liquidated damages give you certainty, efficiency, and enforceability. Get it wrong, and you have an unenforceable penalty clause that leaves your client with nothing.

    This guide covers when to use liquidated damages versus actual damages, how to draft them to survive judicial scrutiny, and the red flags that signal a clause is headed for trouble. If you have a contract on your desk with a damages provision you’re not sure about, upload it to Clause Labs free for an instant risk analysis.

    The Core Distinction: Liquidated vs. Actual Damages

    Actual damages (also called compensatory or general damages) are calculated after a breach occurs. The non-breaching party proves what they lost, and the court awards compensation. The burden of proof is on the claimant, the process is expensive, and the outcome is uncertain.

    Liquidated damages are calculated before breach occurs. The parties agree in advance on a fixed amount (or formula) that will be payable if a specific breach happens. No proof of actual loss is required at the time of claim — the agreed amount controls.

    When to use liquidated damages:
    – Actual damages would be difficult to calculate at the time of breach (lost reputation, operational disruption, opportunity cost)
    – The parties want certainty about exposure
    – Litigation over damages would be disproportionately expensive relative to the contract value
    – The breach type is time-sensitive and delay in calculating damages would compound the harm

    When actual damages are preferable:
    – Losses are easily quantifiable (unpaid invoices, cost of replacement goods)
    – The range of potential damages is too wide to predict at contracting
    – You want full recovery without an artificial cap
    – The contract involves unique or novel arrangements where no reasonable estimate is possible

    When Are Liquidated Damages Enforceable?

    The enforceability test is well-established and remarkably consistent across jurisdictions. Both the Restatement (Second) of Contracts § 356 and UCC § 2-718 apply a two-factor analysis:

    Factor 1: Difficulty of estimation. Actual damages must have been difficult to estimate at the time the contract was formed. If damages are easily calculable, courts ask why the parties needed a liquidated amount at all.

    Factor 2: Reasonableness of the amount. The liquidated amount must be a reasonable forecast of anticipated harm — not a punishment for breach. As the Restatement puts it: “A term fixing unreasonably large liquidated damages is unenforceable on grounds of public policy as a penalty.”

    Here’s what many lawyers miss: the parties’ characterization doesn’t matter. Writing “this amount constitutes liquidated damages and not a penalty” doesn’t make it so. Courts look past the label to the substance. As Restatement § 356 comment c states, “Neither the parties’ actual intention as to its validity nor their characterization of the term as one for liquidated damages or a penalty is significant in determining whether the term is valid.”

    The Penalty Problem

    If a liquidated damages provision is struck down as a penalty, the clause is void. In most jurisdictions, the non-breaching party is then left to prove actual damages from scratch — which may be difficult, time-consuming, and expensive. In some cases, striking the liquidated damages clause eliminates the only practical remedy.

    Courts consider several signals when evaluating penalty risk:

    • Disproportionate amount: Liquidated damages that grossly exceed any reasonable estimate of harm
    • Uniform amount regardless of breach severity: The same dollar amount for a minor delay and a complete failure to perform
    • Amount that grows over time without justification: Escalating damages with no connection to escalating harm
    • One party bears all the risk: Liquidated damages imposed only on one side for every possible breach

    Drafting Liquidated Damages Clauses That Hold Up

    Every enforceable liquidated damages clause includes these elements.

    1. State That Actual Damages Would Be Difficult to Calculate

    This isn’t mere recital — it’s the factual predicate for enforceability. Be specific:

    The parties acknowledge that [Vendor’s/Contractor’s] failure to [perform specific obligation] would cause damages to [Client] that are difficult to ascertain with certainty at the time of contracting, including but not limited to [lost revenue from delayed operations, reputational harm, disruption of dependent business activities].

    2. Set a Reasonable Amount with a Demonstrable Basis

    The amount should relate to an actual estimate of harm, not a round number pulled from thin air. Document the basis:

    • For construction delays: daily carrying costs (interest on construction loan, temporary facilities, lost rental income)
    • For SaaS downtime: hourly revenue impact, customer service costs, contractual penalties to the customer’s own clients
    • For late delivery: warehousing costs, idle labor, lost sales during stockout

    3. Specify the Triggering Event

    Define precisely what constitutes the breach that triggers liquidated damages. Ambiguity here leads to disputes:

    For each calendar day after the Completion Date that Contractor has not achieved Substantial Completion, Contractor shall pay Owner $[amount] as liquidated damages.

    4. Address Whether Liquidated Damages Are the Exclusive Remedy

    This is where many practitioners stumble. You must explicitly state whether liquidated damages are:

    • Exclusive remedy for the specific breach (most common and most enforceable)
    • In addition to other remedies for other types of breach
    • An alternative to actual damages (risky — some courts view this as evidence the parties didn’t intend a genuine pre-estimate)

    The liquidated damages set forth in this Section constitute Owner’s sole and exclusive remedy for Contractor’s delay in achieving Substantial Completion. Nothing in this Section limits Owner’s remedies for any other breach of this Agreement.

    5. Include a Mutual Acknowledgment

    Both parties acknowledge that the liquidated damages amount set forth herein represents a reasonable estimate of the anticipated harm from the specified breach, considering all circumstances known at the time of contracting. The parties agree that this amount is not a penalty.

    While labeling alone doesn’t guarantee enforceability, this acknowledgment reinforces the parties’ intent and may be persuasive to a reviewing court.

    6. Cap the Aggregate Exposure

    Uncapped liquidated damages can accumulate to unreasonable totals. A per-day delay penalty that runs for 18 months, for example, may produce an aggregate amount that far exceeds any reasonable damages. Standard practice: cap liquidated damages at a percentage of the contract value (typically 10-20% for construction, variable for other contract types).

    Liquidated Damages by Contract Type

    Construction Contracts

    Construction is where liquidated damages appear most frequently. Per diem delay damages are standard, and courts have extensive case law on enforceability.

    Typical structure: $X per calendar day of delay beyond the contractual completion date.

    Enforceable range: Courts have upheld daily rates ranging from hundreds to tens of thousands of dollars, depending on project value. Bradley’s analysis of liquidated damages provisions notes that the key is demonstrating a reasonable relationship between the daily rate and actual daily losses (construction loan interest, temporary facilities, lost rental income, management overhead).

    Red flag: Per diem rates that apply identically after substantial completion — when the owner can occupy and use the facility — may be struck as penalties because actual harm diminishes once the owner has beneficial use.

    Bonus/penalty structures: Some construction contracts pair early completion bonuses with delay liquidated damages. These are generally enforceable and demonstrate good-faith risk allocation.

    SaaS and Software Agreements

    SLA credits are, functionally, a form of liquidated damages for service failures.

    Typical structure: If uptime falls below X%, customer receives a credit of Y% of monthly fees.

    Why they’re almost always enforceable: SLA credits are typically modest in amount relative to the contract value, they’re tied to specific, measurable performance failures, and the difficulty of calculating actual business harm from software downtime is well-recognized.

    The exclusive remedy trap: Most SaaS agreements designate SLA credits as the customer’s “sole and exclusive remedy” for downtime. This is favorable for the vendor — it prevents the customer from claiming actual damages (which could far exceed the credit amount). If you represent the customer, negotiate carve-outs from the exclusive remedy designation for extended outages, data loss, or security breaches. For more on SaaS agreement traps, see our guide on reviewing SaaS agreements with AI.

    Employment Agreements

    Liquidated damages in employment contexts most commonly appear in:

    • Training cost reimbursement: Employer pays for employee’s professional development; if the employee leaves within X years, they repay a prorated portion. Courts generally uphold these when the repayment schedule is reasonable and declining.
    • Non-compete breach: Some agreements specify a fixed amount payable if the employee breaches a non-compete. Enforceability is jurisdiction-dependent and highly variable — non-compete law itself varies dramatically by state.

    California note: California’s general prohibition on non-competes under Bus. & Prof. Code § 16600 means liquidated damages for non-compete violations are functionally unenforceable there, regardless of how well the damages clause is drafted. For more on the interaction between damages and indemnification provisions, see our guide on indemnification clauses.

    Real Estate Transactions

    Earnest money deposits are the most common form of liquidated damages in real estate.

    How it works: Buyer deposits 1-3% of purchase price. If buyer defaults, seller retains the deposit as liquidated damages.

    California’s specific framework: California Civil Code §§ 1675-1678 provides detailed rules. If the deposit is 3% or less of the purchase price for residential property, the provision is presumed valid. Above 3%, the seller bears the burden of proving reasonableness. The clause must be separately signed or initialed by both parties.

    Other states don’t have California’s statutory specificity, but the general principle holds: earnest money deposits that represent a reasonable percentage of the purchase price (typically 1-3%) are enforceable as liquidated damages. For a comprehensive look at real estate contract risks beyond damages provisions, see our real estate contract review checklist.

    Supply and Procurement Contracts

    Late delivery damages: $X per day or per week of late delivery. Enforceable when tied to buyer’s documented costs of delay (idle manufacturing line, expedited shipping for alternative supply, lost sales).

    Quality defect damages: A fixed amount per defective unit. Enforceable when the cost of inspecting and replacing defective goods is difficult to calculate per unit at the time of contracting.

    Volume shortfall damages: When a supplier commits to deliver a minimum quantity and falls short, liquidated damages may cover the buyer’s cost of sourcing from alternative (usually more expensive) suppliers.

    Common Liquidated Damages Mistakes

    Mistake 1: Setting the amount too high. The most frequent drafting error. A liquidated damages amount that materially exceeds any reasonable estimate of harm will be struck as a penalty, leaving the non-breaching party with no liquidated recovery and the burden of proving actual damages.

    Mistake 2: Setting the amount too low. Less common but equally problematic. A token amount ($100 per day of delay on a $5 million project) may signal that the parties didn’t take the provision seriously — and courts may decline to enforce it.

    Mistake 3: Failing to state that actual damages are difficult to calculate. This recital is more than boilerplate. Without it, courts may infer that the parties had no reason to use liquidated damages, which undercuts the enforceability rationale.

    Mistake 4: Making liquidated damages cumulative with full actual damages. This is a trap. If a party can recover both liquidated damages AND actual damages for the same breach, the aggregate recovery may be deemed punitive. Specify whether liquidated damages are exclusive or address the interaction explicitly.

    Mistake 5: Not specifying whether LDs are an exclusive remedy. Ambiguity about available remedies invites litigation. State it clearly.

    Mistake 6: Using liquidated damages when actual damages are easily calculable. If the most likely form of harm is an unpaid invoice or a quantifiable cost, liquidated damages may be unnecessary and harder to enforce.

    Mistake 7: Forgetting to update amounts when contract value changes. A liquidated damages amount set for a $100,000 contract may be unreasonable for the same contract after a $2 million change order.

    Liquidated Damages Red Flags in Contract Review

    When reviewing a contract, flag these provisions for closer analysis:

    • LD amount exceeding 15-20% of total contract value — potential penalty
    • No statement about difficulty of calculating actual damages — missing enforceability predicate
    • LDs cumulative with unlimited actual damages — double recovery risk
    • One-sided LDs — only one party faces liquidated damages exposure
    • No cap on aggregate LDs — per-day penalties can accumulate to unreasonable totals
    • LDs triggered by events outside the paying party’s control — unfair risk allocation
    • Escalating LDs without justification — penalty indicator if harm doesn’t escalate similarly
    • Identical LD amount for breaches of wildly different severity — suggests penalty, not pre-estimate

    For a broader framework on identifying contract risks, see our complete contract red flags checklist. And for the related issue of how liability caps interact with liquidated damages, see our guide on limitation of liability clauses.

    How AI Handles Damages Provision Review

    AI contract review tools can flag liquidated damages provisions quickly, but the enforceability analysis requires human judgment. Here’s what AI does well and where you need to step in.

    AI handles effectively:
    – Identifying liquidated damages clauses (even when buried in remedy or general terms sections)
    – Flagging whether the clause specifies exclusive or cumulative remedies
    – Detecting interaction between liquidated damages and limitation of liability provisions
    – Identifying missing elements (no difficulty-of-calculation statement, no cap)

    Requires attorney judgment:
    – Whether the dollar amount is reasonable relative to anticipated harm
    – Jurisdiction-specific enforceability standards
    – Whether the contract’s commercial context supports liquidated versus actual damages
    – Strategic advice on whether to accept, negotiate, or reject the provision

    Clause Labs flags damages provisions, identifies missing elements, and highlights potential enforceability concerns — giving you the starting point so you can focus your time on the judgment-intensive analysis. Try it free with 3 reviews per month.

    Solo lawyers handling 20+ contracts per month use Clause Labs to flag liquidated damages issues, liability cap mismatches, and missing remedy provisions automatically — starting at $0 for 3 reviews. Try Clause Labs free.

    Frequently Asked Questions

    What’s the difference between liquidated damages and a penalty?

    A liquidated damages clause represents a genuine pre-estimate of anticipated harm from a specific breach. A penalty is a punishment for breach — an amount meant to coerce performance rather than compensate for loss. Courts look at whether the amount is reasonable relative to anticipated or actual harm. If it’s grossly disproportionate, it’s a penalty and unenforceable regardless of what the contract calls it.

    Can liquidated damages be challenged in court?

    Yes. The party paying liquidated damages can argue the clause is an unenforceable penalty. The party receiving liquidated damages may argue the clause is valid. The court applies the two-factor test: difficulty of estimation and reasonableness of amount. Burden of proof varies by jurisdiction.

    Should liquidated damages be the exclusive remedy?

    For the specific breach they cover, usually yes. Making liquidated damages the exclusive remedy for a defined breach type (delay, downtime, defects) makes the provision more enforceable because it demonstrates the parties’ intent to pre-allocate risk. But preserve separate remedies for other breach types — liquidated damages for delay shouldn’t preclude claims for, say, defective work or IP infringement.

    How do I calculate a reasonable liquidated damages amount?

    Start with the actual costs that the non-breaching party would likely incur. For construction delay: daily loan interest + temporary facilities + lost rental income + management overhead. For SaaS downtime: hourly revenue impact + customer service costs. Document the calculation and keep it in the contract file — this contemporaneous evidence of reasonableness is your best defense if the clause is challenged.

    Can both parties have liquidated damages obligations?

    Yes, and mutual liquidated damages provisions are often viewed more favorably by courts because they suggest balanced risk allocation rather than one-sided punishment. Example: contractor pays delay LDs; owner pays acceleration costs if owner causes delay.

    This article is for informational purposes only and does not constitute legal advice. Consult a qualified attorney for advice specific to your situation. Liquidated damages enforceability varies significantly by jurisdiction — verify your state’s standards before relying on this guide.

  • Non-Compete Clauses After the FTC Ban: What’s Enforceable in 2026?

    Non-Compete Clauses After the FTC Ban: What’s Enforceable in 2026?

    Non-Compete Clauses After the FTC Ban: What’s Enforceable in 2026?

    The FTC’s federal non-compete ban is dead. On September 8, 2025, the Fifth Circuit officially dismissed the FTC’s appeal in Ryan, LLC v. FTC, ending the agency’s attempt to ban non-competes nationwide. The rule that was supposed to void an estimated 30 million non-compete agreements never took effect.

    But here’s what matters for the lawyers reviewing employment agreements right now: the legal landscape shifted anyway. At least four states now ban non-competes almost entirely. More than a dozen impose income thresholds, notice requirements, or durational limits. And the FTC is still enforcing against individual non-competes it considers unfair under Section 5 of the FTC Act — case by case, employer by employer.

    If you review employment agreements for clients, the question is no longer “Are non-competes legal?” It’s “Is this specific non-compete enforceable in this specific state for this specific employee?” This guide maps the current landscape. Try Clause Labs Free to upload any employment agreement and get instant AI analysis of restrictive covenant issues — including jurisdiction-specific flags.

    What Happened: The FTC Rule Timeline

    Understanding the current state requires knowing how we got here.

    April 23, 2024: The FTC issues a final rule banning most non-compete agreements nationwide, with an effective date of September 4, 2024. The rule would have voided existing non-competes for most workers and banned new ones entirely, with narrow exceptions for senior executives and business sale agreements.

    August 20, 2024: A federal judge in the Northern District of Texas (in Ryan, LLC v. FTC) sets aside the rule nationwide, holding that the FTC exceeded its statutory authority. A separate challenge in Florida reached a similar conclusion.

    September 2025: The FTC officially abandons its appeal, accepting the vacatur. The federal non-compete ban is permanently dead.

    January 2026: At a public workshop, the FTC clarifies it will no longer pursue a categorical ban. Instead, it retains authority to challenge specific non-competes under Section 5 of the FTC Act as unfair methods of competition — particularly those targeting low-wage workers or imposing exceptionally broad restrictions.

    The net result: no federal ban, but a significantly heightened enforcement environment and a patchwork of state laws that have only gotten more aggressive.

    State-by-State Non-Compete Enforceability in 2026

    The real action on non-competes is now entirely at the state level. Here’s where things stand, organized by restriction level.

    States That Ban Non-Competes Almost Entirely

    Four states effectively prohibit non-compete agreements for employees in most or all circumstances:

    California: The broadest ban. Cal. Bus. & Prof. Code § 16600 voids non-competes in nearly all employment contexts. Recent legislation strengthened the ban by voiding out-of-state non-competes applied to California workers — meaning a Texas employer can’t enforce a Texas non-compete against an employee who moves to California.

    Minnesota: Non-competes entered into on or after July 1, 2023, are prohibited for most workers, with limited statutory exceptions for the sale of a business or dissolution of a partnership.

    Oklahoma: Title 15, § 219A generally voids non-competes, with exceptions for the sale of a business and dissolution of a partnership. This has been Oklahoma law for decades.

    North Dakota: N.D. Cent. Code § 9-08-06 broadly prohibits non-competes, with the standard business-sale exception.

    States with Income Threshold Restrictions

    A growing number of states tie non-compete enforceability to how much the employee earns. As of 2026, these income thresholds have been updated:

    State 2026 Non-Compete Income Threshold Notes
    Colorado $127,091 (non-compete); $76,254 (non-solicit) Must protect trade secrets; penalties for violations
    Illinois $75,000 (non-compete); $45,000 (non-solicit) Next increase in 2027
    Washington $126,858.83 (employee); $317,147.09 (contractor) Annual adjustment
    Oregon $119,541 Bureau of Labor and Industries sets annual threshold
    Massachusetts Hourly employees exempt; requires garden leave or other consideration 12-month maximum duration
    Virginia Low-wage employees exempt (below median state wage) Applies to non-competes and non-solicits
    Rhode Island Non-exempt employees exempt Additional protections for healthcare workers

    What this means in practice: If your client employs a marketing coordinator in Illinois earning $60,000/year, a non-compete in that employee’s agreement is void as a matter of law. The same non-compete for an Illinois sales director earning $200,000/year could be enforceable — subject to reasonableness analysis on scope, duration, and geography.

    States with Significant Restrictions (But Not Bans)

    These states allow non-competes but impose meaningful procedural or substantive limits:

    Massachusetts: Non-competes cannot exceed 12 months. The employer must provide either garden leave pay (at least 50% of base salary during the restricted period) or “other mutually-agreed upon consideration.” Non-competes are void for hourly workers, undergraduate or graduate students in internships, and employees terminated without cause.

    Washington: Beyond the income threshold, non-competes exceeding 18 months are presumptively unreasonable. Employers must disclose the non-compete terms before or at the time of the job offer.

    Oregon: Non-competes are limited to 12 months, must be provided in writing at the time of offer or at least two weeks before the start date, and the employee must be given a copy. Only employees earning above the threshold are covered.

    Colorado: Beyond the income threshold, employers must notify the worker of the non-compete “in a separate document” and provide the non-compete terms before the worker accepts the offer. Colorado imposes civil penalties of up to $5,000 per violation for non-competes that don’t meet statutory requirements.

    States Where Non-Competes Are Generally Enforceable

    In the remaining states, non-competes are permitted subject to the traditional common-law reasonableness test:

    • Duration: Typically 6-24 months. Courts in most states view anything over 2 years skeptically.
    • Geographic scope: Must be tied to the employer’s actual business footprint or the employee’s territory.
    • Activity scope: Must be limited to competitive activities, not all employment.
    • Consideration: Most states require independent consideration for existing employees (not just continued employment).

    States like Texas, Florida, Georgia, and Ohio generally enforce non-competes that meet these reasonableness standards — but even in these states, judicial scrutiny has increased since the FTC attempted its ban.

    Non-Compete Red Flags to Catch in Every Employment Agreement

    For lawyers reviewing contracts containing non-competes — whether reviewing for red flags generally or specifically evaluating restrictive covenants — here are the issues that should trigger immediate attention.

    Duration Exceeding State Limits

    The most common enforceable window is 12-24 months. A 36-month non-compete is likely unreasonable in most jurisdictions. Several states cap duration by statute: Massachusetts and Oregon at 12 months, Washington at 18 months (presumptive). Any non-compete exceeding these limits is either unenforceable or requires modification.

    Employee Below Income Thresholds

    If the employee earns less than the applicable state threshold — $75,000 in Illinois, roughly $127,000 in Colorado, roughly $127,000 in Washington — the non-compete is likely void. Review compensation details before analyzing the non-compete itself.

    Independent Contractor Non-Competes

    Non-competes for independent contractors are almost always unenforceable, and in states like Washington (which sets the contractor threshold at $317,147), they face even more scrutiny. Worker misclassification compounds the risk: if the “contractor” is actually an employee under state law, the non-compete analysis shifts entirely.

    Geographic Scope That’s Unreasonable

    A nationwide non-compete for a regional sales representative is overbroad. A non-compete covering “anywhere the Company does business” when the company operates globally is almost certainly unenforceable. Geographic scope must be proportional to the employee’s actual territory or the employer’s legitimate business interests.

    Non-Solicitation Disguised as Non-Compete

    Some agreements label a broad restriction as a “non-solicitation” to avoid non-compete scrutiny. If the non-solicitation effectively prevents the employee from working in their field — for example, by prohibiting contact with any current or former customer of a company with thousands of customers — it may be analyzed as a de facto non-compete.

    Forum Selection Clauses That Forum-Shop

    Watch for a Texas employer with California employees specifying Texas law and Texas courts for non-compete enforcement. California’s strong anti-non-compete policy may override the contractual choice of law — but the employee would have to litigate that point, which costs money and time. Flag these provisions for your clients.

    Missing Adequate Consideration

    In many states, an existing employee signing a non-compete must receive independent consideration beyond continued employment. A new bonus, promotion, stock grant, or similar benefit may be required. If the non-compete is presented to an existing employee with no new consideration, it may be unenforceable.

    Alternatives to Non-Competes That Actually Work

    When advising clients who want to protect business interests without the enforceability risk of non-competes, recommend these alternatives:

    Non-Solicitation Agreements

    Prohibit the departing employee from soliciting specific clients, customers, or employees — but don’t prohibit competitive employment itself. Non-solicitation agreements are enforceable in almost every state, including California (with limitations), because they restrict a specific behavior rather than the ability to earn a living.

    Drafting tip: Limit the non-solicitation to clients the employee actually worked with during their last 12-24 months of employment. Restrictions covering all company clients (including those the employee never met) face enforceability challenges.

    Enhanced Confidentiality / NDA Agreements

    Protect specific trade secrets and confidential information through robust NDAs with clearly defined protected information. When properly drafted, confidentiality agreements protect the employer’s most valuable information without restricting where the employee can work.

    Drafting tip: Define confidential information by category (customer lists, pricing algorithms, strategic plans) rather than using catch-all language. Include the five standard exclusions and a reasonable duration.

    Garden Leave Provisions

    Require the employer to continue paying the employee during the restricted period in exchange for the employee not competing. This approach is gaining traction because it provides the employee with compensation during the restriction, making enforceability far more likely.

    Drafting tip: Specify the percentage of base salary (50-100%) and duration. Massachusetts now requires garden leave as consideration for non-competes. Other states are likely to follow.

    Intellectual Property Assignment Agreements

    Protect company innovations by requiring employees to assign work-related IP to the employer. This doesn’t restrict where the employee works — it restricts what they can take with them.

    Drafting tip: Always include a “prior inventions” schedule so employees can document pre-existing IP. Many states — including California, Delaware, Illinois, Minnesota, and Washington — have statutes limiting the scope of invention assignment agreements.

    Clawback Provisions

    Tie bonuses, equity vesting, or deferred compensation to post-employment behavior. If the employee competes within a specified period, they forfeit unvested benefits. This is functionally a non-compete with an economic enforcement mechanism rather than a judicial one.

    Drafting tip: Ensure the clawback amount is proportional and doesn’t function as a penalty. Courts may analyze excessive clawbacks as non-competes subject to the same enforceability standards.

    How to Review Non-Compete Clauses: A 7-Step Process

    When a client brings you an employment agreement with a non-compete, follow this process:

    1. Identify the governing jurisdiction: Which state’s law controls? Is the employee located in a different state from the employer? If the employee works remotely from a ban state (California, Minnesota), the non-compete may be void regardless of the contract’s choice-of-law clause.

    2. Check if non-competes are enforceable in that state: Refer to the state-by-state table above. If the state bans non-competes, your analysis is short.

    3. Verify income threshold compliance: For states with income thresholds (Colorado, Illinois, Washington, Oregon, Virginia), confirm the employee’s compensation exceeds the applicable limit.

    4. Evaluate reasonableness: Duration (over 24 months is suspect), geographic scope (proportional to the employee’s actual territory), and activity scope (limited to competitive activities, not all employment).

    5. Check for adequate consideration: Is the non-compete part of the initial offer, or is it being imposed on an existing employee? If the latter, what independent consideration is being provided?

    6. Assess blue-pencil doctrine applicability: Some states allow courts to modify overbroad non-competes to make them reasonable. Others strike them entirely. Knowing whether your jurisdiction blue-pencils affects your risk assessment and negotiation strategy.

    7. Review interaction with other restrictive covenants: Does the agreement also contain a non-solicitation, NDA, and IP assignment? Together, these may provide the protection the employer needs without the non-compete — which gives you a negotiation argument for striking it.

    For a broader framework on reviewing employment agreements for all types of red flags, see our complete contract red flags checklist.

    Industry-Specific Non-Compete Considerations

    Technology and Software

    Tech non-competes face the most scrutiny. California’s ban covers virtually all tech workers. In other states, courts are increasingly skeptical of non-competes for software engineers because the “confidential information” at issue (coding skills, general technology knowledge) is difficult to distinguish from general professional competence.

    Healthcare

    Multiple states — including Colorado (effective August 2025) — have specific statutes restricting non-competes for physicians, nurses, dentists, and other healthcare providers. The concern is patient access: if a physician can’t practice within 50 miles, patients lose access to care.

    Financial Services

    FINRA-registered representatives are subject to industry-specific rules. FINRA’s Protocol for Broker Recruiting allows registered representatives to take certain client information (names, addresses, phone numbers, account types) when switching firms, which limits the practical impact of non-compete and non-solicitation restrictions.

    Sales and Business Development

    Sales non-competes are among the most commonly litigated. Courts evaluate them based on whether the salesperson had access to proprietary customer relationships, pricing data, or strategic plans — not just whether they “know the clients.” Account-based restrictions (prohibiting solicitation of specific named accounts) are more enforceable than blanket geographic restrictions.

    Executive Employment

    Senior executives face the fewest protections. Most state restrictions and income thresholds don’t apply at executive compensation levels. Courts generally enforce reasonable non-competes for C-suite executives and senior officers, particularly when tied to significant equity or severance packages. That said, even executive non-competes must meet reasonableness standards on duration, scope, and geography.

    How Clause Labs Handles Non-Compete Analysis

    When you upload an employment agreement to Clause Labs, the AI automatically identifies non-compete, non-solicitation, non-disclosure, and other restrictive covenant provisions. It flags potential enforceability issues based on the governing jurisdiction, highlights overbroad restrictions on duration, geography, and activity scope, and identifies missing consideration provisions.

    For employment agreements specifically, Clause Labs’s employment playbook covers all the restrictive covenant issues discussed in this article — plus compensation risks, termination traps, and IP assignment problems. See our free employment agreement review tool for details on the full employment agreement analysis.

    Frequently Asked Questions

    Are non-competes banned federally in 2026?

    No. The FTC’s federal non-compete rule was struck down by a Texas federal court in August 2024 and the FTC abandoned its appeal in September 2025. There is no federal ban. However, the FTC retains authority to challenge specific non-competes it considers unfair under Section 5 of the FTC Act — particularly those targeting low-wage workers or imposing unreasonably broad restrictions.

    Can my client’s employer enforce their non-compete in 2026?

    It depends entirely on the state, the employee’s compensation level, and the specific terms of the non-compete. In California, Minnesota, Oklahoma, and North Dakota, the answer is almost certainly no. In states with income thresholds (Colorado, Illinois, Washington, Oregon), it depends on whether the employee earns above the threshold. In all other states, enforceability requires meeting the traditional reasonableness test on duration, geography, and scope.

    What happens to non-competes already signed before state bans took effect?

    This varies by state. Minnesota’s ban applies only to non-competes entered into on or after July 1, 2023 — pre-existing non-competes remain enforceable if otherwise valid. California’s strengthened law, by contrast, voids non-competes regardless of when they were signed because the state’s underlying prohibition (§ 16600) has existed for over a century.

    Can a non-compete be enforced across state lines?

    Potentially, but it’s complicated. If a Texas employer sues in Texas to enforce a non-compete against a former employee now working in California, the California court may refuse to enforce it under California’s strong public policy against non-competes. Choice-of-law provisions in the agreement don’t always control — courts apply their own state’s public policy when it conflicts with the contractual choice of law.

    How do I advise a client who already signed a non-compete?

    First, determine the governing jurisdiction and whether the non-compete is enforceable under current law. Second, assess whether the specific terms (duration, geography, scope) are reasonable. Third, evaluate the practical enforcement risk — would the employer actually sue, given the cost and uncertainty? Many non-competes that are technically enforceable are never enforced because the economics don’t justify litigation. Finally, if the client wants to compete, consider whether negotiating a release or buyout is possible.

    Have an employment agreement with a non-compete you need to evaluate? Upload it to Clause Labs free — the AI flags jurisdiction-specific enforceability issues, overbroad restrictions, and missing consideration provisions in under 60 seconds. Start with 3 free reviews per month, no credit card required.

    This article is for informational purposes only and does not constitute legal advice. Non-compete enforceability varies significantly by jurisdiction, and state laws change frequently. The information in this article reflects the legal landscape as of February 2026. Consult a qualified attorney in the relevant jurisdiction for advice specific to your situation.