Z clauses: how to read the amendments that change your NEC contract

How to read Z clauses in an NEC contract and what to look for in the time, payment, programme and compensation event provisions they change.

Tendering and starting a contract4 min read

On this page
  1. What a Z clause is
  2. How to read them
  3. What to look for
  4. Check the interactions
  5. What to do with what you find
  6. Related guides

NEC contracts are meant to be standard, but almost none are used unamended. Clients add additional conditions, called Z clauses, to change the standard text. Z clauses can shift risk quite heavily, and they often hide in the back of the contract in a section most people skim. If you work in time, programme or commercial management, you need to read them as carefully as the core clauses.

What a Z clause is

Z clauses are the additional conditions of contract, listed in the Contract Data and given effect by a very short Option (Z1.1 in NEC3 ECC, saying that whatever is listed forms part of the contract). They are written by the Client and can add to, replace or delete the standard text. Some things do not need a Z clause: a change to a reply period belongs in the period for reply entries in the Contract Data, a daily rate for late Completion is Option X7, a liability cap is Option X18, and NEC4 has a Contract Data entry for additional compensation events (60.1(21)). A Z clause that duplicates one of these can end up with two competing rules. Where a Z clause conflicts with a core clause, the Z clause normally takes priority, but check how your contract ranks its documents.

How to read them

  1. Get the full set. Look at the Contract Data, the contract form and any schedules for the complete list. Some Z clauses sit in the Scope or in tender documents.
  2. Read the core clause first. Know what the standard clause says, then read the Z clause against it. Mark what has been added, changed or removed.
  3. Make a comparison table. For each Z clause, note the clause it affects, what changed, and who benefits. A table helps your commercial and planning teams share the same understanding.
  4. Read the definitions. Z clauses often add or change defined terms. A small change to a definition can alter several clauses.
  5. Check with your version. The standard text differs between NEC3 and NEC4, and Z clauses written for one version sometimes sit awkwardly in the other. For example, early warning is clause 16 in NEC3 but clause 15 in NEC4 (where clause 16 deals with something else), and suspension for non-payment under Y(UK)2 is Y2.4 in NEC3 but Y2.5 in NEC4. A schedule reused across editions can amend the wrong clause. Check every clause number against your version.

What to look for

Time

  • Shorter periods for the Contractor to respond or notify, or longer periods for the Client
  • Changes to Completion, Key Dates or sectional Completion
  • New conditions that must be met before Completion is achieved
  • Limits on extension of time for particular events
  • Delay damages that apply on top of, or in a different way from, Option X7 (or a "time of the essence" wording from another form, which does not fit the way NEC moves the Completion Date through compensation events)

Payment

  • Changes to the assessment and payment periods
  • Extra conditions before payment, such as documents or certificates
  • Pay-when-paid or similar arrangements. Take legal advice, because the Construction Act generally prevents payment being conditional on being paid by someone else, with a narrow exception for upstream insolvency
  • A requirement for a VAT invoice or other document before payment, which the core clauses do not make a condition of payment
  • Changes to retention, bonds and guarantees
  • Changes to how Defined Cost, Disallowed Cost or Fee are dealt with

Programme

  • Extra programme contents, such as resources, method statements or specific software formats
  • Changed rules for acceptance, or a stricter reading of what the Project Manager can refuse
  • A requirement to submit a revised programme at set intervals or with each quotation
  • Float and time risk allowances treated differently from the standard approach
  • Rules on how the Accepted Programme is used to assess compensation events

Compensation events

  • Events removed from the list or limited in effect
  • Added compensation events that favour the Client
  • Shorter notification time bars than the standard eight weeks (seven in the NEC4 subcontract). Check clause 61.3 against the Z clause
  • A catch-all condition such as "no entitlement unless all obligations have been complied with", which read literally could remove every event over one late report. A stated consequence tied to a specific obligation is safer
  • Changes to how events are assessed, for example excluding delay costs or capping recovery
  • Extra requirements on quotations, such as more detailed assessment or a required format

Check the interactions

A Z clause on programme acceptance may undermine your ability to rely on the Accepted Programme in a compensation event. A Z clause on notification may cut across the early warning duty. Read them together, not one by one.

What to do with what you find

  • Price the risk. If a Z clause shifts risk to you, reflect it in the price or raise it before signing.
  • Raise it. Ask the Client to explain or amend clauses that are unclear or one-sided.
  • Brief your team. Send site, commercial and planning teams a short note of the clauses that change how they work.
  • Flow down carefully. Make sure your subcontracts reflect the Z clauses that affect them, and don't promise subcontractors more than you are entitled to.
  • Diarise. Put any changed periods and time bars into your calendar and programme process.

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

Was this useful?