Critical Path
The critical path is automatically highlighted in the Gantt chart, showing which tasks directly affect the project's end date.
What is the Critical Path?
The critical path is the longest sequence of dependent tasks that determines the minimum project duration. Tasks on the critical path have zero "float" (slack time) - any delay to these tasks will delay the entire project.
Critical path dependency lines are displayed in red to distinguish them from non-critical dependencies (shown in gray).
Why It Matters
Understanding the critical path helps you:
- Focus resources on tasks that affect the deadline
- Identify risks where delays will impact completion
- Make trade-offs knowing which tasks have flexibility
- Communicate which work is most time-sensitive
Reading the Critical Path
| What You See | What It Means |
|---|---|
| Red dependency lines | These connections form the critical path |
| Gray dependency lines | These tasks have float and won't delay the project if slightly delayed |
Example
In a simple construction sequence:
Foundation (5d) → Framing (10d) → Roofing (5d) → Interior (8d)
↓
Electrical (4d) → Inspection (1d)
If Framing → Roofing → Interior is the longest path, those dependency lines appear red. The Electrical branch has float because it finishes before Interior, so those lines remain gray.
How Float Works
Float (also called slack) is the amount of time a task can be delayed without affecting the project end date.
| Task Type | Float | Meaning |
|---|---|---|
| Critical | 0 days | Any delay extends the project |
| Near-critical | 1-3 days | Small buffer, could become critical |
| Non-critical | 4+ days | Has flexibility for delays |
The critical path is calculated automatically based on task durations and dependencies. You don't need to manually mark tasks as critical.
Multiple Critical Paths
Complex schedules may have multiple critical paths - parallel sequences of tasks that all determine the project end date. If any task on any critical path is delayed, the project will be delayed.
Tips
- Don't ignore non-critical tasks - they can become critical if delayed too long
- Watch for near-critical paths - tasks with minimal float are at risk
- Re-evaluate regularly - the critical path changes as tasks complete or slip
- Use for resource planning - prioritize critical tasks when resources are constrained
Learn More
For more background on critical path methodology, see Critical Path Method on Wikipedia.
Related
- Gantt Chart Overview - Main Gantt chart features
- Dependencies - Creating and managing task dependencies