the honest guide
How to make a Gantt chart in Word
Word has no Gantt chart button — but a page can be talked into one two ways: a table with the cells shaded in, or a stacked bar chart. Here are both, with the exact clicks and an honest note on what a document will never do for you.
We use the same six-week bakery-website plan as our worked examples, our Excel guide, and our Google Docs guide, so you can line them all up side by side.
before you start
A Word Gantt chart is a plan glued into a document
Worth saying up front, because it decides which method to pick: Word is a tool for writing, not planning. A document's whole talent is prose that reflows — type a sentence in the middle and the paragraphs below shuffle down to make room. A Gantt chart is the one thing on the page that won't do that. Whatever you build here is a fixed picture of your timeline, frozen at the moment you drew it and glued to the page around it. Perfect for the project brief or the status report; dead the week after, when the plan has moved and the document has not. So build the version that reads well in the document, and keep the plan that actually changes somewhere else.
Both methods below start from the same raw material: one row per task, with the day it starts and its duration in days. That is the whole plan, and it is small enough to keep in your head:
| Task | Start on day | Duration (days) |
|---|---|---|
| Design | 0 | 14 |
| Build | 7 | 18 |
| Copy | 17 | 7 |
| Photos | 21 | 10 |
| QA & fixes | 31 | 11 |
method 01 — the document-native way
A table with the cells shaded in
The way most Word Gantt charts are actually built, because it needs nothing but the table tools already on the ribbon. Draw a grid with time across the top and tasks down the side, then shade the run of cells each task passes through. A row of coloured cells reads as a bar; the whole grid reads as a plan. It flows with the document, prints in one pass, and never opens a spreadsheet.
-
Insert a table one column wider than your weeks
Insert → Table, and draw a grid with one row per task plus a header row, and one column for the task name followed by one column per week (or per day, if the plan is short). For the six-week plan that is a 6×7 table: a header, five task rows, and seven columns.
-
Label the axes
Type the task names down the first column and the week numbers across the header row. This is the whole chart in outline — task names on the left, time along the top — before a single bar exists.
-
Shade the cells each task runs through
Select the cells in a task's row that fall inside its dates, then Table Design → Shading and pick a fill. A run of shaded cells reads as a bar; the empty cells are the weeks the task is not running. Do this row by row and the grid becomes a Gantt chart.
-
Quieten the grid
Set the table borders to a light grey (Table Design → Borders) so the scaffolding recedes and the shaded bars carry the eye. Shrink the row height and centre the header text — small moves, but they turn a spreadsheet-looking table into a chart.
-
Mark the milestones
A milestone is a moment, not a span, so it has no cells to shade. Drop a symbol into the single cell where it lands — Insert → Symbol → a filled diamond (◆) — or type one. Launch, sign-off, kickoff: one glyph each, sitting on its date.
| Task | Wk 1 | Wk 2 | Wk 3 | Wk 4 | Wk 5 | Wk 6 |
|---|---|---|---|---|---|---|
| Design | Design runs this week | Design runs this week | ||||
| Build | Build runs this week | Build runs this week | Build runs this week | |||
| Copy | Copy runs this week | Copy runs this week | ||||
| Photos | Photos runs this week | Photos runs this week | ||||
| QA & fixes | QA & fixes runs this week | QA & fixes runs this week | ||||
| Launch | ◆ |
Each shaded run is a task; the diamond in week six is the launch milestone. It reads as a plan — but every cell was coloured by hand, and every cell moves by hand.
Fifteen minutes, and it lives right inside the document, flowing with the text and printing cleanly. The catch: the shading is decoration, not data. The grid has no idea Build waits on Design — there are no dependencies — so when Design runs two days long you re-shade Build, then Copy, then Photos, then QA, one selection at a time. The critical path is invisible, and a snapped-to-weeks grid can't show that a task starts on a Wednesday.
method 02 — the chart
The stacked bar chart with an invisible series
Word borrows the same charting engine as Excel and PowerPoint — Insert → Chart opens a little embedded spreadsheet to hold the numbers. So the trick is the one behind almost every spreadsheet Gantt chart: a stacked bar chart where the first segment, the days before each task starts, is made invisible. What is left floats. It gives you exact durations instead of whole weeks, at the cost of a chart object that sits on the page rather than flowing with it.
-
Insert a stacked bar chart
Insert → Chart → Bar → Stacked Bar. Word drops in a sample chart and opens an embedded datasheet — the same Excel grid, in miniature.
-
Replace the sample data
Make the row labels your task names, and use two columns: “Start on day” and “Duration”. Delete Word's spare third series.
-
Make the offset series disappear
Click the first (left-hand) series and set Format Data Series → Fill → No fill. The remaining bars stop touching the axis and float: that is the Gantt chart. Then tick “Categories in reverse order” on the vertical axis so the list reads top-to-bottom.
what Word gives you
Two stacked series: the striped “Start on day” segment, then the real bar.
after fill → no fill
The offset series is still there — it's just invisible. The bars float.
Cleaner than the table, and it reads dates to the day instead of the nearest week. But the chart is an object anchored to the page — it doesn't reflow with the prose around it, and it is still a picture of two columns of numbers. It doesn't know Build waits on Design, so a slip means re-typing every downstream number in the datasheet, and a milestone has no width to draw at all.
the honest part
What a document can't do
Both methods make a convincing chart to read. Neither makes a plan that maintains itself — because a document holds shading and shapes, not the relationships between tasks. The gaps are the same ones you hit in Excel and on a slide, plus one that is unique to living in a page of prose:
- No dependencies. Nothing knows Build waits on Design. An arrow between bars is a drawing, not a link — slip one date and every other bar is re-shaded or re-typed by hand, and the critical path is invisible.
- Nothing reflows. The prose reflows; the chart never does. Shaded cells and chart objects are pixels, not dates — when the plan moves, the document doesn't, and you re-draw it or ship a timeline that quietly went out of date last Tuesday.
- It's built for the report, not the work. Word is a word processor. A Gantt chart's real job — being the live plan the team checks against — isn't something a paragraph and a table can hold.
- Sharing means sending the file. To hand someone the chart you hand them the whole document, or a screenshot of one table. A link that stays current is easier for everyone.
None of this makes Word wrong — for a plan that has to sit inside a written brief or a proposal, a shaded table is genuinely the right tool for that page. It's when the plan keeps moving that the re-shading begins. A good middle path: keep the live plan in a tool that reflows, and paste a fresh picture into the document before each version. Our guide to planning a project walks through where the plan should actually live.
questions we actually get
Word Gantt charts, answered
Does Microsoft Word have a built-in Gantt chart?
No. There is no Gantt chart command anywhere in Word. Every Word Gantt chart is one of two workarounds: a table whose cells you shade in by hand to form bars, or a stacked bar chart borrowed from Word's charting engine with its first series made invisible. Both produce a picture of a plan sitting inside a document — not a plan that maintains itself.
Should I use a table or a chart for a Gantt chart in Word?
For a plan that lives inside a written document — a project brief, a proposal, a status report — the shaded table is usually the better fit: it prints cleanly, wraps with the text, and needs no chart engine. The stacked bar chart looks more polished and is easier to nudge, but it opens an embedded spreadsheet and floats over the page rather than flowing with it. Neither understands your plan; both are drawings you update by hand.
Can a Word Gantt chart show dependencies?
No — not in any live way. A shaded table stores which cells are coloured, and a chart stores two columns of numbers. Neither holds the fact that Build waits on Design. You can draw an arrow between two bars, but it is decoration: move a bar and the arrow stays put, and nothing downstream shifts. When a date slips you re-shade or re-type every affected cell yourself.
How do I add milestones to a Word Gantt chart?
Type or insert a symbol. A milestone has no duration, so there is nothing to shade — instead drop a filled diamond (Insert → Symbol → ◆) into the single cell where the milestone falls. In the stacked-bar method a milestone is fiddlier still: you add it as a separate one-point series, which is more trouble than dropping a glyph into a table cell.
What's the fastest way to make a Gantt chart?
Describe the plan in a sentence and let ganttchart.ai draw it — tasks, durations, dependencies, and milestones included. The Word methods on this page take fifteen to thirty minutes and have to be re-shaded or re-typed by hand whenever a date moves; the sentence takes about ten seconds, and the chart is a shareable link you can paste into the document instead of a picture that goes stale.
New to the vocabulary? Every planning term on this page is defined in the plain-English glossary.
A chart you can paste in and keep live
Describe your project in plain English and get a shareable, editable Gantt chart in seconds — dependencies and milestones included. Paste a fresh picture into the document, and keep the real plan a link away.