← Back to home

Project plan template

Updated on October 28, 2026

Many small projects fail not for lack of effort but because each person had a different idea of what was supposed to be delivered. This plan fits in one note and makes the goal, what is in and out of scope, milestones with dates and who owns each one clear.

Project: Bakery online shop

Goal: take cake orders through the website by December
Owner: Carla
Deadline: 2026-12-01

Scope

  • Catalog with 20 products and photos
  • Order form with a pickup date

Out of scope (for now)

  • Online payment
  • Home delivery

Milestones

  • Product photos and prices (Ana, by Nov 10)
  • Page copy (Ben, by Nov 17)
  • Site built and tested (Carla, by Nov 24)
  • Announcement to customers (Ana, by Dec 1)

Risks

  • Photos run late: use simple phone photos in the first version

How we know it worked

  • At least 10 orders through the site in December

How to use it

  1. Create the note with "Use this template" at the start of the project and write the goal in one sentence, with a result you can check.
  2. List the scope and, just as carefully, what is out of scope. That list is what keeps the project from growing forever.
  3. Break the work into four to eight milestones, each with an owner and a date. A milestone without an owner does not move.
  4. Share the link with the team and tick each milestone when it is done. Review the plan once a week.

Tips

  • For bigger projects, use subfolders: project/plan, project/meetings and project/reports. The folder panel shows them together.
  • Write each risk with its plan B next to it. A risk with no response only creates worry.
  • When a date changes, update the milestone and note why. Version history keeps what was there before.
  • Create calendar reminders for key dates (⋮ menu › Create reminder), with the plan’s link in the event.

A good goal

"Improve the website" is not a goal: nobody knows when it is done. "Take orders through the website by December" is: it has a result and a deadline. The last section of the template, "How we know it worked", completes it with a simple number. It also helps decide what goes into scope: if a task does not help reach that number, it can wait for the next phase.

When the project ends, run a short retrospective (there is a template for that) and keep the lessons in the same folder. The next plan starts better.

Read also