Critical Path Float
Let's start with a couple of new terms. A "critical path" is the longest chain of connected tasks in your project — the sequence that decides your project's earliest possible finish date. "Float" (sometimes called "slack") is the amount of time a task can be delayed without pushing back the project's end date.
The rule here is beautifully simple: activities on the critical path have a float of zero. That means there is no wiggle room at all. If a task on the critical path slips by even one day, the whole project finishes one day later.
To read this, remember: float = 0 means "handle with care." Tasks with float greater than zero can absorb small delays without hurting your finish date, but zero-float tasks cannot. A project manager uses this every day to know exactly where to focus attention — you protect and monitor the zero-float tasks most closely, because they directly control when you deliver.
Think of it like a chain of dominoes lined up to reach a finish line by a deadline. The critical-path dominoes are packed edge to edge with no gaps — nudge one and the whole line falls later. The non-critical tasks are dominoes with a bit of space between them, so a small bump gets absorbed before it reaches the end.
Imagine a project with two paths to the finish. Path A (Design → Build → Test) takes 5 + 10 + 5 = 20 days. Path B (Order Materials → Install) takes 4 + 6 = 10 days. The critical path is Path A because it is the longest at 20 days. Every task on Path A has float = 0. If "Build" slips from 10 days to 12 days, the whole project now finishes in 22 days instead of 20. Meanwhile, Path B only needs 10 days but has 20 days available, so its tasks share 10 days of float — they could be delayed up to 10 days without affecting the finish date. That contrast shows why the zero-float tasks are the ones you guard.
Every PMP formula explained free — plus worked examples and practice in PMP Math, and full timed mocks in the simulator.