Milestones vs Tasks on a Gantt Chart

The difference in one line

A task consumes time and resources; it has a start, a finish and a duration. A milestone has no duration at all — it is a point marking that something has happened. That is why milestones render as diamonds: there is nothing to draw a bar across.

The practical test takes a second. Can somebody work on it? You can work on drafting a specification. You cannot work on "specification approved": it either has happened or it has not.

A worked example: the Harbour Labs packaging rebrand

One project, followed the whole way down. Harbour Labs is redoing the artwork for a 40-SKU line. Five working days a week, start Monday 2 March 2026.

What happens when a milestone slips

The external lab quotes eight days and takes thirteen. The regulatory check now finishes Tuesday 7 April instead of Tuesday 31 March.

A task slipping means work is taking longer and may still be absorbed. A milestone slipping means a commitment moved. Nobody outside the project cares that proofs took seven days instead of six; they care that the shelf date is now 18 May.

Task or milestone: the dimensions that actually differ

The distinction is not a drawing convention. It changes behaviour in six places.

Dimension	Task	Milestone
Duration	One day or more. Consumes calendar and effort.	Zero. Start and finish are the same date.
Dependencies	Predecessors and successors, most often finish-to-start.	Needs at least one of each, or it is decoration.
A slip means	Work took longer; float or resources may recover it.	A commitment moved. Recovery needs re-planning, not effort.
Resourcing	An assignee doing the work, usually a cost.	An owner who chases it. Effort is typically zero.
How it exports	A bar in PDF, PNG and PowerPoint; a real finish and day count in Excel and CSV; a multi-day calendar event.	A diamond in visual exports; blank finish and duration 0 in Excel and CSV; a single-day calendar event.
Who reads it	The person doing the work, and their manager.	Sponsors, clients, regulators, the summary slide.

The export row surprises people. Set the view to milestones only, export, and you have a one-page schedule for a steering group without building a second chart — but only if your milestones are real milestones.

What it costs to get it wrong

Now model "Label approved" the way most people first write it: a task called "get label sign-off", three days, between the lab check and the proofs.

The reverse mistake is cheaper but real: making "Print run" a milestone because it feels significant. Fifteen days of press time vanish and the critical path routes around the longest item on the plan. Significance decides whether something belongs on the chart; duration decides its shape.

What milestones are actually for

Milestones exist for the reader, not the doer. They are how someone who does not live inside your project finds the moments that matter: approvals, deliveries, gates, go-live.

They also make a schedule enforceable. "Artwork frozen", with the regulatory check depending on it, says what "freeze the artwork" does not: nothing downstream proceeds until this happens. When a designer submits a revision on 24 March, the chart shows a rule being broken, not a date sliding.

A milestone with no links either way is worth deleting. If nothing waits on it, it is a note in the margin — and notes belong in the notes field, not on the timeline.

How many should a project have?

Enough to tell the story, few enough that each one means something. Four to eight is a reasonable range; a hundred milestones is just tasks wearing a different shape.

A test: could you describe progress using only the milestones? Harbour Labs has five for a ten-week project — the upper end, justified because four are external hand-offs. The usual way to overshoot is a diamond at the end of every phase out of symmetry; phases already have summary bars.

Doing it in gantts.app

The Harbour Labs plan in the editor, using the buttons as they are actually labelled.

1. Click ✨ Paste to Gantt and paste the outline. A line ending in ! becomes a milestone, (10d) sets a duration, after Name links a predecessor, a leading # makes a phase — for example Artwork frozen ! after Internal review.
2. By hand instead: ＋ Task for work rows, ◆ Milestone for diamonds, ▣ Group for a phase, →| to indent a row under it.
3. Typed a milestone as a task? Double-click its row and change Type from task to milestone. Its finish collapses onto its start; no need to delete and re-add.
4. In the same panel set Runs after (predecessors), or the milestone will not move when the work in front of it moves.
5. Click ⚡ Auto-schedule to push every row to the earliest date its dependencies allow — this is how you learn whether your milestone dates were wishes or consequences.
6. Tick Critical path to confirm the chain through your gates sets the finish date. Striped bars are critical.
7. Open ◳ Baseline and save the plan before work starts. The variance columns then report milestone slip in days, which is where the five-day figure above comes from.
8. Set View to Milestones only for the sponsor version, then Export → 📄 PDF document or 📽 PowerPoint (.pptx). Switch back to All tasks for delivery.

One thing the editor will not do: drag a milestone wider. Milestones move but never resize, because a milestone with duration is not a milestone.

Common mistakes

Milestones with duration. If it takes three days it is a task. Give it a bar and put a milestone at its end if completion matters.

Milestones nobody owns. The owner is whoever makes the phone call when the date is at risk, not whoever does the approving.

Milestones dated by hope. If "Label approved" sits on 31 March because that is what retail was promised, rather than because eight days of lab work end there, the chart records an ambition. Auto-schedule, then negotiate the gap deliberately.

Milestones reported as percentages. A milestone is 0% or 100%. "Label approval is 60% done" means the underlying task is 60% done and the gate has not happened.

Summary bars and the hierarchy

The third symbol is the summary or phase bar spanning its child tasks. It is calculated, not entered: its dates come from the earliest start and latest finish beneath it, which is why editing them directly is usually disabled. To move a phase, move what it contains.

A summary bar shows when work runs; a milestone shows when a commitment falls due. A "Pre-press" summary spanning 2 March to 8 April is useful to the Harbour Labs team and useless to the retail buyer, who only asks about 11 May.

Templates that use this

• Simple Gantt Chart Template
• Project Management Gantt Chart Template
• Browse all Gantt chart templates

Keep reading

• What Is a Gantt Chart? Definition, Examples & Uses
• Gantt Chart Dependencies Explained: FS, SS, FF and SF
• Nine Gantt Chart Mistakes (and How to Fix Them)

Frequently asked questions