
If you run more than one job at a time, your single shared general liability aggregate is a hidden risk: one bad claim can quietly drain the limit that's supposed to protect every other project. The per-project aggregate endorsement gives each job its own limit. Here is exactly how ISO form CG 25 03 works and why general contractors insist on it.
A per-project aggregate endorsement makes your general liability aggregate limit apply separately to each construction project instead of sharing one limit across everything. On a standard general liability policy there is a single general aggregate — the most it will pay in the policy year across all your work. If one large claim on Project A erodes that shared aggregate, later projects can be left with reduced or no coverage. The designated construction project general aggregate limit endorsement (ISO form CG 25 03) fixes that by giving each designated project its own full aggregate. General contractors frequently require it, and it lets a contractor meet contract language demanding a specified amount of insurance dedicated to a specific project. Ellie Insurance Group is an independent agency (founded 2014, Tampa, Florida) that shops 100+ carrier markets to add per-project aggregate for contractors who need it.
The core exposure — one claim shouldn't be allowed to drain the limit protecting your other active projects.
General contractors routinely require a per-project aggregate in their subcontract insurance terms.
Big projects concentrate exposure; a dedicated aggregate keeps that project fully protected.
When a GC's risk manager reviews your certificate, per-project aggregate is a common must-have.
May also need the companion CG 25 04 for a per-project completed-ops aggregate.
More concurrent work means more chances for the shared aggregate to be a problem.
It doesn't add a new coverage — it reorganizes how your existing general aggregate applies, which is what makes your certificate limits real per job.
Each scheduled project gets its own general aggregate equal to the policy's general aggregate — claims on one don't erode another.
Lets you satisfy contract language requiring a specified amount of insurance dedicated to a specific project.
A large loss on one job no longer reduces the limits available to your other active work.
The limit a GC sees on the COI is genuinely available to their project, not potentially pre-consumed.
When required, a separate products-completed operations aggregate can also be applied per designated project.
It's a limit-structure endorsement, not new coverage — so its boundaries matter.
More scheduled projects means more dedicated aggregate exposure for the carrier.
Larger, higher-hazard projects carry more exposure and cost.
Each project's separate aggregate mirrors the policy's general aggregate.
Availability of CG 25 03/04 and pricing vary meaningfully by carrier.
Prior GL claims affect both eligibility and cost.
Adding CG 25 04 for per-project completed operations affects premium.
Here is the shared-limit problem in numbers — and how CG 25 03 solves it.
A contractor carries a general liability policy with a $2,000,000 general aggregate and is running three projects in the same policy year. Every certificate shows the full $2M — but there is only one aggregate behind all three.
A serious claim on Project A settles for $1,500,000. That single loss consumes most of the one shared aggregate, leaving only $500,000 for Projects B and C combined — even though nothing went wrong on those jobs. The GCs on B and C thought they had $2M each; in reality they're sharing the remainder.
With a per-project aggregate (CG 25 03), each designated project has its own $2,000,000 general aggregate. The $1.5M loss on Project A comes out of Project A's aggregate only — Projects B and C still have their full $2M each. That's exactly the assurance a general contractor is demanding when it requires per-project limits.
Contracts sometimes ask for both. We read the requirement carefully and endorse exactly what's needed.
Applies a separate general aggregate to each scheduled project. The core per-project aggregate endorsement.
Applies a separate products-completed operations aggregate to designated projects. Used when completed-ops exposure also needs a dedicated limit.
One general aggregate across all operations for the policy year — the default, and the exposure per-project aggregate solves.
Per-project aggregate is an endorsement that modifies the GL aggregate.
Another contract-driven GL requirement GCs demand.
Frequently required in the same contract clause.
The other core piece of contractual risk transfer.
Where per-project aggregate matters most.
How endorsements affect GL premium.
Coverage descriptions and regulatory figures on this page are general summaries reviewed against the references above and are not a statement of coverage, legal advice, or a guarantee of eligibility or price. Last reviewed . Requirements and policy terms change — always confirm current rules with the relevant agency and verify coverage against the actual policy and a licensed agent.
As an independent agency we shop 100+ admitted and surplus-lines carrier markets — so the carrier competes for your business, not the other way around.




































Send us the contract's insurance requirements and your current GL declarations. An Ellie agent will confirm whether you need CG 25 03, CG 25 04, or both, add the endorsement, and issue a certificate that genuinely matches what the general contractor is asking for.