How to Plan a Project on a Gantt Chart

A Gantt chart is a schedule of tasks. Each task that has dates occupies a span. A blocking link says one task should hold another. You use the chart to see order and overlap, not to decorate a status meeting. If you only need to know what is in progress this week, a board is the better picture. The comparison is Kanban vs Gantt charts. This page is how to plan on the chart once you have chosen it.

What you put on the chart

Three facts make a task show up as a plan:

1. A start date, when the work may begin.
2. A due date, when it should be finished.
3. A Blocks link, when one task must finish before another can proceed.

Without dates, the task is real and can still live on the board, but it is not a bar on the schedule. Without a Blocks link, two bars can overlap and the chart will not invent an order. Overlap is allowed. It means you believe those tasks can happen in the same days.

The only schedule arrow is Blocks. Related to connects two tasks that matter to each other and does not mean "this one waits." Both relationship types, and nothing else, are explained in how project dependencies work. There is no lag, no start-to-start link, and no finish-to-finish link. If you need those, you do not have them here. Say so in the plan instead of drawing a fake arrow.

A planning sequence

Use one project you are about to start, not a template from a textbook.

1. List the tasks. Keep names short enough to read on a bar.
2. Add start and due dates you are willing to defend. A due date with no start still marks the end. Add the start when the span matters.
3. Draw Blocks only where work truly cannot start. "Design blocks build" is a real block if build cannot start on a guess. "Write copy relates to design" is Related to if they trade drafts but neither fully waits.
4. Read the chart left to right. Ask what is on the critical week, in ordinary language: which bars cover those days, and which of them block later bars.
5. Change a date or a link. Do not add a status column to the chart and call that planning.

There is no milestone object. If you need a moment such as "client sign-off," make it a task with a short span and let later work block on it. There is no baseline. If the dates move, the chart shows the dates you have now, not a ghost of last month. There is no critical-path calculation that paints a special chain. You read the Blocks links yourself.

What the chart will not do

• It will not export itself to a PDF for you. Do not promise a file.
• It will not email the picture on a schedule.
• It will not compute slack, float, or a critical path.
• It will not turn a currency field into a cost-loaded schedule. Dates and blocks are the plan. Money is not on this chart.
• It will not move bars because a status changed. People change dates when the plan changes.

The board still matters after you plan. Status lives there. The Gantt does not replace "In progress." A task can be on the schedule and still be Not started.

Showing the chart to a client

A client update, in this product, means a person with access opens the same chart. It does not mean a portal and it does not mean you generate a separate status document from the bars.

Give the client a limited membership and a view share on the project, the way client access without the whole workspace describes. Then the chart they see is the chart you see, limited to what you shared. Before the meeting, check three things:

• Dates you do not want them to treat as a promise are not on the tasks.
• Internal tasks are not in the shared project or section.
• Blocks they will ask about are real, not leftover links from a draft.

Walk the bars in date order. When they ask "what is holding the launch," point at the Blocks arrow, not at a paragraph in a slide. If you cannot share the live chart, you are not required to. A conversation can use the dates without pretending the product produced a handout.

A three-week brochure

Task	Start	Due	Link
Outline	Monday week 1	Tuesday week 1	Blocks draft
Draft	Wednesday week 1	Wednesday week 2	Blocks design
Design	Thursday week 2	Wednesday week 3	Blocks print files
Print files	Thursday week 3	Friday week 3	None

Related work, such as "collect logos," can be Related to Design if the designer needs the files but the outline does not wait on them. Do not draw that as Blocks unless design truly cannot start.

If print files slip, you change the due date. The chart does not store the old Friday beside the new one. Write the change in a comment if the history matters.

How this stays honest

Update the Gantt when a date changes in real life, the same day if you can. A chart used only for the kickoff is a poster. People will go back to chat for the real dates, which is the failure described when spreadsheets and threads diverge.

Keep the task count small enough that the bars are readable. A hundred tiny tasks make a carpet, not a plan. Subtasks belong on the chart only when they have their own dates. Checklist lines do not appear as bars.

Reading the chart with someone else

Sit with the person who will do the middle task, not only with the person who drew the bars. Ask them which start date they do not believe. A Gantt chart is easy to overdraw because empty space looks like a plan. If they say the draft cannot start on Wednesday because the outline review always slips, either move the start or add a Blocks link from a review task you forgot to create. Do not leave a bar that both of you know is fiction.

Then pick the busiest three days and name every bar that touches them. If you cannot explain why two of them overlap, they may be a hidden block. Add Blocks, or accept the overlap out loud. Silent overlap is how the chart says yes and the team assumes a sequence.

Leave the meeting with dates changed in the product, not in a notebook. A notebook baseline feels responsible and becomes the second copy of the plan. The product will not store that ghost for you. If leadership wants "original versus current," they want a report the product does not generate. Tell them the chart is the current schedule, and a comment holds the reason it moved.

Finally, check the board for the same tasks. Anything In progress on the board should have dates that include today or an honest future start. A task that is In progress with a start date next month is a status problem or a date problem. Fix one of them before you treat the Gantt as the plan you will show anyone else.

Conclusion

To plan on a Gantt chart, put start and due dates on the tasks that form the schedule, and draw Blocks where one task holds the next. Read overlaps as simultaneous work. Do not expect a critical path, a baseline, a milestone type, or a PDF. For a client, share the view with someone who already has access, and make sure the dates on the bars are dates you mean. The product is /pms.