When the Client Breaches the Contract: Compensation Event 60.1(18)

How the catch-all breach event works, which specific events to try first, and why it pays your cost and Fee rather than damages.

Compensation events and change3 min read

On this page
  1. What has to be true
  2. Try these first
  3. Late payment is different
  4. Worked example
  5. How it is assessed
  6. What people get wrong
  7. Related guides

Under clause 60.1(18), a Client's breach of contract is a compensation event, as long as no other listed event already deals with it. It is the catch-all entry, so most Client defaults end up in the same process as everything else: notify, quote, assess. It appears in NEC3 and NEC4.

It sits at the end of the list, so start by hunting for a narrower entry. A narrow clause has a cleaner test and invites fewer arguments.

What has to be true

  1. The Client has breached. Not the Project Manager using a contract power, and not simply something you dislike. The contract must require something of the Client that did not happen, or forbid something that did.
  2. Nothing else covers it.
  3. It had an effect. As always, clause 61.4 needs a change to Defined Cost (your actual cost as the contract defines it), Completion or a Key Date.

Try these first

What the Client failed to do Specific event
Give access to the Site on time 60.1(2)
Provide something by the programme date 60.1(3)
Keep its own work within the programme or Scope 60.1(5)
Supply materials or facilities for tests 60.1(16)
A Client fault, or a risk the contract lists as the Client's 60.1(14)
Anything else breaching the contract 60.1(18)

This ordering has a benefit. When a specific entry fails on a technicality, the breach route can pick up what is left. Suppose the Scope obliges the Client to supply a permit, yet the Accepted Programme gave no date for it. The test in 60.1(3) cannot work, yet the duty was clear. Expect debate about when it fell due.

Late payment is different

Late payment seems an obvious example, but the contract gives it a separate remedy. Clause 51.2 provides interest, and there may be statutory rights too. Read those before using this event for an unpaid invoice.

Worked example

A fictional care home refit on Option A, 10% Fee. The Scope says the Client will keep the shared loading bay clear in working hours, your only delivery route. For ten days the Client lets a neighbouring business stack pallets across it.

The bay lies outside the Site boundary, so access (60.1(2)) does not fit. It is not Others working on the Site and not a listed Client risk. Even so, the Scope placed a plain obligation on the Client. You warn on day two and notify under 60.1(18) on day four.

Effect Cost
Hand-carrying deliveries and a banksman £4,200
Crane delivery rebooked £1,300
Slower fit-out £2,500
Subtotal £8,000
Fee at 10% £800
Change to the Prices £8,800

The slowdown fell on work with float, so the Completion Date does not move.

How it is assessed

It follows clause 63 like every other event: the change in Defined Cost with the Fee on top, and the change to planned Completion. It is not a damages claim, and items outside Defined Cost will not come through. NEC4 clause 63.6 (63.4 in NEC3) makes those changes your only entitlement for the event. If you think another claim can sit beside it, that is a legal question, so take advice where sums are large.

Nothing from the Project Manager caused most breaches, so you notify and the eight-week time bar applies. Calling it a breach does not escape that.

What people get wrong

  • Leading with breach when a specific entry fits. Cite the specific one and add this in the alternative.
  • Using it for decisions you disagree with. A Project Manager's judgement is not automatically a Client breach.
  • Expecting damages. Cost plus Fee can feel low. That is the bargain.
  • Accepting "not listed". If there is a breach, it is listed.
  • Skipping Z clauses. They can narrow this entry.

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

Was this useful?