On April 1, 2020, the First Circuit, applying Massachusetts law, issued a potentially useful decision addressing the Montrose “known loss” language in ISO Form CGL policies. In Clarendon National Insurance Company v. Philadelphia Indemnity Insurance Company, the court applied this language to allow denial of defense for claims of recurring water infiltration that began before the insurer’s policy period, and it found an insurer had no duty to investigate whether the course of property damage might have been interrupted, or whether other property damage might have occurred during the policy period, so as to trigger coverage during a later policy.
In the underlying dispute, a condominium owner (Doherty) asserted negligence claims against her association’s property management company (Lundgren) stemming from alleged water infiltration into her condominium. The complaint said leaks developed in 2004 in the roof above Doherty’s unit, and repairs were not made in a timely or appropriate manner. The following year, the complaint said, a Lundgren employee notified Doherty that the threshold leading to her condominium's deck was rotting. In February 2006, Doherty discovered a mushroom and water infiltration on the threshold and notified Lundgren. At that time, Lundgren asked its maintenance and repair contractor (CBD) to replace the rotting threshold. According to the complaint, CBD did not do this repair in a timely manner and left debris exposed in Doherty’s bedroom.
In March 2006, the complaint said, a mold testing company hired by Lundgren found hazardous mold in Doherty's unit, caused by water intrusions and chronic dampness. Lundgren’s attempts at remediation were ineffectual. In September 2008, Doherty's doctor ordered her to leave the condominium and not to return until the leaks were repaired and mold was eliminated.
Reprinted courtesy of Eric B. Hermanson, White and Williams and Austin D. Moody, White and Williams
Mr. Hermanson may be contacted at email@example.com
Mr. Moody may be contacted at firstname.lastname@example.org