Is a plan on a page the same as a project charter?
No. A charter explains why a project exists and how it is governed. A plan on a page shows the connected delivery work, dates, milestones and current status.
Plan on a page guide
What is a plan on a page?
A plan on a page is a visual summary of a project or programme: its outcomes, workstreams, dated activities, milestones, owners, status and dependencies—clear enough to understand in one view.
The useful version is not merely a smaller schedule. It connects the work that teams deliver with the picture that leaders use to make decisions. Plan on a Page stores those underlying facts, so the picture can change without being rebuilt.
01
What the plan needs to show
- Outcomes and workstreams, grouped into clear swimlanes
- Deliverables and dated activities at the right level of detail
- Milestones, owners, status, risks and blockers
- Dependencies that show where one part of the plan affects another
- A time horizon that is detailed enough to act on and concise enough to discuss
Why static one-page plans drift
A static one-pager records where shapes were placed. Move a date and someone must resize a bar, move its label, redraw the dependency and check that the page still fits. The picture quickly becomes a report about an earlier plan.
A live plan stores dates, relationships and status instead. Change the plan once and every derived view follows.
How to create one
Start with the outcomes or major workstreams. Add the deliverables that make each outcome real, then the dated activity behind them. Mark the decisions and hand-offs as milestones or dependencies. Finally, assign owners and make delivery status visible.
The result should answer three questions quickly: what are we trying to deliver, when does the connected work happen, and where does attention need to go now?
One plan, several conversations
Management can read the timeline, delivery teams can work from Kanban, anyone can check the month in Calendar, and a PMO can focus on exceptions in Reports. These are not separate copies: they are views of the same plan.
That is the product rule behind Plan on a Page: one data model, every view derived from it, and no second source of truth created for a particular audience.
Questions people ask
Is it only for programme managers?
No. It works anywhere several strands of work must be coordinated and explained—from construction and transformation to launches, media production and service improvement.
Can it replace a detailed schedule?
It complements detailed scheduling. Its job is to keep the important cross-workstream picture visible and current, not to reproduce every task in a specialist scheduling system.