Indemnification Clauses in Minnesota Contracts

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 give effect to a clearly drafted indemnity clause according to its terms, but they strictly construe indemnity language and will not read it to shift a party’s own negligence onto another unless that intent is expressed in clear and unequivocal terms. See Yang v. Voyagaire Houseboats, Inc., 701 N.W.2d 783, 791 (Minn. 2005). Clear drafting is not the end of the inquiry: a Minnesota court “will not enforce an indemnification clause if it is contrary to public policy,” id., so even an unambiguous clause can fail on public-policy grounds. And an indemnity that protects you only from third-party claims will not cover a direct dispute between you and your counterparty unless the contract makes that intention unmistakably clear. See Hooper Assocs., Ltd. v. AGS Computers, Inc., 74 N.Y.2d 487, 548 N.E.2d 903 (1989). Hooper is out-of-state authority that Minnesota courts have not formally adopted, but it states a widely followed default: a general indemnity clause reaches only third-party claims unless the contract clearly says otherwise.

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 that competent parties may, without violating public policy, allocate risk by contract, including the risk of one party’s own negligence, so long as the language is clear and unambiguous, because “the public interest in freedom of contract is preserved by recognizing such clauses as valid.” Schlobohm v. Spa Petite, Inc., 326 N.W.2d 920, 922-23 (Minn. 1982). That freedom has limits even when the words are clear. A clause “exonerating a party from liability will be strictly construed against the benefited party,” and one that “purports to release the benefited party from liability for intentional, willful or wanton acts . . . will not be enforced,” so a waiver or indemnity can shift only ordinary negligence, never intentional wrongdoing. Id. at 923. A court also screens for public policy before enforcing such a clause, weighing whether one side was compelled to accept a non-negotiable term through unequal bargaining power and whether the service at issue is a public or essential one. Id. A take-it-or-leave-it clause imposed through unequal bargaining power, or one covering an essential service, may therefore be unenforceable despite clear language.

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. As the Minnesota Supreme Court put it, “[t]here must be an express provision in the contract to indemnify the indemnitee for liability occasioned by its own negligence; such an obligation will not be found by implication.” Farmington Plumbing & Heating Co. v. Fischer Sand & Aggregate, Inc., 281 N.W.2d 838, 842 (Minn. 1979). The Minnesota Supreme Court has reaffirmed that rule and framed the standard as requiring a “clear and unequivocal” expression of intent, holding a broad indemnity clause equivocal as to the indemnitee’s own negligence and declining to read it that far. National Hydro Systems v. M.A. Mortenson Co., 529 N.W.2d 690, 694 (Minn. 1995).

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 otherwise 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 an owner, responsible party, or governmental entity agrees to indemnify a contractor for strict liability under environmental laws. In plain terms: you cannot use a construction contract to shift liability for the indemnitee’s own negligence. The first exception is the one invoked in most construction disputes, because indemnity still stands to the extent the loss is attributable to the promisor’s own fault; the environmental carve-out is narrow. 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 it expressly excludes contracts “for the maintenance or repair of machinery, equipment or other such devices used as part of a manufacturing, converting or other production process, including electric, gas, steam, and telephone utility equipment used for production, transmission, or distribution purposes.” The same section reaches broadly once it applies: it defines an “indemnification agreement” as a promise “to indemnify, defend, or hold harmless” against bodily-injury or property-damage claims, Minn. Stat. § 337.01, subd. 3, and defines the protected “promisee” to include that party’s independent contractors, agents, employees, and indemnitees, Minn. Stat. § 337.01, subd. 4. 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. There is a structural tell, too: language requiring you to notify the other side of a claim and letting them take over the defense only makes sense for third-party claims, because that notice-and-assume-defense machinery has no logical application to a lawsuit between the two of you. That is why an ordinary third-party indemnity does not reach a first-party dispute unless the intent is unmistakably clear. See Hooper Assocs., Ltd. v. AGS Computers, Inc., 74 N.Y.2d 487, 548 N.E.2d 903 (1989). 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. As noted above, Minnesota will not enforce a clause purporting to release a party from “intentional, willful or wanton acts,” and the Minnesota Supreme Court has extended that enforceability framework to indemnification clauses (not only exculpatory clauses), holding them void on public-policy grounds. Yang v. Voyagaire Houseboats, Inc., 701 N.W.2d 783, 787, 791-92 (Minn. 2005). Fraud is usually carved out of any liability cap for the same reason: a limitation that would shield a party from its own fraud collides with the rule against releasing intentional, willful, or wanton conduct. Schlobohm v. Spa Petite, Inc., 326 N.W.2d 920, 923 (Minn. 1982). 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 the answer depends on which kind of promise you are reading. In the insurance context, Minnesota treats the duty to defend as broader than, and separate from, the duty to indemnify: the obligation to defend is triggered by claims that only “arguably fall within the scope of the policy,” while the duty to indemnify turns on liability actually established. Meadowbrook, Inc. v. Tower Ins. Co., 559 N.W.2d 411, 415 (Minn. 1997).

An ordinary contractual “indemnify and hold harmless” clause works differently, and it is a mistake to read it as owing nothing until judgment. The cost of defending an indemnified claim falls within the indemnity promise itself: attorney’s fees incurred defending a covered claim are “included as part of the indemnity obligation implied by law . . . unless the agreement explicitly states otherwise.” Seifert v. Regents of Univ. of Minn., 505 N.W.2d 83, 86 (Minn. Ct. App. 1993). But that obligation is reimbursement, not an insurer-style duty to step in and run the defense from day one, and it does not arise until you act: “[a] tender of defense is a condition precedent to the creation of an obligation to indemnify,” and defense costs you incur before tendering are unrecoverable as a matter of law. Id. at 86-87. So tender promptly.

The drafting lesson follows. If you want a true, up-front duty to defend (the indemnitor selecting counsel and controlling the litigation from the moment a covered claim lands), say so expressly: “defend, indemnify, and hold harmless,” and then spell out who controls counsel selection, who has settlement authority, and how conflicts between the parties are handled. A bare “indemnify and hold harmless” clause presumptively gets you reimbursement of defense costs after tender, not an active defense from the outset. 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), preserves agreements “whereby a promisor agrees to provide specific insurance coverage for the benefit of others.” But a 2023 amendment (2023 Minn. Laws ch. 53, art. 7, § 5) made that preservation expressly subject to a new paragraph (b), which voids as against public policy 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.” Minn. Stat. § 337.05, subd. 1(b). Any older treatment of section 337.05 as an unqualified “agreements to insure are valid” exception is now out of date. 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.

The same amendment kept several common arrangements out of the voiding rule. Paragraphs (c) through (e) provide that paragraph (b) does not reach provisions requiring workers’ compensation insurance, construction performance or payment bonds, builder’s risk policies, owner- or contractor-controlled insurance programs (OCIP/CCIP), or project-specific insurance for claims arising from the promisor’s own negligence; provisions requiring the promisor to insure the promisee’s vicarious or warranty liability arising from the promisor’s acts; or construction work within 50 feet of a railroad. Minn. Stat. § 337.05, subd. 1(c)-(e). So the paragraph (a) / paragraph (b) split is not the whole scheme.

These insurance-procurement covenants have teeth. If the promisor agreed to provide specified insurance, a claim arises within its scope, and the promisor failed to obtain and keep that insurance in force, then regardless of section 337.02 the promisee is entitled to indemnification from the promisor to the same extent as the specified insurance. Minn. Stat. § 337.05, subd. 2. And a certificate does not settle the question: the promisor’s obligation is not waived by the promisee’s failure to demand a certificate of insurance, or by accepting one that varies from the specified coverage. Minn. Stat. § 337.05, subd. 5.

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 operates as a private, contractual claim window that must be read together with the statutory limits on when a claim period can be shortened or extended. For a contract for the sale of goods, for example, the parties “may reduce the period of limitation to not less than one year but may not extend it,” Minn. Stat. § 336.2-725, subsection (1), and the four-year clock starts when the breach occurs (for a warranty, at tender of delivery) regardless of the buyer’s lack of knowledge, unless the warranty explicitly extends to future performance, id., subsection (2).

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: a party cannot shift its fees to its adversary “without a specific contract or statutory authorization.” Kallok v. Medtronic, Inc., 573 N.W.2d 356, 363 (Minn. 1998). (Minnesota also recognizes a third-party litigation exception, allowing a court to award fees as damages when the defendant’s tortious act “thrusts or projects the plaintiff into litigation with a third party,” id., but that is separate from a fee-shifting clause.) Indemnification clauses frequently supply the contractual override: they define “Losses” to include reasonable attorney fees, expert costs, and other defense expenses.

That fee-shifting is enforceable between commercial parties, but the standard is more demanding than ordinary clarity. Minnesota strictly construes an indemnity clause, and to shift fees it must express that intent in “clear and unequivocal” language. A broad clause that even names “attorney fees” can still fail: in DeWitt v. London Rd. Rental Ctr., Inc., 910 N.W.2d 412, 416-17, 419-20 (Minn. 2018), a clause that expressly listed “attorneys’ fees” and swept in “any and all . . . regardless of the cause” was still unenforceable to shift the indemnitee’s own-negligence defense costs, because it did not clearly and unequivocally reach that specific liability.

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 coverage for a minor notice lapse unless the delay caused prejudice, which is why well-drafted clauses spell out the forfeiture consequences expressly. In the insurance setting, Minnesota applies a notice-prejudice rule: absent express policy language making timely submission fatal to the insured’s rights, a late notice or proof of loss does not automatically forfeit coverage, and the insurer must show it was prejudiced by the delay. Nathe Bros., Inc. v. American Nat’l Fire Ins. Co., 615 N.W.2d 341, 347 (Minn. 2000). Even then, the insurer may limit its liability only to the extent of the prejudice shown rather than defeat the claim entirely. Id.

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. The implied warranty of merchantability, Minn. Stat. § 336.2-314, arises by operation of law unless excluded or modified. The implied warranty of fitness for a particular purpose, Minn. Stat. § 336.2-315, arises by operation of law unless excluded or modified and can give a buyer a remedy independent of the indemnity provision. Sellers can disclaim those warranties, but subject to formalities: to disclaim merchantability the language must mention “merchantability” and, if written, be conspicuous, and a fitness disclaimer must be in writing and conspicuous. Minn. Stat. § 336.2-316, subsection (2). Two alternative routes work independently of those formalities: expressions like “as is” or “with all faults” exclude all implied warranties, and a buyer who has examined the goods (or refused to) as fully as desired gets no implied warranty as to defects the examination ought to have revealed. Id., subsection (3).

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.

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.