How do you show a SharePoint list as a Gantt chart?

The built-in view, and where it stops

SharePoint lists have a Gantt view. Three columns and you have a timeline: a title, a start date and a due date. No add-in, no licence, five minutes.

Most people don’t know it exists, so start there. It stops at four places:

It’s a view, not a component. You navigate to the list to see it. You can’t put it on the project’s home page next to the risk register and the document library, which is where people actually look.

Grouping is limited. A plan with workstreams wants swim lanes. The view groups, but not in a way that reads as a plan to somebody who isn’t already holding the plan in their head.

No dependencies. There’s no “this starts when that finishes”. For a lot of operational plans that’s fine. For a sequenced build it’s the whole point.

Anything undated vanishes. A task with no start date is simply absent from the timeline, which makes the gap invisible — the one failure mode worth knowing about, because an incomplete plan looks like a complete one.

Why Project is usually the wrong answer

The instinct is to move the plan into Microsoft Project or Planner Premium. That buys dependencies and costs you the thing that was working: the plan sitting next to the documents, the decisions and the register that belong to it.

It also splits the source of truth. Now the list has dates and the plan has dates, and within a month they disagree.

Buy the tool when you genuinely need critical-path scheduling and a professional scheduler to maintain it. Most operational plans need a timeline people can see, not a scheduling engine.

What to do instead

Keep the list as the record. Put the timeline where the work is:

1. Add start and due date columns if they aren’t there, and make due date required so nothing is silently absent from the plan
2. Set a list validation rule so a due date can’t precede a start date
3. Group by workstream or owner, whichever people actually ask about
4. Surface the timeline on the page the team opens, rather than making them navigate to the list

Step four is the one the built-in view can’t do, and it’s why a web part exists rather than a view.

Dates in a list, not a picture of a plan

The other reason to keep the dates in the list: a list is queryable and an image is not. “What is due this fortnight” has an answer if the plan is data. If the plan is a Gantt chart somebody exported to a slide, it doesn’t.

Where to start

The Gantt Chart Web Part renders any list with start and end dates as a timeline, on the page where the work lives. It is ready — ask for it on the page and we’ll send the package and the setup notes.

If the plan is one part of a register with owners, states and reminders, the timeline is the easy half — the system underneath it is Custom Operational Apps.