3 Risks of Signing a Broad Form Indemnity Clause Without Reading It

Why This Clause Deserves More Attention Than It Usually Gets

Indemnity language often sits buried in the middle of a subcontract, wedged between insurance requirements and payment terms, written in the kind of dense legal phrasing that invites skimming. Broad form indemnity is exactly the clause that shouldn't get skimmed — it can be the single most consequential paragraph in the entire contract, for both the general contractor relying on it and the subcontractor signing it.

Risk One: Agreeing to Cover Someone Else's Negligence

The defining feature of broad form indemnity is that it can require a subcontractor to cover losses "regardless of whether caused in part by the negligence of Contractor" — meaning the sub could end up financially responsible for a claim that was substantially, even entirely, the general contractor's fault. For a subcontractor evaluating whether to sign, this is worth stopping on: it's not indemnifying against your own mistakes, it's potentially indemnifying against someone else's, on a jobsite you don't fully control. See Types of Indemnity Clauses for how this compares to intermediate and limited form language.

Risk Two: It May Not Even Be Enforceable

Here's the twist that catches a lot of GCs off guard: broad form indemnity is restricted or outright void in a meaningful number of states, through anti-indemnity statutes specifically designed to prevent one party from being forced to cover another party's own negligence. A GC relying on broad form language in a state where it's unenforceable isn't actually protected by that clause — they just don't find out until they try to use it, often during litigation, which is the worst possible time to discover a contract provision doesn't do what it says.

Risk Three: It Complicates the Insurance Behind It

Some subcontractor liability policies specifically exclude or limit coverage for "contractual liability" that goes beyond what the subcontractor would owe under general negligence law — meaning a sub's insurer might not actually cover a broad form indemnity obligation, even if the sub signed it. This creates a scenario where the contract says one thing and the available insurance says another, and the gap lands on whoever's counting on that indemnity clause to actually pay out. This is exactly why indemnity language and insurance requirements need to be reviewed as one connected system — see Subcontractor Insurance Requirements.

Risk Four: It Can Sour the Subcontractor Relationship

Subcontractors who understand what broad form indemnity actually asks for tend to push back on it — reasonably. A GC who insists on broad form language purely out of habit, rather than a deliberate risk decision, may be creating unnecessary friction with subs, or losing bids to competitors using more balanced intermediate form language, without gaining meaningfully more protection if the clause isn't even enforceable in their state.

Risk Five: It Can Mask a Bigger Problem — Underinsurance

There's a subtler risk that shows up when a GC leans hard on broad form indemnity language: it can create a false sense of security that substitutes for actually verifying the subcontractor's insurance. The thinking goes something like, "our contract makes them responsible for everything, so we're covered." But a contract clause has never paid a claim by itself — only an actual, funded insurance policy does that. A GC who leans on aggressive contract language instead of verifying real coverage (see Subcontractor Insurance Requirements and Certificate of Insurance Tracking) is trading a false sense of protection for the harder, less glamorous work of actually confirming coverage exists and stays current.

A Practical Example

Picture two subcontractors bidding the same scope of work. Subcontractor A carries strong general liability coverage, agrees to intermediate form indemnity, and maintains current additional insured and waiver of subrogation endorsements. Subcontractor B is thinly insured, but signs whatever broad form language is put in front of them without objection. On paper, Subcontractor B's contract looks like it offers more protection — broader language, no pushback. In practice, if a serious claim hits, Subcontractor A's coverage is what actually pays; Subcontractor B's aggressive contract promise may be functionally worthless if there's no insurance behind it. The lesson: the strength of the contract language matters far less than most GCs assume if it isn't paired with verified insurance capacity to back it up.

What to Do Instead of Signing (or Requiring) It on Autopilot

If you're a subcontractor being asked to sign broad form indemnity language, it's worth having your own attorney confirm whether it's enforceable in your state before you agree to it. If you're a GC whose standard subcontract template defaults to broad form language, it's worth confirming that's a deliberate choice appropriate to your state and risk tolerance, not just what an old template happened to include. In many states, intermediate form language — which still protects against the much more common shared-negligence scenario — is both more defensible and easier to get subcontractors to accept.

General information only — not legal advice. Whether broad form indemnity is enforceable, and what alternative language makes sense, depends entirely on your state's law and your specific contract. This is a conversation for a licensed construction attorney, not a general guide.

Not sure whether your current subcontract's indemnity language is even the right form for your state — or whether your subs' insurance would actually back it up if it came to a claim? [Request a Risk-Transfer Review](/risk-review/) or call 844-967-5247.