Gantt chart example: a small project plan, step by step

Reading about Gantt charts is useful, but a good Gantt chart example teaches faster than any definition. Most explanations stay abstract: bars, arrows, a timeline. This article builds one small plan from scratch, shows the exact tasks, durations and dependencies, and explains why each choice was made. You can copy the structure for your own project in about twenty minutes.

The example is a customer event: a half-day workshop for 40 guests, planned over four working weeks. It is small enough to read at a glance and real enough to contain the things every plan has: phases, waiting time, parallel work and a fixed end date.

The project in one paragraph

We are organizing a half-day customer workshop. We need a venue, invitations, a guest list, catering, an agenda with speakers and printed materials. The event happens at the end of week four, and nothing about it can move once invitations are out. That last sentence matters: it tells us where the risk is.

If you are new to the vocabulary, the guide on how to read a Gantt chart covers the parts of the chart used below.

Step 1: List the work in phases

Start with a list, not dates. Group the tasks into phases so the plan stays readable. This is the idea behind task groups and subtasks: the group is a phase, the tasks inside it are the work.

Phase 1: Plan

• Define goals and budget
• Choose venue and date

Phase 2: Promote

• Design the invitation
• Send invitations
• Collect RSVPs

Phase 3: Prepare

• Book catering
• Prepare agenda and speakers
• Print materials

Phase 4: Run

• Final check
• Event day

Ten tasks, four phases. That is the right size for a first Gantt chart example: nobody needs sixty rows to plan a workshop.

Step 2: Give every task a duration

Next, estimate how long each task takes in working days. Estimate the effort and the waiting time honestly. Collecting RSVPs is a good case: it takes almost no effort but ten working days of elapsed time, because you are waiting for people to reply. If you want help with this step, see how to estimate task duration.

Task	Duration
Define goals and budget	2 days
Choose venue and date	3 days
Design the invitation	2 days
Send invitations	1 day
Collect RSVPs	10 days
Book catering	3 days
Prepare agenda and speakers	5 days
Print materials	2 days
Final check	1 day
Event day	1 day

Step 3: Add dependencies

Durations alone do not give you a schedule. Dependencies say what has to finish before something else can start. The full explanation is in task dependencies in a Gantt chart, but this plan needs only the simplest kind, finish-to-start: task B starts when task A ends.

• Choose venue and date starts after Define goals and budget.
• Design the invitation starts after Choose venue and date, because the invitation needs the place and the date.
• Send invitations starts after Design the invitation.
• Collect RSVPs starts after Send invitations.
• Book catering starts after Choose venue and date.
• Prepare agenda and speakers starts after Define goals and budget.
• Print materials starts after Prepare agenda and speakers.
• Final check starts after Collect RSVPs, Book catering and Print materials.
• Event day starts after Final check.

Notice that the agenda does not wait for the venue. It only needs the goals. Because it does not depend on the invitation chain, it runs in parallel. A Gantt chart is good at showing exactly this: what can happen at the same time and what cannot.

Step 4: Add milestones

A milestone is a marker with no duration. It records a moment you want to be able to point at. Two are enough here:

• Venue confirmed, right after Choose venue and date. Everything promotional depends on it.
• Event delivered, after Event day.

If you want to choose milestones well, the article on milestones in a Gantt chart gives rules of thumb. For this plan, the first milestone is the one that matters: until the venue is confirmed, nothing in Promote can start.

Step 5: Read the result

Add up the longest chain and you get the schedule. Counting working days from the start:

1. Define goals and budget: days 1 to 2
2. Choose venue and date: days 3 to 5
3. Design the invitation: days 6 to 7
4. Send invitations: day 8
5. Collect RSVPs: days 9 to 18
6. Final check: day 19
7. Event day: day 20

Twenty working days is four weeks, which matches the deadline. The side branches finish early: the agenda is done by day 7, printed materials by day 9, and catering is booked by day 8. They have slack, meaning they can slip for a few days without moving the event.

The chain that decides the end date is the critical path. In this example it runs through goals, venue, invitation, sending and RSVPs. That tells you where to be careful. A one-day delay choosing the venue moves the event by a full day. A one-day delay printing materials moves nothing.

What the chart tells you that a list does not

Compare this with the same ten tasks in a plain checklist. The checklist is complete, but it cannot answer questions like these:

• What happens to the event date if the venue takes two extra days? Every task after it shifts.
• Which tasks can start today without waiting for anyone? The agenda and, once the venue is confirmed, catering.
• Where is the plan fragile? The ten-day RSVP wait is the longest single bar, and it sits on the critical path.

The first question is the most valuable. When a date moves, you want to see the consequences immediately instead of recalculating by hand. If you already work in a spreadsheet, the comparison in Gantt chart vs spreadsheet explains when the extra structure pays off.

Common mistakes in a first Gantt chart

• Too many tasks. If a task takes less than half a day, it probably belongs in a checklist inside a bigger task, not on the chart.
• Dates instead of dependencies. Typing a start date on every bar makes the plan rigid. Link tasks and let the dates follow.
• Ignoring waiting time. A task that is mostly waiting still occupies the timeline. Give it its real duration.
• No owner. Every task needs one person responsible. Shared ownership usually means nobody checks.
• Never updating. A plan that was right on Monday is wrong by Friday if nobody touches it. Keep it up to date with a short weekly routine.

Build this example in ProGantt Flow

You can recreate this plan in ProGantt Flow in a few minutes: add the four phases as task groups, put the tasks inside them, set durations, link the dependencies, and add the two milestones. Then try the experiment that makes a Gantt chart worth having: change the duration of Choose venue and date from three days to five and watch the rest of the schedule respond.

If you prefer to describe the plan in words, ProGantt Flow also has an MCP connector, so an AI assistant such as Claude can create tasks and dependencies for you. The connector docs explain how to set it up. Check the result either way: an assistant can draft the plan quickly, but you know which waiting times are real.

Summary

A good Gantt chart example follows five steps: list the work in phases, estimate durations, add dependencies, mark milestones and read the result for the critical path. Ten tasks were enough to show parallel work, a long wait and a fixed deadline. Use this plan as a template, replace the tasks with your own, and you will have a working schedule before lunch.