Project inception

Initiative charter & risk dashboard

Draft: not saved yet

AI guidance available

A. Initiative overview

Project summary

Overall risk: Not scored

Initiative name

Sponsor / Owner

Objective

Target business outcomes

Scope – in

Scope – out

Solution overview

Business case highlights

Key milestones

B. Risk evaluation

Risk matrix

Likelihood × Impact → automatic scoring

Dimension	Guiding question	L (1–5)	I (1–5)	Score	Level	Mitigation notes	Actions

C. Scope & change control

Scope guardrails

Change control process

Examples of items explicitly out of scope

D. RACI alignment

Key roles

Sponsor (A)

Product Owner (R/A)

Project Manager (R)

Tech Lead / Architect (C/R)

Risk & Compliance (C)

Finance / Controller (C)

Use this section to capture who is ultimately Accountable (A) and Responsible (R) for key decisions like scope changes, risk acceptance and budget approvals. Details of the full RACI matrix can live in the underlying deck or Confluence page.

AI Guidance Panel

Workers AI tips Context-aware

Click “Get AI Guidance” to generate tailored advice based on the information you’ve entered for this initiative.

Quick interpretation guide

1–5 Low: proceed, track in standard governance.
6–14 Medium: add explicit mitigations & owners.
15–25 High: escalate to SteerCo; consider phasing or de-scoping.

AI will never replace governance – it simply highlights blind spots and suggests mitigations.

Recommended usage:

Run AI once after completing sections A–D.
Use the tips to refine your charter, risk mitigations and RACI.
Attach a snapshot of this page to your SteerCo pack as the “Initiative evaluation” slide.

How a project manager should use this tool

Before the session, define who needs to be in the room: Sponsor, Product Owner, Project Manager, Tech Lead and at least one representative from Risk/Compliance and Finance.
Start in Section A and agree the objective, target outcomes and scope (in and out). Do not move on until there is clear, shared language – this is your reference point for all later decisions.
Use Section B as a structured risk workshop. Let each stakeholder propose Likelihood and Impact scores, then converge on a single view. Capture named owners and concrete mitigation actions in the notes.
In Section C, translate the biggest risks into scope guardrails and a simple change control process. Explicitly note examples of items that are “out of scope” to reduce future scope creep debates.
Complete the key roles in Section D and check that every major decision type has a clear Accountable and Responsible owner. If accountability is unclear, resolve it before proceeding.
Finally, run the AI Guidance Panel and review the suggestions as a team. Adjust scores, mitigations or RACI assignments where appropriate, then record the overall recommendation: Go, Conditional Go (with actions) or No-Go.

As a PM, treat this artefact as a living document: update it at each major gate and keep it aligned with your formal project charter and SteerCo reporting.