Small-bay industrial is not a smaller version of a distribution warehouse. It is a shared operating system: multiple suites, local businesses, parking patterns, loading paths, power requirements, yards, permitted uses, and neighbors all interacting on one site. If you underwrite only the building total, you are describing the container—not the investment inside it.
The spreadsheet sees a 75,000-square-foot industrial building.
The operator might see thirty suites, thirty front doors, thirty parking patterns, thirty power questions, and thirty businesses sharing one piece of real estate.
That is not a difference in scale. It is a difference in kind.
What does “not miniature big-box” actually mean?
It means the familiar industrial metrics still matter, but they stop too early. Roof, structure, drainage, fire protection, clear height, and access remain important. The mistake is treating those building-wide facts as a complete description of a small-bay property.
A bulk warehouse is often understood through a short list of broad specifications and one or a few major leases. An apartment community is built around repeatable residential units. An office building is commonly discussed through finish, density, amenities, and common areas.
Small-bay borrows a little from each, but behaves like none of them.
Its tenants may include plumbing and electrical contractors, cabinet makers, auto specialists, light manufacturers, wholesalers, custom fabricators, gyms, gymnastics programs, churches, professional services, and many other local businesses. They can all occupy industrial space. They do not use the property the same way.
The correct unit of analysis is therefore not just the building. It is the building, suite, tenant activity, site, permission, and local market together.
Why do building averages hide the important differences?
Because the suite is the actual unit of usefulness. A building can have impressive electrical service while the available bay has a small panel. It can have twenty loading doors while the suite being leased has no door a truck can reach. It can report a strong clear height while ductwork, lights, sprinklers, or a mezzanine control the usable height inside one bay.
The same problem appears in the rent roll. Two suites with the same area and rent can have very different functional value:
- One has a drive-in door, practical frontage, and three-phase power.
- One has substantial office finish and no useful loading.
- One has the best visibility but shares its parking with a customer-intensive use.
- One can combine with the neighboring bay; another cannot divide without relocating its only restroom and electrical panel.
Averages become dangerous when the units are not interchangeable.
The better questions are straightforward: Which suites have the capability? Which tenants need it? What has actually been verified? What would the next likely tenant have to change before opening?
Why is the tenant mix physical, not merely financial?
The rent roll is also an operating map. Rent, term, escalations, deposits, and rollover dates describe the lease. They do not explain how the property functions at 7:00 a.m., 4:30 p.m., or Sunday morning.
A plumbing contractor may dispatch a fleet before sunrise. A gymnastics facility may fill the lot after school. A custom-car shop may need ventilation, power, and outdoor staging. A cabinet maker may receive bulky deliveries. A church may create a weekend parking peak that is invisible during the typical Tuesday tour.
Those businesses can all be good tenants. They are simply not operationally interchangeable.
For each occupant, I want to know:
- What does the business receive, store, build, repair, sell, or send back out?
- When do employees, customers, fleets, and deliveries arrive?
- Which parking spaces, doors, and yard areas does the business depend on?
- Do noise, odor, dust, waste, or outdoor activity affect neighboring tenants?
- Does the observed activity match the lease, permitted use, and life-safety requirements?
That is not about excluding interesting users. A varied tenant base is one of small-bay’s great strengths. The point is to understand the activity well enough to manage the mix intentionally.
Why can the same parking ratio produce two different properties?
Because a parking ratio counts spaces, not competition for them. Striping does not tell you whether work vans remain overnight, trailers occupy the corners, customers arrive in waves, or delivery trucks borrow the fire lane.
Parking should be understood by user and time.
The same is true of yards. Open ground is not automatically a functional yard. Useful yard space needs the right surface, access, gates, drainage, security, and legal permission. It also has to work without trapping another tenant’s truck or consuming the circulation the park depends on.
Local access deserves the same attention. Being near an interstate does not tell a plumber whether a truck can turn into the property, a customer whether the address is visible, or a delivery driver whether a median creates a long detour.
Small-bay tenants experience the local road network every day:
- Curb cuts and turning movements
- Medians, grades, and rail crossings
- School, retail, and neighborhood traffic
- Gate stacking and internal circulation
- The complete path from entrance to loading door and back out
These details look small on a regional map. They are not small to the businesses paying the rent.
Why do power and permission belong at the bay level?
Capability is rarely distributed evenly. The property may have gas, but not at the bay that needs it. A roof plan may show HVAC units without clearly identifying which suite each unit serves or who maintains it. Electrical panels, meters, exhaust, plumbing, mezzanines, and office buildouts often accumulate one tenant improvement at a time.
That history can create useful capability, hidden cost, or both.
Permission works the same way. A business operating today is evidence of activity, not proof that every part of the activity is approved. Zoning labels rarely settle the full question. Certificates of occupancy, permits, fire requirements, outdoor-storage rules, private restrictions, and lease provisions may all matter.
I prefer three plain evidence labels:
- Confirmed: supported by the appropriate document or professional review.
- Observed: visible at the property but not yet documented.
- Unverified: reported, inferred, or still unanswered.
The goal is not to turn a property tour into a laboratory. It is to keep a visible observation from quietly becoming an assumed fact.
What is the right small-bay underwriting hierarchy?
The most useful framework has six layers:
| Layer | What it should explain | |---|---| | Building | Structure, roof, fire protection, utilities, drainage, and shared systems | | Suite | Size, office, loading, clear height, power, plumbing, frontage, and flexibility | | Tenant activity | What each business actually does and when people, vehicles, and deliveries arrive | | Site | Parking, truck paths, loading conflicts, yard utility, security, and circulation | | Permission | Lease rights, zoning, permits, occupancy, life safety, and outdoor-storage rules | | Local market | The businesses the property can serve and the roads they use every day |
This is not a request for a more complicated model. It is a request for a model that matches the asset.
Use building totals to understand the shell. Use suite, tenant, site, permission, and local-market facts to understand the investment.
Frequently asked questions
Is small-bay industrial simply a size category?
No. Size is a useful filter, but the defining characteristic is how smaller suites, multiple local businesses, and shared site systems operate together. Two buildings with the same total square footage can support very different tenant pools and management models.
Which big-box metrics still matter in small-bay?
Roof, structure, fire protection, drainage, clear height, loading, and access all matter. They should be verified at both the building and suite level rather than assumed to apply equally across every bay.
What is the biggest underwriting mistake?
Treating building-wide capability as suite-level capability. The available suite—not the brochure total—is what the next tenant can actually use.
Does this framework replace formal diligence?
No. It organizes the questions that lease review, plans, zoning analysis, property-condition work, engineering, and site visits must answer.
Key takeaways
- Small-bay is a shared operating system, not a miniature warehouse.
- The suite is the practical unit of usefulness.
- Tenant mix changes parking, loading, power, management, and neighbor conflicts.
- Site utility depends on how shared systems work at real peak periods.
- Observed activity and verified permission should never be treated as the same fact.
- The right hierarchy is building, suite, tenant activity, site, permission, and local market.
Download the complete six-page guide: Small-Bay Is Not Miniature Big-Box Industrial.
For the broader investment thesis, read the Small-Bay Industrial Investor Primer. For a practical companion, use the Small-Bay Asset Passport to record what is known, observed, and still unanswered.
SpanVor is connecting the property, building, site, use, and occupancy details that make industrial assets easier to find and understand. You can explore your own market with 14 days of All-Access, no credit card required.
One last thing, since you read this far: the code SpanvorBlog takes 25% off a SpanVor Pro subscription—where the parcel-level data behind posts like this one actually lives.
Written by Jason Probert, Founder of SpanVor.