Project plan template, with one plan built from blank to finished
A project plan says how a project will get done: the goal, what is in and out of scope, who does each task, on which working days, in what order, for how much, and who hears what along the way. Below is a blank nine-part template, then one fictional eight-week brand and website project filled in part by part. Download the plan as Markdown or plain text, and the schedule as a blank CSV or the filled example CSV for Excel or Google Sheets.
A project proposal wins the work and a project charter authorizes it and names who may decide. The plan comes after both and turns that decision into owners, dates and order.
The blank project plan template
Copy this into Word, Google Docs or a spreadsheet and fill in the last column.
| Part | What it answers | Your plan |
|---|---|---|
| 1. Goal and success measure | What changes, measured how, by when? | |
| 2. Scope in and out | What will we do, and what will we not do? | |
| 3. Deliverables | What will exist at the end? | |
| 4. Work breakdown | Which tasks, who owns each, how many working days? | |
| 5. Schedule | Start and finish dates, dependencies, milestones | |
| 6. Budget | Cost lines, contingency, total | |
| 7. Risks | What could go wrong, who watches it, what we do | |
| 8. Communication plan | Who gets which update, how often, from whom | |
| 9. Change control | How a change is asked for and approved |
The example, part by part
Marlow Surveying is a fictional 15-person surveying firm. Kestrel Studio, also fictional, is a four-person agency: project lead, designer, writer and developer. The project runs eight weeks, Monday 1 March to Friday 23 April 2027, weekdays only, with no US public holiday.
1. Goal and success measure
New brand and a 10-page website live by Friday 23 April 2027. Measure: quote requests through the site rise from 4 a month (January and February average) to 10 a month by Friday 30 July 2027.
2. Scope in and out
- In: logo, colours and type; 12-page brand guidelines; 10-page site on a content management system (CMS); copy for all 10 pages; redirects for the 38 old URLs; one hour of editor training.
- Out: photography, printed stationery, vehicle livery, paid ads, search work after launch, moving the 2019 to 2022 news posts.
Contract wording for scope belongs in a statement of work.
3. Deliverables
Brief; logo files; brand guidelines; sitemap; 5 page templates; 10 pages of approved copy; redirect map; the live site; a handover note.
4 and 5. Work breakdown and schedule
Days are working days; each task starts the working day after its dependencies finish.
| # | Task | Owner | Days | Start | Finish | Depends on |
|---|---|---|---|---|---|---|
| 1 | Kickoff meeting with the client | Project lead | 1 | Mon 1 Mar | Mon 1 Mar | None |
| 2 | Interview 5 staff and 3 clients | Project lead | 3 | Tue 2 Mar | Thu 4 Mar | 1 |
| 3 | Audit current site, 38 pages | Writer | 3 | Tue 2 Mar | Thu 4 Mar | 1 |
| 4 | Brief written and approved | Project lead | 2 | Fri 5 Mar | Mon 8 Mar | 2 and 3 |
| 5 | Three logo routes | Designer | 5 | Tue 9 Mar | Mon 15 Mar | 4 |
| 6 | Sitemap and page list, 10 pages | Writer | 2 | Tue 9 Mar | Wed 10 Mar | 4 |
| 7 | Write copy for 10 pages | Writer | 8 | Thu 11 Mar | Mon 22 Mar | 6 |
| 8 | Set up hosting, CMS and staging | Developer | 2 | Thu 11 Mar | Fri 12 Mar | 6 |
| 9 | Client chooses a logo route | Client | 2 | Tue 16 Mar | Wed 17 Mar | 5 |
| 10 | Wireframes for 5 page templates | Designer | 3 | Tue 16 Mar | Thu 18 Mar | 5 and 6 |
| 11 | Refine logo, colours and type | Designer | 3 | Fri 19 Mar | Tue 23 Mar | 9 and 10 |
| 12 | Client reviews and approves copy | Client | 3 | Tue 23 Mar | Thu 25 Mar | 7 |
| 13 | Redirect map for 38 old URLs | Writer | 2 | Tue 23 Mar | Wed 24 Mar | 3 and 7 |
| 14 | Visual design of 5 templates | Designer | 4 | Wed 24 Mar | Mon 29 Mar | 11 |
| 15 | Brand guidelines, 12 pages | Designer | 3 | Tue 30 Mar | Thu 1 Apr | 14 |
| 16 | Client design review, one round | Client | 2 | Tue 30 Mar | Wed 31 Mar | 14 |
| 17 | Design changes from the review | Designer | 2 | Fri 2 Apr | Mon 5 Apr | 15 and 16 |
| 18 | Build 5 templates on staging | Developer | 5 | Tue 6 Apr | Mon 12 Apr | 8 and 17 |
| 19 | Load copy and images, 10 pages | Developer | 2 | Tue 13 Apr | Wed 14 Apr | 12 and 18 |
| 20 | Test on phones and browsers, fix | Developer | 3 | Thu 15 Apr | Mon 19 Apr | 19 |
| 21 | Client signs off staging | Client | 1 | Tue 20 Apr | Tue 20 Apr | 20 |
| 22 | Launch site and redirects | Developer | 1 | Wed 21 Apr | Wed 21 Apr | 13 and 21 |
| 23 | One-hour editor training and handover | Project lead | 1 | Thu 22 Apr | Thu 22 Apr | 22 |
"Client" means the office manager, who sends one combined response. Task 17 waits for task 15 only because one designer does both: a person can be a dependency. Friday 23 April is slack.
| Milestone | Date | Set by task |
|---|---|---|
| Brief approved | Monday 8 March | 4 |
| Logo route chosen | Wednesday 17 March | 9 |
| Copy approved | Thursday 25 March | 12 |
| Design approved | Wednesday 31 March | 16 |
| Staging signed off | Tuesday 20 April | 21 |
| Launch | Wednesday 21 April | 22 |
| Handover | Thursday 22 April | 23 |
6. Budget
Fees are working days times day rate; the project lead's 12 days are 7 task days plus 5 for calls and reviews. Tracking costs line by line is covered in the project budget template.
| Line | Calculation | Amount |
|---|---|---|
| Project lead | 12 days at $900 | $10,800 |
| Designer | 20 days at $750 | $15,000 |
| Writer | 15 days at $650 | $9,750 |
| Developer | 13 days at $800 | $10,400 |
| Font licence, stock photos, a year of hosting | $400 + $350 + $300 | $1,050 |
| Subtotal | $47,000 | |
| Contingency, 10%, released by the managing director | $4,700 | |
| Total | $51,700 |
7. Risks
| Risk | Likelihood | Owner | Response |
|---|---|---|---|
| Client reviews overrun | Medium | Office manager | All four review windows booked at kickoff |
| No logo route chosen in task 9 | Medium | Project lead | One extra 3-day round ($2,250) from contingency |
| Old site has more than 38 URLs | Low | Writer | Full crawl in task 3; extras priced before work starts |
| Designer away for a week | Low | Project lead | Developer builds from wireframes; use contingency |
8. Communication plan
| Who | What they get | How often | From whom | How |
|---|---|---|---|---|
| Managing director (sponsor) | Done, next, decisions needed, budget used | Fridays | Project lead | Email, five lines |
| Office manager | This week's tasks and what is waiting on the firm | Mondays, 30 minutes | Project lead | Video call |
| Partners reviewing work | Review dates and what to check | 2 working days before each review | Office manager | |
| All Marlow staff | What is changing and when | Kickoff and launch | Managing director | Staff meeting |
Who approves and who is informed belongs in a RACI chart; task 1 can follow a kickoff meeting agenda.
9. Change control
Any change to scope, to a milestone date, or over $500 goes to the project lead in writing. The lead prices it in days and dollars within 2 working days; the managing director approves or declines. Approved changes enter the plan with their approval date.
A simple one-page project plan for projects under a month
A short project needs goal, scope, dated steps and one risk. Fictional example: a 9-person cleaning company updates its prices, Monday 10 May to Friday 28 May 2027.
| Line | Example |
|---|---|
| Goal | New prices published by Friday 28 May, customers told 30 days before they apply |
| In and out | In: price sheet, pricing page, customer email. Out: new services, website redesign |
| Steps | Collect last year's prices, office manager, Mon 10 to Tue 11 May; draft prices, owner, Wed 12 to Fri 14 May; page copy, writer, Mon 17 to Wed 19 May; owner approves, Thu 20 May; page updated, web freelancer, Fri 21 to Mon 24 May; customer email, office manager, Tue 25 May |
| Budget | $1,200 for the two freelancers |
| Biggest risk | Owner approval slips; Wednesday 26 to Friday 28 May are slack |
| Updates | Owner and office manager, 10 minutes each Monday |
How to build the schedule in Excel or Google Sheets
- Set up the columns: ID, Phase, Task, Owner, Days, Depends on, Start, Finish, Baseline start, Baseline finish, Slip (A to K). The CSVs above use this order. Mistake: no Days column, so dates are typed by hand and drift.
- Type only the first start date. Finish in H2 is
=WORKDAY(G2,E2-1). WORKDAY returns the date a given number of working days after the start, skipping Saturdays and Sundays (Google Sheets, Excel), so a 1-day task finishes on its start day. Mistake:=G2+E2, which counts weekends. - Chain the starts. A task that depends on row 5 starts
=WORKDAY(H5,1); on rows 3 and 5,=WORKDAY(MAX(H3,H5),1). Mistake: typing start dates, so one late task moves nothing after it. - Add holidays. List them on a tab named Holidays and pass that range as WORKDAY's third argument:
=WORKDAY(G2,E2-1,Holidays!$A$2:$A$12). If Excel shows a number such as 46447, format the cell as a date. - Draw a text Gantt. Put each week's Monday across row 1 from column L (
=L1+7in M1), select the grid below it, and add a formula rule: in Google Sheets, Format, Conditional formatting, "Custom formula is" (Google's steps); in Excel, Home, Conditional Formatting, New Rule, "Use a formula to determine which cells to format" (Microsoft's steps). The rule=AND(L$1<=$H2,L$1+4>=$G2)colours each week a task touches. Mistake: bars drawn by hand.
How to baseline the plan and track against it
When the sponsor approves the plan, copy Start and Finish and paste values only into the two Baseline columns, then never edit them. Each week, =H2-J2 in a Slip column (K) shows calendar days late against the baseline, and any milestone that slips goes in the sponsor's Friday email. Re-baseline only for an approved change, keeping the old baseline on a second tab. Weekly status across several live projects is the job of a project tracker template.
Five ways project plans go wrong
- Calendar days instead of working days. An 8-day task counted in calendar days ends days too early on paper.
- The client's work is missing. Reviews are tasks with owners and days, like tasks 9, 12, 16 and 21.
- People are not dependencies. One designer cannot do tasks 15 and 17 at once.
- No baseline. Dates get quietly re-typed and nobody knows how late the project is.
- Changes without a rule. "Can we add a careers page?" becomes two unpaid days. Part 9 stops it.
Where Flori fits
Flori is a CRM with project management for teams of 1 to 20. The work breakdown becomes tasks with owners, due dates, subtasks and dependencies, a task waiting on the client stays visibly blocked, and a time log on tasks records the time really spent. On every plan, a project's tasks can also be shown as a Gantt chart: bars by week, month or quarter, with dependency lines, milestones and the critical path. Dragging a bar shows which dependent tasks would move and by how much, and nothing changes until you confirm. The free plan covers 3 active projects; for more at no cost, a spreadsheet does the job. Work that flows without fixed dates suits a board like these kanban board examples.
FAQ
What should a project plan include? A measurable goal, scope in and out, deliverables, tasks with owners and estimates, a schedule with dependencies and milestones, a budget, risks, a communication plan and a change rule. A small team fits all nine on two pages.
Is a project plan the same as a project management plan? In everyday use, yes. In formal methods it is a larger document that also says how scope, cost, quality and risk will be managed; small teams rarely need more than these nine parts.
Do agile projects need a project plan? Yes, a lighter one. Keep the goal, scope, budget, milestones and communication plan, and plan tasks a sprint or a week at a time.
Can I use this template in Word or PowerPoint? Yes. Paste the plain-text file into Word, or a table from this page into a slide.
Start your workspace