A milestone is a point in a schedule with no duration that marks an event, such as a sign-off, a delivery or a go-live, rather than a piece of work. Milestones are linked like tasks, so they move when the work before them moves.

Milestones give a plan its checkpoints: they are what sponsors watch and what contracts often name. Because they carry no work, they cannot absorb a delay; whatever reaches them shows.

In a predecessors table a milestone is a task with a duration of zero.

Worked example

TaskDurationDepends onScheduledTotal floatAfter the delay
1. Cutover rehearsal3 daysNoneDays 1 to 30 daysDays 1 to 5
2. Cutover2 days1Days 4 to 50 daysDays 6 to 7
3. Go-liveMilestone2Day 60 daysDay 8

The delay: Cutover rehearsal takes 2 days longer.

Go-live follows Cutover, so it lands on day 6. If the rehearsal runs 2 days late, the milestone moves with it, to day 8.

Open this example in the free delay simulator to change the durations, the links or the delay and watch the schedule move.

Learn more

Related terms

Schedule baseline

A schedule baseline is a saved copy of the approved schedule, the dates a project committed to, that progress and forecasts are measured against.

Critical path

The critical path is the longest chain of dependent tasks through a project.

Finish-to-start (FS)

A finish-to-start (FS) dependency means the successor cannot start until its predecessor has finished.

See it on your own plan

Depentra calculates every date, link and float in your plan and shows what moves when something slips.