Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Design Review topic
No spam. Unsubscribe anytime.
Committee tightens design-review rules, makes pre-application meetings mandatory for site plans
Summary
The commission revised Chapter 11: clarifying the distinction between subjective design review and technical site-plan review, tightening criteria, requiring mandatory pre-application meetings, and proposing mechanisms to encourage lower building heights in exchange for increased ground-level coverage.
Clarkdale staff presented broad revisions to Chapter 11 of the unified development code to make design-review standards clearer, speed technical approvals, and improve transparency for applicants.
Staff emphasized the distinction between design review (a qualitative evaluation of compatibility and aesthetics) and site-plan review (a binary, technical check for conformance with engineering, drainage, utility, and setback standards). "Site plan review is not ambiguous. It is you did these things or you didn't," Jessica told the panel, explaining why many technical checks are being moved to staff-level review.
Key proposed changes discussed by the committee included:
- Moving many subjective design-review criteria to clearer, measurable considerations (preserving natural drainage, minimizing excavation, orienting main building entrances to the street where feasible). - Making pre-application meetings mandatory for site-plan applicants so staff and outside agencies can identify missing items before formal submission, a step several members said would reduce repeated incomplete submittals. - Requiring developers to construct and dedicate necessary water facilities that meet town engineering standards and to warrant that work for two years once accepted by the town. - Requiring performance guarantees (security bonds, lines of credit, escrow) to ensure completion of required public improvements if a developer defaults.
The committee debated several design tensions: how to define compatibility across different contexts (historic downtown, 89A commercial corridor, industrial areas), how to address viewsheds and hillside development without an official map, and whether to craft hard limits or flexible incentives for building height. Staff proposed an incentive model that would allow applicants to lower vertical height in exchange for increased lot coverage on lower levels, preserving the visual scale while not reducing entitled development capacity.
Staff also clarified technical submission standards: drainage reports, grading plans, stormwater control measures and stamped engineering documents will be required, and electronic application materials are acceptable. Staff said they will refine ambiguous terms and prepare guidance documents so applicants and residents understand what is required and which items are handled administratively versus by the planning commission.
No final code text was adopted. Staff will revise Chapter 11 language based on committee feedback and return with more precise definitions, examples, and checklists for both design and site-plan review.
