Project Plan Template: The 9 Sections, Excel Gantt Steps and an Example

8 min read ยท 2026-10-25

A project plan template is a reusable structure that captures what a project will deliver, how the work breaks down, who does what, when each part is due, what could go wrong and how you will report progress. A good one has two parts: a short plan document (in Word or Google Docs) for scope, roles and rules, and a schedule (in Excel, Google Sheets or a project tool) for tasks, dates and dependencies.

Below you will find the project lifecycle the template follows, the nine sections to include and what goes in each, step-by-step instructions to build the schedule and a Gantt chart in Excel, a filled-in example for a 12-week help desk tool rollout, a short who-owns-what list and how to present the plan at kickoff and to your sponsor.

The roadmap at a glance

Goal: A 12-week project delivered to an approved scope, with a baselined schedule, named owners, a live risk log and a signed closure report. Duration: 12 weeks

  1. Initiate (Week 1)

    Agree on why the project exists, what it must deliver and who decides.

    • Write the project summary: problem, objective, success measures and the target end date.
    • Name the sponsor, the project manager and the core team.
    • List what is in scope and, just as important, what is out of scope.
    • Get the sponsor to sign the summary before planning starts.

    Milestone: Project summary and scope signed by the sponsor.

  2. Plan (Weeks 2-3)

    Turn the scope into tasks, dates, owners and rules.

    • Break deliverables into a work breakdown structure, down to tasks of a few days each.
    • Estimate each task with the person who will do it, and link tasks that depend on each other.
    • Fill in the RACI, the risk log and the communication plan.
    • Run a kickoff meeting and walk the team through the plan.
    • Save the approved schedule as the baseline.

    Milestone: Kickoff held and schedule baselined, with every task assigned to one owner.

  3. Execute (Weeks 4-8)

    Do the work while tracking progress against the baseline.

    • Hold a short weekly status meeting focused on blockers and next week's tasks.
    • Update task progress and dates in the schedule every week.
    • Review the risk log weekly and add new risks with an owner.
    • Route every scope change through the change request process.

    Milestone: All build deliverables complete and accepted by their reviewers.

  4. Test and prepare (Weeks 9-10)

    Make sure the result works and the people who use it are ready.

    • Run user acceptance testing with real users and log defects.
    • Fix the defects that block go-live and agree on what can wait.
    • Train users and publish short how-to guides.
    • Hold a go or no-go meeting with the sponsor using a readiness checklist.

    Milestone: Go decision recorded by the sponsor, with no open blocking defects.

  5. Launch and support (Week 11)

    Go live and handle early issues quickly.

    • Follow the launch checklist step by step and record what was done.
    • Run daily check-ins for the first week to catch issues early.
    • Hand ongoing support to the team that will own the result.

    Milestone: Live in production, with support handed over to the business owner.

  6. Close (Week 12)

    Confirm the results and capture what to repeat or change.

    • Compare results with the success measures from the project summary.
    • Run a lessons-learned session with the team.
    • Close open tasks, archive documents and release the team.

    Milestone: Closure report signed by the sponsor.

The nine sections of a project plan template

Keep the plan document short, ideally a few pages. People must be able to read it in one sitting. Use one heading per section, in the order below, and put the detailed schedule in a separate spreadsheet or project tool that the document points to.

If your company already has a project charter, sections one to three may live there. In that case, copy the key lines into the plan so the team has one place to look.

  • 1. Project summary: the problem, the objective in one sentence, success measures and the target end date.
  • 2. Scope: deliverables in scope, items out of scope, and assumptions.
  • 3. Stakeholders and team: sponsor, project manager, core team, business owner and who must be consulted.
  • 4. Work breakdown and milestones: deliverables broken into work packages, plus the five to eight milestones that matter most.
  • 5. Schedule: a link to the task list with dates, owners and dependencies, and a Gantt view.
  • 6. RACI: for each deliverable, who is responsible, accountable, consulted and informed.
  • 7. Risks and dependencies: each risk with likelihood, impact, owner and response.
  • 8. Communication plan: which meeting or report, for whom, how often and who runs it.
  • 9. Change control and approvals: how scope changes are requested, assessed and approved, and who signs off each phase.

How to build the schedule and Gantt chart in Excel

Set up the schedule as a table with these columns, left to right: ID, Phase, Task, Owner, Start, Duration (days), End, Depends on, Status and Percent complete. Group tasks under their phase and give phase rows a light fill color so they stand out.

Then build a simple Gantt chart from the Start and Duration columns with the steps below. The same method works in Google Sheets with Insert, then Chart, and a stacked bar chart, though menu names differ slightly.

  • Enter the formula for End as Start plus Duration, or use WORKDAY to skip weekends.
  • Select the Task, Start and Duration columns, then choose Insert, then the bar chart icon, then Stacked Bar.
  • Select the first series (Start), open Format Data Series and set Fill to No fill, so only the duration bars show.
  • Open Format Axis on the vertical axis and tick Categories in reverse order, so the first task appears at the top.
  • Set the minimum of the horizontal axis to the project start date so the bars do not float far to the right.
  • Add milestones as tasks with a duration of zero and mark them with a diamond in the Task name, or color their row.
  • Use conditional formatting on the Status column to color late tasks, so problems show at a glance.

Example: a filled-in plan for a help desk tool rollout

Picture an IT team replacing a shared email inbox with a ticketing tool for a 400-person company. The sponsor is the IT director. The business owner is the service desk manager. The project has twelve weeks to go live before the start of the busy season.

Here is how the key sections of the template look once filled in.

  • Summary: every employee request goes through one ticketing tool with categories and response targets, live by week 11. Success measures: all requests logged as tickets, response targets visible on a dashboard.
  • Scope: in scope are the employee portal, email-to-ticket, categories, response targets and agent training. Out of scope: asset management and HR requests, planned for a later phase.
  • Milestones: scope signed (week 1), kickoff and baseline (week 3), configuration complete (week 8), go decision (week 10), live (week 11), closure (week 12).
  • RACI extract: service desk manager accountable for categories and response targets, IT systems administrator responsible for configuration, HR consulted on employee communication, all staff informed.
  • Top risks: email routing rules break during cutover (owner: systems administrator, response: test with a pilot group first). Agents keep using the old inbox (owner: service desk manager, response: make the old inbox auto-reply with a portal link from go-live).
  • Communication: weekly 30-minute status meeting with the core team, a one-page update to the sponsor every Friday, and an all-staff announcement one week before launch.

Who owns what

A plan without owners is a wish list. Every task, risk and deliverable needs exactly one name next to it, not a team name.

Write these roles into section three of the template and confirm them at kickoff, so nobody is surprised later.

  • Sponsor: approves scope, budget and phase gates, and removes blockers the team cannot solve.
  • Project manager: owns the plan, the schedule, the risk log and status reporting.
  • Business owner: defines requirements, accepts deliverables and owns the result after launch.
  • Task owners: estimate, deliver and update their tasks each week.
  • Subject matter experts: review designs, test and answer questions within agreed times.

How to present the plan at kickoff and to your sponsor

At kickoff, show the team the objective, the scope, the milestone timeline, the RACI and how you will run the weekly meeting. Spend most of the time on scope and on who does what. Ask each owner to confirm their dates in the room. A plan people helped build is a plan they will defend.

For the sponsor, use one slide: the objective, the milestone timeline with status colors, the top three risks with owners, and the decisions you need. Leave the task list out. If the sponsor wants detail, share the schedule after the meeting. Send the same one-slide update every week so changes stand out.

How to adapt the template

For a small project of a few weeks, merge the sections into a one-page plan: summary, scope, milestones, owners, top risks and the weekly meeting. Skip the formal change control and just log changes with the date and who approved them.

For a large or regulated project, keep all nine sections and add a budget section, a quality plan and a procurement section if vendors are involved. If your team works in sprints, keep the summary, scope, milestones, RACI and risks, and let the backlog in Jira or Azure DevOps replace the task schedule.

Common mistakes to avoid

  • Writing a plan with no out-of-scope list invites endless additions, so write down what the project will not deliver and have the sponsor sign it.
  • Estimating tasks without the people who do them creates dates nobody believes, so estimate with each task owner.
  • Assigning tasks to teams instead of people means nobody feels responsible, so put one named owner on every task.
  • Never saving a baseline hides how far the project has slipped, so baseline the schedule at kickoff and compare against it each week.
  • Filling the risk log once and forgetting it leaves you surprised by known problems, so review risks in every weekly status meeting.
  • Accepting scope changes in hallway conversations breaks the schedule, so route every change through a written request with an impact on dates.

Frequently asked questions

What should be included in a project plan template?

Include a project summary, scope with in and out items, stakeholders and team, work breakdown and milestones, the schedule, a RACI, risks and dependencies, a communication plan and change control. Keep the document short and put the detailed task schedule in a spreadsheet or project tool.

How do I create a project plan in Excel?

Make a table with task, owner, start date, duration, end date, dependency and status columns. Then insert a stacked bar chart from the task, start and duration columns, hide the start series and reverse the task order to get a Gantt view. Add conditional formatting to flag late tasks.

What is the difference between a project plan and a project charter?

A project charter authorizes the project and states its purpose, high-level scope, sponsor and objectives. A project plan explains how the work will be done: tasks, schedule, roles, risks and communication. The charter comes first and the plan builds on it.

How detailed should a project plan be?

Detailed enough that every task has an owner and can be finished in a few days, and no more. Keep the next few weeks in detail and later phases at milestone level, then add detail as you get closer. A plan too detailed to update weekly will soon be out of date.

What is a baseline in a project plan?

A baseline is a saved copy of the approved schedule, scope and budget at the start of the project. You compare actual progress against it to see how far dates have moved. Re-baseline only when the sponsor approves a major change.

Generate this roadmap with AI