sitebraid.
All insights

CONNECTIVITY / INSIGHT

Two carriers do not automatically mean two independent routes.

Treat last-mile connectivity as campus infrastructure. Commercial diversity and physical diversity are different decisions.

Two carrier proposals can look like a resilient connectivity strategy until the routes are drawn on the same map. Both may use one bridge, one duct bank or one entrance into the campus. The owner's problem is not a shortage of carrier names. It is a gap between the service the tenant expects and the physical routes the project can actually deliver.

The campus problem

Illustrative scenario, not a claimed client result.

Two carriers can quote service to a Texas campus, but the operator requires resilient connectivity for its first operating phase. The last mile may share a crossing, corridor or campus entry, and neither installation is fully integrated into the construction schedule. The assignment is to establish the physical delivery scope and close the gaps between service procurement and accepted connectivity.

Commercial diversity and physical diversity answer different questions

A second contract can provide commercial choice without eliminating a shared physical failure. Review the route from the campus boundary to the relevant network handoff, including common crossings, structures and intermediate facilities to the extent the carriers can substantiate them. Two entrances on different sides of a building may still converge immediately outside the property. Conversely, a technically attractive second route may lack the easements or construction permissions needed to meet the opening date.

The last mile is often where the project changes from procurement to development. Someone must secure the corridor, coordinate crossings, construct civil infrastructure and accept the installed connection. Those responsibilities can sit with the carrier, the landlord, a third-party infrastructure owner or several of them. The service price should be evaluated alongside those capital obligations and the operating rights that survive a lease change or property sale.

The Texas context

TxDOT’s fiber guidance addresses installation requests and the right to occupy another utility’s conduit or structures in highway right of way. A carrier’s presence near the site does not itself complete the access and construction arrangements for a campus connection.

Underwrite the route, not just the service contract

A carrier may quote recurring service while leaving civil works, rights of way and an unusual crossing to the campus. Identify the construction contribution, owner of the duct, maintenance access and restoration responsibility. Where tenants share a last mile, allocate the costs and capacity without assuming that separate carrier contracts mean separate failure exposure.

Resolve the missing route, not just the missing order

Suppose two carriers both cross the same highway structure before reaching the campus. The owner could investigate a different crossing, a different network handoff or an accepted interim service arrangement while a separate route is built. The tenant's actual resilience requirements determine which routes are useful. A nominal second connection that retains the critical shared exposure should not be presented as equivalent to a physically independent path.

Sitebraid would coordinate the carrier evidence, land rights and civil schedule with the operator's acceptance requirements. The decision package should separate confirmed segments from assumptions and assign construction and maintenance responsibility for the shared infrastructure. If the second route is delayed, the owner needs the tenant's explicit acceptance of any interim configuration and a funded completion plan. At turnover, route documentation, tests and operating contacts should describe what was installed, not what the original sales proposal intended.

Solutions and their tradeoffs

Use the offered routes

The available evidence demonstrates the agreed separation and operational requirements.

Conditions to resolve: Carrier route evidence and a clear owner for each last-mile construction segment.

Commission a distinct second path

The existing services share a material vulnerability that can be addressed.

Conditions to resolve: Feasible route, land rights, crossings, carrier scope and funded construction schedule.

Revise phase acceptance or choose another solution

An independent path cannot be delivered within the current brief.

Conditions to resolve: Explicit operator decision on residual risk, timing and alternative service configuration.

Test common failure points, not carrier counts

Illustrative route-evidence matrix. Unknown segments are unresolved exposure, not evidence of independence. Carrier confidentiality may require controlled review rather than public route disclosure.

Swipe or scroll to compare all columns.

SegmentCarrier A / Carrier BConsequence and required action
Campus entrancesEast / WestSeparate gates do not establish end-to-end diversity.
Highway crossingBridge 1 / Bridge 1A single incident can affect both; investigate a genuinely separate crossing.
Intermediate structureVault A / UndisclosedObtain sufficient confidential evidence before treating the paths as independent.
Network handoffFacility X / Facility YCheck upstream shared-risk groups and the tenant's required failure boundary.
Interim acceptanceTwo services, one unresolved crossingDocument the residual risk, tenant acceptance and funded second-route completion; do not market full physical diversity.

This is the development problem behind our shared fiber dependencies challenge. Our Fiber & connectivity capability explains the scope Sitebraid can take on.

Putting the analysis to work

We would agree the operator’s capacity, latency and resilience requirements, then obtain the appropriate route and ownership evidence through carrier confidentiality arrangements. The network specialists should distinguish carrier brands from physical paths and identify what is known, what is attested and what remains unverified. Site entry, internal distribution and meet-me-room arrangements belong in the same review as the external routes.

How Sitebraid would support this decision

Trace the connection end to end

With the carrier and network teams, identify shared structures, route segments, entry points and other common dependencies relevant to the operator’s brief. Keep sensitive route drawings in the controlled project file rather than in public material. A map-level indication should trigger verification, not become an availability claim.

Resolve the land and crossing work

Establish the rights and applications needed for each route. Where highway right of way is involved, have the responsible utility or contractor advance the applicable TxDOT process. Confirm who owns, builds and maintains each segment and who is responsible if another project requires a relocation.

Integrate the campus construction

Coordinate conduit, chambers, entries and internal distribution with the civil and building teams before those areas are closed. Include carrier access, installation windows and specialist testing in the schedule. Track external works separately from the facility’s readiness to receive them.

Test and hand over the actual service

Agree the test and documentation requirements with the operator and carriers before installation. Reconcile as-built routes with the intended design and obtain the relevant service acceptance records. Identify any unresolved common dependency for explicit operator acceptance rather than hiding it behind the word diverse.

How we protect the decision

We would maintain a route-and-responsibility schedule, a confidentiality-controlled evidence file and a list of unverified segments. The owner approves changes to the resilience brief and additional last-mile cost. Delay in a crossing or easement should feed into the phase turnover forecast. We would not substitute a sales assurance for the technical acceptance required by the customer.

The result the owner should require

The agreed endpoint is installed and tested connectivity meeting the defined operating brief, with the accepted residual risks documented. If our engagement is limited to readiness, completion is the agreed evidence and executable construction scope, not a claim that the service is already live. The distinction must remain visible to procurement and the operator.

How to measure progress
  • Route segments supported by evidence versus still unverified.
  • Shared dependencies accepted or removed under the operating brief.
  • Land rights, crossing approvals and construction responsibilities closed.
  • Completed installation, as-built information and accepted service tests.

The decision to take forward

Buy a deliverable route and service outcome rather than a count of providers. Protect the necessary corridors during master planning, establish the construction responsibilities and verify the installed paths against the tenant's requirements. Connectivity is complete when it reaches the operating boundary on the agreed terms.

If your two carriers might share the same path, our Fiber & connectivity work checks how independent the routes really are and who holds the rights to deliver them.

Continue with Buy the development footprint, not the acreage headline. to examine the connected decision.

Sources and scope

TxDOT: fiber optic telecommunications in highway right of way

Route-sharing risk is our engineering coordination concern, not a claim about any named carrier. TxDOT requirements apply to relevant highway installations.

The analysis and proposed approach are Sitebraid viewpoints. Scenarios and numerical examples are illustrative, not client results or project estimates. Specialist design and regulated work remain with the qualified project teams. Public context was reviewed September 7, 2026.

Questions or corrections? Email insights@sitebraid.dev.

Is this holding your campus back?

Tell us what needs to move. We can discuss the development work your team needs.

Email the Sitebraid team