Free, no sign-up to start: the plan opens as a live, editable Gantt chart. 17 tasks across 5 phases, about 8 weeks from start to finish with the parallel work shown.
What's in the template
| Phase | Task | Duration | Starts | Depends on |
|---|---|---|---|---|
| Start | Project kickoff | Milestone | Day 1 | Nothing (starts first) |
| Start | Requirements workshops | 5 days | Day 1 | Project kickoff |
| Start | Requirements document | 4 days | Day 6 | Requirements workshops |
| Start | M1: Requirements signed off | Milestone | Day 10 | Requirements document |
| Design | Solution design | 8 days | Day 10 | M1: Requirements signed off |
| Design | Budget and vendor quotes | 6 days | Day 10 | M1: Requirements signed off |
| Design | M2: Design and budget approved | Milestone | Day 18 | Solution design, Budget and vendor quotes |
| Build | Build phase 1 | 15 days | Day 18 | M2: Design and budget approved |
| Build | Build phase 2 | 12 days | Day 33 | Build phase 1 |
| Build | Training materials | 8 days | Day 18 | M2: Design and budget approved |
| Build | M3: Build complete | Milestone | Day 45 | Build phase 2 |
| Test | Testing and fixes | 8 days | Day 45 | M3: Build complete |
| Test | M4: Go/no-go decision | Milestone | Day 53 | Testing and fixes, Training materials |
| Launch | Launch | 2 days | Day 53 | M4: Go/no-go decision |
| Launch | M5: Launched | Milestone | Day 55 | Launch |
| Launch | Post-launch review | 3 days | Day 55 | M5: Launched |
| Launch | M6: Project closed | Milestone | Day 58 | Post-launch review |
Durations are examples to replace with your own estimates, not benchmarks. Some work runs in parallel, so the plan takes 57 days instead of the 71 it would take one task at a time. The 15 darker bars are the critical path: a day lost on any of them moves the finish date.
About this milestone chart
A milestone chart answers the question sponsors actually ask: are we going to hit the dates that matter? It shows the checkpoints (requirements signed off, design approved, build complete, go/no-go, launch) as diamonds on a timeline, without making the reader study every task.
The problem with a milestone chart drawn on its own is that the dates are wishes. Nothing connects "build complete" to the build. This template keeps the milestones front and centre but links each one to the tasks that lead to it, so if the second build phase runs a week long, the build-complete milestone, the go/no-go and the launch all move with it.
The example is a project of about eight weeks with seven milestones. Rename the milestones to your own checkpoints, replace the tasks in between, and the milestone dates follow your estimates.
Who it's for: Project managers who report to a sponsor or steering group, and anyone who needs a one-screen view of the dates that matter.
How to use it
- Use this template. Click Use this template. The plan opens in the editor with the milestones drawn as diamonds and the tasks linked to them. No sign-up is needed.
- Name your own milestones. Rename each milestone after a decision or a deliverable someone outside the team will recognise, such as "Contract signed" or "Beta live". Delete any your project does not have.
- Fill in the work between them. Replace the example tasks with the real work that leads to each milestone and link each task to the milestone it feeds. The milestone dates move as you change durations.
- Share the milestone view. Share a read-only link with the sponsor. The diamonds give them the dates they care about, and the bars show the work behind each one if they want it.
What makes a good milestone
A milestone has no duration. It marks a moment: something approved, delivered, decided or launched. "Testing" is not a milestone because it takes time; "Testing complete and signed off" is. If you cannot say who would confirm that a milestone has happened, it is probably a task in disguise.
Good milestones are few and spaced out. Seven across an eight-week project is about right: one every week or two gives a steady rhythm of checkpoints without turning the chart into a list. Milestones that come with a decision, like the go/no-go here, are the most useful, because they force a conversation while there is still time to act.
How the milestones in this chart depend on each other
The go/no-go decision (M4) waits for two things: testing and fixes, and the training materials. Testing is on the critical path; training materials are not, and have several weeks of slack. That tells you the go/no-go date is set by testing, so testing is where to watch for slippage.
M2 is similar. It waits for both solution design and the budget quotes. Design takes eight days and quotes take six, so the quotes have two days of slack. If a vendor is slow to quote, you have two days before M2 moves. A milestone chart that is linked to the work tells you this; one drawn by hand does not.
Planning tips
- Put a name on each milestone: the person who will say it has been reached.
- Report milestone dates as forecast versus plan. A milestone that has moved three times is the conversation to have at the steering meeting.
- Keep milestones out of the critical path discussion only if they truly have slack. Here M2 to M6 all sit on the critical path, so every one of them moves the end date.
- Use the same milestone names in status reports, the chart and the budget so people recognise them everywhere.
Frequently asked questions
- What is a milestone chart?
- A milestone chart shows a project's key checkpoints as diamonds on a timeline. A Gantt chart with milestones adds the tasks that lead to each one, so a milestone's date comes from the work rather than being typed in.
- How many milestones should a project have?
- Enough that something meaningful is confirmed every week or two, and few enough that a sponsor can read them all on one screen. This eight-week example has seven, counting kickoff.
- What is the difference between a milestone and a task?
- A task takes time and has an owner doing the work. A milestone takes no time: it marks the moment a task or a group of tasks is finished and accepted.
- Does gantt-chart.io draw milestones as diamonds?
- Yes. The milestones in this template open in the editor as diamonds, and the tasks after them start on the milestone's day. Download CSV lists them with a duration of 0 days.
- Is this milestone chart template free?
- Yes. Opening and editing it in the browser is free with no sign-up, and the CSV download on this page is free. A free account keeps one saved project.
Related templates and guides
- Project Timeline Gantt chart template
- Project Roadmap Gantt chart template
- Project Plan Gantt chart template
- Resource Plan Gantt chart template
- Smartsheet alternative
- Free Gantt chart maker, no sign-up
- Critical path calculator
- Free timeline templates
- All Gantt chart templates
- Gantt chart examples
- How to make a Gantt chart
- Excel Gantt chart template
The free plan saves one project. Downloads from the editor (PDF, CSV) and more projects are on Solo, $12/month.