Insurance and Bonds for Land Developers, from Raw Land to Finished Lots

Exposure starts at closing. Raw land brings trespass, dumping, existing wells and structures, farm or grazing leases and access road claims, and the owner's general liability policy is typically the first placement. Ask whether the form schedules vacant land correctly, whether existing tenants carry their own insurance naming the owner and whether any demolition or clearing before the site contractor mobilizes is the owner's work or a contractor's.

Environmental due diligence has its own deadlines. Under 40 CFR 312.20, all appropriate inquiries for CERCLA landowner protections must be conducted within one year before acquisition, and interviews, lien searches, government records reviews, site inspections and the environmental professional's declaration must be conducted or updated within 180 days before acquisition. When a closing slips, a Phase I can age out of those windows. Known or suspected conditions can also lead a developer to consider a pollution legal liability policy for existing conditions, separate from the contractors pollution coverage that responds to the work itself.

Entitlement is where the developer agrees to build what the agency will later bond. Conditions of approval list the streets, utilities, drainage, landscaping and off-site work. The improvement agreement turns them into a promise with a completion date. In California, Government Code §66462 requires that agreement before a final map with unfinished improvements is approved, with options to finance the work through a special assessment act or a Mello-Roos community facilities district, and the agreement must be secured with Map Act improvement security.

The surety relationship should be built during entitlement, not after the map is calendared. Sureties underwrite land developers on balance sheet, liquidity, guarantors, existing bonded obligations and how the improvements will be funded, and they read the engineer's estimate closely. Consultants matter here too: the civil engineer, geotechnical engineer and other design firms typically carry their own professional liability, and the developer's contracts with them should state the limits and the period the coverage must stay in force.

Once grading starts, most of the physical risk sits with the site contractor, but the developer remains the owner of record. The site contractor's general liability, auto, workers' compensation and pollution coverage should be confirmed before mobilization, along with additional insured endorsements that extend to the developer and, where the contract requires it, to completed operations. Builders risk is often limited for horizontal work because many forms exclude or sublimit roads, underground utilities and land, so the developer should ask what physical damage protection exists for the improvements before the city accepts them.

Stormwater permits follow the land, not the lot lines. TCEQ's construction general permit, for example, regulates construction activity that disturbs an acre or more, including smaller activity that is part of a larger common plan of development or sale, and separates large sites of five acres or more from small sites. A land developer selling lots to several builders is often still operating inside one common plan, so who holds coverage, who files changes and when the developer can terminate its own coverage should be settled before the first takedown.

Each state sets up the bond differently, and a land developer working in more than one should expect different forms and release steps. California's Subdivision Map Act sets performance and labor and materials security each between 50 and 100 percent of the estimated cost, plus a warranty amount. Texas leaves most terms to city ordinances and county orders under the Local Government Code, within limits such as rough proportionality. Arizona requires assurances by statute but lets each city choose among bonds, letters of credit, cash and third-party land trusts. Nevada leaves improvements to local ordinance under NRS 278.326 and lets the agreement to improve be secured by a bond or other security under NRS 278.380.

The form of security changes the developer's capital plan. A surety bond typically preserves the bank line but adds an indemnity agreement; a letter of credit uses the line; a trust or escrow restriction uses neither but controls when lots can close. Open bonds also accumulate across phases, so a developer with several communities in progress needs a schedule of every open bond by obligee, amount and expected release date to keep capacity available for the next map.

A lot sale moves the vertical risk to the buyer, but not everything else. The lot purchase or takedown agreement typically obligates the developer to finish the remaining improvements, sets indemnities in both directions and states when the builder's own builders risk and liability program takes over. Additional insured requirements should run both ways: the builder's program naming the developer for the builder's work on the lots, and the developer's site contractor naming the builder where the builder relies on the developer's improvements.

Some states add a sales test. In Arizona, A.R.S. §32-2183(F) makes it unlawful for a subdivider to sell a lot unless the promised improvements are complete, assured by financial arrangements acceptable to the Real Estate commissioner, secured by a government occupancy restriction with an escrow-closing restriction or covered by a recorded trust assurance agreement. Cities may also keep the developer's improvement bond in place until a buyer's replacement assurance is approved, so the purchase agreement should set who posts what, and by when.

Horizontal work can generate claims long after sell-out. Streets, storm drains and grading can be alleged to cause settlement, flooding or slope movement under homes the developer never built, and the public agency that accepted the improvements may also hold a warranty amount or bring its own claim. Completed-operations protection on the developer's program and the site contractor's program, and how long each stays in force, decides whether those claims find coverage, subject to the policy wording and the facts.

Entity planning matters at this stage. Developers often wind down a project entity after sell-out, but bonds may still be open for warranty periods and claims may still arrive. Ask whether completed-operations coverage survives dissolution of the named insured, whether a project-specific policy with a long completed-operations term fits better than annual policies and who will keep the records an insurer will request years later.

Land developers with several communities in progress usually benefit from a master structure: one owner's liability program with each project entity named, per-project aggregate limits so a claim at one community does not exhaust the limit at another, a single surety program with a running bond schedule and consistent insurance requirements for site contractors and builders. The details depend on the developer's entity chart, its lenders and the states where it operates.

The most useful document a developer can bring to a broker is a phase map: each community, its entitlement status, open and expected bonds, site contractors, expected lot sales and the dates each phase will be accepted. That map shows where coverage is missing, where bonds will come due and where capacity is tied up, before the next acquisition closes.