Completed Operations Coverage
Written by Justin Goodman, CIC, CRIS, CCIP, CEO and Co-Founder, Total CSR
Published: August 31, 2026 · Last reviewed: August 31, 2026
In plain language: Completed Operations Coverage pays for injury or property damage claims that show up after a contractor or business finishes a job, if the damage traces back to work they performed. A deck collapses two years after installation. This coverage responds.
Technical definition: Completed Operations Coverage is part of the Products-Completed Operations Hazard within the Commercial General Liability (CGL) policy, ISO form CG 00 01. It covers bodily injury or property damage occurring away from the insured's premises after the insured's work is deemed complete, subject to policy exclusions and per-occurrence limits.
Completed Operations Coverage at a Glance
| Attribute | Detail |
|---|---|
| Also known as | Products-Completed Operations Hazard, Completed Ops, COPO |
| Category | Liability policy coverage part |
| Lines of business | Commercial General Liability |
| Industries most affected | Construction, contracting, manufacturing, habitational real estate |
| Related forms or endorsements | CG 00 01 (CGL Coverage Form), CG 25 03 (Aggregate Limits by Project), CG 21 39 (Contractors – Limited Coverage for Additional Insureds) |
| Who bears the risk | Contractor, subcontractor, or business that performed the completed work |
| Common solution | CGL policy with occurrence-based Completed Operations coverage, tail coverage for claims-made forms |
| Also interacts with | Ongoing Operations coverage, Additional Insured endorsements, subcontractor certificates of insurance |
Key Takeaways
- Completed Operations Coverage protects a contractor or business against liability claims for injury or damage caused by work that has already been finished and handed over.
- Agencies rely on this coverage daily when reviewing contractor GL policies, because most construction lawsuits arise years after a job wraps, not during the work itself.
- The most common misunderstanding is treating "ongoing operations" and "completed operations" as interchangeable, when they trigger under different circumstances and sometimes different aggregate limits.
- A quick win for agencies is confirming the CGL policy is occurrence-based rather than claims-made, since occurrence forms respond years later without needing an active policy at claim time.
What Is Completed Operations Coverage in Insurance?
Completed Operations Coverage is the portion of a Commercial General Liability policy that responds to bodily injury or property damage happening after the insured has finished a job and the work has been accepted by the customer. It exists because construction and manufacturing defects often surface long after completion. A roofer who installs shingles in March may not learn about a leak-caused mold claim until the following winter, well after the crew has left the site.
The coverage protects against a legal doctrine tied to negligence and product liability: a business remains responsible for the reasonably foreseeable consequences of its work, even after delivery. Carriers underwrite this exposure carefully because the tail on construction defect claims can stretch for years, sometimes limited only by a state's statute of repose. Completed Operations sits inside the Products-Completed Operations Hazard, a defined term in the CGL form that groups product liability and completed work liability together under one set of rules.
Consider a general contractor who builds a retaining wall for a homeowner. The wall passes final inspection and the contractor is paid in full. Fourteen months later, the wall fails during a heavy rainstorm and damages a neighboring property. Because the work was complete and the contractor was off the job site when the damage occurred, this falls under Completed Operations rather than Ongoing Operations coverage.
How Does Completed Operations Coverage Work?
- The completed work. The contractor finishes the job, and the client accepts the work as done, whether through final payment, occupancy, or a punch-list sign-off.
- The delayed failure. A defect in the work causes bodily injury or property damage after the contractor has left the site, sometimes months or years later.
- The claim. The injured party or property owner files a claim or lawsuit against the contractor, alleging the finished work caused the harm.
- The tender. The contractor notifies their insurance agency and carrier, who confirms the CGL policy in force at the time of completion, not the time of the claim, generally applies under an occurrence form.
- The coverage determination. The carrier investigates whether the damage falls within the Products-Completed Operations Hazard definition and applies any relevant exclusions, sublimits, or aggregate limits before paying the claim.
Real Claim Examples Involving Completed Operations Coverage
Deck collapse two years after installation
A residential contractor built a deck for a homeowner in 2023. In 2025, the deck collapsed during a family gathering, injuring three guests. Because the contractor had completed the work and left the premises long before the incident, the claim triggered Completed Operations Coverage under the CGL policy active at the time construction finished. The carrier defended the contractor and paid the settlement up to the policy's per-occurrence limit.
HVAC installation causing a fire months later
A commercial HVAC contractor installed rooftop units on a warehouse. Four months after final inspection, faulty wiring from the installation sparked a fire that destroyed inventory. The warehouse owner sued the contractor for the full loss. Completed Operations Coverage responded because the fire occurred after the job was finished and traced directly back to the contractor's installation work, not an ongoing job-site incident.
Subcontractor work causing water intrusion after project handoff
A waterproofing subcontractor completed work on a multi-family building before the general contractor handed the project to the developer. A year later, water intrusion damaged multiple units, and the developer sued both the general contractor and the subcontractor. Coverage disputes arose over which party's Completed Operations coverage applied and whether the subcontractor's policy named the general contractor as an additional insured for completed operations, a gap that delayed the claim resolution by months.
Completed Operations Coverage vs. Ongoing Operations Coverage: What Is the Difference?
Completed Operations Coverage and Ongoing Operations Coverage both live inside the same CGL policy, but they trigger at different points in a project's timeline. Ongoing Operations applies while work is actively in progress at the job site, while Completed Operations applies once the work has been finished and accepted.
| Comparison area | Completed Operations Coverage | Ongoing Operations Coverage |
|---|---|---|
| Primary use case | Claims arising after work is finished and the site is vacated | Claims arising while work is actively underway |
| Coverage / concept type | Part of the Products-Completed Operations Hazard | Part of standard CGL premises/operations liability |
| Typical exclusions | Faulty workmanship repair costs, contractual liability limits, professional services | Employee injuries (covered by workers' comp instead), pollution |
| Who is most affected by errors | Contractors relying on additional insured status years after project completion | Contractors and subcontractors during active build phases |
| Common mistakes | Assuming coverage follows the claim date rather than the occurrence date | Assuming ongoing operations coverage extends automatically after job completion |
What Are the Most Common Mistakes With Completed Operations Coverage?
- Agencies confuse claims-made and occurrence triggers, assuming any active CGL policy will respond to an old completed-operations claim, when only the occurrence-form policy in place at the time of the incident actually applies.
- Producers fail to secure additional insured endorsements that extend to completed operations, leaving general contractors uncovered for subcontractor work discovered defective after project handoff.
- CSRs issue certificates of insurance that reference ongoing operations language only, creating a documentation mismatch that surfaces during a completed operations claim dispute.
- Agencies overlook aggregate limit erosion, not realizing a per-project aggregate endorsement like CG 25 03 can leave insufficient limits for a completed operations claim on a different project.
- Clients assume completed operations coverage pays for the cost of fixing their own faulty work, when the coverage responds to resulting third-party injury or damage, not the repair itself.
- Agencies forget to advise contractors about extended reporting periods when switching carriers, leaving a coverage gap for completed operations claims that surface after a policy nonrenewal.
How to Explain Completed Operations Coverage to a Client
Explaining Completed Operations Coverage to a personal lines client
You're not usually the one buying this coverage, but if you hire a contractor for a remodel, ask whether their policy covers completed operations. That means if something they built fails months later and causes damage, their insurance, not yours, should respond to the claim.
Explaining Completed Operations Coverage to a small business owner
Once you finish a job and leave the site, your liability exposure doesn't disappear. Completed Operations Coverage is the part of your general liability policy that protects you if your finished work causes an injury or property damage down the road. It's why keeping continuous, occurrence-based coverage matters even after a project wraps.
Explaining Completed Operations Coverage to a CFO or risk manager
Your completed operations exposure is a long-tail liability that can outlive the project by years, sometimes bounded only by your state's statute of repose. We need to confirm your CGL form is occurrence-based, your aggregate limits aren't eroded by per-project endorsements, and your subcontractor agreements require additional insured status extending to completed operations. Getting this wrong shows up as an uninsured claim long after the contract has closed.
Frequently Asked Questions About Completed Operations Coverage
Does Completed Operations Coverage apply to work still in progress?
No. Completed Operations Coverage only applies once the work is finished and accepted by the client, or in the case of separate contracts on a project, when that portion of work is complete. Work still underway falls under Ongoing Operations coverage instead.
How long does Completed Operations Coverage last after a job ends?
Coverage typically lasts as long as the occurrence-based policy remains in force at the time of the incident, and claims can surface years after project completion. The practical limit is often the state's statute of repose, which caps how long after completion a construction defect lawsuit can be filed, commonly ranging from six to twelve years depending on the state.
Can a contractor be sued for completed operations even after canceling their policy?
Yes, but coverage depends on the policy that was active when the damage occurred, not the current policy status. Under an occurrence form, the contractor should still have coverage from the policy in force at the time of the incident, even if that policy has since expired or been canceled.
Does Completed Operations Coverage pay to fix the contractor's own faulty work?
No. This coverage pays for third-party bodily injury or property damage resulting from the faulty work, not the cost of repairing the defective work itself. Repairing the contractor's own workmanship is generally excluded under most CGL forms as a business risk exclusion.
Why do general contractors require subcontractors to carry completed operations coverage?
General contractors require it because they can be named in lawsuits over a subcontractor's work long after the project ends, and they want the subcontractor's policy, not their own, to absorb that risk. Requiring additional insured status specific to completed operations, often through an endorsement, helps ensure the general contractor's own aggregate limits stay protected.
What is the difference between Completed Operations and Products-Completed Operations Hazard?
Completed Operations is one half of the broader Products-Completed Operations Hazard definition in the CGL form, with the other half covering product liability for manufactured or sold goods. The two are grouped together because both involve harm occurring after the insured has relinquished control of the work or product.
Related Insurance Terms
- Products-Completed Operations Hazard: the broader CGL policy definition combining completed operations liability and product liability exposure, both triggered by harm occurring after the insured no longer controls the work or product.
- Ongoing Operations Coverage: the CGL coverage responding to bodily injury or property damage occurring while work is actively underway at a job site, distinct from completed operations by timing rather than cause.
- Additional Insured Endorsement: a policy modification extending liability coverage to a party other than the named insured, frequently used by general contractors to gain completed operations protection under a subcontractor's policy.
- Occurrence Form: a liability policy structure that responds based on when the injury or damage happened, not when the claim was filed, making it the standard trigger for completed operations claims.
- Statute of Repose: a state law setting an absolute deadline after project completion beyond which a construction defect lawsuit cannot be filed, effectively capping completed operations exposure.
- Aggregate Limit: the maximum amount a CGL policy will pay across all claims in a policy period, which can be structured per-project through endorsements affecting available completed operations limits.
Sources and References
- International Risk Management Institute (IRMI). Products-Completed Operations Hazard.
- International Risk Management Institute (IRMI). Commercial General Liability (CGL) Policy.
About the Author
Justin Goodman, CIC, CCIP, CISC, CLCS, CRIS, PCIA, QCLS, MFHR CEO and Co-Founder, Total CSR, Inc.
Justin Goodman is a third-generation insurance broker with over two decades in agency operations. He has trained more than 100,000 CSRs, account managers, and producers in commercial and personal lines coverage, from workers' compensation to construction risk. He was named 2024 Insurance Journal Agent of the Year and one of the nation's top five construction insurance experts by Risk & Insurance. He is the author of Retain, which applies cognitive science research on memory and knowledge transfer to insurance training, and speaks nationally on how agencies build durable technical expertise in their teams.