Client change used up our float: can we still claim under NEC?

When a compensation event eats float on your programme, what you can and cannot recover in time and money, and what to do before the notice window closes.

Programmes and timeScenario3 min read

On this page
  1. The short answer
  2. What to do, step by step
  3. One change, three results
  4. What you can still be paid for
  5. What to record
  6. What not to do
  7. When to get help
  8. Related guides

The Client has changed something, your programme still shows the same finish, and the Project Manager says "it went on float, so there is no time in it". You are asking whether the float was yours to lose.

The short answer

It depends which float. Float on the path the change touches, before planned Completion, is shared by whichever event gets there first, so you usually get no extra time for it. You can still be paid for the cost. The gap between planned Completion and the Completion Date is different: that terminal float stays protected, because the Completion Date moves whenever planned Completion moves. The test is clause 63.5 in NEC4 and 63.3 in NEC3.

What to do, step by step

  1. Notify the event, even if you expect no delay. Eight weeks from becoming aware is the limit under clause 61.3 where the Project Manager has not notified it. Their own Scope-changing instruction falls to them under 61.1, but do not bank on that.
  2. Save the programme. Keep the native file of the Accepted Programme (the one the Project Manager has accepted as your baseline) in force at the dividing date, with float showing on the affected path.
  3. Test the change on it. Insert the new work, then look at planned Completion and any Key Date (a date in the Contract Data by which stated work must be done).
  4. Price cost and time apart. Time can come out at nil while cost does not.
  5. Send the quotation inside three weeks (62.3), with any programme alterations it relies on (62.2).

One change, three results

Picture a bridge bearing replacement. Planned Completion is week 30 and the Completion Date is week 33, so there are three weeks of terminal float. The Client's late change adds two weeks to the jacking sequence.

Float on the jacking path beforehand Planned Completion moves to Completion Date moves to Terminal float after
5 weeks Week 30 Week 33 3 weeks
1 week Week 31 Week 34 3 weeks
None (critical) Week 32 Week 35 3 weeks

Top row: no extra time, and two of the five spare weeks on that path are gone. Every row keeps its three weeks at the end. The contract's deal is that float inside the programme goes to whichever event reaches it first, while the gap at the end stays with the Client.

What you can still be paid for

Item Recoverable?
Your actual cost of the extra work (Defined Cost) plus Fee Yes, even when no time is awarded
Gangs or plant held longer because the activity got bigger Yes, if the forecast shows they are needed
Resequencing inside the float Yes, where it changes Defined Cost
An allowance for risks with a significant chance of occurring (63.8 in NEC4) Yes, if you can justify it
The lost float, priced as a line of its own No: the contract has no such payment

What to record

  • The programme file and a screenshot of float on the path before the event.
  • Dates the instruction was given and when you became aware.
  • Resource plans before and after the change.
  • Any revision that removed float just before the event, with the reason.

What not to do

  • Do not accept "it is on float, so it is not a compensation event". Whether it is one depends on the listed events in 60.1, not on delay.
  • Do not let someone say terminal float should be used first. Delay is not measured against the Completion Date.
  • Do not quote time without checking your Z clauses: some amend how float is treated.
  • Do not let the programme go stale. The float assessed is the float shown at the time.

When to get help

Ask a planner when the change touches several paths or when float values depend on contested logic. Bring in a commercial manager if the Project Manager argues that float vanished in an earlier revision.

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

Was this useful?