GDS Technology — Built, Wired and Secured podcast banner
Watch on YouTube →
Built, Wired & Secured episode artwork: The Tenant Experience Gap: When Your Building's Technology Promises Outpace Its Operations
Episodes Built
Episode 189

The Tenant Experience Gap: When Your Building's Technology Promises Outpace Its Operations

November 22, 2026
Key takeaways
  • Audit network, access control, and HVAC with operations before marketing or committing to technology features.
  • Test systems before move-in with the tenant’s equipment and the teams responsible for delivery.
  • Verify every relevant Wi-Fi area, access-controlled door, climate zone, and conference-room AV setup.
  • Set realistic service expectations, and meet any response commitments you communicate.
  • Solicit tenant feedback and use operational data to identify patterns before they become persistent complaints.

Show Notes

The tenant experience gap starts with the promise

A building can be marketed as smart, seamless, and connected, yet fail tenants at the moment they arrive. The episode opens with a Monday morning emergency: a tenant CEO is in the lobby, a badge does not work, and Wi-Fi is unavailable. The immediate technical failure is only part of the problem. The larger issue is the gap between what was promised and what the building can deliver.

That first impression can shape how tenants view the entire property, not just one device or service. Leasing teams may emphasize technology to differentiate a building, while the people responsible for operating it are brought in only after a lease is signed—or after move-in.

Why operations and leasing become disconnected

  • Leasing focuses on closing a deal and communicating amenities.
  • Operations focuses on reliability, support, and systems that work every day.
  • Engineering and IT may inherit technologies they did not select or design.

Without early coordination, the sales promise can outrun the infrastructure and the team's ability to support it. The episode gives the example of “high-speed Wi-Fi throughout the building” when access points cover only common areas, or bandwidth is shared across a floor. Once tenants make video calls, performance may fall short of expectations. The tenant does not distinguish between who sold the feature and who built it; they experience one building.

Other examples include climate-control claims that sit on aging building automation systems, access cards that work at the main entrance but not every relevant door, and conference-room audiovisual equipment that is difficult to use or poorly understood by the support team.

Move-in day is a real-world systems test

A building may appear to run normally until a new tenant brings its own devices, work patterns, and expectations. Move-in exposes gaps that a visual walkthrough will not catch. A badge must be tested on every door the tenant needs. Wi-Fi should be checked throughout the suite, including conference rooms. Climate control needs to be verified in each zone, and audiovisual equipment should be operated rather than merely inspected.

The guests stress that testing should use the tenant's actual equipment where possible and involve the tenant's IT contact if one is available. Leasing, property management, engineering, and IT should coordinate the process. A quick visual handoff is not a substitute for a functional test.

Audit before making the promise

The first recommended step is a pre-lease system audit. Before marketing a technology feature or finalizing a commitment, involve operations and inspect the space. Test the network, access control, and HVAC, then address known issues before the lease is signed. This aligns the advertised experience with what the property can actually support and avoids preventable surprises after occupancy.

The conversation frames this as a cultural change: sales and operations need to act as partners rather than adversaries. Engineering should be included early enough to flag limitations, explain support requirements, and identify work that needs to happen before a tenant arrives.

Build an onboarding process that tests, not just tours

Once a lease is signed, a structured onboarding checklist can turn handover into a repeatable operational process. The checklist should include actual system tests—not just a walkthrough:

  • Connect to Wi-Fi in the suite, try printing, and make a video call.
  • Test access control on every door the tenant will use.
  • Check climate control in each zone.
  • Operate conference-room AV and confirm users can understand it.
  • Include leasing, property management, engineering, and the tenant's IT contact where available.

Testing with the tenant's equipment helps reveal compatibility and coverage problems before the tenant depends on the systems for work. The episode's example of a badge that opened the main entrance but not the stairwell door to a roof patio illustrates why every relevant access point matters.

Set clear service expectations and meet them

Service-level agreements can help tenants understand how issues will be handled. For example, the guests discuss setting a 48-hour response expectation for a non-critical issue. Clear expectations can reduce uncertainty, but only if the team meets the stated commitment. An SLA that is missed can undermine trust more than an undefined process.

Keep listening after move-in

Tenant experience needs attention beyond the handover. Buildings should actively solicit feedback through a quarterly survey, check-in call, or simple email instead of waiting for complaints. Feedback must lead to investigation and improvement; otherwise tenants may carry the unresolved problem through the lease.

Operational data can help identify patterns. The speakers mention tracking network uptime, ticket response times, and amenity usage. If a conference room is used heavily on Tuesdays, teams can ensure its AV system is checked and maintained before that demand. The goal is to turn recurring complaints and usage signals into system improvements.

Three practices to close the gap

  • Audit before you promise.
  • Test before you hand over.
  • Listen after you deliver.

The episode's central point is that technology delivery is also relationship management. Tenants want to feel the building is looking out for them. A reliable, coordinated experience can support renewals and recommendations, while proactive operations can prevent avoidable emergencies and team burnout. The best day in operations, as one guest puts it, is the one nobody notices.

Deeper dive

A smart-building promise is only as strong as move-in day

A tenant arrives expecting a connected, carefully managed workplace. At the lobby, the access badge fails. In the conference room, Wi-Fi is down. A building sold as “smart” suddenly feels anything but. This is the tenant experience gap: the distance between what a property promises and what its systems, support processes, and teams actually deliver.

The episode begins with a Monday morning call about a tenant CEO standing in the lobby with a nonworking badge and unavailable Wi-Fi. The moment is dramatic, but the underlying failure is familiar: the technology promise was made before anyone verified that the operation could support it.

How the gap forms

Leasing teams are tasked with filling space and differentiating a property. Technology amenities can help tell that story. But the engineers, IT staff, and property operations professionals who must make those amenities work may not join the conversation until after the lease is signed—or even after the tenant moves in.

That creates a timing problem and a difference in priorities. Leasing is focused on closing a deal. Operations is focused on reliability. Neither goal is inherently wrong, but without deliberate coordination, an appealing claim can become an unsupported commitment.

The episode describes buildings that advertise high-speed Wi-Fi throughout, even though access points are limited to common areas or bandwidth is shared across a floor. Ordinary use—such as several people joining video calls—can expose the mismatch. Similarly, a marketing claim about modern climate control may be layered over an aging building automation system. When the tenant reports a problem, the operations team is left to support infrastructure it may not have selected, designed, or been trained to troubleshoot.

For tenants, internal boundaries do not matter. They do not separate the leasing brochure from the network design or the property manager from the engineer. They experience one building, and the first failure can shape their impression of the whole property.

Move-in day reveals what a walkthrough misses

Systems that appear to be functioning can behave differently when a new tenant brings its own devices, users, and work habits. Move-in day is therefore not simply a key handoff. It is the moment when the building's promises meet real conditions.

A visual walkthrough can miss a badge that opens the main entrance but not the stairwell the tenant needs. It can overlook weak Wi-Fi in a specific conference room, an HVAC zone that does not respond as expected, or an AV system that nobody can confidently operate. The right question is not “Does the equipment appear to be there?” It is “Can the tenant use it for the work they need to do?”

Audit before you promise

The first practical step is to involve engineering and operations before a technology feature is marketed or committed. A pre-lease system audit gives the team a chance to walk the space, test the network, access control, and HVAC, and identify shortcomings while there is still time to address them.

This is not a call to avoid technology claims. It is a way to make accurate claims and connect them to a delivery plan. Sales and operations should operate as partners. Early involvement gives leasing a clearer picture of what is available and gives engineering a chance to explain limitations, support needs, and required improvements. As the episode notes, fixing a known issue before the lease is signed is less costly and less embarrassing than explaining it on move-in day.

Test with the tenant, not just for the tenant

After lease signing, a structured onboarding process should make the handover repeatable. It should include a full functional test and involve leasing, property management, engineering, and the tenant's IT contact if one is available. Most importantly, test with the tenant's actual equipment where possible, not only with internal test devices.

A practical checklist can include:

  • Connect to Wi-Fi throughout the suite, including work areas and conference rooms.
  • Try common tasks such as printing and making a video call.
  • Test every access-controlled door the tenant will need to use.
  • Verify climate control in each zone.
  • Operate conference-room AV and make sure users know how it works.

These checks surface real-world issues before people depend on the systems. They also create shared visibility: the tenant sees what was tested, and the building team knows what remains to be fixed.

Make service expectations explicit

Even a well-prepared building will encounter issues. Service-level agreements can clarify how quickly different problems will receive attention. The episode gives a 48-hour response for a non-critical issue as an example of a defined expectation. Clarity helps tenants know what to expect, but the commitment must be realistic and consistently met. A missed SLA can damage confidence more than a transparent, achievable timeframe.

Use feedback and operating data to improve

Onboarding is the beginning of the tenant relationship, not the end. The guests recommend asking for feedback through quarterly surveys, check-in calls, or straightforward email. Teams should not wait for a complaint to discover that a service is falling short. They must also respond to what they hear: a report of slow Wi-Fi should lead to investigation and, where necessary, improvement.

Operational measures can make patterns easier to see. Network uptime, ticket response times, and amenity usage are examples discussed in the episode. If data shows that a conference room is used heavily on Tuesdays, the team can test and maintain its AV system before that demand. This approach converts recurring issues and usage patterns into preventive action instead of repeated emergency repair.

Technology delivery is relationship delivery

Overpromising is a common mistake, but excluding the people responsible for delivery is another. A building's technology story should be supported by the people, systems, training, and processes behind it. When that alignment is in place, tenants are more likely to experience the reliability they were offered, and the operations team is less likely to live in a cycle of reactive repairs.

The three-part principle from the episode is simple: audit before you promise, test before you hand over, and listen after you deliver. It keeps expectations connected to reality and gives teams a practical way to protect tenant trust. For more on turning building technology into a dependable tenant experience, listen to the episode of Built, Wired & Secured.

Frequently Asked Questions

How can property teams test building technology before a tenant moves in?

Property teams should conduct a coordinated functional test before move-in, not just a visual walkthrough. Test Wi-Fi throughout the suite, try printing and video calls, check access on every door the tenant will use, verify each climate zone, and operate conference-room AV. Include engineering, property management, leasing, and the tenant’s IT contact when available.

Why does building Wi-Fi fail to meet tenant expectations?

Wi-Fi can fall short when a building promises broad, high-speed coverage but access points are limited to common areas or bandwidth is shared across a floor. Video calls and other everyday work can expose those design limits. The episode recommends auditing the network before making the promise and testing coverage with the tenant’s equipment.

What should a commercial building do after a tenant reports slow Wi-Fi?

The building team should investigate the report, improve the service where needed, and track whether the issue recurs. The episode recommends actively gathering feedback rather than waiting for complaints, then pairing it with measures such as network uptime and ticket response times. That turns tenant feedback into operational improvements instead of a repeated source of frustration.