Skip to main content
SpanVor

SpanVor Industrial Data Atlas / New supply

What industrial space is actually in the pipeline?

A measured view of industrial and small-bay projects from reviewed public records. The page distinguishes metro totals from authority-level subsets, keeps existing inventory separate, and leaves unavailable measures unavailable.

Public market profiles
60Not every market has a complete measured total
Market-specific pipeline cohorts
10Published individually; cross-market ranking withheld
Small-bay projects · reviewed top 10
1,296Active pipeline classification; not all 60 markets
Additional reviewed identities
5,234Across 9 broader universes; not an active-pipeline total

Cross-market ranking is withheld while SpanVor completes a uniform lifecycle audit. The page previously ranked mixed market-contract projects beside broader reviewed identities. That was not a valid like-for-like comparison. The tables now keep market-specific pipeline cohorts and broader project histories separate, publish them alphabetically, and do not add either collection into a national pipeline headline. Another 37 markets publish bounded authority evidence, and 1 market remains candidate-only.

Market-specific pipeline evidence

Useful market counts, without a false national leaderboard.

These cohorts were classified as current or planned under their individual market contracts. Differences in status vocabulary, source windows, and recent-delivery visibility mean they are not yet certified for cross-market ranking.

MarketCoverageIdentity scopeProjectsSmall-bayPublished building SFComparison statusAs of
AtlantaMeasured authority subsetActive pipeline300871,497,382 SFRecovered-project subsetMarket-specific lifecycle contract; not certified for cross-market ranking2026-08-21
Austin / Central Texas I-35Measured authority subsetActive pipeline248153Not publishedMarket-specific lifecycle contract; not certified for cross-market ranking2026-08-21
Baltimore–Columbia–TowsonMeasured authority subsetActive pipeline116Not publishedNot publishedMarket-specific lifecycle contract; not certified for cross-market ranking2026-08-22
Dallas-Fort WorthMeasured authority subsetActive pipeline73844325,913,916 SFRecovered-project subsetMarket-specific lifecycle contract; not certified for cross-market ranking2026-08-20
HoustonMeasured authority subsetActive pipeline382269Not publishedMarket-specific lifecycle contract; not certified for cross-market ranking2026-08-27
Los AngelesMeasured authority subsetActive pipeline45Not publishedNot publishedMarket-specific lifecycle contract; not certified for cross-market ranking2026-08-21
OrlandoMeasured authority subsetActive pipeline2761644,001,826 SFRecovered-project subsetMarket-specific lifecycle contract; not certified for cross-market ranking2026-08-21
PhoenixMeasured authority subsetActive pipeline359180Not publishedMarket-specific lifecycle contract; not certified for cross-market ranking2026-08-21
South Florida / MiamiMeasured authority subsetActive pipeline68Not publishedNot publishedMarket-specific lifecycle contract; not certified for cross-market ranking2026-08-21
Tampa BayMeasured authority subsetActive pipeline51Not publishedNot publishedMarket-specific lifecycle contract; not certified for cross-market ranking2026-08-21

Broader reviewed universes

Useful evidence, without calling all of it future supply.

These counts remain valuable for coverage and project-history analysis. They are intentionally unranked because the source windows include different mixtures of historical, recent, inactive, and lifecycle-unknown records.

MarketCoverageReviewed identitiesCurrent evidencePublished building SFAs of
Baltimore–Columbia–TowsonMeasured authority subset1,879116 planned or under-development projects; also shown in the active table34,551,712 SFMeasured cohort2026-08-22
Cape Coral–Fort MyersMeasured authority subset1,472Lifecycle partition unavailable; not ranked as active pipeline9,860,884 SFMeasured cohort2026-08-22
Charlotte–Concord–GastoniaMeasured authority subset267Lifecycle partition unavailable; not ranked as active pipeline7,270,828 SFMeasured cohort2026-08-22
JacksonvilleMeasured authority subset137Lifecycle partition unavailable; not ranked as active pipelineNot published2026-08-22
Lakeland–Winter HavenMeasured authority subset597Lifecycle partition unavailable; not ranked as active pipeline12,759,446 SFMeasured cohort2026-08-22
Minneapolis–St. Paul–BloomingtonMeasured authority subset32759 projects in the 2025 permit year; construction status is not published17,387,004 SFMeasured cohort2026-08-24
Nashville–Davidson–Murfreesboro–FranklinMeasured authority subset282Lifecycle partition unavailable; not ranked as active pipeline4,711,267 SFMeasured cohort2026-08-22
San AntonioMeasured authority subset230Recent permit and planning evidence; source does not publish construction or completion status495,685 SFMeasured cohort2026-09-02
SavannahMeasured authority subset43Lifecycle partition unavailable; not ranked as active pipelineNot published2026-08-22

Every visible market received a second plausibility pass: Phoenix now shows 359 projects after 16 delivered-status records were removed from active supply. Atlanta shows 300 after eight sign, demolition, and no-new-construction records were removed. Orlando shows 276 after eight completed or finaled projects were moved out of active supply. Austin / Central Texas shows 248 after 12 clear retail, restaurant, school, amenity, utility, and supporting-work records were removed. In each case, only rows proven to be net-new versus the preserved earlier review were subtracted.

DFW publishes a 738-project active minimum while a later 136-project net increment is adjudicated. Houston publishes a measured minimum of 382 explicitly current City ILMS projects, with 1,329 older mixed-lifecycle records held outside active supply. Los Angeles, Miami, and Tampa retain measured minimums while later recovery identities are reworked. San Antonio retains a reviewed permit/planning universe but no active total because its principal City source has no construction or completion status. Baltimore contains 1,879 reviewed identities, but only 116 are classified as planned or under development. Cape Coral–Fort Myers and Minneapolis remain reviewed-universe or recent-permit evidence, not active-pipeline totals.

How to read the pipeline

A project count is not a square-foot forecast.

A 10,000-square-foot flex building and a million-square-foot distribution center are both one project. Use the count to understand activity, then use known area, lifecycle, geography, and product type to understand competitive supply.

01

Reviewed project

A physical industrial or small-bay development identity reconciled from one or more connected public records. Repeated filings should not become repeated projects.

02

Active pipeline

Projects classified as under development or planned under the applicable market contract. Recently completed and terminal records stay separate.

03

Known building area

Only source-stated building area is counted. A project without published square footage remains in the project count and outside the square-foot total.

Download and cite

Use the release, not a screenshot of a changing page.

Every archive carries its release date and coverage label. That makes a comparison reproducible even after SpanVor publishes a newer pipeline view.

Market-level reviewed aggregate.
No exact project address, party, permit-history, or source-document intelligence is included.

Download CSVDownload JSONDownload chart

SpanVor. “U.S. Industrial Development Pipeline.” SpanVor Industrial Data Atlas, data through 2026-09-02; lifecycle presentation corrected 2026-09-02. https://spanvor.com/industrial-development-pipeline