Citizen Portal
Sign In

Get Full Government Meeting Transcripts, Videos, & Alerts Forever!

Get email alerts on the Wildfire Resilience topic

No spam. Unsubscribe anytime.

Planning commission backs moving draft wildfire‑resilience zoning code toward formal notice, limits scope to commercial and multifamily projects

Phoenix Planning Commission · July 14, 2026
AI-Generated Content: All content on this page was generated by AI to highlight key points from the meeting. For complete details and context, we recommend watching the full video. so we can fix them.

Summary

Staff presented draft chapter 3.13 to require fire prevention plans and fuel‑modification measures for new development; commissioners expressed support for limiting mandatory fire‑department review to commercial and multifamily projects and asked staff to consult Ashland and fire officials before DLCD notice.

Phoenix planning staff presented a draft wildfire‑resilience amendment to the city’s development code (draft chapter 3.13) at the July 13 Planning Commission meeting and won broad informal support to proceed toward formal notice after further consultation.

Planner Jeff Wilcox told commissioners the draft arose from a 2025 wildfire audit and focuses on three areas: wildfire‑resistant landscaping, structure hardening to reduce risk to buildings, and limited adjustments to historic‑preservation standards to improve safety. Wilcox described two central requirements in the draft: a fire prevention and control plan submitted at time of development review and subsequent implementation through a fuel‑modification requirement on the site.

Wilcox said the draft draws heavily on the City of Ashland’s code as a starting point and that staff seeks a practical approach that does not make new development “exorbitantly expensive.” He explained applicability in the draft generally covers new development and redevelopment; for residential projects the threshold under discussion was three dwelling units or greater for plan submittal, while small accessory additions would trigger a smaller 30‑foot defensible‑space requirement.

Commission discussion focused on two operational questions: when the fire district must be involved and how to avoid imposing retroactive costs on existing homeowners. Several commissioners urged that the fire district need not be deployed for every small permit; staff agreed to revise thresholds so commercial and multifamily projects would more clearly trigger formal fire‑department review, while single‑family and small accessory projects would generally rely on planning staff review unless the situation merits additional scrutiny.

Commissioners also debated technical prescriptions in the draft, including a 0‑to‑5‑foot noncombustible zone immediately around structures, fencing material restrictions (metal gates or treated alternatives), and a requirement that roof coverings be Class B or better when 50% or more of a roof is replaced. Wilcox said he would follow up with Ashland and fire officials on enforcement mechanisms such as permit triggers and verification timing.

On financing and incentives, commissioners asked whether the city could pair requirements with incentives such as modest water‑bill discounts or grant programs to offset costs of defensible‑space work; Wilcox said he would investigate options and report back. Staff told the commission it needs 35 days to notice the Department of Land Conservation and Development (DLCD) and proposed returning in August or September with updated code language and implementation details.

The commission did not take a formal adoption vote on July 13; instead it gave staff direction to refine the draft, consult Ashland and fire professionals, limit the initial mandatory scope to commercial and multifamily thresholds, and proceed with DLCD notice when ready.