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.
planomatti / Project plan
Guide · worked example · one-page outline
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.
Write two or three goals that can be checked at the end: what changes, by how much, by when.
List the deliverables and, just as important, what is not included. This is what you point to when new wishes appear.
Split each deliverable into phases and tasks small enough to estimate, usually 1 to 10 working days.
One owner per task. Note who approves results and who only needs to be informed.
Order the tasks, estimate durations, derive dates, add milestones and buffer.
What could delay or break the project? Rate likelihood and impact, and agree on a response and an owner.
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.
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.
Each phase ends with a result someone can check, for example “wireframes approved”.
| Deliverable | Responsible | Approves | Informed |
|---|---|---|---|
| Goals and scope | Lea | Managing director | Team |
| Wireframes and design | Tim | Managing director | Sara, Marco |
| Copy and images | Marco | Lea | Tim |
| Development and testing | Sara | Lea | Team |
| Go-live | Lea | Managing director | All staff |
| Phase | Dates | Ends with |
|---|---|---|
| Discovery | Mon 11 Jan – Wed 13 Jan | Analysis done |
| Concept | Thu 14 Jan – Tue 19 Jan | Milestone: concept approved |
| Build | Wed 20 Jan – Fri 12 Feb | Content entered |
| Launch | Mon 15 Feb – Fri 19 Feb | Milestone: go-live |
The task-level schedule with owners, dependencies and a weekly progress check is worked through in how to create a project timeline.
| Risk | Likelihood | Impact | Response | Owner |
|---|---|---|---|---|
| Concept approval takes longer than planned | medium | high | Book the approval meeting at kick-off | Lea |
| Texts arrive late from departments | high | medium | Deadline two weeks before content entry, placeholders allowed | Marco |
| Hosting migration problems | low | high | Test migration one week before launch | Sara |
| Key person ill | medium | medium | 2 days buffer, handover notes per task | Lea |
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.
Keep it to one page for projects under three months. Longer is fine, but nobody reads ten pages before the kick-off.
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
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
Add them with the Phase, Work package and Milestone buttons. In the task panel, set the assignee and a due date.
Dates
Use “Paint plan” to drag planned time across the grid, or type the hours. The grid goes from 30 minutes to whole days.
Order
You set the order by placing bars one after another. planomatti does not link dependent tasks automatically.
Progress
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
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.
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.
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.
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.
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.
As short as possible. One page is enough for most projects under three months; larger projects add detail per phase.
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.
Sign up free, pick the waterfall template and turn your work breakdown into a timeline.