"Is this site already zoned for the units I need, or am I asking the city council for a favor?"
Two paths, but only one is written into state law
Entitlement in Arizona splits the same way it does almost everywhere: an administrative path for a use the zoning already allows, and a legislative or quasi-judicial path for a use it doesn't. The difference from California is that in Arizona this split is not created by a state statute — Arizona's zoning enabling act doesn't itself define a ministerial-versus-discretionary line the way California's SB 423 or AB 2011 do. It's a product of each city's or county's own development code. Nearly every Arizona jurisdiction of any size draws the line the same way in practice — staff-level site plan review for a permitted use, a public hearing and legislative vote for anything that requires a zone change — but that's local convention, not a state mandate, and a specific city's code is the only place to confirm it for a given parcel.
| By-right (site already zoned for the use) | Not by-right (rezoning or conditional use permit needed) | |
|---|---|---|
| Decision-maker | Planning/zoning staff, applying the adopted development code | Planning Commission recommendation, then City Council or Board of Supervisors vote; a conditional use permit may instead route to a Board of Adjustment or Planning Commission depending on the local code |
| State environmental review | None — Arizona has never enacted a state environmental-review statute analogous to CEQA; there is nothing to be exempt from | Same — no state-law environmental-review layer attaches to a rezoning either |
| Public hearings required by state law | Zero | At least one, and only after the citizen review step (A.R.S. § 9-462.03) and mailed/published notice (A.R.S. § 9-462.04) have run |
| What sets the ministerial/discretionary line | The city's or county's own zoning map and development code | Same — not a state statute |
| Realistic duration | Weeks to a few months, staff-paced | Commonly 4–9 months for an uncontested rezoning; well over a year if continued, appealed, or referred to the ballot |
The duration figures are practitioner-level estimates, not measured data — no Arizona agency publishes realized entitlement timelines by pathway (see "What is contested, draft, or unverified").
Order of operations
| Step | Action |
|---|---|
| 1 | Pull the parcel's current zoning district from the city's or county's zoning map and confirm whether the multifamily use — and the density the deal needs — is a permitted use, a conditional use, or not allowed in that district at all. "Zoned multifamily" and "zoned for the density this proforma needs" are not the same fact. |
| 2 | If permitted: route directly to administrative site plan review under the local development code. No rezoning is required. |
| 3 | If conditional: confirm which body actually hears conditional use permits in that specific jurisdiction — it varies by city — and what additional standards attach under A.R.S. § 9-462.01(C)(1). |
| 4 | If not allowed at all: budget for a full legislative rezoning under A.R.S. §§ 9-462.03–9-462.04 inside city limits, or §§ 11-813–11-814 in unincorporated county territory — starting with the mandatory citizen review step, which has to happen before a hearing can even be noticed. |
| 5 | Do not treat a Board of Adjustment variance as a shortcut around a use restriction. A.R.S. § 9-462.06 expressly bars the board from changing the uses permitted in any zoning classification — a variance can relax a setback or height limit, but it cannot add a use the zone doesn't allow. |
| 6 | If the city will condition its zone-change approval on a development schedule, negotiate that condition under A.R.S. § 9-462.01(E) — Arizona's functional substitute for a development agreement, and the mechanism most Arizona cities actually use to lock in unit count, density, and design commitments. |
| 7 | Document the site's zoning/entitlement status for the ADOH application. Every LIHTC application has to show site control and current land-use status; the specific QAP section and documentation format could not be independently confirmed against the current, final QAP text in this research pass (see "The ADOH hook"). |
| 8 | If federal funds sit anywhere in the capital stack — HOME, CDBG, a Section 8 PBV contract, FHA-insured debt, USDA Rural Development 515/538 — run the federal environmental review in parallel. It does not track the local zoning calendar and is frequently the later critical path. |
What the local zoning process actually gates on
Arizona differs from Texas here in a way that matters: Arizona cities, unlike Houston, essentially all have adopted zoning. The state's enabling acts for municipalities and counties are separate statutes with parallel structure, so which one applies depends entirely on which side of an incorporation line the parcel sits on — and that can change mid-application if annexation is pending.
| Provision | Citation | What it does |
|---|---|---|
| General zoning power; what an ordinance may regulate | § 9-462.01(A) | Use of land, height/bulk/number of stories, lot and yard standards, off-street parking, setbacks, special and historic districts |
| Conditional uses | § 9-462.01(C)(1) | Permits a zone to allow certain uses only conditionally, with additional requirements — including site plan review and approval by the planning agency |
| Conditional rezoning tied to a development schedule | § 9-462.01(E) | The legislative body may approve a zone change conditioned on a schedule for developing the specific use requested |
| Citizen review before a rezoning hearing | § 9-462.03 | Adjacent landowners and other potentially affected citizens must be notified of the application and given a chance to raise concerns before the public hearing is scheduled |
| Public hearing notice | § 9-462.04 | At least 15 days' notice; mailed to every owner of record within 300 feet of a non-owner-initiated rezoning site; additional mail/utility-bill-insert/newspaper-display notice triggered by a 10%-or-more change in developable square feet or units, building height, or setback/open-space requirements — but by ANY increase or reduction in permitted uses or in the allowable number of stories, with no percentage threshold on those two; separate mailed notice to any nearby military airport or installation |
| Protest by affected owners; supermajority vote | § 9-462.04(H) | If owners of 20% or more of the property directly affected (by area and number of lots within the notification area) file a written protest, the rezoning cannot become effective except by a three-fourths vote of all members of the governing body — not a simple majority. This is the single biggest vote-count risk on a contested site and is easy to miss if the entitlement plan assumes an ordinary council majority. |
| Board of adjustment | § 9-462.06 | Hears variances and appeals of administrative zoning decisions; cannot change the permitted uses in any zoning classification and cannot grant a variance for a self-imposed hardship |
| Provision | Citation |
|---|---|
| Zoning ordinance and districts | § 11-811 |
| Adoption and amendment; notice; hearing | § 11-813 |
| Rezoning; conditional zoning change; notice; hearing; citizen review | § 11-814 |
Structurally a near-mirror of the municipal statute — relevant to rural and reservation-adjacent LIHTC sites, common in border counties and on tribal-adjacent land outside any city. Like the municipal statute, § 11-814(E) carries its own protest/supermajority trigger: in counties with five or more supervisors, a written protest from owners of 20% of the affected property (by area and number) forces a three-fourths board vote instead of a simple majority; in counties with fewer than five supervisors, a simple majority governs regardless of protest.
One further wrinkle worth pricing in: Arizona's Private Property Rights Protection Act (A.R.S. § 12-1134, enacted by the 2006 Proposition 207 ballot initiative) requires compensation when a land-use law enacted after a property changed hands reduces that property's fair market value. It does nothing to help a developer seeking an upzoning — it protects existing owners against a value-reducing change — but it's a real reason Arizona cities are often cautious about downzoning parcels near a project, and it shapes what conditions a city is willing to attach to an approval.
The 2024–2026 state housing-supply laws — and why they mostly don't reach a LIHTC apartment deal
The Arizona Legislature has been genuinely active on housing supply since 2024, adding several by-right preemption statutes to Title 9. None of them creates anything like California's SB 423 or AB 2011 — a state-law ministerial approval for a mid-rise or garden-apartment LIHTC building. Every one of them is scoped to small-scale, missing-middle, or single-family product instead.
| Attribute | Requirement |
|---|---|
| Applicability | Municipalities with population over 75,000 |
| By-right allowance | One attached and one detached ADU as a matter of right — no public hearing, variance, conditional use permit, or special exception; a second detached ADU on lots of one acre or more if at least one unit is restricted-affordable |
| Size cap | The lesser of 75% of the primary dwelling's gross floor area or 1,000 square feet |
| Restrictions on cities | Cannot require parking or a fee in lieu of parking; cannot mandate design matching; cannot set setbacks over 5 feet from the property line; cannot require public street improvements beyond construction-damage repair |
| Enforcement deadline | Cities that had not adopted compliant regulations by January 1, 2025 must allow unlimited ADUs on residentially zoned lots |
| Attribute | Requirement |
|---|---|
| Applicability | Municipalities with population of 75,000 or more |
| Mandatory zoning areas | All single-family zones within one mile of the central business district, plus at least 20% of any new development exceeding 10 contiguous acres |
| Allowed housing types | Duplexes, triplexes, fourplexes, townhomes |
| Restrictions on cities | Cannot make middle housing impracticable; cannot limit it to fewer than two floors; floor area ratio floor of 50%; cannot require owner-occupancy; cannot require more than one parking space per unit |
| Enforcement deadline | On or before January 1, 2026; a city that misses it must allow middle housing on every single-family-zoned lot with no limitations |
| Class | Product | Size range | Effective |
|---|---|---|---|
| 1 | Single-family home | 800–2,000 sq ft | Beginning July 1, 2026 |
| 4 | Accessory dwelling unit | 200 / 600 / 1,000 sq ft options | Beginning July 1, 2026 |
| 2 | Duplex | 400–1,000 sq ft per unit | Beginning January 1, 2027 |
| 3 | Triplex | 400–1,000 sq ft per unit | Beginning January 1, 2027 |
Municipalities must maintain at least three preapproved elevation options per class and accept submissions without restricting who may apply.
| Attribute | Requirement |
|---|---|
| Applicability | Municipalities with population between 200,000 and 500,000 |
| Trigger | A qualifying employer with more than 1,000 full-time employees at average annual compensation above 125% of the median wage |
| Process | No public hearing required for the ancillary multifamily/hotel use; the city may not unreasonably withhold a building permit or delay a building inspection |
| Density / affordability | Up to 27 multifamily units per gross acre; at least 5% of for-rent multifamily units affordable for a minimum of 10 years |
Narrow by design — it reads as drafted around a specific major-employer project rather than as a general-purpose housing tool. Whether any LIHTC deal will ever qualify under it is unconfirmed.
None of these statutes reaches the unit count or density of a typical tax-credit apartment building, and none displaces the § 9-462.03/§ 9-462.04 rezoning process for a site that isn't already zoned multifamily. They're worth tracking — the legislative direction is unmistakable — but nothing here should be modeled today as a shortcut for a conventional LIHTC deal.
The federal overlay that runs regardless of the local path
Because Arizona has no state environmental-review statute, there is no local process that substitutes for federal review when federal money or federal mortgage insurance is anywhere in the capital stack. That review runs on its own calendar and is easy to miss entirely if the entitlement timeline is built around the city's process alone.
| Trigger | Review | Citation |
|---|---|---|
| HOME, CDBG, HTF, Section 8 project-based vouchers, HUD 221(d)(4)/223(f) insurance | NEPA environmental review as implemented by HUD | 42 U.S.C. § 4321 et seq.; 24 CFR Part 58 |
| USDA Rural Development 515/538 financing — common on rural Arizona and border-county deals | USDA's own environmental review procedures | 7 CFR Part 1970 |
| Federal funds that displace existing occupants or acquire the site | Uniform relocation and real property acquisition requirements | 42 U.S.C. § 4601 et seq.; 49 CFR Part 24 |
| Same federal-nexus triggers as NEPA/Part 58 | Historic-property and tribal consultation review | 36 CFR Part 800 (Section 106, National Historic Preservation Act) |
| HUD-assisted or HUD-insured sites generally | Site-and-neighborhood / undue-concentration review baseline | 42 U.S.C. § 3601 et seq. (Fair Housing Act) |
This isn't a QAP artifact — it's federal law that applies in Arizona exactly as it applies in every other state. A purely local, zoning-only entitlement analysis will miss it completely on any deal that layers HOME funds, RAD, project-based vouchers, or USDA financing under the credits.
The ADOH hook — and where this research hit a wall
The Arizona Department of Housing (ADOH) is the sole state agency responsible for allocating both federal 9% and 4% Low-Income Housing Tax Credits, under the requirement in 26 U.S.C. § 42(m)(1) that a housing credit agency allocate credits pursuant to a qualified allocation plan adopted after a public hearing on reasonable public notice. ADOH also administers Arizona's own state affordable-housing tax credit alongside the federal program.
As a matter of near-universal practice among state housing credit agencies, an ADOH application has to document site control and the parcel's current zoning/land-use status — that showing is where the entitlement-pathway work done in this phase gets consumed by the tax-credit application. What this research could not do is read the current, final 2026-2027 QAP's actual section-and-point-value text for that requirement: housing.az.gov sits behind bot-management protection that blocked every automated retrieval attempt made for this guide, including direct download, a cached-copy search, and a rendered-browser fetch. Do not treat any specific ADOH QAP section number or point value for site control/zoning documentation as confirmed until it has been read directly from the current PDF.
What is contested, draft, or unverified
**The ADOH QAP's specific site-control and zoning-documentation requirement was not read from the primary document.** Everything else in this guide about the QAP — that it's the 2026-2027 cycle, that ADOH posted a final signed version on December 30, 2025 under Information Bulletin IB 50-25, and that a separate redlined version tracks the 2027 amendments — comes from indexed search-result text genuinely tied to those documents, not from having read the PDF itself. The exact section number, point value, and required documentation format for site control/zoning at application need to be confirmed directly against the current QAP before being relied on.
**No verified, measured entitlement-duration data exists for Arizona by pathway.** The 4–9-month and "well over a year" figures in the first table are practitioner-level estimates, not agency-published data — no Arizona agency publishes realized time-to-entitlement by city or by approval type.
**The judicial-review standard for a denied Arizona rezoning was not verified.** This guide makes no claim about how deferential Arizona courts are to a local legislative body's zoning decision, or what litigation exposure attaches to a denial — that would need to be checked against actual Arizona case law before being built into an underwriting assumption.
**§ 9-461.19's real-world relevance to LIHTC deals is unconfirmed.** Its population band (200,000–500,000) and 1,000-employee trigger read as drafted around one specific project rather than as general housing policy; whether it has ever been or will be used by an affordable-housing developer was not established here.
Where this goes wrong
- Treating a Board of Adjustment variance as a way around a use restriction. A.R.S. § 9-462.06 explicitly bars the board from changing the permitted uses in any zoning classification — a variance can relax a dimensional standard, but only a rezoning or conditional use permit can add a use the zone doesn't allow.
- Confirming a site is "zoned multifamily" from a GIS layer without checking whether the allowed density matches what the deal needs. Many multifamily zoning districts cap density well below what a competitive tax-credit project needs per acre — "zoned for apartments" and "zoned for enough units" are different facts.
- Scheduling a rezoning around a single public hearing and missing that the § 9-462.03 citizen review step has to happen before the hearing can even be noticed — it adds real weeks to the front of the calendar that a generic hearing-date estimate skips.
- Assuming a contested rezoning only needs the ordinary council majority. A.R.S. § 9-462.04(H) (and the county equivalent, § 11-814(E), in counties with five or more supervisors) requires a three-fourths supermajority vote of the governing body whenever owners of 20% or more of the affected property file a written protest — a real risk on any site with organized neighborhood opposition, and one that can flip an otherwise-winnable rezoning vote count.
- Assuming the 2024–2026 ADU, middle-housing, or starter-home laws help a 60–200 unit apartment deal. They're capped at duplex/triplex/fourplex/single-family/ADU scale and don't reach mid-rise or garden-apartment multifamily zoning at all.
- Missing that conditional zoning under § 9-462.01(E) is a two-way commitment, not a one-time approval — once a development schedule is written into the rezoning ordinance as a condition, missing that schedule can put the zoning itself at risk, not just the project timeline.
- Assuming federal environmental review is handled because local entitlement is done. Arizona has no state CEQA-equivalent, so nothing stands in for NEPA/24 CFR Part 58 (or USDA's 7 CFR Part 1970) review when HUD or USDA financing is in the stack — it runs on its own calendar, independent of the city's zoning process.
- Building a rezoning timeline around only the City Council vote and missing that most Arizona cities require a separate Planning Commission recommendation hearing first — two hearings, each with its own notice and continuance risk, not one.
- County-versus-city confusion for a site near a municipal boundary. The applicable statute (§ 11-813/§ 11-814 for the county, § 9-462.03/§ 9-462.04 for a city) and the deciding body depend on which side of the line the parcel sits on, and pending annexation can shift that mid-application.
- Relying on a specific ADOH QAP section citation for the site-control/zoning showing without having checked it against the current, final QAP text — the exact section number was not independently confirmed in the research behind this guide.
- Assuming Prop 207 (A.R.S. § 12-1134) creates leverage for the applicant. It compensates existing owners for a value-reducing zoning change; it does nothing to help a developer seeking an upzoning, and mainly explains city caution about downzoning nearby parcels, not help getting the project's own zone change approved.
- HUD
- LIHTC
- State QAPs
- IRS § 42
- Housing Finance Agencies