The short version: you build a Gantt chart in a spreadsheet by listing your tasks with start dates and durations, then turning that data into a stacked bar chart where the first series is hidden. It takes about twenty minutes to set up and works brilliantly for anything under fifteen tasks. Past that, and once real dependencies show up, the spreadsheet stops being a project plan and starts being a second job.
Why I still use a spreadsheet for this, even now
I run a marketing and AI consultancy, and I have paid for Asana, Monday, Trello, and about four other tools over the last decade. For a proper multi-team rollout, I use one of those. But for a client launch with one team, six weeks, and a deadline, nine times out of ten I open Google Sheets. It is free, everyone already has it, and I do not have to onboard anyone onto yet another login they will forget by Thursday.
A Gantt chart, if you have never made one, is just a bar chart where each bar represents a task, its length shows how long the task takes, and its position shows when it happens. The version bankers and project managers use with Microsoft Project has dependencies, resource levelling, and critical path calculations built in. The spreadsheet version has none of that. It is a picture, not a system. That distinction matters more than most guides admit, and I will come back to it.
What you need before you open the spreadsheet
Do this bit on paper first, or you will end up rebuilding the sheet three times.
- A finished task list, broken down to the level you manage at. “Write website copy” is fine. “Write website copy for homepage, services page, about page, contact page” as four separate lines is better if you need to track them separately.
- A realistic start date and duration for each task, in days. Not hours, not weeks, days. It is easier to convert later than to fix a chart built on the wrong unit.
- A rough sense of which tasks depend on which. You will not build this into the chart directly (spreadsheets do not do that well), but you need it in your head so your dates make sense.
If you have not planned a project timeline before, it is worth reading through how to plan a project timeline using a spreadsheet template before you build the chart itself, because the chart is only as good as the plan underneath it.
Step by step: building the chart in Excel or Google Sheets
The method is identical in both tools, the menu names just differ slightly. I will flag both.
- Set up five columns. Task Name, Start Date, Duration (Days), End Date, % Complete. Put these in row 1 as headers.
- Fill in your tasks. One row per task. If you have 12 tasks, you will have rows 2 through 13.
- Calculate End Date with a formula. In the End Date column, type
=B2+C2(assuming Start Date is column B and Duration is column C). Copy it down for every row. This saves you from manually re-dating everything when one task slips. - Select your data. Highlight the Task Name, Start Date, and Duration columns. Do not include the End Date or % Complete columns in this selection, or the chart will get confused.
- Insert a stacked bar chart. In Excel: Insert > Charts > Bar Chart > Stacked Bar. In Google Sheets: Insert > Chart, then change the chart type to Stacked Bar Chart in the panel on the right.
- Reverse the task order. By default the chart usually puts your first task at the bottom. Right-click the vertical axis, choose Format Axis, and tick “Categories in reverse order” so your first task appears at the top, reading like a normal plan.
- Hide the Start Date bar. This is the trick that makes a stacked bar chart look like a Gantt chart. Click on the Start Date series in the chart, open its fill options, and set the fill to “No fill” (Excel) or transparent (Sheets). What is left visible is only the Duration bar, which now floats at the correct starting point because the invisible Start Date bar is pushing it there.
- Add a date axis. Format the horizontal axis to show dates rather than raw numbers, and set sensible intervals, weekly for a two-month project, monthly for anything longer than six months.
- Colour code by owner or status. I use one colour per team member, or red/amber/green for status if it is a one-person project. Select each bar individually and change its fill.
That is the whole build. I have timed myself doing this for a 10-task plan and it took 22 minutes, including fixing my own colour choices twice because the first palette looked like a toddler’s toy box.
A launch that went sideways because of this exact chart
Two years ago I was helping a small ecommerce client plan a product launch. Eighteen tasks, eight weeks, three people involved: her, a freelance designer, and a copywriter (me, doing double duty). I built the spreadsheet Gantt chart in the way above, colour coded by person, and it looked great. Everyone could see at a glance who was doing what and when.
For the first three weeks it worked exactly as intended. Then the designer got delayed by a client emergency elsewhere, her task slipped by four days, and because two other tasks depended on her artwork being finished, the whole back half of the plan needed to shift. In Asana or Monday, that is a five-second drag on one bar and everything downstream moves with it. In the spreadsheet, I had to manually recalculate and retype eleven start dates, because the chart has no concept of “this task cannot start until that one finishes.” It just draws whatever dates you type in.
It took me forty minutes to fix a four-day slip. That is the trade-off nobody tells you about when they show you a pretty finished chart in a tutorial.
Where the spreadsheet approach quietly breaks down
Here is the bit most guides on this topic skip over, because it makes the tool look less impressive: a spreadsheet Gantt chart has no dependency logic, no automatic rescheduling, and no way to flag a resource conflict. It is entirely manual. Every time a date changes, you are the one updating it, and if two tasks silently overlap because you moved one without checking the other, the chart will not warn you. It will just sit there looking correct while being wrong.
This is fine, fine, for a plan under about 15 tasks with one or two people and few real dependencies. Past that point, the maintenance overhead grows faster than the value the chart gives you. I have seen founders spend more time each week fixing their Gantt chart than they spend doing the tasks on it, which defeats the entire purpose of having a plan. If your project has more than one team, more than about three weeks of interlinked dependencies, or people who need to see live status without you emailing them a new screenshot, a spreadsheet is the wrong tool and no amount of clever formatting fixes that.
For that stage, something built for actual project tracking makes more sense, and I have written about the options in the best work OS platforms for running a more agile business. If it is just you managing the whole thing solo, the calculation is different again, and I would point you to how to choose project management software when you work alone before you spend money on tools built for teams you do not have.
Formatting choices that matter
A few small decisions make the difference between a chart people use and one they ignore after week one.
- Keep task names short enough to read without wrapping onto three lines. Eight words maximum.
- Add a vertical line marking “today” using a scatter series or a conditional format, so anyone glancing at the chart instantly sees what is late.
- Do not colour code by more than one variable. Pick person or status, not both, or the chart turns into a puzzle.
- Freeze the header row and the task name column so the chart stays visible while people scroll through longer plans.
If you want the exact formulas and a downloadable template rather than building from scratch, I have a fuller walkthrough in how to build a Gantt chart in Excel to plan a project, which covers conditional formatting for automatic colour changes based on status.
What I use spreadsheets for beyond this
Once you are comfortable turning a plain table into a visual timeline, the same skill transfers. I track leads and follow-ups the same way for smaller clients, and it turns out a spreadsheet can hold up as a lightweight CRM too, which I cover in can you manage a CRM using just Excel. The pattern is the same across both: spreadsheets are brilliant scaffolding for a small, contained job, and a liability once the job outgrows one person’s attention span.
Frequently asked questions
Can I build a Gantt chart in Google Sheets or does it need Excel?
Both work identically for this method. Google Sheets has a built in Gantt chart template under File > New > From template gallery, or you can build one manually with a stacked bar chart exactly as described above, and the free real-time sharing makes Sheets slightly better for a team that needs to view the same chart at once.
How many tasks is too many for a spreadsheet Gantt chart?
Around 15 to 20 tasks is where manual maintenance starts costing more time than the chart saves you, especially once tasks have real dependencies on each other. Below that, a spreadsheet is faster to build and update than dedicated software.
Does a spreadsheet Gantt chart show task dependencies automatically?
No. This is the biggest limitation and the one most tutorials gloss over. You have to manually recalculate and retype dates whenever an earlier task shifts, because the chart has no logic connecting one bar to another.
What is the fastest way to make the bars look like a Gantt chart rather than a normal bar chart?
Build a stacked bar chart using Start Date and Duration as the two series, then set the Start Date series fill to none or transparent. The invisible bar pushes the visible Duration bar to the correct starting position, which is what creates the classic Gantt look.
