How to fill in this blank Gantt chart
What a blank Gantt chart template is for
The other templates on Great Gantt come with a whole project already built in — construction, a thesis, a product launch. This one is different: instead of a specific project, it gives you just the skeleton. Four generic phases, three tasks each (except the last), and a closing milestone, already linked by simple dependencies.
It is for people who already know how they want to structure their own project but do not want to build the dependency links from scratch, and for people learning how a Gantt chart works who want a small example to practice on before applying it to a real project.
The difference from a blank spreadsheet is in the dependencies: Task 2.1, for instance, only starts once tasks 1.2 and 1.3 are both done. Once you rewrite the names with your project's content, those links keep working.
The template's structure: 4 phases, 11 tasks, 1 milestone
Numbers in parentheses are the working days the template starts with — adjust them to your project's actual size.
- Phase 1: planning — Task 1.1 (3), Task 1.2 (2) and Task 1.3 (2), the last two running in parallel after the first.
- Phase 2: execution — Task 2.1 (4) and Task 2.2 (3) running in parallel after planning, Task 2.3 (3) after 2.1, and Task 2.4 (2) after both 2.2 and 2.3.
- Phase 3: review — Task 3.1 (2) and Task 3.2 (1), one after the other.
- Phase 4: closure — Task 4.1 (2), Task 4.2 (1) and the project completed milestone, with zero duration.
How to fill in a Gantt chart, step by step
Order matters: define scope before estimating duration, and estimate duration before linking dependencies. Skipping a step is the most common way a schedule ends up wrong.
- Scope and deliverables. Write, in one sentence, what the project delivers at the end. Without that, every task you list afterward is a guess.
- Break it into tasks. Split the deliverables into pieces small enough to estimate with confidence, usually one to five working days each.
- Estimate duration. Ask the person doing the work for a duration instead of guessing it yourself. Estimates made only by whoever is coordinating tend to come in short.
- Finish-to-start dependencies. For every task, ask what has to be done before it can start. That link is what makes the whole schedule move when one date changes.
- Milestones. Mark the checkpoints that matter to people outside the team — approval, delivery, launch — with zero duration.
- Critical path and slack. Check which tasks have no room to slip (delaying any of them delays the whole project) and which have a few spare days. In this structure, only Task 2.2 has slack, about 4 working days.
- Updates. Once the project starts, mark percent complete for every task weekly and compare it against the baseline you saved at the start.
Common mistakes when filling in a blank Gantt chart
Most problems show up before the first task even starts, while the structure is still being built.
- A task too big to estimate. If a task runs longer than two weeks, it is probably really two or three smaller tasks with visible intermediate deliverables.
- A dependency that is not really a dependency. Chaining everything in sequence, even when two tasks could run in parallel, stretches the timeline for no reason.
- A milestone with more than zero duration. A milestone that takes two days stops working as a checkpoint and becomes just another task.
- A generic owner, like "the marketing team" instead of one person. Without a name attached, nobody feels responsible for the task.
- Forgetting to save a baseline. Without one, there is no way to compare what was planned against what actually happened, and every conversation about delay turns into opinion.
Who this blank template fits
Someone who has run a few projects before and knows how to structure their own, but does not want to rebuild phases and dependency links from scratch on every new project.
Someone learning how a Gantt chart works who wants a small example with dependencies and a milestone to see how the pieces fit together before applying it to a real project.
Someone training another person — an intern, a new project manager — who needs a hands-on exercise without the risk of messing up a real schedule at the company.