SF, Boston, Nashville Are Generating 81% of Tracked Council Activity. That's a Land-Use Signal.

Boston, San Francisco, and Nashville produce 80% of new council-meeting records right now. The volume itself is a leading signal for which markets are actively reshaping their development rules.

The Setup

Across the 22 metros tracked, the Granicus civic-record feed (council minutes, resolutions, public hearing transcripts) produced the following volume in the last 30 days:

The top three (SF, Boston, Nashville) account for 81% of total tracked council records. The bottom three (Atlanta, Houston, NYC) account for under 1% combined. This is not a population-weighted distribution — Houston and NYC have larger populations than every metro on the list except Boston. The volume difference is about how much governance is happening in public, in writing, on a given day.

The Chain

Council-record volume tracks three things, in roughly this order: (1) procedural transparency norms in the local government — Boston and SF run highly-documented public processes, Houston runs a comparatively private one; (2) actual legislative throughput — Nashville's 567 records in 2 active days is a burst pattern that usually indicates a packed agenda window, often around budget cycles or zoning code amendments; (3) ingestion-side coverage on our end — Atlanta and NYC have known ingestion gaps that bias their counts low.

Filter for (3) by checking the active-days metric. SF and Boston each had 14 active days in the window — meaning the ingester pulled records on every other day on average. That's healthy coverage. Nashville's 2 active days for 567 records means the entire month's volume came from two large meetings — most likely the Metro Council's monthly session and a planning commission special session. That burst pattern is meaningful: it indicates a deliberation event, not a steady-state.

The land-use connection is mechanical. Council records are where upzoning happens — every one of: rezoning ordinances, ADU pilots, density bonus passages, IZO amendments, parking-minimum reductions. None of these go from idea to law in a single meeting. They typically appear in committee minutes 6-18 months before they become enforceable. Council-record density is therefore a leading indicator of the regulatory environment a developer will be operating in 1-2 years out.

The Implication

For a developer or land banker, the high-volume metros are the ones to underwrite as policy-active over the next two years. SF and Boston are obvious — both have published housing-element processes and active downzoning/upzoning fights — but the Nashville signal is the surprise. 567 records in 2 active days is the kind of volume that generates 50+ pages of zoning-relevant text per session. The most likely interpretation: Nashville Metro Council is moving on either the Land Use Element update or the Inclusionary Housing Ordinance revision, both of which have been on the agenda for the last two budget cycles.

The Houston/Atlanta low end has a different read. Low ingestion is partly an ingester-coverage gap — both are governed by city councils plus county commissioner courts that publish through different systems. But it's also a real signal: these are markets where land-use decisions happen primarily through administrative processes (Houston has no zoning code in the conventional sense) or through council actions that don't generate written minutes the way SF's do. A developer in those markets gets less leading-indicator value from public records and has to rely more on individual entitlement filings, which arrive later in the cycle.

What to Watch

• Nashville's record-burst sustainability. If May produces another 500+ records, Nashville is in an active land-use legislative period and the burst pattern is the new normal. If it drops back to 100-200, the April spike was a one-off planning session.
• Boston's fall budget cycle. Boston Council typically pivots from operating-budget review (April-June) to zoning and planning ordinances (September-November). Watch the September-November record stream for housing-element amendments specifically.
• Phoenix and Miami pickup. Both saw modest volumes (246 and 146 records) but with limited active days. If their active-days count climbs to 8-10 over a 30-day window, the ingester has caught up to their schedule and we should expect more visibility into their land-use deliberations.
• Atlanta civic-record gap closure. Atlanta's 37 records is anomalously low for a metro of its size. If the ingester is updated to pull from the Atlanta Mayor's Office in addition to the City Council site, that number should jump 10-20×.

Limitations

The civic-record dataset is from Granicus, which serves a specific subset of US municipal governments and not others. Coverage is uneven: SF, Boston, Nashville, and Phoenix are well-covered; Houston, NYC, and Atlanta are partially covered with known gaps. The 81% concentration in the top three is partly a coverage artifact, not a pure governance-activity ranking. A reader should not interpret "low record volume" as "low governance activity" — it might be either.

The leading-indicator framing — council records 6-18 months before enforceable rules — is a heuristic from prior land-use research, not a calibrated forecast. We don't have a quantified model that says "X% of zoning-relevant records turn into ordinances within Y months at confidence Z." The mechanism is real; the timing distribution is fuzzy.

Finally, council records are a bag-of-text dataset. The 567 Nashville records include parking variances, fence permits, liquor license renewals, and budget appropriations alongside the upzoning content that a developer cares about. Filtering by zoning-relevant keywords narrows the signal but introduces its own errors (synonyms, abbreviations, jurisdiction-specific vocabulary). A future version of this analysis will publish the keyword-filtered subset by metro.

Data current as of 2026-04-28. Source: Axiom Locus civic_records table, source = 'granicus', 30-day rolling window across 22 tracked metros. axiomlocus.io/blog