Free, no sign-up to start: the plan opens as a live, editable Gantt chart. 14 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 | Kickoff and goals agreed | 1 day | Day 1 | Nothing (starts first) |
| Start | Requirements gathered | 6 days | Day 2 | Kickoff and goals agreed |
| Start | Milestone: plan approved | 1 day | Day 8 | Requirements gathered |
| Design | Concept and design | 8 days | Day 9 | Milestone: plan approved |
| Design | Supplier and resource booking | 5 days | Day 9 | Milestone: plan approved |
| Design | Milestone: design signed off | 1 day | Day 17 | Concept and design |
| Delivery | Build phase 1 | 10 days | Day 18 | Milestone: design signed off, Supplier and resource booking |
| Delivery | Progress review with stakeholders | 1 day | Day 28 | Build phase 1 |
| Delivery | Build phase 2 | 10 days | Day 28 | Build phase 1 |
| Delivery | Training and rollout materials | 6 days | Day 18 | Milestone: design signed off |
| Launch | Testing and fixes | 6 days | Day 38 | Build phase 2 |
| Launch | Milestone: go-live | 1 day | Day 44 | Testing and fixes, Training and rollout materials |
| Launch | Post-launch support | 10 days | Day 45 | Milestone: go-live |
| Close | Project review and close-out | 2 days | Day 55 | Post-launch support |
Durations are examples to replace with your own estimates, not benchmarks. Some work runs in parallel, so the plan takes 56 days instead of the 68 it would take one task at a time. The 11 darker bars are the critical path: a day lost on any of them moves the finish date.
About this project timeline
A project timeline is the version of the plan you show people. It needs to answer "when?" at a glance: when the plan is approved, when the design is signed off, when it goes live. This template is built around those moments. Each phase ends in a one-day milestone, and the work between them is linked so the milestones move when the work does.
It covers a typical project of about eight weeks: start-up, design, delivery in two build phases, testing and go-live, then a support period and close-out. Work that does not need to wait, such as booking suppliers and writing training material, runs in parallel with the main chain, so the timeline is as short as the dependencies allow.
Use it for an internal change, a client project or a system rollout. If your project is in a specific field, the industry templates (construction, software, events, marketing and more) have more detailed task lists with the same structure.
Who it's for: Project managers and team leads who need a clear timeline to present to sponsors, clients or a steering group.
How to use it
- Use this template. Click Use this template to open the timeline in the editor with phases as lanes and the links drawn. No account is needed to start editing.
- Set the go-live date first. Move the plan so the go-live milestone lands on your target date, then check whether the kickoff still lands in the future. If it does not, the timeline is telling you the date needs more time or less scope.
- Rename the milestones. Name each milestone after the decision it represents, such as "Design signed off by the client". A milestone everyone understands is easier to hold people to than a phase name.
- Share a read-only link. Send stakeholders a read-only link. They see the timeline without an account. Make a new link after big changes, because a link shows the plan as it was when you made it.
Milestones are what stakeholders read
Most people looking at a project timeline read the milestones and skip the bars. That is why the template has one at the end of each phase: plan approved, design signed off and go-live. They are one-day tasks so they show clearly on the chart and can carry an owner, which is usually the person who has to say yes.
Keep milestones few and meaningful. A timeline with twenty milestones is a task list with diamonds on it. Three to six decision points are enough for most projects, and each should be something that can clearly be said to have happened or not.
Project timeline or project plan?
A project plan covers scope, budget, risks and communication as well as the schedule; the project plan template on this site includes those steps. A timeline is the schedule part, shaped for an audience: fewer tasks, clear milestones and a finish date. Many teams keep both, with the timeline as the view they present and the plan as the detail they manage from.
On a Gantt chart they can be the same file. Build the detailed plan, then share the timeline with the milestones and phases that matter to the reader. Because the tasks are linked, the dates you present always come from the work, not from a slide someone typed last month.
Planning tips
- Show the timeline in weeks or months for executives and in days for the team. The underlying plan stays the same.
- Put supplier lead times on the chart as tasks. Bookings and deliveries are the dependencies most often left off a timeline.
- Add a progress review halfway through delivery. It is the cheapest point to change direction.
- Keep the post-launch support period visible, so the team is not booked onto the next project the day after go-live.
Frequently asked questions
- What should a project timeline template include?
- The phases of the project, the main tasks in each, their durations, which tasks depend on which, and the milestones that mark decisions or hand-offs. This template has all of those, with a critical path so you can see which tasks set the finish date.
- How do I make a project timeline?
- List the main pieces of work, estimate how long each takes, decide what each one waits for, then add milestones for the decisions. Starting from this template, you only rename tasks and change durations; the dates are worked out from the links.
- Can I download the project timeline for Excel or Google Sheets?
- Yes. Download CSV on this page gives every task with its start date, end date, phase and dependencies, which opens in Excel and Google Sheets. The download on this page is free.
- What is the difference between a timeline and a Gantt chart?
- A simple timeline shows events or milestones along a line. A Gantt chart shows each task as a bar with a start and an end, and the links between them. This project timeline is drawn as a Gantt chart so durations and dependencies are visible.
Related templates and guides
- Project Plan Gantt chart template
- Milestone Chart Gantt chart template
- Simple Project Plan Gantt chart template
- 12-Month Project Plan Gantt chart template
- Project Roadmap 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.