Critical Path
The longest sequence of dependent tasks in a project that determines the earliest possible completion date. Any delay to a critical path task delays the whole project by the same amount. Tasks off the critical path have float - time buffer before their delay affects the end date.
The critical path is the longest unbroken sequence of dependent tasks from the start of a project to its completion. Because every task in the sequence depends on the one before it, a delay anywhere on the critical path pushes the project end date back by the same amount. Tasks on the critical path have zero float - they cannot slip without consequence. Tasks off the critical path have float, meaning they can be delayed by a defined amount before they affect the project end date.
The term comes from the Critical Path Method (CPM), a scheduling technique developed in the late 1950s for large engineering projects. It remains the most practical framework for any project-based business that needs to understand which tasks require active daily management and which have room to absorb small delays without impact.
Identifying the Critical Path on a Project
To identify the critical path, list every task in the project and note which tasks depend on others being complete before they can start. Then map the chains of dependent tasks left to right and calculate the total duration of each chain. The longest chain is the critical path.
In a promotional merchandise context, the critical path typically runs through the longest-lead product line in a multi-line order. If a conference kit includes four product lines with lead times of 3, 5, 8, and 12 working days - and proof approval adds 2 days to each - the 12-day line defines the critical path. Delaying proof approval on that line by one day delays the entire delivery, even if the other three lines are ahead of schedule.
In construction, the critical path runs through structural and sequencing-dependent trades. Electrical second fix and joinery installation cannot start until walls and ceilings are in place. A one-week delay to structural completions does not only affect that trade - it pushes everything downstream, including programme dates that are contractually committed.
You do not need scheduling software to identify the critical path on most SMB projects. Draw a simple dependency list
which tasks cannot start until another is complete? Map them left to right. The longest connected chain is your critical path. Review it at every project update and actively manage any task with zero float.
Managing Float and Prioritizing the Right Tasks
Float is the amount of time a non-critical task can slip before it joins the critical path. A task with five days of float is not urgent today. A task with zero float needs attention every day until it is complete.
The most common critical path failure in SMB project businesses is treating every task as equal urgency. When everything is flagged as high priority, teams cannot direct effort where delay actually matters. Tracking float alongside the critical path creates a clear picture: tasks with zero float get managed actively, tasks with healthy float get monitored.
On a promotional merchandise multi-line order, this means checking in first with the supplier whose lead time defines the delivery date - not just chasing in the order the POs were raised. On a construction project, it means the site supervisor flags structural programme risk to the contracts manager before it cascades into a programme overrun claim.
Zigaflow's project tracking gives job-level visibility into milestone status across active orders and projects. Linking purchase orders and works orders to specific job milestones means that a delayed supplier delivery on a critical path item surfaces as a visible risk rather than quietly absorbing days of float before anyone notices.
Common in
Frequently asked questions
Ready to put this into
practice?
Book a free demo and see how Zigaflow fits your team.