How to Make a Gantt Chart in Microsoft Word: 7 Steps [2026]
Planning a project in Microsoft Word can feel harder than the work itself. You may have a task list, several deadlines, and multiple people involved, yet still lack a clear view of how everything fits together. A plain list hides dependencies, overlapping work, and schedule risks. As the project grows, small changes can force you to rebuild the entire plan.
That frustration is exactly why a Gantt chart helps. It turns activities into timeline bars, so you can see what starts when, which tasks depend on others, and whether the final deadline is realistic. You do not need specialized software for a simple schedule. With Word, a table or stacked bar chart can create a practical project timeline in minutes.
In this guide, I’ll show you how to do a Gantt chart in Microsoft Word using seven clear steps, explain which method works best, and cover the limitations you should know before choosing Word.
How to Make a Gantt Chart in Microsoft Word
The quickest method is to create a stacked bar chart in Word, use one series for the waiting period, and use another for the task duration. Then make the waiting series invisible so the remaining bars look like a Gantt chart.
Before you begin, prepare four pieces of information for every activity:
- The task name
- The planned start date or start offset
- The expected duration
- The person or team responsible
For a small project, you can also build the timeline with a formatted table. The chart method is easier to adjust when several activities have different start dates.
Step 1: List the project activities
Start by writing every major activity in a logical order. Keep each task specific enough to have its own start and finish point.
For example, a website launch might include:
- Confirm requirements
- Create page layouts
- Write website copy
- Build the pages
- Test the website
- Approve the launch
Avoid vague entries such as “work on website.” That activity could last one day or three weeks, which makes the schedule difficult to manage.
Break large work into milestones and task groups. “Design website” is broad, while “approve homepage layout” gives you a clear completion point.
Step 2: Add start dates and durations
Next, decide when each activity starts and how long it should take. You can use calendar dates or numbered days from the project start.
Here is a simple planning example:
| Task | Start offset | Duration |
|---|---|---|
| Confirm requirements | 0 | 3 days |
| Create page layouts | 3 | 5 days |
| Write website copy | 5 | 4 days |
| Build the pages | 8 | 7 days |
| Test the website | 15 | 3 days |
| Approve the launch | 18 | 1 day |
The start offset shows how many days pass before an activity begins. The duration shows how long that activity remains active.
Use working days if your team does not work weekends. Otherwise, your timeline may appear shorter than the real schedule.
Step 3: Insert a stacked bar chart
Open Microsoft Word and place your cursor where you want the timeline to appear. Then follow these steps:
- Open the Insert tab.
- Select Chart.
- Choose Bar from the chart categories.
- Select Stacked Bar.
- Click OK.
Word will insert a chart and open a small editing grid. You can replace the example values with your task names, start offsets, and durations.
Do not choose a regular bar chart. A regular bar chart shows only one value per task, while a stacked bar chart lets you combine the waiting period and active work.
Step 4: Enter the task schedule
Replace the example labels with your activities. Use three columns in the chart’s editing grid:
- Task: the activity name
- Start: the number of days before the activity begins
- Duration: the number of days needed to complete it
For the website example, “Build the pages” would have a start value of 8 and a duration value of 7.
Keep the start and duration values numeric. If you type “8 days” instead of “8,” Word may treat the entry as text and display the chart incorrectly.
After entering the schedule, close or minimize the chart’s editing grid. You can reopen it later by selecting the chart and choosing Edit Data.
Step 5: Hide the start-offset series
At this point, each activity has two colored sections. The first section represents the waiting period before work begins. The second represents the task duration.
To create the Gantt effect, make the start-offset series invisible:
- Select one of the left-side chart sections.
- Open the Format tab.
- Choose Shape Fill.
- Select No Fill.
- Choose Shape Outline, then select No Outline.
The visible duration bars should now appear to begin at different points along the timeline.
If the entire chart changes color, you selected the whole series rather than one individual bar. Click the same series again to select the series, then apply the formatting.
Step 6: Reverse the task order
Word may display the first activity at the bottom of the chart. That makes the timeline harder to read because the schedule appears upside down.
To correct the order:
- Right-click the vertical task axis.
- Select Format Axis.
- Open Axis Options.
- Enable Categories in reverse order.
The first task should now appear at the top, followed by the remaining activities in planning order.
Check the horizontal axis too. If the timeline begins at an unexpected point, adjust the minimum and maximum bounds so the chart starts near the project’s first day and ends after the final task.
Step 7: Format and review the chart
Finish by improving readability. A useful Gantt chart should be understandable without a long explanation.
- Use a clear title, such as “Website Launch Schedule.”
- Choose one strong color for active work.
- Remove unnecessary chart elements.
- Widen the chart so task names remain readable.
- Use consistent date or day labels.
- Add milestone markers when an approval or launch date matters.
Review the chart against the actual project plan. Confirm that dependent activities do not begin before the work they need is complete.
For example, testing should not start before the build is finished unless your team deliberately tests each completed section as it becomes available.
Which Word Method Should You Use?
Word gives you two practical ways to create a timeline: a stacked bar chart and a formatted table. The right choice depends on how often you expect the plan to change.
| Method | Best for | Main limitation |
|---|---|---|
| Stacked bar chart | Visual schedules with different start dates | Can require manual formatting |
| Formatted table | Simple plans with short timelines | Harder to update when dates move |
| Word template | Quick visual planning with a familiar layout | Layouts may not match your project |
A stacked bar chart works well when you need to show overlap. For example, copywriting and layout design can run during the same week while development starts later.
A table is often better for a one-page plan with five or fewer activities. You can shade cells by day or week, add a legend, and print the result without dealing with chart settings.
Here’s why: a chart communicates timing more naturally, while a table gives you more control over labels, notes, and responsibilities.
How to Build a Gantt Chart with a Word Table
If you prefer a table, create one column for task names and one column for each time period. Use days for short projects and weeks for longer plans.
For example, a four-week marketing campaign could use these columns:
- Activity
- Week 1
- Week 2
- Week 3
- Week 4
Insert a table from the Insert tab, then shade the cells where each task is active. A row for “Write campaign copy” might have shaded cells in Weeks 1 and 2. A row for “Launch campaign” might have one shaded cell in Week 4.
You can add symbols for milestones, such as a diamond or bold letter M. Add a small legend below the table so anyone reading it understands the colors and symbols.
The table method is easy to print and annotate. However, changing a deadline may require you to recolor several cells manually, especially when the plan covers many weeks.
How to Make the Timeline Easier to Read
A Gantt chart should answer three questions quickly: what needs to happen, when it happens, and how activities relate to one another.
Use a sensible time scale
Do not show daily labels for a six-month project. The chart will become crowded and difficult to scan. Use weeks or months for longer schedules.
For a two-week event, daily columns make sense. For a product release spanning six months, monthly labels provide a clearer overview.
Separate phases visually
Group related work under phase labels such as Planning, Design, Development, Testing, and Launch.
You can use different shades for phases while keeping the task bars consistent. Avoid using a different color for every activity, because too many colors make the chart harder to interpret.
Mark milestones clearly
A milestone represents an important point rather than a period of work. Examples include contract approval, design sign-off, testing completion, and public launch.
Use a diamond, vertical line, or bold label. A milestone helps you see whether the project is approaching a decision point without adding another long bar.
Keep the chart to one page when possible
A timeline that spreads across several pages loses much of its value. Reduce unnecessary text, switch the page to landscape orientation, or use a weekly scale.
For a detailed schedule, keep the main chart concise and add supporting task notes beneath it. This preserves the visual overview without forcing every detail into the timeline.
Common Mistakes When Creating a Word Gantt Chart
Word can produce a useful schedule, but manual control creates opportunities for errors. Watch for these problems before sharing the chart.
Using dates as plain text
If you type dates into a chart without converting them into useful numeric positions, Word may not space the bars correctly. Start offsets are often simpler for a basic chart.
Forgetting task dependencies
A chart can look polished while still showing an impossible sequence. If approval must happen before production, production should not begin first.
Making every bar the same color
Uniform colors are clean, but they may hide ownership or project phases. Use a restrained color system when responsibilities or stages matter.
Adding too much detail
Listing every small action can make the timeline unreadable. Show major tasks in the main chart and keep minor actions in a separate task list.
Failing to update the chart
A timeline becomes misleading when deadlines change but the chart remains unchanged. Assign one person to review it after major decisions or at a regular planning meeting.
When Word Stops Being the Right Choice
Word is suitable for a small, mostly static schedule. It becomes less convenient when several people need to update tasks, track progress, or coordinate dependencies.
Imagine a project with 80 activities, four teams, and weekly deadline changes. Each change may require editing chart values, checking overlaps, correcting labels, and redistributing the updated version.
That manual work increases the chance of conflicting copies and missed updates. A dedicated project management platform can connect tasks, owners, discussions, progress, and reports in one workspace.
You might be wondering: when should you move beyond Word? Consider switching when the plan needs live collaboration, automated reminders, task history, dashboards, approvals, or multiple project views.
Project Timeline Solution: ONES.com

Value Proposition
ONES.com combines project management and knowledge management in one platform. For teams that have outgrown a manually maintained Word timeline, it provides a more connected way to plan work, monitor progress, and preserve project knowledge.
ONES Project is a Jira alternative for project planning and delivery, while ONES Wiki supports team knowledge management as a Confluence alternative. They are sold separately.
Core Capabilities
- Scattered task planning: ONES Project brings tasks, owners, deadlines, and priorities into structured project workspaces, helping you see responsibility clearly.
- Manual schedule maintenance: Custom workflows and fields let you represent project stages, risk levels, approvals, and other planning details without rebuilding a chart after every change.
- Limited progress visibility: Built-in reporting helps you review progress, overdue work, workload, and delivery trends from connected project activity.
- Complex sprint planning: Sprint management supports iterative teams that need to plan short cycles, assign work, and review completed activities.
- Repetitive project administration: Automation can trigger routine actions, reduce manual status changes, and keep recurring workflows consistent.
- Plugin-heavy project setups: Jira-compatible workflows can help teams familiar with Jira-style planning transition without abandoning familiar delivery patterns.
- Disconnected team knowledge: ONES Wiki gives teams a central knowledge space for procedures, decisions, requirements, and project guidance.
- Restricted deployment requirements: ONES.com supports Cloud, On-Premise, Private Cloud, and Air-gapped deployments.
- Uneven feature availability: The self-hosted version provides full feature parity with the cloud version, so deployment choice does not require giving up core functionality.
ONES.com also offers a free plan for up to 30 seats. You can select the deployment approach that fits your security and infrastructure requirements.
Application Scenarios
Software release planning: A product team can manage requirements, sprints, testing, approvals, and release work in ONES Project. Instead of manually shifting bars in Word, the team can review live task status and reports.
Engineering work in a restricted environment: A team with air-gapped infrastructure can use a self-hosted deployment while maintaining project workflows, fields, and reporting. This suits environments where cloud access is restricted.
Marketing campaign coordination: A marketing team can plan campaign activities in ONES Project and preserve messaging guidelines, approval procedures, and lessons learned in ONES Wiki.
The best part? You can start with a simple project structure and add workflow rules, reporting, and knowledge pages as the team’s coordination needs grow.
Common Challenges and Practical Fixes
Challenge: The chart becomes too wide
Fix: Change the scale from days to weeks, switch to landscape orientation, and remove labels that do not support a planning decision.
Challenge: Dates shift frequently
Fix: Use Word for a high-level presentation, then maintain the working schedule in a system that can update assignments, dependencies, and progress more efficiently.
Challenge: People cannot tell who owns each task
Fix: Add an owner column beside the task names or use a consistent color key. Every major activity should have one clearly accountable person or team.
Challenge: The timeline shows activities but no dependencies
Fix: Add predecessor notes, arrows, or dependency fields. If the relationship is complicated, use a project management platform with native dependency tracking.
Challenge: The chart looks attractive but does not support decisions
Fix: Add milestone markers, current status, and the next decision point. A useful schedule should help you identify delays and choose an action.
FAQs
Can I create a Gantt chart in Word without Excel?
Yes. Word includes a chart feature that can create a stacked bar chart without requiring Excel as a separate planning tool. You can also build a timeline with a formatted table. The stacked bar method is better when activities start at different times, while a table works well for a short, mostly static schedule.
What is the easiest Gantt chart method in Microsoft Word?
The stacked bar chart method is usually the easiest for a visual schedule. Insert a stacked bar chart, enter start offsets and durations, hide the offset series, reverse the task order, and format the timeline. A table may be faster for a very small plan with only a few activities and weekly time periods.
How do I show overlapping tasks?
Give each activity its own start offset and duration. When two tasks have overlapping date ranges, their visible bars will occupy the same part of the timeline. For example, copywriting can begin on Day 5 while layout work continues through Day 8. Use separate rows so the overlap remains easy to see.
Can Word automatically update a Gantt chart when dates change?
Word does not provide the same scheduling automation as dedicated project management software. You can edit chart values manually, but changes to one activity may require you to review several others. For a simple plan, that is manageable. For a complex or frequently changing project, a connected planning platform is more practical.
Should I use a Word template?
A Word template can save time when you need a quick presentation-ready schedule. Check whether its timeline scale, task rows, labels, and colors fit your project before committing to it. Templates often work best for a basic overview. They may become restrictive when you need dependencies, progress tracking, or frequent updates.
Conclusion
You can create a useful Gantt chart in Microsoft Word by listing your activities, adding start offsets and durations, inserting a stacked bar chart, hiding the offset series, reversing the task order, and reviewing the finished timeline.
For a short project, a formatted table may be enough. For overlapping activities, the stacked bar approach gives you a clearer visual schedule. Keep the chart focused on major tasks, milestones, owners, and decisions.
But here's the truth: Word is strongest when the schedule is small and changes are limited. If your project requires live collaboration, automated workflows, reporting, dependencies, or restricted deployment options, a dedicated platform such as ONES.com can support the work beyond a manually maintained timeline.
Start with the simplest method that solves your planning problem today. Then move to a connected project workflow when updates, coordination, and project scale make manual chart editing too costly.