My WebLink
|
Help
|
About
|
Sign Out
CITY COUNCIL REGULAR MEETING AGENDA PACKET
City of Pleasanton
>
CITY CLERK
>
AGENDA PACKETS
>
2024
>
121724
>
CITY COUNCIL REGULAR MEETING AGENDA PACKET
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
12/11/2024 11:39:08 AM
Creation date
12/11/2024 11:13:09 AM
Metadata
Fields
Template:
CITY CLERK
CITY CLERK - TYPE
AGENDA REPORT
DOCUMENT DATE
12/17/2024
DESTRUCT DATE
15Y
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
893
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
Pleasanton Comprehensive Fee Update and Nexus Study November 2024 <br />5 <br />Impact fee revenues are used to cover the cost of constructing capital and infrastructure <br />improvements required to serve new development and growth in the area in which they <br />apply. As such, impact fees must be based on a reasonable nexus, or connection, <br />between new development and the need for specific capital facilities and improvements. <br />Impact fee revenue cannot be used to cover the operation and maintenance costs of <br />these or any other facilities and infrastructure. In addition, impact fee revenue cannot be <br />collected or used to cover the cost of preexisting infrastructure needs or deficiencies. <br />In establishing, increasing, or imposing a fee as a condition for the approval of a <br />development project, Government Code 66001(a) and (b) require a local agency to: <br />1.Identify the purpose of the fee; <br />2.Identify how the fee is to be used; <br />3.Determine how a reasonable relationship exists between the fee use and type of <br />development project for which the fee is being used; <br />4.Determine how the need for the public facility relates to the type of development <br />project for which the fee is imposed; and <br />5.Show the relationship between the amount of the fee and the cost of the public <br />facility. <br />In September 2021, the State of California adopted Assembly Bill (AB) 602, which <br />includes several new requirements related to the development and implementation of <br />impact fee programs. The key provisions related to the calculations documented in this <br />Nexus Report are summarized below. <br />x Capital Improvement Plan: AB 602 requires that jurisdictions adopt a capital <br />improvement plan as part of the nexus study process. This adoption can occur at <br />the same time as the fee ordinance adoption. Accordingly, this Nexus Study relies <br />on a Pleasanton DIF Long-Term Capital Improvement Plan (Pleasanton DIF CIP) to <br />be approved by the City Council in conjunction with the DIF Program. 1The <br />Pleasanton DIF CIP presented in this Nexus Study is derived from the capital <br />improvements identified as part of the Nexus Study and is attached as Appendix <br />Table A-1. <br />x Explanation of Level of Service and Fee Increase: AB 602 requires that when <br />applicable, the nexus study identifies the existing level of service for each public <br />facility, identifies the proposed new level of service, and includes an explanation of <br />why the new level of service is appropriate. This Nexus Study relies on service <br />standards developed in consultation with City staff, based on City planning <br />documents, and with reference to the existing capital facilities and improvements in <br />1 The Pleasanton DIF CIP is different from and does not replace the City's 5 year CIP budget <br />(balanced) and 10 year CIP. These separate CIP documents serve a shorter-term frame and <br />generally rely on more specific project parameters than the DIF CIP. That said, the DIF CIP <br />may provide funding to support some projects included in the 5-year and 10-year CIPs. <br />Page 66 of 893
The URL can be used to link to this page
Your browser does not support the video tag.