Umbrella Aggregate

Overview

The Umbrella Aggregate is the policy-period cap on the umbrella or excess liability tower — the total pool of money the umbrella insurer will pay out for all covered claims combined during the policy term. Once the aggregate is exhausted, the umbrella is effectively "burned through" for the remainder of the policy period, even if the each occurrence limit has not been reached on any individual claim.

The aggregate serves as the insurer's total exposure ceiling for that policy year. It is the second critical number on the umbrella row of an ACORD 25, alongside the each occurrence limit. Together, the two limits define the shape of the umbrella tower: how much per event, and how much in total.

For small- to mid-market umbrellas, the umbrella each occurrence and aggregate are often set to the same number (e.g., $5M / $5M). Larger towers written by specialty carriers frequently separate the two (e.g., $10M each occurrence / $25M aggregate), giving the insured more total capacity across a potentially claim-heavy year.

How It Works

The umbrella aggregate erodes with every dollar the umbrella pays out, regardless of how many separate claims those dollars come from. Consider a vendor with a $5,000,000 umbrella each occurrence / $5,000,000 umbrella aggregate policy:

• Claim 1 (month 3): $2,000,000 umbrella payout. Remaining aggregate: $3,000,000.
• Claim 2 (month 8): $2,500,000 umbrella payout. Remaining aggregate: $500,000.
• Claim 3 (month 11): $1,000,000 claim. Only $500,000 is available from the umbrella; the insured must pay the remaining $500,000 out of pocket (unless a second excess layer exists above).

A critical subtlety: the aggregate is not visible on the COI. Inori can verify the aggregate as written on the policy, but cannot know in real time how much has been eroded by paid claims. This is one of the fundamental limitations of COI-based compliance and a reason large portfolios increasingly ask for mid-term confirmation or loss runs.

Common Limits

Typical umbrella aggregate limits by tower size:

The ratio of aggregate to each occurrence is a rough proxy for the insurer's expected claim frequency — higher-risk classes tend to get 1:1 aggregates, while lower-risk risks sometimes see 2:1 or higher.

Where it appears on ACORD 25

The umbrella aggregate appears in the UMBRELLA LIAB / EXCESS LIAB block on the ACORD 25, in the "AGGREGATE" field immediately below the "EACH OCCURRENCE" field. The limits column on this row typically shows two values: one for each occurrence and one for the aggregate. Some carriers leave the aggregate blank if it matches the each occurrence — an ambiguity that a well-trained reviewer should resolve by looking at the underlying policy document.

Alongside the aggregate, the same umbrella block carries the policy aggregate status (aggregate per project or per location, when applicable), the retention or deductible, and the umbrella-vs-excess checkbox.

Why It Matters for Compliance

• Annual capacity check: Inori compares the umbrella aggregate against contract requirements that explicitly reference total or aggregate limits (common in large commercial real estate and construction contracts).
• Aggregate gap: If the primary general aggregate limit is $2M and the umbrella aggregate is only $1M, total aggregate capacity is just $3M — often below what a mid-to-high-risk contract requires. Inori surfaces this as a gap even when each occurrence limits look adequate.
• Erosion risk disclosure: While Inori cannot detect real-time aggregate erosion, risk teams can configure reminders to request loss runs mid-term for high-value vendors where an eroded umbrella would materially change exposure.

Related Concepts

The umbrella aggregate pairs with the umbrella each occurrence limit to define the full shape of the umbrella. It is conceptually parallel to the general aggregate limit on the primary CGL but sits one layer higher. For multi-project contractors, aggregate behavior may also be affected by endorsements that reinstate or multiply the aggregate per project — details visible only on the full policy, not on the COI.