What Is Completed Operations Coverage? (And Why Contracts Require It)

Completed operations coverage is the part of a commercial general liability policy that responds to bodily injury or property damage caused by a contractor's or supplier's work after that work is finished and the crew has left the site. It pays for claims that surface later: a faulty installation that fails months on, a defect that causes damage once the building is in use. Contracts require it because the most expensive claims at a plant or job site often appear long after the work is done, and general liability alone may not cover them once the job closes out.

If you verify certificates of insurance for contractors or suppliers, completed operations is one of the easiest coverages to overlook and one of the costliest to be missing. A certificate can show a healthy general liability limit and still leave you exposed if the products and completed operations aggregate is blank or the coverage was excluded. This guide explains what the coverage does, how it differs from products liability, why your contracts should require it, and exactly where to check for it on an ACORD 25.

What is completed operations coverage?

Completed operations coverage protects against claims arising from a contractor's or supplier's completed work, as opposed to claims that happen while the work is still going on. It is built into the products-completed operations hazard of a standard commercial general liability policy. If a contractor installs a piece of equipment and it fails six months later and injures someone, the ongoing operations portion of the policy no longer applies because the job is done; completed operations is the part that responds. That delayed exposure is exactly why it matters to the business that hired the contractor.

What is the difference between products and completed operations?

Products liability and completed operations are grouped together on a general liability policy but cover different parties. Products liability responds to injury or damage caused by a tangible product a business makes or sells, which is why manufacturers and suppliers carry it. Completed operations responds to injury or damage caused by a service or installation a contractor performed after that work is complete. On the ACORD 25 they share a single limit line, the products-completed operations aggregate, so one number on the certificate covers both.

Why do contracts require completed operations coverage?

Contracts require completed operations coverage because the claims that cost the most often appear after a project closes out, when only this coverage responds. A manufacturer that hires an equipment installer, or a general contractor that hires a subcontractor, can be pulled into a lawsuit for work it did not perform if that work later fails. Requiring completed operations, and requiring the hiring party to be named as additional insured for completed operations, pushes that exposure back to the party that actually did the work and the insurer standing behind it. Without it, a business can be left relying only on its own policy for someone else's mistake.

How long does completed operations coverage last?

Completed operations coverage lasts as long as the policy that includes it is in force, and a claim is generally covered if the policy was active when the damage occurred, not when the work was done. Because problems can surface years after a job, many contracts require a contractor to keep completed operations coverage in place for a set tail, often two to three years past project completion, sometimes longer on construction. This is why a certificate on file is not enough on its own: the coverage has to still be current when a late claim hits, which means tracking renewals rather than filing the certificate and moving on.

Does completed operations need to be on the certificate of insurance?

Yes. If your contract requires completed operations, the certificate of insurance should show a products-completed operations aggregate limit that meets your requirement, and the coverage should not be excluded by endorsement. A blank products-completed operations aggregate, a much lower limit than the general aggregate, or an exclusion are all red flags that the coverage you are counting on may not be there. Reading every certificate for that specific line, on every contractor and supplier, is the kind of repetitive check that is easy to miss by hand and straightforward to verify on a certificate of insurance with software.

Is completed operations the same as additional insured?

No. Completed operations is a coverage on the contractor's own policy; additional insured is status that extends some of that coverage to the business that hired the contractor. The two work together: to be protected for a late claim, you generally need both completed operations coverage on the contractor policy and additional insured status that specifically includes completed operations, often through an endorsement like CG 20 37. A certificate that names you as additional insured for ongoing operations only can still leave you uncovered once the work is finished, which is the gap this combination is meant to close. For more on that status, see additional insured vs certificate holder.

How to verify completed operations on a certificate

Verifying completed operations comes down to four checks on each certificate. First, confirm the general liability section shows a products-completed operations aggregate that meets your required limit, not a blank or a token amount. Second, check for any exclusion endorsement that strips the coverage. Third, confirm the policy is current and will stay current through any tail your contract requires. Fourth, confirm you are named as additional insured for completed operations where the contract calls for it, not just ongoing operations.

Doing that on one certificate is quick. Doing it on every contractor, installer and supplier across a plant or a portfolio, and keeping it current as policies renew and cancel, is where it gets hard. COI tracking for manufacturing reads each certificate, checks the products-completed operations limit against your requirement, confirms additional insured status, and flags anything short or expired before work starts. The same checks run through full certificate of insurance management software so coverage is monitored, not just collected.

Completed operations is part of a larger vendor onboarding picture. Once a contractor or supplier clears the insurance check, teams still have to pull data off the agreements, W-9s and licenses that come with onboarding, which is where AI document data extraction helps, get the master service agreement that sets the insurance requirement signed with an online document e-signing tool, and then manage the resulting orders through purchase order management software. Getting the insurance verification right at the front of that process is what keeps a late claim from becoming your problem.

The bottom line

Completed operations coverage is the safety net for work that fails after it is finished, and it is one of the most commonly required, most commonly missed items on a certificate of insurance. Require it in your contracts, require additional insured status that includes it, and check the products-completed operations aggregate on every certificate, not just the general liability limit. Then keep watching it, because the claim that triggers this coverage usually arrives long after everyone has forgotten the job.