· 3 min read
Why is an activity marked as delayed?
"Delayed" is computed automatically from today's date vs. the planned end date — not a status anyone sets by hand.
“Delayed” isn't a status you or anyone else sets. It's computed automatically: an activity shows a “Delayed” badge whenever today's date is past its planned end date and it isn't marked completed. As soon as it's completed, or its planned end date is pushed out, the badge goes away on its own.
This is a separate flag layered on top of an activity's normal status (Not started, In progress, Completed) — an activity can be “In progress” and “Delayed” at the same time, and that combination is exactly what it looks like: work that's happening, later than planned.
Variance against a baseline
Delayed status only compares an activity to its own planned end date. If you've saved a baseline and selected it under “Compare against,” you get a fuller picture: a summary of how many activities have Slipped, are still On baseline, have been Pulled in (moved earlier), plus the Worst slip in days and a list of the biggest individual slips. See how to save a baseline if you haven't yet.
Critical path
On the Gantt chart, activities on the critical path — the chain with zero slack, where any delay pushes the whole project's end date — get a distinct outline, with a tooltip that reads “Critical path — zero slack” on hover.
Was this article helpful?