Commercial liability insurance policy design and terms

What Is a Per-Project Aggregate on Contractor Liability Insurance?

October 22, 2026 - By Admin

Last updated: October 22, 2026

Table of Contents

Key Takeaways

A per-project aggregate is a separate limit for one named project, not the whole policy.
It can help when one job is more likely to generate several claims.
It works by assigning claims from one project to a separate bucket first.
A contractor should check the contract and policy wording with a qualified insurance professional before relying on it.

A per-project aggregate on contractor liability insurance is the part of a contractor general liability policy that puts a separate limit on one job so that claims from that project do not drain the limit available to other jobs. For a contractor trying to keep one problem job from poisoning the rest of the year, that is the core idea of what is a per-project aggregate on contractor liability insurance.

This article is information, not financial advice. A qualified insurance adviser should review your own policy language, contract terms, and state rules before you rely on any limit structure.

Who this applies to, and what I am assuming

A per-project aggregate matters most to contractors who carry a commercial general liability policy and work on more than one job at a time, especially when owners, lenders, or general contractors ask for a project-specific limit. I am assuming the reader already knows the basic idea of liability insurance: a claim can eat into the policy’s available limit, and once that limit is exhausted, the policy stops helping on covered losses.

I am also assuming the reader is dealing with one of three real-world setups: a standard contractor general liability policy, an endorsement that changes how the aggregate applies, or a wrap-up policy structure tied to one project. Those are not the same thing, even if people in the field use the words loosely.

This is not the page for figuring out every limit on a general liability policy or for learning how to read the whole contract line by line. It is narrower: what “per-project aggregate” means, why it shows up in contractor work, and when it changes the way claims are counted.

If the policy has already been issued and the question is how a specific claim will be handled, that is the point to get qualified help from an adviser or coverage lawyer. A single sentence in an endorsement can change the result.

What is a per-project aggregate on a contractor general liability policy?

A per-project aggregate on contractor liability insurance is a separate aggregate limit that applies to losses arising from one named project, instead of letting all project claims share one pool. In plain English, the insurer may treat Project A as having its own cap, while Project B still has its own available limit under the same policy period. If you are unsure how that wording applies, consult a qualified insurance professional.

The term “aggregate” means the most the insurer will pay for a class of claims over a policy term, often 12 months. A “project-specific limit” or project aggregate narrows that cap to one job. The completed operations exposure on a contractor job can still matter here, because property damage or bodily injury tied to finished work may surface after the crew has left the site.

This structure usually appears through a policy endorsement, which is a written change to the policy form. The endorsement may say that claims “arising out of” a particular project are subject to a separate aggregate. That wording matters. “Arising out of” is broader than a claim tied only to a single subcontractor’s mistake, and it can pull in multiple events connected to the same job.

That is why people ask for this feature on larger or riskier jobs. If one project has a cluster of claims, the damage should not automatically consume the aggregate that protects unrelated work elsewhere. The trade-off is cost and complexity: the policy is harder to compare, and the project language can create disputes if the job is not named clearly enough.

Authoritative background on commercial general liability wording can be found through the Insurance Services Office, Inc. forms used in the market, and through insurance department consumer materials that explain endorsements and policy changes. The National Association of Insurance Commissioners also publishes consumer guidance on policy forms and endorsements.

Why contractors ask for it, and when it helps

insurance policy form on clipboard being filled out

A per-project aggregate helps when one job has a higher chance of producing multiple claims than the rest of the contractor’s book. That can happen on a long renovation, a busy site with many trades, or a contract that requires the contractor to take on more exposure than usual. The point is not to make the policy “better” in the abstract; the point is to keep one job from using up the limit that other jobs rely on.

It is especially relevant when contract requirements call for a project-specific limit. Some owners and upstream contractors want evidence that the job itself has its own protection, rather than a shared annual pool. They may ask for a certificate plus an endorsement that names the project. If the policy does not actually contain the separate aggregate, the certificate alone does not create it.

A common situation is completed operations exposure. A roof replacement, a mechanical install, or an exterior envelope project can lead to a claim months after the work is done. If that claim is tied to the named project, the per-project aggregate is what keeps the loss from spilling into the rest of the policy period.

This structure also matters when more than one claim can come from one defect. A single water intrusion issue can trigger several insured events: repair work, interior damage, and third-party injury allegations. A separate project aggregate may contain those losses within the one job, but it does not eliminate them. It only changes where the loss is counted.

The downside is that a contractor can end up with a false sense of security if the endorsement is sloppy. If the project is not described in the schedule, if dates are wrong, or if the endorsement conflicts with the contract, the expected separation may not hold. That is why this is a document-reading problem, not just a marketing-label problem.

How does a per-project aggregate work in practice?

A per-project aggregate works by carving the policy into separate claim buckets for a named project, then tracking claims against that bucket first. The mechanics are usually simple on paper and messy in real life, so the job is to read the schedule, the endorsement, and the declaration page together.

Identify the endorsement that creates the project-specific limit. Verify the form number, the project name, and any schedule reference. If the endorsement is missing or unsigned, the separate aggregate may not exist.
Check whether the project is named with enough detail. Verify the address, project title, owner name, or contract number if the endorsement uses those identifiers. A vague label like “Main Street Project” can cause a dispute if more than one site fits the description.
Read the time trigger for the project aggregate. Verify whether the limit applies only during active construction, during the policy period, or through completed operations for a stated number of years if the policy says so. If the time trigger is unclear, the claim may fall back into the general aggregate.
Look for the coverage part affected. Verify whether the endorsement changes bodily injury, property damage, personal and advertising injury, completed operations, or all of them. If it only changes one part, the rest may still share the policy-wide aggregate.
Map the contract to the policy language. Verify that the project in the contract matches the project in the endorsement. A mismatch in owner name, job number, or location can mean the contract asked for one thing and the policy delivered another.
Ask how claim payments are allocated. Verify whether defense costs erode the same limit, because some policies handle defense differently. If defense costs reduce the aggregate, a modest claim can use more than you expected.
Test the completed operations path. Verify how a loss discovered after substantial completion is classified. If the claim is treated as unrelated to the named project, the separate aggregate may not protect it. If that point is unclear, consult a coverage professional.
Confirm what happens after the project exhausts its bucket. Verify whether the policy then draws from a general aggregate or whether the endorsement changes the relationship entirely. If the policy language is silent, that silence is a warning sign.

The practical sign of trouble is not always a denial letter, because some limits are narrowed long before a claim is denied. Sometimes it is an endorsement that looks helpful but only applies to one coverage part, or only to claims reported within the policy year. Another red flag is an aggregate that sounds project-specific but is actually just a sublimit inside a broader cap. Those are different animals.

What should a contractor check before relying on it?

A contractor should check the contract, the endorsement, and the claim wording before treating the separate aggregate as real protection. If the wording is unclear, a qualified insurance professional should review it. The first check is simple: does the contract actually require a per-project aggregate, or does it merely ask for commercial general liability insurance and proof of a certificate? Those are very different obligations.

Next, verify the exact name of the job in the policy schedule. The wording should match the work being done closely enough that there is no argument over whether the claim belongs to that project. A mismatch in a project title, address, or owner entity can matter as much as the limit itself.

Then check whether the project-specific limit is tied to the general aggregate or replaces it. Some forms create a separate bucket for the project while leaving the policy-wide aggregate in place for other jobs. Others use the endorsement in a narrower way. If a claim on one project can still reduce the general aggregate, the separation is less complete than it sounds.

Also check completed operations exposure. Many contractor claims show up after the work is done, and that is when people discover that the “project aggregate” they thought they had was written only for operations in progress. If the endorsement does not clearly cover completed operations, it may not protect the very claim the contract was worried about.

Finally, check whether the policy uses one project aggregate or a wrap-up policy. A wrap-up policy, such as an owner-controlled or contractor-controlled insurance program, is a different structure altogether. It often covers multiple contractors on one site and can be built for a single project from the start. A per-project aggregate on a standard policy is narrower and usually easier to obtain, but it is not the same thing as a dedicated wrap-up arrangement.

For terminology and structure, the National Association of Insurance Commissioners and state insurance departments often publish plain-language explanations of endorsements and commercial coverage terms. Those materials are useful starting points, but they do not replace the actual policy form.

When should this approach be stopped and reworked?

This approach should be stopped when the policy language does not clearly match the contract or the project. A separate aggregate that cannot be tied to one named job is too ambiguous to rely on.

The endorsement does not name the project: the separate limit may not be traceable to the job that needs protection — get the project identified in writing before work starts.

The contract requires completed operations protection but the endorsement only addresses ongoing work: post-completion claims may still hit the shared aggregate — have the language reviewed and revised.

The schedule uses a different owner, address, or job number than the contract: the insurer may argue the claim belongs to another project or no project at all — align the identifiers first.

The policy says “subject to the general aggregate” in a way that is unclear: the project bucket may be smaller than expected or may not be separate enough — do not assume the brochure version controls.

The job is large enough that one claim could exhaust the project bucket quickly: the per-project aggregate may not solve the real exposure — recheck the contract risk allocation and the broader insurance structure.

The contractor is working under a wrap-up program already: a second project aggregate on a separate policy can create overlap or confusion — coordinate the two programs instead of stacking assumptions.

If any of those apply, the right move is not to guess. It is to have the policy wording, the certificate, and the contract read together by someone who handles commercial liability forms regularly.

Common mistakes that make the limit useless

The most common mistake is treating a certificate of insurance as proof of the limit structure. A certificate can show that coverage exists, but it does not create a per-project aggregate if the endorsement is missing. The fix is to ask for the actual endorsement and schedule, not just the certificate.

Another mistake is assuming “project-specific” means fully isolated from the rest of the policy. In some forms, only part of the coverage is separate, and defense costs may still erode the same pool. The consequence is a faster-than-expected drain on the limit. The better alternative is to read the policy wording for each coverage part.

A third mistake is sloppy project naming. If the endorsement says one thing and the contract says another, the insurer can question whether a claim belongs to the named project. That can turn a simple coverage question into a dispute over identifiers. The fix is to standardize the project description before the endorsement is issued.

A fourth mistake is ignoring completed operations exposure. Contractors often focus on the active jobsite and forget that water intrusion, falling components, or latent defects can show up later. The consequence is a limit structure that looks good on day one but leaves the contractor exposed after closeout. The better alternative is to confirm how post-completion claims are classified.

A fifth mistake is comparing only price and ignoring the endorsement mechanics. A cheaper policy that lacks a usable project aggregate is not a bargain if the contract requires one. The honest alternative is to compare wording, not just premium, and to accept that more specific protection often comes with more conditions.

How does a per-project aggregate differ from a general aggregate?

A per-project aggregate is tied to one project, while a general aggregate applies across the policy period to the whole policy or to all covered jobs. That is the practical difference the reader needs: one limit follows the job, the other follows the policy year.

A general aggregate is broader and simpler. Claims from different jobs can compete for the same pool, so one bad project can reduce what is left for the others. A per-project aggregate tries to stop that spillover by giving the named job its own bucket. The cost is more complex wording and more room for disagreement over what counts as that project.

The two can coexist. A contractor may have a general aggregate for the policy overall and a separate aggregate for a named project under an endorsement. In that case, the question is not which one exists, but which one a claim drains first and whether the policy language says the project loss also counts against the general aggregate.

That is why this is not a generic “more coverage is better” issue. The value of a per-project aggregate depends on the job’s risk, the contract, and the exact endorsement language. For some contractors, it is the right fit. For others, it adds complexity without solving the actual exposure.

For broader context on contractor coverage types, the industry and business-type coverage guides hub is the right place to start.