All topics

Risk Review

Category: Project Management

Focused risk review: project context, risk register, new vs closed risks, escalations, next review date.

When to use this template

Use it for the periodic risk-review meeting in a project or program — the conversation where the register is updated, new risks are added, closed risks are retired, and escalations are decided. For ad-hoc risk discussions embedded in a status update, see Status Update.

Fields captured

Project / context — name and scope of the project or program being reviewed.
Risk register — the live set of risks: id, description, likelihood, impact, owner, and mitigation.
New risks — risks identified in this review that are not yet in the register.
Closed / accepted risks — risks retired or formally accepted in this review.
Escalation needed — anything that needs to leave this meeting (leadership, a vendor, etc.).
Next review date — when the next risk review is scheduled.
Next steps — concrete follow-up tasks.
Key takeaways — the AI's prioritized summary points.

The standard summary, attendees, and per-section summaries also apply.

Sub-views, role views, and pipeline artifacts

Sub-views: none.
Role views: Sales Engineer, Project Manager, Executive Sponsor.
Pipeline artifacts: Risk register (Risk Review only; one-click generate, formatted as [L=… I=…] — mitigation: … rows) and Email draft (recipient, tone, optional subject hint).
Study mode: not available.

Exports

PDF, DOCX, and Markdown include the risk register as a formatted table with likelihood, impact, owner, and mitigation. Approved risk-register artifact appears as its own appendix. Approved email drafts appear in exports too.