Float
Float is a project performance measure that turns progress into a number you can track and act on.
Float is the amount of time an activity can slip without delaying the project (also called slack).
As a metric, Float exists to replace opinion with evidence. It converts the messy reality of project progress into a number you can compare across periods, chart as a trend, and act on before a small problem becomes a large one.
A single reading of Float is a snapshot; the trend is the real story. Watching how it moves over successive reporting periods — and understanding what is driving the movement — is what turns the measure into an early-warning system rather than a scorecard.
Float at a glance
- Category
- Scheduling & Time Management
- Type
- Metric / KPI
- Appears in
- 1 section
- Related
- Late Finish, Total Float, Late Start
Why it matters
Float matters because opinion is a poor guide to project health. By turning progress into an objective number, it lets you spot trouble early, compare periods fairly, and make the case for corrective action with evidence rather than gut feel.
It also changes conversations with stakeholders. A number with a trend behind it is far harder to argue with than a subjective "we're roughly on track", so Float tends to shorten debates and speed up decisions.
Finally, Float compounds in value over time. Tracked consistently across a project — and across projects — it builds a baseline of what "normal" looks like, which sharpens future estimates and makes early warnings more reliable.
When to use it
Use Float whenever the size, risk or complexity of the work makes leaving it implicit dangerous. Small, well-understood efforts can treat it lightly; larger, novel or cross-functional projects benefit from handling it deliberately and documenting the result.
Float earns its keep when there is genuine uncertainty or coordination cost — many stakeholders, real money at stake, or a fixed deadline. When the work is trivial or entirely routine, scale it down rather than skipping it entirely: a lightweight version still beats nothing.
Signs you need it:
- You are relying on subjective "gut feel" for project status.
- Stakeholders are surprised by problems late in the project.
- You cannot compare this period’s performance to the last objectively.
- Corrective decisions are being made without evidence.
How to use it
- Establish the baseline the metric is measured against — usually the approved plan or budget.
- Define exactly how you will collect the underlying data, and how often.
- Collect that data consistently and honestly at each reporting point — garbage in, garbage out.
- Apply the formula to compute the metric for the period.
- Interpret the result against agreed thresholds: what is healthy, what is a warning, what demands action.
- Plot the trend, not just the latest value — direction matters more than any single reading.
- Act on it: where the metric signals trouble, investigate the cause and take corrective action.
Common mistakes to avoid
- Reacting to a single data point instead of the trend, and over-correcting.
- Feeding the metric with sloppy or optimistic data, which quietly makes it meaningless.
- Tracking Float but never acting on what it tells you.
- Comparing against a baseline that has drifted, so the number no longer means what you think.
- Gaming the metric — hitting the number while missing the outcome it was meant to protect.
Best practices
- Agree the thresholds and what each one triggers before you start reporting.
- Report Float alongside its trend and a short narrative of what is driving it.
- Protect data quality — the metric is only as good as the numbers behind it.
- Pair it with complementary measures so no single number can mislead you.
- Review and recalibrate the baseline when scope legitimately changes.
Example
Suppose a project reports its Float at the end of a period and the value falls outside the healthy range. Rather than waiting for the trend to worsen, the project manager investigates the cause, takes targeted corrective action, and confirms the metric recovers in the next period — exactly the early-warning role the measure is meant to play.
Now imagine the same project without the metric. The underlying problem still exists, but no number surfaces it, so it is discovered only when a deadline is visibly missed — far later and far more expensively. That gap is precisely the value Float adds.
Template
A simple Float template or checklist keeps the output consistent from project to project and makes it faster to produce and easier to review.