Status
Overall RAG status, progress and supporting rationale
Not set
Stage gates
Lifecycle position — click a gate to mark it current
Upcoming milestones
Open action due dates, earliest first
Key risks
Open risks, highest severity first
Project charter
Purpose, high-level scope, leadership and success
Writing guide
Purpose and intended outcomes: Why is this project needed, who benefits, and what should change?
High-level scope: Summarise the main deliverables and major exclusions. Keep the detailed lists and work breakdown in Scope.
Sponsor, project manager and key stakeholders: Name the business sponsor, project manager and the main groups involved or affected. Keep the full stakeholder register in People.
Success measures and key commitments: What would success look like? Note the headline measures, major dates, funding limits or constraints that shape the commitment. Keep detailed acceptance criteria in Scope.
Use only the headings that help. This is your project narrative; names and other details are not synchronised with the registers.
Start with an outline, or write freely below.
Scope statement i
Work breakdown i
Schedule i
Stakeholder register
Power / Interest grid
Power →
Keep satisfied
High power, low interest
Manage closely
High power, high interest
Monitor
Low power, low interest
Keep informed
Low power, high interest
Interest →
Dots show initials; hover one for the full name. Position is set from each stakeholder's Power & Interest — edit those to move a dot.
RACI matrix i
Communications plan i
Risk & Issue register
Probability × Impact matrix
Open risks plotted by likelihood and impact (issues have already occurred, so they drop off the matrix). Toggle the view — opportunities are coloured so that high/high reads as "pursue", not danger.