Gantt chart: who does what, in what order, by which date

One project's tasks as bars across weeks, with owners, milestones and a line for today.

Live example

The example: Building out a coffee shop in ten weeks

Four phases, 23 rows, a line for today

Building out a coffee shop in ten weeks

Open the exampleThe names and numbers are made up.

What to notice

  • Its 23 rows are 16 bars and 7 diamonds, and the header counts them for the reader: 9 done, 2 under way, 12 to come.
  • Two Mondays, January 18 and February 15, are shaded as public holidays, and no task starts or ends on either.
  • Under 1,000 pixels wide the chart gives way to a list, where each task has its weekdays written out and a small bar on the same ten-week track.

The prompt that starts one like it

Make a Gantt chart as a single HTML page for [project], from [start date] to [end date]. Tasks, with owner, start, end and what each waits on: [paste list]. Group them by phase and draw bars across weeks, with diamonds for milestones, arrows for dependencies and a line for today, [date]. Check every weekday against the calendar. On a phone, switch to a list of tasks with dates and a small bar. Add what we need from the client, then publish it on sharable.link with a password.

A Gantt chart puts three things in one picture: when each task happens, who owns it, and what it has to wait for. The sample is a ten-week coffee shop build-out, as it stood halfway through week 5. It's a snapshot: when a date slips, someone has to redraw it.

Who it's for

Whoever runs a project with a fixed end and several people's work in sequence: a build-out, an event, a product launch. You send it to the people doing the work and to the client paying for it, at kickoff and each time something moves.

It suits a plan of 15 to 40 rows. Under ten, a dated list does the job. Past a few dozen, or when tasks change daily, use scheduling software, where dragging one bar shifts everything behind it.

What a good one contains

  • Phases, each with a bracket. The sample has four. A client reads the brackets, and the crew reads the rows under them.
  • One owner per row. "Kofi" beside drywall settles who to call.
  • Dates checked against a calendar. Every bar starts on the weekday it claims. January 18 and February 15 are shaded as holidays, because a plan that books a plumber on a day off loses the crew's trust.
  • Diamonds for milestones. Inspections, deliveries and sign-offs take no time, yet everything hinges on them. There are seven here, ending with "Doors open" on Saturday, March 13.
  • Arrows for what waits on what. Flooring starts the Monday after drywall ends, and the arrow says that's no coincidence.
  • A line for today. Bars to its left are done or under way. Without it, the reader works out the status from dates.
  • Where the slack is. A short panel names the plan's two spare days, March 10 and 11. It's the first thing an owner asks when something slips.
  • What you need from the client. Paint colors by Monday, February 8. Decisions are tasks too, and the ones most often late.

On a phone, and after week one

Ten weeks of bars won't fit a phone, and a shrunken chart is a gray smudge. On a narrow screen the sample becomes a list: task, owner, weekdays, status and a small bar. Ask for that in your prompt: most of a crew opens the link on site.

When a task slips, don't redraw quietly. Say what changed, why, and what it did to the end date. The sample admits electrical rough-in ran two days late and that nothing after it moved. Then replace the page from the conversation where you made it. The link stays the same, so the crew's chat still points at the current plan.

How to send it

With a password. It gives a client's opening date and says who is on site which week. One password in the crew's group chat is easier than asking five trades to sign in.

Every page you publish gets one link that opens in any browser. You choose who can open it: anyone with the link, anyone with the password, or only the people and company domains you name, who sign in with Google or Microsoft. Change the page later and the link stays the same.

Make yours in Claude

Add the connector once, then publish from any Claude conversation and get a link to send.

Add Claude Connector

Already have the file? Upload it here.

More in strategy and finance

  • Business plan: A one-page plan an owner sends to a bank, a landlord or a partner ahead of the full version.
  • SWOT analysis: Strengths, weaknesses, opportunities and threats for one organization, each backed by evidence.
  • Executive summary: One screen that tells executives what a longer report found and what they're being asked to decide.
  • Timeline: Dated events in order, for a history people will enjoy or a project they have to follow.
  • Org chart: Who reports to whom in a small company, with teams, open roles and what each person looks after.
  • Mind map: One central idea with branches and twigs, sent to collaborators so they can say what's missing.
  • All use cases