How is a milestone different from an activity?

A milestone has zero duration; an activity has work and takes time. An activity like "pour foundations" consumes days, crews, and cost. A milestone like "foundations complete" is an instant: it marks the moment the work finishes, but it does nothing itself and spans no time on the schedule. In the Critical Path Method, milestones are modeled as zero-duration events tied into the logic, so they move when the work feeding them moves. The value of a milestone is as a checkpoint: it is a named, trackable point that stakeholders, contracts, and payments can hang on, without having to reference the dozens of detailed activities that actually produce it.

What is the difference between a contractual and an interim milestone?

Whether missing it carries a contractual consequence. A contractual milestone is written into the agreement, often with a date and sometimes with liquidated damages or a payment tied to it, so missing it has direct commercial weight: substantial completion is the classic example. An interim milestone is one the team sets for its own management, like "level 3 dried-in" or "permanent power energized," to track progress and coordinate trades, with no contractual penalty attached. Both are useful, but they are read differently: a slipped contractual milestone is a commercial event that may trigger notice and damages, while a slipped interim milestone is a management signal to investigate and recover.

Why do milestones slip when no single activity looks late?

Because a milestone sits at the end of a chain, and it moves when the net of everything feeding it moves, even if no one activity looks dramatically late. Several activities each slipping a day, or an owner decision taking a little longer, or a near-critical path overtaking the one everyone was watching, can push a milestone without any obvious culprit. This is why milestones are read against the critical path and the baseline rather than in isolation: the milestone date is a summary of the schedule logic behind it. Tracking the milestone alone tells you that it moved; tracking it against the path that drives it tells you why.

Construction Glossary · Scheduling

TheMilestone

A milestone does no work and takes no time. It is a named instant, the moment real progress is reached, and often the moment a payment or a deadline comes due.

Definition

A milestone is a zero-duration marker in the schedule that represents a significant event or checkpoint, such as foundations complete, dried-in, or substantial completion. Milestones carry no work and no duration of their own; they mark the completion of the work that leads to them. They are often tied to contractual deadlines, payment triggers, or interface dates with other parties, which makes a slipped milestone both a schedule signal and a commercial one.

Checkpoints on the timeline

Four milestones mark the job. Three are hit; Power-on has drifted six days past its planned mark, a slip that is read against the path feeding it, not the diamond alone.

Contractual vs interim

The same diamond carries very different weight depending on whether a contract hangs on it.

	Contractual milestone	Interim milestone
Set by	The contract	The team, for management
Missing it	Notice, damages, or payment impact	A signal to investigate and recover
Example	Substantial completion	Level 3 dried-in

A missed contractual milestone can trigger liquidated damages and a contractual notice.

How POD tracks milestones

POD reads the milestone rows from the schedule you import and shows their planned dates against the actual completions statused in the field, flagging a milestone as upcoming or missed when its planned date passes without a recorded finish. Because a contractual milestone can carry a notice deadline or a payment, seeing a checkpoint pass unmet next to the field record is where the value is. POD reads the milestone dates the scheduling tool holds; it does not forecast a milestone’s drift before its date, recompute the schedule, or decide the commercial consequence of a miss.

Construction scheduling software guide

Frequently asked questions

When a milestone is at risk, you compress

A milestone drifting toward a contractual date is the trigger for recovery, by crashing or fast-tracking the work that feeds it.

Schedule Compression Back to the Glossary