Home › Guide
What is a plan on a page?
A plan on a page is a one-page visual summary of a project or programme. It shows the phases, workstreams, key milestones and decision points on a single timeline, so anyone can understand the plan in about a minute.
- One page, one timeline, the whole plan.
- It shows the shape of the work, not every task.
- It's made for the people who need to understand and decide: sponsors, boards, steering groups and the wider team.
Plan on a page, programme on a page, roadmap on a page
You'll hear several names for the same idea. Plan on a page and project on a page usually describe a single project. Programme on a page is common in the UK public sector, infrastructure and construction, where a programme groups several related projects under one plan. Product teams often say roadmap on a page, and project controls teams may call it a summary schedule or level 1 plan.
Whatever the name, the purpose is the same: one page that shows where the work is going and when the important things happen.
What goes on a plan on a page
- A title and date range, so people know what they're looking at and how current it is.
- A calendar across the top: years, quarters or months, and sometimes your organisation's reporting periods.
- Phases or life-cycle stages, such as concept, definition, delivery and handover, shown as bands across the timeline.
- Workstreams as rows, grouped into a few sections, for example governance, design, delivery and transition.
- Key activities as bars, summarised rather than listed task by task.
- Milestones and decision points as diamonds, ideally ranked by importance so the critical ones stand out.
- Stage gates and approvals, such as business case decisions.
- A today line, so it's obvious what's done and what's coming.
- A short legend explaining colours and symbols.
Who uses one, and when
- Board packs and steering groups: the one picture that frames the discussion.
- Sponsors and senior stakeholders, who need the overall shape and the big decisions, not the detail.
- Teams and suppliers, so everyone shares the same picture of the plan.
- Business cases and bids, to show a credible delivery timeline.
- Progress meetings, where the today line makes it easy to see what has moved since last time.
Plan on a page vs a Gantt chart
A plan on a page usually sits on top of a detailed schedule rather than replacing it. The two do different jobs:
| Plan on a page | Detailed Gantt chart | |
|---|---|---|
| Purpose | Communicate the plan and support decisions | Plan and manage the work in detail |
| Detail | Phases, key activities and milestones | Every task, resource and dependency |
| Audience | Sponsors, boards, the wider team | Planners and project managers |
| Size | One page or slide | Often hundreds of lines |
| Updated | Each reporting cycle | Continuously |
How to make a plan on a page
-
Decide who it's for
A board needs decisions and milestones; a delivery team needs more of the work. Pick one audience and design for them.
-
Set the time window
Show the whole programme, or the next 12 to 24 months if it's long. Choose the calendar your organisation reports in.
-
Lay out the phases and gates
Put the life-cycle stages across the top and mark the stage gates and approval points.
-
Choose your rows
Pick the workstreams and group them into a few sections. Fewer rows make a clearer page.
-
Add the key activities
Summarise. One bar for "design" usually says more than ten bars for its tasks.
-
Add milestones, by importance
Rank them, for example P1 for board-level decisions, P2 for key controls and P3 for working milestones, and make P1 the most prominent.
-
Link what depends on what
Connect the activities that drive each other, so moving one date moves everything after it and the page stays honest.
-
Finish and share it
Add a today line, a legend and the date. Check it reads from across the room, then export it for the board pack and update it each reporting cycle.
Tips for a plan on a page people actually read
- Keep it to one page. If it doesn't fit, it's too detailed; the detail belongs in the full schedule.
- Use colour consistently, for example one colour per phase, and stick to it.
- Label bars directly rather than making people look things up in a key.
- Show fewer milestones, more clearly. Twelve visible milestones beat forty tiny ones.
- Always show the date it was produced and a today line.
Common mistakes
- Shrinking the full Gantt chart onto one slide in tiny text.
- Too many colours, so nothing stands out.
- No date or today line, so nobody knows if it's current.
- Drawing it by hand in slides, so it falls out of date as soon as a date moves.
Make your plan on a page, free
PlanOnAPage is a free plan-on-a-page planner. Start from a ready-made example, set out your stages, gates and milestones, link the dates, and export a picture or PDF for the board pack. No account needed.
Frequently asked questions
What should a plan on a page include?
A title and date, a calendar, the phases, workstream rows, key activities, milestones and decision points, a today line and a short legend. Leave out task-level detail.
How many rows should it have?
As a rule of thumb, roughly ten to twenty-five rows stay readable on a landscape page or slide. If you need more, you're probably showing too much detail.
Is a plan on a page the same as a roadmap?
They're close. A roadmap often shows direction and themes over time; a plan on a page usually shows dated activities, milestones and gates. Many teams use the terms interchangeably.
What can I use to make one?
Many people draw them by hand in PowerPoint, Excel or Visio. A dedicated tool such as PlanOnAPage keeps the dates linked, so the chart updates when the plan changes, and exports a clean picture or PDF.
Is there a free plan on a page template?
Yes. PlanOnAPage includes a simple and a detailed example you can edit, rename and export for free, with no sign-up. Open the planner to start from one.