Free Project Plan Template
Preview the full project plan template — download Word/PDF or copy the text in one click.
Your download has started.
Didn’t start? Retry the Word file or get the PDF.
Industry template packs — coming soon.
1.Project Overview
| Project name | {{Project name}} |
|---|---|
| Sponsor | {{Sponsor / decision-maker}} |
| Project manager | {{Project manager}} |
| Start date | {{Start date}} |
| Target end date | {{Target end date}} |
| Status | {{Not started / On track / At risk}} |
Keep this block on page one so anyone can see the project, its owner, and where it stands at a glance. Name one accountable project manager and one sponsor who can unblock decisions.
2.Objectives & Success Criteria
- {{Primary objective — a measurable outcome with a date, e.g. "Launch the new website by Sept 30 with a sub-3s load time"}}
- {{Business reason this project exists — the problem it solves or the result it delivers}}
- {{Success metric #1 — how you will measure that the objective was met}}
- {{Success metric #2 — a second number that proves the result}}
Write objectives you can measure — “launch the new checkout by Q3 with under 1% error rate”, not “improve checkout”. If you cannot tell whether it is done, rewrite it.
3.Scope
In scope
- {{Work this project will deliver — be specific about deliverables and audiences}}
- {{Second deliverable or workstream that is clearly included}}
- {{Systems, pages, or teams this project will touch}}
Out of scope
- {{Work people will assume is included but is not — name it to prevent scope creep}}
- {{A phase or feature deliberately deferred to a later project}}
- {{Ongoing/operational work that continues outside this project}}
Naming what is out of scope is what actually prevents scope creep. Be explicit about the work people will assume is included but is not.
4.Milestones & Timeline
| Milestone | Owner | Target date | Status |
|---|---|---|---|
| {{Kickoff / plan approved}} | {{Project manager}} | {{Target date}} | Not started |
| {{Phase 1 complete — first reviewable deliverable}} | {{Owner}} | {{Target date}} | Not started |
| {{Build / production complete}} | {{Owner}} | {{Target date}} | Not started |
| {{Go-live / launch}} | {{Owner}} | {{Target date}} | Not started |
Milestones are checkpoints, not tasks — a handful of dates that prove the project is moving. Each should be a clear “done / not done”, with one owner.
5.Tasks & Work Breakdown
| Task | Owner | Start | Due | Status |
|---|---|---|---|---|
| {{Task — small enough to finish in a week or less}} | {{Owner}} | {{Start}} | {{Due}} | Not started |
| {{Next task in the sequence}} | {{Owner}} | {{Start}} | {{Due}} | Not started |
| {{Dependent task — starts after the one above is done}} | {{Owner}} | {{Start}} | {{Due}} | Not started |
| {{Review / sign-off task before the milestone}} | {{Owner}} | {{Start}} | {{Due}} | Not started |
Break the work into tasks small enough to track in a week or less. Give each an owner and a due date; a task with no owner will not happen.
6.Roles & Responsibilities
| Role | Name | Responsibility |
|---|---|---|
| Project manager | {{Name}} | Owns the plan, schedule, and status reporting |
| Sponsor | {{Name}} | Approves scope and budget; removes blockers |
| {{Delivery lead / role}} | {{Name}} | {{The deliverable this person is accountable for}} |
| {{Reviewer / stakeholder}} | {{Name}} | Reviews and signs off before launch |
Assign responsibilities to roles so the plan survives a team change. Be clear who decides, who does the work, and who needs to be kept informed.
7.Risks & Mitigation
| Risk | Impact | Likelihood | Mitigation | Owner |
|---|---|---|---|---|
| {{Risk that would actually derail the project}} | {{High / Med / Low}} | {{High / Med / Low}} | {{The action you will take to prevent or contain it}} | {{Owner}} |
| {{A dependency or resource risk}} | {{High / Med / Low}} | {{High / Med / Low}} | {{Mitigation}} | {{Owner}} |
| {{A schedule or scope risk}} | {{High / Med / Low}} | {{High / Med / Low}} | {{Mitigation}} | {{Owner}} |
List the few risks that would actually derail the project, rate impact and likelihood (High/Med/Low), and name the action and the owner. Review this table at every status check.
8.Budget
| Item | Estimate | Actual |
|---|---|---|
| {{Labor — internal or contractor effort}} | {{Estimate}} | {{Actual}} |
| {{Tools, licenses, or services}} | {{Estimate}} | {{Actual}} |
| Contingency | {{Estimate}} | {{Actual}} |
Estimate the main cost lines and add a contingency for the unknowns. If your project has no budget, keep the section and write “N/A” — reviewers expect to see it.
9.Approval
Both sign-offs confirm the plan, scope, and budget are agreed before work starts.
A worked example for a marketing-site redesign — from kickoff to launch — owned by a small in-house team plus an external developer.
1.Project Overview
| Project name | Corporate website redesign (acme.com) |
|---|---|
| Sponsor | Dana Whitfield, VP Marketing |
| Project manager | Priya Nair |
| Start date | July 6, 2026 |
| Target end date | October 16, 2026 |
| Status | On track |
2.Objectives & Success Criteria
- Relaunch acme.com on the new design system by October 16, 2026 with all 40 pages migrated.
- Cut mobile load time from 5.8s to under 3s (Largest Contentful Paint) to reduce bounce.
- Increase demo-request conversion from 1.4% to 2.5% within 60 days of launch.
- Move all content editing to the new CMS so marketing can publish without a developer.
3.Scope
In scope
- Redesign and rebuild the 40 core marketing pages (home, product, pricing, solutions, blog index).
- New design system and component library, built mobile-first.
- Content migration into the new CMS and a 301 redirect map for changed URLs.
- Analytics and conversion tracking re-implemented on the new site.
Out of scope
- The customer support knowledge base (stays on its current platform — separate Q4 project).
- The logged-in customer dashboard / web app (different team, different codebase).
- A net-new brand or logo refresh — this project uses the existing 2025 brand.
4.Milestones & Timeline
| Milestone | Owner | Target date | Status |
|---|---|---|---|
| Kickoff & plan approved | Priya Nair | July 6, 2026 | Complete |
| Design system & key page mockups approved | Marcus Lee | August 7, 2026 | On track |
| Content migrated & staging site built | Sara Olsen | September 18, 2026 | Not started |
| QA, redirects & accessibility sign-off | Priya Nair | October 9, 2026 | Not started |
| Go-live on production | Tomás Reyes | October 16, 2026 | Not started |
5.Tasks & Work Breakdown
| Task | Owner | Start | Due | Status |
|---|---|---|---|---|
| Audit current site & lock the page inventory | Sara Olsen | July 6 | July 17 | Complete |
| Wireframe home, product & pricing pages | Marcus Lee | July 20 | July 31 | In progress |
| Build the component library in the design system | Marcus Lee | August 3 | August 21 | Not started |
| Develop & template the 40 pages in the CMS | Tomás Reyes | August 24 | September 18 | Not started |
| Migrate copy & images; build the 301 redirect map | Sara Olsen | September 7 | September 25 | Not started |
| Cross-browser QA, accessibility & performance pass | Priya Nair | September 28 | October 9 | Not started |
| Cutover to production & monitor for 48 hours | Tomás Reyes | October 16 | October 18 | Not started |
6.Roles & Responsibilities
| Role | Name | Responsibility |
|---|---|---|
| Project manager | Priya Nair | Owns the plan, schedule, weekly status, and launch decision |
| Sponsor | Dana Whitfield | Approves scope and budget; unblocks legal and brand sign-off |
| Design lead | Marcus Lee | Owns the design system and page mockups |
| Developer (external) | Tomás Reyes | Builds the CMS templates and runs the production cutover |
| Content lead | Sara Olsen | Owns the page inventory, copy migration, and redirect map |
7.Risks & Mitigation
| Risk | Impact | Likelihood | Mitigation | Owner |
|---|---|---|---|---|
| External developer is part-time and may slip the build | High | Med | Lock his availability in writing; review build progress every Friday; keep a backup contractor on standby | Priya Nair |
| Broken redirects after launch tank organic search traffic | High | Med | Build the 301 map from a full crawl; test every old URL on staging before cutover | Sara Olsen |
| Legal/brand sign-off on new copy arrives late | Med | High | Send copy for review in batches starting week 6, not all at the end | Dana Whitfield |
| Performance target missed on image-heavy pages | Med | Med | Set an image budget; lazy-load and serve modern formats; measure LCP on every staging build | Marcus Lee |
8.Budget
| Item | Estimate | Actual |
|---|---|---|
| External developer (10 weeks, part-time) | $32,000 | |
| Design system tooling & stock imagery | $3,500 | |
| CMS plan upgrade (annual) | $2,400 | |
| Contingency (10%) | $3,800 |
9.Approval
Project planning templates
How it works
- Preview the full project plan — objectives, scope, milestones, tasks, roles, risks and budget.
- Download Word/PDF, or copy the text to paste into Google Docs or a sheet.
- Replace the placeholders with your own objectives, dates and owners, then share it for sign-off.
Frequently asked questions
What is a project plan?
A project plan is the single document that says what a project will deliver, by when, and who is responsible. At a minimum it sets the objectives and success criteria, the scope (what is in and out), the milestones and tasks with owners and dates, the risks, and the budget. This template includes all of those sections so you can fill in the blanks.
What should a project plan include?
A good one-page plan covers an overview (name, sponsor, manager, dates, status), measurable objectives, an explicit in-scope and out-of-scope list, a milestone table, a task breakdown with owners and due dates, roles and responsibilities, a risk table with mitigations, and a budget. This template lays out those nine sections in order.
How do I write a project plan step by step?
Start with the objective and how you will measure it, then write down what is in and out of scope. List the handful of milestones that prove the project is moving, break each into tasks with an owner and a due date, name the risks and what you will do about them, and add a budget. Get the sponsor to approve it before work starts.
What is the difference between a project plan and a project charter?
A charter comes first and is short: it authorizes the project and sets the why, who and what (business case, objectives, scope, roles, high-level risks) before any detailed work. The project plan is the fuller working document with the milestone schedule and task breakdown you run the project from. Many teams write the charter, get sign-off, then expand it into the plan.