Project-Specific Liability Insurance for Developers and General Contractors

The first question an underwriter and a broker ask is who the policy is for. A development entity, its managing member, the GC and sometimes affiliated property entities may each need named insured status, or they may be added as additional insureds with narrower rights. A party that is only an additional insured typically has protection limited to the scope the endorsement describes, which may stop at the end of ongoing work.

The project definition matters just as much. It usually names the site address or legal description, the scope of work and sometimes the contract value. If the scope changes, a phase is added or off-site improvements such as utility extensions and street work are built under a separate agreement, those operations may fall outside the defined project. Ask whether the definition includes staging areas, haul routes and off-site improvements required by the conditions of approval.

Entity structure is where developers most often get caught. A single-purpose entity formed after the policy is bound, or a land-holding entity that never appears on the declarations, can leave a gap that only shows up when a claim names it.

A general aggregate is the most a policy pays for most kinds of claims during its term. On an annual contractor policy, a bad year on one job can use up the aggregate that every other job depends on. Contracts and lenders often ask for an aggregate that applies separately to the project, and the standard way to do that on an annual policy is an endorsement scheduling the project.

The ISO endorsement Designated Construction Project(s) General Aggregate Limit (CG 25 03, 05 09 edition, as reproduced by the New York Office of General Services) gives each scheduled project its own aggregate equal to the declarations amount. The detail buyers miss is the wording: the separate aggregate applies to damages attributable only to ongoing operations at a single designated project. Payments for bodily injury or property damage within the products-completed operations hazard reduce the products-completed operations aggregate instead, and claims that cannot be tied to one designated project draw on the policy's general aggregate.

That means a per-project aggregate endorsement on an annual policy may protect limits during construction while leaving completed operations limits shared across every job the contractor has finished. A true project-specific policy can avoid that sharing, but only if its own completed operations aggregate and term are written for the project. Read the endorsement and the declarations together, and ask the carrier which aggregate a defect claim after turnover would reduce.

Construction liability has two phases. Ongoing operations are the claims that arise while work is underway: a passerby hurt near the site, damage to a neighbor's property from excavation, a crane incident. Completed operations are claims that arise after the work is finished and turned over, which on construction projects often means alleged defects that cause property damage or injury.

The distinction matters because the two phases are often subject to separate aggregates, different additional insured endorsements and different durations. On most projects the larger financial exposure sits in the completed operations phase, because defect claims can surface years after occupancy. California, Texas, Arizona and Nevada each have statutes of repose that set outer limits on many of those claims, and those time frames shape how long a project policy's completed operations term should run.

A project policy that ends at substantial completion, or that includes only a short completed operations extension, may leave the developer and GC relying on whatever annual policies are in force years later.

Many contractor liability forms now carry subcontractor conditions. Some require the named insured to obtain certificates, indemnity agreements and additional insured status from every subcontractor; if the documentation is missing, the carrier may deny or limit coverage for claims arising from that subcontractor's work. Others exclude work performed by subcontractors altogether, or exclude specific trades such as roofing, structural or excavation work.

Residential projects draw more restrictive language. Exclusions for multifamily, condominium or tract work, for earth movement and subsidence, and for prior or continuing damage are common on the market today, and each can remove the exposure a developer most needs protected. Exterior insulation and finish systems, water intrusion and mold language deserve a line-by-line read on any podium or wood-frame residential project.

The practical point is that a project policy and the subcontract program have to be designed together. If the policy conditions require something the subcontracts do not demand, the gap belongs to the developer or GC.

Project limits are usually built in layers. A primary general liability policy sits at the bottom, and one or more excess policies attach above it. An excess layer typically responds only after the scheduled underlying limits are paid, and only to the extent its own wording allows.

Follow-form excess generally adopts the terms of the underlying policy, but many excess forms follow form except where they say otherwise, and those exceptions can include residential work, professional services, pollution and specific additional insured terms. Ask whether each excess layer recognizes the same named insureds, the same project definition and the same completed operations term as the primary. If the primary carries a per-project aggregate but the excess applies a single aggregate across the insured's operations, the excess may not track the project the way the contract assumes.

Attachment also depends on the underlying schedule. Excess carriers often require that employers liability and auto liability sit underneath, which can matter when a contractor's own policies are scheduled as underlying to a project placement.

Risk transfer on a project is a chain: the owner's contract with the GC, the GC's subcontracts and the insurance each party carries. Indemnity clauses shift liability by contract, and additional insured endorsements give the upstream party direct rights under a downstream policy. Both are limited by statute in the three launch states.

California Civil Code §2782 voids construction indemnity for the promisee's sole negligence or willful misconduct, and for contracts entered into on or after January 1, 2013, limits indemnity for an owner's or public agency's active negligence. Section 2782.05 limits a subcontractor's indemnity for a GC's active negligence on many commercial contracts, but it does not apply to wrap-up programs or to provisions requiring the subcontractor to buy insurance, including additional insured endorsements for ongoing and completed operations. Texas Insurance Code §151.102 voids indemnity for the indemnitee's own negligence, with an exception for claims by the indemnitor's employees, and §151.104 voids additional insured requirements to the same extent. Arizona's A.R.S. §32-1159 voids indemnity for the promisee's sole negligence in private construction contracts.

These statutes have exceptions and effective dates, and Texas carves out single-family, townhouse and duplex work. Contract language should be reviewed by counsel, and the insurance requirements should be written so they match what the statutes allow.

A contractor's annual policy is designed for a volume of work, not one job. A project-specific placement tends to make sense when one or more of these is true: the project is large relative to the contractor's annual volume; the contract or lender requires limits that are not shared; the work is residential or condominium construction that the annual policy excludes or restricts; or the developer wants completed operations limits that will remain available for the full repose period rather than depending on renewals years from now.

It can make less sense when the project is modest, when the contractor's annual program already carries a per-project aggregate and acceptable completed operations terms, or when the owner is arranging a wrap-up that enrolls the contractors directly. Cost also enters, because a project policy is often priced on construction value and may require the full term's premium up front.

None of these factors is decisive alone. The comparison should be made on the actual forms, with the contract and lender requirements in hand.

Underwriters price project liability on the project, not only on the contractor. Expect to provide the site plan, the scope and schedule, construction value, the delivery method, the contract or draft contract, the subcontract insurance requirements and the GC's loss history. For residential work, they often ask for the entity structure, whether units will be sold or rented and how homeowner association turnover is handled.

A submission that answers those questions before the underwriter asks tends to reach more carriers and yields terms that are easier to compare. The same package usually feeds the builders risk, pollution and surety submissions for the same project.