Show Notes
Designing for the Unknown Tenant
Spec buildings and flexible workspaces are built before the eventual tenant’s technology requirements are known. That creates a difficult design problem: owners and operators must make foundational decisions about power, risers, fiber, cabling, metering, shared networks, and access systems without knowing what equipment will arrive later.
This episode examines how small assumptions made early in design can become outages, delayed move-ins, expensive retrofits, and tenant concessions after a space is occupied. The central question is simple: What breaks if this goes down, and who takes the risk when tenants show up with surprises?
The conversation focuses on practical ways to preserve flexibility without treating overbuilding as the only answer. The goal is to make informed trade-offs, establish capacity margins, document infrastructure clearly, and build repeatable onboarding workflows before a lease begins.
Why Spec-Space Infrastructure Becomes Brittle
Infrastructure often fails not because the building’s main systems are inadequate, but because the paths between shared systems and tenant spaces were designed around assumptions that no longer hold.
A representative scenario involves a growing tenant moving into a spec suite with racks and power-hungry equipment. The building’s main power remains healthy, yet a backup feeder trips because a riser circuit was never expected to carry that level of demand. The resulting connectivity loss forces facilities teams into a reactive response at the exact moment a tenant move-in should be a success.
Several recurring assumptions create this kind of brittleness:
- Using average office power-density estimates, such as two to four watts per square foot, for spaces that may later contain data closets, server equipment, or lab loads.
- Sizing risers only for the base-building load with minimal spare breakers.
- Building a single shared backbone with too few spare fiber strands.
- Assuming tenants will bring fully independent managed services and will not need building-provided network services, public IPs, redundant fiber, or dedicated meter feeds.
- Centralizing ownership of shared systems without clear tenant demarcation points.
Each individual assumption may appear reasonable during construction. Together, they can turn a routine tenant installation into an outage, a stop-work order, or a disruptive retrofit.
Choosing Between Lean Design and Future Capacity
Owners must balance upfront capital expense, construction duration, and rentable square footage against the financial and operational consequences of reactive upgrades. The episode recommends starting with a risk matrix rather than treating extra capacity as either an automatic requirement or unnecessary waste.
That matrix should compare:
- The cost of added power, conduit, fiber, equipment space, and construction time.
- Potential loss of rentable area.
- The likelihood and impact of tenant-specific requirements.
- The cost of tenant downtime, expedited materials, hot work, finished-space disruption, and lease delays.
- The risk of concessions or reputational damage when infrastructure prevents a tenant from operating as planned.
A practical decision rule offered in the episode is to bias toward additional capacity or modular designs when a retrofit could prevent lease commencement or create more than two weeks of downtime. This is not a call to overbuild everything. It is a way to identify where flexibility has a much lower long-term cost than a future emergency.
Practical Capacity Thresholds
Specific thresholds give project teams a starting point for discussions that otherwise remain vague. These figures should scale with the building, tenant mix, and anticipated use, but they offer useful baseline margins for spec and flexible spaces:
- Design for at least 25% to 30% spare capacity at riser panels, tenant distribution panels, and in spec suites.
- Plan one additional empty four-inch pathway per major riser.
- Maintain approximately 30% to 50% spare capacity in fiber innerduct or raceway count.
- Provide a minimum of six fiber strands per riser.
- Use two fully redundant fiber paths where possible.
Technology-focused, laboratory, and high-density tenants may require larger margins. The important point is that capacity should be intentional, visible, and expandable rather than left to assumption.
Make Capacity Usable Through Operations
Spare conduits and spare fiber do not create flexibility on their own. They only help when teams know what is available, whether it works, and who is responsible for using it safely.
The episode identifies three operational disciplines:
- Standardized labeling and as-builts: Require a single turnover package containing electrical single-line drawings, conduit maps, fiber strand counts, fiber test results, and access-control schematics.
- Acceptance testing: Energize and load feeders at 80% of expected tenant density. Perform OTDR or loss testing on fiber to confirm that spare strands are genuinely viable.
- Tenant onboarding playbooks: Define who pulls permits, isolates feeds, coordinates security credentials, manages vendor access, and confirms readiness before move-in.
These practices transform infrastructure changes from frantic troubleshooting into managed operational work.
Metering, Billing, and Tenant Visibility
Tenant-level metering is presented as the safer approach when varied loads are likely. It creates transparency and reduces billing disputes. Where centralized metering is used, the infrastructure should still support later segregation and submeter installation without major demolition.
The broader principle is to plan for tenant visibility, even if every tenant will not initially need it. That preserves options as equipment loads, business models, and lease requirements evolve.
Examples That Show the Difference
One mixed-use building maintained a 30% spare breaker margin and empty innerduct in every riser. When a tenant needed redundant fiber and a dedicated utility feed for lab equipment, the team installed redundant fiber and a tenant breaker bank in three days with no downtime. The tenant’s move-in stayed on schedule.
At another property, riser space was reduced to lower cost. A tenant later needed to add a small server room but had no practical path for additional conduit without opening finished ceilings. The workaround created weeks of downtime, expedited purchasing fees, and tenant concessions.
The contrast illustrates how modest early planning can prevent costly operational consequences later.
Three Actions for the Next Project
- Build a risk matrix and establish objective power, conduit, and fiber thresholds.
- Make standardized labeling, as-built documentation, and test results conditions of turnover.
- Create a tenant onboarding playbook, then test it with a simulated tenant move before leases begin.
For owners, general contractors, IT leaders, and facilities teams, future-proofing is not simply about adding more infrastructure. It is about making deliberate decisions now so tenant variability does not become a production crisis later.
Future-Proofing Shared Infrastructure When the Tenant Is Unknown
Spec buildings and flexible workspaces are designed under a fundamental uncertainty: the people who will eventually occupy the space have not yet revealed what their technology environment will require.
A future tenant may arrive with ordinary office needs. Or they may bring dense rack equipment, a server room, lab systems, dedicated utility requirements, redundant connectivity expectations, public IP needs, or a security and access-control workflow that does not align with the original assumptions.
That uncertainty makes shared infrastructure a strategic decision, not a construction detail. Power, riser capacity, conduit pathways, fiber, metering, network demarcation, and access frameworks must be designed well before a lease exposes whether the building can support the tenant’s actual operating model.
The key question for owners, operators, general contractors, facilities leaders, and IT teams is not simply whether a system works at turnover. It is: What breaks if this goes down, and what happens when a tenant’s real requirements exceed the assumptions made during design?
How Small Assumptions Become Expensive Problems
Most infrastructure failures in flexible and spec environments do not begin with a dramatic equipment failure. They begin with a reasonable-looking assumption that later proves too narrow.
Consider a tenant that occupies a spec suite, installs racks and power-hungry equipment, and trips a backup feeder within the first week. The building’s main power is still fine. The problem is that the riser circuit was not intended to carry the tenant’s actual load. Connectivity is lost, facilities teams scramble, and a planned move-in success becomes an unexpected operational expense.
In this type of event, the root cause often traces back to decisions made long before the tenant appeared. Common examples include:
- Using two to four watts per square foot as the assumed power density because it fits conventional office cubicles, even though the space could later support a data closet or lab equipment.
- Sizing risers for the base-building load while leaving minimal spare breaker capacity.
- Installing a single backbone with only a small number of spare fiber strands.
- Assuming tenants will bring their own managed services and will not need building-provided subnetting, DHCP scopes, redundant fiber, public IPs, or dedicated meter feeds.
- Creating shared networks or metering systems with no clear tenant demarcation, making upgrades disruptive for everyone involved.
These decisions may reduce cost or simplify construction in the short term. But they can convert a tenant’s ordinary request into hot work, ceiling demolition, an outage, a stop-work order, or a delayed lease commencement.
Use a Risk Matrix Instead of Guessing
Future-proofing does not mean indiscriminately overbuilding every component. There are legitimate trade-offs. More capacity can require more capital, consume more space, and extend construction windows. Lean designs can preserve rentable square footage and reduce initial cost.
The right approach is to quantify the decision with a risk matrix.
Start by measuring the cost of capacity added during construction against the potential cost of capacity added after a tenant occupies the space. The analysis should include capital cost, lost rentable square footage, and construction time on one side. On the other, it should include tenant downtime, expedited materials, disruptions to occupied areas, potential concessions, and the risk that a retrofit delays lease commencement.
A useful operating rule is to favor more capacity or modular expansion paths when a retrofit could stop lease commencement or result in more than two weeks of downtime. That threshold gives teams a practical basis for deciding when a lower upfront cost creates an unacceptable downstream risk.
The risk matrix also helps owners avoid a false choice between “build for everything” and “build only for today.” The better decision is often to create a modular environment that can expand cleanly as tenant requirements become known.
Set Objective Capacity Margins
Vague requirements such as “leave room for growth” are hard to enforce and easy to lose during value engineering. Objective thresholds make the intended flexibility visible to designers, contractors, operations teams, and future tenants.
For spec and flexible environments, the episode identifies several practical starting points:
- Maintain at least 25% to 30% spare capacity at riser panels, tenant distribution panels, and within spec suites.
- Include one additional empty four-inch pathway for each major riser.
- Reserve roughly 30% to 50% spare capacity in fiber innerduct or raceway count.
- Provide at least six fiber strands per riser.
- Use two fully redundant fiber paths where possible.
These are starting thresholds rather than universal rules. The appropriate capacity margin should reflect building size and expected tenant mix. A space likely to serve labs or technology-intensive tenants requires higher margins than a traditional office environment. The important discipline is to define the margin early and design the expansion path before finished space makes future work difficult.
Capacity Is Not Valuable Unless It Is Documented and Tested
Spare breakers, empty pathways, and unused fiber strands can appear on drawings without being operationally useful. If teams cannot identify the spare capacity, confirm its condition, or access it safely, the building still faces avoidable risk when a tenant changes the plan.
Documentation must be treated as an operational asset. A standardized as-built package should include:
- Single-line electrical drawings.
- Conduit maps.
- Fiber strand counts.
- Fiber test results.
- Access-control schematics.
Uniform labeling should connect the documentation to physical reality. Teams should be able to walk into a riser room, identify pathways and feeds, understand the available capacity, and see how those resources connect to tenant spaces.
Acceptance testing is equally important. Feeders should be energized and loaded at 80% of expected tenant density. Fiber should undergo OTDR or loss testing so the project team knows that spare strands are viable rather than merely listed on paper. These checks catch issues before a tenant’s deadline turns them into an emergency.
Tenant Onboarding Is Part of the Infrastructure Design
Future-proofing shared infrastructure is not complete at construction turnover. The environment also needs a repeatable process for safely connecting a tenant’s real systems to the building.
A tenant onboarding playbook should assign responsibilities for permits, feed isolation, security credentials, vendor coordination, installation scheduling, acceptance tests, and move-in readiness. Without this playbook, even a well-provisioned building can become chaotic when multiple parties arrive with overlapping scopes and unclear ownership.
Clear roles matter because a tenant installation touches several teams at once. Facilities may control electrical feeds. Security teams may control access credentials. Network or telecom teams may manage riser access and carrier pathways. Contractors may need permits, escorts, or approved work windows. The tenant may have a separate IT provider with its own equipment and timelines.
A documented playbook makes those dependencies predictable. It reduces the chance that a tenant discovers an access, power, or pathway constraint only after vendors are already on site.
The playbook should be tested before leases begin through a simulated tenant move. A rehearsal exposes unclear responsibilities, missing documentation, and broken handoffs while the cost of correction is still low.
Metering Should Support Transparency and Change
Metering often becomes a source of disagreement when tenants have materially different loads. Tenant-level metering provides better visibility and helps avoid billing disputes. It is the safer route when varied loads are expected.
Where centralized metering is selected, owners should still preserve the ability to separate loads and add submeters later without substantial demolition. Even if tenant-level visibility is not initially required, designing for it keeps future operating choices open.
This is consistent with the broader objective of flexible infrastructure: avoid making future change depend on disruptive construction in occupied spaces.
Two Outcomes, One Difference: Early Planning
In one mixed-use building, a 30% spare breaker margin and empty innerduct in every riser created a straightforward path for a tenant that later required redundant fiber and a dedicated utility feed for lab equipment. The team installed redundant fiber and a tenant breaker bank in three days, with no downtime. The move-in remained on schedule.
In another case, a property reduced riser space to save money. When a tenant needed a small server room, there was no feasible route for additional conduit without cutting finished ceilings. The workaround resulted in multiple weeks of downtime, expedited purchasing fees, and tenant concessions.
The lesson is not that every building must be built to maximum capacity. It is that modest, intentional margins can prevent small unknowns from becoming expensive operational failures.
Build for Change Before Change Arrives
On the next spec or flexible-space project, begin with three actions: create a risk matrix with measurable capacity thresholds, require standardized as-builts and test results at turnover, and establish a tenant onboarding playbook that is tested before lease commencement.
These steps move infrastructure decisions beyond initial installation and toward long-term operational resilience. They help owners protect lease timelines, give facilities and IT teams clearer control, and make it easier for tenants to enter a space without forcing costly changes to systems that were supposed to support them.
For a deeper discussion of the thresholds, testing practices, and operational workflows behind this approach, listen to this episode of Built, Wired & Secured.