Process to Revise Austin’s Land Development Code GENERAL USE George Adams, Assistant Director, PDRD George Zapalac, Division Manager, PDRD Matt Dugan, Development Services Process Coordinator, PDRD A priority program of

Presentation Overview WHY? WHAT? WHO? HOW? WHEN?

Why? Why revise the code?

It’s Time to Revise the LDC when… Last comprehensive revision in proposed amendments since 2005 Over 60 zoning districts Multiple overlay districts on a single property Multiple duplicative & conflicting requirements Complexity convolutes the permitting and approval process It’s not user-friendly

offers clear direction for code revisions Vision statement 30+ policies 40+ actions Priority Program #8 Imagine Austin Provides Opportunity

Code Revision General StepsImagine Austin’s LDC Revision Goals Priority Program #8 Revise Austin’s development regulations and processes to promote a compact and connected city. Complete neighborhoods and expanded housing choices Neighborhood protection Household affordability Environmental protection Efficient service delivery Clear guidance and user-friendly

What? What should be revised?

Regulations relating to… Procedures for review & approval Zoning Subdivisions Site Plans Drainage Transportation Environment Signs On the Table for Reconsideration

Types of Zoning Codes Euclidean / Conventional Separates land uses into zones such as residential, commercial, industrial, etc. Performance Uses goal-oriented criteria to establish review parameters for proposed projects Form-based Addresses the relationship between building facades and the public realm; the form and mass of buildings in relation to one another; and the scale and types of streets and blocks Hybrid Combines one or more types of codes such as Form-Based and Euclidean

Who? Who will revise the code?

City Council Planning Commission Advisory Group Staff Consultant Team Code Revision Core Team

Advisory Group Purpose: Assist with public outreach Provide feedback on development and implementation of a revised code Meets regularly throughout process Advisory Group members: Chris BradfordMelissa Neslund Mandy De MayoStephen Oliver Stephen DelgadoBrian Reis Jim DuncanBeverly Silas Will HerringDave Sullivan Jeff Jack

Staff & Consultant Resources 3 1/2 new staff positions in Planning and Development Review Dept. (PDRD) Support from multiple PDRD divisions and other departments as needed Up to $2M for consultant services and related expenses

Staff & Consultant Resources Opticos Design – Lead consultant Fregonese Assoc. Peter J. Park McCann Adams Cultural Strategies Group Solutions Lisa Wise Consulting RCLCO ECONorthwest Taniguchi Architects Kimley Horn McGuireWoods Urban Design Group

How? How will the code be revised?

Organizing the Process Preliminary outreach to key stakeholders— development and business community, affordable housing, neighborhoods, environment/sustainability, etc. (Complete as of Jan. 17, 2013) Advisory Group appointed (Jan-Feb 2013) “Code 101” and best practices “Headliners” ongoing throughout the process RFQ issued in early November 2012 Consultant Team selected by Council March 21, 2013

Code Revision—Four Steps Listening & Understanding Diagnosis & Outline Preliminary Draft Code Code Adoption 1234

Ongoing Review and Oversight Public Review and Comment Advisory Group Review and Comment Planning Commission Recommendation City Council Approval Planning Commission Recommendation City Council Approval Step 1 Step 2 Step 3 Step 4

Listening and Education Step 1 Designing listening sessions— Advisory Group, consultant, and staff Conduct listening sessions (what works, what doesn’t work, identification of critical issues & divisive topics) Generate contact list of interested parties for ongoing outreach and information Results of listening sessions compiled and provided to consultant team

Code Diagnosis & Outline Step 2 Code Diagnosis (Generated by consultant) Discussion of alternative approaches to critical issues with Advisory Group Prepare draft diagnosis (what’s left alone, what’s to be revised, and what to explore further) Advisory Group and staff review Public and Boards and Commissions review Planning Commission recommends and City Council approves diagnosis Direction from Imagine Austin Input from Listening Sessions

Code Diagnosis & Outline Step 2 Annotated Outline (Generated by consultant) Summary organization of the revised code Community dialogue on alternative approaches to critical issues Advisory Group and staff review Boards and Commissions review Planning Commission recommends and City Council approves outline

Diagnosis & OutlinePreliminary Draft Code Step 3 Initial Draft of Code (Generated by consultant) Based on annotated outline Conduct workshops on draft sections of the code Develop roll-out process for mapping Broad events to allow public to explore and comment on code Advisory Group and staff review Public and Boards and Commissions review Adoption draft of code based on input

Code Adoption Process Step 4 Public Hearings Planning Commission recommends and City Council adopts

When? When will the project be complete?

STEP 1 STEP 2 STEP 3 STEP JUL 2013-JAN 2014 LISTENING & UNDERSTANDING JUL 2013-JUL 2014 CODE DIAGNOSIS & DRAFT CODE OUTLINE AUG 2014-SEPT 2015 CODE DEVELOPMENT OCT 2015-JUNE 2016 CODE ADOPTION TIMELINE: LAND DEVELOPMENT CODE REVISION Next Steps

Summary of Proposal Austin’s land development regulations and process need a holistic review Imagine Austin provides a clear, community-based vision Consultant team authors work products Iterative, step-by-step process and community review Planning Commission recommendations and City Council approvals throughout process

What Does Success Look Like? On time and within budget Open to all Engaging people who use the code Respectful and fair Informative and educational Focus on common ground Avoid assumptions Not letting perfection get in the way of improvement A clear, predictable, user-friendly code that implements

Role of Department Representatives Providing information, resources or expertise to consultant team Meeting with consultant and serving as technical representative for your work area Distributing information, status reports, and work products to your team for review and comment Ensuring staff input from your department is provided to consultant team on schedule and in well-organized format

Questions? G:\Code Revision