Time Risk Allowance vs Terminal Float in NEC: Why Contractors Need to Keep the Difference Clear

Time Risk Allowance vs terminal float in NEC is a distinction contractors need to keep clear. The two are related, but they are not the same thing, and confusing them can weaken programme acceptance, distort update logic and blur compensation event assessments.

One of the easiest ways to weaken an NEC programme is to blur the line between Time Risk Allowance and terminal float. They are related, but they are not the same thing. NEC guidance requires the programme to show float and time risk allowances, and industry commentary distinguishes TRA from float, including terminal float.

That distinction matters because TRA sits inside the contractor’s realistic plan for events at its own risk, while terminal float is the gap between planned Completion and the Completion Date. NEC guidance says a programme without float or time risk allowance, or one that pushes all the allowance to the end, can be rejected. Fenwick Elliott likewise notes that float and TRA are different concepts and that terminal float is treated distinctly under NEC.

Why Time Risk Allowance vs terminal float in NEC matters

On a live project, both TRA and terminal float can look like “extra time” in the programme. Both can create breathing space between the current logic and the contractual Completion Date. That is why people often merge them in conversation. But commercially and contractually, they do different jobs. NEC’s own recent guidance explains that showing less TRA on critical path operations can bring planned Completion forward and increase terminal float, which only makes sense because they are separate concepts in the first place.

The confusion usually comes from poor programme presentation. Either the contractor hides risk allowance inside durations without explaining it, or it drops a soft block of contingency at the end of the programme and treats that as TRA. NEC says that approach is not logical and is misrepresentative.

What Time Risk Allowance actually is

TRA is the contractor’s allowance in the programme for events that are at the contractor’s risk. NEC guidance says those allowances should sit in the duration of activities or parts of the works, not as a vague lump at the back end. It also says they should be retained when assessing delay to planned Completion caused by a compensation event.

So TRA is not just “spare time”. It is identified, reasoned allowance built into the working programme. If access friction, local logistics, ordinary weather exposure, commissioning uncertainty or similar contractor-risk issues are realistically expected, that is where TRA belongs.

What terminal float actually is

Terminal float is different. It is the gap between planned Completion and the Completion Date. NEC webinar guidance states that the float between planned Completion and the Completion Date, often referred to as terminal float, belongs to the contractor under clause 63.3. Fenwick Elliott and NEC commentary both treat that end-gap as a separate concept from TRA sitting inside the activity logic.

That is why terminal float has a different commercial role. It is not an allowance for contractor-risk events within individual operations. It is the time cushion that exists if the accepted programme shows planned Completion earlier than the contractual Completion Date. One sits inside the programme logic. The other sits at the end of it.

How TRA and terminal float connect without being the same

This is the part people often miss. TRA can influence terminal float over time, but that does not make them identical. NEC’s recent guidance explains that where a critical path activity finishes earlier than planned because the risk never materialised, the next update may bring planned Completion forward. When that happens, unused TRA can effectively turn into more terminal float.

That is a useful contractor point. Unused TRA may become terminal float through the update cycle, but that is the result of progress and revision, not proof that the two concepts were interchangeable all along. They start life in different places and serve different functions.

Why the distinction matters for contractors

First, it matters for programme acceptance. NEC requires float and time risk allowance to be shown, and NEC says the Project Manager can reject a programme where they are missing or where all the allowance is parked at the end. If TRA is confused with terminal float, the programme is easier to attack as unrealistic or non-compliant.

Second, it matters for compensation events. TRA is part of the contractor’s own risk allowance within the programme, whereas terminal float sits in the relationship between planned Completion and the Completion Date. If those are blurred, the baseline for time entitlement becomes weaker.

Third, it matters commercially because incentives are different. NEC’s recent note says contractors may have an incentive to show fewer time risk allowances on critical path operations because doing so can bring planned Completion forward and increase terminal float. That is exactly why the allowance shown still needs to be reasonable and defensible.

What good practice looks like

A good NEC programme keeps the distinction clean. TRA should be shown where the contractor-risk exposure actually sits. Terminal float should remain what it is: the gap between planned Completion and the Completion Date. The narrative should not merge the two, and the update cycle should make clear when unused TRA has fallen away and genuinely improved the forecast.

Where that discipline is weak, the problems usually show up as programme acceptance comments, blurred update logic and avoidable friction on change. If that is happening on a live job, our NEC Programme Compliance service helps contractors tighten programme logic, submission quality and alignment between the programme and its narrative.

Public commentary and adjudication-related guidance

There is no widely cited public NEC judgment focused purely on whether Time Risk Allowance is the same as terminal float. But the public guidance is still clear. Fenwick Elliott notes that float and TRA are different concepts, while Ashfords, in an article originally published on the NEC-

Adjudicators website, explains that terminal float under NEC is treated separately and can protect the contractor where planned Completion sits earlier than the contractual Completion Date.

NEC’s own guidance also makes clear that unused TRA can bring planned Completion forward and increase terminal float, which reinforces the point that the two are connected but not interchangeable.

Simple example: why TRA is not terminal float

Assume the accepted programme shows planned Completion on 1 October and the contractual Completion Date on 15 October. That 14-day gap is terminal float. Now assume a critical commissioning activity includes 3 days of Time Risk Allowance because normal contractor-risk uncertainty is expected. That 3-day allowance is not terminal float. It sits inside the activity logic. If the risk never materialises and the next accepted update brings planned Completion forward to 28 September, the contractor may now have 17 days of terminal float. The unused TRA has helped create more terminal float through the update cycle, but it was not terminal float to begin with.

That example aligns well with NEC’s own explanation that unused time risk allowance can bring planned Completion forward and thereby increase terminal float.

Conclusion

So, is TRA the same as terminal float? No. TRA is identified allowance for contractor-risk events within the programme logic. Terminal float is the time between planned Completion and the contractual Completion Date. One may become the other through updating if risk does not materialise, but they are not the same concept and should not be managed as if they are.

For contractors, that is not just technical wording. It affects whether the programme is accepted, whether the update cycle looks credible and whether later change discussions start from a clean and defensible baseline.

FAQ

Can unused TRA become terminal float?

Yes, it can through the update process. If a risk allowed for within an activity does not occur and planned Completion moves earlier in the next accepted programme, the contractor may end up with more terminal float. That does not mean TRA and terminal float are the same thing. It means one can lead to more of the other through realistic updating.

Can a Project Manager reject a programme that treats terminal float as Time Risk Allowance?

Yes. NEC requires the programme to show float and time risk allowances, and NEC’s guidance says a programme may be rejected if it does not show reasonable TRA or if the allowance is pushed to the end of the programme in a way that is not logical and misrepresents the contractor’s plan.

Does terminal float belong to the contractor under NEC?

Generally, yes. NEC guidance and commentary treat terminal float, meaning the gap between planned Completion and the Completion Date, as contractor-owned. That is different from activity-level TRA sitting within the programme logic.

Should Time Risk Allowance be shown within activities or as a separate block at the end?

It should be tied to the activities or parts of the works where the contractor-risk exposure actually sits. NEC guidance says putting TRA in one block at the end is not a logical approach, while Fenwick Elliott describes TRA as specifically identified time risk added into the programme.

---

Need stronger programme control on a live project?

If you need clearer programmes or contract-aligned planning support, start with a practical discussion about your project.