How to write a one-page project plan
Most small projects do not need a 30-page document. They need one page that everyone agrees on and that answers: what, who, when and what could go wrong.
Last updated 2026-10-24
State the goal in one sentence
Finish the sentence “This project is done when…”. If you cannot, the scope is not clear yet.
Say what is out of scope
Write two or three things you are not doing. It prevents most of the arguments later.
Break the work into tasks
- Each task should be small enough to finish in a few days.
- Each task has one owner, even when several people help.
- Each task has a due date.
Group tasks into phases
Four phases fit most projects: start, plan, do and finish. The names matter less than the idea that early work (decisions, requirements) comes before the building.
Name the risks
List the three things most likely to delay you, such as waiting for approvals, a key person being away, or a supplier. Next to each, write what you will do if it happens.
Agree how you will check progress
A short weekly check-in is enough for most small projects. Look at what is done, what is blocked, and whether the end date is still realistic.
Draw the timeline
A bar chart of tasks against dates shows overlaps and crunch points that a list hides. Check that no one person has too much in the same week.
Please note. This guide is general information, not financial, legal or professional advice. Read the full disclaimers.