Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Land Use Development Code topic
No spam. Unsubscribe anytime.
Council Adopts Code Changes Tightening Developer Assurances and Pre‑construction Requirements
Summary
Council unanimously approved two text amendments codifying requirements for developer assurances (performance guarantees and warranty assurances) and formalizing pre‑construction meeting procedures; staff said the changes clarify bid/estimate standards, allow assurances to cover liens, and implement state-mandated categorical reporting.
City staff presented two related code amendments aimed at clarifying how Highland handles assurances tied to subdivisions and nonresidential developments.
Rob (staff) told council the first amendment focuses on the "third option" for assurances—when a developer has completed some improvements and bonds the remainder. The amendment requires a current engineer's estimate or contractor bid broken down by improvement category and material quantities (for example, linear feet of specified pipe) and requires an updated certified estimate when a partial build is bonded. Rob said the changes also permit the city to use assurances to clear contractor liens left on property.
On warranty and maintenance assurance, staff reiterated a typical structure: developers provide a warranty assurance equal to 10 percent of total public-improvement costs for one year after final acceptance, per usual practice and state guidance. Staff explained inspection, punch lists and the city's administrative preference to see improvements fully built (option 1), but acknowledged partial‑build bonding (option 3) is often used by developers.
The second amendment codifies pre‑construction meeting procedures (pre‑cons) currently performed in practice for subdivisions and major site plans—requiring approved construction plans on site, clarifying stormwater and SWIP responsibilities, fees and timing before land disturbance.
Council adopted the assurances ordinance 5–0 and then adopted the pre‑construction ordinance 5–0. Staff will update administrative checklists and forms to implement the new code language.
