Free Gantt Chart Maker: How to Plan a Project Step by Step
Your manager asks, “When will this be done?” You open a spreadsheet, look at a long list of tasks, and give a date that feels about right.
Then one task slips. Another task was waiting on it. And the date you gave? It was a guess.
A Gantt chart fixes that. A free Gantt chart maker puts every task on a timeline, shows what depends on what, and tells you which delays really matter.
In this guide you’ll build one step by step, using a small worked example. You can follow along in the free Project Planner on this site.
Why project plans fall apart
Most plans don’t fail on day one. They fail quietly, in the gaps between tasks.
- A list hides the order. You can’t see what must finish before something else can start.
- Dates are guessed one at a time. Each task gets a date without checking the tasks around it.
- Nobody sees the chain that controls the finish date. So everything feels equally urgent.
- The plan is never updated. It looks fine in week one and is out of date by week three.
You are not bad at planning. A list is the wrong tool for the job.
A Gantt chart is built for exactly this job.
What a Gantt chart actually shows
A Gantt chart is a bar chart turned on its side. Each task is a bar. Where the bar sits shows when the task starts, and how long it is shows how many days the task takes.
Links between the bars show dependencies. That simply means: this task can’t start until that one finishes. Add milestones, which are key dates with no duration, such as “go live”, and you have a plan anyone can read in thirty seconds.
That helps you, and it helps even more when a sponsor or a client asks for an update.
How to use a free Gantt chart maker: a worked example
We’ll plan a small website update. It’s simple on purpose, so you can see each idea clearly. Then you can repeat the same steps on your own project.
Step 1: Write down the work
List the tasks first. Don’t think about dates yet. Break the work into pieces small enough that one person can own each piece and you can estimate it in days.
Our example has six tasks: Requirements, Design, Build, Write test cases, Testing and Release.
Takeaway: If one task feels too big to estimate, split it.
Step 2: Estimate how long each task takes
Give every task a duration in working days. Ask the person who will do the work, not the person who wants it finished. If you add a buffer, add it on purpose and say so. Quiet padding hides the real picture.
Our estimates are: Requirements 2 days, Design 3, Build 5, Write test cases 2, Testing 3 and Release 1.
Step 3: Link the dependencies
Now ask one question for each task: what must finish before this can start?
| Task | Days | Can start after |
|---|---|---|
| Requirements | 2 | Nothing, it comes first |
| Design | 3 | Requirements |
| Build | 5 | Design |
| Write test cases | 2 | Requirements |
| Testing | 3 | Build and Write test cases |
| Release | 1 | Testing |
Look at “Write test cases”. It only needs the requirements, so it can run at the same time as Design and Build. A plain list would never show you that. A Gantt chart does.
Step 4: Read the schedule
Once the links are in, the dates work themselves out. Counting from day 0:
| Task | Starts | Finishes |
|---|---|---|
| Requirements | Day 0 | Day 2 |
| Design | Day 2 | Day 5 |
| Build | Day 5 | Day 10 |
| Write test cases | Day 2 | Day 4 |
| Testing | Day 10 | Day 13 |
| Release | Day 13 | Day 14 |
The test cases are ready on day 4, but Testing can’t start until the build is finished on day 10. The whole project takes 14 working days.
Step 5: Find the critical path
The critical path is the longest chain of linked tasks. It decides your finish date. In our example it runs Requirements, then Design, then Build, then Testing, then Release: 2 + 3 + 5 + 3 + 1 = 14 days.
Write test cases is not on that chain. It finishes on day 4 but isn’t needed until day 10, so it has about six days of float. It can slip by up to six days and the release date won’t move.
Any delay on the critical path delays the release by the same amount. That’s where your attention should go.
Takeaway: Watch the critical path closely. Stay relaxed about tasks that have float.
Want the full method? Read How to Find the Critical Path, or check your own tasks with the Critical Path Calculator.
Step 6: Assign people and check the workload
Put a name on every task. Then check whether anyone is booked for two things at the same time. A plan that works on paper but needs one person to do two jobs at once isn’t really a plan.
Step 7: Save a baseline and track progress
When the team agrees on the plan, save a baseline. That’s a snapshot of the original plan. As work moves, update progress and compare it with the baseline. Without one, you can’t tell whether you’re late or just different.
Update the chart at least once a week. Five minutes is usually enough.
Doing this in the free Project Planner
The Project Planner follows the same steps, tab by tab:
- Gantt chart tab: add tasks, milestones and phases.
- Resources tab: link tasks with predecessors and assign people.
- Workload tab: spot anyone who is over-allocated.
- Tracking tab: save a baseline, then update progress.
- Reports tab: get a status report you can copy.
The critical path, budget and earned value update as you work. One thing to remember: your plan is saved only in your own browser. Export it as a file or a CSV so you always have a copy.
Common mistakes to avoid
- Too many tasks. A plan with hundreds of tiny tasks is one nobody reads. Start with 8 to 12 and add detail only where the risk is.
- Skipping dependencies. Bars without links are just a pretty list.
- Ignoring float. Treating every task as urgent wears the team out.
- Never updating the chart. An old plan is risky, because people still trust it.
Simple Action Plan
- Pick one real project you’re working on this week.
- List 8 to 12 tasks and give each a duration in working days.
- Link each task to what must finish before it can start.
- Find the critical path and mark it.
- Assign owners, check the workload, then save a baseline.
- Update the chart once a week.
Conclusion
A Gantt chart isn’t about pretty bars.
It’s about seeing the order of the work, the real finish date and the few tasks that can move it.
You don’t need expensive software to start. You need a clear list, honest estimates and a few links between tasks.
Build one small plan this week. You’ll stop guessing dates.
Call to action
Open the free Project Planner and build the six-task example above. Then swap in your own project. If you like plain-English, practical guidance for project work, you may enjoy my books on the My Books page.
FAQs
What is a Gantt chart used for?
A Gantt chart is used to plan and track a project on a timeline. It shows each task, how long it takes, what it depends on and where the milestones are.
Is there a free Gantt chart maker I can use online?
Yes. The Project Planner on this site is a free online Gantt chart. Your plan is saved only in your own browser, so export it as a file or a CSV to keep a copy.
What is the difference between a Gantt chart and the critical path?
The Gantt chart shows the whole schedule. The critical path is the longest chain of linked tasks inside it, and it sets the earliest finish date. Tasks off that chain have float.
How detailed should my Gantt chart be?
Detailed enough to track progress every week, and simple enough that people actually read it. Start with 8 to 12 tasks and add detail only where the risk is high.
Can I use a Gantt chart on an Agile project?
Yes. Many teams plan sprints in their own way but still need a high-level view of releases, milestones and dependencies. A simple Gantt chart gives stakeholders that view without changing how the team works.
How often should I update my Gantt chart?
Once a week is a good habit. Update progress, check the critical path and change dates only when there is a real reason.
Atul Sharma PMP
IT professional with 20+ years of experience and author of books on communication, AI and career growth for testers, project managers and IT professionals.
