Float isn’t contingency.

This is one of the most expensive misunderstandings in project controls.

And I’ve seen it cost programs months.

Here’s the difference:

Float is the time an activity can be delayed before it affects the critical path.

It belongs to the program.

It exists because of how the schedule logic is structured.

Contingency is a buffer you deliberately allocate to absorb risk.

It is planned. Intentional. Owned.

When a team treats float as contingency – they start consuming it.

“We have 15 days of float on this package, we can afford to slip.”

And they’re right.

Until three other activities also consume their float.

And suddenly there’s no buffer left anywhere.

And the critical path just shifted to something nobody was watching.

The schedule didn’t lie.

The team just misread what the float was telling them.

Float is information.

Contingency is protection.

They are not the same thing.

The moment you start spending float like it’s a budget line, you’ve lost control of the schedule.

The best project controls teams I’ve worked with treat every day of float as early warning data, not permission to slip.

How does your team handle float? As a buffer or as a signal?