Guide · 2026-09-10

How to Create a Gantt Chart in Tableau: A Step-by-Step Guide

Building a Gantt chart in Tableau can feel harder than it should. You may have task names, start dates, end dates, and progress values, yet still see a confusing timeline. A small setup mistake can turn planned work into unreadable bars, hide delays, or place tasks in the wrong order.

That frustration grows when stakeholders need a clear answer quickly. Which tasks are active? What finishes this month? Where is the schedule slipping? Tableau can answer those questions when you structure the view correctly.

Here’s the practical solution: create a calculated duration, place tasks on rows, use a Gantt mark, and size each bar by duration. Then add filters, labels, and formatting that help people read the schedule at a glance.

How to Create a Gantt Chart in Tableau

A Gantt chart in Tableau is a timeline view that represents each task with a horizontal bar positioned by its start date and sized by its duration. Follow these steps to build a clear project schedule.

Step 1: Prepare the Required Fields

You need at least three useful fields:

Helpful additions include project phase, owner, priority, status, percent complete, and milestone type. These fields let you filter the schedule and explain what each bar means.

For example, your project may include the following values:

Task Start date End date Status
Requirements review January 8 January 12 Complete
Interface design January 15 January 26 In progress
User acceptance testing February 5 February 16 Not started

If you only have start and end dates, create a duration calculation before building the view.

Step 2: Create a Duration Calculation

In Tableau, open the calculation editor and create a field such as:

DATEDIFF('day', [Start Date], [End Date]) + 1

The + 1 includes both the starting and ending day. Without it, a task running from January 8 through January 12 appears four days long instead of five.

If your schedule uses working days, calendar days may produce misleading bars. You can use a working-day calendar or create a calculation that excludes weekends and holidays.

Give the calculated field a clear name, such as Duration Days. A descriptive name makes later editing easier, especially when several calculations appear in the workbook.

Step 3: Place the Start Date on Columns

Drag Start Date to the Columns shelf. Tableau will create a time axis.

Choose a date level that matches the schedule. Use continuous days for short implementation plans, weeks for monthly programs, and months for long initiatives.

A continuous date axis usually works best because it preserves the spacing between dates. A discrete date can divide the view into separate headers, which makes duration bars harder to interpret.

To change the date level, select the date pill and choose a suitable option. You can also choose whether Tableau displays the date continuously or discretely.

Step 4: Place Tasks on Rows

Drag the task field to the Rows shelf. Each task should appear on its own row.

Tableau may sort tasks alphabetically. That order rarely matches the project sequence. Use a task order field, phase order, or manual sorting so the schedule follows a logical path.

For example, a product launch may follow this sequence:

  1. Requirements
  2. Design
  3. Development
  4. Testing
  5. Launch

Sorting by task name could place “Launch” before “Requirements.” Sorting by a numeric sequence keeps the schedule readable.

Step 5: Change the Mark Type to Gantt Bar

On the Marks card, open the mark type menu and select Gantt Bar. Tableau will display a mark for each task.

At first, the bars may have equal lengths. That happens because Tableau needs a field that controls each mark’s size.

The start position comes from the start date. The bar length comes from the duration value.

Step 6: Add Duration to Size

Drag Duration Days to Size on the Marks card. Each bar will now represent the time between the task’s start and finish.

Adjust the size slider until the bars are visible without overwhelming the timeline. Narrow bars work well for dense schedules. Wider bars improve readability when the view contains fewer tasks.

Check several tasks manually. A five-day activity should appear shorter than a twelve-day activity. If every bar looks identical, verify that the duration field is continuous and placed on Size.

Step 7: Add Status or Phase to Color

Drag Status or Phase to Color. This gives the schedule a visual layer that helps people understand progress.

A simple status palette might use:

Use colors consistently. If red means blocked in one dashboard and delayed in another, people may misread the schedule.

Step 8: Add Labels and Tooltips

Drag the task field to Label if the task names are not already visible. You can also add owner, percent complete, or end date.

Keep the chart uncluttered. Show the most important information directly on the view and place supporting details in the tooltip.

A useful tooltip could display:

Use a custom tooltip to write a short, readable summary. For example, “Interface design runs from January 15 to January 26 and is 60 percent complete.”

Step 9: Add Filters for Practical Analysis

Drag fields such as project, owner, phase, or status to the Filters shelf. Then show the filter controls so viewers can narrow the schedule.

A project manager may filter to one owner. An executive may filter to delayed work. A team lead may focus on the next two weeks.

A date filter can also reduce visual noise. Showing a twelve-month schedule on one screen often makes individual tasks too small to read.

Step 10: Format the Timeline

Use formatting to guide attention toward schedule risk and upcoming work.

Test the chart at the size people will actually use. A view that looks excellent on your screen may become crowded when embedded in a dashboard.

How the Tableau Gantt Chart Works

The chart combines position, length, and appearance. The start date positions a mark along the horizontal axis. The duration controls its length. The color communicates a category such as status or phase.

This is similar to placing strips of tape on a calendar. A strip begins on a specific day and continues for a defined number of days. Tableau creates that effect through the Gantt mark type.

Start Date Controls Position

When the start date sits on Columns, each task begins at the correct point on the timeline. A task starting on March 10 appears after a task starting on March 1.

If you place an end date on Columns instead, the bars begin at task completion dates. That may produce a technically valid view with the wrong visual meaning.

Duration Controls Length

The duration field determines how far each bar extends. A two-day task receives a shorter mark than a twenty-day task.

Use consistent units. Mixing hours, days, and weeks in one calculation can create distorted results. Convert all durations to one unit before adding them to Size.

Color Adds Context

Color can show status, phase, owner, risk, or priority. Select one main meaning for color in each view.

For example, color by phase helps explain the project structure. Color by status helps reveal progress. Trying to show both through color creates confusion, so use shape, label, or a separate filter for the second category.

Common Tableau Gantt Chart Variations

Once the basic view works, you can adapt it for different planning needs. The right variation depends on the question your audience needs answered.

Project Schedule Gantt Chart

This version displays tasks across a complete project. Add phase, owner, and status fields to help people understand responsibility and progress.

For example, a software release may use phase colors and show milestones as separate marks. A filter can isolate development tasks while leaving testing activities hidden.

Resource Planning Timeline

Place a team member or department on Rows instead of task. Then add task to Detail or Label.

This view shows when a person has several activities at once. Overlapping bars can reveal capacity pressure that a task-only view hides.

Milestone Gantt Chart

Milestones have little or no duration. A standard bar may make them difficult to see.

Create a separate milestone field or use a different mark type. You can add milestone dates as points, reference lines, or a second worksheet in the dashboard.

Percent-Complete Gantt Chart

A standard Gantt bar shows scheduled duration. It does not automatically show how much work is complete.

You can create a second bar layer or use a dual-axis design to display progress inside the scheduled bar. Keep the progress treatment visually lighter than the main schedule.

Baseline Versus Actual Timeline

To compare planned and actual timing, create fields for planned start, planned duration, actual start, and actual duration.

Use one layer for the baseline and another for actual work. A difference between the two makes schedule variance easy to spot.

How to Improve Accuracy and Readability

A technically correct chart can still fail if people cannot interpret it quickly. Review the schedule through the eyes of someone who did not build it.

Validate Dates Before Designing

Check for missing starts, end dates earlier than start dates, and unusually long durations. These issues can create bars that disappear, reverse, or stretch across the entire view.

Create a simple exception calculation for invalid records. Then filter those records into a review view instead of allowing them to distort the main schedule.

Choose the Right Time Granularity

Daily labels suit a two-week sprint. Weekly labels suit a quarterly program. Monthly labels suit a multiyear roadmap.

If the timeline is too detailed, viewers spend more effort reading the axis than understanding the schedule. If it is too broad, short activities become invisible.

Limit the Number of Colors

A palette with twelve status colors forces people to remember too much. Use a small set of meaningful categories.

Reserve strong colors for attention-worthy conditions such as blocked work or missed dates. Use neutral tones for routine activities.

Show the Current Date

A reference line for today helps viewers distinguish past, current, and future work. It is especially useful in recurring project reviews.

For example, a vertical line on April 15 immediately shows whether a task should already be complete. Without that line, the audience must estimate the current position from the calendar.

Test Filters and Tooltips

Apply every filter before publishing the dashboard. A filter may remove the only task carrying a required legend category or create an empty view.

Hover over short, long, delayed, and completed tasks. Each tooltip should display accurate dates and useful context.

Natural Project Timeline Solution: ONES.com

Tableau is useful for visual analysis and reporting. ONES.com supports the work that creates and updates the project schedule. It combines project management and knowledge management in one platform, with ONES Project available as a Jira alternative and ONES Wiki available as a Confluence alternative. They are sold separately.

ONES.com product screenshot

The practical value comes from connecting planning activity with team knowledge. You can manage tasks, approvals, sprints, and project information in a structured workspace, then use reporting to inspect progress.

Value Proposition

ONES.com helps teams manage project timelines in one structured environment. It can reduce the manual coordination required before a schedule becomes useful for reporting.

Core Capabilities

Application Scenarios

Software release planning: A product team can manage requirements, development tasks, testing work, and release approvals in ONES Project. A reporting view can then show schedule progress for leadership reviews.

Air-gapped engineering programs: An organization with restricted network requirements can deploy the platform in an air-gapped environment. Teams can continue managing tasks and workflows without using a public cloud connection.

Cross-functional launches: Marketing, engineering, operations, and support can use custom fields and workflows for their responsibilities. ONES Wiki can hold launch guidance while ONES Project tracks execution.

Common Challenges When Building a Tableau Gantt Chart

Bars Have the Same Length

Problem: Every task appears to last the same amount of time.

Solution: Confirm that the duration calculation returns a numeric value. Place that field on Size and check whether it is aggregated correctly.

Tasks Appear in the Wrong Order

Problem: Tableau sorts task names alphabetically.

Solution: Add a numeric sequence field and sort the task dimension by that sequence. Use phase order when the chart follows a delivery framework.

The Timeline Looks Too Crowded

Problem: Labels overlap and short bars become hard to see.

Solution: Filter the date range, increase row height, reduce label content, or use a higher-level date such as week or month.

Weekends Distort the Schedule

Problem: Calendar-day durations make work appear longer than working-day schedules.

Solution: Use a working-day calculation or a calendar that excludes weekends and holidays. State the convention clearly in the dashboard.

Progress Is Misunderstood

Problem: Viewers assume the bar length represents completed work.

Solution: Label the view as planned duration, then add a separate progress indicator. Include percent complete in the tooltip or a second visual layer.

FAQs

Can I create a Gantt chart in Tableau without an end date?

Yes. You can create one with a start date and duration value. Tableau needs the start date to position each bar and the duration to control its length. If you only have an end date, calculate duration from the start and end dates first. Check whether the calculation should count calendar days or working days.

Why are my Tableau Gantt bars not showing?

Several settings can cause this issue. Confirm that the mark type is Gantt Bar, the start date is on Columns, and the duration field is on Size. Also check for null dates, zero durations, and filters that remove every task. Enlarging the Size slider can help when bars are present but too narrow to notice.

How do I show milestones in a Tableau timeline?

Milestones usually need a separate visual treatment because they have little or no duration. Create a milestone field, then display milestone dates with a point, shape, or reference mark. You can also combine a task Gantt worksheet with a milestone worksheet in one dashboard. Add labels so viewers understand what each milestone represents.

Can Tableau show planned and actual project dates together?

Yes. Create separate fields for planned dates and actual dates, then use layered marks or a dual-axis design. Show the planned schedule with a lighter color and actual work with a stronger color. Add a variance calculation to identify tasks that started late, finished late, or exceeded the planned duration.

How can I make a Tableau Gantt chart easier to read?

Start with a focused date range and a logical task order. Use a small color palette, readable labels, and a reference line for today. Put detailed information in tooltips rather than showing every field on the chart. Test the view with real filters and at the size used by your audience.

Conclusion

Creating a Gantt chart in Tableau comes down to four essentials: position tasks with a start date, size bars with duration, organize rows logically, and add only the context people need.

Begin with a small schedule containing task names, dates, and durations. Validate the results before adding status colors, filters, milestones, or progress indicators.

But here’s the truth: a polished chart cannot repair unclear planning. Keep project work, ownership, approvals, and schedule rules organized before visualizing them.

Tableau can then turn that organized project information into a timeline people understand quickly. ONES.com can support the planning workflow behind it, especially when your team needs structured project management, reporting, knowledge management, or flexible deployment options.