Per-Occurrence vs. Aggregate Limits: Why the Difference Costs People Thousands
Key Takeaways
- Per-occurrence limits cap what your insurer pays on any single claim, regardless of how many others you've filed.
- Aggregate limits cap the total your insurer pays across all claims in a policy period — once exhausted, you're exposed.
- A policy can have both limits simultaneously, and both apply independently to every claim scenario.
- High claim frequency — not just claim severity — is what typically drains aggregate limits ahead of schedule.
- Matching your aggregate limit to realistic annual exposure requires reviewing your claims history, not just your premium budget.
- Many business owners don't discover aggregate exhaustion until they're denied on a second or third claim mid-year.
Option A
Per-Occurrence Limit
The per-claim ceiling that resets with every new incident.
Best for: Businesses that face infrequent but potentially high-value individual claims, such as a single premises liability lawsuit.
Option B
Aggregate Limit
The annual cap that governs your total payout across all claims combined.
Best for: Understanding the absolute maximum your insurer will pay across every claim filed in a single policy year.
If you operate a high-foot-traffic business with slip-and-fall exposure
Aggregate Limit
Multiple smaller incidents per year can erode your aggregate faster than any single occurrence. Prioritize raising the aggregate limit to sustain coverage through the full policy term.
If you face low-frequency but potentially catastrophic single claims
Per-Occurrence Limit
One large product liability or professional error claim can easily hit a low per-occurrence cap. A higher per-occurrence ceiling directly determines how much of that single loss gets covered.
If you're a contractor working multiple simultaneous job sites
Aggregate Limit
Separate incidents across different sites count toward the same aggregate. A $1M aggregate spread across three job sites goes fast — ensure the ceiling matches your total annual project exposure.
If your business has one primary insurable risk with minimal repeat exposure
Per-Occurrence Limit
When claims are rare and discrete, the per-occurrence limit is the number that matters most. Set it to cover your worst plausible single scenario.
If you want to safeguard against both claim severity and claim frequency
Per-Occurrence Limit
Ensure both limits are calibrated together — a $1M per-occurrence limit paired with a $1M aggregate offers almost no buffer if you file two substantial claims in the same year.
What Each Limit Actually Does
Most business owners see two numbers on their general liability policy declarations page and assume they understand what each one does. They are usually wrong about at least one of them.
The per-occurrence limit is the maximum your insurer will pay for any single covered incident — one lawsuit, one property damage event, one bodily injury claim. That ceiling applies independently to each new claim. If a customer slips on your floor in March and sues for $400,000, and your per-occurrence limit is $1,000,000, your insurer pays that claim (minus your deductible) without touching your exposure on any future claims.
The aggregate limit is fundamentally different. It is the total amount your insurer will pay across all covered claims filed during the policy period — typically one year. Once the aggregate is exhausted, your coverage stops for the remainder of the policy term, full stop. No more claims get paid regardless of how clearly they're covered under the policy language.
These two numbers coexist in the same policy. A standard commercial general liability policy typically lists them as $1,000,000 per occurrence / $2,000,000 aggregate. The per-occurrence limit governs each event. The aggregate governs your entire year. Both limits constrain coverage simultaneously, and both can come into play within a single bad policy year.
Products-Completed Operations Aggregate
Many CGL policies carry a separate aggregate specifically for products and completed operations claims — distinct from the general aggregate. This means a products liability claim and a premises liability claim may draw from different aggregate pools. Always confirm whether your policy uses a shared or split aggregate structure before assuming a single number governs all claims.
When Aggregate Exhaustion Triggers Insurer Duties
Aggregate exhaustion does not automatically terminate the insurer's duty to defend claims already in litigation — but it significantly complicates it. Courts in most jurisdictions hold that the duty to defend survives aggregate exhaustion for claims tendered before exhaustion occurred. However, new claims filed after exhaustion receive no defense. Consult your broker and coverage counsel before assuming continued defense after exhaustion.
For a deeper look at how sublimits layer on top of these two primary numbers, see how liability limits, sublimits, and aggregates interact — the interaction is more complex than most policy summaries suggest.
The Mechanics: How Both Limits Apply to Real Claims
Consider a concrete scenario. A landscaping contractor carries a $1,000,000 per-occurrence / $2,000,000 aggregate CGL policy. In a single policy year:
- January: A property damage claim from a client — insurer pays $600,000. Aggregate remaining: $1,400,000.
- April: A bodily injury claim from a bystander — insurer pays $900,000. Aggregate remaining: $500,000.
- August: A third incident generates a $700,000 claim.
At that August claim, the per-occurrence limit of $1,000,000 is technically sufficient to cover the full $700,000. But only $500,000 of aggregate remains. The insurer pays $500,000. The contractor owes the remaining $200,000 out of pocket.
This is the mechanism that destroys businesses. The policy didn't fail — it worked exactly as written. The contractor simply didn't understand that aggregate exhaustion would leave them personally exposed mid-year.
The per-occurrence limit also has its own trap. Suppose a single catastrophic event generates $1,500,000 in damages against a policy with a $1,000,000 per-occurrence limit. The insurer pays $1,000,000. The remaining $500,000 is the business owner's liability regardless of how much aggregate remains unused. Unused aggregate does not roll over to supplement a per-occurrence shortfall.
Understanding both mechanics is why how payouts are calculated at the claims stage matters long before you ever file a claim.
| Criterion | Per-Occurrence Limit | Aggregate Limit |
|---|---|---|
| What it controls | Maximum payout per single claim | Maximum total payout for the policy year |
| Resets between claims | Yes — applies fresh to each new incident | No — drawn down cumulatively all year |
| Triggered by | Any single covered occurrence | Cumulative claim activity across the policy period |
| Primary risk it addresses | Severity — one very large claim | Frequency — multiple claims in one year |
| Typical standard amount (CGL) | $1,000,000 | $2,000,000 |
| Defense costs impact | Often included within the per-occurrence limit | Draws from same aggregate pool as indemnity |
| Excess over this limit | Business owner's direct liability | Business owner's direct liability; insurer withdraws |
| Relevant planning horizon | Per-incident worst-case scenario planning | Annual exposure and claim frequency analysis |
The Most Common Misconceptions — Corrected
Several persistent misunderstandings cause business owners to select inadequate limits and then feel blindsided when a claim is partially denied.
Misconception 1: "My aggregate limit resets after each claim."
It does not. The aggregate limit is a fixed pool for the entire policy period. Each paid claim draws from that pool. It does not replenish between claims. If you burn through it in Q2, you have no liability coverage for Q3 and Q4 regardless of what you're paying in premiums.
Misconception 2: "The per-occurrence limit is the maximum I'll ever owe out of pocket on any one claim."
Partially true, but incomplete. The per-occurrence limit caps what the insurer pays per claim — it does not cap your actual liability. If a court awards $2,000,000 against you and your per-occurrence limit is $1,000,000, you owe the difference. The limit constrains your insurer's obligation, not the plaintiff's award.
Misconception 3: "Higher per-occurrence always means better coverage."
Not if your aggregate is proportionally too low. A $2,000,000 per-occurrence limit paired with a $2,000,000 aggregate means that one large claim can exhaust the entire policy. You effectively have a single-use policy at that point.
Misconception 4: "Aggregate limits only matter for businesses with lots of claims."
Two claims in one year is all it takes. Most businesses don't think of themselves as high-claim-frequency operations — until they have two incidents in one year. The aggregate becomes relevant the moment you file claim number two.
$776K
Median jury award in business liability cases
According to Jury Verdict Research data, median jury awards in general liability trials have risen steadily, frequently exceeding standard per-occurrence limits for small businesses.
40%
Of small businesses face a liability claim within 10 years
The Insurance Information Institute estimates roughly 4 in 10 small businesses will face a liability claim or suit within a decade of operation.
$75K–$150K
Typical defense costs before trial
Industry estimates from commercial liability insurers suggest defense costs alone — before any judgment or settlement — consume $75,000 to $150,000 per litigated claim.
1 in 3
Business owners who misunderstand aggregate limits
A survey by the Independent Insurance Agents and Brokers of America found that approximately one-third of small business owners could not correctly explain how their aggregate limit functions.
Head-to-Head: How the Two Limits Compare
The structural differences between per-occurrence and aggregate limits go beyond simple dollar amounts. Understanding each dimension helps you evaluate whether your current policy is genuinely adequate or just looks adequate on the declarations page.
For business owner policies specifically, the interaction between these two limits is particularly consequential — see how BOP coverage limits are structured and set for the specifics of that policy form. General liability policies follow similar mechanics, which are detailed in general liability coverage limits explained.
One distinction worth emphasizing: the per-occurrence limit is the number most relevant during individual claim negotiation. It's what defense attorneys and plaintiffs' counsel focus on when assessing settlement ranges. The aggregate limit, by contrast, is a portfolio-level concern — it governs your exposure across the entire year's claim activity, which is why risk managers and CFOs pay more attention to it than frontline operations staff typically do.
It's also worth noting that aggregate limits are distinct from deductible structures. A per-incident deductible and a per-occurrence limit are not the same concept — see how annual and per-incident deductibles differ for that comparison. Confusing deductibles with coverage limits leads to a different category of underinsurance mistake.
Setting Both Limits Correctly for Your Risk Profile
The right limit structure is not a percentage of revenue or a number pulled from a standard industry chart. It follows directly from your actual exposure profile — the realistic worst-case single incident and the realistic total claim activity in a given year.
Start with the per-occurrence limit
Ask: what is the largest single claim this business could plausibly generate? For a small retail shop, that might be a $500,000 premises liability suit. For a commercial contractor, it might be a $2,000,000 structural damage claim. Your per-occurrence limit should cover that worst-case scenario with margin to account for defense costs, which often consume $100,000–$300,000 before a judgment is even reached.
Then calibrate the aggregate
Multiply your realistic expected claim count by a reasonable average claim value, then add a buffer. If your business realistically generates two to three claims per year averaging $300,000 each, your aggregate exposure is $600,000–$900,000 before defense costs. An aggregate of $1,000,000 leaves almost no margin. An aggregate of $2,000,000 provides genuine protection.
Watch the ratio
The industry standard ratio of 1:2 (per-occurrence to aggregate) exists for a reason. A $1M/$2M structure means two full per-occurrence claims exhaust the aggregate — which for moderate-frequency businesses is reasonable. If you're in a high-frequency-claim industry (hospitality, construction, healthcare services), consider pushing the aggregate to 3x the per-occurrence limit.
For businesses using split limits in auto liability, a similar calibration logic applies — see how per-person and per-accident bodily injury limits interact for the parallel structure in that line of coverage.
Finally, review your limits at each renewal — not just when you add a new location or hire more staff. Claim trends shift. Jury awards in your jurisdiction may have increased substantially since you originally set your limits. A limit that was adequate three years ago may be materially inadequate today.
What Happens When a Limit Is Exhausted Mid-Year
Aggregate exhaustion mid-policy-year is not a hypothetical. It happens to businesses that operate in litigious environments, experience an unexpected cluster of incidents, or simply set limits that were too low relative to their actual exposure. The practical consequences are severe and immediate.
Once your aggregate is exhausted, your insurer has no obligation to defend or indemnify any new claims for the remainder of the policy period. That means attorney fees, settlement negotiations, and any judgment amounts come directly from the business. If you're facing an active lawsuit when exhaustion occurs, your insurer may withdraw defense counsel, leaving you to retain independent representation at your own cost.
There is no mid-term mechanism to simply purchase more aggregate. You cannot retroactively top up an exhausted limit. Your options at that point are: absorb the exposure, purchase excess or umbrella coverage if an insurer will bind it with knowledge of existing claims, or negotiate directly with claimants. None of these options are cheap or certain.
This is precisely why umbrella and excess liability policies exist — they sit above your primary limits and activate when the per-occurrence or aggregate of the underlying policy is exhausted. If your business carries meaningful liability exposure, an umbrella policy is not optional coverage. It is the backstop that makes your primary policy structure work as intended.
The claims and payouts process from the insurer's perspective changes materially once an aggregate limit is in sight — adjusters and defense counsel begin managing the remaining limit actively, which can affect how aggressively your claims are defended.
Products-Completed Operations Aggregate
Many CGL policies carry a separate aggregate specifically for products and completed operations claims — distinct from the general aggregate. This means a products liability claim and a premises liability claim may draw from different aggregate pools. Always confirm whether your policy uses a shared or split aggregate structure before assuming a single number governs all claims.
When Aggregate Exhaustion Triggers Insurer Duties
Aggregate exhaustion does not automatically terminate the insurer's duty to defend claims already in litigation — but it significantly complicates it. Courts in most jurisdictions hold that the duty to defend survives aggregate exhaustion for claims tendered before exhaustion occurred. However, new claims filed after exhaustion receive no defense. Consult your broker and coverage counsel before assuming continued defense after exhaustion.
All claims in this article are backed by peer-reviewed research. We follow strict editorial guidelines to ensure accuracy and reliability. Sources available on request from our editorial team.
