Critical Path Method in Construction: CPM Logic, Total Float, Free Float and Near-Critical Paths
The Critical Path Method is not simply a red line in a Gantt chart. CPM is a network calculation that determines how activity logic, durations, calendars and constraints combine to produce the earliest and latest feasible dates in a schedule model. Understanding the calculation matters because criticality can change when logic is incomplete, calendars differ, constraints override the network or progress is entered incorrectly. A planner should be able to explain why an activity is critical, how much float remains and which sequence is actually driving the project milestone.
Definition: what CPM is calculating
A CPM schedule represents work as activities connected by logical relationships. Each activity has a duration and usually a calendar. The network calculates when activities can start and finish based on predecessor logic, then calculates how late they can occur without delaying the selected completion point. The longest controlling path through the network typically determines project or milestone completion. In software such as Primavera P6, several settings influence how the calculation is presented, but the underlying idea remains the same: dates are consequences of logic, duration, calendars, status and constraints. A credible schedule therefore needs a credible network before any float value can be trusted.
Understand the four basic relationship types
Finish-to-Start (FS) means the successor cannot start until the predecessor finishes and is the most common relationship for sequential construction work. Start-to-Start (SS) allows activities to overlap once the predecessor starts. Finish-to-Finish (FF) controls completion alignment, while Start-to-Finish (SF) is rare and should be used cautiously. Leads and lags change the separation between activities. A lag can be legitimate, such as curing time, but excessive lag often hides real work that should be represented as an activity. Good schedule logic makes physical execution visible rather than burying assumptions inside relationship settings.
Forward pass: calculate Early Start and Early Finish
The forward pass moves from project start toward completion. Conceptually, an activity's Early Start is controlled by the latest applicable predecessor requirement. Early Finish is then Early Start plus the activity duration, adjusted for the working calendar and the scheduling convention used by the software. Where multiple predecessors exist, the controlling predecessor is the one that produces the latest permissible early date. This is why adding one overlooked predecessor can move an entire downstream chain. The forward pass answers: if everything before this activity occurs as soon as logically possible, when can this activity start and finish?
Backward pass: calculate Late Start and Late Finish
The backward pass works from the required completion or milestone date toward the beginning of the network. Late Finish is the latest date an activity can finish without delaying the selected completion point, and Late Start is derived by subtracting the duration through the applicable calendar. Where multiple successors exist, the most restrictive successor condition governs. The backward pass answers: how late can this activity occur before it begins to consume completion flexibility? If constraints force artificial late dates, the backward-pass results may reflect the imposed constraint rather than the natural network, which is why planners must review constraint usage carefully.
Total Float and Free Float are different control signals
Total Float is generally the amount of time an activity can slip before it delays the relevant project or milestone completion, subject to scheduling settings. Conceptually, Total Float can be viewed as Late Start minus Early Start or Late Finish minus Early Finish. Free Float is the time an activity can slip without delaying the early start of its immediate successor. An activity can therefore have positive Total Float but little or zero Free Float. Total Float supports overall completion-risk analysis; Free Float helps understand local handoff flexibility. Negative float indicates that the current network forecast conflicts with a required date or imposed constraint.
Critical path, longest path and near-critical work
Activities with zero or very low float are often called critical, but a fixed threshold alone can be misleading. Modern schedule analysis should also examine the longest path or driving paths to key milestones. Near-critical paths deserve attention because a path with five days of float can become critical after a small delay. For a complex EPC project, management should monitor several key paths: engineering release, long-lead procurement, civil readiness, mechanical completion, energization, commissioning and handover. A single project-level critical path may not explain risks to each contractual milestone.
Calendars, constraints and lags can change float dramatically
Two activities with the same nominal duration can produce different dates if their calendars differ. A seven-day procurement calendar and a six-day site calendar interact differently around weekends and holidays. Hard constraints such as Mandatory Start or Mandatory Finish can sever normal network behavior and should be rare. Other constraints may be contractually justified but still need governance. Long lags can consume or create apparent float without showing the underlying work. When float changes sharply between updates, the planner should determine whether the change came from real progress, changed remaining duration, logic edits, calendar changes or new constraints.
Statusing at the data date changes the network
A schedule update divides the model into actual history and remaining forecast. Actual starts and finishes should reflect verified events, while remaining durations should represent realistic work left. Out-of-sequence progress requires explicit treatment because work may have started before a predecessor was complete. Different scheduling options can retain or override predecessor logic for remaining work. The data date is the reference point for the current forecast, so incorrect actuals or progress after the data date can distort critical paths. A schedule that is logically perfect at baseline can become unreliable if monthly status is poor.
Use float as a management signal, not as a private buffer
Float should be treated as a property of the network, not as spare time secretly owned by one party. Management should examine where float is being consumed, why it is changing and which interfaces are responsible. Float erosion can reveal emerging delay before a milestone becomes late. Trend charts can track Total Float at key milestones, near-critical path count and float consumption by period. The correct response is not always acceleration. Sometimes logic needs correction, a constraint needs removal, or an upstream deliverable needs priority. The schedule should make those choices visible.
Practical CPM health check
A practical review checks open-ended activities, excessive constraints, excessive lags, unrealistic durations, calendar misuse, missing predecessor or successor logic, negative float, high-float outliers, invalid actual dates and unstable critical paths. The planner should be able to trace a key milestone backward through driving relationships and explain the physical sequence in site terms. If the critical path cannot be explained without relying on software color coding, the schedule model is not yet sufficiently understood.
Standards and professional guidance used for this article.
Always apply the governing contract, project specifications, approved procedures and jurisdictional requirements for the actual project.
Move from guidance to governed workflow.
ORQIV publishes practical project-control guidance publicly while keeping customer data, proprietary algorithms and private implementation details inside the governed product boundary. Review methodology is documented in the Editorial Policy.