Phoenix General Plan: Long-Term City Growth and Vision

The Phoenix General Plan is the legally mandated, long-range policy document that guides land use, transportation, housing, infrastructure, and environmental decisions across Arizona's largest city. State law requires Arizona municipalities with populations exceeding 2,500 to maintain a general plan, and Phoenix — covering approximately 517 square miles — operates under one of the most complex versions in the Southwest. This page explains the plan's structure, the forces that shape it, how it classifies land and policy priorities, and where its provisions are most contested.

• Definition and scope
• Core mechanics or structure
• Causal relationships or drivers
• Classification boundaries
• Tradeoffs and tensions
• Common misconceptions
• Checklist or steps
• Reference table or matrix
• References

Definition and scope

The Phoenix General Plan is a comprehensive policy framework adopted by the Phoenix City Council that establishes the city's vision for physical development over a planning horizon of roughly 25 years. Under Arizona Revised Statutes § 9-461.05, general plans in municipalities of Phoenix's size must address at minimum land use, circulation, open space, growth areas, environmental planning, cost of development, water resources, and housing. Phoenix's plan — marketed under the brand name PHX Forward in its most recent cycle — incorporates all mandatory elements and adds supplemental elements covering urban design, economic development, public safety siting, and arts and culture.

The plan applies to all land within Phoenix's incorporated limits. It does not govern unincorporated Maricopa County land, state trust land held by the Arizona State Land Department, tribal land, or incorporated areas of adjacent cities such as Scottsdale, Tempe, or Glendale. The Maricopa County Planning and Development Department administers separate regulations for unincorporated parcels that physically border Phoenix but fall outside city jurisdiction. State trust land — which accounts for significant acreage on Phoenix's fringe — follows the disposition process managed by the Arizona State Land Department, not the general plan, until annexation occurs.

Core mechanics or structure

The general plan operates through a layered system of maps, goals, policies, and implementation measures. The Land Use Map is the plan's most operationally significant component: it assigns future land use designations — such as Residential, Commerce, Employment, or Mixed-Use — to every parcel within city limits. These designations do not directly regulate development but set the policy framework within which zoning codes operate. A parcel's zoning must be consistent with its general plan designation; any rezoning that conflicts with the plan requires a concurrent plan amendment.

Plan amendments fall into two categories. Major amendments involve large land areas or significant policy changes, require a public hearing before the Phoenix Planning and Development department, a recommendation from the Planning Commission, and final action by the City Council. Arizona law mandates that major amendments be voted on no more than twice per calendar year. Minor amendments address smaller parcels or technical corrections and may be processed on a more frequent schedule.

The plan is also structured around Urban Villages, a geographic organizing framework unique to Phoenix. The city is divided into 15 urban villages, each with its own Village Planning Committee that provides localized input on land use and development proposals. The Phoenix Urban Villages framework routes neighborhood-level concerns into the broader plan's implementation. Village Planning Committees advise the Planning Commission but do not hold final approval authority; final decisions rest with the City Council.

Arizona law requires that general plans be readopted or updated at least every 10 years. Phoenix ties major updates to civic engagement campaigns, environmental impact analyses, and infrastructure capacity studies.

Causal relationships or drivers

Several quantifiable pressures drive the plan's content and revision cycles. Phoenix added approximately 163,000 residents between 2010 and 2020 (U.S. Census Bureau, 2020 Decennial Census), placing sustained demand on land supply, transportation networks, and water infrastructure. The Salt River Project and City of Phoenix Water Services (Phoenix Water Services) project demand scenarios decades into the future, and water availability findings are legally required to accompany major land use designations under Arizona's Assured Water Supply program, administered by the Arizona Department of Water Resources.

Regional transportation investment shapes land use patterns as strongly as any zoning decision. Light rail corridors managed through Valley Metro have historically concentrated higher-density land use designations along transit alignments. The Metropolitan Planning Organization for the Phoenix region — the Maricopa Association of Governments (MAG) — produces the long-range Regional Transportation Plan, which the general plan must coordinate with rather than contradict.

Phoenix economic development goals also drive plan policies. Employment-intensive designations are strategically placed near Sky Harbor International Airport, along Interstate 10 and Interstate 17 corridors, and within designated Opportunity Zones to align land use with job creation targets.

Climate and environmental pressures have become structural drivers since the 2000s. Phoenix recorded a 24-night streak of temperatures above 90°F in July 2023 (National Weather Service, Phoenix Forecast Office), reinforcing the policy weight of the Phoenix Heat Action Plan and its integration into general plan environmental elements covering urban tree canopy, heat island mitigation, and green infrastructure standards.

Classification boundaries

The Land Use Map uses a hierarchy of designations, each with defined intensity ranges. Key designations and their general parameters include:

• Residential Village Core (RVC): Higher-density mixed residential, typically associated with urban village cores and transit proximity.
• Residential (R): Low- to moderate-density single-family and multifamily uses, the predominant designation by land area.
• Commerce (C): Retail, services, and neighborhood commercial nodes.
• Employment (E): Office, light industrial, and business park uses.
• Mixed-Use (MU): Horizontal and vertical integration of residential with commercial or employment uses, primarily mapped along transit corridors.
• Public/Quasi-Public (PQP): Government facilities, schools, hospitals, and institutional uses.
• Open Space/Recreation (OSR): Parks, preserves, and the Phoenix Mountain Preserve system.

A parcel may carry only one primary general plan designation. When a proposed development's density or use type exceeds what the designation allows, the applicant must file a plan amendment before or concurrent with a rezoning request. This sequencing — plan amendment preceding or accompanying zoning change — is a hard procedural requirement under Arizona statute.

Tradeoffs and tensions

The general plan sits at the intersection of competing priorities that cannot all be fully satisfied simultaneously.

Infill vs. Greenfield Development: Phoenix contains significant vacant and underutilized land within its already-urbanized footprint. Infill development reduces infrastructure extension costs and supports transit ridership, but encounters resistance from established neighborhoods protective of existing density and character. Greenfield annexations on the city's periphery offer development ease but impose long-term infrastructure maintenance obligations on the city.

Housing Affordability vs. Neighborhood Character: Higher-density designations near employment centers and transit are a recognized tool for expanding housing supply. Arizona's Housing Supply Study has identified Phoenix as among the state's highest-need markets for workforce housing production. Density increases often generate organized opposition from Village Planning Committees and adjacent property owners citing traffic, parking, and scale incompatibility.

Water Supply Limits vs. Growth Ambition: Arizona's Assured Water Supply program requires municipalities to demonstrate 100 years of physically, legally, and continuously available water before approving new residential subdivisions. Phoenix holds senior Colorado River water rights through the Salt River Project and Central Arizona Project allocations, but reductions in Lake Mead storage — triggered by Bureau of Reclamation Tier 1 and Tier 2 shortage declarations beginning in 2021 — have tightened the margin available for future growth commitments.

Regional Coordination vs. Municipal Autonomy: The general plan operates within a web of regional frameworks — MAG's long-range transportation plan, the Central Arizona Association of Governments, and county-level plans — but Phoenix retains independent land use authority within its borders. Coordination is policy-driven and voluntary except where state law mandates consistency. This creates seams where Phoenix planning decisions affect neighboring jurisdictions without binding coordination mechanisms.

Common misconceptions

Misconception: The general plan directly controls what can be built on a specific parcel.
Correction: The plan sets policy direction and designations, but actual development rights are established through the zoning ordinance. A parcel designated "Mixed-Use" under the general plan is not automatically approved for a mixed-use building; it must also carry compatible zoning. The plan authorizes the zoning direction — it does not replace the zoning code.

Misconception: Village Planning Committees can approve or deny projects.
Correction: Village Planning Committees are advisory bodies. They transmit recommendations to the Planning Commission and City Council, which hold decisional authority. A unanimous Village Planning Committee objection can be — and has been — overruled by the City Council.

Misconception: The general plan applies to all land within Phoenix's metro region.
Correction: The plan's legal authority extends only to parcels within Phoenix's incorporated city limits, covering approximately 517 square miles. The broader Phoenix metropolitan area, as defined by the U.S. Office of Management and Budget, encompasses the entire Maricopa-Glendale-Scottsdale Metropolitan Statistical Area, which spans multiple jurisdictions with entirely separate planning documents.

Misconception: A general plan update automatically changes existing zoning.
Correction: Plan amendments and zoning changes are separate legal acts. A land use designation change requires a subsequent — or concurrent — rezoning action to have regulatory effect on what may be built. The plan is policy; the zoning code is law.

Checklist or steps

The following sequence describes the standard major general plan amendment process in Phoenix as structured by Arizona statute and Phoenix Planning and Development procedures:

1. Pre-application conference with Phoenix Planning and Development staff.
2. Filing of a formal General Plan Amendment application with required exhibits, including site plan, legal description, and water availability documentation where applicable.
3. Staff completeness review; application deemed complete or returned for supplementation.
4. Neighborhood notification distributed to property owners within 300 feet and applicable Village Planning Committee.
5. Village Planning Committee review meeting; written recommendation forwarded to Planning Commission.
6. Planning Commission public hearing; staff report and recommendations presented; commission vote on recommendation to City Council.
7. City Council public hearing; final vote on plan amendment adoption.
8. If major amendment approved, concurrent or subsequent rezoning application processed through standard zoning code amendment procedures.
9. Post-adoption recording of plan amendment and update to official Land Use Map maintained by Phoenix Planning and Development.

Reference table or matrix

The full scope of Phoenix's civic planning framework — including how the general plan interfaces with the city budget, capital improvement planning, and intergovernmental agreements — is indexed on the Phoenix Metro Authority home page.

References

• Arizona Revised Statutes § 9-461.05 — General Plan Requirements
• City of Phoenix Planning and Development Department
• Arizona Department of Water Resources — Assured Water Supply Program
• U.S. Census Bureau — 2020 Decennial Census, Phoenix City Data
• Maricopa Association of Governments (MAG) — Regional Transportation Plan
• U.S. Bureau of Reclamation — Colorado River Shortage Declarations
• Arizona Department of Housing — Housing Supply Study
• National Weather Service Phoenix Forecast Office
• U.S. Office of Management and Budget — Metropolitan Statistical Area Definitions