On most Gantt charts the vocabulary is small and it barely changes between tools. A diamond is a milestone. A heavy bar spanning a group of rows is a summary. A hollow or outlined bar under a solid one is the baseline, showing where the task was originally planned. A partially filled bar shows progress. Almost everything else on the chart is a local convention someone in your organization invented, and that is where the confusion starts.
The Symbols You Actually Need
Five carry nearly all the meaning.
The task bar. One bar, one piece of work, length equals duration. This is the only symbol most audiences read correctly without being told.
The summary bar. Heavier, often with turned-down ends, spanning everything beneath it. It represents the rollup, not work of its own. Executives routinely misread these as tasks that are somehow running for eighteen months.
The milestone diamond. Zero duration. It marks a date, not a stretch of time: a delivery, a gate, a review. Filled usually means complete, hollow means pending, though that is a convention rather than a rule and you should say so in the legend.
The baseline bar. Drawn under the current bar, showing the original plan. The gap between the two is the whole story in a status review, and it is the symbol most often left off charts that badly need it.
The progress fill. Shading inside the bar for percent complete. Watch for the ambiguity here: percent complete by duration and percent complete by effort produce different pictures of the same task.
Build a Legend, Then Hold It
Write down what each symbol means first, then draw the chart to match. Doing it the other way round is how a schedule ends up with three shades of blue that meant something specific to whoever built it five years ago.
Keep the set small. If your legend runs past about eight entries, you are asking an audience to learn a language during a status meeting, and they will not. Cut the distinctions that do not change a decision.
Colour needs a caveat. Use it to separate event types, but never make it the only carrier of meaning. A meaningful share of any audience is colour-blind to some degree, and projectors wash out warm colours badly. Pair every colour distinction with a shape difference or a text label. If the red bar and the green bar look identical in the room, the chart has told nobody anything.
Holding the legend steady across projects is the part organizations skip, and it costs more than any individual chart.
If a circled red arrow means “critical milestone” on project A, it must not mean “completed” on project B. An executive who sits through six status reviews in a week should not be re-learning the notation at the start of each one. Every minute spent explaining symbols is a minute not spent on whether the program is in trouble.
Nobody expects every company and agency to converge on one standard set, and they never will. But a single set within one organization, held for the life of a program, is achievable and it is worth the argument it takes to agree on. Write it down. Circulate it. Make new charts inherit it rather than reinvent it.
The same discipline pays off when you present the same schedule in a different medium. A chart exported from Microsoft Project for an executive review should use the notation the audience already knows, and so should a timeline you have rebuilt as a PowerPoint slide. The tool changes. The vocabulary should not.
Showing Plan Against Actual
When management asks how the program is doing against the original plan, the baseline bar and the progress fill do the work together. Put the current bar and the baseline bar on the same row and the slip reads itself, with no narration required.
You can push this further than most people do. A task that started late but will still finish on time, a task rescheduled three times that lands on the original date, a task that started early and finished early: all of these are distinguishable with plain bar notation and a status line, without inventing new symbols for each case.
Nine variations, one notation, no new symbols. That is the standard to aim for.
Where This Goes Wrong
Three failures account for most unreadable schedules.
Too many symbols. The instinct when a chart is confusing is to add notation. It is almost always the wrong move. Confusing charts usually have too many distinctions, not too few.
A legend that contradicts the chart. Symbols drift as a schedule is edited over months, and the legend is rarely updated with them. A wrong legend is worse than no legend, because the audience trusts it.
Symbols that carry no decision. If nobody would act differently based on a distinction, it does not need its own shape. Cut it.
When to Drop the Legend Entirely
Here is the case against the advice above. Sometimes the legend should go.
On a summary chart showing many programs on one page, space is the binding constraint, and a legend eats space that symbols and labels need. If the audience already knows the notation cold and the acronyms are genuinely standard in that room, dropping the legend and presenting the detail verbally is the better trade.
That works only under both conditions. If the audience is mixed, or anyone in the room is seeing your notation for the first time, keep the legend and cut something else. Getting this wrong in front of a customer is expensive in a way that a slightly cramped chart is not.
Summary
Learn the five symbols that carry the meaning, keep your legend under eight entries, never let colour do a job alone, and hold the same notation across every chart your organization produces. Tools like Microsoft Project, Primavera and Milestones Professional will all draw these conventions; none of them will decide for you what a symbol means.