Legal Redline Response Cheat Sheet

How to Use This

When legal's redline comes back, most reps either panic-forward it to their own legal team with no context, or accept it to avoid the friction. Use this to understand what's actually being asked for, and to send a same-day standard response instead of losing the deal to a week of email ping-pong.

The 10 Most Common Redlines

1. Uncapped / Unlimited Liability

What they're asking for: Removal of the liability cap, so their exposure to your negligence (or yours to theirs) has no ceiling. What it actually means: Their legal team is following standard policy to protect against catastrophic risk — this is rarely personal to your contract. Standard response:

"We can't remove the liability cap entirely, but we can discuss raising it — typically to 12 months' fees, or 24 months for breaches of confidentiality/IP/data protection, which is standard in enterprise agreements at our size."

Hold or fold: Hold on "uncapped." Fold on raising the cap multiple, especially carving out higher caps for the specific categories (IP, confidentiality, data breach) that usually matter most to their legal team.

2. Broad / One-Sided Indemnification

What they're asking for: You indemnify them broadly (including for their own misuse), while their indemnification of you is narrow or absent. What it actually means: Standard opening position from buyer-side legal — indemnification is almost always negotiated to mutual. Standard response:

"We're comfortable with mutual indemnification — each party indemnifies the other for its own breaches, IP infringement claims, and confidentiality violations. One-directional indemnification isn't something we can agree to."

Hold or fold: Hold on one-sided. Fold on making it explicitly mutual and scoped to IP/confidentiality/data breach.

3. IP Assignment / Ownership of Feedback & Work Product

What they're asking for: Any feedback, customizations, or configurations the buyer provides become their IP, potentially including your core product improvements. What it actually means: They don't want to be seen as "giving away" ideas for free — reasonable in principle, overreaching in scope as drafted. Standard response:

"Feedback and suggestions can remain non-exclusive and freely usable by us to improve the product for all customers. Any customer-specific configuration or data remains yours. We can't assign core product IP."

Hold or fold: Hold on core product IP. Fold on customer data/config ownership — that should already be theirs.

4. Auto-Renewal With Long Notice Period

What they're asking for: Removal of auto-renewal, or a very long (90–180 day) notice period to cancel before renewal. What it actually means: They've been burned by a vendor before, or they simply want more control over the renewal decision timeline. Standard response:

"We can move to a 60-day notice period ahead of renewal — enough time for both sides to plan, without the deal defaulting to non-renewal by accident."

Hold or fold: Fold to 60 days if 90+ is the ask; hold on removing auto-renewal entirely if it undermines your renewal forecasting.

5. Termination for Convenience

What they're asking for: The right to cancel the contract at any time, without cause, often with little or no notice. What it actually means: They want to de-risk in case the initiative loses internal sponsorship or budget — a real, common concern, not necessarily distrust of you. Standard response:

"We can offer termination for convenience with 90 days' written notice and payment for services rendered/committed through that period. Immediate no-notice termination isn't something we can agree to."

Hold or fold: Hold on no-notice/no-payment termination. Fold on offering a notice-period version.

6. Data Processing / Sub-Processor / Cross-Border Transfer Terms (DPA)

What they're asking for: Approval rights over sub-processors, restrictions on where data is processed, specific breach-notification timelines. What it actually means: Compliance-driven (GDPR, sector regulation) — usually non-negotiable on their end, and legitimate. Standard response:

"We can commit to [X-hour] breach notification and provide our current sub-processor list with advance notice of material changes. Full pre-approval of every sub-processor isn't operationally something we can commit to, but we can offer an objection window."

Hold or fold: Mostly fold — this is compliance, not negotiation leverage. Hold only on operationally impossible asks (e.g., pre-approval with no timeline).

7. Most-Favored-Nation / Most-Favored-Customer Pricing

What they're asking for: A guarantee that no other customer ever gets a better price than them, indefinitely. What it actually means: They want price protection without doing the work of renegotiating — reasonable instinct, unreasonable as an open-ended clause. Standard response:

"We can commit that your pricing won't be undercut for equivalent volume and term during your current contract period, reviewed at renewal — an indefinite, unscoped MFN clause isn't something we offer any customer."

Hold or fold: Hold on indefinite/unscoped. Fold on a scoped, term-limited version.

8. SLA Credits / Liquidated Damages for Downtime

What they're asking for: Financial penalties (service credits or direct damages) tied to uptime/SLA misses. What it actually means: They want downtime to have a real cost to you, not just an apology — fair in principle if scoped correctly. Standard response:

"We can offer service credits scaled to the severity and duration of an SLA miss, capped at [X]% of monthly fees. Uncapped liquidated damages beyond service credits isn't something we can agree to."

Hold or fold: Hold on uncapped damages. Fold on a capped service-credit schedule.

9. Non-Solicitation of Employees

What they're asking for: A one-way clause preventing you from hiring their employees, without a matching restriction on them hiring yours. What it actually means: Genuine concern about losing staff to a vendor they've worked closely with — common, and usually fixable by making it mutual. Standard response:

"We're fine with a mutual, time-limited (12-month) non-solicitation clause covering employees directly involved in the engagement. A one-directional or indefinite version isn't something we can agree to."

Hold or fold: Hold on one-directional/indefinite. Fold on mutual, scoped, 12-month version.

10. Payment Terms Extension (Net 60/90/120) + Removal of Late Payment Penalties

What they're asking for: Longer payment windows and no interest/penalty for late payment. What it actually means: Cash-flow optimization on their side — standard ask from finance/procurement, not a signal of financial distress (usually). Standard response:

"We can move to net-60 in exchange for annual upfront billing rather than monthly. We do need to retain a late-payment interest clause — standard at [X]% per month past due — to keep terms enforceable."

Hold or fold: Fold on net-60 (with a trade — see the Concession Strategy Matrix). Hold on removing late-payment penalties entirely; that's an enforceability issue, not just a friction point.

Escalation Rule

If a redline response above doesn't resolve the issue after one round, that's the signal to loop in your own legal/deal-desk directly rather than keep negotiating contract language yourself — cheat sheets get first-pass movement, not final terms.