Excess vs Umbrella

Overview

On a certificate of insurance, the row labeled UMBRELLA LIAB / EXCESS LIAB treats two related but distinct coverages as interchangeable. In practice, they behave differently when claims arise, and the distinction often determines whether a particular loss is covered, how much the insured must pay out of pocket, and whether the certificate holder's risk-transfer expectations are actually met.

Umbrella liability is a standalone liability policy that sits above the underlying policies and may provide broader coverage than the underlying. When a covered loss falls outside the underlying policy grant but within the umbrella's broader grant, the umbrella "drops down" and pays — subject to a self-insured retention.

Excess liability is a strictly follow-form layer that attaches above a specific underlying policy. It adopts the underlying policy's terms, conditions, exclusions, and definitions. Excess does not broaden coverage and does not drop down — it only extends the limits.

The ACORD 25 includes two checkboxes in this block: UMBRELLA LIAB and EXCESS LIAB. The checkbox that is marked tells a reviewer what type of layer is in force. Inori's extraction captures this distinction in the type field of the umbrella schema ("umbrella" or "excess").

How They Work

Excess Liability

An excess policy is designed to follow form — mirror the terms of the underlying policy. If the underlying CGL excludes pollution, the excess layer also excludes pollution. If the underlying has a professional services exclusion, the excess does too. The excess policy adds a new layer of limit on top of the underlying layer with no change in coverage scope.

Attachment is strict: the excess policy attaches at a specific dollar amount above the underlying (typically right at the underlying per-occurrence limit, with no gap). When the underlying is exhausted by covered claims, the excess responds for the balance up to its own limit.

If the underlying policy does not cover a claim, neither does the excess. There is no drop-down mechanism.

Umbrella Liability

An umbrella policy typically has its own coverage grant — broader in some respects than the underlying — and attaches above the underlying limits for claims that both policies cover. For claims the underlying does not cover but the umbrella does, the umbrella drops down to first-dollar after the insured satisfies a retention (typically $10,000 to $25,000).

This drop-down behavior is the defining feature of a true umbrella. It creates a second layer of coverage that can fill gaps in the underlying policy — liquor liability on a restaurant CGL, certain personal injury offenses, some international exposures — depending on the umbrella's specific grant.

Comparison Table

When Each Is Used

Umbrella is common as the first layer above the primary CGL, Auto, and EL policies for small and mid-market vendors. Insureds want the broader coverage and drop-down behavior because the underlying policies may have meaningful gaps.

Excess is common for:

• Layered towers ($5M excess of $5M, $15M excess of $10M, etc.) where total limits of $25M, $50M, or $100M+ are built from multiple excess layers stacked above a single primary.
• Large corporate programs where the risk manager wants strict follow-form alignment and no ambiguity about drop-down.
• Situations where the underlying is already broad enough that drop-down would be redundant.

Many modern "umbrella" policies are in fact written on excess follow-form terms but still called umbrellas by convention — the label on the COI is not always a reliable indicator of drop-down behavior. The most reliable signal is the self-insured retention: true umbrellas carry a retention, pure excess does not.

Where it appears on ACORD 25

Both coverages share the UMBRELLA LIAB / EXCESS LIAB block on the ACORD 25. At the top of the block are two checkboxes labeled UMBRELLA LIAB and EXCESS LIAB — the marked box indicates the policy type. Immediately below are the standard fields: policy number, effective and expiration dates, each occurrence limit, aggregate limit, and a deductible / retention area.

The OCCUR / CLAIMS-MADE checkboxes on the umbrella row mirror the occurrence vs claims-made distinction on the primary CGL.

Why It Matters for Compliance

• Drop-down expectation: Contracts that require "umbrella" coverage often assume drop-down behavior. If the certificate shows EXCESS LIAB checked instead, risk teams may need to verify the underlying coverage scope is adequate, since the excess layer cannot compensate for gaps in the underlying.
• Retention gating: Inori captures the retention independently and cross-references it with the coverage type. A retention on an EXCESS LIAB row is unusual and may warrant review.
• Follow-form verification: For excess policies, the schedule of underlying is the source of truth for what the excess actually follows. When a contract requires excess coverage above specific primary policies, Inori flags mismatches between the schedule of underlying and the listed primary policies.

Related Concepts

The follow-form principle that defines excess liability is explained in follow form. The broader coverage grant of true umbrellas is the feature examined in umbrella liability. The retention that gates drop-down claims is documented in self-insured retention.