Read this as a checklist, not an essay. Each clause below has a one-line job: tell you what the vendor wants the default to be, what that default costs you, and the change to ask for. Across 500+ engagements since 2019, the deals that held their value were not the ones with the deepest day-one discount. They were the ones where these clauses were fixed before signature. The discount erodes; the terms compound.
This library tells you what to look for. When you need the proposed redline language and the leverage to land it, our contract negotiation service runs the redlines for you on fixed fee or gainshare.
Which price and uplift clauses matter most?
These eight clauses decide whether your day-one number survives the contract. The most common buyer mistake is to negotiate the discount hard and leave the uplift open, which gives back the saving inside two cycles.
| Clause | What it costs you if wrong | Buyer-side counter |
|---|---|---|
| 1. Price hold | Rate moves mid-term on a re-quote or product re-pack | Freeze the unit rate for the full term. Detail in price-hold and rate-card clauses |
| 2. Uplift cap | Open-ended renewal increases of 7 to 15 percent or more | Cap the annual uplift in writing. See price protection and uplift caps |
| 3. Rate card | Add-ons priced at list when you expand | Lock per-unit add-on rates for the term, not just the base |
| 4. Most favored customer | You pay more than comparable accounts of your size | Benchmark and request parity. See benchmarking and MFC clauses |
| 5. Volume band | A small seat increase trips you into a higher price tier | Negotiate the band boundary and step rate. See volume-band and tier-migration clauses |
| 6. Ramp and phasing | Paying full volume from day one for seats you onboard later | Phase the spend to the rollout. See ramp and phasing clauses |
| 7. Currency and tax | FX swings and pass-through taxes inflate the invoice | Fix the billing currency and clarify who carries tax changes |
| 8. True Forward / catch-up | Overage trued up at list with no credit for under-use | Cap the catch-up and align it to the anniversary, not mid-term |
Do this next: pull your current order form and check whether clauses 2 and 8 exist at all. If the uplift is silent, it is uncapped, and that is the single highest-value redline in most ITSM contracts.
Which term, renewal and exit clauses protect you?
Term clauses decide whether you control the renewal clock or the vendor does. The notice window is the one buyers miss most: blow past it and the contract auto-renews at the vendor's number with no negotiation.
| Clause | What it costs you if wrong | Buyer-side counter |
|---|---|---|
| 9. Initial term | A long lock-in at a rate you cannot revisit | Match the term to your planning horizon, not the vendor's quota year |
| 10. Renewal notice window | Auto-renewal at list because you missed the deadline | Widen the window and set internal alerts. See renewal notice and non-renewal windows |
| 11. Auto-renewal | Silent rollover removes your negotiation leverage | Require active renewal, or cap the auto-renew rate |
| 12. Termination for convenience | No exit without cause locks you in for the full term | Negotiate a convenience exit with notice. See termination for convenience |
| 13. Co-termination | Staggered end dates weaken every individual renewal | Align dates to one anniversary. See co-termination clauses |
| 14. Assignment / change of control | Your rate or rights change if either party is acquired | Protect terms through M&A. See assignment and change-of-control clauses |
| 15. Exit and data return | Hostage data and a costly extraction at the end | Fix format, timeline and cost. See exit, transition and data-return clauses |
| 16. Transition assistance | No vendor help when you move off the platform | Bind the vendor to a costed transition period |
| 17. Renewal pricing method | Renewal priced off list, not your held rate | State that renewal starts from the current paid rate plus the capped uplift |
| 18. Non-renewal effect | Service cut-off before you have migrated | Secure a wind-down period and read-only access window |
Do this next: put the renewal notice date for every ITSM contract on a shared calendar with a reminder 30 days before the window opens. A missed window is the cheapest mistake to prevent and the most expensive to make.
Which usage and audit clauses decide your bill?
Usage definitions are where vendors quietly grow a contract. If the agreement does not pin down what counts as a billable user, the vendor's interpretation wins, and it will favour the broader count.
| Clause | What it costs you if wrong | Buyer-side counter |
|---|---|---|
| 19. Usage / user definition | Light users and viewers billed as full agents | Define each user class precisely. See usage definition clauses |
| 20. Named vs concurrent | Paying per named seat for occasional users | Use concurrent where usage is intermittent |
| 21. Audit rights | Broad audit scope and short response windows | Limit scope and notice. See audit and true-up clauses |
| 22. True-up procedure | Overage billed retroactively at list with penalties | Set a defined true-up cadence and rate, no penalty multiplier |
| 23. Overage rate | Excess usage priced far above your contract rate | Hold overage to the contract unit rate |
| 24. AI / consumption metering | Metered AI assists or tokens that overrun with no cap | Cap consumption and price overage. See our guide to agentic AI ITSM pricing |
| 25. Down-scaling rights | Seats can only go up, never down, at renewal | Secure the right to reduce counts at each renewal |
| 26. Shelfware reclamation | Paying for modules and seats nobody uses | Reconcile and drop unused entitlement. See shelfware reclamation |
| 27. Reporting access | No usage data to defend your counts | Require admin-level usage reporting in the contract |
Do this next: ask the vendor for a written definition of a billable user and compare it to your actual roles. Misclassified requesters and viewers are the most common source of overspend we find.
Which service and continuity clauses are worth fighting for?
SLA and continuity clauses turn vendor promises into remedies you can enforce. A service credit you cannot trigger is marketing, not protection.
| Clause | What it costs you if wrong | Buyer-side counter |
|---|---|---|
| 28. Uptime commitment | A vague availability target with no teeth | Set a measured target and method. See uptime and availability commitments |
| 29. Service credits | Credits too small or too hard to claim to matter | Make credits automatic and meaningful. See service credit and SLA remedy clauses |
| 30. Support response SLA | Slow priority response with no escalation path | Define response and resolution targets by severity |
| 31. Maintenance windows | Downtime during your business hours, excluded from SLA | Agree windows in your off-peak and count the rest |
| 32. Force majeure | Broad excuses that suspend the vendor's obligations | Narrow the scope. See force majeure and continuity clauses |
| 33. Roadmap / deprecation | A feature you bought for is sunset mid-term | Require notice and a substitute or credit on deprecation |
| 34. Business continuity / DR | No recovery commitment if the vendor has an outage | Bind RPO and RTO targets into the agreement |
Do this next: test one service-credit clause against a real recent outage on paper. If you could not have claimed, the clause needs rewriting before you sign.
Which risk, liability and data clauses cap your exposure?
These six clauses decide who carries the loss when something goes wrong. The liability cap is the one most often left at the vendor's standard, and the standard is written for the vendor.
| Clause | What it costs you if wrong | Buyer-side counter |
|---|---|---|
| 35. Limitation of liability | Cap set at fees paid, leaving you exposed on a breach | Raise the cap for data and IP events. See indemnity and liability caps |
| 36. Indemnification | You carry third-party IP and breach claims the vendor caused | Get vendor indemnity for IP, breach and confidentiality |
| 37. Data processing | Unclear handling of your data and obligations | Attach a DPA. See data processing and sub-processor clauses |
| 38. Sub-processors | Data passed to fourth parties without notice | Require a sub-processor list and change notice |
| 39. Confidentiality | Your pricing and usage disclosed or used as a reference | Mutual confidentiality, no reference use without consent |
| 40. Security and breach notice | Slow or vague breach notification | Set a notification clock and minimum security standard |
How do you actually get these clauses changed?
Vague asks get refused. Named clauses with proposed language get negotiated. Work in priority order: cap the uplift and pin the usage definition first, because those protect the most money over the life of the deal. Then secure the renewal window and exit terms so the next cycle is yours to run. Leave the lower-stakes language for the final pass so you are not trading hard currency on items that do not move the number.
Leverage is what turns a redline into an accepted edit. A vendor agrees to a capped uplift when it believes the deal is contestable, which is why a benchmarked rate and a credible alternative sit behind every clause you win. The cross-platform discipline behind this sits in our guide to ITSM renewal negotiation, and the term-by-term mechanics are detailed in our white paper, the ITSM contract terms and True Forward guide.
The gated contract terms and True Forward guide includes the redline language and the clause-priority worksheet behind this library.
Why do the defaults always favour the vendor?
Because the vendor wrote them. An order form and a master agreement are drafted by the vendor's legal team to protect the vendor's revenue and limit the vendor's risk, and the buyer is handed the result as though it were a fixed market standard. It is not. Every uncapped uplift, every narrow notice window, every broad usage definition is a choice the vendor made and can unmake when the deal is contestable. The reason these defaults survive is not that they are reasonable; it is that most buyers do not read them clause by clause or do not bring proposed language to change them.
Look at the pattern across the five groups. The price clauses leave future increases open. The term clauses put the renewal clock in the vendor's hand. The usage clauses leave the billable-user definition vague. The service clauses promise availability without an enforceable remedy. The risk clauses cap the vendor's exposure at the very events where your loss could be largest. None of this is accidental, and none of it is hostile; it is simply one party drafting in its own interest and the other party signing without redlining. Your job is to redline.
Which clauses do you hold, and which do you trade?
Not every clause is worth the same fight, and a negotiation that treats all 40 as equally important wastes leverage on language that does not move money or risk. Sort them into three tiers before you open the conversation.
Tier one: hold these every time
The uplift cap (clause 2), the usage definition (clause 19), the renewal notice window (clause 10), and the exit and data-return terms (clause 15). These four protect the largest share of the deal's value over its life. The uplift cap stops the discount eroding, the usage definition stops the bill growing through reclassification, the notice window keeps the renewal yours to run, and the exit terms keep your data from becoming a hostage. Concede these and you have won a price and lost the contract.
Tier two: push hard, settle if you must
The liability cap and indemnities (clauses 35 and 36), the audit and true-up procedure (clauses 21 and 22), the service credits (clause 29), and the down-scaling rights (clause 25). These matter, sometimes a great deal, but they are situational: the liability carve-outs matter most where your data exposure is large, the audit terms most where your usage is hard to count, and the down-scaling rights most where your headcount is volatile. Push for the buyer-side position, and trade the weakest of them last if the vendor needs a concession to close.
Tier three: useful, but trade freely
Currency and tax (clause 7), maintenance windows (clause 31), force majeure scope (clause 32), and confidentiality reference use (clause 39). Worth asking for, rarely worth a delay in signing.
Frequently asked questions
- Which ITSM contract clauses matter most to a buyer?
- The clauses that control future cost and exit, not the ones that control today's price. The uplift cap, the renewal notice window, the usage definition that decides what counts as a billable user, the audit and true-up rights, and the exit and data-return terms do more to protect a deal over its life than the headline discount.
- What is the difference between a price-hold clause and an uplift cap?
- A price-hold clause freezes the unit rate or rate card for a fixed window, usually the contract term. An uplift cap limits how much that rate can rise at renewal, expressed as a percentage ceiling. You want both: the hold protects the current term, the cap protects the next one.
- Can you negotiate clauses on a standard vendor paper contract?
- Yes. Order forms and master agreements are templates, not statutes. Most vendors will accept buyer redlines on renewal caps, notice windows, true-up procedure and exit assistance when the deal is contestable and the requests are specific. Vague asks get refused; named clauses with proposed language get negotiated.
Explore the full Clause Library series
Know the clauses. Win the redlines.
We run the redlines and the leverage that gets these terms accepted. Fixed fee or gainshare.
Book a contract review →