Laserfiche WebLink
units that may be built and identify what year a developer may pull a building permit to <br /> construct the units. As an example, the City Council could approve a PUD for 50 units in <br /> 2015, but authorize issuance of the building permit for these units in 2017. Therefore, <br /> for tracking purposes, the 50 units would be deducted from the annual growth <br /> management limit in 2017. In essence, it's best to think of the current ordinance as <br /> granting a developer a "ticket" to develop a certain number of units in a specific year. <br /> Notwithstanding this current requirement, due to the recent "backlog" of developments <br /> that had "by right" status, this provision of requiring growth management units to be <br /> constructed in a specific year has not been applied. However, with the City's approved <br /> Housing Element, and the lifting of the by right status, it is now necessary to re- <br /> implement this allocation process. <br /> While the current building permit oriented process has value in that a fundamental <br /> purpose of the ordinance is determining when a unit is to be constructed, it creates both <br /> significant administrative tracking issues and, more importantly, a system whereby <br /> developers must regularly request reallocations of their growth management approvals <br /> to accommodate construction schedules that are often impacted by conditions outside <br /> their control such as financing, the economy, design services, etc. The method is also <br /> somewhat confusing to the public who may sense the City Council is approving <br /> residential currently without realizing that it's actually approving development for future <br /> years. <br /> The building permit reallocation and "balancing" process is spelled out primarily in <br /> Section 17.36.090 which establishes a detailed system for determining when and how a <br /> developer requests the moving of building permits from one year to another. Options <br /> identified include trades with other developers, transfers and reallocations, all of which <br /> must be approved by the City Council. While the City Council has employed <br /> subcommittees to oversee the initial reallocation process, the actual approvals are <br /> subject to both City Council action as well as approval from multiple developers willing <br /> to trade and exchange growth management units allocations from one year to another. <br /> The recommended amendment would transition tracking of growth management <br /> approvals from the issuance of a building permit to project approval, which is most <br /> typically PUD approval or in infrequent situations, part of a design review or tentative <br /> map actions. As such, the year that a development is approved would be the year that <br /> the unit would be allocated unless the City Council determined that it should be <br /> allocated to a future year. The specific language implementing this change is included in <br /> Section 17.36.080 (d) as follows: <br /> "Any growth management unit allocation approved by the City Council will be deducted <br /> from the total number of annual growth management unit allocations available for the <br /> year in which the project is approved and from the total number of growth management <br /> unit allocations in the regional housing needs cycle." <br /> One immediate impact of this change is that it would negate a significant amount time <br /> related to unit tracking, proration, trades, and transfers. In addition, the process <br /> alleviates the need to constantly be tracking a developer's intention to pull permits, <br /> which is necessary if the Council and staff expect to know the number of growth <br /> management unit allocations available in any given year. While this change is fairly <br /> Page 3 of 7 <br />