What 30,000 jurisdictions look like from the inside

In Braintree, Massachusetts, the document that decided a housing project was a denominator: 1.65% by the town's math, 1.39% by the state's, against a 1.5% statutory threshold, with 244 acres of conservation land deciding which number the Appeals Court believed. In Cape Coral, Florida, the deciding document was a permit ledger showing 14 self-storage applications in 18 months, six months before the council enacted the moratorium that ledger predicted. In Spokane, it was a bus plan: a rapid-transit line expected in 2030 that became, on April 13, 2026, a 5-2 emergency prohibition on new drive-thrus along the city's major transit corridors. In Oregon's Lower Umatilla Basin, it was a 30-year-old state acknowledgment of aquifer contamination that matured into a federal class action and a $20.5 million settlement.

Same country. Same constitutional framework. Four completely different documents holding the outcome, and not one of them was the zoning code's use table.

This is the thing our research coverage of 30,000+ U.S. jurisdictions has taught us that no amount of theorizing would have: the variation between jurisdictions is not primarily a variation in rules. It is a variation in where the decision actually lives.

Why is the deciding document never the same one twice?

Because jurisdictions accumulate their politics in different filing cabinets. Every one of the 30,000 has a zoning ordinance, and the ordinance is the backbone; it defines what is possible before politics enters the room, which is why we ingest codes whole rather than in fragments. But the code is one source family among several that a jurisdiction generates: agendas and minutes, staff reports, permit records, court filings, and the public-record materials where opposition organizes. Which family carries the live risk is a local fact, and it moves.

A concrete example of how local that fact gets. In Braintree, the zoning board's hearing was close to irrelevant; the fight was arithmetic inside a state regulation, resolved three appellate levels above the town. In Cape Coral, the code said yes the entire time, and the risk lived in application-volume data that predicted the code would change before the project could file. In Meridian, Idaho, an In-N-Out application's record filled with what the file describes as more than 300 written submissions, and reading that opposition file was worth more than reading the use table ever was. A team that brought the same research checklist to all three would have been perfectly prepared for a fight that happened somewhere else.

The inside view, then, is not a map of 30,000 dots. It is a texture of unevenness. Some jurisdictions are code-decided, and the cross-references settle everything. Some are data-decided, where a permit-velocity trend or a tax-revenue study tips a council. Some are record-decided, where the volume and organization of written opposition is the whole forecast. And a meaningful number are decided by documents that are not local at all: a state statute's threshold, a federal court's docket, a utility's interconnection queue, a statehouse incentive deal.

The label on the folder matters less than knowing which folder to open.

What does unevenness cost when you ignore it?

Real money, and the receipts are public. Data Center Watch counts $64 billion in U.S. data-center projects blocked or delayed since 2023, with $98 billion delayed in a single quarter of 2025. Those numbers are usually quoted as evidence that opposition is rising, which is true, but the inside reading is sharper: they are evidence that screening built for the average jurisdiction fails in the specific one. A diligence process that reads every county the same way is implicitly betting that the deciding document sits in the same place everywhere. Across a portfolio, that bet loses exactly as often as jurisdictions differ, which is to say constantly.

Unevenness also runs in both directions at once, which is what makes averages so useless. In April 2025, Carlsbad, California voted 3-2 to end a 27-year drive-thru ban while Cape Coral was converting a self-storage moratorium into permanent separation rules; a year later Spokane closed its transit corridors to the same vehicle-first formats Carlsbad had just conditionally reopened. Same country, same twelve months, opposite doors swinging. A single national posture on QSR entitlement risk in that window would have been wrong somewhere every day of it.

The uncomfortable corollary is that coverage claims, ours included, mean nothing without an honesty policy about depth. A universe of 30,000+ jurisdictions is not uniformly documented; some maintain immaculate digital records, others scan paper minutes months late, and the coverage behind any single read is only as strong as that jurisdiction's actual public record. This is why the platform is built to hold a brief rather than ship one when the record under it is too thin to defend. Unevenness in the world has to show up as unevenness in confidence, or the research is lying to you somewhere.

We would rather tell you the folder is thin than pretend we read a thick one.

How do you actually work a jurisdiction from the inside?

Ask three questions in order, before any site-level question. What kind of document has decided contested projects here before: code interpretation, quantitative study, opposition record, court order? Second, is the live risk even local, or does it sit at the state or federal layer, the way Braintree's denominator did, and the way an expiring federal tax credit repriced the BlueOval battery plants in Kentucky and Tennessee? Third, how fresh and complete is this jurisdiction's record, because the answer bounds how confident anyone, human or platform, is entitled to be about the first two.

That ordering sounds obvious written down. Almost nobody does it, because it requires holding the whole record of a jurisdiction rather than querying it for keywords, and because the professionals who can do it by hand cost enough that they get deployed after site selection, not before. The Braintree sponsor needed a regulatory-arithmetic read before filing. The Cape Coral developer needed a permit-velocity read before committing six figures of pre-development. Neither needed a better use-table summary, which is the product most screening tools actually sell, and both times the failure mode was identical: money moved before the record was read. Doing it before, across every jurisdiction a portfolio touches, at the depth each record actually supports, is the entire reason this platform exists.

My bet on where this goes: within three years, jurisdiction-level unevenness becomes an explicitly priced input in institutional underwriting, the way submarket rent comps became one a generation ago, and screening decks that treat entitlement risk as a single national adjustment will read as dated as a pro forma without a vacancy assumption. If 2029 arrives and portfolio committees are still applying one entitlement haircut across 40 markets, I was early or I was wrong.

There are 30,000 of these systems. You are not going to read them. Somebody, or something, has to, one whole record at a time, and the first question to ask any research tool is whether it knows which document decides in the jurisdiction you are about to spend money in.

This analysis is a source-cited research summary drawn from public records, not legal advice. It can contain errors and should be verified independently before any investment decision.