Subdivision Site Improvement Insurance and Bonds

Both the developer and the site contractor need general liability, but for different reasons. The developer carries the owner's exposure for the land, the project and anything it self-performs. The site contractor carries the exposure from its operations. The subcontract or site improvement agreement usually ties the two together with indemnity, additional insured requirements and waiver of subrogation.

On a tract development, watch for residential and tract-housing exclusions on the site contractor's GL. Some contractor forms limit or exclude work on residential projects or projects over a certain unit count, and a grading or utility contractor that mostly does commercial work may not notice the restriction until a homeowner claim arrives. Ask whether the contractor's GL applies to residential subdivision work and whether additional insured endorsements extend to completed operations.

Larger subdivisions sometimes justify a project-specific policy or a wrap-up that enrolls the site contractor along with the vertical builders. Either structure can concentrate limits on the project, but it also changes what each contractor's own annual policy is expected to do, so the enrollment terms and off-site exclusions need a careful read.

Builders risk is designed for structures under construction, and many forms exclude or sharply limit land, earthwork, roads, paving, underground pipe and landscaping. A developer who buys builders risk for the homes may find that a washout of graded pads, a collapsed storm drain or a flooded joint trench sits outside that policy. Some markets will add horizontal improvements by endorsement or write a separate civil works form, usually with its own deductibles and sublimits.

Ask three questions before relying on builders risk for site work: whether the form lists roads, pipe, earthwork or landscaping in its exclusions or property not covered, whether there is a sublimit for underground or horizontal property and how the policy treats completed improvements before they are dedicated to the city. If the answer to any of those is unclear, the contractor's equipment and installation coverage and the developer's own risk retention have to fill the gap.

Materials stored on site or in transit, such as pipe, precast boxes and streetlight poles, are another common gap. Decide in writing whether they are the contractor's responsibility until installed or fall under the developer's property program.

Subdivisions disturb large areas of ground, which puts stormwater and soil conditions at the center of the pollution question. The EPA states that construction disturbing one acre or more, or a smaller site that is part of a common plan of development, needs Clean Water Act permit coverage for stormwater discharges, and every phased subdivision is a common plan. Sediment that leaves the site can bring agency enforcement and third-party claims, and many GL forms treat it under the pollution exclusion.

Former agricultural or industrial land can hold pesticides, fuel or fill that becomes a problem once grading starts. The contract should say who characterizes soils, who pays for disposal and who carries pollution risk. A developer may carry a site pollution policy for pre-existing conditions while requiring the site contractor to carry contractors pollution coverage for its operations, and the two policies should be read together so that neither assumes the other responds.

Before a final map records or permits issue, the local agency usually requires the developer to secure completion of the public improvements. In California, Government Code §66499 lets the agency accept a corporate surety bond, a cash or negotiable-bond deposit, an instrument or letter of credit from a regulated financial institution or, in limited cases, a lien on the property. Section 66499.3 sets the faithful performance amount at 50 to 100 percent of the estimated improvement cost, plus a separate 50 to 100 percent amount securing payment to contractors, subcontractors and suppliers. It also allows an amount for a one-year warranty after completion and acceptance. In Arizona, A.R.S. §9-463.01(C)(8) authorizes municipalities to require performance bonds, assurances or other security for streets, utilities, drainage and flood control improvements.

That security is not insurance. A subdivision bond protects the agency, and the developer signs an indemnity agreement with the surety. The site contractor's own performance and payment bonds, if the developer requires them, protect the developer. A developer that confuses the two may find it is bonded to the city for work its contractor never bonded to the developer.

Bond forms, release mechanics and the agency's amounts are set locally, so read the subdivision improvement agreement before choosing the form of security.

The exposure does not end when the paving crew leaves. In California, Government Code §66499.7 releases performance security upon final completion and acceptance, and it lets the subdivider give written notice that work is complete, after which the agency has 45 days to approve it or list remaining work. Payment security and any warranty amount typically remain in place for their own periods after that.

Between substantial completion and acceptance, the developer often still owns and maintains streets and storm systems that the public is already using. Claims during that window can involve both the developer and the contractor. After acceptance, the maintenance or warranty period keeps the contractor responsible for defects, and completed operations coverage and additional insured endorsements need to run long enough to match it.

Phased subdivisions complicate this further because some streets are accepted while others are still being built. Track acceptance dates by phase and confirm that bonds, completed operations and builders risk end dates line up with them.

Developers often require the site contractor to provide performance and payment bonds naming the developer, and sometimes the lender, as obligee. Those bonds protect the developer and lender if the contractor fails to finish or fails to pay its suppliers and subcontractors. The contractor's surety will underwrite its financial statements, WIP schedule and backlog, so a large subdivision package can strain capacity for a mid-size site contractor.

When the city's improvement security and the contractor's bonds cover the same work, coordinate the amounts and the completion definitions so they mirror each other. A city that defines completion as acceptance and a subcontract that defines it as substantial completion leaves the developer exposed in between.