The critical path is the longest path through the network. It sets the shortest time the project can take if the logic and durations are true. Everything else has float — until you spend that float, at which point you have grown a second critical path and a surprised sponsor.
Longest path, not 'the important tasks'
Forward pass: earliest start and finish for each activity. Backward pass: latest start and finish. The path whose total duration is longest — typically the chain with zero total float — is critical. Miss a day there and the end date moves, unless you change logic, scope, or resources.
Critical does not mean valuable or difficult. The procurement wait can be critical while a technically heroic module sits on a side path with two weeks of float. Stakeholders will argue with this. Show the network. Importance is a value conversation. Criticality is arithmetic. Mixing them is how you crash the interesting work and still miss the date.
Near-critical paths matter. A path with two days of float is a week away from joining the crisis if anything sneezes. Watch the top two or three paths, not only the red bar the tool highlighted. Multiple critical paths are common once you stop pretending the plan is a single story.
Total float versus free float
Total float is how long an activity can slip without delaying the project end date. It is shared along a path. If three activities each appear to have ten days of total float, that is often the same ten days. The first one to use it spends it for the others. Treating total float as a personal slush fund is how 'we had float' becomes 'how are we late?'
Free float is how long an activity can slip without delaying the early start of its immediate successor. It is local. Free float is the safer place to park a small delay or a resource dip, because you are not borrowing from the rest of the chain. If you have neither, you are on or next to the critical path whether the colour coding has caught up or not.
Negative float means the imposed date and the network already disagree. The tool is telling you the promise is false. Do not 'solve' it by deleting logic or shrinking estimates until the bar turns green. That is a graphics exercise. Solve it with scope, sequence, resources, or a different date — in change control, not in a quiet edit.
Why crashing the wrong task wastes money
Compression only moves the end date if it shortens the current critical path. Adding people to a task with float makes that bar shorter and your invoice longer. The project finish does not notice. You have purchased a tidier Gantt chart.
Even on the critical path, not every task crashes well. Some work does not divide. Nine people cannot make a baby in a month, and nine developers cannot always make a module in a ninth of the time. Coordination cost, ramp-up, and specialism eat the theory. Estimate the crash cost and the days actually returned before you spend.
After you crash, recompute. The path you shortened may hand the crown to a sibling path. The second cheque is often waiting there. This is why 'we added two people to the integration' can coincide with no movement on the milestone. The network moved the bottleneck. Nobody updated the story they tell in steerco.
Summary & next steps
The critical path is the longest path and sets the minimum duration. Total float is shared and easy to spend twice; free float is local. Negative float is a broken promise, not a formatting error. Only shortening the current critical path can move the end date — and it may create a new one.
Next: resource leveling — what to do when the network is elegant and the same three people are booked at 160 percent.