Indemnification Clauses in Minnesota Contracts

What does an indemnification clause actually do?

An indemnification clause (also called an indemnity clause or indemnification provision) 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. A simple example: you hire a contractor to remodel your office, and the contractor’s work floods the tenant below. An indemnification clause in your contract can require the contractor to cover that loss, including the cost of defending the lawsuit the downstairs tenant files against you. The key drafting questions are which claims the clause covers, whose conduct triggers it, 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.

What do “indemnify,” “defend,” and “hold harmless” mean in a contract?

Most clauses stack three verbs, and you should read each one separately.

Indemnify (pay for losses). In law, to indemnify means to reimburse someone for a loss. The Minnesota Supreme Court has adopted the dictionary definition: to “indemnify” means “[t]o reimburse (another) for a loss suffered because of a third party’s or one’s own act or default,” “[t]o promise to reimburse (another) for such a loss,” and “[t]o give (another) security against such a loss.” DeWitt v. London Rd. Rental Ctr., Inc., 910 N.W.2d 412, 416 n.5 (Minn. 2018) (quoting Black’s Law Dictionary). If the clause says “Party A shall indemnify Party B,” Party A pays Party B’s covered damages, settlements, and judgments.

Defend (pay for and run the lawsuit). A duty to defend means you pay for the other side’s lawyers and litigation costs, and often control that defense, from the time a covered claim arrives, whether or not the claim has merit. For many businesses it is the most expensive of the three, because defense bills accrue long before anyone knows who was at fault. The next sections explain how Minnesota treats a clause that promises to defend and one that does not.

Hold harmless (absorb the risk). “Hold harmless” means you absorb the loss so the other party suffers none. Is there a difference between hold harmless and indemnify? In the Minnesota decisions discussed in this article, the words “hold harmless” did not create a separate or broader duty. In Yang, the Minnesota Supreme Court analyzed a promise “to defend and save . . . harmless” and a promise to “indemnify and hold harmless” together as the agreement’s “two indemnification clauses.” 701 N.W.2d at 791. In DeWitt, a clause promising to “INDEMNIFY, DEFEND AND HOLD HARMLESS” received the same strict-construction test as any other indemnity, and it failed that test. 910 N.W.2d at 418-19. Minnesota’s construction statute likewise treats all three verbs as one kind of promise: an “indemnification agreement” is “an agreement by the promisor to indemnify, defend, or hold harmless the promisee.” Minn. Stat. § 337.01, subd. 3. The practical lesson: do not count on “hold harmless” to add anything a court will enforce. State each obligation you intend in its own words.

One-way vs. mutual indemnification: what is fair?

One of the first things to check in any indemnification clause is whether the obligation runs in one direction or both.

One-Way Indemnification

In a one-way (one-sided) clause, only one party takes on the obligation; the other gets protection without giving any. A one-way clause makes sense when one party clearly controls the risk: a subcontractor working on your premises, or a vendor handling your customer data. Placing the risk on the party that controls it is a fair allocation.

Push back when a counterparty insists that you indemnify it but refuses to reciprocate for risks it controls. That imbalance usually means the other side is moving its own operational risk onto your company. One-sided clauses are common when one party has far more leverage, such as a large corporation contracting with a small vendor. If you accept one, know exactly what risks you are taking on and whether the deal is worth that exposure.

Mutual Indemnification

In a mutual clause, each party indemnifies the other for losses caused by its own acts, negligence, or breach of the contract. Mutual indemnification ties responsibility to fault, so each side pays for its own mistakes. For most arm’s-length business contracts between parties of comparable bargaining power (vendor agreements, service contracts, partnership arrangements), a mutual, fault-based clause is the usual starting point, and it is the structure I suggest proposing first.

What triggers the obligation? The “arising out of” trap

The trigger language decides which losses the clause covers, and it matters as much as the word “indemnify.” A promise to cover losses “arising out of or related to this Agreement” ties your obligation to a connection with the deal, not to your fault. That wording can pull in losses caused by a third party, by no one, or by circumstances you had nothing to do with. A promise limited to losses “caused by” your negligence or breach ties your obligation to your own conduct.

Minnesota’s strict-construction rule (explained below) limits how far broad trigger language reaches when the indemnitee seeks coverage for its own negligence; the Minnesota Supreme Court has treated “arise out of or result from performance of the WORK by CONTRACTOR” as limiting language that made an otherwise broad clause equivocal. DeWitt, 910 N.W.2d at 417 (describing National Hydro). That rule protects you only as to the other side’s own negligence. For every other loss, the trigger words control.

Negotiate for fault-based triggers: “caused by,” “resulting from the negligent acts or omissions of,” or “attributable to the breach by” the indemnifying party. Acceptable triggers usually include breach of the contract, negligent or willful acts, violation of law, and breach of representations and warranties. Be cautious of “arising out of or related to” with no fault limitation.

Does Minnesota law limit what I can shift by contract?

Yes, and in two distinct ways: a strict-construction rule that applies to every contract, and a construction statute that applies to building and construction contracts.

The Strict Construction Rule

Indemnity agreements are enforceable in Minnesota, but a clause that shifts liability for the indemnitee’s own negligence is strictly construed. 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 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).

The current controlling statement is DeWitt v. London Rd. Rental Ctr., Inc., 910 N.W.2d 412 (Minn. 2018). The court rejected the idea that a clause can qualify because it is “so broad” that it necessarily includes the indemnitee’s negligence and stated the test: “whether the clause includes specific language that expressly shows, in clear and unequivocal language, that the parties intended the clause to obligate the indemnitor to indemnify the indemnitee for the indemnitee’s own negligence.” Id. at 417. Such a provision “need not include the word ’negligence,’ but it must use specific, express language that ‘clearly and unequivocally’ states the contracting parties’ intent” for the indemnitor to cover the indemnitee’s own negligence. Id.

The same standard now reaches release (exculpatory) clauses. In Justice v. Marvel, LLC, 979 N.W.2d 894 (Minn. 2022), the court held “that both indemnity clauses and exculpatory clauses are subject to the same standard of strict construction,” and it held a waiver of “any and all claims” unenforceable against a negligence claim because “the waiver does not specifically provide that it releases Marvel from liability for its own negligent acts.” The court also explained that no particular words are required: a party “who wishes to limit their liability for negligence” must do so “by using specific, express language that clearly and unequivocally states such an intent; no certain words are required to satisfy this standard.”

What this means for you: if someone asks you to sign a broad clause, Minnesota courts will ask whether its words specifically reach the other side’s own negligence. If you want that protection in your own contracts, say it expressly. Note the line the rule draws: a broadly worded clause can still shift liability for someone else’s negligence; in Farmington the contracts did “permit Fischer to be indemnified if it were held liable for Hilite’s negligence,” though not for its own. 281 N.W.2d at 842.

Commercial Contracts: Greater Flexibility

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 an exculpatory clause, both prongs of the test are examined”: (1) whether there was a disparity of bargaining power, meaning a compulsion to sign a contract with an unacceptable provision and no ability to negotiate it out, and (2) the types of services offered, “taking into consideration whether it is a public or essential service.” 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.

The Minnesota Supreme Court applied these indemnity rules outside construction in Yang v. Voyagaire Houseboats, Inc., 701 N.W.2d 783 (Minn. 2005), a houseboat rental. Treating the rental company as an innkeeper providing a public service, the court held that indemnification clauses requiring the renter to indemnify the company for the company’s own negligence “violate public policy and are unenforceable.” Id. at 792. Even in commercial contracts, then, the clause must clearly and specifically address the risk being transferred, and it must not offend public policy.

Anti-Indemnity in Construction

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, id., subd. 4. Misread that threshold and you can draft an unenforceable clause without realizing it. If your business is in construction, review your existing subcontractor and vendor agreements against this statute.

How do courts read an ambiguous indemnity clause? The contra proferentem rule

Contra proferentem is the rule that ambiguous contract language is construed against the party who drafted it. Minnesota recognizes it, but between businesses of similar sophistication it is a last resort. In Staffing Specifix, Inc. v. Tempworks Mgmt. Servs., Inc., 913 N.W.2d 687 (Minn. 2018), the Minnesota Supreme Court explained that “[i]n cases involving parties of relatively equal sophistication and bargaining power, we have always treated contra proferentem as a supporting-not deciding-rationale.” Id. at 693. The court has “applied the rule of contra proferentem only after an attempt is made to determine the parties’ intent behind an ambiguous term, using extrinsic evidence if available,” and “[o]nly if a preponderance of the evidence does not prove the parties’ intent should the jury construe ambiguous terms against the drafter.” Id. at 694. Whether the terms are ambiguous in the first place is a question for the court. Id. at 692.

Two consequences follow for indemnity clauses. First, do not count on the drafter-loses rule to rescue you from a clause you signed: the court will look at the negotiation history and other evidence of intent first. Second, a clause that tries to shift the indemnitee’s own negligence never gets that far. Strict construction does not wait for a finding of ambiguity: “ambiguity cannot be the trigger for strict construction because an ambiguous provision, by definition, cannot also ‘clearly and unequivocally’ state[ ] the contracting parties’ intent.” Justice v. Marvel, LLC, 979 N.W.2d 894 (Minn. 2022). The cleanest protection is language precise enough that neither rule comes into play.

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 (first-party) indemnity is rarer and materially different. It says that if the indemnitor causes the indemnitee a loss directly (for example, by breaching a representation or delivering defective products that damage your equipment), 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
Confidentiality and data breaches	Often a separate cap or uncapped	Breach costs can be large and hard to predict
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 held indemnification clauses (not only exculpatory clauses) void on public-policy grounds. Yang v. Voyagaire Houseboats, Inc., 701 N.W.2d 783, 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). Parties may still validly limit liability for ordinary negligence, so the carve-outs worth fighting for are the intentional tier. 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.

Tendering does not help when the claim falls outside the clause. In Farmington, the Minnesota Supreme Court recognized that “an indemnitee may recover attorneys fees where the action is found to be within the hold harmless provision of the contract,” but because the subcontractor “was not contractually obligated to indemnify Fischer for Fischer’s own negligence,” its “refusal to accept the tendered defense does not render it liable for attorneys fees.” Farmington Plumbing & Heating Co. v. Fischer Sand & Aggregate, Inc., 281 N.W.2d 838, 842 (Minn. 1979). If you are the indemnitee and the clause does not expressly cover your own negligence, expect to fund your own defense.

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, how defense costs count against any cap, 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. If you are the one agreeing to defend, ask for control of the defense, because a party spending your money with no accountability can run up costs quickly. If someone else is defending you, keep the right to approve any settlement that imposes obligations on your company beyond a payment.

What insurance should back up an indemnification clause?

An indemnification promise is only as good as the indemnitor’s ability to pay. A small vendor that agrees to unlimited indemnity but has few assets and no insurance gives you little real protection. That is why indemnity provisions usually come paired with an insurance-requirements clause, sometimes called an insurance backstop clause: a covenant requiring the indemnitor to buy and keep specified insurance that supports its indemnity promise. Insurance is a contract with a third party (the insurer); indemnity is a promise between the contracting parties. You want the two aligned.

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. Professional liability or cyber coverage is added where the work calls for it. In construction, add workers’ compensation and builder’s risk where appropriate. The indemnitee usually wants a certificate of insurance before work starts. Coordinate the indemnity cap with the policy limits, so that insurable risks run through insurance rather than through open-ended indemnity exposure.

Do not assume your own insurance covers an indemnity you give. Many liability policies treat liability you assume by contract differently from liability imposed by law. Before you agree to indemnify anyone, have your broker read the clause against your policy’s contractual-liability provisions and confirm the obligation is covered.

Common Clause Phrases

When you read an insurance-requirements clause tied to an indemnity, these phrases do most of the work:

• “Primary and non-contributory.” The indemnitor’s policy responds first for the additional insured, and it does not seek contribution from the indemnitee’s own insurance.
• “Excess of underlying insurance.” A policy or limit that pays only after the underlying (primary) coverage is used up.
• “Subject to the limits of insurance coverage.” Language that may tie the indemnity itself to the policy limits; read it closely, because it can quietly cap the indemnity at whatever insurance pays.
• “Notwithstanding any other provision.” Signals that the insurance or indemnity term overrides conflicting terms elsewhere, such as a limitation-of-liability clause.
• “Maximum aggregate liability.” The total cap across all claims, as opposed to a per-claim limit.
• “Additional insured” and “waiver of subrogation.” The endorsements that let the indemnitee claim directly under the indemnitor’s policy and keep the insurer from suing the indemnitee after it pays.

Make sure the clause also says the indemnity obligation is independent of the insurance, so that a denied claim or an exhausted policy does not erase the indemnitor’s promise.

Key Insurance Terms That Affect Indemnity

• Primary coverage pays first, up to its limit, regardless of other insurance.
• Excess coverage (including umbrella policies) pays only after the primary limits are exhausted.
• Self-insured retention (SIR) is an amount the insured must pay itself, typically including defense costs, before the policy begins to respond. A large SIR means the indemnitor’s own cash, not its insurer, funds the first part of any claim against you.
• Deductible is an amount subtracted from what the insurer pays. Policies differ on whether the insurer pays first and seeks reimbursement or the insured pays first, so read the policy.

For the indemnitee, a high SIR or deductible on the indemnitor’s policy is a credit question: can the indemnitor actually pay that first layer?

Construction Insurance Requirements Under Minn. Stat. § 337.05

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 since a 2013 amendment (2013 Minn. Laws ch. 88, § 1), that preservation has been expressly subject to 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 2013 amendment also kept several common arrangements out of the voiding rule, and a 2023 amendment (2023 Minn. Laws ch. 53, art. 7, § 5) narrowed the project-specific insurance exception to claims arising from the promisor’s own negligence or that of its contractors, agents, employees, or delegatees. Paragraphs (c) through (e) now 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 “shall have indemnification from the promisor to the same extent as the specified insurance.” Minn. Stat. § 337.05, subd. 2. That remedy “is not available if” the specified insurance “was not reasonably available in the market” and the promisor “so informed the other party to the agreement to insure before signing the agreement, or signed the agreement subject to a written exception as to the nonavailable insurance.” Id., subd. 3. 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. Id., subd. 5.

How Insurance Requirements Differ Across Industries

The insurance package tracks the industry’s risks. Construction contracts focus on bodily injury, property damage, and third-party claims, under the section 337.05 limits above. Technology and data agreements add cyber and technology errors-and-omissions coverage for data breaches and service failures. Healthcare and professional-services agreements add professional liability (malpractice) coverage. Match the required policies to the claims the indemnity actually covers.

Can Insurance Requirements Affect Premium Costs?

Yes, and the indemnitor pays. Every requirement you add (higher limits, additional-insured endorsements, primary and non-contributory wording, waivers of subrogation, a separate cyber or professional policy) can add an endorsement charge or raise the premium, because it widens what the insurer may pay. A narrower, fault-based indemnity paired with ordinary limits generally costs less to insure than a broad one. If you are the indemnitor, ask your broker what each requirement costs before you agree, and price it into the deal. If you are the indemnitee, expect a counterparty to push back on requirements that cost more than the risk justifies.

How do caps, baskets, and survival periods work?

Sophisticated contracts rarely leave indemnity obligations uncapped. An indemnity without a dollar cap is an unlimited liability exposure. Three structural tools contain it:

Caps set a ceiling on total indemnity liability. Often the cap equals the purchase price, the fees paid, or the contract value, sometimes a multiple or a percentage; some contracts tie it to insurance limits. Different categories can carry different caps, for example a general cap with a higher or no cap for IP infringement or confidentiality breaches. 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, except that “where a warranty explicitly extends to future performance of the goods and discovery of the breach must await the time of such performance the cause of action accrues when the breach is or should have been discovered,” id., subsection (2). Those limits do not apply to goods “incorporated into an improvement to real property, except equipment and machinery,” which are “subject only to the statute of limitations set forth in section 541.051.” Id., subsection (4).

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, and match the structure to the deal: a $5,000 software subscription and a $500,000 construction contract call for very different caps and carve-outs. For related drafting considerations on fee allocation, see allocation of legal fees in multi-party claims.

How does indemnification connect to your other contract terms?

An indemnity clause never works alone. Read it together with these provisions:

• Limitation of liability. This clause caps total exposure. Make the cap and the indemnity work together: a contract that caps liability at $50,000 but leaves the indemnity uncapped invites a fight over which controls. Say expressly whether the indemnity sits inside or outside the cap.
• Insurance requirements. The required policies should cover the same kinds of claims the indemnity covers, at limits that match the cap.
• Representations and warranties. Breach of a representation is a common indemnity trigger, so what you represent determines part of what you indemnify.
• Termination and survival. Indemnity obligations usually survive termination. Know how long, and prefer a defined survival period over an open-ended one.
• Definitions. The definitions of “Claims,” “Losses,” and “Indemnified Parties” often decide more than the indemnity paragraph does.

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 for the indemnitee’s own negligence 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? Silence does not drop defense fees: under Seifert, fees spent defending a covered claim are presumed included “unless the agreement explicitly states otherwise,” 505 N.W.2d at 86. Listing them still removes the argument. Fees spent establishing the right to indemnity are different: the same court held the indemnitees could not recover them, though they may be recoverable “if the agreement . . . explicitly states so.” Id. 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. Insurance law takes a similar approach to a late proof of loss: absent express language making the failure to timely submit it “fatal to the rights of the insured, an insurer must show it was prejudiced to avoid its liability under policy.” Nathe Bros., Inc. v. American Nat’l Fire Ins. Co., 615 N.W.2d 341, 347 (Minn. 2000). Under the Standard Fire Insurance Policy’s 60-day proof-of-loss provision, a prejudiced insurer “may seek to limit its liability to the extent of its prejudice.” 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. If you are the indemnitee, negotiate a workable notice period, practical delivery (email should suffice), and language that late notice matters only to the extent it actually prejudiced the indemnitor. 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. Unless excluded or modified, a warranty of merchantability is implied in a contract for the sale of goods “if the seller is a merchant with respect to goods of that kind.” Minn. Stat. § 336.2-314, subsection (1). A warranty of fitness for a particular purpose is implied when “the seller at the time of contracting has reason to know any particular purpose for which the goods are required and that the buyer is relying on the seller’s skill or judgment to select or furnish suitable goods.” Minn. Stat. § 336.2-315. Either warranty 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). Subsection (3) supplies three routes that apply notwithstanding those formalities: “unless the circumstances indicate otherwise,” expressions like “as is” or “with all faults” exclude all implied warranties; 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; and an implied warranty “can also be excluded or modified by course of dealing or course of performance or usage of trade.” 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.

Which law governs, and are indemnity and insurance clauses enforceable internationally?

The rules in this article are Minnesota law. Other states and other countries treat indemnity, exculpatory, and insurance-requirement clauses differently, and a clause valid here may be limited or void where you need to enforce it. Whether a clause is enforceable abroad depends on the law that governs the contract and on the courts where you would have to sue or collect.

Put a governing-law clause and a forum clause in every cross-border contract. For transactions under Minnesota’s Uniform Commercial Code, such as a sale of goods, “when a transaction bears a reasonable relation to this state and also to another state or nation the parties may agree that the law either of this state or of such other state or nation shall govern their rights and duties.” Minn. Stat. § 336.1-301, subsection (a). Choosing a governing law does not settle how a foreign court will treat the clause, so when the counterparty or its assets are overseas, have counsel licensed in that country review the indemnity and insurance terms before you rely on them.

How are indemnity payments treated for tax purposes?

The tax treatment depends on what the payment is for, and you should confirm it with your CPA before you price an indemnity. The federal starting point allows a deduction for “all the ordinary and necessary expenses paid or incurred during the taxable year in carrying on any trade or business.” 26 U.S.C. § 162, subsection (a). Not every indemnity payment fits. No deduction is allowed for capital expenditures, such as amounts paid “for permanent improvements or betterments made to increase the value of any property or estate,” 26 U.S.C. § 263, subsection (a)(1), and a separate rule generally bars deducting amounts paid to a government “in relation to the violation of any law,” subject to exceptions such as restitution, 26 U.S.C. § 162, subsection (f). An indemnity payment in a business sale, a payment that reimburses a fine, and a payment covering a customer’s injury claim can land in different places. Insurance premiums you pay to meet an insurance requirement, and the timing of any deduction, are also questions for your tax preparer. Build the after-tax cost into the price you negotiate.

Negotiation Strategies for Business Owners

When an indemnification clause lands on your desk, work through these questions in order:

1. Is it mutual? Start from mutual obligations: propose that each party indemnifies the other for losses caused by its own breach, negligence, or misconduct. If the clause is one-sided against you, ask why. If the other side resists reciprocity, it may be trying to avoid accountability for its own conduct.
2. What triggers it? Negotiate specific, fault-based triggers (“caused by,” “resulting from the negligent acts of”). Vague triggers create disputes; specific ones create clarity.
3. Is there a cap? Tie the cap to the contract value, the fees paid, or your insurance limits, and resist uncapped obligations unless the risk clearly justifies it.
4. What is carved out? Check exclusions for consequential damages, the indemnitee’s own negligence, and the separate treatment of IP, confidentiality, and willful misconduct.
5. What are the notice requirements? Insist on a reasonable notice period and late-notice language tied to actual prejudice.
6. Who controls the defense? State whether there is a duty to defend, who controls it, who approves settlements, and how defense costs count against the cap.
7. Does insurance back it up? Align the required policies with the indemnity, and confirm your own policy covers the indemnity you give.
8. Is there a claims process? Spell out how claims are submitted, evaluated, and resolved, so a stressful situation does not become a procedural fight.

Red flags that deserve an immediate push back: uncapped one-sided indemnity; a requirement that you cover the other party’s own negligence; a definition of “Losses” that includes lost profits and speculative damages without limit; no offset for the indemnitee’s own insurance recovery, which can let it collect twice; and silence about who pays for the defense.

When should you bring in counsel?

Not every contract needs a lawyer’s review of the indemnity clause. Bring in counsel when:

• the contract is high-value, or the exposure is large relative to your business;
• the indemnification language is non-standard or unfamiliar to you;
• the clause is one-sided and the other party refuses to negotiate;
• it is a construction contract subject to Minnesota’s anti-indemnity statute, Minn. Stat. § 337.02; or
• the contract involves your intellectual property, customer data, or regulatory compliance.

For a routine, low-dollar contract on familiar terms, reading the indemnity, insurance, and limitation-of-liability sections together yourself, with your insurance broker checking coverage, may be enough.

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 aaron@aaronhall.com with a short description of the deal. Do not send confidential information until an attorney-client relationship is confirmed and conflicts are cleared.