Frameworks · Managing change

Gantt charts

A chart of a project's tasks as bars against a timeline, showing when each starts and ends, which overlap, and the milestones along the way.

An IB toolkit tool, guide p. 14 HL only IB DiplomaUndergraduateMBAProfessional

Section 01: The framework at a glance

A Gantt chartA Gantt chart for opening a fictional café over 12 weeks. Find and sign a site: weeks 1 to 3. Arrange finance: weeks 2 to 4. Fit out the café: weeks 5 to 9. Recruit staff: weeks 6 to 8. Train staff: weeks 9 to 10. Launch marketing: weeks 8 to 11. Opening day is a milestone in week 12. Overlapping bars run at the same time, and an arrow shows that fitting out cannot start until the finance is in place.123456789101112WEEKFind and sign a siteArrange financeFit out the caféRecruit staffTrain staffLaunch marketingOpening dayBars show when each task runs; overlapping bars run at the same time. The arrow marks a dependency: fitting out cannotstart until the finance is in place.
A Gantt chartA Gantt chart for opening a fictional café over 12 weeks. Find and sign a site: weeks 1 to 3. Arrange finance: weeks 2 to 4. Fit out the café: weeks 5 to 9. Recruit staff: weeks 6 to 8. Train staff: weeks 9 to 10. Launch marketing: weeks 8 to 11. Opening day is a milestone in week 12. Overlapping bars run at the same time, and an arrow shows that fitting out cannot start until the finance is in place.123456789101112Find and sign a siteArrange financeFit out the caféRecruit staffTrain staffLaunch marketingOpening dayWeeks across the top. Overlapping barsrun at the same time; fitting outcannot start until the finance is inplace.

A Gantt chart HL Tasks against time, with overlaps, a dependency and a milestone.
Text description

A Gantt chart for opening a fictional café over 12 weeks. Find and sign a site: weeks 1 to 3. Arrange finance: weeks 2 to 4. Fit out the café: weeks 5 to 9. Recruit staff: weeks 6 to 8. Train staff: weeks 9 to 10. Launch marketing: weeks 8 to 11. Opening day is a milestone in week 12. Overlapping bars run at the same time, and an arrow shows that fitting out cannot start until the finance is in place.

Section 02: What it is, and what it is for

A Gantt chart lists the tasks of a project down the side and time along the top. Each task is a bar from its start to its finish, so the chart shows at a glance the order of work, which tasks run at the same time, and the milestones, such as a launch date. Dependencies, where one task cannot start until another ends, can be shown with arrows, and progress can be shaded in as the project runs.

It is easy to read and good for communicating a schedule to a team. It shows dependencies less rigorously than a critical path network, and does not by itself reveal which tasks have float, so the two tools are often used together.

What it is for

To plan and track a project's timing, allocate people to tasks and communicate the schedule. The toolkit lists it as an HL tool for units 4 and 5; its full guide is in preparation.

Section 03: How it is built

The parts of the framework, and what each one holds.

The task list
Every task in the project, in the order they happen, with an estimated duration for each.
The timeline
A horizontal scale of days, weeks or months across the top of the chart.
The bars
One bar per task, starting when its dependencies allow and as long as its duration, so overlapping bars show tasks that run at the same time.
Dependencies
The tasks that must finish before another can start, shown by the bars' positions or by linking arrows.
Milestones
Key dates, such as an opening day or a sign-off, usually marked with a diamond.
Progress
How much of each task is done, shaded within its bar or marked against a line for today's date.

Section 04: When to use it

The business situations it suits, and where another tool will serve better.

It suits

  • Communicating a project's timetable to a team, a client or a board who need to see at a glance what happens when.
  • Tracking a project week by week, so that a task that slips is seen early.
  • Planning the use of shared people or equipment, by seeing which tasks overlap.

Look elsewhere when

  • Finding the critical path and the float of each task in a complex network, where critical path analysis is clearer.
  • Work whose tasks are unknown or keep changing, where a fixed chart soon misleads.

Section 05: How to use it, step by step

A short method. The toolkit guide gives the full one, with the evidence each step needs.

  1. List the tasks and estimate the duration of each.
  2. Identify which tasks depend on others finishing first.
  3. Draw each task as a bar on the timeline, starting when its dependencies allow.
  4. Mark milestones and the project's end date.
  5. Track progress against the plan and adjust the bars when tasks slip.

Section 06: Applied: Juniper Café plans its opening

Fictional business

The owner of Juniper Café, a fictional business, plans the twelve weeks to opening day, as in the diagram above: find and sign a site (weeks 1 to 3), arrange finance (weeks 2 to 4), fit out the café (weeks 5 to 9), recruit staff (weeks 6 to 8), train staff (weeks 9 and 10) and run the launch marketing (weeks 8 to 11), with the opening in week 12.

What it showed

The chart shows that training cannot start until recruitment ends in week 8, and that the café cannot open until the trained staff are in place, so a delay of two weeks in hiring would leave almost no margin before opening day. The owner starts advertising the jobs a week earlier to build one in.

Section 07: Reading the result

How to interpret what it shows, and what that does and does not justify deciding.

Read the chart for its pinch points: places where several tasks overlap and compete for the same people, and chains of dependent tasks with no gap between them, where any delay passes straight through to the finish.

Compare the plan with progress regularly. A bar that is behind today's line is a problem only if a later task depends on it and has no room to absorb the delay, so check the dependency before reacting.

What it can justify deciding

  • Starting early tasks sooner, or adding resources to a chain of dependent tasks, to build in a margin before a fixed date.
  • Re-planning the bars when a task slips, and telling the people whose tasks depend on it.

What it does not justify on its own

  • Concluding that tasks without visible dependencies can slip freely; the chart does not calculate float.
  • Treating the end date as certain while the durations are estimates.

Section 08: Strengths and limits

Why it helps

  • Easy to read, so everyone can see what happens when.
  • Good for allocating people and spotting overlaps and clashes.
  • Progress can be tracked against the plan visually.

Where it falls short

  • Dependencies are harder to read than on a network diagram, especially in large projects.
  • It does not by itself identify the critical path or the float on each task.
  • Estimates of duration are uncertain, so the chart needs updating.

Section 09: Common mistakes

Errors often made with it, by students and by managers, and how to avoid each.

  1. Mistake Drawing bars without showing which tasks depend on which.

    Instead Mark the dependencies, so that the effect of a delay can be traced.

  2. Mistake Making the chart once and never updating it.

    Instead Record progress against the plan regularly and move the bars when tasks slip.

  3. Mistake Treating the Gantt chart as a substitute for critical path analysis in a complex project.

    Instead Use critical path analysis to find the critical path and float, and the Gantt chart to communicate and track the plan.

Section 10: Apply it

The application mode: the platform's tools that apply this framework, and a worksheet for your own case.

Frameworks structure judgement; they do not produce answers. Each one organizes evidence so that you can see it, test it and argue from it, and the decision, and the reasons for it, remain yours.

No interactive tool on the platform applies Gantt charts in full yet, so the worksheet below is its application mode, with the tools that help with parts of it.

For part of it

Your worksheet

Work through the framework part by part for a business you know, then say what the result does and does not justify.

Kept on this device as you type, and nowhere else. Not saved without JavaScript: print the page or copy your answers before you leave.

For example: When does each task happen, and is the project on schedule?
Who it is, what it sells, to whom, and what has changed.
Part by part

For each part, write what you find for this business and the evidence for it. Leave a part blank only if you can say why it does not apply.

What the framework shows when the parts are read together, and how sure you are of it.
The decision the result supports, what else you would need to know, and what would change your mind.

The Framework Application Lab: choose a framework by the decision you face.

Section 11: Try it

The platform's own exercise. Write your answer, then open the guidance.

Plan a school charity fair with six tasks, such as booking the hall, recruiting volunteers and advertising. Draw a Gantt chart over six weeks, show one dependency and one milestone, and explain which task would most delay the fair if it ran late.

Kept on this device as you type, and nowhere else. Your answer is not saved without JavaScript; copy it before you leave.

Guidance: what a strong answer does
  • Give each task a realistic duration and a reason for its start date.
  • Show at least one task that cannot start until another ends.
  • Mark the fair itself as the milestone.
  • Explain the delay using the dependencies, which is where critical path analysis adds detail.

In the glossary

  • Gantt chart A bar chart that shows the tasks of a project against a time scale, with each bar showing when a task starts and how long it lasts.
  • Critical path analysis (CPA) A project-planning tool that shows a project's activities as a network, in the order they must happen, to find the shortest time in which the project can be completed and the activities that cannot be delayed without delaying it.
  • Lead time The time between placing an order with a supplier and receiving the goods, ready to use.

Read with

Compared with it: Gantt chart against critical path analysis . Or compare it with any other framework in the library.

The explanation, method, example and exercise are the platform's own. Statements about the IB course cite the Business management guide; the business in the example is fictional.