Now Advisory · Buyer side guide · 2026 edition
ServiceNow indemnification clause: a buyer side analysis
A buyer side analysis of the ServiceNow indemnification clause: how the clause allocates legal risk between the parties, where the drafting tilts toward the vendor, and the redline guidance that restores a balanced position.
Section 01Why the ServiceNow indemnification clause deserves a buyer side review
A ServiceNow indemnification clause sets out which party covers the other for defined third party claims, most commonly intellectual property infringement, and on what conditions and limits. Read carelessly, it gives the buyer a narrow vendor indemnity hedged with exclusions while imposing a broad buyer indemnity in return, so the risk allocation tilts the wrong way. This clause analysis sets out how the indemnity works, where the drafting favours the vendor, and the redline guidance that balances it, with benchmark data from real enterprise renewals.
We are independent advisors with no vendor partnership and nothing to resell, so the analysis is buyer side and direct. For the wider method start with our pillar on ServiceNow contract terms, and where the clause needs a full read against your paper, our ServiceNow contract review service does that line by line. Indemnity language is legal as well as commercial, so final contract language should be reviewed by counsel. The guidance here is commercial advisory, not legal advice.
Section 02How the clause works
An indemnification clause allocates the cost of defending and settling certain third party claims. The vendor typically indemnifies the buyer against claims that the licensed platform infringes a third party intellectual property right, while the buyer often indemnifies the vendor against claims arising from the buyer data, configurations, or misuse of the service.
The clause defines the scope of each indemnity, the conditions for claiming it, the remedies available, and how it interacts with the overall liability cap. A vendor intellectual property indemnity usually comes with a set of self help remedies, such as procuring a licence, modifying the service, or refunding fees, which determine what the buyer actually receives if a claim succeeds.
The mechanism is standard, since each party is best placed to manage the risks it controls. The risk for the buyer is in the asymmetry and the exclusions, where the vendor indemnity is narrowed by carve outs while the buyer indemnity is drawn broadly, and where the remedy on offer is weaker than the exposure it is meant to cover.
Section 03Where the risk sits
The first risk is a narrow vendor indemnity. Common carve outs exclude claims arising from combinations with other software, from buyer modifications, or from use outside documentation, and a broad reading of these can hollow out the protection in exactly the integrated environment every enterprise runs. The second is a broad buyer indemnity, where the buyer agrees to cover the vendor for an open ended range of claims tied to data and use.
The third risk is the remedy. An intellectual property indemnity whose ultimate remedy is termination and a pro rata refund leaves the buyer to absorb the cost of switching platforms, which dwarfs the refund. The fourth is the cap interaction, where the indemnity is subjected to the general liability cap, so a large infringement claim is limited to a number set for ordinary contract damages.
Together these defaults shift legal risk toward the buyer while presenting the clause as mutual. The vendor indemnity reads as protection but is narrowed by exclusions and weakened by remedies and caps, while the buyer indemnity is wider than the risk the buyer can realistically control.
Section 04ServiceNow indemnification clause analysis: reading the language
Read the clause for the exclusions to the vendor indemnity. Carve outs for combinations, modifications, and use outside documentation are the lines to scrutinise first, since a broad version of any of them can exclude the normal integrated use of the platform. Read the buyer indemnity for breadth, and narrow any open ended language tied to data or use to specific, controllable risks.
Read the remedy ladder in the intellectual property indemnity. A clause whose final step is refund and termination should also commit the vendor to defend and to pay damages and costs, not merely to hand back fees. Read for the obligation to procure continued use rights, since the buyer needs the platform to keep running, not a cheque after it stops.
Finally, read the indemnity against the liability cap. An infringement indemnity that is squeezed under the general cap is not real protection for a serious claim, so look for the indemnity to sit outside the cap or under a separate, higher cap. The cap interaction often matters more than the indemnity wording itself.
Section 05Redline guidance
Narrow the carve outs to the vendor indemnity so they exclude only genuine buyer fault, not ordinary integrated use, and resist exclusions that would void the indemnity for any combination with other software. Balance the buyer indemnity so it is reciprocal in structure and limited to risks the buyer actually controls, such as the buyer own data and unlawful use.
Strengthen the remedy so the vendor commits to defend the claim, to pay resulting damages and costs, and to procure the right for the buyer to keep using the platform, with refund and termination as a last resort rather than the primary remedy. This keeps the business running, which is the point of the indemnity.
Lift the indemnity out of the general liability cap, or place it under a separate higher cap, so a serious infringement claim is not limited to a number set for ordinary damages. Run these redlines with counsel inside the wider negotiation so the legal and commercial trade offs stay visible. A related allocation sits in our analysis of the ServiceNow assignment clause, and the exit side in the ServiceNow audit clause analysis. Final contract language should be reviewed by counsel.
Section 06The clause under the 2026 commercial model
The 2026 model replaced the five legacy tiers, Standard, Pro, Pro Plus, Enterprise and Enterprise Plus, with Foundation, Advanced and Prime, and bundled AI across all of them with metered assists. That introduces a new indemnity question, because generative and agentic AI features raise the prospect of claims tied to AI output as well as to the platform itself.
Read the indemnity for how it treats AI generated output. A clause that indemnifies the platform but is silent on, or excludes, claims arising from bundled AI features leaves a gap exactly where a new category of risk now sits. Where the vendor markets AI capability as part of every tier, the indemnity should follow that capability rather than stopping at the traditional platform boundary.
Settle the clause before any 2026 migration so the indemnity scope matches the AI features you will actually use under the new tiers. The consumption side of those features is covered in our analysis of the ServiceNow audit clause, which interacts with how usage is measured and challenged.
Section 07Common drafting variations to watch
Indemnity clauses come in two common shapes. A mutual indemnity gives each party a defined indemnity within its own area of control, while a one sided structure gives the vendor a narrow indemnity and the buyer a broad one. Push the drafting toward genuine mutuality, where each party covers the risks it is best placed to manage.
Watch the conditions attached to claiming the indemnity. A clause that requires immediate notice, sole vendor control of the defence, and full buyer cooperation, with any lapse voiding the indemnity, can make the protection hard to actually invoke. Negotiate reasonable notice, a say in any settlement that affects the buyer, and a cure for minor procedural lapses.
Check how the indemnity treats third party and open source components embedded in the platform. An indemnity that excludes third party code can exclude a large part of what the buyer actually relies on. Require the vendor indemnity to cover the platform as delivered, including its embedded components, rather than only the vendor own code.
Finally, read the indemnity against the warranty and liability sections, since the three together set the real risk position. An indemnity that looks strong can be undercut by a narrow warranty or a low cap elsewhere, so review them as one package rather than clause by clause. See the related ServiceNow audit clause analysis for an adjacent risk provision.
Section 08Folding the clause into the renewal runway
The clause review belongs at the start of the renewal runway and should run with counsel from the outset, since the indemnity is as much a legal provision as a commercial one. Four quarters out, read the indemnity, the carve outs and the cap interaction. Two quarters out, draft the redlines and decide which are dealbreakers, particularly the remedy ladder and the cap. One quarter out, negotiate the clause inside the main renewal.
Held this way, the indemnity stops being boilerplate that no one revisits and becomes a balanced allocation of real risk. An independent advisor who has reviewed this clause across hundreds of enterprise agreements, working alongside your counsel, shortens the work, because the pattern of where the language favours the vendor is already known.
The aim is one renewal where the indemnity allocates risk fairly by design, not by luck. To pressure test your specific language and the renewal behind it, book a renewal assessment call with our advisory team. Final contract language should be reviewed by counsel.
FAQFrequently asked questions
What is a ServiceNow indemnification clause?
It is the provision that allocates the cost of defending and settling defined third party claims between the parties, most commonly intellectual property infringement. The vendor typically indemnifies the buyer for platform infringement while the buyer indemnifies the vendor for its data and use, and the balance depends on the exclusions, remedies and cap, which is why it should be reviewed with counsel rather than accepted as written. Final contract language should be reviewed by counsel.
Where does an indemnification clause cost buyers the most?
In the carve outs that narrow the vendor indemnity, the breadth of the buyer indemnity, a remedy ladder that ends in refund and termination rather than keeping the platform running, and an indemnity squeezed under the general liability cap so a serious claim is limited to ordinary damages.
How do you balance an indemnification clause?
Narrow the carve outs to genuine buyer fault, make the buyer indemnity reciprocal and limited to controllable risks, require the vendor to defend, pay damages and procure continued use rights, and lift the indemnity out of the general cap or place it under a separate higher cap.
Should counsel review the indemnification clause?
Yes. Indemnity language is legal as well as commercial, so the clause should always be reviewed by counsel. Our role is the buyer side commercial analysis and negotiation strategy that sits alongside that legal review.