Critical Path on the Gantt: Which Tasks Can't Slip

What is the critical path on a construction schedule?

The critical path is the longest unbroken chain of dependent tasks in your construction schedule — and it is the single sequence that controls when the project ends. Every task on the critical path has zero float: if it slips by one day, the project finishes one day late. Tasks that are not on the critical path have float — some slack before they affect the end date — but tasks on it have none. Understanding which tasks sit on this chain changes how a contractor prioritises resources, responds to delays, and communicates timelines to the owner. A schedule with twenty tasks does not mean twenty things can go wrong equally — a handful of tasks are driving the project end date, and the rest have room to move.

Why does the critical path matter for Thai contractors?

Thai residential and commercial construction schedules are often tighter than they look. A 90-day renovation or a 12-month build packs in structural, waterproofing, MEP, and finishing work — all with inter-dependencies that are easy to lose track of on a plain list or a basic Excel table. When a contractor knows the critical path, every site conversation becomes clearer: a steel subcontractor asking for three extra days is a very different problem depending on whether the frame is on the critical path or has a week of float. Without that information, the contractor either panics unnecessarily or misses a real threat. With it, they can redirect resources the moment a slip is detected — before the end date moves.

How do you find the critical path on a Gantt chart?

The practical method is to trace forward from your project start through all task dependencies until you reach the final task. At each junction — where one task depends on another finishing first — follow the longest chain. The tasks in that chain, from the first day to the last, form the critical path. In SiteBoard's Gantt planning view, you can set task dependencies so each task knows what it is waiting for. Once those links are in place, the longest chain of dependent tasks becomes visible: it is the route from project start to project end where every task sits end-to-end with no gap between them. Scanning the dependency links on the Gantt tells you which chain is the critical path without any complex calculation.

Which construction tasks are almost always on the critical path?

Foundation work sits on the critical path in nearly every project — nothing can build above it, and delays cascade everywhere. For above-ground structure, concrete frame and slab pours are critical because finishing trades cannot start until the structure is weather-tight. MEP rough-in — the first pass of electrical conduit, plumbing pipe, and air-conditioning duct — is critical when it must be completed before walls are plastered. Government statutory inspections, such as the structural frame sign-off or electrical rough-in certification, sit on the critical path when their approval gates a payment milestone. Finishing trades like tiling and joinery often have float because they can be done room by room, but the final handover inspection is always on the critical path: it is the last task before the project ends.

What is float, and how do contractors use it?

Float is the number of days a task can be delayed before it pushes the project end date. A task with three days of float can slip three days without affecting anything downstream. Knowing the float of each task allows a contractor to make resource decisions that would otherwise be guesswork. If the roofing subcontractor and the concrete frame team both need labour at the same time, and the frame is on the critical path while the roof has two days of float, the answer is clear: protect the frame crew first. Without float information, site managers tend to react to whoever shouts loudest rather than whoever matters most to the project timeline. Float turns a reactive site into a managed one.

A worked example: critical path on a three-storey house in Nonthaburi

Khun Ratchanee is building a three-storey family home in Nonthaburi for a 4.5-million-baht contract over 28 weeks. Her Gantt has four chains of work: groundwork and foundation (weeks 1–4), concrete frame (weeks 3–12), MEP rough-in (weeks 8–16), and finishes including tiling, joinery, and painting (weeks 14–26). The longest chain — running from pile driving all the way through to the final paint coat — is the critical path. At week nine, the concrete frame subcontractor falls four days behind because formwork arrives late. Because Khun Ratchanee has task dependencies set in SiteBoard's Gantt planning view, she sees immediately that MEP rough-in cannot start on its planned date. She negotiates a partial overlap: the MEP team starts on the completed lower floors while the frame continues above, recovering two of the four lost days and keeping the handover date intact.

What should you do when a critical path task slips?

The moment a critical path task falls behind, the response must be immediate and specific. First, confirm the slip is real — not just a conservative estimate from the foreman — by checking the on-site update in SiteBoard against the planned percentage for that day. Second, calculate how many days have been lost and whether the next task has float that can absorb them. Third, choose a recovery action: adding resources, approving overtime, allowing a partial overlap between tasks, or splitting scope across two crews. Fourth, update the Gantt so the whole team sees the revised timeline — never carry the slip in your head while the schedule shows the original plan. The owner sharing link updates automatically, so the owner sees the revised dates without a separate call.

Can every task on a project end up on the critical path?

In theory, a schedule could be drawn so tightly that every task has zero float. In practice this almost never happens, and it would be unmanageable if it did. Most construction projects have two or three chains of work — structure, MEP, and finishes — that converge at the final handover. Only the longest of those chains is the critical path; the others have float equal to the difference between their duration and the longest chain. Worth watching closely: tasks that are nearly critical — with just one or two days of float — can shift onto the critical path without warning. A heavy-rain afternoon that stops the crew early can turn a comfortable two-day buffer into zero by the time everyone packs up, making it a genuine emergency by morning.

What is the difference between the critical path and a milestone?

A milestone is a single point in time on the schedule — a decision, an inspection, or a payment event — with zero duration. The critical path is the chain of tasks and milestones whose combined duration equals the total project duration. A milestone can sit on the critical path, such as a structural inspection that must pass before finishing trades begin, or off it, such as an internal review meeting that no task is waiting on. When a critical-path milestone slips, the project end date moves. When a non-critical milestone slips but still completes before the next dependent task needs it, nothing downstream changes. Knowing which milestones are on the critical path tells a contractor which ones need advance booking and which ones have room to flex.

How often should you review the critical path on a live project?

A weekly review is the practical standard for most Thai SME construction projects. At the site meeting or on a Monday morning, check whether the tasks that were on the critical path last week are still on track, whether any near-critical tasks have drifted onto the path, and whether recovery actions from the previous week produced results. SiteBoard's Gantt planning view shows plan versus actual progress on every task, making this a five-minute scan rather than a manual recalculation. For projects shorter than eight weeks, a twice-weekly review is worthwhile because a single slipping task can affect the end date within days rather than within a planning cycle. The goal is to catch critical-path slippage while there is still time to act — usually within two or three days of the first sign of delay.