Schedule Float and How to Use It

What Float Actually Is

Schedule float is the amount of time an activity can be delayed without delaying the project completion. Activities on the critical path have zero float (any delay pushes the end date). Activities off the critical path have positive float (they can move within a window without affecting the end).

Float exists in every project schedule, even tight ones. The question is whether your team knows where it is, how much there is, and who has the authority to use it.

Why Float Matters More on Multisite Projects

On a single-project build, float is a project management consideration. On a multisite portfolio, it is also a resource allocation tool. When 20 projects are running simultaneously and resources are shared (regional PMs, key trades, equipment vendors), float on one project is what lets you reallocate to a project that needs help.

Multisite operators who do not track float at the portfolio level lose this leverage. They treat each project's schedule as fixed, which means a delay anywhere becomes a delay somewhere else.

Identifying Float in Your Schedules

Float identification requires a properly built schedule with defined dependencies. If your schedule is a list of dates without dependency relationships, float is invisible. The schedule has to be a network, not a calendar.

• Build construction schedules with predecessor and successor relationships, not just start and end dates
• Run critical path analysis to identify zero-float activities
• Document total float for non-critical activities
• Distinguish total float from free float (free float is the amount an activity can move without affecting any other activity)
• Update float weekly as the project progresses; float changes constantly

Using Float Strategically

Most teams burn float reactively. A trade is late, the schedule has float in that area, the float gets consumed, no decision is made. Eventually the float is gone and the next delay hits the critical path.

Strategic float use is different. Float is treated as a resource, like budget contingency. It is allocated deliberately to protect against the risks the team has identified. It is reviewed before being spent. The team knows when float is going to be consumed and has visibility into how much remains.

On a multisite portfolio, float can also be reallocated across projects when resources shift. If a regional PM moves from a project with three weeks of float to one with zero float, both projects' schedules need to be re-evaluated.

Float as Communication

Float numbers are also a communication tool with executives and stakeholders. Saying a project has 10 days of total float on the critical path versus zero days tells a story about risk and intervention urgency.

Leadership reviewing a portfolio of 20 projects can use float as a triage signal. Projects with zero or negative float are at risk and need attention. Projects with healthy float are absorbing normal variance. The numbers focus management attention where it matters rather than turning every status update into a binary on-track or off-track conversation.