OSERAN HAHN
Attorneys at Law
← Insights
Insight

Indemnification vs. liability caps vs. warranties: a contract's risk-allocation clauses

Indemnification, liability caps, and warranties look like boilerplate. They are where a contract decides who pays when the deal goes wrong, and they only make sense read together.

▍ Key takeaways

A vendor sends over its standard agreement, and the business owner skims to the price, the term, and the signature line. The three clauses that will actually decide who pays if the deal goes wrong, the indemnification, the limitation of liability, and the warranties, sit in the middle, written in the kind of language that invites skimming. They look like boilerplate. They are the opposite of boilerplate. They are where the contract quietly assigns risk, usually to whichever side did not read them.

These three clauses do different jobs, and they only make sense read together. An indemnity that looks generous can be worth almost nothing if a liability cap two pages later swallows it. A warranty means little if the disclaimer beneath it is drafted to take the promise back. Before signing anything, it pays to understand what each clause does and how they interact.

What an indemnification clause does

An indemnification clause shifts the cost of certain claims from one party to the other. In the usual form, one party agrees to cover the other’s losses, including defense costs, when a third party brings a claim arising from the first party’s acts. A customer buying software wants the vendor to indemnify it if the software infringes someone else’s patent. The vendor wants that indemnity narrowed to claims it can actually control.

Two things decide what an indemnity is really worth. The first is scope: which claims are covered, whether it reaches the indemnitor’s negligence or only third-party suits, and whether the language is a sweeping “any and all claims” or something bounded. The second is defense and control: who hires the lawyers, who decides whether to settle, and who pays as the bills come in rather than after a judgment. A one-way indemnity that runs only against you, with no reciprocal obligation, is the most common one-sided term hiding in a standard form.

Indemnification vs. limitation of liability

A limitation-of-liability clause does something different. It caps the total dollars one party can owe the other, often at the fees paid under the contract, and usually excludes consequential damages, the lost profits and downstream losses that dwarf the direct ones. Where indemnification answers “who pays for a third party’s claim,” the liability cap answers “how much can I ever owe you at all.”

The two clauses collide, and that collision is where the negotiation actually happens. A vendor will offer a broad indemnity in one section and then, in another, cap its total liability at the value of the contract. Read together, the generous indemnity is only ever worth the cap. The fix is a carve-out: indemnification obligations, along with breaches of confidentiality and similar core promises, are excluded from the cap so they survive at full value. Whether the indemnity sits inside or outside the cap is often the single most important number in the contract, and it is rarely obvious from reading either clause alone.

Warranties, and the disclaimer that takes them back

A warranty is a promise that goods or services will meet a defined standard. Express warranties are the ones the contract spells out. Implied warranties arrive by operation of law, and in a sale of goods, Washington’s Uniform Commercial Code supplies them automatically: a warranty of merchantability that the goods are fit for ordinary use, and, when the seller knows the buyer’s particular purpose, a warranty of fitness for that purpose.

Those implied warranties apply unless the seller disclaims them, and the disclaimer only works if it is done right. A warranty section is usually followed by a disclaimer, frequently in capital letters, that strikes the implied warranties and sells the goods “as is.” That capital-letter styling is not decoration; the UCC requires a disclaimer to be conspicuous, and one buried in ordinary type can fail to disclaim anything at all. For a buyer, the warranty is only as strong as the disclaimer is weak.

Here is how the three clauses line up against one another.

Risk-allocation clauses

Indemnification, liability caps, or warranties, side by side

Three contract clauses that allocate risk in different directions. What each does, who it protects, and where the negotiation usually lands.

DimensionIndemnificationLimitation of liabilityWarranties
What it doesShifts third-party claim costs to the other partyCaps the dollars one party can owe the otherPromises goods or services meet a standard
Who it protectsThe indemnified party (often the customer)The party exposed to large damages (often the vendor)The buyer or customer
What triggers itA third-party claim from the other’s actsAny breach, once damages exceed the capThe product or service failing to conform
Where it’s negotiatedScope of covered claims; who controls the defenseThe cap amount and its carve-outsExpress vs. implied; the disclaimer
Without itCommon law applies; each bears its own claimsLiability for all foreseeable damagesUCC implied warranties apply by default
Watch forBroad “any and all claims” language; one-way indemnitiesA cap that quietly swallows the indemnityDisclaimers buried in fine print; “as is” sales

Under Washington’s UCC (RCW 62A.2), implied warranties of merchantability and fitness apply to the sale of goods unless they are effectively and conspicuously disclaimed.

Where Washington law overrides the contract

Some of these clauses do not get the last word, because Washington statute does. Three limits come up often enough to plan around.

Indemnification has a hard limit in construction. Under RCW 4.24.115, a clause in a construction contract that purports to indemnify a party against its own sole negligence is void, and even a clause covering concurrent negligence only reaches the indemnitor’s share. A broad-form indemnity copied from a national template will not hold up on a Washington project.

Warranty disclaimers run through the UCC. To strike the implied warranties of merchantability and fitness (RCW 62A.2-314 and RCW 62A.2-315), the disclaimer has to satisfy the conspicuousness and language rules in RCW 62A.2-316. A disclaimer that misses those requirements leaves the implied warranties in force, whatever the seller intended.

Liability caps have limits too. Under RCW 62A.2-719, a contract can limit or exclude consequential damages, but not where doing so is unconscionable, and a limited remedy that fails of its essential purpose can fall away entirely. One more Washington rule catches owners by surprise: under RCW 4.84.330, a one-sided attorney-fee clause is read as mutual, so a fee provision a company thought protected it can be turned against it by the side that wins.

Reading the three as a set

The mistake is treating these clauses as separate boilerplate sections rather than one risk-allocation system. They interact in ways that only show up when you read them together.

Which language you want depends on which side of the deal you sit. The party with leverage and the party absorbing the exposure never want the same words, and a clause that protects a vendor selling to many customers reads very differently when you are the customer.

How to choose what to push on

You cannot renegotiate every clause in every contract, so the question is where to spend the leverage you have.

Frequently asked questions

What is an indemnification clause?

An indemnification clause is a contract provision where one party agrees to cover the other’s losses, including legal defense costs, usually for third-party claims arising from the first party’s acts or products. It shifts the cost of those claims from the party that would otherwise bear them to the party that agreed to indemnify.

What is the difference between indemnification and a limitation of liability?

Indemnification shifts the cost of specific claims, typically third-party claims, from one party to the other. A limitation of liability caps the total amount a party can owe and often excludes consequential damages. One assigns who pays for a category of loss; the other sets a ceiling on how much can be owed at all.

Can a liability cap limit an indemnification obligation?

Yes, and that is the trap. If the contract caps total liability and does not carve indemnification out of the cap, a broad indemnity is only ever worth the capped amount. Negotiated contracts usually exclude indemnity obligations, and breaches of confidentiality, from the liability cap so they survive at full value.

What is the difference between an express and an implied warranty?

An express warranty is a promise the contract states directly. An implied warranty is supplied by law: in a Washington sale of goods, the UCC implies a warranty of merchantability and, where the seller knows the buyer’s purpose, a warranty of fitness for that purpose. Implied warranties apply automatically unless the seller disclaims them conspicuously.

Does Washington limit indemnification clauses?

Yes, in places. In construction contracts, RCW 4.24.115 voids an indemnity for a party’s own sole negligence. Implied-warranty disclaimers must meet the UCC’s conspicuousness rules to be effective, consequential-damage exclusions cannot be unconscionable, and one-sided attorney-fee clauses are read as mutual under RCW 4.84.330.

Indemnity, liability, and warranty clauses are where a contract decides who pays, and they are easiest to fix before anyone signs. Our contract attorneys in Bellevue and Seattle read these clauses the way the other side’s lawyer will. Talk to us before you sign, not after the claim arrives.

Paul Spencer

Paul Spencer is a Shareholder at Oseran Hahn with thirty-five years of experience in complex civil litigation for closely held companies and the people who run them.

His practice covers complex commercial litigation, real estate litigation, labor and employment, TEDRA trust-and-estate disputes, and personal-injury litigation. The matters get unusual: high-rise building defects, complex road designs, the development of floor-coating formulas, even a batch of “bad fish” processed and shipped to Europe. Over the years he has litigated in Washington, Oregon, Alaska, California, Nevada, and North Dakota, in both state and federal court.

Born and raised in the Seattle area, Paul has practiced in Washington since 1990. He began as an associate and then partner at McInerney·Baker, where he tried his first cases, and in April 2001 he opened Spencer Law Offices, PLLC, which he led for more than a decade before joining Oseran Hahn as a Shareholder. He is a member of the Washington State Bar, the King County Bar Association, and the Washington State Association for Justice.

Paul holds a B.A. from the University of Washington (1986) and graduated with honors from the University of Puget Sound School of Law (1989). Outside the office he skis, hikes, boats, and watches football, and he stays active in the community coaching youth sports and serving on nonprofit management teams.

Need counsel like this? Talk to a partner.

Contact us →
Keep reading

More from Insights.