Power, Water, Telecoms: Putting Third-Party Connections Back Under Commercial Control
Photo: Meirion , CC BY-SA 2.0, via Wikimedia Commons
Utility connections are rarely described as construction work, yet they can sit on the critical path with the same authority as a steel frame. A new supply, a capacity upgrade, a water connection or a telecoms duct can absorb programme float months before the first trade reaches site. The commercial risk is not only that the utility is late. It is that nobody can show who was responsible for the application, the information, the acceptance or the access.
Build a connection responsibility matrix
Start with a matrix that names the applicant, the payer, the information provider, the acceptor, the party responsible for land access and the party responsible for commissioning. The matrix should cover each utility separately: electricity distribution, water and sewerage, telecoms and any private network. Identify whether the connection is to a distribution network operator, an independent distribution network operator, a water undertaker or a telecoms provider. Record the contract mechanism that makes each obligation enforceable, whether that is a client obligation, a contractor obligation or a shared risk.
Check lead times as programme milestones
Utility lead times are often described in months, but the programme needs dates. Break the connection into stages: capacity enquiry, point of connection, offer, acceptance, design approval, legal agreement, construction, commissioning and energisation. Add each stage to the programme as a third-party milestone with an owner and a hold point. Check offer validity periods and any conditions attached to acceptance. An accepted offer is not an energised supply. A wayleave signature is not a completed connection. The programme should show the difference.
Pin down client-supplied information
Many connection delays begin with missing information. Load schedules, single line diagrams, site layouts, ownership boundaries, existing services and access arrangements are common examples. Set information due dates in the programme and link them to the connection stages. Where the client is responsible for information, record the date requested, the date received and the effect of any late receipt. Where the contractor is responsible, do not let the obligation sit in a document without a named owner.
Treat wayleaves and adoption as commercial items
Wayleaves, easements and adoption agreements are not administrative footnotes. A wayleave may be a personal permission rather than a permanent interest. An adoption agreement may carry design, construction, bond and maintenance obligations. Record the legal position, the parties, the duration and the payments. Check whether adoption affects the programme or the cost of temporary works. If a landowner or utility requires access, confirm that the access is documented before the relevant works start.
Recover cost only with evidence
When a third-party connection slips, the first question is not who should pay. It is what the contract says about the risk. Check the allocation of responsibility, the notice provisions and the relief mechanism. Then build the evidence: the date of the application, the information provided, the offer received, the acceptance date, the chase correspondence, the revised date and the programme effect. Show mitigation. A claim that simply says the utility was late is unlikely to survive scrutiny. A record that shows causation, notice and mitigation has a better chance.
Run a monthly connection review
Keep a connection register with the utility, stage, owner, due date, actual date, risk rating and next action. Review it monthly alongside the programme. Escalate any stage that is close to a hold point. Carry a programme risk allowance where the lead time is uncertain, but do not use contingency to hide a missing decision. The objective is commercial control: knowing which connection is on the critical path, who must act next and what evidence will be needed if the date moves.