Last updated: October 22, 2026
Key Takeaways
- The aggregate limit is the policy’s total payment ceiling for covered claims in one policy term.
- Trace one policy period from start to finish to see how the limit is used.
- The per-occurrence limit caps one claim; the general aggregate caps all covered claims combined in the policy period.
- When the aggregate is used up, later covered claims may go unpaid even before the policy period ends.
An aggregate limit on business liability insurance is the most an insurer will pay for all covered claims combined during a policy period, usually 12 months. If a business has more than one claim in that period, every payment reduces that shared cap until it is exhausted.
This matters most when claims stack up. A single slip-and-fall can be one issue; a busy year with repeated injuries, advertising disputes, or product claims can drain the limit faster than owners expect. This article explains how the aggregate limit works, how it differs from the per-occurrence limit, and why one large loss or several smaller losses can leave a business underinsured. This is information, not financial advice; a qualified adviser should be consulted about your own policy and situation.
Who this applies to, and what you need to know first
This applies to a business owner, manager, or bookkeeper who already has a liability policy and wants to understand the limit that caps total claim payments over the policy term. It assumes you can read a declarations page and know the policy period dates, such as 1/1/2026 to 1/1/2027, even if the exact wording varies by insurer and country.
The main terms are simple once they are separated. A per-occurrence limit is the most the insurer pays for one claim or one covered incident. The aggregate limit is the most the insurer pays across all covered claims in the policy period. In many commercial general liability policies, the general aggregate limit applies to most claims, while the products-completed operations aggregate applies to claims tied to work you finished or products you sold. Those two aggregates may be separate, and that separation is the part many people miss.
This is not a page about how much liability coverage to buy, what liability insurance is, or what a policy costs. It is about how the cap works after a claim is paid. If the policy language is unclear, if the business has multiple locations, or if the work involves products, construction, food, or repeated customer contact, the wording deserves a close read from a qualified adviser or broker before a loss happens.
What the aggregate limit actually does
The aggregate limit is the policy’s total payment ceiling for covered claims during the policy term. If the aggregate is exhausted, the insurer can stop paying new covered claims even if the policy is still active and premiums are current.
That is the practical risk. A business can look well covered because it has a large per-occurrence limit, yet still run out of money after a cluster of claims. For example, if a policy has a 1-year term and the business gets three separate covered claims in that year, each payment comes out of the same aggregate bucket unless the policy says otherwise. Once the bucket is empty, later claims may have to be paid by the business itself.
The exact wording matters. Some policies define one aggregate for all covered liability; others split the policy into categories. The common split is between the general aggregate and the products-completed operations aggregate. The point is not merely academic. A restaurant, contractor, manufacturer, or landlord can see different claim patterns over a 12-month term, and the aggregate structure determines where the losses land.
A useful way to think about it is this: the per-occurrence limit answers “How much can one claim cost the insurer?” The aggregate limit answers “How much can the whole policy year cost the insurer?” That second question is where repeated losses become expensive. A year with five smaller claims can be more damaging than one memorable loss, because each claim can nibble away at the same cap.
How the aggregate limit works, step by step
The mechanics are easier to follow if you trace one policy period from start to finish. Here is the usual sequence, though policy language can change the details.
- Check the policy period dates. Confirm the start and end date, such as a 12-month term. Verify that the aggregate resets only when a new policy period begins. A problem is assuming a calendar year reset when the policy renews on a different date.
- Identify the aggregate type. Find whether the policy has a general aggregate, a products-completed operations aggregate, or both. Verify the declarations page and definitions. A problem is treating all claims as if they draw from one identical bucket when the policy has separate buckets.
- Match each claim to the right bucket. Classify the loss by policy wording, not by intuition. A customer injury at the premises may hit the general aggregate; a claim involving a completed job may fall under products-completed operations. A problem is putting a completed-work claim into the wrong category and misreading remaining capacity.
- Apply the per-occurrence limit first. Check how much the insurer pays for that single loss, up to the claim’s allowed maximum. Verify that no payment exceeds the per-occurrence cap. A problem is thinking the aggregate controls the first dollar of payment when the per-occurrence limit usually sets that ceiling.
- Subtract the paid amount from the aggregate. Track the amount actually paid on the claim, not the amount alleged in the complaint. Verify the insurer’s payment ledger or claim summary. A problem is counting the entire lawsuit demand instead of the settled or paid amount.
- Repeat for every covered claim in the term. Keep a running total across all payments in that bucket. Verify after each claim whether the remaining balance is enough for another loss. A problem is reviewing the policy only when a large claim arrives.
- Watch for defense costs treatment. Determine whether legal defense expenses reduce the aggregate or are paid outside the limit. Check the policy wording and ask a broker, attorney, or other qualified adviser if it is unclear, because this can differ by form and jurisdiction. A problem is assuming defense is always separate when some policies erode the limit with legal costs.
- Recalculate after renewal. At the new policy period, confirm whether the aggregate resets or whether any claims-made features affect timing. Verify the effective date before relying on a fresh limit. A problem is assuming a loss reported late will draw from the new year automatically.
The cleanest proof that the system is working is a written claim ledger that shows each payment, the bucket it came from, and the remaining balance. If the ledger is missing or vague, the business is guessing about its exposure.
What is the difference between a per-occurrence limit and a general aggregate?
The per-occurrence limit caps one covered claim; the general aggregate caps all covered claims combined in the policy period. They answer different questions, and confusing them is a common way businesses misjudge their protection.
A policy might pay the full per-occurrence amount on a single loss and still have plenty left in the aggregate. Or it might pay several smaller losses that never come close to the per-occurrence ceiling, then quietly run out of aggregate room. The first limit controls the size of one payment, while the second controls the total amount the insurer will spend over the year.
The general aggregate limit is the broader cap on many standard liability claims. In commercial general liability forms, it often applies to bodily injury, property damage, and personal and advertising injury claims, subject to exclusions and policy wording. The products-completed operations aggregate is narrower and is tied to liability from products sold or work finished. A contractor who completes a job in March and sees a claim in November may find that the loss falls under this separate bucket, not the general aggregate.
One practical test helps: ask whether the claim arises from ongoing operations, a finished job, or a product after transfer of possession. That classification often decides which aggregate is touched. If the answer is unclear, the policy language controls, not the business’s internal labels.
What happens when the aggregate gets used up
When the aggregate is used up, later covered claims may be unpaid by the insurer even if the policy period has not ended. That is the underinsurance problem many owners discover only after a bad month or a repeated-loss year.
The consequence is straightforward but painful. A business can still face lawsuits, settlements, or repair demands after the limit is gone. The policy may continue to exist on paper, but the financial protection for that bucket is exhausted. If there is a separate products-completed operations aggregate, that bucket might still have room even when the general aggregate is empty, or the reverse may be true.
This is why one large claim can hurt twice. First, it consumes the per-occurrence limit. Then it may drain a large share of the aggregate, leaving less protection for the rest of the year. A second claim can arrive while the first is still being defended, and if defense costs erode the limit, the remaining balance can shrink faster than expected.
The most useful thing to monitor is not the original policy limit but the remaining limit after each payment. A business with a 12-month policy should know the remaining aggregate after every claim report, settlement, or judgment payment. Without that running total, the business is steering by last year’s assumptions instead of current numbers.
The mistakes people actually make with aggregate limits
The most common mistake is treating the aggregate like a separate pot for each claim. The consequence is underestimating how fast repeated losses can drain the policy. The correct approach is to track one shared balance across the policy period and, where applicable, separate balances for separate buckets. If the wording is unclear, a broker or qualified adviser should review it before a loss arrives.
Another mistake is ignoring products-completed operations coverage. The consequence is thinking a finished-job claim still has full room under the general aggregate when it may be drawing from a different limit altogether. The correct approach is to identify whether the loss comes from ongoing operations, completed work, or a product after sale.
A third mistake is forgetting that defense costs may reduce the limit. The consequence is discovering less aggregate left than expected after legal fees are paid. The correct approach is to read the policy wording on defense expense treatment before a claim arrives, not after, and to confirm it with a qualified adviser if needed.
A fourth mistake is assuming every claim payment counts the same way. The consequence is double-counting a reserved amount or counting an alleged demand that never gets paid. The correct approach is to track actual insurer payments and settlements, because those are what usually erode the limit.
A fifth mistake is renewing the policy without checking whether the new term resets the aggregate in the same way. The consequence is confusion about what losses belong to which year. The correct approach is to confirm the effective dates and how late-reported claims are handled under the policy form, especially if the business has a claims-made component.
If the business has a history of several claims a year, or if one incident could trigger multiple related claims, this is the point where a broker, risk adviser, or attorney familiar with the policy language can be helpful.
When the standard reading of the limit does not fit
The standard reading needs adjustment when the policy form is unusual, the business is heavily product-driven, or the claim pattern is not ordinary. Some policies bundle exposures differently, and some jurisdictions use different forms or required wording.
Completed work is the main exposure: A contractor or installer may see most losses land in the products-completed operations aggregate, not the general aggregate — review which bucket applies before assuming the main limit is still intact.
Defense costs reduce limits: If legal expenses erode the aggregate, a claim that settles near the per-occurrence cap can still leave less room for later losses — check the policy wording line by line.
Multiple claims arise from one event: A fire, contamination, or batch issue can create several related claims — one event may exhaust the aggregate faster than a single-file loss would suggest.
The business sells products across time: Repeated shipments or installations can spread exposure over months — a separate completed-operations bucket may matter more than the general aggregate.
The policy has endorsements that change the form: An endorsement can alter how limits apply — verify any added clause before relying on the declarations page alone.
The business is close to renewal or cancellation: Timing can decide which policy year pays — confirm which policy period receives the claim before making assumptions about remaining limit.
In each case, the issue is not that the aggregate limit stops working. The issue is that the policy structure determines which bucket is drained, when it is drained, and whether defense costs count against it.
What a careful review should show on the declarations page
A careful review should show the per-occurrence limit, the general aggregate limit, and any products-completed operations aggregate in plain view. If the declarations page does not clearly display those figures, the policy language that defines them becomes even more important.
The review should also show the policy period, because an aggregate limit usually resets only when a new term begins. A 12-month policy period is common, but the exact dates matter more than the label. The review should identify whether the form is occurrence-based or claims-made, because that changes when a claim is tied to a policy year.
A good result is not “I think it is enough.” A good result is a written understanding of which claims erode which limits, what defense costs do to the balance, and how much remains after each payment. The business should be able to answer, in a sentence, how much of the annual cap is already spoken for.
For broader policy-setting decisions, the hub on policy decisions and buying guidance can sit above this page. This page’s job is narrower: to explain the cap itself so the next policy conversation is better grounded.
What does aggregate limit mean?
An aggregate limit is the total amount an insurer will pay for covered claims during the policy period. It is a shared ceiling, not a per-claim allowance, so each paid loss reduces what remains for later claims in the same term.
How is an aggregate limit different from a per-occurrence limit?
A per-occurrence limit applies to one claim or one incident, while an aggregate limit applies to all covered claims combined during the policy period. A single claim can be capped by the per-occurrence limit and still leave room in the aggregate, or several smaller claims can exhaust the aggregate without ever reaching the per-occurrence cap.
Can one claim use up my aggregate limit?
Yes, if the claim is large enough and the policy’s aggregate is modest, one covered claim can consume a large share or even all of it. That depends on the claim size, the per-occurrence limit, and whether defense costs also reduce the limit.
Drafted with AI; not yet reviewed by a person.
