
A Gantt chart is a bar chart of a project schedule. Tasks are listed down the left side, time runs across the top, and each task is a horizontal bar that runs from its start date to its finish date. Diamonds mark milestones and arrows mark dependencies, so you can see what happens when, what overlaps and what has to wait.
This guide explains how to read a Gantt chart, what each element and marker means, and how dependencies and the critical path work. It then walks through three worked examples. The examples are fictional teaching projects, and their schedule math was recalculated on November 4, 2026. AFFiNE publishes this blog. AFFiNE does not have a Gantt chart view today; Where AFFiNE fits explains what it does and doesn't do.
Downloads:
A Gantt chart answers four questions about a project on one page:
In one sentence, the Gantt chart meaning is: a project schedule drawn as bars on a calendar. The Project Management Institute's glossary, as quoted in Wikipedia's Gantt chart article, describes it the same way: activities on the vertical axis, dates on the horizontal axis, and durations shown as horizontal bars placed by their start and finish dates.
The chart is named after Henry L. Gantt, an American engineer who designed and popularized it around 1910 to 1915. Today it is the default schedule view in most project management software, and you can build one in a spreadsheet.
A Gantt chart fits best when a project has a fixed end date, tasks that hand off to each other, and more than one person doing the work. Construction, events, product launches, office moves and software releases are typical. It fits poorly for continuous work with no end date, such as a support queue. A Kanban board handles that better.

Read a Gantt chart in this order:
| Element | What it shows | How it is drawn |
|---|---|---|
| Task list | The work, one row per task, often grouped by phase | Left-hand column |
| Time scale | Days, weeks or months across the top | Header row |
| Task bar | When a task starts and finishes; length is its duration | Horizontal bar |
| Milestone | A zero-length checkpoint such as an approval or launch | Diamond |
| Dependency | A task that has to wait for another | Arrow between bars |
| Progress | How much of a task is done | Shaded part of the bar or a % |
| Status (today) line | The date the chart reports on | Vertical line |
| Owner | Who is responsible for the task | Column or bar label |
| Summary bar | A phase that spans its child tasks | Thick or bracketed bar |
| Baseline | The original plan, to compare against the current one | Thin bar under the task bar |
| Critical path | Tasks with zero float that set the finish date | Highlighted bars, often red |
Not every chart needs all eleven. The minimum is a task list, a time scale and bars. Add milestones, dependencies and a status line as soon as more than one person relies on the chart. Baselines and critical path highlighting usually come from scheduling software, because they are hard to keep current by hand.
Gantt chart markers and symbols. Conventions vary a little between tools, but most use the same set:
A milestone is a checkpoint with zero duration: an approval, an inspection, a delivery or a launch. It is drawn as a diamond on the date it happens and takes no time itself. In the kitchen example, the rough-in inspection on Feb 9 and the final handover on Mar 5 are milestones.
Good milestones have three things in common:
Aim for about one milestone per phase. If every other row is a diamond, the chart stops telling readers which dates matter.
A dependency says which end of one task controls which end of another. There are four types:
| Type | Rule | Example | When to use it |
|---|---|---|---|
| Finish-to-start (FS) | B starts after A finishes | Pour the foundation, then frame the walls | Most common; default in most tools |
| Start-to-start (SS) | B starts after A starts | Electrical rough-in starts one day after plumbing starts | Overlapping work; often with a lag |
| Finish-to-finish (FF) | B finishes after A finishes | Testing finishes after development finishes | Work that wraps up together |
| Start-to-finish (SF) | B finishes after A starts | The old system runs until the new one goes live | Rare; handovers and shift cover |

Two more terms come with dependencies:
Most links in a typical schedule are finish-to-start. Use the other types only when the overlap is real, because every extra link type makes the chart harder to read.
The critical path is the longest chain of dependent tasks from start to finish. It sets the earliest date the project can finish, and any delay on it delays the finish by the same amount. Float, also called slack, is how long a task off the critical path can slip before it moves the finish date.

In the kitchen example, the critical path runs through tasks 1, 2, 4, 5, 6, 7, 8, 9, 10, 11 and 12. It takes 40 workdays, from Jan 11 to Mar 5, 2027. Only one task has float: the cabinet lead time. The cabinets arrive on Feb 5, but cabinet install can't start before Feb 17, so the order can slip 7 workdays without moving the handover. If it slips 8, it becomes the task that sets the finish date.
This is why the critical path matters more than the length of any single bar. The 15-day cabinet order is the longest bar on the chart, but it doesn't drive the finish date. The 10-day permit review does.
How it is calculated. Scheduling software runs two passes. The forward pass sets each task's early start to the latest finish of the tasks it depends on. The backward pass starts from the project finish and sets each task's late finish to the earliest late start of the tasks that depend on it. Float is late start minus early start, and the tasks with zero float form the critical path. PMI has a full walkthrough of these critical path method calculations. The example workbook does the same with formulas, so the float and critical flags update when you change a duration.
One caveat: a classic hand-drawn Gantt chart doesn't show the critical path or slack, a limitation PMI points out in its history of the harmonogram. You need dependency links and a calculation. That is why the critical path method was developed as a separate technique in the late 1950s.
Here is the full schedule behind the charts above: a 12-task, 8-week plan for a fictional kitchen renovation. Durations are in workdays. Weekends are excluded, and no public holidays are included.
| Task | Workdays | Depends on | Dates (2027) | Float |
|---|---|---|---|---|
| 1. Design and quote | 5 | None | Jan 11 - Jan 15 | 0 (critical) |
| 2. Permit review | 10 | 1 (FS) | Jan 18 - Jan 29 | 0 (critical) |
| 3. Cabinet lead time | 15 | 1 (FS) | Jan 18 - Feb 5 | 7 workdays |
| 4. Demolition | 3 | 2 (FS) | Feb 1 - Feb 3 | 0 (critical) |
| 5. Plumbing rough-in | 3 | 4 (FS) | Feb 4 - Feb 8 | 0 (critical) |
| 6. Electrical rough-in | 3 | 5 (SS +1) | Feb 5 - Feb 9 | 0 (critical) |
| 7. ◆ Rough-in inspection | 0 | 5 (FS), 6 (FS) | Feb 9 (milestone) | 0 (critical) |
| 8. Drywall and paint | 5 | 7 (FS) | Feb 10 - Feb 16 | 0 (critical) |
| 9. Cabinet install | 3 | 8 (FS), 3 (FS) | Feb 17 - Feb 19 | 0 (critical) |
| 10. Countertop fabrication | 7 | 9 (FS) | Feb 22 - Mar 2 | 0 (critical) |
| 11. Backsplash and appliances | 3 | 10 (FS) | Mar 3 - Mar 5 | 0 (critical) |
| 12. ◆ Final inspection and handover | 0 | 11 (FS) | Mar 5 (milestone) | 0 (critical) |
What this example teaches:
The workbook's Kitchen renovation tab has the same tasks with live formulas. Change a duration or a lag, and the dates, float and critical flags recalculate.
A launch campaign suits a Gantt chart because several teams work in parallel toward one fixed date.
| Task | When | Depends on | Owner |
|---|---|---|---|
| Brief and audience research | Week 1 | None | Marketing lead |
| Messaging and creative concept | Weeks 2-3 | Brief (FS) | Content + design |
| ◆ Concept approved | Start of week 4 | Concept (FS) | Head of marketing |
| Landing page build | Weeks 4-5 | Approval (FS) | Web team |
| Ad creative and copy | Weeks 4-5 | Approval (FS) | Design |
| Email sequence | Weeks 5-6 | Landing page (SS +1 week) | Lifecycle |
| ◆ Launch | Start of week 7 | Page, ads, email (FS) | Marketing lead |
| Paid and email campaign live | Weeks 7-8 | Launch (FS) | Growth |
| Results review | Week 9 | Campaign (FS) | Marketing lead |

Research and the creative concept run in sequence. Approval at the start of week 4 then releases three workstreams at once. The email sequence starts a week after the landing page (SS +1 week) because the emails link to it, and the launch waits for the page, the ads and the emails. Coloring bars by owner makes busy stretches easy to spot: design work runs from week 2 through week 5.
Agile teams often assume Gantt charts don't fit sprints. They do, one level up. Keep tickets on the sprint board, and use the Gantt chart for sprints, parallel workstreams and fixed dates.
| Workstream | When | Depends on | Note |
|---|---|---|---|
| Sprint 1: data model and API | Weeks 1-2 | None | Backlog items live on the sprint board |
| Sprint 2: core screens | Weeks 3-4 | Sprint 1 (FS) | Bar shows the sprint, not each ticket |
| Sprint 3: integrations | Weeks 5-6 | Sprint 2 (FS) | Scope can move between sprints |
| Docs and help center | Weeks 4-7 | Sprint 2 (SS) | Runs in parallel with build work |
| ◆ Code freeze | End of week 6 | Sprint 3 (FS) | Fixed date the whole team plans around |
| Beta and bug fixing | Weeks 7-8 | Code freeze (FS) | Feeds bugs back into the backlog |
| ◆ Public release | End of week 8 | Beta (FS), Docs (FS) | Milestone shared with sales and support |
Here the milestones carry most of the value. Sales, support and marketing don't need ticket detail. They need to know when code freeze and release happen, and what depends on them.
| Chart | What it shows | Best for | Weak at |
|---|---|---|---|
| Gantt chart | Tasks as bars on a calendar, with dependencies | Projects with dates, handoffs and a deadline | Fast-changing scope; looks precise even when it is not |
| PERT chart | Tasks as a network of nodes and arrows | Estimating duration under uncertainty | Reading dates at a glance |
| Kanban board | Work items moving through stage columns | Continuous flow such as support or content | Deadlines and dependencies |
| Timeline | Key dates and milestones on one line | Briefing stakeholders on the big moments | Showing overlap, owners and knock-on effects |
| Roadmap | Themes or goals by month or quarter | Strategy and direction over 6 to 18 months | Day-to-day scheduling |

Advantages:
Disadvantages:
Where to build it:
AFFiNE isn't a Gantt chart tool and doesn't draw Gantt bars. Its database documentation lists Table and Kanban views as available today, with Calendar and Timeline views planned. Where it helps is the work around the schedule: the project brief, decisions, meeting notes and a task table in one workspace, plus a whiteboard for sketching phases before you commit to dates. A practical setup is to plan dates in the example workbook or a Gantt tool, keep the brief and task table in AFFiNE, and link the two. You can start from the project timeline template.
A Gantt chart is a project schedule drawn as bars on a calendar. Each row is a task, and each bar shows when that task starts, how long it takes and when it ends. Diamonds mark milestones, and arrows show which tasks have to wait for others.
The essential elements are a task list, a time scale and task bars. Most charts also show milestones, dependencies, progress, a status or today line, and task owners. Scheduling software adds summary bars, baselines and critical path highlighting.
A milestone is a checkpoint with zero duration, such as an approval, an inspection or a launch. It is drawn as a diamond on its date. Good milestones have a clear yes or no test and at least one task that waits on them.
A diamond is a milestone, an arrow is a dependency, a vertical line marks today or the status date, and shading inside a bar shows percent complete. Red bars usually mark the critical path, and a thin bar under a task shows the original baseline.
Yes, if the tasks are linked with dependencies. Scheduling software and the example workbook on this page calculate float for each task and highlight the zero-float chain that sets the finish date. A hand-drawn Gantt chart without dependency links can't show it.
A Gantt chart shows tasks as bars on a calendar, so dates and overlaps are easy to read. A PERT chart shows tasks as a network and uses three time estimates per task to handle uncertainty. Many teams estimate with PERT and share the plan as a Gantt chart.
This guide was checked on November 4, 2026.
The kitchen renovation, campaign and software release are fictional teaching examples. The kitchen dates, float and critical path come from a forward and backward pass over the published durations and links, and the workbook formulas recalculate the same values.