A project plan can start with a few sentences: “We’re launching the new site in six weeks — design first, then build, content can overlap with build, and we need a week of QA before go-live.” That gives you enough of a schedule to draft a chart for the team to review.

A Gantt chart puts those tasks on a calendar and shows what’s waiting on what. Below, we’ll turn that description into a chart and check the result. If you’re still choosing a planning tool, compare Gantt charts, boards, and lists first.

The four things every timeline needs

Gather these four details before you make the chart:

  1. Tasks — the chunks of work, named the way your team actually talks about them. “Design,” “Build,” “Taste-testing photos.” For a short project, aim for about five to twelve tasks so the team can read the chart in a meeting.
  2. Durations — how long each chunk takes. Rough is fine. “About two weeks” is enough for a first draft when you don’t have a more precise estimate.
  3. Dependencies — what can’t start until something else finishes. For example: “Build starts when design is done. Photos can happen during build.”
  4. Milestones — the moments that matter to people outside the work: a launch or a design review. A milestone appears as a diamond on the chart.

You can describe all of these in ordinary sentences. The plain-English glossary explains the scheduling terms if you need them.

Write the paragraph first

Before opening a tool, try writing the plan as a short paragraph. Include the ordering words: first, then, while, once, by.

First two weeks: design. Then three weeks of build — content writing can overlap with the second half of build. Once build and content are both done, one week of QA. Launch by March 28.

Those ordering words are your dependencies. “Then” is a finish-to-start link. “While” and “overlap” are parallel tracks. “Once X and Y are done” is a merge. “By March 28” is a milestone with a deadline. The paragraph gives you the information needed to draw a first draft, which you’ll still need to check with the people doing the work.

Three ways to render it

The spreadsheet way. List tasks down column A, dates across row 1, and fill cells to make bars. This is quick to set up, but if design slips two days, you’ll have to move the affected bars yourself unless you’ve added formulas to handle dependencies. Our guide to Gantt charts in Google Sheets covers three methods, including formulas and their limits.

The project-management-suite way. Heavyweight PM tools make excellent Gantt charts and can also manage resources and budgets. That may be useful for a large program. For a short project, consider how much setup the tool requires and whether people will need accounts to view the plan.

The plain-English way. Paste the paragraph into ganttchart.ai and it generates a chart with tasks, durations, dependencies, and milestones. Check the draft against what you meant. Adjust the dates and names it got wrong, then share the result as a link with no accounts on either end. We built it because we kept writing that paragraph and resenting every tool that made us re-type it as form fields. (The full story is in the case study.)

The mistakes that sink timelines

Check these points before sharing the chart:

  • Missing dependencies. If every bar starts on day one, check whether any task needs something from another before it can begin. Record those constraints.
  • Too many tasks. “Design” can be one bar even if it contains forty tickets. Keep the detailed work in your issue tracker so people can read the schedule without it.
  • No room for delays. Put a visible buffer before a deadline that matters, and agree on it with the team. A plan that fills every available day has no room for estimates to be wrong.
  • Treating the first draft as final. Review the chart with the team and update it when the work changes. Easy editing makes it more likely that the schedule will stay current.

Ten minutes, start to finish

For a short project you already understand, aim to spend three minutes writing the paragraph, generate the chart, and use the remaining time to check the dates and dependencies before sharing it. We designed ganttchart.ai around those ten minutes before a meeting. If the draft exposes a question you can’t answer, bring that question to the meeting too.

If you’d rather start from a finished chart than a blank page, we keep five worked Gantt chart examples — a website launch, a product launch, an app MVP, a house move, and a meetup — each with the exact prompt that generates it.