What are milestones in project management?
Short answer
A milestone is a point in a project that marks a significant event, such as a phase finishing, a deliverable being approved, or a release going live. Unlike a task, it has no duration: it is a moment, not work. Milestones break a long project into checkpoints, give stakeholders a simple way to follow progress, and show early whether the end date is still realistic.
Last updated 19 October 2026. Written by the Kaneo team, who also build one of the tools mentioned.
Milestone, task, and deliverable
| Milestone | Task | Deliverable | |
|---|---|---|---|
| What it is | A point in time | A piece of work | A thing handed over |
| Duration | None | Hours to weeks | Produced by tasks |
| Example | Design approved | Create page layouts | Approved page designs |
| Audience | Stakeholders and team | Team | Client or next team |
What makes a good milestone
It is observable
Anyone can tell whether it happened. "Beta live with 20 customers" is observable; "backend mostly done" is not.
It marks a decision or handover
Sign-offs, launches, and the end of a phase make good milestones, because something changes when they are reached.
There are few of them
Four to eight for a project of a few months. A milestone every week is just a task list with diamonds.
It has a date and an owner
Someone is responsible for it being reached on time and for raising the alarm early if it will not be.
Milestone examples
Software release
Spec approved, feature complete, beta live, release candidate signed off, generally available.
Website redesign
Sitemap and wireframes approved, designs approved, content complete, site built on staging, launched.
System migration
Migration plan approved, test migration complete, user acceptance signed off, cutover done, old system decommissioned.
Event
Venue booked, speakers confirmed, registration open, final agenda published, event day.
Tracking milestones
Put milestones on the project timeline and review them weekly. The useful question is not whether the next milestone is on time, but whether the work leading to it is: by the time a milestone is visibly late, the slip has usually been building for weeks.
When a milestone moves, say what it moves: later milestones, the end date, or the scope. A milestone that quietly slides teaches people to ignore the others.
Some teams use milestone trend analysis for this: each week, record the forecast date for every milestone, and chart the forecasts over time. Lines that keep rising show a schedule that is slipping long before the deadline.
How to lay out work and milestones by date.
Milestones in Kaneo
Kaneo has no separate milestone type. Create a short task for each milestone with a due date and a milestone label, and it appears on the Gantt and Calendar views alongside the work leading up to it. Filter by the label to get the milestone-only view for stakeholders.
Mark the tasks that must finish first with a Blocks relation to the milestone task, so anyone opening it can see what it is waiting on. When the milestone is reached, move it to Done like any other task.
Frequently asked
How many milestones should a project have?
Enough to give a checkpoint every few weeks: typically four to eight for a project of a few months. More than that and they lose their meaning.
Do milestones have a duration?
No. A milestone is a point in time. In a Gantt chart it is usually shown as a diamond or a zero-length bar.
What is the difference between a milestone and a goal?
A goal is the outcome the project is for. Milestones are checkpoints on the way to it.
Should milestones be tied to payments?
Often, in client and contract work. Payment milestones need clear acceptance criteria, so both sides agree when one has been reached.