Show Notes
Who Owns the Riser?
Shared building infrastructure often becomes visible only after something fails. In a multi-tenant property, a riser panel, telecom closet, fiber path, power feed, or automation connection may sit between landlord-controlled space, tenant equipment, contractors, service providers, facilities teams, IT, and leasing. When nobody has clear responsibility, a routine change can turn into a disruptive outage.
This episode of Built, Wired & Secured examines how unclear ownership creates operational risk in commercial buildings and how property teams can establish practical governance before a production issue forces the conversation. The discussion focuses on shared stacks: the infrastructure that supports multiple parties but can fall into the gaps between contracts, handoffs, documentation systems, and vendor scopes.
The Failure Scenario: A Small Change With Broad Impact
Consider a contractor opening a riser panel during a tenant fit-out. Two floors lose phone service, building automation trips, and a point-of-sale system goes offline. The immediate technical issue matters, but the operational problem is larger: no one knows who owns the riser, who approved the work, who has access to the closet, or which vendor is accountable for restoration.
When shared infrastructure breaks, the first practical question is not merely who touched it. It is: what breaks if this system goes down? Identifying downstream impact makes the governance problem concrete. It also helps decision-makers prioritize the interfaces where failure will produce the highest cost, longest disruption, or greatest tenant impact.
Why Shared-Infrastructure Ownership Becomes Unclear
- Contract silos: Lease agreements, construction scopes, and service contracts are often created by separate teams. Without reconciliation, no single source of truth exists for shared assets.
- Short-term fit-out incentives: During construction, parties may push responsibility to another scope to reduce cost or speed completion. Those decisions are rarely revisited as the building, vendors, or ownership changes.
- Documentation decay: Drawings, change orders, access lists, and operational knowledge live in separate locations. When a vendor leaves the site, the people who understood the installation may leave with them.
These patterns do not create a problem only on paper. They create the conditions for outages, emergency work, tenant dissatisfaction, unplanned costs, and difficult negotiations after a failure.
Examples of Responsibility Gaps in the Field
One example involved a tenant that installed a private fiber path from a basement riser to its floor. The path crossed landlord spaces but was documented only in the tenant handover binder. Two years later, a landlord contractor re-terminated fiber in the same riser during a lighting upgrade and severed the tenant path. The tenant lost internet service for hours, and resolution required emergency technician time, rerouting work, and a tenant-retention discussion.
Another incident involved a security camera feed that went dark over a weekend. A contractor had temporarily repurposed a riser circuit without updating access lists. Warning signs had been present: inconsistent closet labeling, multiple vendors carrying independent key sets, and informal workarounds recorded only in email.
A third example centered on intermittent HVAC control faults during peak season. Shared building-automation controllers had split responsibilities: tenant-side logic called vendor-side endpoints, but no party owned end-to-end testing. Repeated tickets were passed back and forth, and there was no single troubleshooting runbook.
Centralized Control Versus Tenant Autonomy
There is no universal ownership model. Centralized landlord control can be appropriate for multi-tenant office buildings where shared fiber, centralized security, standardized maintenance, uptime, and predictable capital planning are priorities. It simplifies maintenance boundaries and helps create uniform operating standards.
Tenant autonomy can also be necessary. Tenants with specialized automation, unique network topologies, colocation requirements, or other specific technology needs may require flexibility over portions of their infrastructure. The practical approach is to lock down high-impact interfaces, where failure is costly or difficult to remediate, while allowing flexibility where risk is lower and recovery is straightforward.
A Practical Governance Framework
The recommended starting point is a 90-minute ownership-mapping workshop supported by a short checklist. The goal is not to produce a complex governance program before taking action. It is to create visibility, name accountable parties, and document the assets and interfaces that matter most.
- Asset cataloging: List risers, closets, feeders, and control points. Include physical location, patching information, and vendor contacts.
- Decision ownership matrix: Identify who may make changes, who approves work, and who leads emergency response for each asset.
- Maintenance boundaries: Define responsibility for cabling, power feeds, labeling, access control, and related maintenance.
- Minimum contractual language: Include handoff documentation, test signoffs, and a 30-day acceptance period in fit-out scopes. Final contractual language should be reviewed by legal counsel.
Three Actions to Take This Week
- Document the physical path and termination points for every shared riser and closet, even if the first version is a one-line record.
- Create a current contact list for everyone with keys, credentials, or rack access.
- Record existing exceptions and temporary workarounds in one location, with an expiration date.
Durable responsibility matters because people change, vendors leave, and contracts expire. A forced handoff process and a living asset catalog keep risk visible. That visibility can be the difference between a quick recovery and a multi-day outage.
For the downloadable riser ownership checklist and workshop template referenced in this episode, visit gds.technology/builtwiredsecured and look for the riser ownership checklist.
Shared Infrastructure Needs Clear Ownership Before It Fails
Commercial buildings depend on infrastructure that no single person or team may fully own. Telecom closets, riser cabling, fiber paths, power feeds, security connections, and building-automation touchpoints often cross landlord spaces, tenant environments, contractor scopes, and provider responsibilities. These systems can operate quietly for years. Then a routine change, tenant fit-out, upgrade, or troubleshooting effort exposes a basic problem: nobody can clearly answer who is responsible.
That uncertainty is more than an administrative inconvenience. It increases downtime, emergency costs, tenant frustration, and the likelihood that an incident gets passed between facilities, IT, leasing, contractors, and service providers without a coordinated response.
The practical question for property owners, facilities leaders, and tenant technology teams is simple: who owns the riser? More broadly, who has decision authority, maintenance responsibility, access rights, emergency-response duties, and documentation accountability for every shared infrastructure component?
Why Ownership Gaps Become Operational Failures
Shared infrastructure is vulnerable because it exists at the boundary between multiple parties. Lease language may address one set of obligations. Construction scopes may define another. Service contracts may be managed separately. Each document can be reasonable on its own while still leaving critical interfaces unassigned.
Three patterns repeatedly create this outcome. The first is contract silos. Different teams draft leases, construction scopes, and vendor agreements, but nobody reconciles them into one operational view of shared assets. The second is short-term decision-making during fit-outs. It can be easier, faster, or less expensive to label a responsibility as landlord scope or tenant scope than to resolve the details. The third is documentation decay. Drawings, access lists, change orders, and operational notes end up distributed across handover binders, email threads, contractor files, and individual knowledge.
When a contractor leaves the property, that operational knowledge can disappear. When the building changes hands, historical decisions may not transfer. When a tenant changes providers or alters its environment, an undocumented dependency can be affected without anyone realizing it.
What a Shared-Infrastructure Incident Looks Like
A typical failure may begin with a contractor opening a riser panel in a telecom closet during a fit-out. The consequences can extend far beyond the immediate work area: multiple floors may lose phone service, a building-automation system can trip, and a point-of-sale system may go down. Tenants call leasing. Leasing calls facilities. Facilities calls IT. Meanwhile, no one can establish who authorized the change, which vendor has access to the closet, or who is responsible for restoring service.
In this situation, technical troubleshooting must happen, but the absence of governance makes restoration slower. The relevant operational question is: what breaks if this goes down? Once teams identify the downstream impact of each shared interface, they can prioritize the systems that require stronger controls, clearer boundaries, and better documentation.
Examples of How Documentation Decay Creates Cost
One anonymized example involved a tenant that installed a private fiber path from a basement riser to its floor. The cable path crossed multiple landlord spaces, yet the installation was documented only in the tenant handover binder. Two years later, a different contractor, working for the landlord during a lighting upgrade, re-terminated fiber in the same riser and severed the tenant’s connection.
The result was hours of lost internet service. The property and tenant then had to absorb emergency technician time, patchwork rerouting work, and a tenant-retention negotiation. The root cause was not simply an incorrect fiber termination. The root cause was the lack of an accessible, shared record defining the fiber path and the parties responsible for it.
Another example involved a security camera feed that went dark over a weekend. A contractor had temporarily repurposed a riser circuit without updating the access list. In hindsight, the building had several visible warning signs: inconsistent labels in closets, independent key sets held by multiple vendors, and informal workarounds that existed only in email threads.
In a third incident, a tenant experienced intermittent HVAC control faults during peak season. Tenant-side logic called vendor-side endpoints on shared building automation controllers. No one owned end-to-end testing, so tickets were repeatedly reassigned between parties. The lack of a single troubleshooting runbook turned a recurring issue into an accountability problem.
Choose Governance Based on Risk, Not Habit
Property teams do not need to choose between complete landlord control and complete tenant independence. The right model depends on the building, the technology, and the consequences of failure.
Centralized control is often effective in multi-tenant office buildings with shared fiber, centralized security, uniform service expectations, and a need for predictable maintenance and capital planning. It can clarify maintenance boundaries and reduce the chance that separate tenant activities interfere with shared systems.
However, tenants may need autonomy when they have specialized automation, colocation needs, or unique network topologies. A one-size-fits-all landlord standard can limit legitimate operational needs. The practical standard is to identify the interfaces where failures would be most costly and lock those down. Then allow flexibility in areas where risk is lower or failures are easier to remediate.
This risk-based model makes governance useful rather than restrictive. It protects the shared systems that affect many occupants while recognizing that tenants may require tailored technology solutions inside their own environment.
Make Handoffs Explicit During Fit-Outs
Ownership is especially likely to become unclear during transitions: between contractor and operations, between build-out and occupancy, or between temporary and permanent service arrangements. These transitions require explicit, time-boxed handoffs in the project plan.
A simple model is to define a control point at the riser boundary, name the responsible party, and establish a 30-day acceptance window. During that window, the installing contractor remains available to validate connections and documentation. After the acceptance period, responsibility moves to the operations team.
This approach prevents assets from sitting in limbo. It also creates a clear expectation that documentation and validation are part of completion, not optional follow-up work after the contractor has departed.
Run a 90-Minute Ownership-Mapping Workshop
A short ownership-mapping workshop can establish an actionable foundation. The purpose is to capture the most important shared assets, document interfaces, and assign responsibility before an outage forces the issue.
- Catalog assets: List risers, closets, feeders, control points, physical locations, patching details, and vendor contacts.
- Assign decision ownership: Document who can make changes, who approves work, and who leads emergency response.
- Define maintenance boundaries: Establish responsibility for cabling, power feeds, labeling, access control, and maintenance.
- Set minimum fit-out requirements: Require handoff documentation, test signoffs, and a 30-day acceptance period. Have legal counsel review final contract language.
The workshop does not need perfect records on day one. It needs enough accurate information to make dependencies visible and to stop critical work from proceeding without the right approvals.
Three Documents That Reduce Risk Immediately
Teams can make progress this week by documenting three items in a single, accessible location.
- The physical path and termination points for each shared riser and closet.
- The current contact list for people with keys, credentials, and rack access.
- Existing exceptions and temporary workarounds, each with an expiration date.
These records reduce finger-pointing and speed remediation when something fails. They also reveal recurring risk signals before an outage: mismatched labels, split tickets, ad hoc keying, undocumented access, and service issues that bounce between vendors.
Build Durable Accountability
Shared infrastructure governance is not about creating bureaucracy for its own sake. It is about making responsibilities durable when people, vendors, and contracts change. A living asset catalog and a forced handoff process preserve visibility across the lifecycle of the building.
For commercial properties, that visibility supports tenant uptime, reduces coordination failures, and improves both capital and operational planning. It gives decision-makers a practical way to distinguish between a quick fix and the conditions that lead to a multi-day outage.
To hear the full discussion and access the riser ownership checklist and workshop template referenced in the episode, listen to Built, Wired & Secured and visit gds.technology/builtwiredsecured.