Coverage Explained

The Products-Completed Operations Aggregate Explained

A worker shoveling and spreading fresh concrete across a rebar-reinforced deck — concrete contractor insurance

General liability does not carry one single limit — it carries several, and the one tied to your finished work is the products-completed operations aggregate. It is a separate annual cap, distinct from the general aggregate that answers your on-site claims, and the losses on the work you leave behind draw against it. For a concrete contractor, it is the limit that matters most.

This post explains what the products-completed operations aggregate is, how it differs from the general aggregate, why completed-operations claims erode this specific bucket, and why an umbrella sits above it for a concrete business. The short version: your finished installation is “your work,” and the aggregate behind it is a distinct pool of limit worth knowing rather than assuming.

General liability carries more than one limit

The structural fact most owners miss is that a general liability policy does not have a single cap. It has several limits working at once — a per-occurrence limit that caps any one claim, and separate aggregates that cap total payouts over the policy term. Understanding which claim draws against which limit is what turns a policy from a stack of numbers into something you can actually reason about.

For a concrete installation contractor, the two aggregates are what matter most. One answers the claims that happen while the job is running; the other answers the claims that arise from work you have already finished. They are separate buckets, and a claim draws against one or the other depending on where in the life of the job the harm arises. Knowing the difference is the whole point of this post, because for concrete the two buckets are not used equally.

The general aggregate versus the completed-operations aggregate

The general aggregate is the annual cap for your on-site, in-progress claims — the premises-and-operations losses that happen while the work is underway. A member of the public hurt around your pour, a blowout that damages a neighbor’s property, a delivery driver injured on the site: those are ordinary general liability claims, and they draw against the general aggregate.

The products-completed operations aggregate is a separate annual cap for claims arising from work you have already finished. A slab, footer, driveway, or foundation you placed that fails downstream, after the job is done, and injures someone or damages property draws against this bucket — not the general one. The two aggregates are distinct pools of limit, and the whole reason completed operations has its own cap is that claims on finished work behave differently from claims on work in progress. For a concrete contractor, that separation is not a technicality: it is the reason the completed-operations bucket is the one to watch.

How the general-liability limits stack for concrete — two aggregates with an umbrella above A limit-stack diagram in three parts. At the top, an umbrella liability band sits above both aggregates. Below it, two boxes show the two general-liability aggregates: on the left, the general aggregate, the annual cap for on-site premises-and-operations claims while the job is running; on the right, the products-completed operations aggregate, a separate cap for the work left behind after the pour. Arrows lead up from both boxes to the umbrella band, and a line at the bottom reads completed-operations claims erode their own bucket first. No dollar amounts, limits, or figures are shown — the diagram shows the structure, not numbers. How the limits stack — two aggregates, umbrella above Umbrella liability sits above both aggregates General aggregate The annual cap for on-site, in-progress premises-and-ops claims while the job is running. Products-completed operations aggregate A separate annual cap for the work you leave behind — the finished slab, footer, or foundation. Completed-operations claims erode their own bucket first.
Two separate aggregates with an umbrella above — for a concrete contractor, the completed-operations bucket is the one the serious downstream losses actually draw against.

Why completed-operations claims erode this specific bucket

The reason a concrete failure draws against the products-completed operations aggregate comes straight from the form. In the standard ISO commercial general liability coverage form — the one most policies start from, in ISO’s system usually the occurrence version known as CG 00 01 — the products-completed operations hazard covers bodily injury and property damage arising out of “your work” away from your premises, after the work is complete and has left your control.

The phrase to hold onto is “your work.” A concrete contractor performs work — you pour, place, and finish concrete and leave the finished installation behind. That finished slab, footer, or foundation is “your work” in the policy’s language, so when it fails downstream and causes a serious third-party claim, the loss is routed to the products-completed operations hazard, and it draws against that hazard’s aggregate. This is the completed-work mechanism — it turns on the concrete you install and leave behind — and for a concrete business it is the heart of why the aggregate matters at all: the bucket exists to answer the exposure that defines the trade.

Real-World Scenario: A crew pours and finishes the foundations and flatwork on a commercial project and closes the job out. Well after the work is done, a structural section fails as the ground moves through repeated freeze-and-thaw cycles, and the resulting third-party property-damage and bodily-injury claim is serious. Because the harm arises from finished work — “your work” away from the premises after completion — the claim draws against the products-completed operations aggregate, not the general aggregate that answers the on-site claims. The contractor whose completed-operations aggregate was set for the work being done, and who carried an umbrella above it, is in a very different position than the one who never looked at the bucket the loss would actually hit.

Confirm the hazard is not excluded first

Before the size of the aggregate matters at all, the hazard behind it has to be present. Some policies can carve out the products-completed operations hazard with an exclusion endorsement — in ISO’s system, a form along the lines of CG 21 04 — which would remove the very coverage a concrete contractor most needs. If the hazard is excluded, the aggregate is beside the point, because the coverage it caps is gone.

That makes the check a two-step one: first confirm the products-completed operations hazard is actually in your policy and not excluded, then confirm the aggregate behind it is set for the work you do. It is an easy thing to miss on a policy bought on price and a hard thing to discover after a failure. How this is written varies by carrier, so read the form rather than assume — the point of naming the coverage is so you can verify it is there.

Why an umbrella sits above the aggregate

Because the products-completed operations aggregate is separate and finite, a serious completed-operations claim can test it — and this is a class where that bucket actually gets used. When the work you leave behind could produce a claim large enough to reach the primary limit, umbrella liability sits above the primary policy and adds limit over both aggregates, including the completed-operations one.

An umbrella does not replace the aggregate, and it does not change what the primary form covers or how the trigger works. It extends the height of coverage over the primary policy — more room above the bucket the completed-operations losses draw against. For a concrete contractor with real completed-work exposure, or one whose contracts demand higher limits, the umbrella is often the layer that makes the whole structure adequate. How much sits above, and how it is arranged, depends on the work and the contracts, which is why we build it to the operation rather than quote a figure in the abstract.

The truck seam: what this aggregate does not cover

The products-completed operations aggregate is a general liability limit, and it answers the harm your finished work causes — not your vehicles. A boom pump truck and a ready-mix mixer fleet are covered under commercial auto, which answers auto liability and physical damage on the trucks themselves. When a claim involves a truck, it runs to auto; when a claim involves your finished concrete, it runs to completed operations and draws against this aggregate. Keeping that seam clear matters, because the two lines answer different exposures and carry different limits.

Set the aggregate for the work you actually do

The takeaway is simple: for a concrete contractor, the products-completed operations aggregate is the limit that answers the work you leave behind, and it is separate from the general aggregate that answers your on-site claims. Confirm the hazard is present and not excluded, make sure the aggregate is set deliberately for your completed-operations exposure rather than left at a default, and layer an umbrella above it when the work could produce a claim large enough to test the primary limit. How the trigger is written matters here too, so it is worth reading occurrence versus claims-made and the full picture of completed operations alongside this. When you are ready, start a quote, read the full general liability page, or browse the coverage overview to see where each limit sits. For what drives the cost behind these limits, see what drives concrete insurance cost.

The bottom line

General liability does not carry one single limit — it carries several, and the one tied to your finished work is the products-completed operations aggregate. It is a separate annual cap, distinct from the general aggregate that answers your premises-and-operations claims, and completed-operations losses erode this specific bucket. In the standard ISO commercial general liability form, usually the occurrence version known as CG 00 01, the products-completed operations hazard attaches to "your work" — the finished slab, footer, or foundation — so a downstream failure draws against this aggregate, not the general one. For a concrete contractor that is the limit to watch, and when the work you leave behind could produce a claim large enough to test it, an umbrella sits above the primary policy and adds limit over it. Limits vary by carrier, so confirm how yours is set before a loss.

Frequently asked questions

What is the products-completed operations aggregate?

It is a separate annual limit inside your general liability, specific to claims arising from your completed work. General liability does not carry one single cap; it carries several, and completed-operations losses draw against this particular bucket rather than the general aggregate. For a concrete contractor, that means a slab, footer, or foundation that fails downstream and injures someone or damages property erodes the products-completed operations aggregate. It is the limit tied to "your work" — the finished installation — which is why it is the one worth watching in this trade.

How is it different from the general aggregate?

The general aggregate is the annual cap for your on-site, in-progress claims — premises-and-operations losses that happen while the job is running. The products-completed operations aggregate is a separate cap for claims arising from work you have already finished. They are two distinct buckets, and a claim draws against one or the other depending on whether it comes from ongoing operations or from your completed work. For a concrete contractor, the completed-operations bucket is the one that tends to get used, because the work fails downstream after the job is done.

Why do completed-operations claims erode this bucket?

Because the standard general liability form routes them there. In the standard ISO coverage form, usually the occurrence version known as CG 00 01, the products-completed operations hazard covers bodily injury and property damage arising out of "your work" away from your premises, after the work is complete. A concrete failure that surfaces downstream is exactly that kind of claim, so it draws against the products-completed operations aggregate rather than the general aggregate. Editions vary by carrier, so confirm how your form is written, but this is the bucket completed-work losses are built to erode.

Why does an umbrella sit above this aggregate?

Because the aggregate is separate and finite, and a serious completed-operations claim can test it. An umbrella liability policy sits above the primary general liability and adds limit over its aggregates, including the products-completed operations aggregate. It does not replace the aggregate or change what the primary form covers; it extends the height of coverage over it. For a concrete contractor whose finished work could produce a claim large enough to reach the primary limit, an umbrella is the layer that adds room above the bucket. Limits and structure vary by carrier.

Can the completed-operations hazard be excluded from my policy?

Yes, and that is the check worth running. Some policies can carve out the products-completed operations hazard with an exclusion endorsement — in ISO’s system, a form along the lines of CG 21 04 — which would remove the very coverage a concrete contractor most needs. If the hazard is excluded, the aggregate behind it does not matter, because the coverage is gone. Confirming the hazard is present and not excluded, and that the aggregate is set for your work, is a review worth doing before a loss. Forms vary by carrier.

How high should my products-completed operations aggregate be?

There is no single right number, because it depends on the work you do, the contracts you sign, and the exposure your finished installations carry — and we will not quote a figure in the abstract. What matters is that the aggregate is set deliberately for the completed-operations exposure of your operation rather than left at a default, and that an umbrella sits above it when the work could produce a claim large enough to test the primary limit. Reading how your policy sets this aggregate against the work you actually do is the check to run before binding.

About the author

Nate Jones, CPCU

Nate Jones, CPCU, is the founder of Wexford Insurance and Concrete Guard Insurance, a specialty insurance agency placing concrete contractor coverage in 48 states across a 23-carrier specialty panel. He structures general liability limits for concrete contractors around the products-completed operations aggregate — the separate bucket the completed-work losses actually draw against — and reads whether it is set for the finished slabs, footers, and foundations a crew leaves behind rather than left to a default. He shows owners why this aggregate is distinct from the general aggregate, why a downstream failure erodes it, and why an umbrella sits above it when the work could produce a claim large enough to test the primary limit. Connect via the Concrete Guard Insurance quote form or call 317-942-0549.

Insure your concrete operation with a CPCU-led agency

Tell us how you work — an install crew, a pump truck, a ready-mix fleet, or all three — and we will market it to carriers that write the class.