What the Client must do under NEC, and what it means when they do not

The Client's few direct duties under the NEC4 ECC, how failures become compensation events, and what to expect from a Client's staff.

NEC basics for newcomers3 min read

On this page
  1. Client failures and your remedy
  2. What the Client keeps for itself
  3. When Client staff give you orders
  4. What a well-prepared Client has in place
  5. Where Clients most often lose ground
  6. Related guides

The Client pays for the work, and its own obligations under NEC are short: let you onto the site, provide what the Scope says it will, take the finished works over, and pay. In daily practice you deal with the Project Manager it appoints, not the Client. NEC4 says Client where NEC3 says Employer, and the clauses here are from the NEC4 Engineering and Construction Contract (ECC). They matter to you because each Client failure can become a compensation event, which is your route to extra time and money.

Client failures and your remedy

If the Client... Clause Your route
Withholds the site access or use you need 33.1 Event 60.1(2)
Fails to supply the services or items the Scope lists 25.2 Event 60.1(3)
Does not provide test materials, facilities or samples the Scope promised 41.2 Compensation event 60.1(16)
Uses part of the works early 35 Possibly taken over; 60.1(15) may apply
Pays late 51.2 Interest on the late sum
Fails to meet its own listed liabilities 80.1 Compensation event 60.1(14)
Breaches the contract in a way nothing else covers n/a Compensation event 60.1(18)

Because of that last line, the compensation event process is your main route to recover time and money, rather than a separate damages claim. Underlying it all is the duty on everyone to act as the contract says and with mutual trust and co-operation (10.1, 10.2).

What the Client keeps for itself

  1. Choosing and changing its team. The Project Manager and Supervisor are named in Contract Data, and the Client may replace them by telling you (14.4).
  2. Termination, if one of the contract's grounds applies (clause 90), with the Project Manager issuing the certificate.
  3. A pay less notice under Option Y(UK)2 (Y2.3), which has to arrive a week or more ahead of the final date for payment.
  4. Dispute steps. In NEC4 it may name senior representatives, and it can take a dispute to adjudication or the final tribunal as the W Option allows.
  5. Contract changes. Changing the conditions needs agreement from both parties (12.3).

When Client staff give you orders

People on the Client side often tell your site team what they would like. Such remarks are not contract instructions, because only the Project Manager can change the Scope (14.3).

Say a council engineer mentions to your site agent that a valve chamber hatch "ought to go a metre east". The agent relocates it. Six weeks later you notify a compensation event, and the Project Manager says no instruction was ever issued. You have built something with no contractual basis, and the Client has its change but a fight over paying for it.

A call to the Project Manager that same day would have settled it. Ask for a written instruction, or for a quotation to be sought beforehand as a proposed instruction (65.1).

What a well-prepared Client has in place

Use this as a test of the party you are working for.

  • A Scope that says what is truly needed, with tests, standards and the Client's own supply obligations.
  • Complete, consistent Contract Data, including access dates, the Completion Date and reply periods.
  • A Project Manager with enough hours and authority to meet those periods.
  • An approval route fast enough for the two weeks allowed to answer your quotation (62.3).
  • Payment arrangements that match the assessment cycle: a certificate inside a week of each assessment date (51.1), and money in your account three weeks later unless Contract Data differs (51.2).

Where Clients most often lose ground

  • Late access. Dates in the Accepted Programme count as well as Contract Data, so read every programme you submit and be sure the access dates in it are right.
  • Late information or supplied items. They are shown on the programme, and if one slips you have an event under 60.1(3).
  • Other contractors clashing with you. Work outside agreed times can trigger 60.1(5).
  • Slow internal sign-off. Unanswered communications can lead to compensation events and treated acceptance.
  • Early use of part of the works. That can shift responsibility for it, so raise it with the Project Manager.

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

Was this useful?