NEC on Water Projects

NEC water projects often mean working on live assets that have to keep running, plus buried pipes and poor ground, so outages, physical conditions and staged commissioning cause most of the contract activity. The clauses are ordinary NEC4 Engineering and Construction Contract (ECC) ones, but they need careful use.

This page gives general contract points and doesn't describe any water company's terms. Frameworks in this sector often have their own requirements, so check your Scope, Z clauses and any Option X12 or X20 arrangements. See the guide to managing NEC contracts for the general routine.

Where the contract feels the pressure

Issue	What to check	Clause (NEC4 ECC)
Outages on a live asset	Who decides when, what notice is needed, and what happens if the operator refuses	Scope, 31.2, 33.1, 60.1(5)
Hidden condition of existing structures	What the Site Information shows. Physical conditions test	60.1(12)
Ground and groundwater	Ground reports, any Contract Data limits, and what an experienced contractor could have expected	60.1(12)
Rain and river levels	Weather data covers rainfall in the Contract Data measurements, but not necessarily flooding from elsewhere. Read it closely	60.1(13), 60.1(19)
Client-provided equipment	Pumps, kiosks, valves, and who supplies them when	60.1(3)
Early use	Bringing a new process stream on line before Completion	35.2, 60.1(15)
Performance	Whether Option X17 applies, and how the tests are set up	X17, 41.1

Live assets and outages

If the operator is part of the Client's organisation, is it the Client or Others? The answer matters. The Client's own failure to provide something falls under 60.1(3) or 60.1(18), while Others working outside the Scope's times fall under 60.1(5), as covered in the guide to Others. Clarify this at the start, not when the first outage is refused.

Put outage needs on the programme: the date, duration, what needs isolating, and the notice to give. Show the risk allowance around them. Treat each outage as a small project with its own go or no-go date, and use early warning meetings to look at those due in the next two months.

A worked example

A fictional sewage treatment upgrade, with illustrative figures. The Scope allows up to two 72-hour outages of a settlement tank, each with four weeks' notice to the operator. The Contractor gives notice, and the first outage is cancelled one day before it begins because storm flows are forecast.

1. The Contractor warns that same day: cost and delay are likely.
2. Is it a compensation event? If the cancellation falls outside what the Scope allows the operator to do, then 60.1(5) may apply where the operator is Others. If the Scope lets the operator cancel for wet weather, it may be the Contractor's risk, or there may be another route such as 60.1(13). This turns on what the Scope says.
3. Notify within eight weeks if the Contractor believes it is an event (61.3), with the date of awareness.
4. Quotation: standing costs for the gang and any hired plant, the new outage date with a fresh four weeks, and the movement of planned Completion, plus any effect on a Key Date.

The clearest possible Scope wording, written before tender, would have saved all of that debate. If you're writing the Scope, deal with cancellations directly.

Ground, existing structures and 60.1(12)

Water work often runs along old buried assets, so this event comes up often. Three practical points:

• Baseline survey. A CCTV or structural survey before starting gives both sides a record of the condition at that time.
• What counts. The event is judged on the probability seen at the Contract Date, by an experienced contractor, from the Site Information and publicly available information. Keep a note of what you looked at. See physical conditions.
• Quick decisions. When an open trench is waiting, the normal week may be too slow. Agree how to deal with urgent cases, and use the early warning meeting route (15.2).

Commissioning and handover

• Agree exactly what Completion means for a process asset: mechanical completion, wet commissioning or proving. The Scope should state it. See Completion under NEC.
• Consider sectional completion where parts are handed over at different times.
• Check the effect of the Client's use of part of the works. Unless the Scope covers that use, it may be a take-over (35.2), with implications for 60.1(15) and delay damages under X7.3.
• Make sure operators' training and documents are in the Scope if they're needed before Completion.

Where there is long-term maintenance work on a network, see NEC on maintenance and term contracts.

Related guides

• Managing NEC Contracts: A Practical Guide
• NEC on Energy and Nuclear Projects
• NEC on Building Projects
• NEC on Maintenance and Term Contracts
• NEC on Highways Projects
• NEC on Rail Projects

This guide is general information in our own words, not legal advice. Your contract and its Contract Data always govern. NEC, NEC3 and NEC4 are trade marks of Thomas Telford Ltd; Contract Status is not affiliated with or endorsed by NEC.