sitebraid.

CAMPUS CHALLENGE / DECISION BRIEF

Tenant diversity can still hide a campus-wide failure point.

Two carriers can fail together because they share one bridge, one duct bank, one powered node or one control dependency.

ILLUSTRATIVE FAILURE SCENARIO

How the problem unfolds

Assume each tenant contracts with two carriers and the campus has separate building entrances. Upstream, both services use a common road crossing and the same local aggregation facility. Expansion excavation damages the crossing. The buildings' independent entrances remain intact, but both external paths fail. A separate operating network also depends on a powered communications node without the expected backup. The commercial diversity was real; the physical and operational independence was not.

Hypothetical development case. Assumptions are not project results, quoted prices or predicted failure rates.

TEXAS / LAW, REGULATION & LOCAL REQUIREMENTS

The Texas constraints to resolve

Reviewed September 10, 2026

Development issues to resolve, not a legal opinion. Applicability depends on the parcel, provider, project configuration and current instruments. Texas counsel, the responsible authority and qualified technical specialists should confirm the route before commitments are made.

Which requirements apply to this campus?

  • Identify which crossings use TxDOT right of way and which depend on private easements. Ask carriers for evidence covering both approaches to each crossing.
  • Distinguish covered excavation-notification obligations from private-facility locating and the operator's live-work permissions.

Use these questions to direct the review, not to determine legal eligibility. Open the applicable constraint below for the source, consequence and next action.

Different carriers may depend on the same permitted crossingTxDOT right-of-way installations and route-specific private rights.

Texas basis. The state highway accommodation framework controls the location and conditions of utility installations. A carrier agreement does not itself establish a second permitted physical route. TxDOT Utility Accommodation Rules guidance

Campus consequence. Two commercial services can converge on one approved crossing because the alternate path lacks accommodation or private rights. Contractual diversity is not evidence of physical independence.

Resolve before commitment. Obtain route and crossing evidence from the carriers, with confidentiality protections where needed. Confirm the separate accommodation and easement route before describing the campus as physically diverse.

A locate request is not a complete live-fiber protection planTexas Utilities Code Chapter 251; coverage and exceptions require review.

Texas basis. Section 251.151 establishes notice duties for covered excavation, with specified timing and exceptions. The chapter's process is not an assurance that every private campus facility has been identified. Texas Utilities Code Chapter 251, including §251.151

Campus consequence. A contractor can hold a notification record and still lack the information needed to protect owner-installed or otherwise unmarked lines. The consequence can affect several tenants at once.

Resolve before commitment. Confirm statutory obligations with the excavation team, then add private-facility locating and operator-approved protection. Reconcile all carrier and campus records before authorizing a shared crossing.

01 / CAMPUS EXPOSURE

Follow the consequences.

Physical routes
Identify common ducts, bridges, rail crossings, manholes and last-mile rights. Record unknown segments as unresolved exposure rather than assuming independence.
Powered infrastructure
Ask about shared aggregation points, power supply and restoration dependencies. Two fiber paths may still rely on the same facility or regional access route.
Control systems
Separate tenant traffic from the campus monitoring and operating dependencies. A communication failure should be evaluated for its effect on alarms, control and authorized recovery.
Contracts
Define notice, evidence and review requirements for material route changes where obtainable. A delivered diverse route can become less diverse after provider maintenance or migration.
Construction
Make locate, protection and crossing plans reflect both live carrier paths. A common contractor or excavation zone can defeat otherwise separate systems during campus expansion.

COMBINED FAILURE TEST

A common crossing fails and restoration cannot reach it

Test loss of the shared crossing while construction blocks the restoration route and a powered aggregation node loses supply. Count only continuity options that survive those same dependencies. Two service contracts do not establish two recoverable paths.

Questions to take to the project team
  1. Can one excavation, flood-prone crossing or powered facility interrupt both services?
  2. What evidence supports the route beyond the campus boundary, and which segments remain unknown?
  3. How will the owner learn that a provider has rerouted a supposedly independent path?

02 / RESPONSE CHOICES

When to advance. When to stop.

These are decision conditions, not universal thresholds. Confirm the evidence with the responsible providers, specialists and affected tenants before the owner authorizes a commitment.

Remove a common physical segment

Advance whenThe new segment removes the controlling shared failure and its rights, construction and upstream connections are supported.

Stop or revise whenThe paths separate at the campus boundary but reconverge at the same critical crossing or powered node.

Tradeoffs and scope

Secure and build a genuinely separate last mile or crossing where that is the controlling exposure. Confirm upstream independence within the agreed resilience scope.

Contract for evidenced diversity

Advance whenCarrier evidence supports the agreed diversity boundary and changes trigger a review.

Stop or revise whenThe evidence is unavailable or only shows carrier brands, not the relevant route dependencies.

Tradeoffs and scope

Define the required route information, changes and acceptance with the carriers and tenant. Recognize confidentiality limits and do not present unavailable evidence as verified independence.

Accept a bounded residual risk

Advance whenThe tenant explicitly accepts the identified common risk and a supported continuity response.

Stop or revise whenMarketing or lease language still describes the service as fully independent despite the retained shared exposure.

Tradeoffs and scope

Where full separation is uneconomic or unavailable, document the common dependency and price an appropriate continuity option with the tenant's technical team. Do not market the result as fully diverse.

The work Sitebraid would take on

Sitebraid would bring carrier evidence, rights of way, campus layout and construction sequencing into a shared-risk map. We would distinguish fixable last-mile conflicts from upstream dependencies requiring provider or tenant decisions, then coordinate the selected route, funding and protection works. Network specialists validate architecture and performance. The owner receives an evidenced resilience claim with known limits, not simply more carrier logos.

03 / DECISION GATE

Evidence before commitment

  • Provider-supported path evidence and an explicit boundary for the diversity claim.
  • Accepted common-risk register covering physical, powered and control dependencies.
  • Funded protection or rerouting works and a route-change review process.

NEXT ACTION

Start here

Ask the carriers to identify the common structures, not just draw different colored lines. The unanswered part of that request is the risk to resolve before tenant acceptance.

SITEBRAID RESOURCES

Take the working tool into the owner meeting

Source context and boundaries

Reviewed September 10, 2026. The scenarios and decision tests are Sitebraid analysis. Source materials establish context, not approval of a particular project. Applicable law, provider terms and technical requirements require project-specific confirmation.