The Critical Path Method, or CPM, calculates the sequence of activities that controls the finish of a schedule network at the time of analysis. It helps a team distinguish work with little flexibility from work that can move within a limited range. The critical path is not a permanent label: it can change as progress, remaining duration, logic, calendars, and constraints change.
CPM begins with an activity network
Each activity has a duration and logical relationships to other activities. The scheduling calculation evaluates paths through the network from project start to completion. The path controlling the calculated completion date is the critical path. Depending on configuration and constraints, activities on that path commonly have zero or very low total float.
Early and late dates
A forward pass calculates the earliest dates on which activities can start and finish according to the network. A backward pass calculates the latest dates that can be achieved without moving the required completion under the model’s assumptions. The difference between these dates contributes to float calculations.
Float is not simply spare time
Total float describes flexibility relative to a network endpoint, while free float focuses on movement before a direct successor is affected. Its practical use may depend on project procedures and contract terms. It should not automatically be treated as time owned by one party. Using float without coordination can transfer risk to another package or remove protection from a later milestone.
A simple network example
Imagine that approval of a shop drawing releases two work streams. Fabrication and erection of structural steel require 20 days in total, while area preparation requires 8 days. Final installation must wait for both. With no other constraints, the steel path is likely to control. If area preparation later encounters a restriction and its remaining duration increases, the controlling path may shift.
- Do not accept the software’s red bars without checking the logic.
- Review constraints, calendars, and lags that may distort the result.
- Watch near-critical paths because available float can disappear quickly.
- Confirm that actual dates and remaining durations reflect field conditions.
Not every activity delay delays the project
A delayed activity may consume float without changing completion. Conversely, an activity that was non-critical may become critical later. The effect of an event therefore depends on where the affected work sat in the network at the relevant time, how much float existed, what other changes occurred, and whether the team resequenced or mitigated the work.
Use CPM to ask better management questions
CPM is most useful when it prompts questions: Why does this activity control the milestone? Can sequence or resources be changed? Which decision or approval is required first? Where will recovery action move the risk? Software performs the calculation, but useful interpretation still depends on realistic logic, disciplined updates, and knowledge of how the project is actually being delivered.