The Milestone tab does not exist as a standalone ribbon tab in Microsoft Project 2016. Milestones are created and managed through the Task tab, the Format tab for Gantt Chart views, and the Task Information dialog. The confusion usually comes from older documentation, from Project 2007's menu system, or from third-party add-ins that add their own tabs.
This distinction matters because Project 2016's ribbon is context-sensitive. What you see depends on which view is active, which table is applied, and whether you have selected a task or a chart element. A user hunting for a milestone button in a static location will not find one. The functionality is distributed across several locations that each serve a different milestone-related job.
How the ribbon exposes milestone functions
Project 2016 organizes commands by what you are doing, not by what object you are touching. There is no object-centric "Milestone" tab the way Excel has a Chart Design tab when a chart is selected. Instead, milestone tools appear inside broader task and format groups.
The primary creation path is the Task tab. In the Insert group, the Milestone command inserts a new task flagged as a milestone, with zero duration by default. This is the closest thing to a dedicated milestone button in the default Gantt Chart view.
The Format tab appears when a Gantt Chart view is active. Its Bar Styles and Gantt Chart Style groups control how milestone diamonds render, including shape, color, and label position. This is where you change appearance, not where you create records.
The Task Information dialog, reached by double-clicking a task or pressing Shift+F2, contains the Advanced tab. The "Mark task as milestone" checkbox lives there. This is the authoritative toggle that determines whether a task behaves as a milestone regardless of its duration.
The Filter drop-down on the View tab includes Milestones as a built-in filter. Applying it hides non-milestone tasks so you can audit the milestone schedule in isolation.
A plain-language way to hold this: creation lives on the Task tab, appearance lives on the Format tab, and the true milestone flag lives in Task Information.
Why the milestone flag is separate from duration
A common misconception is that setting duration to zero days makes a task a milestone. It usually does, but the two properties are independent switches that Project treats differently.
Duration is a scheduling value. A zero-day duration task consumes no working time and sits at a single point on the timeline. The milestone flag is a behavioral property stored in the task record. When the flag is set, Project renders the task as a diamond in Gantt views and reports it in milestone filters, even if its duration is greater than zero.
This separation exists because some organizations track "milestone tasks" that span a review window. A gate review might occupy three working days of calendar time but still need to appear in milestone rollups and executive reports. Setting duration to three days and checking the milestone flag satisfies both needs.
The counterintuitive detail: if you set duration to zero but leave the milestone flag unchecked, some views and exports will treat the task as an ordinary zero-duration task. The diamond may still appear in the default Gantt Chart because Project's default bar style maps zero-duration tasks to the milestone shape. Change the bar style, and the visual cue disappears while the task remains zero-duration.
Conversely, checking the milestone flag on a task with a positive duration forces the diamond rendering but does not collapse the duration. The task still occupies its scheduled span in the timeline and in resource calculations.
Quantified context for milestone behavior
Default milestone duration in Project 2016 is 0 days, expressed as "0 days" in the Duration field. The default constraint is As Soon As Possible, which lets the milestone float with predecessor logic rather than pinning it to a date.
Milestone diamonds render at roughly 7 to 9 pixels in the default Gantt Chart at 100 percent zoom, depending on display scaling. That small footprint is why label placement matters: the default label position is to the right of the diamond, and long task names overlap adjacent bars.
The built-in Milestones filter reduces a typical 200-line project schedule to the subset of flagged tasks, often 10 to 30 rows in a phase-gate plan. That reduction is the practical reason the filter exists.
Project 2016 supports up to 10,000 tasks per project file in standard configurations, though performance degrades well before that ceiling. Milestone counts are bounded by the same limit.
The rollup milestone feature, which lifts a subtask milestone to the summary bar, is controlled by the "Rollup" checkbox in Task Information's General tab. It does not require the milestone flag, but it is most commonly used with it.
Where numbers do not help, the qualitative point stands: milestone behavior is binary and view-dependent, not gradual.
Edge cases that break milestone workflows
Manual scheduling changes the rules. When a task is set to manually scheduled, Project 2016 allows a duration and dates that ignore calendar logic. A manually scheduled milestone can carry a nonzero duration and still be flagged, and its diamond may not sit at a predictable point.
Summary tasks cannot be marked as milestones. The checkbox is grayed out or ignored for summary rows. If you need a phase-level milestone, create it as a separate task and use rollup.
Milestones inside subprojects behave differently in a master project. The flag travels with the subproject file, but the master project's filters operate on the inserted project summary, not on individual subproject milestones unless you expand the insertion.
Copied milestones can lose context. Pasting a milestone between projects sometimes carries the flag but drops custom calendars or constraint types, producing a milestone pinned to an unexpected date.
Milestone filters in Project 2016 do not catch rollup milestones whose flag is unchecked. Auditing by filter alone will miss them.
Common misconceptions about the tab
The most persistent myth is that Project 2007's menu structure carried forward. Project 2007 used a menu bar with an Insert menu that contained a Milestone command. Project 2010 replaced menus with the ribbon, and Project 2016 continues that ribbon model. Documentation and tutorials written for 2007 still circulate and fuel the search for a missing tab.
A second myth is that the Format tab is the "milestone tab" because it changes diamond appearance. It is context-sensitive and only appears in Gantt views. Switch to a Network Diagram or Timeline view and the tab changes entirely.
A third myth is that milestones live in a separate table. They do not. A milestone is a row in the same task table, distinguished by its flag. You can add the Milestone column to any task table to see the Yes/No flag directly.
A fourth myth is that the Timeline view has its own milestone controls. The Timeline view can display milestones added to it, but the add and remove actions live on the Format tab of the Timeline view, not on a milestone-specific tab.
Bullet list of red flags to watch for:
A tutorial showing an Insert menu with a Milestone item is describing Project 2007 or earlier. A screenshot with a ribbon tab labeled "Milestone" comes from an add-in, not stock Project 2016. A task with zero duration but no flag may vanish from milestone filters after a bar style change. A grayed-out milestone checkbox means you selected a summary task, not a regular task. A master project filter that returns nothing may be scoped to the insertion summary, not subproject tasks.
Comparing milestone access paths
| Location in Project 2016 | What it does | When to use it | Requires Gantt view | Affects the milestone flag |
|---|---|---|---|---|
| Task tab, Insert group, Milestone | Creates a new flagged task at zero duration | Adding a milestone to the schedule | No | Yes, sets it |
| Task Information, Advanced tab | Toggles the "Mark task as milestone" checkbox | Converting an existing task to a milestone | No | Yes, the authoritative switch |
| Format tab, Bar Styles | Changes diamond shape, color, and label | Adjusting how milestones look | Yes | No |
| View tab, Filter, Milestones | Hides all non-milestone rows | Auditing or reporting the milestone set | Yes for Gantt output | No |
| Task Information, General tab, Rollup | Lifts a milestone to its summary bar | Showing phase milestones on summary rows | No | No, separate property |
| Timeline view, Format tab | Adds or removes items from the timeline | Building an executive timeline | No | No |
The table makes the division of labor explicit: two locations touch the flag, and the rest touch presentation or filtering. That split is the answer to the original question stated as a grid.
Practical steps to find and use milestone controls
Start by confirming your view. Click the View tab and select Gantt Chart. The Format tab only appears with a Gantt view active, and most milestone appearance tools live there.
To create a milestone, use the Task tab and click Milestone in the Insert group. Type the milestone name directly into the new row. Press Enter. The duration should read 0 days.
To convert an existing task, double-click the row to open Task Information. Go to the Advanced tab. Check "Mark task as milestone." Click OK. Verify the diamond appears in the Gantt chart.
To audit the milestone set, go to View, then Filter, then Milestones. The row count in the status bar gives you the milestone total. Clear the filter to return to the full schedule.
To expose the flag as a column, right-click a column header, choose Insert Column, and select Milestone. The column shows Yes or No for each task.
To fix an unexpected nondiamond, check three things in order: the view is Gantt Chart, the task is not a summary task, and the bar style for milestones has not been customized to a non-diamond shape.
If you need a milestone on the Timeline, right-click the task and choose Add to Timeline. The diamond appears on the timeline band, and its display options live on the Timeline view's Format tab.
Limits of this explanation and version caveats
Project 2016's ribbon is stable and well documented, but the product has been superseded by Project for the web, Project Online, and later desktop releases. Menu locations in Project 2019 and Project 2021 remain similar for the Task tab and Task Information paths, but Microsoft has shifted emphasis toward cloud-hosted project tools where the desktop ribbon model does not apply.
Localization changes labels. In non-English builds, the Task tab, Milestone command, and "Mark task as milestone" checkbox carry translated names, so searching for the English string fails even though the command exists. Match by icon and group position instead.
Third-party add-ins can add tabs and rename commands. If your ribbon does not match Microsoft's default, check File, Options, Add-ins to see whether a custom add-in is injecting commands.
Custom ribbon modifications via XML also persist across files and profiles, so a colleague's screenshot may not match your installation.
This article describes software behavior and is general educational information, not a technical support guarantee for a specific installation. For licensing, deployment, or configuration questions, consult Microsoft's official documentation or a qualified IT professional.