Coverage
13 cities across 1 counties in the Phoenix metro — monitored automatically, every P&Z cycle.
The idea is simple: this data is public, and checking the portals is manual work. We automate the manual work — that's it. Below is every source we watch, where it posts, and when packets typically drop, so you can verify us against the source any time.
Teal = live coverage (alerts flowing). Grey = on the expansion list.
Every city, every source
| City | County | Where agendas post | P&Z meeting cadence | Packet drop (observed) | Last packet seen | Cases tracked | Status |
|---|---|---|---|---|---|---|---|
| Avondale | Maricopa | avondaleaz.portal.civicclerk.com | Pc 3rd tuesday | ≥72h before meeting (TOMA) | 2026-07-06 | 0 | Seeding |
| Buckeye | Maricopa | — | P&z 2nd & 4th tuesday | ≥72h before meeting (TOMA) | — | 0 | Seeding |
| Chandler | Maricopa | — | 1st & 3rd wednesday | ≥72h before meeting (TOMA) | — | 0 | Seeding |
| Gilbert | Maricopa | gilbert.granicus.com | Pc 1st wednesday | ≥72h before meeting (TOMA) | — | 0 | Seeding |
| Glendale | Maricopa | — | Pc 1st thursday | ≥72h before meeting (TOMA) | — | 0 | Seeding |
| Goodyear | Maricopa | goodyear.legistar.com | 1st & 3rd wednesday | ≥72h before meeting (TOMA) | — | 0 | Seeding |
| Mesa | Maricopa | mesa.legistar.com | P&z 2nd wednesday | ≥72h before meeting (TOMA) | — | 0 | Seeding |
| Peoria | Maricopa | — | P&z 1st & 3rd thursday | ≥72h before meeting (TOMA) | — | 0 | Seeding |
| Phoenix | Maricopa | phoenix.legistar.com | Pc 1st thursday | ≥72h before meeting (TOMA) | — | 0 | Seeding |
| Queen Creek | Maricopa | queencreekaz.granicus.com | P&z 2nd wednesday | ≥72h before meeting (TOMA) | — | 0 | Seeding |
| Scottsdale | Maricopa | — | Pc 2nd & 4th wednesday | ≥72h before meeting (TOMA) | — | 0 | Seeding |
| Surprise | Maricopa | surpriseaz.portal.civicclerk.com | 1st & 3rd tuesday | ≥72h before meeting (TOMA) | 2026-07-10 | 5 | Live |
| Tempe | Maricopa | tempe.granicus.com | Drc 2nd & 4th tuesday | ≥72h before meeting (TOMA) | — | 0 | Seeding |
Packet-drop timing is observed from each portal's publish history; the Texas Open Meetings Act requires posting at least 72 hours before a meeting.