EarlyDocket · week of 2026-10-12

What moved in Florida development this week

Coverage in this issue: Miami (3,396 permits read) over the last 7 days, plus 8,077 scanned agenda items across county and city bodies. Every line below is checkable — permits by number, address and — where the authority prints one — the parcel folio, so a row can be pulled straight from the county's own record; agenda items against the meeting's own published agenda document.

Largest permits issued

Land-use hearings still ahead

Zoning public hearings, rezonings, planned unit developments, site plans, plats and comprehensive-plan items whose next hearing had not yet been held when this issue was generated on 2026-10-12 — the decisions that precede the permits above by 12–24 months. The date is the one the authority printed: the agenda the item sits on, or the date that body continued it to, stated in that same document. In this issue the bodies with a hearing still ahead are Broward County, Clearwater, Coral Gables, Delray Beach, Hallandale Beach, Hillsborough County, Hollywood, Jacksonville. We also read Coconut Creek, Doral, Fort Lauderdale, Miami-Dade County BCC, Miramar, Ocala, Pinellas County, Plant City, Polk County, and none of them has a land-use item with a future hearing date in the agendas they have published so far.

Heard recently — context, not a lead

These hearings have already happened. They are printed separately, and never under a heading that says “on the docket”, because a hearing you cannot attend is not the product: an earlier issue of this digest published four Miami-Dade rows from meetings on 2026-07-23 and 2026-06-18 as though they were upcoming. They are here because the outcome of a heard item is how you tell what a jurisdiction is approving.

The bodies you asked us to diary

Read from each authority’s own calendar in the same run that produced this issue. Miami-Dade County comes from the county’s events API and City of Miami from the city’s granicus calendar; neither is a Legistar tenant, which is why they were missing from this page until 2026-07-31. A body with nothing listed says so, next to the date of the last agenda we actually read from that jurisdiction, so “in recess” and “we cannot read this clerk” are never printed as the same thing.

Scheduled next, agenda not published yet

These meetings are on the clerks’ own calendars and we have not been able to read an agenda for them, because none exists yet. This is the difference between “nothing is happening” and “the agenda has not posted”, and it is the only honest way to read an empty week. 23 land-use meetings are on the watchlist within 60 days; the machine-readable copy, including the ones whose agenda we HAVE read, is at /hearings.json.

Recall audit — how much of each agenda is here

Every other check on this page proves that what we printed is real. None of them can notice what we missed, because a missing item has no row to test. So each agenda cited above is re-opened and its land-use items counted, and the difference is printed here. Run by recall-audit.py on 2026-10-12. This issue cites 15 agendas. For the 15 of them the audit has re-opened, their clerks listed 177 land-use items, and the four count columns sum to that total, row by row. This issue prints 20 items in all. 144 were read, passed the publish rule, and were still held back because this issue caps any one body at 4 rows — they are not lost, they are queued, and a subscriber file is not capped. 13 were read and then dropped by the publish rule in agenda_quality.py (no parcel named, line-wrap fragment, meeting boilerplate). 0 were never read at all — the failure this table exists to make visible.