Designated Construction Project(s) General Aggregate Limit
Per-project aggregate — protects you from limit erosion by claims on the sub's other jobs.
What it actually does
CG 25 03 establishes a separate general aggregate limit *per construction project*. Without it, a sub's policy aggregate is shared across all of that sub's jobs — meaning if Job A has a $1M claim, the aggregate left for your Job B is $1M less.
With a per-project aggregate, each project gets its own dedicated aggregate. This is critical on long-running or high-risk projects where you want certainty that limit erosion on someone else's job won't drain coverage you're relying on.
Many subcontracts on commercial projects ($5M+) require per-project aggregates explicitly. The endorsement schedules each project; verify your project is listed.
Verification checklist
- 01Confirm the schedule includes your specific project name and address.
- 02Verify per-project aggregate limits meet subcontract requirements (often equal to the per-occurrence limit).
- 03Check that the sub's broker hasn't substituted a 'designated location' aggregate (CG 25 04) when 'designated project' is required.
- 04Confirm coverage continues through the products-completed-operations period.
Common mistakes
- ·Confusing per-location aggregate (CG 25 04) with per-project aggregate (CG 25 03).
- ·Skipping the aggregate review when the sub's general aggregate looks high — the question is what's left after their other projects.
- ·Missing that CG 25 03 may require a separate completed-ops endorsement to extend the per-project treatment past completion.
Verify CG 25 03 on every sub's COI automatically
Paste your vendor list, upload their COIs, get back a per-vendor gap report — including whether they have CG 25 03 attached. Free, no signup until you want monitoring.
Run a free batch audit →