Who Owns the Meter? Making Utility Connections a Programme Workstream
Photo: Thomas Nugent , CC BY-SA 2.0, via Wikimedia Commons
Utility connections have a habit of appearing in a fit-out programme as a single line: power and water connections — supplier. It looks controlled. It is often not. The line may sit with a contractor, a solicitor, a landlord's managing agent or a project manager who already has a full diary. Nobody owns the whole sequence. That is the silent dependency.
The problem is not that connections are ignored. It is that they are treated as administration until they become the critical path. A distribution network operator's offer, a water undertaker's survey, a telecoms provider's survey and an energisation slot do not move to the rhythm of a construction programme. They move to their own statutory and operational timetables. By the time the fit-out is at second fix, the connection enquiry is already late.
The boundary problem
Most fit-out contracts draw a clear line around the works. That line rarely matches the boundary of the utility connection. The contractor may be responsible for internal distribution, containment and containment testing. The landlord may control the incoming supply and the meter position. The tenant may need a new MPAN, a sub-meter or a water account. The telecoms provider may need a wayleave, riser access and a landlord's consent before a cable is pulled.
When these responsibilities are not written down, the gap is filled by assumption. Each party assumes another is progressing the application. The programme assumes a date that has never been accepted. The risk register assumes a contingency that has never been sized. This is not a failure of diligence. It is a failure of definition.
A useful first step is a connections matrix. It should list each utility — electricity, water, telecoms, and any district heating or gas supply — and set out who owns the application, who owns the commercial decision, who controls access, and who provides evidence. The matrix should be agreed before the contractor is appointed, not after the first delay. For multi-let buildings, it should also record the landlord's role in consent, metering and wayleaves.
A date is not evidence
Supplier dates are forecasts, not commitments. A supplier may quote a lead time, but the clock often starts after acceptance, design approval, survey or payment. An offer is not an acceptance. A scheduled date is not a confirmed appointment. An appointment is not an energisation.
The programme needs evidence, not adjectives. For each connection, the project should record the reference number, the current status, the next decision required and the date by which that decision must be made. A weekly connection status report should state what has been accepted, what has been paid for, what has been designed and what has been booked. If the answer is simply 'on track', the report is not doing its job.
This matters most where statutory processes apply. For electricity, the distribution network operator may need to design a new connection, issue an offer, receive acceptance and payment, and then schedule the works. For water, the undertaker may require a survey, a connection agreement and testing before supply is available. For telecoms, the provider may need to survey the route, agree access and install equipment before the service can be ordered. Each stage has a dependency. Each dependency needs a name.
Sequence the connection, not just the works
The common mistake is to compress the connection into the final weeks before practical completion. That is when the pressure is highest and the options are fewest. A better approach is to build a separate connection sequence with its own milestones: enquiry, survey, offer, acceptance, design approval, works order, installation, testing and handover. Then test that sequence against the construction programme.
Where the connection sits on the critical path, the programme should show it. Where it does not, the programme should still show the float. If the float is thin, the risk is real. If there is no float, the project is relying on a supplier's goodwill.
Contingency should be designed, not declared. That may mean a temporary supply, an early meter installation, a phased handover or a pre-agreed standby arrangement. It may also mean ordering telecoms earlier than the fit-out sequence would suggest. The right answer depends on the building and the occupier's needs, but the decision should be taken while there is still time to act.
Define what ready means
Practical completion and occupier readiness are not the same test. A space can be complete in construction terms while the meter is not energised, the water account is not live or the telecoms service is not provisioned. The project should define what 'ready' means for each connection and who signs it off. That definition should be agreed with the occupier before the final month, not discovered at handover.
Handover also needs an evidence pack. Meter serial numbers, MPANs, water account details, telecoms references, test certificates and access arrangements should be recorded and passed to the party who will manage them. Without that pack, the connection becomes an orphan after the keys change hands.
For clients, the test is simple. Ask who owns the connection, ask what evidence supports the date, and ask what happens if the date moves. If the answers are vague, the programme has a silent dependency. It is better to find it now than to explain it later.
IPM Limited's view is that utility connections deserve the same governance as any other workstream: a named owner, a clear sequence, tested evidence and realistic contingency. The meter is not a detail. It is a programme risk with a reference number.
