Rip and Tear Coverage

Rip and tear coverage addresses a specific and expensive gap in liability insurance: the cost of tearing out and putting back good property just to get at defective work or a defective product buried inside it. The physical labor of jackhammering a slab, opening finished walls, or dismantling equipment to reach a faulty component can dwarf the cost of the defective part itself. Under a standard commercial general liability policy, the your-work exclusion and related exclusions often bar the cost of repairing the defective work, and courts disagree on whether the surrounding rip-and-tear expense is covered. This coverage—usually added by endorsement—removes that ambiguity for the access-and-restoration costs.

This matters most to contractors, installers, and product manufacturers whose work becomes embedded in a larger structure. Plumbers, HVAC installers, electricians, and building-material suppliers face real exposure: when their component fails after installation, fixing it means damaging otherwise sound property owned by the customer. Rip and tear coverage responds to those third-party access and restoration costs, sitting alongside products-completed operations coverage, which handles bodily injury and property damage arising from finished work. For a small contractor, one embedded-component failure can generate a claim many times larger than the original job value.

The practical nuance is that rip and tear is not a universal, automatic grant—terms, sublimits, and triggers vary widely by carrier and endorsement. Some forms cover only the tear-out and restoration of undamaged property but still exclude the cost to repair or replace the defective product itself; others require that the defect cause resulting damage before any coverage applies. Buyers should read the endorsement carefully, confirm whether it applies to their specific trade, and check how it interacts with the impaired property exclusion. Because interpretation is litigated, contractors handling embedded or subsurface work should treat explicit rip and tear language as a priority rather than assuming their base CGL will respond.