COI term
Products & completed operations
The part of the sub's general liability that answers after their work is finished. It carries its own aggregate, separate from the general one.
Key takeaways
- It covers damage arising out of the sub's work after that work is complete and off their own premises. During the job you are in ongoing operations; after handover you are here.
- It has its own aggregate, printed on the ACORD 25 as a separate line from the general aggregate. Same policy, different bucket — and a sub can have an untouched general aggregate while this one is already spent.
- A per-project aggregate endorsement does not extend to it. CG 25 03 carves out a fresh general aggregate for a designated project and expressly leaves products-completed operations on the shared, policy-wide limit.
- Requiring the coverage and collecting CG 20 10 alone gets you neither. That form reaches ongoing operations; CG 20 37 is the one that makes you an additional insured in completed operations.
By the Sealinn team · 4 min read · Updated July 2026 · Written for general contractors
When the coverage takes over
The general liability form defines a "products-completed operations hazard", and the definition is the useful part. It picks up bodily injury and property damage arising out of the subcontractor's work once that work is finished and once the loss happens away from premises the sub owns or rents. It expressly does not include work that is still under way, or work at the site that has not yet been put to its intended use.
So the same crew, the same policy and the same mistake fall into two different places depending on when the damage shows up. A pipe joint that fails while the plumber is still on site is ongoing operations. The same joint failing eighteen months after the owner moved in is completed operations — and that is the claim that arrives long after everyone has left, addressed to the general contractor.
Its own aggregate, and what that means for you
Look at the limits column on the ACORD 25. Under the general aggregate there is a separate line — products-completed operations aggregate. It is not a subdivision of the general aggregate; it is a parallel one. A sub whose general aggregate is untouched can still have this bucket half-consumed by a defect claim from a job three years ago, and the certificate shows you the limit, never the remaining balance.
That is the same blind spot the per-project aggregate exists to close, and here is the wrinkle worth knowing: it does not close it. The designated-construction-project endorsement gives a project its own general aggregate, and it states that damages inside the products-completed operations hazard are not covered by that project limit — they remain subject to the policy-wide products-completed operations aggregate, shared with every other job the sub has ever finished. A GC who bought a per-project aggregate and assumed the whole exposure was ring-fenced has ring-fenced the half that surfaces during the job, not the half that surfaces afterwards.
The endorsement most often collected is the wrong half
A subcontract requiring "additional insured status including products and completed operations" is answered, more often than not, with a CG 20 10 — which reaches ongoing operations only. The completed-operations form is CG 20 37, and since the 1993 editions the two have been separate documents on purpose. Requiring both and checking that both arrived is a two-minute job now and an uninsurable one later.
The tail is the whole reason it is in your subcontract
Subcontracts usually require this coverage to be maintained for some number of years after final completion. That clause exists because construction-defect claims are slow: water intrusion, settlement, a roof detail that fails in the fourth winter. The statute of repose in your state sets the outside edge, and the number in your contract is somebody's attempt to sit inside it.
Whether the requirement is meaningful depends on how the sub's policy is written. On an occurrence policy the policy in force when the damage happened responds, even if the sub has since changed carriers — so the tail requirement is really about the sub not going bare in the meantime. On a claims-made policy it is a different problem entirely: coverage attaches when the claim is reported, so a sub who lets the policy lapse has no coverage for their own past work unless they bought an extended reporting period. That distinction decides whether your tail clause is enforceable in practice or decorative.
Requiring the coverage, the endorsement and the years
- Require the coverage and the endorsement separately. "Products and completed operations coverage" and "additional insured for completed operations per CG 20 37" are two different asks, and a sub can honestly satisfy the first while giving you nothing on the second.
- Name the tail in years, tied to final completion, and pick a number you can defend against your state's statute of repose rather than a round one copied from another contract.
- Ask what happens if they change carriers, particularly on claims-made policies. The answer you want is an occurrence policy; the answer you can live with is a documented extended reporting period.
- Keep the certificate after the job closes. The exposure outlives the project by years, and a certificate you cannot produce is the same as coverage you never required — which is the whole argument in the records that survive an audit.
Copy-paste to the sub’s agent
Subject: Products-completed operations aggregate and CG 20 37 — [Project]
Hi [Agent name], We're the general contractor on [Project]. Two questions on [Sub name]'s general liability that the certificate doesn't answer: 1) Is the products-completed operations aggregate shown on the certificate the full limit, or has any of it been eroded this policy period? 2) Our subcontract requires additional-insured status including completed operations. Could you confirm which form is on the policy and send a copy — CG 20 37, or the blanket form your carrier uses if it reaches completed operations? If there's a per-project aggregate endorsement in place, I'd also like to confirm it doesn't change the products-completed operations limit. Thanks, [Your name], [Your company]
What Sealinn does with this line
Sealinn reads the products-completed operations aggregate off the certificate and, if you set a minimum for it, holds the certificate to that minimum — including when the line is missing from the certificate entirely, which is the case this coverage exists for. Set it separately from your general aggregate, because they are separate buckets and a general-aggregate minimum does nothing for this one. Leave it blank and the number is recorded and searchable but not checked, which is the right answer if you have not decided what to require yet.
Where this comes from
- ISO — Commercial General Liability Coverage Form (CG 00 01 occurrence / CG 00 02 claims-made)
- ISO — Additional Insured — Owners, Lessees or Contractors, Completed Operations (CG 20 37)
- ACORD — Certificate of Liability Insurance (form 25)
The claim arrives years after the crew left. The certificate should still be findable.
Sealinn keeps every certificate you ever collected, including after you cancel — which matters most for the coverage whose whole purpose is answering later.
