My WebLink
|
Help
|
About
|
Sign Out
AGENDA PACKET
City of Pleasanton
>
CITY CLERK
>
AGENDA PACKETS
>
2024
>
082024 WORKSHOP
>
AGENDA PACKET
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/14/2024 10:59:15 AM
Creation date
8/14/2024 10:59:00 AM
Metadata
Fields
Template:
CITY CLERK
CITY CLERK - TYPE
AGENDA REPORT
DOCUMENT DATE
8/20/2024
DESTRUCT DATE
15Y
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
40
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
Affordable Housing Fee – May 7 Findings and City Council Feedback <br />The May 7, 2024 Background Report provides background on the basis for the current <br />Affordable Housing Fee (see Background Report, Pages 5-7). As described in the <br />report, the current fee (just over $52,203 per unit for detached single-family homes, and <br />$51,077 for townhomes and other attached units), does not meet the equivalent cost of <br />constructing an affordable housing unit, particularly for single-family and townhome <br />units. Establishing a better comparability between the cost to build an on-site <br />inclusionary unit and the amount of the in-lieu fee would disincentivize developers from <br />defaulting to payment of the fee. <br />EPS evaluated several scenarios, looking at different inclusionary rates and affordability <br />mixes. Each of those scenarios was used to develop a corresponding maximum <br />supportable housing in-lieu fee. EPS also evaluated the financial feasibility of potential <br />fee increases based on current market factors and a range of market-appropriate <br />assumptions.1 Key findings of the analysis include: <br />Current affordable housing fee rates for single-family and for-sale development is <br />significantly discounted compared to the corresponding cost to build affordable <br />units on-site, so there is some capacity to increase affordable housing and other <br />fees for single-family and townhome projects. <br />With the City’s current 20% inclusionary rate, increasing fees to the maximum <br />level supportable is unlikely to be feasible for most single-family projects. <br />Multi-family rental projects have marginal financial feasibility under current <br />economic conditions, and it will be challenging to increase the current 15% <br />inclusionary rate, or substantially increase the affordable housing fee and other <br />fees. <br />Any increase in affordable housing fees needs to be considered in the broader <br />context of the overall fee burden, including potential increases to the Capital <br />Facilities and Traffic Impact Fee. <br />Based on those findings, among staff’s initial recommendations were for City Council to <br />consider lowering the current 20% single-family inclusionary rate, and to retain (not <br />increase) the current 15% multi-family rate. <br />City Council feedback at the May 7 meeting included: <br />Concern from some Councilmembers that lowering the inclusionary rate would <br />adversely affect the City’s ability meet its RHNA allocation, although others were <br />more comfortable with considering lowering the rate. <br />Broad agreement with staff’s general premise that setting fees at an appropriate <br />rate that does not work against economic development goals was important. <br />Interest in adopting fees formulated on a per-square-foot basis, rather than per <br />unit. <br />Interest in allowing for alternatives that still produced inclusionary units but <br />provided some flexibility to developers (e.g., allowing for different product types <br />or for units to be provided off-site). <br />1 See link for Background Report above: Background Memo, Pages 13-15, for a summary of the scenarios and <br />comparable in-lieu fees per unit. <br />Page 6 of 40
The URL can be used to link to this page
Your browser does not support the video tag.