Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Neighborhood Planning topic
No spam. Unsubscribe anytime.
City staff previews North of Campus area plan; adoption scheduled for May 5
Summary
City planning staff presented the North of Campus neighborhood area plan, summarizing community engagement, survey results and implementation steps. Council discussed implementation tracking and asked staff to provide clearer action‑item timelines before adoption on May 5.
City planning staff presented an extensive draft of the North of Campus neighborhood area plan, one of seven area plans associated with the city’s comprehensive plan. Craig Garrison described the plan boundary, the engagement process (steering committee meetings, walking tours and three public workshops), and the structure of the plan (seven topic areas with recommendations, case studies and implementation tools).
Garrison said staff mailed hundreds of postcards to promote community workshops, collected more than 200 comments and revised the plan to reflect community input. The plan includes an action plan that identifies short‑term items, potential funding sources and recommended partners. Staff said the plan will not change conditions on the ground until it is implemented through subsequent initiatives such as code amendments and capital projects.
Council members pressed staff on implementation accountability, asking for more detail about which recommendations are immediately actionable, which require Development Code (LDC) changes, and how staff will track progress. Assistant director Via Lobos described a new implementation tracking tool being explored with IT to show actions and progress publicly and to foster cross‑departmental accountability.
Council took no action; adoption is scheduled for the May 5 meeting when staff will present technical edits and the finalized plan for consideration.
Ending: Council asked staff to provide clearer, item‑level action timelines and to bring the finalized plan for adoption on May 5 so implementation steps can proceed.
