Project plan template

• A new project has a goal and a deadline but no agreed list of work yet.
• Several people or teams share the work and need one place that says who does what by when.
• A sponsor or client wants to see the route to the deadline, not just the deadline.
• An existing project keeps slipping and nobody can say which task is late.

Fill in the blanks and replace the example rows with your own. Everything below is what the copy and download buttons give you.

1. 01

   Write the summary first

   Name the sponsor, the lead, the objective and how success will be measured. If you cannot write the objective in one sentence, the project is not ready to plan.

2. 02

   Draw the scope line

   List what is in and, just as important, what is out. Most schedule overruns start as scope nobody wrote down.

3. 03

   Break the work into phases and tasks

   Work from the deliverables backwards. Each task should have a clear finish and be small enough that a missed date is noticed within days, not weeks.

4. 04

   Give every task one accountable owner and a due date

   A task owned by "the team" is owned by nobody. Put a person's name on each row, even if several people help.

5. 05

   Record dependencies

   Note which tasks cannot start until another finishes. Those chains decide the real end date, whatever the deadline says.

6. 06

   Set milestones and the update rhythm

   Pick the few checkpoints the sponsor cares about and agree how often status goes out. Then update the Status column at least that often.

A spreadsheet plan goes stale the moment someone finishes a task without updating it. In Kavanah the plan is the board people already work from, so status is current because the work itself moves it.

What should a project plan include?

At minimum: the objective and how success is measured, the scope (including what is out of scope), the tasks with an owner and a due date on each, the dependencies between tasks, the milestones, and how progress will be reported. Budget and risk sections are worth adding when the project carries either.

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

A charter authorizes the project: it states why it exists, the objective, the sponsor and the boundaries, and it is usually signed off once. A project plan is the working schedule that follows from the charter: tasks, owners, dates and dependencies, updated throughout the project.

How detailed should the task list be?

Detailed enough that each task has one owner, a clear finish and a duration of a few days. If a task takes longer than a week or two, split it; if you are listing ten-minute steps, group them into a task with a checklist.

Can I use this project plan template in Excel or Google Sheets?

Yes. Download the CSV and open it in Excel, Google Sheets or Numbers; the columns stay intact. You can also copy the whole template as Markdown and paste it into a document or wiki page.

How often should a project plan be updated?

At least as often as you report status, and whenever a task finishes, slips or changes owner. A weekly review is a sensible default for most projects; fast projects with daily standups can update daily.

Is a project plan the same as a Gantt chart?

No. A Gantt chart is one way to draw the schedule part of a plan, as bars on a timeline. The plan also carries the objective, scope, owners and communication rules that a chart does not show.