Back to Glossary
COI VerificationInsurance Basics

Umbrella & Excess Liability Insurance: Definition & Compliance Guide

Bramble·March 23, 2026·3 min read

Umbrella liability insurance and excess liability insurance are related but distinct coverages that extend protection beyond the limits of an insured's underlying policies. Both are used to satisfy high-limit contractual requirements that cannot be met by primary coverage alone. Understanding the difference between the two - and how to verify compliance on a certificate of insurance - is essential for contracts with substantial liability requirements.

Key Definition

Umbrella and excess liability insurance extend protection above underlying policy limits - umbrella policies both follow form and can drop down to fill gaps, while excess policies only add limits on top of the underlying policy.

Key Comparison
Umbrella Policy
  • Follows form above underlying policies
  • Can drop down to fill coverage gaps
  • Broader protection with retained limit
  • More flexible for the insured
Excess Policy
  • Only adds limits above underlying policy
  • Does not drop down for coverage gaps
  • Terms tied entirely to underlying policy
  • More restrictive than umbrella

Umbrella Insurance Defined

An umbrella policy does two things:

  1. It follows form - it picks up where underlying policies leave off when their limits are exhausted, providing coverage on top of general liability, commercial auto, and employers' liability
  2. It drops down - it can sometimes provide coverage for claims that are covered by the umbrella but not by the underlying policy (filling gaps), subject to a retained limit or self-insured retention

The "follow form" behavior means an umbrella policy adopts the terms, conditions, and exclusions of the underlying policy. The "drop down" feature provides additional coverage flexibility.

Excess Liability Insurance Defined

An excess liability policy does only one thing: it provides additional limits on top of an underlying policy when that policy's limits are exhausted. An excess policy follows form - it adopts the terms and conditions of the underlying policy - but does not drop down to fill coverage gaps. It simply adds limit.

Excess policies are more restrictive than umbrella policies. They do not provide the drop-down feature, and their terms are tied entirely to the underlying policy.

Which Contracts Require Umbrella or Excess Coverage

Large commercial contracts - construction projects, commercial leases, major service agreements - frequently require total coverage limits that exceed what primary policies provide. A contract may require $5 million in general liability coverage, but a primary CGL policy might have a $1 million per occurrence limit. An umbrella or excess policy providing $4 million above the primary satisfies the total requirement.

Common structures:

  • Primary CGL: $1M / $2M + Umbrella: $5M = $6M total capacity
  • Primary CGL: $2M / $4M + Umbrella: $10M = $12M total capacity

Some contracts specify that the umbrella or excess limits apply per occurrence as well as in aggregate. Others specify the total required across all layers without prescribing the structure.

Reading Umbrella/Excess on a COI

On the ACORD 25, umbrella and excess coverage appear in a dedicated section. Key fields:

  1. Coverage designation - "Umbrella" or "Excess Liability" - note which type is submitted and confirm it satisfies the contract's requirement
  2. Underlying policies - the umbrella or excess policy should reference the underlying policies it sits above; these should match the other coverage lines on the same COI
  3. Each occurrence limit - the per-occurrence limit of the umbrella or excess layer
  4. Aggregate limit - the total limit for the policy period
  5. Self-insured retention (SIR) - some umbrella policies include a retention the insured must pay before the umbrella responds; contracts may limit allowable SIRs
  6. Effective and expiration dates - must align with underlying policy dates and cover the performance period
  7. Additional insured and waiver of subrogation - if your contract requires these on all policies including umbrella, they must be noted

The Underlying Policy Schedule

A well-structured umbrella or excess policy sits above specific underlying policies and requires those policies to maintain minimum limits. If underlying limits drop below the required minimum (because a claim partially exhausts a primary policy), the umbrella may not respond as expected until the insured satisfies the gap.

When reviewing a COI, confirm that the umbrella or excess policy references underlying policies that match the other lines on the certificate. A mismatch - such as an umbrella referencing a different general liability policy number than what is shown on the certificate - is a red flag.

Common Compliance Issues

Excess-only submitted when umbrella is required. Some contracts specify "umbrella" coverage, and an excess-only policy may not satisfy that requirement if the drop-down feature is material to the contract's intent.

Underlying limits too low to trigger the umbrella properly. If primary limits have been eroded by prior claims, the umbrella may not respond as expected.

SIR too large. Some umbrella policies carry significant self-insured retentions. Contracts may cap allowable SIRs; if the SIR exceeds that cap, the requirement is not met.

Additional insured not carried through to umbrella. A contract requires additional insured status on all policies including umbrella. The COI shows it on the CGL line but not on the umbrella.

Limits structured incorrectly. The contract requires $5M total coverage. The vendor submits a $1M primary and a $3M umbrella - only $4M total, not $5M.

How Bramble Helps

Bramble reads your contractual umbrella and excess requirements - total limits, underlying policy references, endorsement requirements - and validates them against submitted COIs, catching mathematical shortfalls, missing endorsements, and underlying policy mismatches that manual review commonly misses.

Visit getbramble.com to learn how Bramble handles contract-vs-COI compliance across all coverage layers.

See how Bramble reads the document that defines what the certificate should contain.

See It In Action