Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Land Use Process topic
No spam. Unsubscribe anytime.
Planner explains Aspen's "public projects" review and what it means for the HPC
Summary
City planner Ben explained differences between the Land Use Code's planned‑development process and the public‑projects review, telling the Aspen HPC that public projects combine multiple review steps into a single council decision while preserving the commission's ability to evaluate historic‑preservation criteria and offer recommendations.
City planning staff gave a focused explanation of the Land Use Code's "public projects" review and how it differs from a two‑step planned‑development review, aiming to clarify the commission's role if a major public project—such as the Armory—proceeds under that path.
"If this were a planned development that was not a public project, you folks would still be a recommending body on the first step of that review," Ben said. He explained that planned development typically has a project‑level step followed by a final‑detail step where the commission may act on details; by contrast, the public‑projects process combines those reviews into a single review and makes city council the deciding body while retaining the requirement that review criteria be submitted and considered. Ben cited past local examples including Lift 1 Lodge and an ambulance facility to illustrate how the public‑projects path has been used.
Ben also noted the procedural origin of the public‑projects process in local practice and state interjurisdictional review (referenced in the transcript as location and extent review), and staff said a pre‑application summary for the Armory had already been issued and that a full land‑use application might arrive around the first of the year.
