Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Development Process Incentives topic
No spam. Unsubscribe anytime.
Committee pushes for clearer implementation language: developer guidance, fire‑code coordination and renaming incentives
Summary
Committee members asked staff to prepare clearer procedural guidance for developers, to reword recommendation language that uses terms such as "leniencies" and "by right," and to explore coordinated pre-application review with fire districts.
Committee members spent part of the session on implementation language and recommendations intended to help small businesses and developers navigate county processes. Discussion covered several themes: streamline/expedited review, how incentives are described, and cross‑jurisdictional coordination, particularly with fire districts.
Members asked that the plan and subsequent UDO work include an easy-to-follow checklist or centralized guidance so applicants can see required steps, known requirements (for example, fire-district sprinkler thresholds), and responsible contacts. Several speakers recounted cases where developers received different requirements from different reviewers late in the process and said a consolidated checklist or online intake (for example, a QR-code hub) would reduce those surprises.
Committee members also questioned wording in the recommendations that they said could be misread as a promise of regulatory leniency. The draft language referenced "offer incentives including development leniencies such as expedited or streamlined reviews and density bonuses." Several members proposed removing the word "leniencies" and the phrase "by right" in one place and substituting a more positive, incentive-focused term such as "awards" or "credits". The group discussed editing another sentence to read simply that the list of desirable uses should be amended to ensure compatible uses are allowed and undesirable uses are prohibited, removing the ambiguous phrase "undesirable uses are prohibited unless..." unless staff can provide a clear operational definition.
On cross‑jurisdiction coordination, members emphasized that individual fire districts and other authorities have independent code interpretations and enforcement powers; they asked staff to explore whether the county and fire jurisdictions can coordinate pre-application review steps so applicants receive consistent guidance early and avoid late, costly changes.
Ending: Staff was directed to propose draft edits to recommendation language (replace or reframe "leniencies"), draft a developer checklist or intake guidance, and consult with fire districts about options for coordinated pre-application review.
