planomatti

planomatti / Project plan

Guide · worked example · one-page outline

How to create a project plan

A project plan answers six questions: why (goals), what (scope), how (tasks), who (responsibilities), when (timeline) and what could go wrong (risks). Write the parts in that order, get the plan approved, then keep it up to date. This guide walks through each part with a website relaunch as the example. If you only need the schedule, see how to create a project timeline.

  • Free, no subscription
  • Sign up with email
  • Hosted in Switzerland
Website relaunch · project plan1 page
  1. Goals: why
  2. Scope: what is in and out
  3. Tasks: how
  4. Responsibilities: who
  5. Timeline: when
  6. Risks: what could go wrong
The six parts, in the order you write them.

How to write a project plan in 6 steps

  1. 01Define the goals

    Write two or three goals that can be checked at the end: what changes, by how much, by when.

  2. 02Set the scope

    List the deliverables and, just as important, what is not included. This is what you point to when new wishes appear.

  3. 03Break down the work

    Split each deliverable into phases and tasks small enough to estimate, usually 1 to 10 working days.

  4. 04Assign responsibilities

    One owner per task. Note who approves results and who only needs to be informed.

  5. 05Build the timeline

    Order the tasks, estimate durations, derive dates, add milestones and buffer.

  6. 06List the risks

    What could delay or break the project? Rate likelihood and impact, and agree on a response and an owner.

Example: project plan for a website relaunch

A small company replaces its website. Team: Lea (project lead), Tim (design), Sara (development), Marco (content). Client: the managing director, who approves the concept and the launch.

1. Goals

  • New website live by Friday 19 February 2027.
  • Contact requests via the website up 30 percent within three months of launch.
  • All pages work on mobile and pass a basic accessibility check.

2. Scope

In: 12 pages, new design, contact form, migration of existing texts, basic search engine setup.

Out: online shop, new logo, translations, paid advertising. These go into a later project.

3. Work breakdown

  • Discovery: kick-off, analysis of the current site
  • Concept: sitemap, wireframes, approval
  • Build: design, copy and images, development, content entry
  • Launch: testing and fixes, buffer, go-live

Each phase ends with a result someone can check, for example “wireframes approved”.

4. Responsibilities

Who does, approves and is informed
DeliverableResponsibleApprovesInformed
Goals and scopeLeaManaging directorTeam
Wireframes and designTimManaging directorSara, Marco
Copy and imagesMarcoLeaTim
Development and testingSaraLeaTeam
Go-liveLeaManaging directorAll staff

5. Timeline (summary)

Phases of the website relaunch, 2027
PhaseDatesEnds with
DiscoveryMon 11 Jan – Wed 13 JanAnalysis done
ConceptThu 14 Jan – Tue 19 JanMilestone: concept approved
BuildWed 20 Jan – Fri 12 FebContent entered
LaunchMon 15 Feb – Fri 19 FebMilestone: go-live

The task-level schedule with owners, dependencies and a weekly progress check is worked through in how to create a project timeline.

6. Risks

Risk register
RiskLikelihoodImpactResponseOwner
Concept approval takes longer than plannedmediumhighBook the approval meeting at kick-offLea
Texts arrive late from departmentshighmediumDeadline two weeks before content entry, placeholders allowedMarco
Hosting migration problemslowhighTest migration one week before launchSara
Key person illmediummedium2 days buffer, handover notes per taskLea

Project plan, work plan, timeline: what is the difference?

Project plan: the whole picture, from goals and scope to risks. It is what a client or manager approves.

Work plan: the execution part of it: tasks, owners and dates, often for one team or one phase. Many organisations use “work plan” and “project plan” interchangeably; for small projects one document covers both.

Timeline: the dated schedule inside the plan, usually shown as a Gantt chart.

One-page project plan outline

  1. Project name, lead, date
  2. Goals (2–3, checkable)
  3. Scope: in / out
  4. Phases and deliverables
  5. Responsibilities (responsible, approves, informed)
  6. Timeline with milestones
  7. Top 5 risks with response
  8. Budget, if any

Keep it to one page for projects under three months. Longer is fine, but nobody reads ten pages before the kick-off.

Where planomatti helps

planomatti covers the tasks, responsibilities and timeline of your plan. Goals, scope and risks fit in a short document or in the description of a task.

Calendar

Set up the project

Pick the “Waterfall project” or “Event & campaign” template. Enter the start date, number of working days, hours per day and days off such as public holidays.

Tasks

Phases, work packages, milestones

Add them with the Phase, Work package and Milestone buttons. In the task panel, set the assignee and a due date.

Dates

Paint the plan

Use “Paint plan” to drag planned time across the grid, or type the hours. The grid goes from 30 minutes to whole days.

Order

By placing the bars

You set the order by placing bars one after another. planomatti does not link dependent tasks automatically.

Progress

Track actual time

Paint actual time, type it or use the timer. Key figures show total planned, actual so far and percent of plan; each row shows its difference.

Team

Share and export

Invite as many members as you need, share a read-only link with people who have no account. Export as PDF, SVG, PNG at 300 dpi or planned vs actual as CSV.

Frequently asked questions

What should a project plan include?

Goals, scope (in and out), the work broken down into phases and tasks, responsibilities, a timeline with milestones, and a list of risks with responses. Add a budget if the project has one.

How do I write a project plan?

Start with checkable goals, set the scope, break the work into tasks, assign one owner per task, build the timeline and finish with the risks. Get the plan approved, then update it when things change.

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

The timeline is the dated schedule. The project plan contains the timeline plus goals, scope, responsibilities and risks. See how to create a project timeline.

What is a work plan for a project?

A work plan describes how the work gets done: tasks, owners and dates, often for one team or phase. In practice the term is often used for the whole project plan.

How long should a project plan be?

As short as possible. One page is enough for most projects under three months; larger projects add detail per phase.

Is planomatti free?

Yes, with no trial and no credit card. You need an account with name, email and password to edit; viewers can use a read-only link.

Related guides

Plan your project together.

Sign up free, pick the waterfall template and turn your work breakdown into a timeline.

Start planning