A long list of tasks tells you what is left. It does not tell you where you are. Milestones do.
What a milestone is
A named point in the project with a due date — Identity design, Site live, Handover. Tasks are grouped under it, and the record shows the next one and when it is due.
The part that earns money
A milestone can carry an amount, and be marked invoiced. That is how staged billing works on a fixed-price job.
| Milestone | Amount | Invoiced |
|---|---|---|
| Discovery and audit | ₹1,50,000 | Yes |
| Identity design | ₹3,00,000 | Yes |
| Applications and guidelines | ₹2,50,000 | No |
| Handover | ₹1,50,000 | No |
Four rows that answer the two questions everybody has about a fixed-price project: what is left to deliver, and what is left to bill. Without them, both live in somebody’s head or in an email from March.
Agree the milestones and their amounts before the work starts, and write them here. Stage payments renegotiated halfway through are renegotiated from a weak position, and “we said 40% on design approval” is only useful if somebody can find where it was said.
Choosing them
- Pick points a client would recognise — things they see or sign off, not internal stages.
- Three to six for a normal job. Twelve is a task list wearing a hat.
- Make each one verifiable. “Design approved” is a milestone; “design mostly done” is not.
- Tie each to money where the contract does.
On the record
The Milestone tile shows the next one and its date. A milestone in the past is the clearest single sign a project has slipped — clearer than progress, because it is a date somebody agreed to rather than a number that was computed.
Milestones and tasks are different things
| Milestone | Task |
|---|---|
| A point the client recognises. | A piece of work somebody does. |
| Three to six per project. | As many as the work needs. |
| Can carry an amount and be invoiced. | Carries hours, not money. |
| Has a date you agreed. | Has a date you planned. |
Tasks are grouped under milestones, so the plan reads as stages rather than as a list of forty things.
A milestone in the past
The single clearest signal a project has slipped. Progress is computed and can be argued with; a milestone date is something somebody agreed to, in writing, and it has been missed.
When one goes past, there are only three honest responses: it is nearly done and the date moves by days, the scope changed and the client needs telling, or the project is in trouble and somebody senior should know today.
Do not quietly move a milestone date. It is the one date the client also has. Moving it without telling them is how a project that was recoverable in September becomes a dispute in November.
Where to go next
Something missing or wrong here? Tell us. A question that needed asking usually means a page that needed writing.