Milestone

A milestone is a point-in-time marker in a programme — it has no duration, consumes no resources, and does nothing by itself. What it does is define when something significant has happened: design approved, structure complete, possession granted, handover achieved, funding released. Milestones are the skeleton of a schedule: they define the events that matter to the client, the contract, and the stakeholders, and they provide fixed reference points against which progress can be measured even when the detailed activity logic below them is in flux. A programme without clear milestones is difficult to report on and almost impossible to analyse for delay.

Milestones serve several distinct purposes. Contractual milestones define obligations — miss the handover milestone and there may be liquidated damages, loss of payment, or a compensation event claim. Programme milestones divide the project into phases that can be reported and managed separately. Interface milestones capture the handover of information or work between parties — when design is issued to the contractor, when a third-party connection is available, when the client-supplied equipment arrives. Keeping these distinct in the programme structure is important for both management and commercial analysis.

A common mistake is creating too many milestones and diluting their significance, or too few and losing the ability to track meaningful progress. A well-structured programme has milestones at every significant decision point, phase completion, and contractual obligation — and nothing else. Milestones should have zero duration: a 'milestone' with a duration is an activity, and calling it a milestone is misleading. In earned value management, many organisations use milestone-based earning rules, crediting earned value only when specific milestones are achieved rather than against percentage-complete estimates. This is a good practice precisely because milestones are objective — they are either achieved or they are not.