What Is the Critical Path?
The critical path is the longest chain of dependent tasks running through a construction program, and it sets the shortest possible time the whole project can take to build. Every task on the critical path must finish on time for the project to finish on time — delay any one of them and practical completion slips by the same number of days. Tasks that sit off the critical path usually carry some spare time, called float, so they can move a little without changing the finish date.
Key takeaways
- The critical path is the longest sequence of dependent tasks in the program — it sets the minimum time the project can take to build.
- A delay to any task on the critical path pushes out practical completion by the same number of days, because there is no float to absorb it.
- Tasks off the critical path carry float — spare time they can use without changing the project’s finish date.
- The critical path is calculated from task durations and dependencies, usually inside scheduling software, and it can shift as the program is updated.
- Knowing the critical path is essential to assessing delay claims and extensions of time, since it shows which delays actually affect the finish date and which do not.
What Is the Critical Path?
The critical path is found by mapping every activity in the construction program, along with its duration and what it depends on, and then tracing the longest chain of dependent tasks from start to practical completion. Whatever that longest chain adds up to is the shortest possible duration of the whole project.
Because the tasks on the critical path have no spare time between them, they are described as having zero float — any slip in one of them flows straight through to the project finish date, with nothing else in the program able to absorb it.
Critical Path vs Float
Float — sometimes called slack — is the amount of time a task can be delayed or extended without pushing out the project finish date. Tasks with zero float sit on the critical path; tasks with float do not, even though they still matter to the overall program.
- Critical path tasks — zero float, delay flows straight through to the finish date.
- Near-critical tasks — a small amount of float that can be used up if the program slips.
- Non-critical tasks — meaningful float, some room to run late without affecting completion.
| Task | Duration | Depends on | Float | On critical path? |
|---|---|---|---|---|
| Site works & footings | 15 days | — | 0 days | Yes |
| Frame & roof | 20 days | Site works & footings | 0 days | Yes |
| Fix-out & linings | 18 days | Frame & roof | 0 days | Yes |
| Landscaping | 10 days | Site works & footings | 25 days | No |
Why the Critical Path Matters for Delay Claims
The critical path is the test used to work out whether a delay actually affects the project finish date. A delay to a critical path task pushes out completion and can support a claim for an extension of time and associated prolongation costs. A delay to a task with float, absorbed within its float, usually does neither.
In plain terms
Not every delay is a real delay to the project — only a delay that eats into the critical path (or removes enough float to make another task critical) actually pushes out the finish date.
Managing the Critical Path During Construction
The critical path is not fixed for the life of the project — as tasks finish early, run late, or the program is revised, the chain of zero-float tasks can shift to a different sequence of activities entirely. Experienced site managers track the current critical path continuously, not just at the start.
- Recalculate the critical path whenever the program is updated, not only when something goes wrong.
- Prioritise resources and problem-solving on whatever is currently critical, not whatever feels most urgent.
- Watch near-critical tasks closely — a small slip can make them the new critical path.
How My Trade Hub Helps
My Trade Hub does not replace your scheduling software, but the priced Bill of Quantities it produces is one of the first real inputs your program needs — you cannot sequence and duration trades accurately until the scope and quantities are settled.
Because the estimation engine automates the quantity takeoff and applies your rates library automatically, it turns a priced BOQ around fast — commonly 60 to 75 per cent faster than doing it manually — leaving more time before the tender deadline to build a proper program and work out the critical path, instead of guessing at durations under time pressure.
Frequently asked questions
What is the difference between critical path and float?
The critical path is the chain of tasks with zero float — any delay to them delays the whole project. Float is the spare time a task off the critical path can use without affecting the finish date. Every task on the critical path has zero float by definition.
What happens if a critical path task is delayed?
The project finish date moves back by the same number of days as the delay, because there is no float on the critical path to absorb it — unless the delay can be recovered elsewhere in the program, such as by compressing a later activity.
How do you find the critical path in a construction program?
You map every activity, its duration and its dependencies, then trace every possible path from start to finish through the program. The path with the longest total duration is the critical path, and any task on it has zero float.
Does every project have a critical path?
Yes. Every program with at least one sequence of dependent tasks has a critical path, even a very simple one — it is simply the longest route through the work, whether that is obvious or not.
Can the critical path change during construction?
Yes. As tasks run ahead of or behind schedule, or as the program is revised, float can be used up on one chain of tasks and created on another, shifting which activities are currently critical.
Ready to win more work?
Turn your plans into professional tenders 60–75% faster with My Trade Hub. Plans built around your tendering volume — no lock-in contracts.
Get started free