Template

Project Plan Template

Define goals, scope, milestones, tasks and owners for any project in one clear document, from a website launch to an office move.

Updated November 19, 2026In Meetings & ProjectsFree download: Excel, Word, PDF

Download this template free

No sign-up needed. Word and Excel files also open in Google Docs, Google Sheets and Apple Pages/Numbers. Letter size (8.5 × 11 in).

Project Plan

Project name
Project manager
Sponsor
Start date
Target end date
Budget$

1. Overview

Background / problem
Goal
Success measures

2. Scope

In scope

  • [Deliverable or activity]
  • [Deliverable or activity]
  • [Deliverable or activity]

Out of scope

  • [Excluded item]
  • [Excluded item]

3. Milestones

MilestoneTarget dateOwner

4. Tasks

#TaskOwnerStartDueDepends onStatus

5. Budget

ItemEstimated costActual cost
Total

6. Key risks

RiskLikelihoodImpactResponse

7. Stakeholders and communication

StakeholderWhat they needHow / how often

Preview of the template. Highlighted [brackets] show text to replace.

How to create a project plan

  1. Define the goal and success measures. What problem are you solving, and how will you know the project succeeded? Measures such as “launch by March 31 with fewer than 5 critical bugs” give the team a clear target.
  2. Set the scope. List what the project will deliver and what it will not. A clear out-of-scope list is your best defense against scope creep.
  3. Identify milestones. Milestones are key checkpoints, such as “design approved” or “beta launched”, that show progress and give stakeholders something to review.
  4. Break the work into tasks. For each task, record an owner, start and due dates, and any dependency on other tasks.
  5. Estimate the budget. List the main costs and track actual spend against estimates. The Excel version totals both columns.
  6. Plan for risks. Note what could go wrong, how likely and serious it is, and what you will do about it. Use the risk register for larger projects.
  7. Plan communication. Decide who needs updates, what they need to know and how often. A weekly status report works for most stakeholders.

Example: small business website relaunch

Milestone Target date Owner
Requirements and sitemap approved Feb 12 Ana
Design mockups approved Mar 5 Design agency
Content written and reviewed Mar 19 Marcus
Site built and tested Apr 9 Developer
Launch Apr 15 Ana

Tips for project success

  • Get sign-off early. Ask your sponsor to approve the goal, scope and budget before work starts.
  • Assign one owner per task. Shared ownership often means no ownership. Use a RACI chart to clarify roles.
  • Visualize the timeline. A Gantt chart makes dependencies and overlaps obvious.
  • Review weekly. Update task status and risks every week, and adjust the plan when reality changes.

Frequently asked questions

What should a project plan include?

At minimum, the project goal, scope, deliverables, milestones, tasks with owners and dates, budget, risks and how you will communicate progress. Larger projects may add a RACI chart, a detailed schedule and a change control process.

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

The project plan is the overall document describing what, why, who, how much and how. The schedule, often a Gantt chart, is one part of it that shows when tasks happen and how they depend on each other.

How detailed should tasks be?

Break work down until each task can be assigned to one person and completed in a few days to two weeks. Larger tasks are hard to estimate and track.

Related templates and guides