What Is a Gantt Chart? Definition, Example and Tools

A Gantt chart is a schedule you can read in one glance. Tasks run left to right across a calendar. The length of each bar is the duration. Links between bars show which work is waiting on something else. A milestone is a date with no real duration, such as a launch or a client approval. Project managers use the chart to plan the sequence, spot the tasks that control the finish date, and tell stakeholders whether the deadline still holds.

ClickUp's help center uses the same definition: a Gantt chart plots tasks along a timeline to show start dates, due dates, durations and dependencies. This guide stays on the idea. If you already use ClickUp, ClickUp Gantt chart covers the view, the plan limits and the setup steps. The ClickUp hub is the wider map of that tool.

What is a Gantt chart?

Read a Gantt chart in four parts.

1. Time scale. The header is days, weeks, months or quarters. A week scale is enough for a launch. A quarter scale fits a program with several phases.
2. Task list. Names sit on the left, often grouped by phase or team. Each row is one task, or a summary bar for a group.
3. Bars. A bar starts on the start date and ends on the due date. A longer bar is more calendar time, which is not the same thing as more effort.
4. Dependencies. A link means one task is blocked by another. If the design bar moves, the build bar that depends on it should move too, or the chart is out of date.

Milestones sit on the same timeline as diamonds or markers. They are the dates you report: kickoff, content freeze, launch. The chart does not assign the work by itself. Its value is that a slipped date is visible on the bar.

What does a Gantt chart example look like?

The table below is an example, not a template from a vendor. It is a small website launch. Day 1 is the Monday the project starts. "Depends on" is the task that must finish first.

Task	Start	Finish	Depends on	Milestone
Kickoff	Day 1	Day 1	None	Yes
Write the brief	Day 1	Day 3	Kickoff	No
Design the pages	Day 4	Day 8	Write the brief	No
Build the site	Day 9	Day 15	Design the pages	No
Client review	Day 16	Day 16	Build the site	Yes
Launch	Day 17	Day 17	Client review	Yes

On a chart, kickoff and the two later milestones would be diamonds. The brief, design and build would be bars. The arrows would run brief to design, design to build, build to review, review to launch. There is no gap in that chain, so the launch date is the end of the chain. If design slips from Day 8 to Day 10, build cannot honestly start on Day 9. The finish moves by the same two days unless you overlap work on purpose.

That overlap is a real choice. You might start build on the pages that are already approved while design finishes the rest. The chart should show that as its own dependency. Add one owner per task when you turn this example into a real list. A bar without an assignee is only a date.

When should you use a Gantt chart?

Use a Gantt chart when three things are true.

• The work has an order. Framing before drywall, copy before design, design before build.
• There is a finish date someone will ask about.
• Moving one task can force you to move another.

ClickUp's planning guide gives the same test: a product launch, a construction sequence, or a release tied to a calendar. It also names the poor fits: discovery work, a support queue, and workflows whose priority changes every day. Those are clearer on a board, where the column matters more than the calendar.

Kanban vs Scrum is the board-side choice. Kanban fits a continuous queue. Scrum fits a fixed sprint. A Gantt chart fits the plan across sprints, or across a project that is not a sprint at all. Plenty of teams keep a board for the week and a Gantt chart for the phase. You do not have to pick one view for every kind of work.

Skip the chart when the work is a handful of tasks for one person. A list with due dates is faster to update.

Which tools include a Gantt chart?

Several work-management tools draw this view. The names differ. ClickUp, monday.com and Wrike call it a Gantt chart. Asana calls its schedule view Timeline. Trello offers a Timeline view on paid plans and is built for simpler boards. Prices below were checked in October 2026 and come from each tool's profile on this site.

Tool	Schedule view	Price	A good fit when
ClickUp	Gantt view, plus List, Board, Calendar, Table, Workload and Mind Maps. Free Forever includes 60 Gantt uses. Unlimited and above include unlimited Gantt view.	Free, then $7 per user/month billed annually	You want the chart, docs and time tracking in one Workspace
monday.com	Kanban, Gantt, Calendar and Timeline. Some timeline features sit on higher tiers.	Free for up to 2 seats, then about $9 per seat/month billed annually	You want visual boards and dashboards
Wrike	Gantt charts, boards and tables. The free plan covers essential task management plus board and table views.	Free, then $10 per user/month billed annually	You need resource planning and reporting for a larger team
Asana	Timeline, plus List, Board and Calendar. Timelines are a common reason teams move to a paid plan.	Free for 2 users, then $10.99 per user/month billed annually	You want a polished timeline and clear ownership

ClickUp is the practical pick when you want a Gantt view, docs and time tracking in one Workspace. The learning curve is the trade-off: turn on Gantt after List and Board already make sense. Asana is the calmer rollout if your team wants structure and will pay more per person. monday.com suits people who think in boards first. Wrike suits resource planning for a larger team. Its free plan, in our data, covers board and table views, so confirm Gantt on the plan you intend to buy.

Trello stays the simplest board, from $5 per user/month on Standard. It is limited for complex projects and dependencies, so it is a weak Gantt replacement. Basecamp is easy to share with clients and does not offer Gantt dependencies or workload planning.

If you are still choosing a system, best project management software compares the category. ClickUp for project management is the feature-level look at one tool.

How do dependencies and the critical path work?

A dependency is an order rule. "Build the site" waits on "Design the pages." On the chart, that rule is a line. The direction matters. In ClickUp's example, if task A is blocking task B, the arrow starts at A and ends at B. Other tools draw the same idea with a different arrow style. Read the legend in the product you use before you assume every line means "finish before start."

The critical path is the chain that sets the earliest possible finish. In the website example, every task is on that path, because each one starts the day after the previous one ends. A task you can delay without moving Day 17, such as buying the domain during design, has slack and sits off the path.

You use the path to decide what to protect. A late brief moves the launch. A late domain purchase might not. ClickUp can highlight the path in red and show slack as a dashed bar. The plan limits are in the ClickUp Gantt chart guide.

A few habits keep the chart honest:

• Give every bar a start date and a due date. A due date alone does not show duration.
• Link only real dependencies.
• Mark a few milestones, not every task.
• Update the bar when the date changes.
• Keep the written scope next to the schedule. In ClickUp that is a Doc on the same List. The chart does not hold the reason for the work.

If the work has a sequence and a date you have to defend, a Gantt chart is the right picture. If it is a queue, use a board. ClickUp can hold both views on the same tasks.