New to this topic?
We recommend reading these guides first to get the most out of this one:
1910s
Invented by Henry Gantt
Bars
= Tasks Over Time
◆
Milestones
Link
Show Dependencies

What Is a Gantt Chart?

A Gantt chart is a horizontal bar chart that shows project tasks plotted against time. Each task is a bar whose length represents its duration, positioned along a calendar timeline. Dependencies between tasks are shown as lines connecting the bars. It is the most widely used project visualization tool in the world.

Developed by Henry Gantt during World War I for scheduling military production, Gantt charts remain the default way to communicate a project schedule because they are intuitive: anyone can look at one and understand what needs to happen, when, and how tasks relate to each other.

Anatomy of a Gantt Chart

ElementVisualWhat It Shows
Task barHorizontal barDuration of a task — length = time, position = when
Summary barBold or grouped barA phase or WBS group spanning its child tasks
MilestoneDiamond (◆)A zero-duration event: approval, delivery, go-live
Dependency lineArrow connecting barsPredecessor relationship (FS, SS, FF, SF)
Progress fillShaded portion of barPercentage of task completed
Baseline barGray bar below actualOriginal planned schedule for comparison
Today lineVertical lineCurrent date — tasks to the left should be done, tasks to the right are future
Critical path highlightRed barsTasks on the critical path
Float barThin extension on a barHow much a task can slip without impacting the project

Building a Gantt Chart

Start with the WBSList all work packages. These become the rows in your Gantt chart. Group them under summary phases.
Estimate durationsAssign a duration to each task. Use historical data where possible; use PERT three-point estimates for uncertain tasks.
Define dependenciesIdentify predecessor-successor relationships. Most are Finish-to-Start. Draw the arrows.
Assign resourcesWho does each task? Check for resource overallocation — the same person scheduled for two tasks at the same time.
Set milestonesMark key decision points, deliverables, and external dependencies. Milestones are your communication anchor with stakeholders.
Save the baselineBefore execution begins, save the schedule as a baseline. This lets you compare actual vs. planned throughout the project.

Reading a Gantt Chart Effectively

What to Look ForWhat It MeansAction
Task bar extends past the today line with no progress fillTask should have started but has notInvestigate immediately — likely blocking downstream work
Actual bars slipping right of baseline barsSchedule is slipping vs. original planCheck if critical path is affected. If yes, act now.
Many parallel bars in one periodHigh resource demand — potential overallocationCheck resource histogram. Level if needed.
Long float bars on non-critical tasksThese tasks have scheduling flexibilityUse this flexibility for resource balancing or risk mitigation
All bars concentrated at end of timeline"Hockey stick" schedule — everything crammed at the endPull work forward. This pattern almost always causes a crunch.

Gantt Charts for Manufacturing Projects

Project TypeWhat the Gantt Shows
Plant shutdown / turnaroundAll maintenance activities across trades, with dependencies. Critical path highlighted for shutdown duration management.
New line installationProcurement lead times, construction, installation, commissioning phases — all on one timeline with milestones.
NPI launchDesign → tooling → validation → production ramp. Shows where engineering handoffs create dependencies.
Lean implementationAssessment → kaizen events → standard work → training → audit. Shows which cells/areas are being transformed and when.
SMED projectsVideo analysis → internal/external separation → hardware modifications → trial → validation.

Gantt Chart Limitations

✅ Gantt Strengths
  • Intuitive — anyone can read a Gantt chart with minimal training
  • Shows both timeline and dependencies in one view
  • Baseline comparison makes slippage immediately visible
  • Milestones provide clear communication points for stakeholders
  • The universal language of project scheduling across industries
❌ Gantt Weaknesses
  • Does not show resource allocation or overallocation (need a histogram for that)
  • Gets unwieldy for large projects (500+ tasks) — difficult to see the big picture
  • Does not show uncertainty or risk — every bar looks equally certain
  • Can give false confidence — a pretty Gantt chart is not the same as a realistic plan
  • Dependencies become spaghetti on complex projects with many cross-links

Gantt + Network Diagram

For complex projects, use the Gantt chart for communication and status reporting, and the CPM network diagram for scheduling logic and critical-path analysis. The Gantt is the "what and when" view; the network diagram is the "why this sequence" view. Use both.

🎯 Key Takeaway

The Gantt chart is the most effective way to communicate a project schedule to anyone — from operators to executives. Build it on a solid WBS, link dependencies, highlight the critical path, save a baseline, and track progress against it. But do not let a clean-looking Gantt give you false confidence — it does not show resource constraints, risk, or uncertainty. Use it as a communication tool, and pair it with network analysis and resource leveling for the real planning work.

Interactive Demo

Build a Gantt chart for a manufacturing project. Adjust task durations and see the timeline update.

⚡
Try It Yourself
Interactive Gantt Chart
▼
Adjust task durations to see the Gantt chart update in real time. Tasks turn red when they push the project past the deadline.
D1D2D3D4D5D6D7D8D9D10D11D12D13D14D15D16D17D18D19D20DeadlineRequirements3dD1D3Design4dD4D7Development6dD8D13Testing3dD14D16Deployment2dD17D18
On Time
Extended
Past Deadline
Baseline (dashed)
3d
1d12d
4d
1d12d
6d
1d12d
3d
1d12d
2d
1d12d
18 days
Project Duration
18 days
Deadline
0 days
Slack
Ready for the full knowledge check? Test your understanding with guided scenarios and data export.
PROTake the Pro Knowledge Check →
Free forever · Every feature included

Stop reading, start modeling

Model your process flow, run simulations, optimize staffing with TOC math, and test your knowledge with 107 interactive checks — all in one platform.

Open Workbench → Pro Knowledge Check

Take this to a room

The running order

For anyone presenting a schedule. They should leave using the Gantt for communication and a network for the logic, with a saved baseline.

7 beats · 9 min
  1. 1

    The best communication tool in scheduling

    Anyone can read a Gantt chart with almost no training. That is its entire superpower.

    • Bars are tasks over time. Diamonds are milestones. Lines are dependencies.
    • Operators and executives read the same picture.
    • It is the universal language of project scheduling across every industry.

    Ask the room Who are we showing our schedule to, and can they read it?

  2. 2

    Build it on a WBS

    The rows come from the work breakdown structure, not from a brainstorm.

    • Every work package becomes a row, grouped under summary phases.
    • If the WBS is incomplete, the Gantt is confidently incomplete too.
    • This is why a good Gantt starts somewhere other than the Gantt.
  3. 3

    Save the baseline before you start

    The single most valuable habit, and it takes one click.

    • Save the schedule before execution begins.
    • Then every actual can be compared to what was planned.
    • Without a baseline, slippage is invisible - the chart just quietly redraws itself.

    Ask the room Do we have a baseline saved on our current project?

  4. 4

    What to look for when you read one

    There are a handful of visual signals worth knowing.

    • Bars drifting right of baseline: slippage, and how much.
    • Long unbroken bars: probably under-decomposed tasks hiding detail.
    • Milestones bunched at the end: risk concentrated where you can least absorb it.
  5. 5

    What it does not show

    Three blind spots, and each has caused a lot of confident failures.

    • Resource allocation - you need a histogram for that.
    • Uncertainty - every bar looks equally certain, and they never are.
    • Above about 500 tasks it becomes unreadable, which is its own risk.
  6. 6

    A pretty chart is not a real plan

    Say this out loud, because a clean Gantt is genuinely persuasive.

    • Neatness is not feasibility.
    • The Gantt is the what and when. The network diagram is the why this sequence.
    • Use the Gantt for communication and status, the network for the scheduling logic.

    Ask the room Has our Gantt ever been checked against a resource histogram?

  7. 7

    What we do next

    WBS, durations, dependencies, resources, milestones, baseline. In that order.

    • Historical durations where they exist, three-point estimates where they do not.
    • Check for resource overallocation before publishing.
    • Mark the milestones that stakeholders actually care about.
    • Save the baseline and then track against it weekly.

    Ask the room Which project do we baseline this week?