Critical Path vs Float Path: What's the Difference?

The Short Answer

The critical path is the single longest sequence of dependent activities through a schedule — the path with the least float that determines the project's minimum duration. A float path is any path through the schedule network, ranked by its total float value. The critical path is simply the float path with the lowest float (usually zero).

Put differently: the critical path is one specific float path — the most critical one. Float path analysis looks at all the paths, ranking them from most critical to least critical, giving you a complete picture of schedule risk rather than just the single worst path.

Understanding the Critical Path

The critical path is the foundation of CPM scheduling. It is the sequence of activities that, if delayed, will delay the entire project. Activities on the critical path have zero total float — there is no slack, so any delay to them pushes the completion date directly.

The critical path answers the most important scheduling question: what is the shortest possible time to complete the project? By summing the durations along the longest logical path from start to finish, the critical path defines the minimum project duration given the current logic and durations.

Managing the critical path is essential because it is where delays hurt most. But focusing exclusively on the critical path creates a blind spot — it ignores the paths that are almost critical, which represent the project's next tier of risk.

Understanding Float Paths

Every path through the schedule network has a total float value — the amount of time that path can be delayed before it affects the project completion date. The critical path has the lowest float (typically zero). But there are many other paths, each with progressively more float.

Consider a project with these paths:

• Path 1: 0 days float (the critical path)
• Path 2: 2 days float (near-critical)
• Path 3: 5 days float
• Path 4: 15 days float
• Path 5: 40 days float

Float path analysis ranks all of these. Path 1 is the critical path, but Path 2 with only 2 days of float is nearly as risky — a small delay could make it the new critical path. Path 5 with 40 days of float has substantial cushion and represents low risk.

Understanding total float across all paths reveals the true risk profile of the schedule. A schedule where the second path has 20 days of float is far more robust than one where the second path has only 1 day of float — even if both have the same critical path.

Why the Critical Path Alone Isn't Enough

Relying solely on the critical path creates several risks:

Near-critical paths become critical. When you accelerate the critical path or when it slips, a near-critical path can quietly become the new critical path. If you were only watching the original critical path, you would miss this shift until it manifests as a delay. Float path analysis shows you which paths are poised to become critical.

The critical path shifts over time. As the project progresses and activities complete, the critical path changes. A path that was fifth-most-critical at the start might become the critical path midway through. Monitoring all float paths — not just today's critical path — keeps you ahead of these shifts.

Multiple near-critical paths compound risk. A schedule with one critical path and several near-critical paths converging on the same completion milestone is far riskier than a schedule with a single dominant critical path. Float path analysis reveals this concentration of risk that a critical-path-only view hides.

Resource conflicts hide in near-critical paths. When crews are shared across paths, delays on near-critical paths can cascade in ways that a critical-path-only analysis misses. Seeing all paths helps identify where resource contention creates hidden risk.

How Float Path Analysis Works

Float path analysis systematically identifies and ranks every path through the schedule network by total float. The process assigns each activity to a float path based on its total float value, then groups activities into continuous chains that share the same float value and logical connectivity.

The result is a ranked list: Float Path 1 (the critical path, lowest float), Float Path 2 (next lowest float), Float Path 3, and so on. Each path shows its constituent activities, its total float, and how it connects to the overall network. This lets you see not just the single critical path but the entire risk hierarchy of the schedule.

Primavera P6 does not perform this ranking natively — it identifies the critical path but does not automatically group and rank all secondary paths by float. This is why dedicated analysis tools add so much value. Float Master generates the complete float path ranking automatically from any XER file, giving you the full risk picture in seconds.

Practical Applications

Schedule risk assessment: Before committing to a schedule, examine the float path distribution. Many near-critical paths signal a fragile schedule; a single dominant critical path with well-separated secondary paths signals a robust one.

Acceleration planning: When compressing a schedule, accelerating the critical path only helps until a near-critical path becomes the new constraint. Float path analysis shows you how much you can compress the critical path before the next path takes over — preventing wasted acceleration effort.

Delay analysis: When assessing delay impact through time impact analysis, understanding float paths clarifies whether a delay consumed float on a near-critical path (creating future risk) or directly impacted the critical path (immediate delay).

Resource focus: Float path rankings help prioritize management attention. The critical path and near-critical paths deserve intensive oversight; paths with abundant float can be managed more loosely.

Critical Path vs Float Path: Summary

Critical Path: The single longest path with the least float. Defines minimum project duration. Essential but represents only one dimension of schedule risk.

Float Paths: All paths through the network, ranked by total float. Includes the critical path as the top-ranked path plus all secondary paths. Reveals the complete risk hierarchy and shows where the next risk is hiding.

The relationship is simple: the critical path is the most critical float path. Float path analysis extends critical path analysis by showing you not just the worst path but the ranking of all paths — turning a single data point into a complete risk profile.

Conclusion

The critical path answers "how long will the project take?" Float path analysis answers "where is my risk, and where will it appear next?" Both questions matter. Managing only the critical path leaves you blind to near-critical paths that can become critical with a single delay. Analyzing all float paths gives you the foresight to manage risk proactively rather than reactively.

Modern schedule analysis tools make float path analysis accessible. Rather than manually tracing paths and calculating float across a complex network, Float Master ranks every path automatically from your XER file — giving you the complete risk picture that the critical path alone cannot provide. In construction scheduling, seeing all your paths is the difference between reacting to delays and preventing them.