Free, no sign-up to start: the plan opens as a live, editable Gantt chart. 19 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 |
|---|---|---|---|---|
| Initiate | Project charter and objectives | 3 days | Day 1 | Nothing (starts first) |
| Initiate | Stakeholder register | 2 days | Day 4 | Project charter and objectives |
| Initiate | Sponsor approval to plan | 1 day | Day 6 | Stakeholder register |
| Plan | Scope statement and deliverables | 4 days | Day 7 | Sponsor approval to plan |
| Plan | Work breakdown and estimates | 4 days | Day 11 | Scope statement and deliverables |
| Plan | Schedule and resource plan | 3 days | Day 15 | Work breakdown and estimates |
| Plan | Budget | 3 days | Day 15 | Work breakdown and estimates |
| Plan | Risk register | 2 days | Day 15 | Work breakdown and estimates |
| Plan | Communication plan | 2 days | Day 7 | Sponsor approval to plan |
| Plan | Baseline sign-off | 1 day | Day 18 | Schedule and resource plan, Budget, Risk register, Communication plan |
| Execute | Kickoff meeting | 1 day | Day 19 | Baseline sign-off |
| Execute | Deliverable 1: build and review | 15 days | Day 20 | Kickoff meeting |
| Execute | Deliverable 2: build and review | 12 days | Day 20 | Kickoff meeting |
| Monitor | Mid-project review and change requests | 2 days | Day 32 | Deliverable 2: build and review |
| Execute | Deliverable 3: build and review | 10 days | Day 35 | Deliverable 1: build and review, Mid-project review and change requests |
| Monitor | Quality check and acceptance testing | 5 days | Day 45 | Deliverable 3: build and review, Deliverable 2: build and review |
| Close | Customer acceptance and sign-off | 2 days | Day 50 | Quality check and acceptance testing |
| Close | Handover and documentation | 3 days | Day 52 | Customer acceptance and sign-off |
| Close | Lessons learned and closure report | 2 days | Day 55 | Handover and documentation |
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 77 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 project plan
Most project plan templates are documents: a page for scope, a table for the schedule, a list of risks. They are fine on the day you write them and out of date a week later, because nothing connects the schedule to the work. This template keeps the same structure but puts every planning step and every deliverable on one Gantt chart, linked, so when a task slips you can see what moves with it.
It follows the five stages most project management courses teach: initiate, plan, execute, monitor and close. The planning tasks (scope, work breakdown, schedule, budget, risks and communication) run partly in parallel and all feed a baseline sign-off, which is the point where the plan stops being a draft. Three deliverables then run in execution, with a mid-project review and an acceptance check before closing.
It is sized for a project of about two months with a small team. Rename the three deliverables to the real outputs of your project, change the durations to your own estimates, and the finish date updates for you.
Who it's for: Project managers, team leads and consultants who need a full project plan that the sponsor, the team and the client can all read.
How to use it
- Use this template. Click Use this template. The plan opens in the editor with initiate, plan, execute, monitor and close as lanes and every link drawn. No sign-up is needed to start.
- Write your own deliverables. Rename Deliverable 1, 2 and 3 to the real outputs of your project and split any that are longer than three weeks into smaller tasks. Keep the links: each deliverable should wait for what it really needs.
- Estimate with the people doing the work. Replace the example durations with estimates from the team. The finish date updates as you type, so you find out in the meeting whether the plan fits the deadline.
- Baseline it and share it. Once the sponsor signs off, save a baseline so you can compare actual dates against the agreed plan. Share a read-only link with stakeholders; they do not need an account.
What a project plan needs to answer
A sponsor reading a project plan wants four answers: what will be delivered, when, for how much, and what could stop it. The scope statement answers the first, the schedule the second, the budget the third and the risk register the fourth. The communication plan says how they will hear about changes. Those five planning tasks are all on this chart, so none of them is quietly skipped.
The work breakdown is the task that connects scope to schedule. Until the deliverables are broken into pieces small enough to estimate, any finish date is a guess. In this template the schedule, budget and risk register all wait for the work breakdown, which is the order that works in practice. If you need to go deeper, the work breakdown structure template shows how to break a project down level by level.
Reading the critical path in this plan
The darker bars are the critical path: the chain of tasks with no slack. Here it runs from the charter through scope, work breakdown, the schedule and the budget, then through deliverable 1, deliverable 3, acceptance testing and closing. Deliverable 2, the communication plan and the risk register have slack, so a day or two lost on them does not move the end date.
That tells you where to spend your attention. If deliverable 1 is late, the project is late, so it is the one to staff first and check most often. If you add a dependency the plan did not have, for example deliverable 2 needing an output from deliverable 1, the critical path changes and the chart shows it straight away.
Planning tips
- Keep the plan at a level the sponsor can read on one screen. Detailed day-to-day tasks can live in a team board; the plan should show deliverables, gates and dependencies.
- Put a name on every task in the owner field. A task without an owner is the one that is still open at the status meeting.
- Treat the baseline sign-off as a real gate. Changes after it go through the mid-project review as change requests, so the plan and the agreed scope stay in step.
- Leave the closing tasks in. Handover and lessons learned take real days, and leaving them out makes every plan look shorter than the work.
Frequently asked questions
- What should a project plan template include?
- Objectives, scope and deliverables, a work breakdown with estimates, a schedule with dependencies, a budget, a risk register and a communication plan, plus how the project will be monitored and closed. This template puts all of those on one Gantt chart as linked tasks.
- What is the difference between a project plan and a project schedule?
- The schedule is one part of the plan: the tasks, durations, dependencies and dates. The plan also covers scope, budget, risks and communication. On this template the planning steps and the schedule sit together, so you can see that the schedule cannot be finished before the work breakdown is.
- Can I use this project plan template in Excel?
- Yes. Download CSV gives you every task with start date, end date, phase and dependencies, which opens in Excel or Google Sheets. The Excel Gantt chart guide shows how to turn it into bars with conditional formatting.
- Is this project plan 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
- Work Breakdown Structure (WBS) Gantt chart template
- Resource Plan Gantt chart template
- Milestone Chart Gantt chart template
- Implementation 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.