Free Simple Project Plan Template
A simple one-page project plan you can fill in today — download or copy in seconds.
Part of our free project plan templates.
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
- {{What this project will achieve, with a date — e.g. "Move the team into the new office by Aug 14 with zero lost work days"}}
- {{How you will know it worked — the one number or outcome that defines success}}
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
- {{What is included — the deliverable everyone is counting on}}
- {{A second thing this project covers}}
Out of scope
- {{What is NOT included — the assumption you need to head off}}
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 |
|---|---|---|---|
| {{First checkpoint — plan agreed}} | {{Owner}} | {{Target date}} | Not started |
| {{Midpoint — the main work is done}} | {{Owner}} | {{Target date}} | Not started |
| {{Done — project complete}} | {{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 — keep each one a single, ownable job}} | {{Owner}} | {{Start}} | {{Due}} | Not started |
| {{Next task}} | {{Owner}} | {{Start}} | {{Due}} | Not started |
| {{Final task before you are done}} | {{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 |
|---|---|---|
| Lead | {{Name}} | Runs the project and makes the call when something slips |
| {{Helper / role}} | {{Name}} | {{What they handle}} |
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 |
|---|---|---|---|---|
| {{The thing most likely to go wrong}} | {{High / Med / Low}} | {{High / Med / Low}} | {{What you will do about it}} | {{Owner}} |
| {{A second risk worth a plan B}} | {{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 |
|---|---|---|
| {{Main cost}} | {{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 12-person team relocating to a new office — small, fast, and run by one coordinator without project software.
1.Project Overview
| Project name | Office move — Suite 210 to Riverside floor 4 |
|---|---|
| Sponsor | Helen Cho, Operations Director |
| Project manager | Jordan Bell |
| Start date | July 27, 2026 |
| Target end date | August 14, 2026 |
| Status | On track |
2.Objectives & Success Criteria
- Move all 12 staff and equipment into the Riverside office over the weekend of Aug 8–9 so Monday Aug 10 is a normal work day.
- Have internet, phones, and printers tested and working before anyone arrives on Monday.
3.Scope
In scope
- Packing, moving, and unpacking desks, IT equipment, and the supply room.
- Internet, network, and phone setup at the new office, tested before move-in.
Out of scope
- New furniture purchases — the team is reusing existing desks and chairs.
- Updating the business address on the website, invoices, and Google listing (handled separately by marketing).
4.Milestones & Timeline
| Milestone | Owner | Target date | Status |
|---|---|---|---|
| Lease signed & move date locked | Helen Cho | July 24, 2026 | Complete |
| Internet & network live at new office | Raj Patel | August 7, 2026 | On track |
| Move complete & desks set up | Jordan Bell | August 9, 2026 | Not started |
| Everyone working normally | Jordan Bell | August 10, 2026 | Not started |
5.Tasks & Work Breakdown
| Task | Owner | Start | Due | Status |
|---|---|---|---|---|
| Book the moving company & confirm the weekend slot | Jordan Bell | July 27 | July 31 | Complete |
| Order broadband & schedule the install | Raj Patel | July 27 | August 7 | In progress |
| Hand out boxes & labels; everyone packs their own desk | Jordan Bell | August 3 | August 7 | Not started |
| Move day — supervise load-out and load-in | Jordan Bell | August 8 | August 9 | Not started |
| Test internet, phones & printers before Monday | Raj Patel | August 9 | August 9 | Not started |
6.Roles & Responsibilities
| Role | Name | Responsibility |
|---|---|---|
| Lead | Jordan Bell | Coordinates the move, the movers, and the schedule |
| IT | Raj Patel | Sets up and tests internet, network, phones, and printers |
7.Risks & Mitigation
| Risk | Impact | Likelihood | Mitigation | Owner |
|---|---|---|---|---|
| Broadband install is delayed and the office has no internet Monday | High | Med | Book the install two weeks early; keep a 4G hotspot as backup for day one | Raj Patel |
| Movers run over and desks are not ready Monday morning | Med | Med | Book the move for Saturday, not Sunday, to leave a buffer day | Jordan Bell |
8.Budget
| Item | Estimate | Actual |
|---|---|---|
| Moving company (weekend rate) | $2,800 | |
| Broadband install & phone setup | $600 | |
| Boxes, labels & supplies | $250 | |
| Contingency | $400 |
9.Approval
How it works
- Preview the simple project plan — a short objectives, milestones, tasks and risks layout.
- Download Word/PDF, or copy the text to paste anywhere.
- Fill in your objective, a few dated milestones, the key tasks and owners, and you are done.
Frequently asked questions
What is a simple project plan?
A simple project plan is a stripped-down plan for a small, short project — one objective, a handful of milestones, the key tasks with owners and dates, and the one or two risks worth a backup plan. It keeps the structure of a full plan but cuts the rows so a small team can fill it in once and run with it. The worked example here is a 12-person office move.
Do I need project management software for a small project?
No. For a project a small team can finish in a few weeks, a one-page plan in a doc or sheet is usually clearer than setting up project software. This template gives you the objectives, milestones, tasks, roles and risks on a single page — enough to keep everyone aligned without the overhead of a tool.
How many tasks should a simple project plan have?
List only the tasks you would actually check off — for a small project that is often five to ten. Make each one a single, ownable job with a due date, and roll the rest up under a milestone. If your list runs to dozens of tasks, the project is probably big enough to need the full project plan template instead.
When should I use a full project plan instead?
Move up to the full project plan when the project runs longer than a few weeks, spans multiple teams, has a real budget to track, or carries enough risk that you need a proper risk table and sign-off. The simple plan is for small, fast, low-risk work where speed matters more than detail.