10 Ideas about Indemnification Procedures: Practice Points

Define what actually triggers the duty to give notice. Emily said ambiguity cuts against both parties here, and she wanted specificity even though vagueness sometimes helped her side. A trigger written as "becoming aware of a claim" gives us no idea whose awareness counts. Emily pointed out that she could argue the cashier at the grocery store knew about the claim. Name a role or a level in the business, or name the document that starts the clock.

Say what the notice has to contain. A requirement to notify "in writing" without any content standard leaves the indemnifying party unable to evaluate coverage and leaves the indemnified party guessing at compliance. Emily wanted the who, what, when, where, why, and how, plus the complaint or demand letter attached. An open standard like "all material facts then known" sounds thorough and delivers nothing. Put a concrete list in the provision, or in a schedule the provision points to.

Watch for notice triggers that reach facts rather than claims. Brian flagged the prong requiring notice on awareness of any facts that could reasonably give rise to a claim. In a product or IP dispute, those facts are design decisions, sourcing decisions, and engineering choices made years before anyone filed anything. Read literally, that language creates a notice obligation long before a claim exists. A court might refuse that reading, but we should not leave wording in the contract that invites it.

Tie the consequences of late notice to real prejudice. Brian noted that a plaintiff has ninety days to serve under the federal rules, and docket monitoring tools tell you about a filing within minutes. He has waited out service on cases that simply went away. A ten business day clock running from awareness can force both parties to spin up over a case that never arrives. Brian sees the notice condition kept in, with the failure relieving the indemnifying party only where it actually prejudiced them, and Laura liked "to the extent" language over the cliff of either being on the hook or off it.

Remember that a judge gets to decide whether your out is fair. Emily gave the litigator's view that trial judges have wide discretion and think hard about fairness, and that judges who believe a party should be indemnified will often find a way. Drafting a one business day forfeiture feels like the upper hand. Laura's experience is that what we actually buy is uncertainty about whether a judge will enforce it, plus a defense we probably have to keep funding while we find out. Emily's advice was to pick a period you can defend as reasonable so you can show a court you were not just looking for a way out.

Check that your indemnity notice lines up with the rest of the contract. Brian made the point that we draft this clause in isolation while a general notices provision elsewhere sets the actual delivery mechanics. Look at who is named there, because it is often a procurement contact, a sales contact, or a shared inbox that nobody routes to legal. Laura requires delivery to the business role AND to legal, and she names a role rather than a person so the address survives that person leaving the company.

Think about who your counterparty would actually hire. Brian was comfortable giving the indemnifying party sole control of the defense, because that is the quid pro quo of the indemnity and it avoids the too many cooks in the kitchen problem. Counsel selection is where he gets particular, and the answer depends entirely on who you are contracting with. A small software vendor facing a bet the house patent case may hire the lawyer who handled a copyright matter for them once, because that is who they know. Push for a reasonably acceptable standard, or attach a list of approved outside counsel to the contract.

Make the cooperation obligation something you could enforce. A clause telling the indemnified party to cooperate fully and take no inconsistent action reads fine and means very little. Emily wanted to know which witnesses, which documents, and how many days she has to respond to a request. She also wanted a deadline for the indemnifying party to actually assume the defense, because a missed answer deadline produces a default judgment and, potentially, ethics and malpractice exposure. Move the detail into a schedule if the provision is getting crowded.

Expect a reservation of rights even when the contract never mentions one. Brian described it as arguing in the alternative, where the indemnifying party defends now and reserves the right to deny the obligation at the end. Emily was blunt about the odds. "If your indemnification provision doesn't have reservation of rights, you shouldn't be surprised when you get one anyway," she said. It can be useful in the right facts, like a claim implicating components from several vendors where nobody can be given sole control. Broad language letting them reserve on anything undercuts the exchange we bargained for.

Scale your settlement consent rights to what can be settled. Brian treats this as a sliding scale. Where the indemnifying party can settle only for money, with a full release, no admission of liability, and no publicity, he may not need a consent right at all. Peel back those limits so they can admit fault, make a public statement, or agree to change your product, and you need much broader consent. He also caught the asymmetry in the sample clause, where the indemnified party had to be reasonable in withholding consent but the indemnifying party's cap triggered on any withholding at all.