How to Build an Excel Gantt Chart with Dependencies (and When to Stop)

How do you make a Gantt chart in Excel?

The standard recipe: list tasks in column A, start dates in column B, durations in column C, and an end date formula in column D (=B2+C2-1). Select the data, insert a stacked bar chart, set the first series (start date) to no fill, and format the axis so dates run left to right. You now have bars on a timeline.

This is the easy 80%. It's static - the chart shows what you typed, nothing more - but for a one-page snapshot of a small project it's perfectly serviceable.

How do you add dependencies to an Excel Gantt chart?

Excel has no native concept of a task dependency, so you encode it in the start-date formula. Add a predecessor column (say column E holds the row number of the task that must finish first), then replace the typed start date with a formula: the task starts the day after its predecessor ends, e.g. =D3+1 for a task that follows the task in row 3.

For working-day schedules, use =WORKDAY(D3, 1) so weekends don't count. Chain these formulas down the sheet and you have functioning finish-to-start dependencies: change one duration and everything downstream shifts.

• One predecessor per task is manageable; multiple predecessors need =MAX() over several end dates and get fragile fast.
• Only finish-to-start is practical - start-to-start or finish-to-finish relationships turn the formulas into puzzles.
• Inserting or reordering rows silently breaks cell references - the most common way these sheets die.
• Nothing validates the chain: a circular reference or a typo just produces wrong dates that look right.

Where does the spreadsheet approach break down?

The formulas above handle dates. They do not handle the things that make dependencies useful in practice: there is no critical path, so you can't see which slips actually move the deadline. There is no resource dimension, so two dependent tasks can be assigned to the same person at the same time without complaint. And there is no uncertainty - every duration is a single number pretending to be certain.

The maintenance cost compounds with plan size. A 15-task sheet is fine. A 60-task plan with a client asking weekly what-if questions is a part-time job. The spreadsheet isn't wrong - it's just doing structural work by hand that scheduling software does automatically. Our deeper comparison of Gantt planning with dependencies, resources and costs covers what that automation buys you.

What's the fastest way out of the spreadsheet?

If you already have a task list in Excel, don't rebuild it. Axioplan's Excel to Gantt converter reads any .csv or .xlsx task list - the parsing happens in your browser, nothing is uploaded - and turns it into a live project. From there you add dependencies by drawing them on the chart, not by writing formulas.

The payoff is everything the spreadsheet couldn't do: a real Gantt chart with dependencies - all four dependency types, automatic rescheduling, critical path - plus fractional resource allocation on the same timeline, and PERT-based confidence dates instead of single-number wishes.

Final thoughts

Build the Excel Gantt when the project is small, the audience is internal, and the plan will live for weeks, not months. The predecessor-formula trick genuinely works at that scale.

Switch tools at the first sign of any of these: more than one predecessor per task, a client who asks what-if questions, more than one person doing the work, or a date you'd have to defend commercially. Those are exactly the jobs dependencies exist for - and exactly what formulas simulate worst.