Route decision
You receive A specialist-reviewed route comparison and common-dependency record.
Acceptance The operator can distinguish verified physical independence from contractual diversity and explicitly evaluate any remaining uncertainty.
CAPABILITIES / DEFINED DEVELOPMENT SCOPE
Two deliverable routes, not just two carrier names.
We connect physical resilience requirements to carrier delivery, land rights, civil works and operating acceptance. The scope addresses the gap between commercially available service and a connection the campus can actually use.
Engage us when the operator cannot verify route independence, when the last mile has no accountable delivery party, or when a carrier order depends on works outside its quoted scope. Sensitive route evidence stays within controlled project access.
01 / ENGAGEMENT ENDPOINTS
These are distinct scopes, not an automatic three-stage contract. The engagement defines the selected endpoint, deliverables, authority and acceptance criteria.
You receive A specialist-reviewed route comparison and common-dependency record.
Acceptance The operator can distinguish verified physical independence from contractual diversity and explicitly evaluate any remaining uncertainty.
You receive An assigned and funded last-mile scope with the required rights, permissions and campus interfaces.
Acceptance Carrier and civil delivery obligations reconcile at every boundary; missing work is not left between purchase orders.
You receive Closure of agreed delivery interfaces and collection of carrier and network-specialist acceptance evidence.
Acceptance The operator accepts the specified service and residual shared dependencies. A sales order or nearby fiber is not completion.
02 / WORK PRODUCTS
ILLUSTRATIVE DECISION / NOT A CLIENT RESULT
Illustrative decision: two carriers approach the campus from different directions but use the same bridge outside the boundary. We would not call that end-to-end physical diversity. The operator can fund an independently supported crossing, select a genuinely different route, or knowingly accept the common failure exposure. Renaming the services or separating campus entrances does not resolve the upstream dependency.
03 / TEXAS EXECUTION
Reviewed September 10, 2026. These are development interfaces, not project-specific legal opinions. Counsel and qualified specialists confirm applicability and current requirements.
TxDOT accommodation rules govern installations in state highway right of way. We bring the carrier, civil team and rights specialists around the actual route so commercial availability is not mistaken for permission to build.
TxDOT Utility Accommodation Rules guidanceChapter 251 governs covered excavation notification. We coordinate the required process with private-facility locating and operator-approved access; a notification record is not evidence that every campus line has been identified.
Texas Utilities Code Chapter 251, including §251.151Sitebraid owns the development interfaces, rights-and-construction responsibility map and agreed closure work. Carriers and network specialists retain route representations, service engineering and testing responsibilities. The operator decides whether residual risk meets its resilience standard.
Agree confidentiality protections and the evidence carriers can provide before promising a diversity conclusion. Select the engagement lead and technical reviewers based on the specific connection and construction interfaces, not a list of carrier contacts.