A task is considered “critical path” in gantterAi if:
It has zero total float (slack):
Total float is the amount of time you can delay a task without delaying the project’s finish date.
If a task can’t slip even one day without pushing the whole project end date out, Gantter marks it as critical.
It directly or indirectly drives the project’s finish date:
Even if a task doesn’t have successors, if it’s sitting at the “end of the chain” that determines the project finish, it’s on the critical path.
For example: if line 14 is the last task finishing on the same day as the overall project, gantterAi will highlight it as critical because any delay there is a delay to the project finish.
Dependencies don’t always matter:
A task doesn’t have to feed into another task to be critical.
If it’s scheduled so tightly that the project end date depends on it, gantterAi flags it.
Why your example task might show as critical even without successors:
The task ends on the same date as the project finish.
There’s no slack built in, so delaying it pushes the project end.
GantterAi still considers that “critical,” even though it doesn’t drive another task.
✅ In short: In gantterAi, a critical task is any task that determines the project finish date by having zero float, whether or not it has successors.