A useful project plan turns a goal into work people can actually deliver. It records what needs to happen, who owns each task, when work is due, which tasks depend on others, and how the team will know the project is on track.
This guide includes project plan templates you can copy directly into Excel, Google Sheets, Notion, or another spreadsheet. It also includes a filled example and a simple project schedule. Replace the sample tasks and dates with details from your own project.
Project plan template: copy and paste
Use the table below for a straightforward project. To copy it into a spreadsheet, select the rows and columns in the table and paste them into cell A1. If the columns do not separate automatically, use your spreadsheet’s split-text or paste-special options.
| ID | Phase | Task or deliverable | Owner | Start date | Due date | Depends on | Priority | Status | Milestone? |
|---|---|---|---|---|---|---|---|---|---|
| 1.1 | Initiation | Confirm project goal and success measures | Project sponsor | Enter date | Enter date | None | High | Not started | Yes |
| 1.2 | Initiation | Identify stakeholders and decision makers | Project manager | Enter date | Enter date | 1.1 | Medium | Not started | No |
| 2.1 | Planning | Confirm scope and exclusions | Project manager | Enter date | Enter date | 1.2 | High | Not started | Yes |
| 2.2 | Planning | Break the work into tasks and estimate effort | Team lead | Enter date | Enter date | 2.1 | High | Not started | No |
| 2.3 | Planning | Approve schedule, budget, and risks | Project sponsor | Enter date | Enter date | 2.2 | High | Not started | Yes |
| 3.1 | Execution | Complete the first deliverable | Delivery owner | Enter date | Enter date | 2.3 | High | Not started | No |
| 3.2 | Execution | Review deliverable with stakeholders | Project manager | Enter date | Enter date | 3.1 | Medium | Not started | No |
| 4.1 | Launch | Test, approve, and release deliverables | QA or project lead | Enter date | Enter date | 3.2 | High | Not started | Yes |
| 4.2 | Closure | Hand over ownership and record lessons | Project manager | Enter date | Enter date | 4.1 | Low | Not started | Yes |
How to use it: Give each task one accountable owner, enter realistic start and due dates, and use the dependency column to show what must finish first. Keep statuses consistent, for example Not started, In progress, Blocked, and Done. A milestone is a significant checkpoint or approval, not a task that takes several days.
What is a project plan template?
A project plan template is a reusable structure for defining a project’s goals, scope, tasks, owners, timeline, milestones, resources, and risks. It helps teams plan consistently without starting from a blank page each time.
A template is a starting point, not a schedule that can be used unchanged for every project. A small internal task may need only a one-page plan. A software implementation or cross-functional launch may need a detailed schedule, budget, risk register, communication plan, and change-control process.
What should a project plan include?
- Project goal: The outcome the project is meant to achieve.
- Success measures: How you will determine whether the result meets expectations.
- Scope and exclusions: What the project includes and what it does not include.
- Deliverables: The outputs that must be produced and accepted.
- Tasks and owners: The work required and the person accountable for each item.
- Dates and milestones: Planned start dates, deadlines, and major checkpoints.
- Dependencies: Tasks or decisions that must happen before other work can proceed.
- Resources and budget: People, tools, suppliers, and expected costs.
- Risks and assumptions: What might disrupt delivery and what the plan assumes to be true.
- Communication and approvals: Who needs updates, how often, and who can approve changes.
Not every project needs a separate document for each item. Keep related details in one place when the project is small, and split them into dedicated registers when the team needs more control.
Example project plan: launching a company website
The example below uses a fictional website launch. The dates and owners are illustrative. Adjust the schedule to your team size, review process, content volume, and technical needs.
| Phase | Task | Owner | Example duration | Dependency | Completion check |
|---|---|---|---|---|---|
| Discovery | Agree goals, audience, and success measures | Project sponsor | 2 days | None | Goals approved |
| Planning | Confirm sitemap and page requirements | Product owner | 3 days | Goals approved | Sitemap signed off |
| Content | Draft and review priority page content | Content lead | 5 days | Sitemap signed off | Content approved |
| Design | Create and approve page designs | Designer | 5 days | Page requirements | Design approval recorded |
| Development | Build pages and configure forms | Developer | 8 days | Design approval | Pages available for testing |
| QA | Test mobile layouts, links, forms, and accessibility | QA owner | 3 days | Build complete | Critical defects resolved |
| Launch | Approve release and publish website | Project lead | 1 day | QA approval | Launch verified |
| Handover | Document ownership and review analytics | Marketing lead | 2 days | Launch | Owners and next review agreed |
Some tasks can run in parallel. For example, content planning and early technical setup may overlap once the key requirements are clear. Do not shorten the schedule by assuming that every task can run at the same time. Confirm dependencies and make room for stakeholder feedback.
Choose the right project plan format
| Format | Best for | Main trade-off |
|---|---|---|
| One-page plan | Small projects and leadership updates | Limited detail for dependencies and risk tracking |
| Excel or Google Sheets | Task lists, owners, dates, budgets, and simple tracking | Manual updates can become difficult as complexity grows |
| Gantt chart | Projects with linked tasks and important deadlines | Needs careful maintenance when dates or dependencies change |
| Agile sprint plan | Product or software teams delivering work in short iterations | Does not replace a broader roadmap or stakeholder plan |
| Project management software | Teams that need shared updates, automation, reporting, or cross-project visibility | Setup, training, and subscription costs may be involved |
Microsoft provides project planning and to-do list templates for Excel, including options for timelines and task tracking. Choose a format your team will maintain, rather than the most complicated template available.
If you are comparing software for a growing team, explore our guide to free project management software. Teams that need to map ideas visually may also find our guide to online whiteboards useful.
How to create a project plan in seven steps
- Define the outcome. Write a clear goal and two or three measurable success criteria. Avoid vague goals such as “improve the website.” Specify the result you need.
- Set the scope. List the deliverables, boundaries, constraints, and exclusions. This gives the team a reference when new requests appear.
- Break the work down. Divide deliverables into tasks that can be estimated and assigned. If a task is too large to track, split it into smaller pieces.
- Assign owners and resources. Give every task one accountable owner. Check availability, specialist skills, suppliers, and budget before committing to dates.
- Build the schedule. Estimate effort, identify dependencies, set milestones, and add time for review or uncertainty. A deadline without an owner and a realistic sequence is only a wish.
- Review risks and approvals. Record the most likely problems, their potential impact, and the action you will take if they occur. Identify who can approve scope, budget, and schedule changes.
- Share and maintain the plan. Agree on a review cadence. Update task status, blockers, decisions, and forecast dates. Record major changes so stakeholders can see why the plan moved.
Project plan template: blank fields to copy
For a short project, copy this checklist into a document and fill in the answers. It works as a one-page project brief before you build the task schedule.
PROJECT NAME:
PROJECT SPONSOR:
PROJECT MANAGER:
PLANNED START:
TARGET FINISH:
GOAL:
SUCCESS MEASURES:
SCOPE INCLUDED:
OUT OF SCOPE:
KEY DELIVERABLES:
MILESTONES:
1.
2.
3.
TASKS AND OWNERS:
Task | Owner | Start date | Due date | Dependency | Status
| | | | |
| | | | |
| | | | |
BUDGET / RESOURCES:
KEY RISKS:
ASSUMPTIONS:
APPROVALS REQUIRED:
UPDATE CADENCE:
NEXT REVIEW DATE:
Download an Excel project plan template and try it now
Want to start in Excel instead of building a sheet from scratch? Download the free Excel project plan templates and try them now from Microsoft. Choose a task list or planning layout, then adapt it using the examples and guidance in this article.
Prefer to copy and paste? Use the project plan table above or the blank project brief below. Replace the sample tasks, owners, dates, and dependencies with your own project details.
Common project planning mistakes
- Starting with tasks before agreeing on the goal. The team may deliver work that does not solve the original problem.
- Using vague task names. “Work on launch” is difficult to track. “Approve launch email copy” has a clear completion point.
- Giving a task several owners. Several people can contribute, but one person should be accountable for moving it forward.
- Ignoring dependencies. A design review cannot finish before a design exists. Model the sequence before setting final dates.
- Leaving no room for review. Stakeholder decisions, testing, and revisions take time. Include them in the schedule.
- Failing to update the plan. An old plan can mislead people more than no plan. Review it on a predictable schedule.
- Tracking too much detail. Fields that nobody uses create overhead. Start with what the team needs to make decisions.
When should you move from a spreadsheet to project management software?
A spreadsheet can work well when the project is small, the task list is short, and one person can maintain updates. Consider a dedicated tool when several teams depend on each other, dates change frequently, approvals are hard to track, or leaders need progress reporting across multiple projects.
Compare tools based on the workflow you need: task ownership, timeline views, recurring work, dependencies, reporting, integrations, permissions, and the effort required to keep data current. A more feature-rich tool is not automatically a better fit if your team only needs a shared task list.
Frequently asked questions
What is the difference between a project plan and a project schedule?
A project plan covers the overall approach, scope, responsibilities, resources, risks, communication, and control process. A project schedule focuses on tasks, durations, dependencies, dates, and milestones. The schedule is often one part of the broader plan.
Can I use this project plan template in Excel or Google Sheets?
Yes. Copy the table into a spreadsheet and replace the sample rows. You can add date validation, filters, formulas, or a Gantt view if your project needs them.
How detailed should a project plan be?
Use enough detail to assign work, coordinate dependencies, identify risk, and measure progress. A small internal project may need only a one-page brief and task list. A complex implementation may require separate schedules, budget tracking, risk logs, and formal approvals.
Who should own the project plan?
A project manager or designated project lead usually maintains the plan. Task owners are responsible for updating their work, while the sponsor or steering group approves major changes when required.
How often should I update a project plan?
Update task status when meaningful changes happen and review the full plan at a cadence that fits the project. A fast-moving project may need daily updates; a small project may work with a weekly review. Escalate blockers as soon as they threaten a milestone.
Does a project plan guarantee on-time delivery?
No. A plan improves shared understanding and makes risks visible, but delivery still depends on estimates, resources, decisions, external dependencies, and changing requirements. Treat the plan as a working forecast, not a guarantee.
Final takeaway
A project plan template is useful when it makes the next action clear. Start with the goal, define the deliverables, assign owners, map dependencies, and set realistic dates. Then keep the plan current as the work changes. Use the simplest format that gives your team enough visibility to deliver and make decisions.
Sources and further reading
- Microsoft Excel: Project planning and to-do list templates
- Microsoft Support: Create a project in Project
- Smartsheet: Project management plan templates
Template note: The sample project and task schedule are illustrative. Adjust ownership, dates, budgets, and approval requirements to your project rather than treating the example as a commitment.
