Spec building vs. build-to-suit: reading the site plan from orbit

A permit filing tells you a shed got approved. It doesn't tell you whether the developer is building on faith or building for a signed tenant. For that, you have to read the site itself, and the site tells you plenty before any lease ever hits a filing.

Why the distinction matters before you ever see a lease

Spec buildings and build-to-suit warehouses absorb regional capacity differently. A developer pouring a 600,000 square foot spec shed on open land is betting on demand that hasn't shown up yet. A build-to-suit on the same acreage means demand already arrived, signed, and specified its own dock count. If you're sizing absorption or forecasting vacancy for a submarket, lumping the two together will throw off your numbers every time. One is supply chasing a tenant. The other is supply built around one.

The trouble is that county permit data rarely flags which is which, and news releases lag construction by months. By the time a trade publication names the tenant, the roof's already on and the yard's already paved.

The tells that show up in the site plan, not the press release

Start with the footprint itself. Spec shells run to a standard rectangle, 200 to 250 feet deep, built to a generic bay spacing that fits most logistics tenants without retrofitting. Build-to-suit footprints get stretched, notched, or cross-docked to match one specific operation: a produce distributor's refrigerated bay sticking off one end, a parcel sorter's unusually narrow depth, an auto parts cross-dock with trailer doors on both long walls instead of one.

Look at the yard next. A spec building gets a minimal truck court and parking lot poured to code minimums, because the developer isn't guessing at a specific tenant's trailer count. A build-to-suit site often shows an oversized trailer storage field, extra parking stalls well beyond what the building's square footage would normally need, or a rail spur graded in before the structure is even topped out. That kind of early, expensive site work only happens when someone's already paying for it.

Clustering matters too. Spec development shows up as two or three near-identical shells rising together inside one park, started on roughly the same timeline, because the developer is hedging across unit sizes rather than building one answer to one tenant. A build-to-suit is almost always a single building on its own parcel, sized and graded for exactly one occupant, with none of the sibling shells a spec developer would add to cover different tenant appetites.

Construction sequencing is the last tell, and it's the one analysts miss most. Spec shells go vertical first and finish the yard later, sometimes leaving trailer parking gravel or unstriped for a year while the developer waits on a tenant to specify dock equipment. Build-to-suit sites tend to finish site work and shell at the same pace, because the tenant's fit-out crew is already queued behind the general contractor.

None of these signals is proof by itself. A produce distributor's refrigerated bay could, in theory, get built on spec by a developer chasing that exact tenant type. But stack three or four of these signals, footprint shape, yard oversizing, cluster pattern, and sequencing, and you get a read that's right far more often than a single filing search. This is the same pattern-matching that a quarterly change layer tracking new sheds and yard extensions across a region is built to make routine, instead of something an analyst reconstructs shed by shed from scratch each quarter.

Spec buildings and build-to-suit warehouses both add square footage to a region's logistics stock, but they say very different things about where demand already landed versus where a developer is still guessing. Reading the yard, not just the roofline, is what separates the two.

See the next quarter's new sheds before the filings catch up.