The Clause Watchlist
Clauses that cost money
Not a dictionary of legal definitions but a risk-first field guide to the provisions we keep finding buried in contracts during audits. What each clause actually does, what to check before you sign, and the operational read on why it matters.
Field note
Before signing anything, Ctrl/Cmd+F for "renew," "terminate," "notice," and "assign." Four searches, two minutes, catches most of the traps.
Why it breaks: It catches them at signing. Nobody re-runs the search 11 months later when the clause actually fires. Contracts don't bite when you sign them; they bite on a Tuesday two years later.
Or: we re-read your contracts every week so the clauses can't wait you out.
Auto-renewal clauses
An auto-renewal clause is a provision that extends a contract automatically unless notice is given within a defined window. The risk isn't the renewal itself, it's the window. Miss it by a day and you're locked in for another term, often at the counterparty's pricing.
247
average software renewals a company handles per year, roughly one every business day.
Source: Vertice, 2025
~25%
of SaaS budgets lost to unused entitlements, by Gartner's estimate.
Source: Gartner, via License Logic, 2026
4 in 10
organizations have nobody actively tracking SaaS usage or right-sizing contracts.
Source: Flexera, 2025 State of ITAM Report
What to look for
The exact notice window (30/60/90 days) and whether it's measured from the renewal date or the contract's end date.
Whether notice must be in writing, and to which named address or contact. Informal notice often doesn't count.
Whether the renewal term matches the original term, or silently extends to something longer.
Whether pricing is locked or resets to a new rate on renewal.
The operational read
Notice-window math should account for how your business actually counts days, calendar vs. business days and any recurring closures on your calendar. A fixed day-count built without checking that assumption is the most common way teams miss a window they thought they'd hit comfortably.
Field note
Set your renewal alert for the notice deadline minus 30 days, not the renewal date. The renewal date is when it's already too late; the notice window is the only date that matters.
Why it breaks: Someone has to read every contract to find the notice period first, and then maintain the calendar when contracts get amended. That someone has a day job.
Or: reading notice periods is literally what we do all day.
How much notice is usually required to stop an auto-renewal?
It varies by contract and is anywhere from 30 to 120 days is common. The number that matters is the one written in your specific agreement, not a market average.
Can you cancel after the notice window has closed?
Usually not without the counterparty's agreement. Some contracts have a hardship or mutual-consent exit, but by default you're bound for the new term.
Uncapped indemnities and liability caps
An indemnity is a promise to cover the other party's losses arising from specific events. When it's uncapped, your exposure isn't limited to the contract value and it can extend to the counterparty's full downstream losses, which is where the real risk lives.
What to look for
Whether the indemnity carves out an exception to the general liability cap (a common and easy-to-miss pattern).
Which events trigger the indemnity: IP infringement, data breach, and gross negligence are the usual carve-outs.
Whether the cap is a multiple of fees paid, a fixed figure, or genuinely uncapped.
Mutual vs. one-sided and whether both parties carry the same exposure.
The operational read
Carve-outs for gross negligence and wilful misconduct are standard across most commercial law systems and usually can't be negotiated away entirely so treat them as a given rather than a negotiation lever.
Is an uncapped indemnity always a dealbreaker?
No, for high-risk categories like IP infringement or data breach, an uncapped indemnity from a vendor may be reasonable. The question is whether it's scoped to the right events, not whether a cap exists at all.
Change-of-control and assignment clauses
These clauses determine what happens to a contract when a party is acquired, merges, or is restructured. Left unchecked, they surface as diligence findings and a counterparty can terminate or renegotiate the moment your company changes hands.
What to look for
Whether a change of control counts as an assignment requiring the other party's consent.
Whether consent can be 'unreasonably withheld' or is entirely at the counterparty's discretion.
Termination rights triggered by a change of control, separate from assignment consent.
Whether internal restructuring (moving the contract between affiliates) is exempted.
The operational read
Check whether the contract names a specific legal entity or licence rather than the company generally because restructuring within the same group can still trigger the clause if the named counterparty changes.
Notice provisions and notice windows
A notice provision defines how, when, and to whom formal notices under a contract must be delivered. It's the most operationally significant clause nobody reads twice and it governs the deadlines for auto-renewal, breach, and termination all at once.
What to look for
The required delivery method (email, courier, registered post), many contracts still require physical delivery to be valid.
The named recipient and address, which goes stale as teams and offices change.
How notice periods are calculated: business days vs. calendar days changes the math materially.
Whether the clause deems notice 'received' on sending or on actual receipt.
The operational read
Notice-window math should always be built around your actual working calendar with weekends, public holidays, and any regional closures rather than a generic assumption. This is the single most common way a notice deadline gets missed by a matter of days.
Exclusivity and non-compete clauses
Exclusivity clauses restrict one or both parties from working with competitors for the contract's duration (or beyond). They're common in distribution, reseller, and services agreements, and easy to sign without registering the ongoing restriction they create.
What to look for
The scope: by product category, geography, or customer segment.
The duration, and whether it survives termination of the underlying agreement.
Carve-outs for existing relationships signed before the exclusivity took effect.
Whether breach triggers termination, damages, or both.
The operational read
Non-compete and exclusivity enforceability is typically fact-specific and subject to reasonableness limits on duration, geography, and scope and a clause that reads as absolute in the contract text isn't automatically enforceable as written.
Payment terms and late-payment interest
Payment terms set the invoice-to-payment window and what happens when it's missed. The clause that matters most is the one CFOs never see until cash flow is already strained: the late-payment interest rate and when it starts accruing.
What to look for
The payment window (net 30/45/60) and whether it starts from invoice date or receipt of goods/services.
The late-payment interest rate and whether it compounds.
Whether late payment gives the counterparty a right to suspend performance.
Currency and jurisdiction for payment on cross-border arrangements.
The operational read
Confirm the late-payment interest rate against what's customary for your sector before signature. An aggressive rate is a negotiation point worth flagging early, not after cash flow is already strained.
Termination for convenience vs. cause
Termination for convenience lets a party exit without a reason, usually on notice. Termination for cause requires a breach and often a cure period. Confusing the two or missing which one you actually have changes your entire exit strategy.
What to look for
Whether a for-convenience right exists at all, and whether it's mutual or one-sided.
The notice period and any early-termination fees attached to a for-convenience exit.
The cure period for termination for cause, and what counts as a 'material' breach.
Wind-down obligations like data return, transition assistance, final invoicing are triggered by either path.
The operational read
Fixed-term contracts without an explicit for-convenience right can be harder to exit early than teams assume, hence confirm the exit mechanism before treating any contract as cancellable at will.
Most-favoured-nation (MFN) clauses
An MFN clause commits you to giving one counterparty terms at least as good as those offered to anyone else. They're common in early enterprise and channel deals, and become a quiet drag on every future negotiation once several stack up.
What to look for
The scope of comparison: pricing only, or all commercial terms.
Whether it's self-reporting (you must proactively notify) or claim-based (they must ask).
The comparison universe: 'any customer' vs. 'similarly situated customers.'
Duration, and whether it survives contract renewal.
The operational read
MFN clauses show up more often in agreements drafted by counterparties used to enterprise SaaS norms and are worth flagging specifically when reviewing unfamiliar paper from a new type of counterparty.
Perpetual and evergreen licence terms
A perpetual licence has no end date; an evergreen one renews indefinitely absent action. Both feel like a convenience at signature and become a governance gap later and nobody owns the decision to revisit terms that never formally expire.
What to look for
Whether 'perpetual' applies to the licence grant only, or also to pricing and support commitments.
Termination rights independent of the licence term for breach, insolvency, or convenience.
Whether support/maintenance is bundled or a separate, cancellable line.
Audit rights tied to usage-based perpetual licences.
The operational read
Perpetual software and IP licences should be checked against how your company structures IP ownership and a later corporate restructuring can complicate a licence that was never designed to survive one.
Limitation of liability carve-outs
A limitation of liability clause caps what each party owes the other. The list of exceptions where the cap doesn't apply are where the actual risk sits, and they're usually buried in a subordinate clause referencing the main one.
What to look for
Standard carve-outs: confidentiality breach, IP infringement, gross negligence, wilful misconduct.
Whether data breach or regulatory fines are carved out separately (increasingly common).
Whether the carve-out list is symmetric between both parties.
Interaction with the indemnity clause carve-outs are often defined once and referenced twice.
The operational read
Negotiated liability caps are generally enforceable between commercial parties, but carve-outs for gross negligence and wilful misconduct reflect a public-policy floor that can't be contracted away in most systems so treat them as a given, not a negotiation lever.
We check every contract for this.
A Leak Audit runs your active contracts against this exact watchlist and tells you what's actually exposed.
Get the Leak AuditThis page is operational guidance based on patterns we see in contract audits, not legal advice. Engage qualified counsel for legal opinions specific to your situation.