The per-occurrence limit on a general liability policy is the most the carrier will pay for any single covered claim. The general aggregate limit is the most the carrier will pay across every covered claim during the policy period combined. Both limits apply at the same time, and a bad claim year can erode the aggregate to the point that subsequent losses get reduced or denied even when the per-occurrence limit looks intact. Reading both numbers together is the only way to know what the policy will actually pay when claims arrive.

A general liability declarations page shows two liability numbers stacked on top of each other, and a policy review that treats them as a single dollar figure misses how commercial claims actually pay out. Per-occurrence is the ceiling on any one event. The general aggregate is the ceiling on the year. A separate products and completed operations aggregate sits alongside the general aggregate for long-tail claims arising from finished work or sold products. A worked example with three claims in one policy year shows how the math erodes quietly until the renewal date — and why Iowa commercial accounts that operate on a thin aggregate run the risk of being underinsured by month nine without ever seeing it on the declarations page.

• What are per-occurrence and aggregate limits on a general liability policy?
• How do per-occurrence and aggregate limits work together — a worked example
• What causes an aggregate to exhaust quietly during the policy year?
• When are per-occurrence and aggregate limits not enough on their own?
• How Avanti Group reviews per-occurrence and aggregate limits on a commercial program
• Frequently Asked Questions

What are per-occurrence and aggregate limits on a general liability policy?

Every commercial general liability policy written in the United States stacks two liability limits on the declarations page. They both apply, they pay claims in the same year, and they do different jobs. The starting point for any business insurance review is reading them together.

The per-occurrence limit is the most the carrier will pay for any one occurrence — a single covered event that produces bodily injury, property damage, or personal and advertising injury. A single slip-and-fall in a retail space, a single property-damage event on a job site, a single trade-libel claim arising from one advertisement — each is one occurrence, capped at the per-occurrence number. Most small and mid-market commercial accounts carry a $1 million per-occurrence limit as the default. Larger accounts, public-entity contracts, and accounts with contractual indemnity obligations routinely sit at $2 million or higher.

The general aggregate limit is the most the carrier will pay across all occurrences during the policy period combined. It is a separate ceiling that applies to the sum of every claim payment under Coverage A and Coverage B of the CGL policy and the coverage parts inside it during the year. The default for small and mid-market accounts is typically $2 million general aggregate against a $1 million per-occurrence — the classic $1M/$2M structure that shows up on most quote summaries. Larger accounts run $5 million, $10 million, and higher; very small accounts sometimes carry $1M/$1M, which is materially different from $1M/$2M and worth flagging at any policy review.

A separate products and completed operations aggregate sits alongside the general aggregate for long-tail claims arising from finished work or products the business has sold. Manufacturer, contractor, and product-seller policies carry this third limit because claims tied to completed work or sold goods often surface years after the policy period ends and tend to cluster in patterns the general aggregate is not sized to absorb. The products and completed operations aggregate is often equal to the general aggregate but sits in its own bucket and erodes independently.

Where these limits live is on the commercial declarations page, and the order in which they appear matters. The per-occurrence and aggregate numbers are usually listed before the line-by-line endorsement schedule, before the sublimits, and before the deductibles. Reading them in isolation — without also reading the sublimits and exclusions further down the form — produces a number that looks adequate and a policy that may not be.

How do per-occurrence and aggregate limits work together — a worked example

The math is easier to see in a single worked example than in any explanation.

An Iowa commercial contractor carries a CGL policy with $1 million per occurrence, $2 million general aggregate, and $2 million products and completed operations aggregate. The policy period is January 1 through December 31. Three claims arrive across the year.

Claim one, February. A property-damage occurrence on an active job — the contractor’s crew damages a neighboring building during a tear-off. Settlement and defense costs total $400,000. The per-occurrence limit of $1 million absorbs it cleanly. The general aggregate, which started the policy period at $2 million, draws down to $1.6 million.

Claim two, June. A homeowner falls on the same project during punch-list work and brings a bodily-injury claim. The settlement is $800,000. The per-occurrence limit is intact and pays in full. The general aggregate now stands at $800,000 — $2 million minus $1.2 million in cumulative paid claims.

Claim three, November. An unrelated trade-libel claim arrives, settling at $500,000. The per-occurrence limit of $1 million is still intact for the new occurrence, but the general aggregate has only $800,000 left. The carrier pays the $500,000, and the aggregate now stands at $300,000 — meaning any further covered claim in the last six weeks of the policy year is capped at $300,000, not the $1 million per-occurrence number on the declarations page.

If a fourth claim arrives in December — a routine property-damage event that would normally be a $400,000 settlement — the carrier pays $300,000 and the contractor is out-of-pocket for the rest. The aggregate is exhausted. The per-occurrence limit is meaningless once the aggregate is gone. Coverage does not reset until the renewal date.

This is the math underneath every renewal conversation about whether to raise limits, layer a commercial umbrella on top, or restructure the program. The carrier and the broker are not arguing about a single $1 million decision; they are arguing about how the $2 million aggregate is going to be sized against a realistic frequency of claims across a year of operations.

What causes an aggregate to exhaust quietly during the policy year?

Aggregate erosion almost never announces itself. It accrues across small and mid-sized claims that each individually fit comfortably inside the per-occurrence limit, and by the time the aggregate is depleted, the business is typically months into the policy year and operating on a coverage ceiling it does not realize has dropped.

A few patterns drive quiet aggregate exhaustion in Iowa commercial accounts:

The first is a high-frequency, low-severity operation — restaurants with slip-and-fall exposure, habitational accounts with premises liability events, retail with shoplifting-related personal-injury claims. Each individual loss is small. Ten claims at $80,000 each absorb $800,000 of the aggregate without any one of them being a noteworthy event.

The second is a long-tail product or completed-operations pattern. A roofing contractor whose workmanship issues surface eighteen months after install, a manufacturer whose product defect claims cluster after a model year ships — these claims hit the products and completed operations aggregate in waves, often after the policy period that originally covered the work has expired.

The third is a single open claim with a reserve set high. A reserved claim that has not yet paid still draws against the aggregate from the carrier’s reserving standpoint, and a $750,000 reserve on a claim that may eventually settle for $200,000 will narrow the available aggregate during the year even though no money has changed hands.

The fourth is the interaction of the aggregate with sublimits and policy conditions. A claim that triggers a sublimited coverage — abuse and molestation, communicable disease, certain pollution time-element extensions — pays inside its own sublimit but may also erode the general aggregate. The mechanics depend on the form, and the form is where the answer sits.

None of these patterns produce a single moment of alarm. The aggregate gets quieter as it gets smaller, and the renewal date is often the first time the business sees it in writing.

When are per-occurrence and aggregate limits not enough on their own?

A $1M/$2M GL program is the floor of a commercial liability tower, not the ceiling. Several common Iowa commercial situations push the program beyond what the standalone CGL can absorb:

Contracts that require $5 million, $10 million, or higher liability limits — common in general-contractor relationships, public-entity work, healthcare contracts, and large landlord agreements — require a commercial umbrella sitting on top of the primary CGL. The umbrella attaches at the per-occurrence and aggregate ceilings of the underlying policy and provides excess capacity for both.

A products or completed operations exposure that is materially larger than the general operations exposure may require a sized-up products and completed operations aggregate, a separate product recall policy, or a manuscripted endorsement to widen the coverage trigger. A contractor whose workmanship claims surface years after install needs a program structured for the long tail, not just the policy year.

A high-frequency operation with a thin aggregate may need the aggregate raised at the primary layer before the umbrella attaches. A $1M/$2M structure on a habitational or restaurant account that historically produces three to five paid claims per year is structurally underfunded; raising to $1M/$3M or $1M/$4M closes the gap without changing the per-occurrence number.

Property exposure is a separate decision and a separate program. The CGL does not respond to damage to the business’s own property — that risk sits on the commercial property policy, and the limits there are sized by replacement cost, business income, and the value of the schedule, not by the GL aggregate.

How Avanti Group reviews per-occurrence and aggregate limits on a commercial program

Avanti Group does not start a general liability insurance review at the per-occurrence number. The Business Risk Diagnostic™ starts at the operation: what the business does, what its customer and vendor contracts require, what its three-to-five-year loss history looks like, what its frequency-versus-severity pattern is, and what coverages are stacked above and beneath the GL. The per-occurrence and aggregate decision is the output of that work, not the starting point.

A $1M/$2M structure on a business whose loss history shows two or three open claims per year and a six-figure average settlement is a structure that will exhaust the aggregate before the renewal date in a normal year. A $1M/$4M structure on the same operation closes that gap without forcing an umbrella decision tied to a contractual requirement that does not yet exist. Conversely, a $1M/$2M structure on a low-frequency operation with one paid claim every three years is appropriately sized — and over-buying the aggregate is a premium decision that should be made with eyes open, not on autopilot.

The Diagnostic also surfaces the products and completed operations aggregate as its own decision. Contractors and manufacturers whose products and completed operations exposure exceeds their general operations exposure should not assume the default equal-bucket structure is the right one. The same applies to umbrella attachment: the per-occurrence and aggregate at the primary GL layer is what the umbrella attaches to, and the umbrella’s economics depend on whether the primary is sized correctly underneath it.

For Iowa commercial accounts — contractors, manufacturers, restaurants, habitational, healthcare, professional services — the working principle is straightforward: the math on the declarations page is supposed to match the math of the operation. The Avanti Group team runs the Business Risk Diagnostic before the quote because the per-occurrence and aggregate decision is a coverage decision, not a price decision, and it is the kind of decision that gets answered correctly once or gets answered too late.

Frequently Asked Questions

What does $1M/$2M mean on a general liability policy?

The first number is the per-occurrence limit — the most the carrier will pay for any single covered claim. The second number is the general aggregate limit — the most the carrier will pay across all covered claims during the policy period combined. A $1M/$2M structure means the carrier will pay up to $1 million on any one event and up to $2 million total for the year. Once the aggregate is paid out, no further claims pay until the renewal date resets the limit, even if the per-occurrence number looks intact on the declarations page.

Does the per-occurrence limit reset after each claim?

The per-occurrence limit applies fresh to each new occurrence, but every claim payment also draws against the aggregate. A $1 million per-occurrence policy will pay up to $1 million on each of three unrelated claims only if the aggregate is large enough to support the cumulative total. With a $2 million aggregate, the carrier can pay one $1 million claim and one $1 million claim and then the aggregate is exhausted; a third claim pays nothing under that policy regardless of how the per-occurrence limit reads.

What is the products and completed operations aggregate, and how is it different from the general aggregate?

The products and completed operations aggregate is a separate ceiling that applies to claims arising from products the business has sold or work the business has finished and turned over. It pays in its own bucket and is not eroded by claims arising from current operations or premises. Most CGL policies set it equal to the general aggregate by default, but the right limit depends on whether the products and completed operations exposure is materially larger or smaller than the general operations exposure. Contractors and manufacturers should not assume the default structure fits their exposure.

How much general liability aggregate does an Iowa business actually need?

The aggregate should be sized to absorb a realistic year of claims for the operation, not the minimum the carrier will quote. A high-frequency operation — restaurant, habitational, retail — with three to five paid claims per year at a six-figure average settlement needs an aggregate well above the default $2 million. A low-frequency professional or office operation may be fully covered at $1M/$2M with an umbrella above it. The right number falls out of three-to-five-year loss history and the operating profile, not out of a quote summary.

Does a commercial umbrella reset the per-occurrence and aggregate limits underneath it?

No. A commercial umbrella sits on top of the underlying CGL and pays only after the underlying per-occurrence and aggregate are exhausted on a covered claim. The umbrella does not reset the primary limits — it provides additional capacity above them. If the underlying aggregate is exhausted by smaller claims that never reached the umbrella, the umbrella still attaches at the original per-occurrence ceiling of the underlying policy, which means there can be a gap between an exhausted primary aggregate and the umbrella’s attachment point for the remainder of the year. Sizing the primary aggregate correctly is what keeps that gap from opening.