“Free Gantt Chart Template for Word (Download + Guide)”

Why would anyone build a Gantt chart in Word?

gantt chart template for word is a key topic in modern project management and teamwork. Because the deliverable is a document, not a dashboard. Bid submissions, planning applications, grant proposals, audit packs, and board papers all specify a format, and that format is usually a paginated file with a cover page and a page number in the footer. A screenshot pasted into a report looks like a screenshot. A native table looks like part of the document, edits cleanly, and survives being printed on the client’s monochrome office printer.

There is also a governance reason. Word documents can be locked, signed, versioned, and filed. A shared link to a live board cannot be attached to a contract. When the schedule is evidence, it has to be a file.

The cost is maintenance. Every revision means updating the table by hand or re-linking the data, and every hand update is a chance for the document to disagree with reality. Accept that trade-off deliberately, and keep the Word file’s lifespan short: build it at submission, archive it after approval.

What does the template actually contain?

Six columns of data, then as many date columns as your project needs. The data columns carry the meaning; the date columns carry the picture.

Two details matter more than they look. Set the font size for date columns to 8pt and rotate the week headers 90 degrees, otherwise the header row becomes taller than the data rows. And keep the dependency column as text: Word tables do not compute predecessors, so the column is a human-readable reference, not a formula.

For a 26-week project, 26 columns at 0.28 inches is 7.28 inches. In landscape orientation on A4 with 0.6-inch margins you have about 10.5 inches of usable width, so the six data columns at 6.4 inches plus the bar area fits with roughly 0.8 inches to spare. On US Letter landscape the usable width is 9.8 inches, which is tighter; reduce week columns to 0.24 inches or drop the dependency column to a footnote.

How do you build it, step by step?

1. Set the page first. Layout, Orientation, Landscape; Margins, Custom, 0.6 inches on all sides. Set the footer now, with a field for page numbers, because adding it later shifts your table.
2. Insert the table. Insert, Table, Insert Table, with 8 columns and 2 rows. Do not use a predesigned style yet.
3. Build the header. Type the six data headers and two week headers, then select the week cells and merge them into a single band you can style. Repeat the process per month if you want month groupings above the weeks.
4. Set column widths explicitly. Table Properties, Column, Preferred width in inches. Turn off “Automatically resize to fit contents” under Table, Options, because it will destroy your bar area the first time someone types a long task name.
5. Repeat the header row. Select the header row, Table Properties, Row, and tick “Repeat as header row at the top of each page”. Without this, page two is a wall of unlabelled cells.
6. Set row height. Select all data rows, Table Properties, Row, “Specify height” 0.32 inches, and row height rule “Exactly”. Exactly is important: “At least” lets a long task name stretch one row and make the chart look broken.
7. Fill the data. One row per deliverable, durations in working days, and durations that include any lag you are modelling. A task with a two-day lag after its predecessor should show the lag explicitly in the dependency column rather than being silently absorbed.
8. Draw the bars. Select the cells in a task’s row that fall inside its date range and apply shading: Table Design, Shading, choose your colour. To make bars consistent, use the same colour for all normal tasks, a darker tone for milestones, and a third for the critical path.
9. Add a key. A small two-column table beneath the chart, with shaded sample cells and labels: planned, milestone, critical, complete.
10. Lock the structure. Review, Restrict Editing, “Allow only this type of editing: Filling in forms” while circulating for comment, then unprotect to edit. This prevents a reviewer from deleting a column by accident.

Total build time for a 30-task, 16-week schedule is about 40 minutes the first time and 15 minutes on later revisions once the template exists.

Can you do conditional formatting in Word?

No. Word has no conditional formatting feature, and pretending otherwise wastes an afternoon. There are three honest ways to get bars that react to dates, and they differ mainly in how much automation you can tolerate.

Option 1 — manual shading with a status key. Fully native, zero setup, and the only option if the document must be edited on a locked-down machine. The bar is whatever you shade. It is reliable, and it is manual, which means it drifts the moment dates change and nobody re-shades.

Option 2 — an Excel range with real conditional formatting, linked into Word. This is the method that actually behaves like conditional formatting, because Excel has the feature and Word can display a live copy.

• In Excel, put dates across row 1 (`G1:AF1`) as real dates, formatted `dd mmm`.
• Put Start in column D and Finish in column E, as real dates, not text.
• Select `G2:AF200`, then Home, Conditional Formatting, New Rule, “Use a formula to determine which cells to format”.
• Enter the rule `=AND($D2<=G$1,$E2>=G$1)` and choose a fill colour. Note the mixed references: the date row is locked (`G$1`), the start and finish columns are locked (`$D2`, `$E2`), and the cell reference is free, which is what lets one rule paint a whole row’s bar.
• Add a second rule for milestones where duration equals zero: `=AND($D2=G$1,$E2=G$1,$F2=0)`, with a contrasting shape or colour.
• Copy the range in Excel, then in Word use Home, Paste, Paste Special, “Microsoft Excel Worksheet Object”, and tick “Paste link”. The table now updates when the source changes, and Word shows it with the bars already painted.

The trade-off is fragility. A linked object breaks when the file moves, when a colleague opens the document without the workbook, or when someone “unlinks” it to save space. Send both files, or paste a fresh copy at each submission and archive the pair.

Option 3 — a short macro. For teams that must keep everything inside one `.docx`, a macro that shades cells based on the date in the header row works. Word exposes each cell as `Cell.Range.Text` and each table cell has a `.Shading` property, so a loop that compares a task’s start and finish against the header date can set the fill in one pass. Two cautions: macros mean a `.docm` file, which many corporate mail filters block, and the shading is baked in until the macro runs again. It automates the tedium, not the truth.

How do you calculate dates that match the bars?

Working-day arithmetic is where most Word schedules go wrong, because Word will happily show a finish date that includes a weekend.

Example 1 — duration to finish date. A task starts Monday 2 March 2026 with a duration of 12 working days. Week one gives 5 days (2–6 March), week two gives 10 (9–13 March), and the remaining 2 days land on Monday 16 and Tuesday 17 March. The finish is Tuesday 17 March 2026, not 13 March and certainly not 14 March. Shade eleven cells starting at the week of 2 March.

Example 2 — lag between tasks. Task 4 finishes Friday 13 March and Task 5 has a two-day lag before starting. Two working days after Friday 13 March is Tuesday 17 March, so the bar for Task 5 must start one cell later than a naive “next day” assumption, and the gap must be visible. If you hide the lag inside Task 5’s duration, the critical path total will be wrong by two days and nobody will find it until the schedule slips.

Example 3 — critical path total. A tender requires practical completion within 40 working days. The chain is 6 + 9 + 12 + 4 + 3 = 34 working days. That leaves 6 working days of total float, which is the number to quote in the covering letter. Quote 34 and the client assumes no contingency; quote 40 and you have committed your float without saying so. Show the chain in a bold accent colour and state the float in a footnote.

Example 4 — page planning. Forty tasks at exactly 0.32 inches is 12.8 inches of table, plus a 1.1-inch header and a 2-inch title block. Landscape A4 with 0.6-inch margins gives about 7.5 inches of usable height, so the schedule needs two pages. Set a manual page break after task 22 rather than letting Word split a row, and check that the repeated header lands correctly on page two.

What should you put in the title block and notes?

A schedule appendix without context invites the wrong questions. Add four short lines under the heading: revision and date, prepared by, the basis of the plan (working days, calendar, exclusions), and the status of the data.

The basis line is the one people skip and later regret. “Working days, Monday to Friday, excluding public holidays in England and Wales; durations exclude procurement lead times” answers three arguments before they start. If the plan assumes a client decision by a certain date, say so explicitly and shade that milestone differently, because an assumption buried in a row is an assumption nobody manages.

Why does the Word file go stale so fast?

Because two people now maintain the same information in two places, and one of them is a document. The live plan changes on Tuesday; the Word appendix changes when someone remembers. Within a month the appendix is a historical artefact that still carries an approved stamp, which is worse than no appendix at all.

Three habits reduce the drift. First, generate the document on demand rather than maintaining it continuously. Second, keep the data layer in one file (the linked Excel workbook, if you use Option 2) so there is only one source to correct. Third, add a revision table at the top with a date and a one-line description of what changed, so a reader can see how old the picture is.

When is Word the wrong tool?

Word is wrong when the schedule changes more than once a week, when more than two people edit it, or when the same plan is needed in three formats for three audiences. At that point the document should be generated from a system that holds the work, not typed beside it.

The practical dividing line is revision count. A bid appendix might be revised twice. A delivery schedule is revised weekly. One of those is a document; the other is a live plan that occasionally needs a document.

Where does a live workspace fit?

This is the part where the template stops being enough. In Doitify, tasks, sub-tasks, checklists, owners, due dates, dependencies, milestones, and Gantt charts are the same data, so a schedule view is always current and a document is a print of it rather than a separate file. Disclosure: Doitify is our product.

The relevant advantage is not that it draws a better bar. It is that the numbered task list, the dependency chain, and the workload view update together, and a single task can carry its checklist, documents, and meeting notes. The relevant limitation is that a Word file with a signed cover page is still a legal artefact, and no project tool replaces that. Use both: the workspace for the truth, Word for the submission.

Which mistakes should you avoid?

• Typing dates as text. “02 Mar” typed as a string cannot be compared, sorted, or linked. Use real dates and format them for display.
• Letting Word resize columns. One long task name and the bar area collapses. Turn the option off and set widths manually.
• Shading the wrong cells. A bar that starts one cell late makes a 3-week activity look like a 2.5-week one, and nobody notices in review.
• Mixing calendar and working days. Pick one, state it in the basis line, and apply it consistently to every duration.
• Skipping the repeating header. Page two without headers is unreadable when printed.
• Circulating an unprotected file for comment. Someone will delete a row. Restrict editing.
• Assuming colour survives printing. Test on a monochrome printer; a 20 percent grey fill often prints as white.

Conclusion

A Gantt chart template for Word solves a document problem, not a planning problem. It gives you a landscape table with fixed widths, repeating headers, and shaded cells that reads as part of the submission and prints correctly on the client’s printer.

Build it once, keep the data columns clean, and use real conditional formatting where it exists — in a linked Excel range — rather than pretending Word has it. Then retire the file after approval and keep the live plan somewhere it can change without a new revision number.

If this post on gantt chart template for word was helpful, you might also enjoy Stakeholder Management: Complete Guide and How to Automate Project Documentation (Workflow + Tools).