Phoenix rezoning trends
What 1,024 tracked cases across 29 Phoenix cities show about where and what is getting entitled. Built from official Planning & Zoning agendas, updated as packets drop.
Busiest of the last 12 completed months (Nov 2025 – Oct 2026): Sep 2026 with 188 cases scheduled.
Data current as of — updated as agenda packets are captured. Activity here reflects the cases in our collected archive grouped by their scheduled hearing date, not confirmed hearings or approvals.
Tracked cases by scheduled hearing month — last 12 completed months (Nov 2025 – Oct 2026)
November 2026 is still in progress and is not charted; hearings already held this month appear in the public archive as they are captured. Counts are the cases we captured, grouped by scheduled hearing date — coverage varies by city and month, so month-to-month changes reflect our capture as well as market activity.
Case types
Most active cities
By county
Watch how to use these trends · 2:41
The charts summarize the archive, not completed construction or final approvals: use them to form a question, then answer it from the records.
Recorded September 2026 using historical records; the site may have changed since. Not a live feed.
Read the transcript
Once you have explored individual cases, the next question is how to follow the activity that matters to your team. You may care about a particular applicant, a corridor or a few cities. P&Z Radar’s public archive can help you define that focus. Let’s look at applicant history and market activity, then review the monitoring options without turning every filing into an inbox distraction.
The petitioner index groups names found in the collected cases. Open one and you can review its recorded filings, cities and dates. This is useful background when researching who is active in a market. Treat the name as it appears in the record, and check the individual cases before assuming two similar names are the same organization. A filing history is research material, not proof that someone is currently buying your service.
Next, look at trends. The charts summarize the archive by scheduled hearing month, case type and geography. They can help you decide where to investigate next, but they are not a count of completed construction or final approvals. Changes can also reflect what was captured in the archive. Use the chart to form a question, then move back to individual records and sources to answer it.
Now define what your team actually needs to follow. One city, a county and a whole metro are different research scopes. Review the available coverage before choosing one. The product describes matching alerts and keyword filters; the public trial gives you a way to evaluate the data in a city. Start narrowly enough that you can read what arrives and judge whether the matches are relevant.
For a team workflow, review how the information is delivered. The site describes email and private RSS options, with API access on the eligible plans. Developers should check the documented host, authentication and limits before connecting a system. Keep private feed links and API keys private. An integration is only useful when it brings the right records into a place your team actually checks and preserves a link back to the source.
For your first week, choose one market, a small set of research questions and a simple way to review the results. Use applicant history to understand context, trends to spot areas worth investigating, and the original packets to check important details. Then evaluate whether ongoing monitoring earns a place in your routine. Start with the public archive and coverage page, and move into a trial when the records look relevant to your work.
Most active petitioners
The applicants filing most often — click through for their full filing history.
Browse by city: Phoenix · Chandler · Casa Grande · Tempe · Maricopa County · Pinal County · Surprise · Mesa · Peoria · Eloy · Wickenburg · Avondale
P&Z Radar AI agent · Expand
Hi, I’m Pip. How can I help?