Read a Gantt chart from left to right: identify the status date, scan phases, inspect task bars and owners, follow dependency arrows, then check milestones and the critical path.
How do you read a Gantt chart?
Read a Gantt chart in this order: find the status date, understand the phase hierarchy, read each bar’s start and finish, check owners and progress, follow dependency arrows, inspect milestones, and finish with the critical and near-critical paths. The goal is not to admire the timeline; it is to decide whether the forecast is credible.
Start with the chart’s coordinate system
The left pane is usually a task table. The right pane is a calendar. Each row refers to the same work item in both panes.
Before interpreting any bar, identify:
- the displayed scale—hours, days, weeks, months, or quarters;
- whether weekends and holidays are working time;
- the project start and forecast finish;
- the status date or “today” line;
- whether end dates are inclusive or exclusive in the tool;
- whether the chart shows the current forecast, a baseline, or both.
A one-pixel movement means very different things at day and quarter zoom. Calendar assumptions also explain why a “five-day task” may span seven calendar days.
Read the hierarchy before individual tasks
Parent or summary rows group child tasks into phases. Their bars normally roll up the earliest child start and latest child finish; they are not extra work.
Scan the project at phase level first:
- What are the major deliverables?
- Which phases overlap?
- Where are the major handoffs?
- Which phase is forecast to finish last?
Then expand only the phase that needs investigation. This keeps a 300-row schedule from becoming a wall of bars.
What does a task bar mean?
The bar’s left edge is the planned or forecast start. The right edge is the finish. Its length represents duration on the chosen calendar.
Depending on the tool, a task bar can also encode:
| Visual | Likely meaning |
|---|---|
| Filled section inside a bar | Reported progress |
| Different bar color | Status, team, workstream, or criticality |
| Thin summary bar | Rolled-up phase |
| Lighter or second bar | Baseline or comparison schedule |
| Label beside bar | Owner, dates, or task name |
| Warning icon | Constraint, conflict, or overdue state |
Never infer color without checking the chart legend. Red may mean critical, late, blocked, or simply the marketing team.
How do you read dependency arrows?
An arrow explains why one task is scheduled relative to another. Follow it from predecessor to successor.
The four standard relationships are:
- Finish-to-start (FS): successor starts after predecessor finishes.
- Start-to-start (SS): successor starts after predecessor starts.
- Finish-to-finish (FF): successor cannot finish before predecessor finishes.
- Start-to-finish (SF): successor cannot finish before predecessor starts; rare and often confusing.
A number beside a link may be lag or lead. FS + 2d means wait two days after the predecessor finishes. FS - 1d means the successor overlaps the predecessor by one day.
When a date looks wrong, inspect its incoming links before dragging the bar. A predecessor, lag, calendar, or hard constraint may be calculating that date. See detailed examples in What Are Gantt Chart Dependencies?.
What does a milestone mean?
A milestone marks a significant zero-duration point: approval, delivery, contract signature, release, inspection, or phase exit. It is often drawn as a diamond, circle, flag, or star.
Read a milestone as a condition, not an activity. “Design approved” should have predecessor tasks that prepare the design and run the review. If a milestone floats alone with no incoming logic, its date may be an unsupported promise.
How do you read progress correctly?
Compare the task bar with the status date:
- A task entirely left of today should normally be complete.
- A task crossing today should have actual progress and a remaining forecast.
- A future task should not report actual completion unless work began early.
- An unfinished task with a finish date in the past is overdue.
Percentage complete can mislead. A ten-day task at 90% may still have its hardest two days left. Ask for remaining duration and completion evidence, not only a percentage.
How do you identify the critical path?
The critical path is the linked chain that determines the earliest project finish. In many tools it is highlighted. Critical tasks have no usable total float: if one slips and nothing else changes, the finish slips.
Read it from the final milestone backward:
- Find the project completion milestone.
- Follow the driving predecessor chain.
- Verify that each relationship reflects real work.
- Check for constraints manufacturing a false critical path.
- Inspect the next-longest paths, not only the red one.
A task can become critical after another branch slips. That is why near-critical work with one or two days of float deserves attention. The full calculation is explained in the Critical Path Method guide.
A five-minute Gantt chart review
Use this sequence in a status meeting:
Minute 1: forecast
- What is the current finish date?
- Did it move since the last review?
- Which milestone moved most?
Minute 2: actuals
- Which tasks should be complete but are not?
- Are actual starts and finishes recorded?
- Is remaining duration realistic?
Minute 3: logic
- What task is driving the next milestone?
- Are any tasks disconnected?
- Are there suspicious hard constraints or large lags?
Minute 4: capacity
- Is one owner assigned overlapping full-time work?
- Are critical resources available?
- Can flexible work move within float?
Minute 5: decisions
- What must change now?
- Who owns the recovery action?
- When will the schedule be updated?
This turns the Gantt chart into a management instrument instead of a presentation artifact.
How do you read a Gantt chart in GanttFather?
The left side shows task hierarchy and fields; the right side shows calendar bars. Dependency arrows connect linked sibling tasks. Leaf-task bars can be moved or resized, milestone markers appear as icons, and the today line anchors the review.
Turn on critical path to highlight the driving bars and links, then inspect FS, SS, FF, or SF relationships and any lag before manually moving a date. Switch to List view for dense field review or Kanban for status flow; all three views use the same tasks, and real-time sharing lets reviewers inspect one current schedule.
GanttFather does not provide a dedicated baseline-bar overlay. If the review is about variance from an approved plan, compare the live chart with a named snapshot or exported baseline rather than assuming a second bar is available on every task.
Open a free GanttFather project and practice the five-minute review on a real schedule.
Frequently asked questions
Why do some Gantt bars move automatically?
Auto-scheduled tasks react to dependencies, duration, calendars, and constraints. Changing a predecessor can move every downstream successor. That is expected behavior in a connected schedule.
Why is a parent bar longer than its own duration?
A parent bar normally summarizes its children. It begins with the earliest child and ends with the latest child, so it represents the phase span rather than separate work.
Why is a task red if it is not late?
Red often marks critical-path work, not lateness. Check the legend or toggle. Critical means schedule-sensitive; late means the current forecast or actual progress has passed an expected date.
What should executives look at?
Executives usually need milestones, phase forecast, variance from baseline, critical risks, and decisions. They rarely need every detailed task. Provide the smallest view that preserves the real drivers of the date.
Sources
