A Gantt chart can look completely normal and still be lying to you — bars in the right rows, colors in the right places, dates that seem plausible. The only way to tell a calculated schedule from a decorated drawing is to check whether it behaves like a calculation when something changes. Here are seven quick signs yours is lying.
1. Dragging a Bar Doesn't Move Anything Else
Drag any task's start date two weeks later. In a real schedule, every task linked to it — and everything chained after those — shifts automatically, because the link is a constraint the engine enforces. If nothing downstream reacts, the arrows on your chart are decoration, not dependencies, and the dates around them were never really connected in the first place.
2. Two People Show Green on the Same Overbooked Day
Open two different projects that share a team member and check the same date in both. If each project shows that person cheerfully "on schedule" while their combined workload for the day adds up to sixteen hours, the schedule isn't tracking capacity at all — it's tracking intentions, one project at a time, with no idea what else that person is committed to.
3. No One Can Name the Task Driving the Finish Date
Ask your scheduling tool — not a person, the tool — which task is on the critical path today. If it can't answer instantly with a specific chain of tasks, no critical path has actually been calculated. Whatever task "feels" urgent in the next status meeting may have nothing to do with the task that actually controls when the project finishes.
4. "On Track" Is an Opinion, Not a Comparison
Being on track only means something if there's an original plan to be on track against. Without a saved baseline, the current dates are simply the most recent dates — quietly adjusted over time until they match reality. Ask to see the gap between today's schedule and the plan from three months ago. If there's nothing to show, "on track" was never a measurable claim.
5. The Dates Change Every Status Meeting and No One Can Say Why
In a calculated schedule, a date only moves because something specific changed upstream — a duration, a dependency, a resource conflict — and you can trace exactly what caused it. If your finish date drifts week to week and the honest explanation is "it just needed updating," the schedule is being maintained by hand, not computed.
6. Every Task Looks Equally Urgent
Float is the amount of time a task can slip before it delays the project. A schedule that actually calculates float will show you that some tasks have weeks of breathing room while others have none. If every task on your chart looks equally critical, float was never calculated — which means you have no way to tell which delays are harmless and which ones aren't.
7. The Schedule Was Never Recalculated After the Plan Changed
Scope changes. Someone gets pulled onto another project. A task takes twice as long as planned. In a real schedule, one of those events triggers a full recalculation of every downstream date. If your schedule's response to change is a person manually re-typing a handful of dates, the chart has quietly become a record of what happened — not a plan for what happens next.