Coverage

28 cities across 3 counties in the Phoenix metro — monitored automatically, every P&Z cycle. The table also lists 1 checked on schedule but never retrievable (Not retrievable); they are not in this count.

The idea is simple: this data is public, and checking the portals is manual work. We automate the manual work — that's it. The table below lists the sources our monitor reads and the expansion candidates it does not yet, where each posts, and when packets typically drop, so you can verify us against the source any time. The status column says which is which.

Coverage is where we start, not where we stop. We follow each case through its stages — hearing scheduled, continued, advanced from Planning & Zoning to Council — flag the ones where staff has recommended denial, and alert on filings near land you own. How that works.

Teal = a portal our monitor read successfully within the last 21 days and holds at least one case from. Grey = on the expansion list.

City and source status

Jump to county: Maricopa · Pima · Pinal

Last checked is when our monitor last read that portal successfully; last packet seen is when the city last published one. They differ whenever a city simply has not met — which is most of the time, and is why both are shown rather than one being made to stand for the other.

Status: Live means our monitor read the portal successfully within the last 21 days and we hold at least one case from it; Seeding means the monitor is configured (its first checks may not have landed yet) and no case has been read from it; Checks stalled means our reads have stopped landing; Not retrievable means the portal answers but has never returned an agenda we can fetch; Coming soon means the city is on the expansion list and not yet checked; Covered by … County means the county's portal carries that city's cases. Rows in those last two states are listed for transparency and are not monitored cities: the count at the top of this page, each county heading and the metros page count only the cities our monitor polls. None of these is a statement about what the city has published or about alerts delivered.

First capture vs. meeting is measured from when our own monitor first captured each packet relative to its meeting date, not from the portal's self-reported publish time; historical archive ingestion is included in that figure until it is separately split, so an old packet captured during a backfill reads as captured after its meeting. State open-meetings law sets a minimum posting notice ahead of each meeting; the period and its exceptions vary by state.

Curious who keeps filing across these cities? See the petitioner index → · Activity trends across the metro →

Start 14-day free trial