Products-completed operations is the part of a general liability policy that defines manufacturing risk, and it is the piece owners most often misunderstand. In plain terms, it is what answers when a product you made — or a job you completed — causes third-party harm out in the field, after it has left your control. A machine shop machining to a customer’s print and a manufacturer selling its own finished goods both live or die on this coverage, because the product keeps existing long after it leaves the dock. This post explains what the hazard is, the real form it lives in, when it responds and when it does not, and the two separate lines that sit just beside it.
The short version: products-completed operations covers the harm a defective product causes. It does not pay to recall the product, and it does not answer a product that simply underperforms without hurting anyone — those are two different lines. Getting that boundary right before a claim is the whole point. The full coverage-page treatment lives on our general liability and products liability page; this post goes deep on the single mechanic that page is built around.
The real form: the products-completed operations hazard
Almost every commercial general liability policy starts from the standard ISO coverage form — typically the occurrence-based one known as CG 00 01. Inside it, the coverage we are talking about is a defined term: the products-completed operations hazard. It covers bodily injury and property damage arising out of “your product” or “your work,” occurring away from premises you own or rent, after the product has been put to its intended use or the work is complete. That is the real, named mechanism in the policy — not something a carrier invents per account — and for a manufacturer it is not a footnote; it is the core of why the coverage matters.
Two of those words do a lot of work. “Your product” is, broadly, goods you manufactured, sold, or distributed; “your work” is work you performed and the materials supplied with it. Both are defined terms, and the hazard turns on them — which is exactly why reading what counts as your product or your work is worth doing before a loss rather than during one. The practical effect is that the coverage follows the thing you shipped, wherever it goes, once it is in use.
When it responds — and when it does not
The hazard responds to the third-party harm your product or completed work causes once it is out in the field: the operator hurt by a part that fails in a machine, the property damaged when a component lets go downstream, the end user injured by a finished good far down the chain. What it does not do is pay to rebuild your own defective product. The standard form carries exclusions, framed around “your product” and “your work,” that treat the cost of redoing your own scrapped run as a business cost rather than a covered third-party claim. The resulting damage to others is the insured event; making your own bad output good again is not.
Real-World Scenario: A shop machines a run of pins to a customer’s print and ships them. Months later, one fails in the customer’s assembly out in the field and injures an operator — that downstream third-party injury, arising out of your product, away from your premises, is what the products-completed operations hazard answers. If instead the whole run had simply come back out of tolerance and the customer scrapped it, the cost of remaking your own pins would fall on you, not the policy. Same parts, two very different outcomes — and the line between them is exactly what this coverage is built around.
There is one more thing worth checking, because it is quiet and consequential. Some policies carve the products-completed operations hazard out entirely with an exclusion endorsement — in ISO’s system, a form along the lines of CG 21 04. For most businesses that endorsement is harmless; for a manufacturer it can be the difference between a covered claim and an uncovered one. Whether that endorsement is sitting on your policy is exactly the kind of thing worth reading before you need the coverage.
The two seams beside it: recall and E&O
This is where owners most often get the boundary wrong, so it is worth drawing clearly. Products-completed operations covers the harm a defective product causes. Two related exposures sit right beside it and are not the same thing.
The first is the cost to recall the product. When a defect means the product has to come back out of the market, the expense of that recall — customer notification, shipping it back, disposal, and replacement — is a first-party cost, not a third-party claim, and general liability does not pay it. That is what product recall coverage is for. Products-completed operations answers the lawsuit over the harm; recall coverage pays to get the defective product out of circulation. Different bills, different lines.
The second is a product that underperforms without hurting anyone. When a product is out of spec — it fails to do what the contract said, leaves the customer with a financial loss, but injures no one and damages no other property — the standard form’s exclusions around “impaired property” and property that has not been physically injured typically apply, so products-completed operations does not respond. That pure financial-loss exposure runs to manufacturers errors and omissions, a professional-liability line distinct from the bodily-injury and property-damage side this hazard covers. Three exposures, three lines: the harm, the recall cost, and the financial loss — and a manufacturer with real products exposure usually wants all three written together rather than assumed into one. We lay the three out side by side in how the three products coverages differ.
The tail, and the limit that goes with it
Two structural points follow from the fact that products-completed operations is a long-tail exposure — a defective product can surface a claim years after it ships. First, the trigger matters: an occurrence policy, typically the CG 00 01 form, responds to harm that occurs during the policy period no matter when the claim is finally made; a claims-made policy, the CG 00 02 version, responds based on when the claim is reported and depends on continuous coverage and a retroactive date. The long tail usually makes occurrence-based coverage valuable to a manufacturer, but the form your policy actually uses is something to read before a loss.
Second, the products-completed operations aggregate — a separate limit bucket, distinct from the general aggregate that responds to the slip-and-falls and on-premises claims — is the cap that the serious products claims erode. For a manufacturer that is the number to watch, because this is the class where that bucket actually gets used, and it is part of why an umbrella often sits above the primary policy to add limit over it.
Why it matters for your operation
If you make or machine a product, products-completed operations is the coverage your program should be built around, not an afterthought bolted onto a generic business policy. It is the line a customer, distributor, or supply contract scrutinizes, because a product failure has a long tail that can reach back up the chain to you. We read the hazard — the occurrence-versus-claims-made trigger, the separate aggregate, and whether an endorsement quietly carves it out — against the products you actually ship, and we write the recall and errors-and-omissions seams as their own lines rather than pretending one policy answers for all three. When you are ready, start a quote and tell us what you make or machine, or read the full general liability and products liability page and the rest of the coverage overview to see how the lines fit together. Forms and editions vary by carrier, so the right move is always to confirm what your policy actually carries rather than assume.