Terminal float under NEC: the time buffer at the end of your programme

What terminal float is, why NEC's delay rule protects it, what eats into it and how to show it honestly on your programme.

Programmes and time4 min read

On this page
  1. In plain English
  2. Why the rule protects it
  3. What uses it up
  4. Can the Project Manager object to it?
  5. Finishing early is not automatic
  6. How to show it
  7. Be honest
  8. Related guides

Terminal float means the time between the planned Completion on your programme and the Completion Date in the contract. NEC does not define the term; planners use it for that gap. In practice the gap stays yours: the delay caused by a compensation event is worked out from planned Completion, and the Completion Date shifts by exactly that delay.

NEC3 works the same way, with the rule at 63.3 instead of NEC4's 63.5. This page is only about the tail end of the programme. For float within the sequence, see float and time risk allowance.

In plain English

If you plan to finish before the contract date, the spare time stays yours. A Client delay pushes both dates back together, so your buffer survives, ready to absorb your own problems.

Why the rule protects it

A school extension, invented weeks. The Accepted Programme (the one named in the Contract Data or last accepted by the Project Manager) shows planned Completion in week 30. The Completion Date is week 35. Terminal float is five weeks.

A Client instruction delays the critical path by three weeks. Planned Completion moves to week 33. The delay is three weeks, so the Completion Date moves to week 38. You still have five weeks.

Figure 1. The school extension with planned Completion in week 30 and the Completion Date in week 35, so five weeks of terminal float. A Client instruction adds three weeks to the critical path: planned Completion moves to week 33, the Completion Date moves to week 38, and the five weeks of terminal float survive.
Figure 1. The school extension with planned Completion in week 30 and the Completion Date in week 35, so five weeks of terminal float. A Client instruction adds three weeks to the critical path: planned Completion moves to week 33, the Completion Date moves to week 38, and the five weeks of terminal float survive. Open full size

Had delay been measured against the Completion Date, that event would have given you nothing, since week 33 is still before week 35. Your margin would have been spent on the Client's change. NEC's method avoids that.

What uses it up

What happens Effect on your float
A compensation event is implemented Usually none, both dates shift together
You run late yourself Shrinks once planned Completion moves out
You recover time or plan to finish early Grows
A risk that is yours, like ordinary weather Shrinks
You accept an acceleration quotation The quotation sets a new date and a revised programme

This is why contractors value it: it is the cushion for your own risks, and it sits between you and delay damages under Option X7.

Can the Project Manager object to it?

Not just for having it. A programme that finishes before the Completion Date is not among the four grounds for refusal in 31.3. What the Project Manager can reasonably do is question whether the plan is believable. If you have squeezed the durations to create six weeks of float, they may doubt you will really build that fast. That challenges the realism of the plan, not your right to float.

A Client wanting an earlier finish has two options: write a harder Completion Date into the contract before it starts, or negotiate a deal under clause 36. See acceleration.

Finishing early is not automatic

Having float does not force the Client to take the works early. Clause 35.1 lets the Contract Data record that the Client will not take over before the Completion Date. If that entry is blank, take over happens no later than two weeks after Completion. Read the entry before you promise an early finish. On Option A you are paid for the final activities as they complete, which helps cash flow, yet your preliminaries and security costs may continue until the Client takes over.

How to show it

  • Draw planned Completion and the Completion Date as separate milestones, with the gap labelled.
  • Never hide the gap inside a bloated last activity that lands on the Completion Date. A programme with no visible float looks completely critical and loses credibility.
  • Keep it distinct from time risk allowance, which sits inside individual operations. Terminal float starts after the last of them.
  • Apply the same thinking to Key Dates, where a planned date for meeting the Condition may sit ahead of the Key Date.

Be honest

Show the real position on every revision. If your own delays have used up the float, say so on the programme. Propping it up on paper invites a refusal as unrealistic and leaves you a poor baseline for the next event.

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

Was this useful?