Citizen Portal
Sign In

Get Full Government Meeting Transcripts, Videos, & Alerts Forever!

Get email alerts on the Development Code topic

No spam. Unsubscribe anytime.

Planning commission recommends approval of pre-construction meeting and developer-assurance code changes

Highland Planning Commission · January 28, 2026
AI-Generated Content: All content on this page was generated by AI to highlight key points from the meeting. For complete details and context, we recommend watching the full video. so we can fix them.

Summary

The Highland Planning Commission recommended approval of two code amendments that would require pre-construction meetings after site-plan or subdivision approval and clarify developer assurances (performance guarantees, bonding, warranties). Staff emphasized templates for cost estimates and authority to reject inaccurate bids.

The Highland Planning Commission on an affirmative roll call recommended that the city council adopt two related amendments to the development code: a formal requirement for pre-construction meetings after site-plan or subdivision approval, and clarified rules on development assurances that spell out performance guarantees, bonding and warranty requirements.

Staff member Rob, who presented both items, said the proposed pre-construction meeting process would require developers to bring stamped paper copies of approved plans to a meeting with their contractor, engineer and public-works staff so parties coordinate inspections and scheduling. "It requires a pre construction meeting after the site plan subdivision approval before work," Rob said, noting the requirement is intended to put longstanding practice into writing.

Rob walked the commission through how assurances would work if a developer chooses not to build all improvements before platting. Under the proposed approach a developer may provide a performance guarantee—either a cash deposit or a letter of credit—equal to 100% of the estimated cost of the remaining public improvements plus a 10% administration factor. Rob used an illustrative example of a $1,000,000 public improvement with a $100,000 (10%) warranty and said a typical bond amount would equal the future cost plus the 10% administrataive margin. He also described partial releases when inspected work has been completed and accepted: "We reduce the amount we're holding based on how much of the work is completed," he said.

Commissioners questioned how smaller developers without large cash reserves would secure assurances and whether staff can reject low or incomplete cost estimates. Rob explained letters of credit allow a bank to guarantee funds so long as the issuing institution will pay if the developer defaults; he also said city engineers review submitted estimates and can require revised bids or broken-down estimates by improvement category. He noted the city has used assurances to clear contractor liens where necessary, although he said the city has "never had to do that" and prefers to use assurances to motivate completion rather than perform the work itself.

A commissioner moved and the commission seconded a recommendation that the city council adopt both the pre-construction meeting requirement and the clarified development-assurance language. The motion was approved in roll call. No public comments were received on the items during the hearing.

Next steps: both recommendations will be forwarded to the city council for consideration. Staff told the commission they will provide the specific cost-estimate templates and the updated ordinance language when the items go to council.