The Setup
Denver's composite cell score averages 56.60 — mid-range for a tracked U.S. metro. Its safety and environment score averages 77.18, one of the higher figures in the tracked set. Those numbers suggest a city with regulatory capacity and relative civic stability.
Its development pipeline score averages 15.95.
That is the lowest average pipeline score of any metro in the dataset.
The Chain
120 cells cover the Denver metro. Their pipeline distribution:
- 53 cells score between 5 and 9 — single digits, near-total suppression of modeled development activity
- 26 cells score between 10 and 19
- 9 cells score between 20 and 32
- 32 cells score 33 — the default assigned when the permit feed returns no data
The floor is 5. The ceiling is 33. No cell exceeds the permit-default value.
Of the 88 cells with real scores (non-default), the average is 9.7. That is not a coverage gap masquerading as suppression — it is permit data arriving and producing consistently low pipeline signal. The model is reading something. Whatever it is reading, it is scoring it low.
The 32 default cells carry the highest composite scores in the metro (avg 59.31). The 53 lowest-scoring cells carry the lowest composite scores (avg 54.15). The cells where permit data is absent are the model's best-quality cells. The cells with real permit data are the ones scoring closest to the floor.
The Implication
In Chicago, a similar suppression pattern had a visible cause: ESGI scores above 10 corresponded to a development pipeline floor, and the relationship held across cells. High environmental-sensitivity index values tracked regulatory friction.
Denver's ESGI score is 0.00 across all 120 cells. Not low — absent.
The explanatory variable the model uses in other metros does not exist here. Whatever is driving pipeline scores to single digits in 53 Denver cells — permit bottlenecks, infrastructure constraints, zoning holds, land-cost crowding — is invisible to the scoring model. The number exists. The reason does not.
CRE investors using cell scores for Denver allocation will see a suppressed pipeline score and no accompanying attribute explaining the suppression. The score is useful for ranking cells. It is not useful for diagnosing them.
What to Watch
The 32 default cells are the most actionable gap. These cells carry the highest composite scores in the metro (59.31 avg) and empty permit feeds. If permit data arrives and scores low, Denver's suppression is genuine across its best cells. If it arrives and scores higher, the current 15.95 metro average is understating activity where the market is strongest.
ESGI zero is the structural issue. Until Denver's gentrification-sensitivity index is populated, pipeline score outputs have no explanatory variable attached. That limits the scores to directional signals — useful for rough ranking, not for cause attribution.
Limitations
Cell scores are computed at a point in time from available permit, civic, and economic inputs. Denver's low figures may partially reflect data ingestion lag rather than true market suppression. The ESGI = 0 condition may be a loader artifact rather than a deliberate gap. These should be treated as signals worth investigating, not confirmed market characteristics.
Data: 120 cell\_scores rows, metro\_slug = 'denver'. Locus production data as of 2026-07-31.