NEC on utilities projects: working with diversions, networks and third parties

How NEC contracts behave on utilities work: network outages, diversions, third-party dependencies, permits and the pressure points to plan around.

NEC by sector2 min read

On this page
  1. What makes utilities programmes different
  2. The NEC pressure points
  3. Programme habits that help
  4. Questions to ask on day one

Utilities work is often shorter and more fragmented than a big civil project: many small sites, live networks, outages and diversions, road space, permits, and other parties who do not work to your programme. If your team is new to NEC, the contract matters most where those outside dependencies meet your own plan.

What makes utilities programmes different

  • Many small jobs, one programme. A mains replacement or connection scheme can be hundreds of short activities across dozens of locations. Good logic and clear grouping matter more than detail on each task.
  • Other people hold the keys. Network operators, statutory undertakers, highway authorities and permit offices decide when you can start or finish. Their dates are rarely yours.
  • Live networks. Outages, shutdowns and tie-ins often have fixed windows, and a missed window can cost weeks.
  • Frameworks and task orders. Much utilities work is let through a framework with separate orders. The programme and the contract mechanics then sit at order level. See task orders explained.

The NEC pressure points

Pressure point What to watch Where to look
Unmapped or mis-recorded services Pipes and cables that are not where the records show Unmarked utilities found
Third parties late or not working as stated Network operators, other contractors and authorities Others delaying you and Client or Others not working as stated
Permits and road space Consents and permissions that decide your start Permits delayed
Access to sites and property Dates the Client must provide access Access dates
Contaminated ground Unexpected material in trenches and chambers Contaminated ground
Weather Work that cannot be done in prolonged wet weather Bad weather

Programme habits that help

  1. Show third-party activities as their own bars, named after the party and the thing they must do, with the date you need it. That is what the programme must show under NEC, and it makes the dependency impossible to miss.
  2. Hold access and permit dates as milestones, so a late consent shows up as a late milestone with a cause.
  3. Group by location or work package, so the Project Manager can follow the programme and you can see where float is being used.
  4. Record outage and tie-in windows with the date they are confirmed, and warn early when they move.
  5. Keep an early warning register that is actually used. On utilities work the problems are usually known weeks ahead. See early warning notice template.
  6. Plan what you will do when a dependency slips: re-sequence to other locations, or stand down. The programme should show it.

Questions to ask on day one

  • Who are the third parties, and what dates do the contract and the Scope give for their work?
  • Which services records are reliable, and what survey is the Scope asking for?
  • What does the contract say about permits and who applies for them?
  • If this is a framework order, what time and money does each order carry?

This guide is general information, not legal advice. Check it against your contract.

Was this useful?