Planning a project with a Gantt chart

A Gantt chart shows every task in a project as a bar on a timeline. It is the clearest way to see what happens when and what depends on what. You can draw one on paper in under an hour.

Key takeaways

  • A Gantt chart is a bar chart of a schedule: tasks down the side, time across the top, one bar per task.
  • List tasks, set the time scale, draw bars, then add dependencies with arrows.
  • The critical path is the longest chain of dependent tasks; any delay on it delays the finish.
  • Tasks off the critical path have slack, time they can slip without moving the end date.
  • Keep a paper chart under about 30 tasks; split bigger projects into phases.
On this page
  1. Why a Gantt chart helps
  2. Step 1: list the tasks
  3. Step 2: choose the time scale
  4. Step 3: draw the bars
  5. Step 4: add dependencies
  6. Step 5: check the load
  7. Tracking progress
  8. Keeping it simple
  9. Printing

Why a Gantt chart helps

A to-do list tells you what needs doing; a Gantt chart tells you when, and how tasks fit together. You can see at a glance which tasks overlap, which weeks are overloaded and how a delay in one task pushes everything after it.

The chart is named after Henry Gantt, who designed and popularised it around 1910–1915, although the Polish engineer Karol Adamiecki had drawn a similar “harmonogram” in 1896. More than a century later, a sheet of paper and a pencil is still one of the quickest ways to plan a project.

Step 1: list the tasks

Write down everything the project needs, then group small jobs into tasks of a sensible size: for a twelve-week project, tasks of a few days to a few weeks. Write them in rough order down the left-hand column. The chart’s Task, Owner, Start and End columns let you note who is responsible and the planned dates.

Step 2: choose the time scale

Pick the template that fits: the weekly chart for most projects, the 30-day chart for events and sprints, the 12-month chart for long plans. Write dates or week numbers above the columns.

Step 3: draw the bars

For each task, shade from the start column to the end column. Use pencil at first, since plans change. Mark milestones (moments when something must be finished, like a launch or a deadline) with a diamond.

Step 4: add dependencies

Some tasks cannot start until another ends: you cannot paint a wall before plastering it. Draw an arrow from the end of one bar to the start of the next. The longest chain of dependent tasks is the critical path; any delay along it delays the whole project.

A worked example

Here is a small project, a school fair, planned week by week. Each task has a length and a list of tasks it must wait for. Working forwards gives each task its earliest start; working backwards from the finish gives the latest it can end; the difference is its slack.

W1W2W3W4W5W6W7W8W9 A. Book the hall Book the hall: weeks 1–1, on the critical path B. Recruit volunteers 3 weeks of slack Recruit volunteers: weeks 2–4, 3 week(s) of slack C. Invite stallholders Invite stallholders: weeks 2–5, on the critical path D. Design posters 4 weeks of slack Design posters: weeks 2–3, 4 week(s) of slack E. Print and put up posters 4 weeks of slack Print and put up posters: weeks 4–4, 4 week(s) of slack F. Floor plan and stall map Floor plan and stall map: weeks 6–7, on the critical path G. Volunteer briefing Volunteer briefing: weeks 8–8, on the critical path H. Fair day Fair day: weeks 9–9, on the critical path
  • Critical path (no slack)
  • Other tasks
  • Slack: how late a task can finish without delaying the fair
TaskWeeksAfterEarliest startFinishSlack
A. Book the hall1—week 1end of week 10
B. Recruit volunteers3Aweek 2end of week 43 wk
C. Invite stallholders4Aweek 2end of week 50
D. Design posters2Aweek 2end of week 34 wk
E. Print and put up posters1Dweek 4end of week 44 wk
F. Floor plan and stall map2Cweek 6end of week 70
G. Volunteer briefing1B, Fweek 8end of week 80
H. Fair day1E, Gweek 9end of week 90
A 9-week plan for a school fair, scheduled with the critical path method. The critical path is A → C → F → G → H: any delay to those tasks moves the fair. Posters and volunteer recruitment have slack.

Reading it is the useful part. Inviting stallholders, the floor plan, the volunteer briefing and the fair itself sit on the critical path: if stallholder invitations take an extra week, the fair moves a week. Recruiting volunteers has three weeks of slack and the posters four, so those can wait if the hall booking runs late, without risk to the date.

Finding the critical path on paper

  1. Write each task’s length and what it waits for in the Task column.
  2. Draw each bar starting at the end of the latest task it waits for.
  3. The task that ends last sets the project’s finish.
  4. Trace back from it: at each step, follow the task that ends exactly when the next one starts. That chain is the critical path; highlight it.
  5. Every other bar can move right until it touches the next task in its chain. That gap is its slack.

Step 5: check the load

Look down each column. If one week has too many bars, or one person owns several overlapping tasks, move something. It is far easier to fix on paper than in the middle of the project.

Tracking progress

Each week, colour in the part of each bar that is done, and draw a vertical line for today. Anything to the left of the line that is not coloured is behind schedule. Keep the detailed tasks for each week on a to-do list.

Keeping it simple

A paper Gantt chart works best with fewer than 30 tasks. If a project has more, make one chart for the phases and separate charts for the busiest phases.

Printing

Print landscape at 100% / Actual size; for a team wall chart, print on Tabloid or A3.

Printable 12-week Gantt chart – US Letter (landscape) — preview of the PDF
Example sheet: 12-week Gantt chart – US Letter (landscape) — open it in the generator from any paper page.

Sources

Facts in this guide were checked against these sources on 30 October 2026. Figures marked as our own data were calculated with the same code that runs our tools.

  1. Gantt chart— Wikipedia
  2. Critical path method— Wikipedia

Frequently asked questions

What is a Gantt chart?

A bar chart of a project schedule: tasks are listed down the side, time runs across the top, and each task is a bar from its start to its end.

Should I use days, weeks or months?

Match the length of the project: days for a one-month event, weeks for a three-month project, months for a year-long plan.

How do I show that one task depends on another?

Draw an arrow from the end of the first bar to the start of the second.

Is a paper Gantt chart useful for teams?

Yes, especially pinned on a wall where everyone can see it. Update it at a weekly meeting.

Last updated · About us