When a customer sues your counterparty over a product you both touched, who writes the check? That question is the entire point of an indemnification clause, and it is one of the most expensive clauses to get wrong. Minnesota law gives contracting parties broad freedom to allocate risk, but with firm statutory and common-law limits that every CEO should understand before signing. This article walks through how indemnification clauses actually work in Minnesota contracts, the carve-outs that matter, and the construction-specific rule at Minn. Stat. § 337.02 that voids common boilerplate. For broader context on Minnesota contract issues, see our contracts practice area overview.
What does an indemnification clause actually do?
An indemnification clause is a risk-shifting agreement: one party (the indemnitor) agrees to cover specified losses, claims, or expenses that the other party (the indemnitee) suffers. The clause allocates who pays when something goes wrong, independent of who is technically at fault. In my practice, the sticking point is almost never whether the clause applies; it is what scope of claims, whose conduct, and on what terms.
Three things a well-drafted indemnity accomplishes. First, it shifts the cost of defined risks from one party to the other. Second, it often brings insurance coverage with it (the indemnitor’s insurer ends up on the hook). Third, it sets the procedural rules: who controls the defense, when notice has to be given, and what happens if notice is late. Minnesota courts enforce indemnity clauses as written between sophisticated parties, but they read ambiguous language narrowly. An indemnity that protects you only from third-party claims will not cover a direct dispute between you and your counterparty unless the text says so.
Does Minnesota law limit what I can shift by contract?
Yes, and in two distinct ways. Outside of construction, Minnesota follows the general common-law rule: competent businesses can allocate risk by contract, including the risk of one party’s own negligence, so long as the language is clear and unambiguous. A clause shifting liability for your counterparty’s negligence must say so expressly; courts will not infer it from general “any and all claims” language.
Inside building and construction contracts, the rule is statutory and much stricter. Minn. Stat. § 337.02 declares that an indemnification agreement “contained in, or executed in connection with, a building and construction contract is unenforceable except to the extent that” the injury traces to the negligent or wrongful act or omission, including breach of a specific contractual duty, of the promisor or the promisor’s independent contractors, agents, employees, or delegatees, or fits a narrow environmental exception. In plain terms: you cannot use a construction contract to shift liability for the indemnitee’s own negligence. A boilerplate broad-form indemnity that would work in a supply contract is unenforceable to the prohibited extent if the contract qualifies as a building and construction contract.
The threshold question is therefore scope: is this contract a “building and construction contract” as Minnesota defines it? Section 337.01, subdivision 2 answers that it means a contract “for the design, construction, alteration, improvement, repair or maintenance of real property, highways, roads or bridges,” and excludes contracts for maintaining machinery used in manufacturing or utility production. Misread that threshold and you can draft an unenforceable clause without realizing it.
What is the difference between direct claims and third-party claims?
Most commercial indemnity clauses cover third-party claims: a customer, regulator, or bystander sues one of the contracting parties, and the indemnity reallocates the cost. Direct-claim indemnity is rarer and materially different. It says that if the indemnitor causes the indemnitee a loss directly (for example, by breaching a representation), the indemnitee can recover under the indemnity rather than suing for breach of contract.
The practical difference: third-party indemnity usually kicks in when a complaint or demand arrives from outside. Direct indemnity operates as an internal claims procedure between the parties, often with its own notice requirements, caps, and exclusions. If you agree to direct-claim indemnity, you may be giving up or altering breach-of-contract remedies you would otherwise have. Read the definition of “Claim” or “Losses” carefully; if it says “whether brought by a third party or by a Party to this Agreement,” you have both. If it says “third-party Claims,” you have one. Our article on breach of confidence vs. breach of contract theories explains related choice-of-remedy issues.
What exclusions and special categories should the parties address?
Three different drafting moves get conflated under “carve-outs.” Each matters, but they do different work: (a) true exclusions from the indemnity grant itself, (b) separate indemnity buckets such as IP that usually live in their own clause with their own caps and procedures, and (c) exceptions from caps or limitations of liability for categories like fraud or willful misconduct, where the recovery itself is preserved but the cap does not apply.
The commonly addressed categories in Minnesota commercial contracts:
| Category | Typical treatment | Why it matters |
|---|---|---|
| Indemnitee’s own negligence | Exclusion from indemnity (default Minnesota rule already requires express language to shift; carve-out clarifies) | Removes ambiguity about whether broad language reaches indemnitee fault |
| Gross negligence | Often excluded from indemnity or, at minimum, excepted from caps | Public policy and enforceability concerns |
| Willful or intentional misconduct | Often excluded from indemnity entirely; indemnity for intentional wrongdoing may be unenforceable | Public policy limits, especially for intentional misconduct |
| Fraud | Usually preserved as a recoverable claim but excepted from caps/limitations | Caps that swallow fraud recovery raise enforceability concerns |
| IP infringement | Almost always a separate indemnity clause, not an exclusion | Different risk profile, different caps, different control-of-defense rules |
| Consequential or punitive damages | Exclusion from the definition of recoverable Losses | Without exclusion, exposure can far exceed the deal value |
| Caps and baskets | Floor or ceiling on indemnity dollars | Containment tools; see the caps question below |
The practical effect of mishandling these categories can be dramatic. An indemnity that expressly covers the indemnitee’s intentional or willful misconduct creates serious enforceability and public-policy problems and should be addressed directly. Our deeper look at this problem is in carve-outs in indemnification clauses that invite exposure.
Do I have to provide a defense, or just pay after the judgment?
These are two different obligations, and Minnesota courts generally treat them as distinct absent contractual language merging them. A duty to indemnify is a payment obligation: after liability is established, the indemnitor reimburses the indemnitee. A duty to defend is a service obligation: from the moment a covered claim lands, the indemnitor pays counsel and manages the litigation.
Minnesota treats them distinctly. If your clause says only “indemnify and hold harmless,” a court is unlikely to read in a free-standing duty to defend. If you want both, the clause should say “defend, indemnify, and hold harmless” and then spell out which side controls counsel selection, who has settlement authority, and how conflicts between the parties are handled. In my experience, the defense-control fight is where indemnity disputes get bitter: the indemnitor is writing the checks but the indemnitee’s reputation is on the line, and neither side wants to lose the steering wheel.
What insurance should back up an indemnification clause?
The standard package in a sophisticated commercial contract requires the indemnitor to carry commercial general liability insurance, name the indemnitee as an additional insured, include a waiver of subrogation in the indemnitee’s favor, and maintain specified minimum limits. In construction, add workers’ compensation and builder’s risk where appropriate. The indemnitee usually wants a certificate of insurance before work starts.
Construction contracts face another statutory layer. Minn. Stat. § 337.05, subd. 1(a) expressly preserves agreements “whereby a promisor agrees to provide specific insurance coverage for the benefit of others.” But paragraph (b) voids any provision that “requires a party to provide insurance coverage to one or more other parties, including third parties, for the negligence or intentional acts or omissions of any of those other parties, including third parties.” That distinction is the whole ballgame in construction insurance drafting. You can require the subcontractor to insure the subcontractor’s own work. You cannot require the subcontractor to insure the general contractor against the general contractor’s own fault. A clause that crosses that line is void and unenforceable on its face.
How do caps, baskets, and survival periods work?
Sophisticated contracts rarely leave indemnity obligations uncapped. Three structural tools contain exposure:
Caps set a ceiling on total indemnity liability. Often the cap equals the purchase price or the contract value, sometimes a percentage. Above the cap, the indemnitor owes nothing.
Baskets set a floor. A “tipping basket” means if cumulative losses exceed the basket threshold, the indemnitor pays from dollar one; a “deductible basket” means the indemnitor pays only amounts above the threshold. Tipping baskets favor the indemnitee; deductible baskets favor the indemnitor.
Survival periods determine how long the indemnity obligation lasts after closing or contract expiration. Different categories of representations often get different survival windows: fundamental reps (ownership, authority) frequently survive for a long negotiated window or without a stated cutoff; general business reps survive for a shorter negotiated period; tax and environmental reps usually survive longer. The survival period is negotiated, but it must be read together with applicable statutes of limitation, statutes of repose, and any limits on shortening or extending claim periods.
The interaction matters. A generous indemnity with a short survival period, tight notice requirement, and low cap can be functionally narrow. A modest-looking indemnity with long survival, lenient notice, and a high cap can be broad. Read all four together. For related drafting considerations on fee allocation, see allocation of legal fees in multi-party claims.
Can I recover attorney fees through an indemnification clause?
In Minnesota, the default American Rule is that each party bears its own attorney fees absent a contract or statute that says otherwise. Indemnification clauses frequently provide that override: they define “Losses” to include reasonable attorney fees, expert costs, and other defense expenses. That fee-shifting is enforceable in Minnesota between commercial parties as long as the language is clear.
Two drafting details determine how this plays in practice. First, does the definition of “Losses” or “Damages” explicitly list attorney fees? If not, an argument exists that general damages language does not reach fees. Second, are fees recoverable only in defending third-party claims, or also in enforcing the indemnity itself (fees-on-fees)? Most drafters intend the former but not the latter; silence on the second point produces litigation. Our article on legal triggers for withholding payment in B2B contracts covers related leverage questions.
What procedure must the indemnitee follow to trigger indemnity?
Indemnification clauses typically impose three procedural conditions: prompt written notice of the claim, cooperation in the defense, and some limit on settling without the indemnitor’s consent. Courts often decline to forfeit indemnity for a minor notice lapse unless the delay prejudiced the defense, which is why well-drafted clauses spell out the forfeiture consequences expressly.
In practice, the notice provision does a lot of work. A 10-day notice requirement with an express “time is of the essence” clause, a mandatory delivery method (certified mail or a specific email address), and a forfeiture consequence can convert a minor scheduling slip into a loss of coverage. The indemnitor-control-of-defense provision is where most real fights happen: who selects counsel, whether the indemnitee can retain its own counsel at the indemnitor’s expense when conflicts arise, and who holds settlement authority. My recurring observation is that well-drafted control provisions are rare; most contracts borrow boilerplate that gives the indemnitor sole control, which works poorly when the indemnitee’s brand is at risk.
How do UCC Article 2 defaults apply when contracts involve goods?
For contracts involving the sale of goods, Minnesota’s Uniform Commercial Code (“UCC”) Article 2 supplies default warranty and indemnity-adjacent rules that layer on top of any express indemnification clause. Implied warranties of merchantability and fitness for a particular purpose can give a buyer a remedy independent of the indemnity provision. Sellers can disclaim those warranties, but only with conspicuous language and, for merchantability, by mentioning the word “merchantability” or using a recognized disclaimer phrase.
The practical point: an express indemnity and the UCC’s warranty regime are not substitutes for each other. A goods contract can have an express indemnity for third-party claims and, at the same time, implied warranties that give the buyer direct remedies against the seller. If the contract’s integration and exclusive-remedy clauses are sloppy, the buyer can end up with both tracks, and the seller with unexpected exposure. Drafting both layers together is the fix. Our piece on integration clauses that override side letter terms explains how integration language interacts with other remedy tracks.
Are broad-form indemnity clauses ever enforceable between businesses?
Outside construction, yes, if the language is clear and unambiguous and the parties are sophisticated. Minnesota courts allow businesses to shift risk by contract, including the risk of the indemnitee’s own negligence, but only when the text expressly says so. Boilerplate ‘any and all claims’ language is usually read narrowly and will not be stretched to cover the indemnitee’s own fault. Inside building and construction contracts, broad-form indemnity is unenforceable to the extent it requires indemnity for the indemnitee’s own fault, subject to the statute’s limited exceptions under Minn. Stat. § 337.02.
Can I indemnify someone for their own negligence in Minnesota?
Outside construction, yes, if the contract says so in clear, unambiguous terms. Minnesota courts require express language; ambiguity is read against the drafter. Inside building and construction contracts, Minn. Stat. § 337.02 voids indemnity for the indemnitee’s own fault with only two narrow exceptions, including a specific environmental carve-out.
How do IP indemnities differ from general indemnification?
IP indemnities are usually pulled out of the general indemnification clause and given their own section with separate caps, exclusions, and control-of-defense rules. The typical reason: IP exposure (patent, trademark, copyright infringement claims) has a very different risk profile than ordinary tort claims and often carries higher or uncapped limits. Treating IP in its own clause lets each side negotiate those specific terms without distorting the general indemnity.
Who pays defense costs if the indemnitor's insurer denies coverage?
The indemnitor still owes whatever the indemnity clause promises, independent of insurance. If the clause requires defense and the insurer walks away, the indemnitor has to fund defense out of its own pocket or negotiate a new arrangement. Well-drafted clauses anticipate this by making the indemnity obligation separate from the insurance obligation, so a coverage denial does not gut the contractual promise. Insurance is a backstop, not a substitute.
Do indemnification clauses cover direct claims between the parties?
Sometimes, depending on wording. Most indemnity clauses cover third-party claims by default. Language extending indemnity to direct claims between the contracting parties is less common and changes the risk picture. Read the clause carefully to see whether ‘claims’ is limited to third-party actions or reaches inter-party disputes.
Does a certificate of insurance prove the indemnitor actually has coverage?
No. A certificate of insurance is a summary document issued by the broker; it is not the policy and does not create coverage. It can be out of date, list stale limits, or describe endorsements that were never actually issued. For any indemnity worth relying on, ask for the actual additional-insured endorsement and the waiver-of-subrogation endorsement, not just the certificate. In construction, confirm the endorsements fit within the Minn. Stat. § 337.05 limits.
A practical read before signing
Indemnification clauses do not look dangerous on a first read. They look technical, and most business owners skim them. The expensive surprises come from what is left out: a missing gross-negligence carve-out, a silent duty-to-defend, a cap that sounds generous until the basket provision cancels half of it, or a construction-contract clause that was valid in the template but void under Minn. Stat. § 337.02. Before signing, read the indemnity, the insurance provision, the limitation of liability, and the definitions section together, because they interact. For broader context on how contract terms fit together in Minnesota deals, see our contracts practice area overview.
If you would like a second set of eyes on an indemnity clause in a specific contract, email [email protected] with a short description of the deal. Do not send confidential information until an attorney-client relationship is confirmed and conflicts are cleared.
