First, What Is Float?

Float, sometimes called “slack” is the wiggle room in your project schedule. It’s the amount of time a task can be delayed without delaying the overall project completion date. Float exists outside the critical path. That means, if everything runs on time, it won’t be touched. But in the real world, delays happen and that’s when float becomes gold dust.

So, Who Owns It?

It depends. And that’s the problem.

In many cases, contractors assume they own the float after all, they’re responsible for the programme and they’re managing the risks. But employers and contract administrators often argue that float is a shared project resource and should be used to absorb delays on either side whether they’re caused by the contractor or the client.

This isn’t just theoretical. Ownership of float can determine:

• Whether a contractor gets an extension of time

• Whether delay damages are enforceable

• Who takes the hit when things go wrong

What Does the Contract Say?

In some cases, contracts explicitly state who owns the float. Most of the time, they don’t.

Some standard forms (like NEC or JCT) are silent on the issue leaving the question open to interpretation. That’s where disputes can start. Without clarity, employers may assume the float is “for the project,” while contractors believe it’s “theirs to manage.” Cue confusion.

Float on the Critical Path?

Wait, isn’t float always off the critical path? Not quite.

You can get “total float” shared across multiple activities or “free float”, specific to one task. And sometimes, delays to non-critical tasks can impact the critical path, depending on how float is absorbed.

When this happens, ownership becomes even trickier because now the stakes include overall programme completion.

Practical Takeaways

Whether you’re a contractor, client, or consultant, here’s how to stay on top of the float debate:

✅ Clarify ownership in the contract. If it matters (and it does), write it in. Don’t rely on assumptions.

✅ Treat float like money. It’s a limited resource. Use it wisely and track it closely.

✅ Be transparent. If float is being absorbed, flag it early. Don’t wait until the programme slips.

✅ Negotiate before things get messy. If you’re entering a delay dispute and float is part of the discussion, align on
principles before you start arguing about numbers.

Final Word

Float isn’t just a technical detail, it can shape the outcome of a dispute, define programme flexibility and impact financial recovery. Whether it belongs to the contractor, the client or the project as a whole, make sure you know who holds the reins.

Because when push comes to shove, float ownership could be the difference between a smooth handover and a legal battle.

Written by:
XX, Risk & Advisory Lead at Middleton

Supporting better decisions through clarity, accountability, and legal alignment.