Home › Study guides › Critical path, float, crashing, fast tracking
Critical Path and Float Explained Simply (PMP Examples)
The critical path is the longest path through the schedule; its activities have zero float, so any delay on it delays the project.
In simple words
The critical path is the longest chain of tasks. If anything on it is late, the whole project is late. Tasks off that path have spare time, called float. To finish sooner, add people (costs money) or overlap tasks (adds risk).
What the PMP exam wants
The PM defines activities, sequences them, estimates durations, and builds the schedule. The approved version is the schedule baseline. Float (slack) is how long an activity can slip without delaying the project end. Critical path activities have zero float.
A near-critical path has very little float and can become critical. To shorten a schedule: crashing adds resources (costs money); fast tracking overlaps activities that were planned in sequence (adds risk).
How to find the critical path: a simple example
Four activities, with durations in days. A must finish before B and C start. D starts when both B and C are finished.
| Activity | Duration | Comes after |
|---|---|---|
| A | 3 | (start) |
| B | 4 | A |
| C | 2 | A |
| D | 2 | B and C |
There are two paths. A–B–D = 3 + 4 + 2 = 9 days. A–C–D = 3 + 2 + 2 = 7 days. The longest path is A–B–D, so it is the critical path, and the project takes 9 days. A, B and D have zero float.
How to calculate float
Total float is how long an activity can be delayed without delaying the project end date. The simple way: length of the critical path − length of the activity's longest path. Here C has 9 − 7 = 2 days of float.
The exam may also use the forward and backward pass (this example counts from day 0):
| Activity | Early start | Early finish | Late start | Late finish | Float (LS − ES) |
|---|---|---|---|---|---|
| A | 0 | 3 | 0 | 3 | 0 |
| B | 3 | 7 | 3 | 7 | 0 |
| C | 3 | 5 | 5 | 7 | 2 |
| D | 7 | 9 | 7 | 9 | 0 |
Forward pass: early finish = early start + duration. Backward pass: late start = late finish − duration. Float = late start − early start (or late finish − early finish).
Total float vs free float
Total float protects the project end date. Free float protects the next activity: it is how long an activity can slip without delaying the early start of its successor. Free float of C = early start of D − early finish of C = 7 − 5 = 2 days.
What happens when an activity is delayed?
- On the critical path: every day of delay moves the project end date, unless you recover the time with crashing or fast tracking.
- Off the critical path, delay smaller than the float: the end date does not move, but the float on that path gets smaller.
- Off the critical path, delay larger than the float: the project is late by (delay − float), and that path becomes the new critical path. In the example, if C is 3 days late, the project is 3 − 2 = 1 day late.
Negative float
Negative float means the schedule cannot meet a required date. If the customer requires the work on day 8 but the critical path needs 9 days, the float is −1. The project manager must compress the schedule, change the plan or negotiate the date.
Near-critical paths
A path with very little float (A–C–D has only 2 days) is near-critical. A small problem can make it critical, so it deserves attention too. A schedule can also have more than one critical path, which means more schedule risk.
Shortening the schedule: crashing vs fast tracking
| Crashing | Fast tracking | |
|---|---|---|
| What you do | Add resources to critical path activities | Do activities in parallel that were planned in sequence |
| Main cost | More money | More risk and possible rework |
| Use it on | Critical path activities where more resources really shorten the work | Activities that can overlap (often finish-to-start links that are not mandatory) |
Only work on the critical path shortens the project. Adding people to an activity that has float does not change the end date.
Real example
Robot delivery (8 weeks) → installation → programming → FAT is the longest chain, so it's critical. Guard fabrication has 2 weeks of float: a 1-week delay there doesn't move FAT, but a robot arriving 1 week late does.
The common trap
A delay smaller than an activity's float does not delay the project. Adding people to an activity that isn't on the critical path doesn't shorten the project.
Remember: Critical = no cushion. Crash costs money; fast track costs risk.
🗝 Words to notice in the question
“float”, “slack”, “critical path”, “delayed X days” → compare delay with float
Try 3 practice questions
Choose an answer, or open “Show the answer.”
Question 1 An activity with 3 days of float is delayed by 2 days. What happens to the project end date?
Show the answer
Answer: C. The delay is within float, so the end date holds; 3 − 2 = 1 day of float remains, so the path is now near-critical.
Question 2 The schedule must be shortened without adding cost. Which technique fits?
Show the answer
Answer: B. Fast tracking overlaps work; it adds risk but not direct cost. Crashing adds cost.
Question 3 Path A–B–D takes 12 days and path A–C–D takes 10 days. Activity C is delayed by 3 days. What happens to the project?
Show the answer
Answer: C. C had 2 days of float (12 − 10). A 3-day delay uses the 2 days of float and adds 1 day: A–C–D now takes 13 days, so it becomes the new critical path and the project is 1 day late.
The free demo has this chapter with the key words, the PMP rule and every wrong answer explained. No sign-up, no card.
Open the free chapter → Practice more PMP questionsLearn more in PMCLEAR lessons
- Free lesson: Critical path and float
- Lesson: Dependencies, leads and lags
- Lesson: Crashing and fast tracking
- Study guide: Resource leveling vs resource smoothing