Two providers do not answer every question
A connection strategy needs to describe the dependencies behind the service. When reviewing proposals, the client team can ask its appointed network specialists to explain physical routes, building entry points, shared infrastructure and the assumptions behind failover. The number of supplier names alone does not establish independence.
Bring the interfaces into the programme
Connectivity requirements should be visible alongside power, design and procurement milestones. Identify who confirms the technical requirements, who coordinates the routes and permissions, and who obtains the operator information. Record decisions that could affect space, access, civil works or the sequence of delivery.
Agree how the strategy will be demonstrated
Ask the responsible specialists to define the testing, acceptance criteria and handover information. Clarify what is included in each appointment and contract, what remains an assumption, and who will own operational procedures after handover. A development tracker is useful only when the underlying responsibilities are clear.
The client-side contribution
An independent client representative can bring these workstreams into a consolidated action register and decision report. We coordinate the appointed teams and escalate missing inputs to the client. Network design, resilience assessment and testing remain with the appropriately appointed specialists.
Inspired by Moroz & Partners’ LinkedIn post on connectivity resilience
Open the source on LinkedIn