A per project aggregate endorsement gives each construction project its own general aggregate limit, so claims on one job stop eating the limit that protects every other job. The ISO general liability forms are CG 25 03 for a designated construction project and CG 25 04 for a designated location, both in the 05 09 edition. Neither one gives you a separate completed operations aggregate, which is the gap most certificate reviews miss. Upload a certificate above and the AI reads the endorsement form numbers off the page.
Last updated August 2026
Upload your certificates of insurance
Drop files here or click to upload
Up to 50 files
Uploading...
The two ISO general liability endorsements that create a separate aggregate, plus the default they replace. The wording for CG 25 03 05 09 and CG 25 04 05 09 was read directly from the published ISO forms, so the coverage parts and carve outs below are quoted rather than summarized.
| Form | Official ISO title | Separate limit applies per | Completed operations included |
|---|---|---|---|
| CG 25 03 05 09 | Designated Construction Project(s) General Aggregate Limit | Each designated construction project shown in the schedule, for ongoing operations at that project | No. Products-completed operations damages are carved out and continue to erode the single policy-wide Products-completed Operations Aggregate Limit |
| CG 25 04 05 09 | Designated Location(s) General Aggregate Limit | Each designated location shown in the schedule, for operations at that location | No. The same carve out applies, worded identically |
| CG 00 01 Section III | Limits Of Insurance in the coverage form itself | Nothing. One General Aggregate Limit is shared across every job the insured performs in the policy year | The Products-completed Operations Aggregate is already separate from the General Aggregate under the unendorsed form |
| Carrier manuscript forms | Titles vary by carrier | Varies. Some are blanket, applying automatically to any project required by written contract | Varies. Read the form rather than assuming it matches CG 25 03 |
A contract can demand a per project aggregate in one sentence. Confirming the vendor actually bought one takes the endorsement page, because the certificate has nowhere to put the answer.
The certificate grid carries two endorsement columns, ADDL INSR and SUBR WVD, and a set of limit boxes. There is no field that says this aggregate is per project. The claim can only appear as free text somebody typed into the Description of Operations box, which is an assertion rather than proof.
Without the endorsement, one General Aggregate Limit covers every job the contractor runs that policy year. A vendor showing a $2,000,000 aggregate in March may have $300,000 left by October because of claims on work you never saw. The certificate shows the limit purchased, never the limit remaining.
This is the misreading that matters most. Both CG 25 03 and CG 25 04 explicitly exclude damages included in the products-completed operations hazard from the separate aggregate. Those claims keep drawing on one policy-wide Products-completed Operations Aggregate, shared across every project, for as long as the coverage lasts.
CG 25 03 attaches the limit to a designated construction project and speaks about ongoing operations there. CG 25 04 attaches it to a designated location, defines that term, and drops the word ongoing. A contract that asks for a per project aggregate and receives CG 25 04 has been answered with a different form.
COISoftware reads the endorsement pages behind a certificate, records which per project aggregate form is attached and in what edition, and checks it against the requirement recorded for that contract.
The two forms look similar and are routinely swapped. Each is captured by its own number, so a contract requiring a per project aggregate is not quietly satisfied by a per location form that attaches the limit to premises instead of to your job.
Both current forms carry the 05 09 edition and the ISO 2008 copyright. Older editions and carrier manuscript versions behave differently, so both halves of the number are recorded and you can pull every vendor sitting on something other than the current form.
Because the separate aggregate never covers products-completed operations, a vendor can hold CG 25 03 and still share one completed operations limit with every other job. That distinction is recorded against the vendor rather than left for someone to notice at claim time.
With no checkbox for this requirement, the claim usually hides in free text. That block is read as language rather than skipped, so a typed per project aggregate statement is captured and matched against whether an endorsement actually sits behind it.
Record the requirement once per contract type. If your master subcontract calls for a per project aggregate and the packet contains no CG 25 03, the vendor is flagged short while you can still hold the mobilization rather than after a loss.
Endorsements get dropped at renewal and nobody downstream is told. Each renewal packet is compared against the prior year, so a per project aggregate that quietly disappears surfaces as an exception instead of a discovery during a claim.
Five checks, in the order that finds problems fastest.
The General Aggregate box on an ACORD 25 shows the limit the policy was written with. It does not say whether that limit is shared across every job, and it never shows how much of it is already spent. Two vendors with identical certificates can have very different amounts of real capacity.
Request CG 25 03 by name if your contract wants a per project aggregate, or CG 25 04 if the exposure is a fixed location rather than a construction project. Naming the form is what gets it produced. A request that only says please confirm the aggregate is per project comes back as another sentence typed on another certificate.
The form number prints at the top of the endorsement beside the words COMMERCIAL GENERAL LIABILITY and again in the footer next to the ISO copyright line. Confirm you are holding CG 25 03 05 09 or CG 25 04 05 09 rather than a carrier manuscript form with a similar name.
Both forms are scheduled. The separate limit applies only to the projects or locations written into the schedule. An endorsement attached to the policy with a blank schedule, or a schedule listing three other jobs, does nothing for you. Look for your project name, address or contract number on the page.
Neither form gives you a per project completed operations aggregate. If your exposure is long tail construction defect work, the per project aggregate solves the ongoing operations problem and leaves the completed operations problem exactly where it was. That usually needs a higher limit or a project specific policy instead.
Most pages about this endorsement paraphrase it. Below is what the two ISO forms say, transcribed from the published form documents, so you can compare them yourself.
Transcribed from the form published in the Independent Insurance Agents of Texas form library. It carries the Insurance Services Office 2008 copyright and modifies the Commercial General Liability Coverage Part only. Paragraph A is the operative grant, and it applies to sums that can be attributed only to ongoing operations at a single designated construction project shown in the schedule:
A separate Designated Construction Project General Aggregate Limit applies to each designated construction project, and that limit is equal to the amount of the General Aggregate Limit shown in the Declarations.
Read that second clause carefully, because it is where most contract drafting goes wrong. The endorsement does not let you pick a number. Each project limit is set equal to the General Aggregate Limit already on the policy. A contractor carrying a $2,000,000 general aggregate who adds CG 25 03 gets $2,000,000 per designated project, not a separate amount you negotiated.
Paragraph A.2 states the Designated Construction Project General Aggregate Limit is the most the insurer will pay for the sum of all damages under Coverage A, and then removes one category:
except damages because of "bodily injury" or "property damage" included in the "products-completed operations hazard"
Paragraph C says the same thing from the other direction. Payments for damage inside the products-completed operations hazard reduce the Products-completed Operations Aggregate Limit, and reduce neither the General Aggregate Limit nor the Designated Construction Project General Aggregate Limit. So the separate project limit covers the job while it is being built. Once the work is complete and a defect claim arrives years later, that claim draws on one policy-wide completed operations aggregate shared with every other project the contractor ever finished. If your risk is construction defect rather than a jobsite injury, a per project aggregate does less for you than the phrase suggests.
Paragraph B handles sums that cannot be attributed only to ongoing operations at a single designated project. Those payments reduce the General Aggregate Limit or the Products-completed Operations Aggregate Limit, whichever applies, and they do not reduce any Designated Construction Project General Aggregate Limit. The policy keeps its ordinary shared limit for everything outside the scheduled jobs, so the endorsement adds project limits rather than replacing the general one.
Paragraph A.4 is worth knowing at renewal. The Each Occurrence, Damage To Premises Rented To You and Medical Expense limits shown in the Declarations continue to apply, but instead of sitting under the General Aggregate Limit they sit under the applicable project aggregate. The per occurrence limit is not multiplied by the endorsement.
Paragraph D is the provision almost nobody quotes, and it protects the insurer rather than you:
If the applicable designated construction project has been abandoned, delayed, or abandoned and then restarted, or if the authorized contracting parties deviate from plans, blueprints, designs, specifications or timetables, the project will still be deemed to be the same construction project.
A job that stops for eighteen months and restarts does not become a second project with a second aggregate. Neither does a job that is substantially redesigned. On long or troubled projects that is a real limitation, and it is the answer to the common question of whether a multi-phase job earns multiple limits. Under CG 25 03 it does not, unless each phase is separately scheduled.
Transcribed from the same form library, also carrying the ISO 2008 copyright and also modifying the Commercial General Liability Coverage Part only. The structure mirrors CG 25 03 paragraph for paragraph, with two differences that decide which form your contract actually needs.
First, the trigger. CG 25 03 applies to sums attributable only to ongoing operations at a single designated construction project. CG 25 04 applies to sums attributable only to operations at a single designated location. The word ongoing is absent, and the anchor is a place rather than a job. That makes CG 25 04 the right form for an owner or operator with several premises, such as a portfolio of stores, plants or apartment communities, and the wrong form for a general contractor who wants a limit tied to one build.
Second, CG 25 04 uses its paragraph D to define the term instead of dealing with delays:
"Location" means premises involving the same or connecting lots, or premises whose connection is interrupted only by a street, roadway, waterway or right-of-way of a railroad.
That definition is doing real work. Two buildings across an alley from each other are one location and share one aggregate. Two buildings a mile apart are two locations with two aggregates. CG 25 04 carries no abandonment or deviation provision at all, because a location does not stop and restart the way a project does.
Under the unendorsed CG 00 01 coverage form, Section III gives the insured one General Aggregate Limit for the policy period, shared by every job, every location and every claim other than products-completed operations. That is a per policy aggregate. The first vendor to have a bad year spends limit that would otherwise have been available to you.
A per project aggregate replaces that arithmetic for scheduled jobs only. Your project gets its own full limit, claims elsewhere cannot touch it, and claims on your project cannot touch anyone else. What stays shared is the completed operations aggregate and everything outside the schedule. When a subcontract says the general aggregate shall apply per project, this pair of forms is what satisfies it, and the schedule page is the part worth reading.
Some carriers issue a blanket per project aggregate that applies automatically to any project the insured is required by written contract to schedule. These are manuscript forms rather than ISO forms, so the numbers vary and the wording varies with them. A blanket form is genuinely more useful, because nobody has to remember to add your job to a schedule before a loss. It is also the version most likely to differ from what your contract assumed, so read the grant and the carve outs rather than accepting the label. If the endorsement number does not begin with CG, it is not one of the two forms quoted above.
It is a form attached to a general liability policy that gives each scheduled construction project its own general aggregate limit, equal to the general aggregate shown in the Declarations. Claims on one project stop reducing the limit available to the others. The ISO general liability form is CG 25 03.
It means the policy aggregate is measured job by job rather than across the whole policy year. Without it, one shared general aggregate covers every project the contractor runs, so a bad claim on an unrelated job can leave very little limit for yours. With it, your project holds its own full limit.
CG 25 03, titled Designated Construction Project(s) General Aggregate Limit, currently in the 05 09 edition with the ISO 2008 copyright. The related form CG 25 04, Designated Location(s) General Aggregate Limit, does the same job for premises rather than construction projects.
CG 25 03 attaches a separate aggregate to each designated construction project and applies to ongoing operations there. CG 25 04 attaches it to each designated location and applies to operations at that place. CG 25 03 suits contractors, CG 25 04 suits owners with multiple premises.
A per policy aggregate is the default under CG 00 01: one general aggregate shared by every job for the whole policy period. A per project aggregate gives each scheduled job its own limit of the same size. The difference is whether other people claims can exhaust the limit protecting you.
No. Both CG 25 03 and CG 25 04 expressly exclude damages included in the products-completed operations hazard from the separate aggregate. Those claims continue to erode one policy-wide Products-completed Operations Aggregate shared across every job. This is the most commonly misunderstood limitation of the endorsement.
Usually yes. The insurer is multiplying its aggregate exposure by the number of scheduled projects, so most carriers charge additional premium and some decline it for certain classes. Cost varies with class code, project count and limits, so it is quoted rather than published on a rate table.
You cannot verify it from the certificate face. The ACORD 25 has no field for it. Ask for the endorsement page, confirm the form number reads CG 25 03 or CG 25 04, and check that the schedule actually names your project or location rather than sitting blank.
It is the separate aggregate CG 25 03 creates for each project listed in its schedule. The form sets that limit equal to the General Aggregate Limit shown in the Declarations, and payments against it reduce only that project limit, not the policy general aggregate or any other project limit.
No. Paragraph D of CG 25 03 states that a project which is abandoned, delayed, or abandoned and then restarted, or where the parties deviate from plans, designs, specifications or timetables, is still deemed the same construction project. Multi-phase work does not earn extra limits unless each phase is separately scheduled.
It is a carrier manuscript form that applies a separate aggregate automatically to any project the insured is required by written contract to cover, with no schedule to maintain. It is more reliable in practice than a scheduled form, but the wording is not standardized, so read the grant and its exclusions.
Not as a field. The certificate has limit boxes and two endorsement checkboxes, ADDL INSR and SUBR WVD, and none of them record how the aggregate applies. Any mention appears only as free text in the Description of Operations box, which is a statement rather than evidence of an endorsement.
A shared aggregate is the unendorsed default, where one general aggregate covers every project a contractor performs in the policy year. It is a problem because the limit shown on a certificate is the limit purchased, not the limit remaining, and claims you never hear about spend it.
Most large construction subcontracts, owner-contractor agreements on sizeable builds, and public works contracts. The clause usually reads that the general aggregate shall apply on a per project basis. Smaller service and vendor agreements rarely ask for it, since the exposure does not justify the premium.
No. Paragraph A.4 of CG 25 03 keeps the Each Occurrence, Damage To Premises Rented To You and Medical Expense limits exactly as shown in the Declarations. It only changes which aggregate those limits sit beneath. A single large loss is still capped by the same per occurrence figure.
Every ISO endorsement form that shows up on a certificate.
CG 20 10, CG 20 37 and the rest of the CG 20 series.
CG 24 04, CG 24 53 and the workers compensation waiver form.
CG 20 01 and CA 04 49, quoted from the issued forms.
Project-level insurance requirements, tracked automatically.
Why general contractors require a per project aggregate.
How the two limit types interact on a certificate.
No credit card required to start your free trial.
Start tracking vendor certificates of insurance and never miss an expiration.
USD
per month
billed as
$288 yearly
Choose speed vs accuracy when extracting
| Base AI Faster | 2,500 pages |
| Pro AI Best accuracy | 500 pages |
Scale COI compliance across your whole team with automated reminders.
USD
per month
billed as
$888 yearly
Choose speed vs accuracy when extracting
| Base AI Faster | 10,000 pages |
| Pro AI Best accuracy | 2,000 pages |
Enterprise‑grade COI tracking, security, and controls.
USD
per month
billed as
$ yearly
Choose speed vs accuracy when extracting
| Base AI Faster | pages |
| Pro AI Best accuracy | pages |
Custom workflows and deployment for AI automation at scale
