Working as a contractor under NEC4: what to protect from tender to completion

A practical NEC4 guide for contractors new to the form: what to check at tender, the three things to protect on site, and the traps that cost money.

Tendering and starting a contract4 min read

On this page
  1. In plain English
  2. Before you price
  3. Three things to protect on site
  4. Traps that catch contractors
  5. A short illustration
  6. Related guides

NEC rewards the contractor who tells the other side early, keeps the programme up to date and prices change properly as it happens. It punishes the one who leaves paperwork until the end. There is usually no big final account to rescue you, because change is meant to be notified, priced and paid as the job goes along.

This guide covers the NEC4 Engineering and Construction Contract (ECC), where you are "the Contractor", the party doing the work.

In plain English

Report events the day you spot them, keep an accepted programme in place, and make sure every agreed change reaches your payment.

Before you price

  • Start with the Z clauses. These are amendments the Client has written in. They can shift risk or cut notice periods, so either price them or ask about them.
  • Work out who carries ground and weather risk. Look at the Site Information, any limits in the Contract Data (the project-specific entries), and how 60.1(12) and 60.1(13) interact with them. Weather payment turns on the weather data the contract points to.
  • Know your main Option. On A you carry your own cost risk, on C you share it. See choosing a main Option.
  • Test the Fee and price the admin. The Fee must cover what Defined Cost leaves out (52.1), and planner and QS hours go into quotations and revisions.

Three things to protect on site

1. Your right to be paid for an event

Tell the Project Manager about an event later than eight weeks after you knew of it and, in general, neither the Prices nor the dates will change (61.3). The exception is an event caused by something the Project Manager or Supervisor did. So foremen and engineers must report oddities the day they see them, without waiting for a QS to cost them.

Warn as well. If a contractor of normal experience would have warned and you did not, the assessment can proceed as if you had (61.5, 63.7). See missed early warnings.

2. Your programme

The Accepted Programme (named in the Contract Data, or the one the Project Manager last accepted) is the yardstick for delay, so an out-of-date one weakens your case. Send revisions on time with genuine logic, and leave float visible.

Where the Contract Data names no first programme, each assessment holds back 25% of the Price for Work Done to Date (the value of work done so far) until you send one in (50.5). Two buffers protect you against your own slippage: terminal float and time risk allowance. Do not give them away. See terminal float.

3. Your cash

  • Apply before every assessment date (50.2), and check each certificate within a week.
    • Push events through to implementation. If one is notified but never quoted, it normally has not reached the Prices, so it has not reached your bank.
  • Keep cost evidence. Under C, D and E, unsupported cost can become Disallowed Cost. See defined cost, fee and disallowed cost.

Traps that catch contractors

  1. Extra work on a spoken request. Without an instruction there may be no compensation event. Ask for it in writing and keep a note of having asked.
  2. Assuming a quiet Project Manager helps you. Silence only turns into acceptance after you give notice of the failure to reply. So chase, then notify (61.4, 62.6, 64.4, 31.3).
  3. Quoting low to keep the peace. After implementation the assessment normally stands, even if you were wrong (66.3). Forecast honestly and state your risk allowance.
  4. Pricing change from tender rates. An event is assessed from forecast Defined Cost plus Fee, not by remeasuring at your tender rates.
  5. Ignoring subcontract timing. Their deadlines run on regardless. See managing NEC subcontracts.

A short illustration

An Option A culvert job, invented numbers. Bad ground costs £60,000 and three weeks. The foreman knew in March, the QS noticed in June, and nobody warned.

  • Notified in April: a quotation of about £60,000 and three weeks, if 60.1(12) is made out.
  • Notified in late June: more than eight weeks have passed, so probably nothing. You carry the cost, and delay damages under X7 may follow.

One short email from site in March would have changed the result. NEC3 has the same eight weeks, with different wording on what starts the clock. If your team comes from JCT, say plainly that an end-of-job claim does not carry across.

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

Was this useful?