Milestones
A milestone marks a moment rather than a stretch of work: a delivery, an approval, a go-live. This page covers the ways to create one, how it is drawn, and the rules it follows once it exists.
Every row on your chart is one of two things: a task, which takes time, or a milestone, which doesn’t. A milestone has a start date, no duration and no bar, just a diamond on the day it happens. Everything else on the form still works, so a milestone can carry a resource, a status, notes and a dependency like any other row.
01 What a milestone is for
Use a milestone whenever the thing you want on the chart is an event rather than an effort. In a villa build that’s “Permits approved”, “Watertight” and “Handover”: moments that either happened or didn’t, with no sensible answer to “how many days did it take?”
Three reasons it’s worth the extra row:
- It reads instantly. A diamond on a chart of bars is the first thing the eye finds, which is what you want for the dates a client asks about.
- It gives other tasks something to hang off. “Electrical first fix” shouldn’t wait on the whole Structure phase. It should wait on the house being closed in, and a milestone is the right predecessor for that. In the villa build three trades hang off “Watertight” for this reason.
- Its length can’t creep. A zero-duration row can’t quietly grow from three days to five. Its date still moves if its predecessors move; its length never does.
02 Adding a milestone
There are three ways in, and each one puts the milestone at a row you choose:
From the ribbon. Select the row, then go to Gantt Excel → Tasks → Add Milestone.
From the right-click menu. Right-click the row in the task grid and choose Add Milestone.
From the timeline. Right-click the timeline on the row and the day where the milestone belongs, and choose Add Milestone on followed by that date. The menu item names the date you clicked, and the form opens with it already set as the start.
The timeline menu appears in the Daily and Hourly views. In a weekly or coarser view one column covers a whole period rather than one day, so right-clicking there gives you Excel’s ordinary menu instead. In the Hourly view the start also takes the hour you clicked. The same menu can start, finish or add a task on the clicked date; those items are covered in Adding, editing & deleting tasks.
Every route opens the Task Form in milestone mode. You’ll see three differences from an ordinary Add Task:
- The window is titled Add Milestone, and its first tab reads Milestone Details rather than Task Details.
- The field beside the name is labelled Milestone, not Task.
- End Date and Duration are locked in all three bands and skipped by the Tab key, so typing runs straight from the name to the dates that matter.
The form doesn’t open empty. The Estimated Start Date is already filled in: with the day you right-clicked if you came from the timeline, and otherwise with today, or the next working day if today isn’t one. The End Date matches it and the Duration reads 0, so a milestone on that day needs nothing but a name. Overtype the start date with the one you want, say Wed 2 September for “Watertight”, and the Estimated End Date follows it to Wed 2 September, the Duration still 0. The Baseline and Actual bands behave the same way: give either one a start date and its end date mirrors it. Click OK and the diamond appears on the chart.
03 Converting a task you already have
You can also start from a task that already exists. There are two ways to convert it: tick a box in the Task Form, or type 0 as its duration.
With the Convert to Milestone tickbox
Open the task in the Task Form by double-clicking its row, and on the Task Details tab tick Convert to Milestone. Gantt Excel asks Convert this task to a milestone?
under a Confirm heading; answer Yes and the conversion happens immediately in the open form.
What changes when you say yes:
- The Estimated duration is set to 0 and the Estimated End Date is rewritten to match the Estimated Start Date.
- The same happens to the Baseline and Actual bands, but only where that band already has a start date. A band you never filled in is left empty.
- End Date and Duration lock in all three bands, and the Resource Cost figure is cleared.
- Work is recalculated from the new duration of 0, so it reads 0. When you click OK, any percentages set for the people on the task are dropped, because a milestone has no working time to book anyone for.
- The form retitles itself: the first tab becomes Milestone Details and the window heading becomes Edit Milestone.
Nothing is written to the sheet until you click OK. The Task Form covers the tickbox itself under Turning a task into a milestone; what happens after the conversion is on this page.
The tickbox is hidden on a parent (summary) task. Its dates are rolled up from its children, so there is nothing of its own to zero out.
A task linked to its predecessor by FS or SS converts like any other, and keeps its link: those are the two link types a milestone takes, so the link goes on placing the milestone’s date. On a task driven by an FF or SF link the tickbox is shown, but ticking it is refused. Section 05 explains why.
By typing 0 as the duration
A length of 0 is what makes a milestone, so a 0 typed into a task’s duration is taken as a request to convert it. That works in two places, on daily and hourly charts alike:
- The Duration cell in the task grid. Type 0 into the cell and press Enter.
- The Duration box in the Estimated band of the Task Form’s Task Details tab.
Either way you get the tickbox’s own question, Convert this task to a milestone?
under a Confirm heading. Answer Yes and the task is converted: the duration is 0 and the end date matches the start in the Estimated band, and in the Baseline and Actual bands wherever they have a start date, and the Resource Cost is cleared. Answer No and the duration the task had before comes back, its dates unchanged, with no further message.
The two places differ in when the change is saved. In the Task Form nothing reaches the sheet until you click OK, so Cancel still backs out. In the grid there is no OK step: the task is converted on the sheet as soon as you answer Yes.
A few cases don’t ask:
- Pasting or filling down a 0. Only a 0 typed into a single cell asks. Paste one into several rows, or fill it down, and you get
Please check the duration.
instead, and each task keeps its length. - A summary task. Its duration is rolled up from its children, so there is nothing to set to 0.
- A task driven by an FF or SF link. The 0 is refused with the same message the tickbox gives (see section 05), and the old duration comes back.
04 How a milestone is drawn
A task is drawn as a rectangle spanning its dates. A milestone has no span, so it is drawn as a diamond centred on its single date. That keeps it legible at any zoom level: a one-day bar shrinks to a sliver on a yearly view, a diamond doesn’t.
“Can a milestone show a baseline and an actual too?”
Yes. In a daily view each band draws its own diamond in that band’s colour, just as each band draws its own bar for a task. If you set a baseline on “Watertight” for Wed 2 September and the roof was actually finished on Mon 7 September, you get two diamonds three working days apart, and the slippage is visible without reading a date.
Whether those diamonds appear at all depends on the two tickboxes that control baseline and actual bars: Show Baseline Bars and Show Actual Bars, in Settings.
“And in the hourly view?”
Only the Estimated diamond is drawn. The hourly view doesn’t show baseline or actual bars at all, and Show Baseline Bars and Show Actual Bars are greyed out in Settings while it is on. Milestones follow the same rule: the renderer draws the Estimated diamond and hides any Baseline or Actual diamonds left over from a daily render.
This follows the view, not the chart. Switch an hourly chart into a daily view and its milestones get their baseline and actual diamonds back, with both tickboxes live again. Dependencies, status and resources work the same either way.
05 Milestones and dependencies
Milestones are wired into the schedule like anything else, but the two directions behave differently.
As a predecessor: no restrictions
Any task can wait on a milestone, using any of the four link types. This is the pattern to build your plan around. “Electrical first fix”, “Plumbing first fix” and “Windows and doors” each take an FS link from “Watertight”, so all three start the working day after the roof is finished. Push the roofing back a week and all three trades move with it, along with everything downstream of them.
On a daily chart a milestone is a moment at the start of its day, before any work that day. Its finish is its start, so the two links measured from a predecessor’s finish behave differently from the same links on a task:
- FS from a milestone: the successor can start on the milestone’s own date. The roof finishes on Tue 1 September, “Watertight” sits on Wed 2 September, and the three trades start that same Wednesday rather than the Thursday.
- FF from a milestone: the successor finishes on the last working day before the milestone’s date.
SS and SF already measure from the start, so they are unchanged, and so are links from ordinary tasks. A summary task that finishes on a milestone counts as finishing at that moment too. Hourly charts keep the ordinary rules. Lags still apply on top of all of this, counted in working days.
It is also the reliable way to link across phases. Pointing a task at a whole summary row is fragile; pointing it at that phase’s closing milestone is exact.
As a successor: Finish to Start and Start to Start only
Open a milestone’s Dependencies tab and the Type list offers just two entries:
| Type | Code | Offered on a milestone? | Why |
|---|---|---|---|
| Finish to Start | FS | Yes | Drives the milestone’s date from the predecessor’s finish |
| Start to Start | SS | Yes | Drives it from the predecessor’s start |
| Finish to Finish | FF | No | Drives an end date, which on a milestone only mirrors the start |
| Start to Finish | SF | No | Same reason |
Both omitted types drive a task’s end date and let the start follow from the duration. On a milestone the end date mirrors the start, so the four types collapse to two distinct outcomes, and the list offers just those two.
The rule holds outside the list too. On daily and hourly charts alike, a task driven by an FF or SF link cannot be converted. Tick Convert to Milestone on one, or type 0 as its duration, and you get Fit kitchen units cannot become a milestone while a Finish to Finish or Start to Finish dependency drives it. A milestone takes Finish to Start and Start to Start dependencies only. Change those dependencies, or remove them, first.
A file saved by an earlier version can hold such links already, because earlier versions let a task keep them when it was converted. What happens to them depends on the chart:
- Daily chart. When the file is opened, or the chart is imported, each FF link into a milestone becomes FS and each SF becomes SS, keeping its lag, and a message of its own lists the links that changed (a long list shows its first eight).
- Hourly chart. The links are kept, and the milestone goes on being scheduled by them. You can’t add another link of that kind.
The lag works as normal on the two types that are offered. “Final inspection” with an FS link and a lag of 2 lands two working days after its predecessor finishes, skipping weekends and holidays on the resource’s calendar. The four link types in full are covered in the Dependencies guide.
06 Turning a milestone back into a task
The Task Form has no “convert back” control. Convert to Milestone is only shown on a row that is currently a task, and it disappears once the conversion happens. After you have clicked OK, reopening the row shows a Milestone Details tab with no tickbox to untick.
Cancel is your undo, and it only works while the form is open. If you are unsure whether a row should be a moment or a stretch of work, decide before you tick the box or answer Yes.
A related limit: a milestone cannot have children. Try to indent a task underneath one and Gantt Excel stops you with Milestones cannot have child tasks under them.
A parent’s dates are rolled up from its children, and a milestone has no span to roll anything up into. Indenting and summary rows are covered in the outline guide.
07 Common questions
Why can’t I type a duration on my milestone?
I don’t see Convert to Milestone on this task. Where has it gone?
Why are Finish to Finish and Start to Finish missing from my milestone’s Type list?
My baseline diamond has vanished in the hourly view. Is it a bug?
Should I use a milestone or a one-day task?
Can I group tasks under a milestone to mark the end of a phase?
Milestones cannot have child tasks under them.The usual shape is the other way round: a summary task holding the phase’s work, with a milestone as the last row inside it marking the phase complete. Other phases then link to that milestone.
Related: The Task Form · Adding, editing & deleting tasks · Linking tasks with dependencies · Summary tasks, indenting & the WBS