How to Track Progress on a Gantt Chart
A Gantt chart built once and never touched is not a plan, it is a wish. The value of a schedule is not in drawing it, it is in comparing it to reality week after week and acting on the gap. Tracking is the discipline that turns a pretty chart into an early-warning system: it tells you a project is slipping while there is still time to do something, instead of at the deadline when there is not. This guide covers how to track progress properly, the signals that actually mean something, the ones that lie to you, and how to read trouble before it becomes a surprise.
Why a plan you do not track is just a guess
Every project plan is a forecast made at the moment you know least about the work. It starts going out of date the day it is approved. Tracking is how you keep it honest: you record what has actually happened, lay it against what you planned, and let the difference tell you whether the finish date is still real.
Teams that skip this do not find out they are late until the deadline arrives, because a plan with no actuals cannot warn anyone. Teams that track well see the slip building for weeks and get to choose how to respond. The chart does not change your luck, it changes how early you know.
Percent complete: the basic signal, and its trap
The most common way to show progress is to fill each bar to the fraction of the task that is done: a task half finished gets a bar shaded halfway. It is simple and it reads at a glance. It also lies more often than any other number on the chart.
The trap is that "percent complete" usually means "percent of time elapsed", not "percent of work done". A task scheduled for ten days, on day five, gets marked 50% because five days have passed, whether or not half the work exists. That is not progress, it is a calendar. The fix is to insist on physical percent complete: what fraction of the actual deliverable is finished, judged by the work, not the clock.
The status date: where you read progress
Every tracking update happens as of a date, the status date, often drawn as a vertical "today" line on the chart. It is the single most useful mark you can add, because it turns the whole picture into a test: any bar whose fill has not reached the status line is behind, and any bar filled past it is ahead.
Without a status date, "the project is going fine" is an opinion. With one, it is something you can see: the line either cuts through solid, completed bars or it cuts through empty ones, and the difference is your status.
Planned vs actual: the honest comparison
Percent complete tells you how far a task has come; it does not tell you whether that is good enough. For that you need a baseline: a frozen copy of the original plan to compare against. Tracking then becomes a comparison of two things, where the task was supposed to be by now, and where it actually is.
A task can be 60% complete and perfectly on track, or 60% complete and badly behind, and only the baseline tells you which. The gap between planned and actual is called variance, and it is the number that actually deserves a manager's attention.
Spotting slippage early
The point of tracking is to catch a slip while it is small. A few habits make that reliable:
- Watch tasks that should have started but have not, a late start is the earliest possible warning.
- Watch tasks stuck at the same percent complete two updates in a row, they are quietly stalled.
- Distrust any task that jumps from 10% to 90% in one update, someone is guessing.
- Treat "90% done" that stays 90% for weeks as the classic sign of a task in trouble.
A worked example: elapsed time is not progress
- Read as time elapsed, 6 of 10 days, that is exactly on plan. Green.
- But ask the writer: only 3 of 10 sections are drafted. Physical progress is 30%, not 60%. The task is four days of work behind, hidden behind a number that tracked the calendar instead of the work.
Time-based vs physical percent complete
| Time-based % | Physical % | |
|---|---|---|
| Measures | days elapsed | work actually done |
| Effort to record | none, automatic | a real judgement |
| Honesty | flatters a late task | tells the truth |
| Use for | nothing important | every task that matters |
If your tool fills bars by elapsed time automatically, treat those fills as decoration and override them with a real judgement of the work.
How often to update
Tracking too rarely lets slips hide; tracking too often turns the plan into a full-time job. Match the cadence to the project:
| Project pace | Update cadence |
|---|---|
| Fast, short tasks | daily or twice weekly |
| Typical delivery project | weekly |
| Long, slow-moving work | every two weeks |
Whatever you choose, keep it regular. A status date that jumps around irregularly makes trends impossible to read. Each update, work through the same short routine:
- Move the status date to today.
- For each task in progress, record its physical percent complete, judged by the work done, not the days elapsed.
- Compare every bar's fill against the status line and flag anything that has not reached it.
- Check the critical path first, then the tasks with the least float.
- Read the variance against baseline and decide what, if anything, needs action.
Track the critical path first
Not every slip matters equally. A task with float can run late and hurt nothing; a task on the critical path moves the finish date the moment it slips. When tracking time is short, update the critical path first and in the most detail, that is where a delay is never absorbed.
This also focuses your status reports: leading with the critical path answers the only question most stakeholders have, which is whether the end date still holds.
A worked example: the status line reveals a hidden slip
- The one number that matters: Build is on the critical path and is behind. Test's early start is on a task with float, so it does not help the finish date.
- Action: put attention on Build now, while it is days behind, not weeks.
Reporting progress up
Once you are tracking, reporting almost writes itself. For a stakeholder update, lead with three things the chart already shows: is the finish date still on track, what is the biggest risk, and what you need from them. Summarise to phases and milestones rather than showing every tracked task, and if you keep a baseline, show planned against actual so a slip is visible rather than explained away. The detailed tracked chart stays your working tool; the summary is what goes on the slide. There is more on this in the guide on presenting a Gantt chart to stakeholders.
The short version
A Gantt chart earns its keep only when you track it. Record physical percent complete, not time elapsed; add a status date so slippage is visible; compare against a baseline so you know whether progress is good enough; and update on a regular cadence, watching the critical path most closely. Do that and the chart stops being a decoration and becomes what it was meant to be, an early warning that buys you time to act. Track your own plan free in the gantts.app editor.
Templates that use this
Keep reading
- Baseline vs Actual: Tracking Schedule Variance on a Gantt Chart
- Critical Path Method (CPM): Steps, Formula & Example
- How to Present a Gantt Chart to Stakeholders
Frequently asked questions
How do you track progress on a Gantt chart?
Fill each task bar to its percent complete, add a status date (a vertical "today" line), and compare progress against a baseline of the original plan. Bars not filled up to the status line are behind; the gap between planned and actual is the variance worth acting on.
What is a status date on a Gantt chart?
The status date is the point in time an update reflects, usually drawn as a vertical line on the chart. It lets you read progress at a glance: any bar not filled up to the line is behind schedule, and any filled past it is ahead.
What does percent complete mean on a Gantt chart?
It is the fraction of a task that is finished, shown by how far its bar is shaded. The honest version is physical percent complete (how much of the work is actually done). Beware tools that fill bars by time elapsed, which flatters a late task.
Why is my task 90% complete for weeks?
A task stuck at 90% is the classic sign of trouble: the easy part is done and the hard remainder was underestimated. Track physical progress rather than time elapsed, and treat a percent complete that stops moving as a warning to investigate.
How often should I update a Gantt chart?
Match the cadence to the project: daily or twice weekly for fast work, weekly for a typical delivery project, every two weeks for slow-moving work. Keep it regular so trends stay readable, and always update the critical path in the most detail.