An insured contract is a contract type that a liability policy agrees to treat as covered for certain assumed tort liability obligations. It matters because liability policies often exclude contractual liability in general, then carve back coverage for specifically defined insured contracts.
In plain language, the policy usually does not cover every promise the insured makes in a contract. Instead, it covers only the contractual assumptions that fit the policy’s insured-contract definition.
Why the definition matters
Commercial agreements often require one party to indemnify another for bodily injury or property damage claims. Without an insured-contract exception, those indemnity promises could fall outside ordinary liability coverage because the insured assumed liability by contract.
The definition therefore becomes a key risk-transfer tool in leases, service agreements, construction work, easements, and similar business relationships. It also creates coverage disputes when the parties assume the policy covers a contract that does not actually fit the definition.
Coverage mechanics
The exact wording matters. Many liability forms focus on assumed tort liability of another party, not every contractual obligation the insured may owe. Pure breach-of-contract damages, performance guarantees, or broad commercial promises may still sit outside coverage.
That is why insured-contract analysis is usually tied to indemnity language, the liability form, additional-insured requirements, and the specific allegations in the claim.
Practical example
A contractor signs an agreement promising to indemnify a property owner for certain bodily-injury claims arising from the contractor’s work. If a worker is injured and the owner seeks indemnity, the policy may respond only if that promise fits the insured-contract definition and no other exclusion removes coverage.