Each Occurrence vs. General Aggregate: COI Limits Explained

by

Coverage limits

Each Occurrence vs. General Aggregate: COI Limits Explained

Each occurrence and general aggregate answer different limit questions. Contractors should compare each requirement with its matching certificate field instead of treating the largest displayed number as the available limit.

By COI Workbench Editorial Team · Reviewed September 2026 · General U.S. guidance

Each occurrenceA limit associated with one covered occurrence, subject to policy terms

≠

General aggregateA broader cap that may apply across covered occurrences during the policy period
Do not infer claim coverage from a limit. A displayed dollar amount does not show whether a loss is covered, which exclusions apply, how much of an aggregate remains, or how multiple policies interact.

The difference in plain language

An each-occurrence limit is associated with the amount the insurer may pay for one covered occurrence under the applicable policy terms. A general aggregate is a cap that may apply to a collection of covered losses during the policy period. Policies define how these concepts operate; the certificate only reports selected values.

For an administrative comparison, the important point is simpler: they are separate requirements. If a contract asks for both, verify both. A $2 million general aggregate does not automatically answer a $2 million each-occurrence requirement.

A non-coverage example

Suppose a project requirement lists commercial general liability of $1 million each occurrence and $2 million general aggregate. The certificate displays $1 million each occurrence and $2 million general aggregate. The values appear to meet the numeric request, but that comparison alone says nothing about exclusions, endorsements, project-specific aggregate wording, erosion from prior claims, or whether the policy applies to a future event.

If the certificate instead displays $1 million each occurrence and $1 million general aggregate, the occurrence line matches while the aggregate line shows a $1 million numeric shortfall. The correct result is two separate statuses—not an average and not a pass because one field is large enough.

Other limits that should stay separate

Coverage area Common field Do not substitute
General liability Each occurrence General aggregate
General liability Products/completed-operations aggregate General aggregate without confirmation
Commercial auto Combined single limit A general-liability limit
Umbrella/excess Each occurrence and aggregate Underlying limits without policy review
Employer’s liability Each accident Disease policy limit or disease per employee
Professional liability Each claim/occurrence and aggregate Commercial general liability

What about products and completed operations?

The products/completed-operations aggregate is often displayed separately from the general aggregate. Contracts may request a specific value and may ask for additional-insured evidence addressing completed operations. Keep the numeric limit comparison separate from the endorsement question: matching numbers do not establish the scope of additional-insured protection.

Can umbrella or excess insurance fill a difference?

Sometimes a contract permits a combination of primary and umbrella or excess limits. That is not a reason to add every displayed number automatically. Ask three questions:

  1. Does the written requirement expressly allow limits to be provided through umbrella or excess insurance?
  2. Does the applicable umbrella or excess policy sit over the required underlying coverage?
  3. What certificate and endorsement evidence does the reviewer require?

The agent should answer policy-structure questions. The client or its risk reviewer should clarify an ambiguous contract requirement.

Why an aggregate may need special attention

An aggregate can apply across operations, locations, projects, or a defined category depending on policy wording and endorsements. Some public contracts explicitly require the aggregate to apply separately to a project or location. Do not assume a project-specific aggregate exists because a contract requests one or because the general aggregate value is high enough. Send the exact clause to the agent.

A five-step comparison

  1. Transcribe the written requirement. Record the label and dollar amount exactly.
  2. Find the corresponding certificate field. Do not compare across unrelated rows.
  3. Enter both values. The COI Coverage Limit Comparator reports matches, shortfalls, and missing values.
  4. Keep policy questions separate. Additional-insured, primary, waiver, and aggregate wording are not solved by arithmetic.
  5. Send unresolved items together. Use the Agent Request Builder to prepare a clear follow-up.

Frequently asked questions

Is the aggregate always twice the occurrence limit?

No universal ratio should be assumed. Compare the actual contract and certificate fields. Public requirements often use different combinations based on the work and risk.

Does a higher aggregate compensate for a lower occurrence limit?

Not in a direct field-by-field comparison. If the occurrence amount is below the stated requirement, flag that line for the agent and reviewer.

Does the certificate show the remaining aggregate?

A standard certificate value generally reports a policy limit, not a live balance after claims. Ask the appropriate insurance professional if remaining aggregate information matters.

Are all umbrella policies the same?

No. Attachment points, underlying coverage, terms, exclusions, and follow-form features vary. A certificate comparison cannot determine how an umbrella policy will respond.

Sources and limits

Examples explain document comparison only. They do not calculate claim payments, available aggregate, or contract compliance.