How to Create a Basic Gantt Chart in Excel: 7 Easy Steps
Project plans can become difficult to follow when tasks overlap, deadlines move, and several people share responsibility. A plain task list may show what needs doing, yet it rarely reveals how one activity affects the next.
That confusion grows quickly. You may miss a dependency, underestimate a delay, or spend time formatting a complex planning tool when you only need a clear visual timeline.
But here’s the good news: you can create a basic Gantt chart in Excel in about seven steps. With task names, start dates, durations, and a stacked bar chart, you can turn a simple project plan into an easy-to-read schedule.
How to Create a Basic Gantt Chart in Excel
A basic Gantt chart in Excel uses a stacked bar chart with two parts: a hidden starting position and a visible task duration. The hidden section pushes each task to its correct start date, while the visible section shows how long the task lasts.
Here’s why this approach works: Excel does not offer a standard Gantt chart button in its regular chart options. A stacked bar chart provides the same visual effect with a few formatting changes.
Step 1: Build the project schedule
Open a blank Excel workbook and create four columns with these headings:
- Task
- Start Date
- Duration
- End Date
Then add a few sample activities. For example, a website redesign might look like this:
| Task | Start Date | Duration | End Date |
|---|---|---|---|
| Project kickoff | April 1, 2025 | 2 days | April 2, 2025 |
| Content planning | April 3, 2025 | 5 days | April 7, 2025 |
| Design approval | April 8, 2025 | 4 days | April 11, 2025 |
| Development | April 12, 2025 | 10 days | April 21, 2025 |
You can skip the End Date column if you prefer. The chart only needs task names, start dates, and durations. Still, an end-date column helps you check whether the schedule makes sense.
Step 2: Calculate each task’s duration
Duration means the number of working days, calendar days, or elapsed days assigned to an activity. Choose one method and use it consistently.
For a calendar-day schedule, subtract the start date from the end date and add one:
=D2-B2+1
Here, B2 contains the start date and D2 contains the end date. The extra one includes both the first and last day.
For working days, use Excel’s NETWORKDAYS function:
=NETWORKDAYS(B2,D2)
This calculation excludes weekends. You can also add a range of holiday dates when your project schedule needs more precision.
For example, a task running from Monday through Friday has a duration of five working days. A task spanning Saturday and Sunday may have four calendar days but only two working days.
Step 3: Select the task, start date, and duration columns
Highlight the Task, Start Date, and Duration columns. Leave End Date out of the chart selection because it is useful for checking the schedule rather than creating the bars.
If your columns are separated, hold the Ctrl key on Windows or the Command key on Mac while selecting each range.
You can also select the full range first, then remove End Date after inserting the chart. The first method usually creates a cleaner result.
Step 4: Insert a stacked bar chart
Go to Insert, choose Bar Chart, and select 2-D Stacked Bar.
Excel should create two horizontal bar series:
- The first series represents the time before each task begins.
- The second series represents the task duration.
At this stage, the chart may look unusual. The start-date series will appear as colored bars, and the task-duration series will sit beside them. That is expected.
The best part? You are only one formatting change away from a recognizable Gantt chart.
Step 5: Hide the start-date series
Click one of the bars representing the start dates. Open the formatting panel, choose Fill, and select No Fill. Then choose Border and select No Line.
The start-date series will become invisible. It still takes up space and positions each activity correctly, but viewers will only see the colored duration bars.
Choose a clear color for the duration series. Blue works well for general project plans, while different colors can separate workstreams or responsibility areas.
Step 6: Reverse the task order
Excel often places the first task at the bottom of a horizontal bar chart. You can fix that by changing the category order.
Click the vertical task axis, open Format Axis, and select Categories in reverse order.
Your first activity should now appear at the top. This matches the way people usually read a project plan: kickoff first, final delivery last.
Reversing the order may move the horizontal date axis to the top of the chart. If that happens, open the horizontal axis settings and choose the option that places the axis at the bottom.
Step 7: Improve the chart’s readability
Finish the chart by adjusting its size, title, date scale, colors, and spacing.
- Replace the default chart title with a name such as Website Redesign Schedule.
- Widen the chart so task labels and date markers remain easy to read.
- Reduce the gap width between bars to make the schedule look more connected.
- Set the horizontal axis to a suitable minimum and maximum date.
- Choose a readable date format, such as
1-AprorApr 1. - Remove the legend if the chart is self-explanatory.
- Use one color for standard tasks and a contrasting color for milestones or critical activities.
Now you have a basic timeline that shows when each task begins, how long it continues, and where activities overlap.
How the Chart Works Behind the Scenes
The visual effect comes from layering two horizontal values. The first value creates blank space before a task begins. The second value creates the visible task bar.
Imagine a task beginning on April 12. Excel places the hidden start-date segment before the visible duration segment. The visible bar therefore begins around April 12 on the horizontal calendar.
Let me explain with a simple example. If a project starts on April 1 and a task starts on April 8, the task needs seven calendar days of invisible positioning. A five-day duration then appears after that gap.
This technique gives you a quick planning view without requiring specialized scheduling software. It works especially well for small projects with a few tasks and straightforward timing.
How to Add Dependencies and Milestones
A basic chart shows timing, yet it does not automatically explain why one activity must wait for another. You can make relationships clearer with a few planning conventions.
Show dependencies in the schedule
Add a column called Predecessor to record the activity that must finish first. For example, “Development” might depend on “Design approval.”
You can also add short notes beside the chart, such as “Development starts after approved layouts.” This keeps the schedule understandable when several tasks overlap.
Mark milestones clearly
Milestones are important points with little or no duration. Examples include:
- Contract signed
- Design approved
- Testing complete
- Product launched
Give milestones a different color or use a narrow duration. A one-day bar can represent a milestone, although a diamond symbol gives a more traditional project-management appearance.
For a simple chart, color coding is often enough. For instance, use blue for planned work, orange for review points, and green for completed milestones.
How to Update a Gantt Chart When Dates Change
A timeline is useful only when it stays current. The easiest maintenance routine is to update the schedule values first, then check whether the chart reflects the new dates.
If a task slips by three days, change its start date or end date. The duration formula should update automatically when the end date changes.
Here’s a practical example. Suppose content planning was scheduled for April 3 through April 7, but approval takes two extra days. Move the next activity from April 8 to April 10 if it cannot begin until approval finishes.
Keep a separate status column with labels such as Not started, In progress, At risk, and Complete. You can then apply conditional formatting to make schedule health visible beside the chart.
A weekly review works well for small teams. During the review, check three points:
- Which tasks finished during the previous week?
- Which activities changed their expected dates?
- Will any delay affect a milestone or final deadline?
When Excel Is the Right Choice—and When It Starts to Strain
Excel is a practical choice for a short project, a personal plan, or a presentation-ready timeline. For example, a renovation with 12 activities and one coordinator may be easy to manage this way.
The approach becomes harder when many people edit the schedule, tasks change frequently, or several projects share the same resources. Manual formatting can take longer than planning the work itself.
| Situation | Excel may work well | A project platform may help more |
|---|---|---|
| Number of tasks | Small or moderate plan | Large, cross-functional plan |
| Schedule changes | Occasional updates | Frequent changes and dependencies |
| Collaboration | One or two editors | Many contributors and reviewers |
| Reporting | Basic visual timeline | Dashboards, workload views, and live progress |
| Access needs | Simple local planning | Shared access across teams or environments |
You might be wondering: when should you move beyond Excel? Consider the change when status updates become unreliable, dependencies are easy to miss, or you need to ask several people for progress every week.
Natural Project Planning Solution: ONES.com

Value Proposition
ONES.com combines project management and knowledge management in one platform, with ONES Project for project work and ONES Wiki for team knowledge. Each product is sold separately, so you can choose the capability your team needs.
It can suit teams that have outgrown manually maintained timelines and want Jira-compatible workflows, built-in reporting, custom fields, and deployment flexibility.
Core Capabilities
Task timing is difficult to maintain
ONES capability: ONES Project supports structured tasks, milestones, sprint planning, and custom workflows.
Result: Your schedule can reflect the way your team actually moves work from planning through completion.
Dependencies are easy to overlook
ONES capability: You can organize related work within projects and connect activities through workflow relationships.
Result: Teams gain a clearer view of blocked work and activities that must happen in sequence.
Manual status collection takes too long
ONES capability: Built-in reporting gives you project visibility without recreating a chart for every status meeting.
Result: Project leads can review progress, risks, and outstanding work in a shared workspace.
Every team needs different fields
ONES capability: Custom fields and custom workflows let you capture details such as priority, owner, risk level, approval stage, or release target.
Result: Your planning structure can match your process instead of forcing every team into the same template.
Repeated work creates administrative overhead
ONES capability: Automation can handle routine workflow actions and reduce repetitive coordination.
Result: A completed review, approval, or status change can trigger the next step more consistently.
Agile teams need sprint visibility
ONES capability: ONES Project includes sprint management and supports Jira-compatible workflows.
Result: Teams moving from Jira can preserve familiar working patterns while using a broader project environment.
Plugin-heavy setups are difficult to manage
ONES capability: Core project functions, reporting, workflows, fields, and automation are available within the platform.
Result: You may reduce the number of separate plugins needed to coordinate everyday project work.
Restricted environments need deployment control
ONES capability: ONES.com supports Cloud, On-Premise, Private Cloud, and Air-gapped deployments, with full feature parity between cloud and self-hosted versions.
Result: Organizations can choose an operating model that matches their security and infrastructure requirements.
Application Scenarios
Small product team: A team moving beyond manual timeline planning can use sprint management, custom workflows, and reporting to coordinate releases. The project lead can track progress without rebuilding a visual plan after every change.
Enterprise engineering group: A group with Jira-compatible processes may use ONES Project as a Jira alternative while keeping familiar workflows. Custom fields can separate release risk, service area, and approval stage.
Restricted-network organization: A team that cannot use a public cloud environment can deploy ONES.com On-Premise, in a Private Cloud, or in an Air-gapped environment. The team can retain the same core capabilities through a self-hosted deployment.
Common Challenges
The dates appear as large numbers
Problem: Excel may display dates as serial numbers on the horizontal axis.
Solution: Open the axis formatting options and apply a date number format. Choose a compact style such as mmm d to keep labels readable.
The bars appear in the wrong order
Problem: The first activity appears at the bottom, which makes the plan feel reversed.
Solution: Select the task axis and enable Categories in reverse order. Check the horizontal axis position afterward.
Tasks begin on the same date accidentally
Problem: Multiple bars line up even though the schedule should stagger them.
Solution: Check the start-date cells for duplicate values, then confirm that Excel recognizes them as dates rather than text.
The chart becomes too crowded
Problem: Long task names and many activities make the visual difficult to scan.
Solution: Shorten labels, divide the plan into phases, or create separate charts for major workstreams.
Updates do not match real progress
Problem: The timeline shows planned duration but hides how much work has finished.
Solution: Add a status or percent-complete column. Use a second color, a progress marker, or a companion summary to distinguish planned work from completed work.
FAQs
Can I create a Gantt chart in Excel without a template?
Yes. You can build one manually with task names, start dates, and durations. Insert a stacked bar chart, hide the start-date series, reverse the task order, and format the date axis. A template can save setup time, but creating the chart yourself helps you understand how to update it later.
What information do I need before creating the chart?
You need each task’s name, start date, and duration. An end date is helpful because it lets you calculate duration and check the schedule. You may also want task owners, predecessors, milestones, and status labels when the plan involves several people.
How can I show weekends in an Excel timeline?
Use calendar-day durations when weekends should appear in the schedule. If you use NETWORKDAYS, weekends are excluded from the duration calculation. Choose the method that matches your planning rule, then keep it consistent across every activity.
Can I add task dependencies automatically?
A basic Excel Gantt chart does not automatically create dependency links like dedicated project software. You can record predecessors in an extra column and adjust dates manually. For complex relationships, frequent schedule changes, or many linked activities, a project-management platform may be easier to maintain.
How many tasks should a basic chart include?
There is no fixed limit, yet readability declines as the list grows. A chart with roughly 10 to 30 well-named activities is usually easier to review than one containing every small action. Group detailed work under phases or create separate views for different teams.
Conclusion
A basic Gantt chart in Excel is practical when you need a clear timeline for a small or moderately sized project. Create task rows, calculate durations, insert a stacked bar chart, hide the start-date series, reverse the task order, and refine the formatting.
But here’s the truth: the chart is only as useful as the schedule behind it. Keep dates current, mark dependencies, identify milestones, and review changes regularly.
When manual updates begin consuming more time than project planning, consider a structured platform such as ONES.com. You can start with a simple Excel timeline, then move to dedicated project management when collaboration, reporting, automation, or deployment requirements grow.