What is a Gantt chart?
A Gantt chart is a project drawn as time. Down the left side, the list of tasks; across the top, the days or weeks; and in the grid between them, a horizontal bar for each task showing when it begins and ends. Arrows between bars show dependencies: the edit cannot start until the shoot wraps, the shoot cannot happen until casting is done. Milestones appear as diamonds, today is a vertical line, and a glance at the chart tells you what is late, what is next and how much of the project is left.
The chart is a century old and still the standard view in project management software, because it answers the question every stakeholder asks first: when. For a creative project it maps the sequence from brief to delivery, pre-production, shoot, edit, review rounds, finishing, and it makes the consequences of a change visible: move the shoot by a week and the chart shows the delivery moving with it, which is a far more persuasive argument than an email saying so.
Why it matters
Why a Gantt chart matters
A project is a chain of commitments, and most problems come from one link slipping without anyone noticing what it pulls. The Gantt chart makes the chain visible. The producer sees that the client review falls on a holiday, the editor sees that the grade is scheduled before the final cut is locked, the client sees that their three-day approval window is the only thing standing between the film and the launch date. Problems found on the chart are cheap; the same problems found on the day are not.
It is also the clearest way to communicate a plan. A schedule as a list of dates is read and forgotten; a schedule as a chart is understood in seconds by people who have never managed a project, including clients, who tend to become far more reasonable about deadlines once they can see what their late feedback does to the bar at the end.
In practice
How a Gantt chart works in practice
- 01
The project manager breaks the work into tasks, estimates how long each takes, identifies which depend on which and assigns owners. The chart is then built, almost always in project management software rather than by hand, with the dependencies linked so that moving one task moves the ones downstream. The critical path, the sequence of dependent tasks that determines the earliest possible finish, is identified and watched, because any delay on it delays the whole project and delays elsewhere may not matter at all.
- 02
During the project the chart is kept current: tasks are marked complete, dates are adjusted as reality intervenes and the plan is re-read weekly with the team. Different audiences get different levels: the team sees every task, the client sees phases and milestones, the agency owner sees the chart for every project at once to spot where the studio is overcommitted. The chart is most useful when it is honest, which means recording the slip rather than quietly redrawing the plan to hide it.
Watch out
What people get wrong about Gantt charts
Planning in too much detail. A chart with four hundred tasks is unmaintainable, nobody reads it and it is out of date by the second week; the right level is the task you would actually reschedule, not every step inside it. The other mistake is treating the chart as a promise. It is a model built on estimates, and a project manager who defends the original dates against the evidence has stopped managing and started hoping.
A third mistake is building it without the people who will do the work. Durations estimated by a manager who has never cut a film produce a chart that is wrong from the first day, and a team that was not consulted has no reason to believe in it.
