What Is a Gantt Chart? The Complete Guide for Project Managers (2026)

A Gantt chart is a horizontal bar chart that shows a project schedule over time. Each bar represents a task: its position shows when it starts and ends, its length shows duration, and the lines between bars show dependencies. At a glance, you can see what needs to happen, when, and in what order.

Named after Henry Gantt, who popularised the format around 1910, the Gantt chart is the most widely used project scheduling tool in the world. From construction projects to software launches to marketing campaigns, it remains the universal visual language of project timelines.

The 30-Second Summary

• What it is: a horizontal bar chart of a project schedule.
• What it shows: task durations, parallel work, dependencies, milestones, the critical path, and progress.
• When to use it: projects with deadlines, ordered work, and 15+ tasks.
• When to skip it: fast-iterating Agile work or tiny task lists.
• What separates good tools from bad ones: all four dependency types (FS/SS/FF/SF), automatic critical path, and baseline tracking.

Why Gantt Charts Matter

Gantt charts solve a fundamental project management problem: how do you communicate a complex schedule so everyone understands it?

A task list tells you what needs to be done. A Gantt chart tells you what needs to be done, when, in what order, and how everything connects. That visual context is what makes them powerful.

What You Can See at a Glance

• Project timeline: total duration from start to finish
• Task durations: how long each piece of work takes
• Parallel work: which tasks happen simultaneously
• Dependencies: which tasks must finish before others can start
• Critical path: the longest chain of dependent tasks that determines the project's minimum duration
• Progress: how far along each task is, shown as a filled portion of the bar
• Milestones: key dates or deliverables, shown as diamond markers
• Resource assignments: who's responsible for each task

Anatomy of a Gantt Chart

A typical Gantt chart has two panels working together.

The Left Panel (Task List)

A structured list of tasks, often organised hierarchically:

• Summary tasks (parent): group related tasks together
• Work tasks (child): the actual work items
• Milestones: zero-duration markers for key dates or deliverables

Each row also shows metadata: assigned resources, start/end dates, duration, percent complete.

The Right Panel (Timeline)

A horizontal timeline with:

• Time scale: days, weeks, or months across the top
• Task bars: horizontal bars showing each task's duration
• Progress fill: a darker fill inside each bar showing completion percentage
• Dependency arrows: lines connecting related tasks
• Today line: a vertical line marking the current date
• Baseline bars: lighter bars behind the actual bars showing the original planned schedule (when baselines are set)

The Four Dependency Types

Dependencies are the arrows between tasks. There are four kinds.

Finish-to-Start (FS): the most common. Task B can't start until Task A finishes. Example: you can't start painting until the drywall is installed.

Start-to-Start (SS): Task B can't start until Task A starts. Example: quality testing starts when development starts (runs in parallel, but can't begin earlier).

Finish-to-Finish (FF): Task B can't finish until Task A finishes. Example: documentation can't be finalised until the feature it describes is complete.

Start-to-Finish (SF): Task B can't finish until Task A starts. Rare in practice. Example: the old security system can't be decommissioned until the new one is activated.

Lag and Lead

• Lag: a delay between linked tasks. FS + 2 days means Task B starts 2 days after Task A finishes.
• Lead: an overlap. FS − 3 days means Task B starts 3 days before Task A finishes.

When to Use a Gantt Chart

Gantt charts aren't the right tool for every situation. Here's when they shine and when to consider alternatives.

Use a Gantt Chart When

• You have a defined timeline: projects with clear start dates, end dates, and deadlines benefit most from Gantt charts.
• Tasks have dependencies: if the order of work matters (and it usually does), Gantt charts visualise those relationships.
• You need to communicate schedules: Gantt charts are universally understood. Stakeholders, executives, and clients can read them without training.
• You're managing resources across tasks: seeing who's working on what, and when, helps prevent overallocation.
• The project has 15+ tasks: below that, a simple task list might suffice.

Consider Alternatives When

• Work is highly iterative: Agile sprints with rapidly changing priorities are better served by Kanban boards.
• You have 5–10 simple tasks: a checklist or task board is faster to set up and maintain.
• Everything is parallel with no dependencies: if tasks are independent, a Gantt chart adds complexity without value.
• Requirements are undefined: if you don't know what the tasks are yet, you can't schedule them.

The Hybrid Approach

Many modern teams use Gantt charts for planning and high-level tracking, and Kanban boards for daily execution. This gives you the best of both: a structured timeline for stakeholders and a flexible task flow for the team.

Onplana supports this natively: switch between Gantt, Kanban, Calendar, and List views without losing any data.

How to Create a Gantt Chart: Step by Step

Step 1: Define Your Tasks

Start with a Work Breakdown Structure (WBS): break the project into phases, then break phases into deliverables, then break deliverables into tasks.

Rule of thumb: tasks should be 1–10 days in duration. Anything longer should be broken into subtasks. Anything shorter is usually too granular for the Gantt view and belongs on a checklist.

Step 2: Estimate Durations

For each task, estimate how long it will take. Use:

• Historical data: how long did similar tasks take in past projects?
• Expert judgment: ask the person who'll do the work.
• Three-point estimation: (optimistic + 4 × most likely + pessimistic) ÷ 6. Accounts for uncertainty more honestly than a single number.

Don't confuse effort (work hours) with duration (calendar days). A 16-hour task assigned to someone working 50% on your project has a duration of 4–5 days.

Step 3: Identify Dependencies

For each task, ask: "What must be done before this can start?" and "What can't finish until this is done?"

Map out the FS, SS, FF, and SF relationships. Most will be Finish-to-Start.

Common mistake: over-constraining the schedule. Not everything needs a dependency. If two tasks are truly independent, don't link them just because they happen to be sequential in your list.

Step 4: Assign Resources

Assign team members to tasks. Watch for:

• Overallocation: one person assigned to too many concurrent tasks
• Single points of failure: critical tasks with only one possible assignee
• Availability gaps: vacations, part-time schedules, shared resources

Step 5: Set Milestones

Mark key dates: phase completions, deliverable due dates, stakeholder reviews, go-live dates. Milestones are zero-duration tasks that appear as diamond markers on the Gantt chart.

Step 6: Establish a Baseline

Before work begins, save a baseline. This captures the planned start/end dates and effort for every task. As the project progresses, you can compare actual vs. planned to measure schedule health. Without a baseline, you can't tell whether you're ahead or behind: only what date the chart currently shows.

Step 7: Track and Update

As work progresses:

• Update task completion percentages
• Record actual start/finish dates
• Add new tasks or adjust estimates as scope evolves
• Monitor the critical path for slippage

Understanding the Critical Path

The critical path is the longest sequence of dependent tasks from project start to project finish. It determines the minimum possible project duration.

Why it matters:

• Any delay on a critical path task delays the entire project.
• Tasks not on the critical path have float: they can slip without affecting the end date.
• If you need to shorten the project, you must shorten critical path tasks. Anything else is wasted effort.

Worked example:

Path A → B → D :  5 + 3 + 4 = 12 days  (CRITICAL PATH)
Path A → C → D :  5 + 2 + 4 = 11 days  (1 day of float on Task C)

Shortening Task C doesn't help: the project still takes 12 days because path A → B → D is longer.

Modern Gantt chart tools highlight the critical path automatically, usually in red or orange. This is one of the most valuable features to look for when choosing a PM tool. See our deep dive on the Critical Path Method for the algorithm behind it. To see what the critical path actually looks like in your own schedule, the free Schedule Health Check parses any .mpp and computes the path from the dependency graph directly. That's useful for catching the cases where Project's displayed critical path is wrong.

Gantt Chart Best Practices

Keep It Readable

• Limit to 50–100 visible tasks. Use summary tasks to collapse sections. A 500-row Gantt chart is unreadable.
• Use color coding. Different colors for phases, teams, or priority levels.
• Show the right time scale. Weeks for multi-month projects, days for short sprints, months for multi-year programs.

Keep It Accurate

• Update weekly. A Gantt chart that's not current is worse than no Gantt chart; it creates false confidence.
• Don't pad estimates. If you add buffer to every task, your timeline becomes fiction. Use explicit buffer tasks or management reserve instead.
• Track against baselines. Without baselines, you can't tell if you're ahead or behind.

Keep It Useful

• Share it. A Gantt chart locked in one person's desktop tool is worthless. Use a collaborative platform where the team can see and update it.
• Review it in meetings. Walk through the Gantt chart in weekly status meetings. It becomes the single source of truth for the schedule.
• Use it for decisions. When someone asks "can we add this feature?", show the impact on the Gantt chart. Visual impact is more persuasive than "it'll take longer."

Gantt Chart Tools in 2026

The tool landscape has evolved significantly, especially as Microsoft Project Online retires in September 2026. Here's what to look for.

Must-Have Features

• All four dependency types (FS, SS, FF, SF) with lag and lead
• Critical path highlighting
• Baseline comparison
• Resource assignments and workload views
• Drag-and-drop task editing
• Real-time collaboration (multiple users, live updates)

Nice-to-Have Features

• AI-powered scheduling suggestions
• Multiple views (Gantt + Kanban + Calendar + List)
• Sprint / Agile integration
• .mpp and Project Online OData import
• Mobile access for field updates

Tool Quick Comparison

Tool	Dependency Types	Critical Path	Baselines	Starting Price
Onplana	FS, SS, FF, SF + lag	✅	✅	Free
Microsoft Project Desktop	FS, SS, FF, SF + lag	✅	✅	$30 / user / mo
Smartsheet	FS, FF	✅	❌	$9 / user / mo
Monday.com	FS only	❌	❌	$9 / seat / mo
Asana (Timeline)	FS only	❌	❌	$11 / user / mo

Try Onplana's Gantt chart free →

Common Gantt Chart Mistakes

1. Too much detail. A Gantt chart with 300 tasks is a maintenance nightmare. Summarise, group, and only detail the current phase.
2. Ignoring the critical path. If you don't know your critical path, you're guessing about what matters. Every Gantt chart should highlight it.
3. No baselines. Without a baseline, you can't measure schedule performance. Set one before work starts.
4. Treating it as static. A Gantt chart is a living document. If you create it once and never update it, it's art, not a management tool.
5. Overcomplicating dependencies. Start with FS dependencies. Add SS, FF, and SF only when they genuinely reflect real-world constraints. Unnecessary dependencies over-constrain the schedule and create false critical paths.

---

Audit your existing Gantt schedule in 30 seconds Upload an .mpp to the free Schedule Health Check and see the real critical path, dangling tasks, broken dependencies, and per-finding severity. No signup, no credit card. → Run the Schedule Health Check

Onplana offers full-featured Gantt charts with all four dependency types, critical path analysis, baseline tracking, and AI-powered scheduling, starting with a free plan and a one-click .mpp migration path for teams leaving Microsoft Project Online. Create your first Gantt chart →

Related reading: How to Create a Project Plan · Critical Path Method Explained · Work Breakdown Structure Guide · Microsoft Project Online End-of-Life 2026

Microsoft Project Online™ is a trademark of Microsoft Corporation. Onplana is not affiliated with Microsoft.