Skip to content

← Back to blog

Frameworks · 7 min read · 2026-09-02

The PRINCE2 Risk Theme, Mapped to KinetiRisk

A step-by-step walk through the PRINCE2 risk procedure, identify to communicate, with the part of KinetiRisk that does each one: proximity, response strategies, review cadence and AI-assisted scoring.

PRINCE2 handles risk as one of its seven themes, with a five-step procedure that most people working in a PRINCE2 environment can recite: identify, assess, plan, implement, communicate. If your governance is built on that procedure, you want a tool that follows the same shape rather than one you translate into it every week.

KinetiRisk does. It is not an introduction to the risk theme: it assumes you know the terms and want to see the mapping.


How KinetiRisk Maps to the PRINCE2 Risk Theme

KinetiRisk maps each step of the PRINCE2 risk procedure to a specific part of the product. The risk management strategy is project settings: scales, risk tolerance, proximity, categories and roles. Identify is structured risk creation and CSV import. Assess is AI probability and impact scoring plus a dedicated proximity field. Plan is the response strategy field and AI-drafted response actions. Implement is the action tracker with owners, due dates and progress. Communicate is automated escalation email, the dashboard, the board narrative, programme rollups and risk change history. Each step is covered in order below.

Assessment uses the qualitative probability times impact model common to PRINCE2, PMBOK and ISO 31000, not quantitative simulation.


The Risk Management Strategy

PRINCE2 expects a documented risk management strategy that sets risk appetite, scales, proximity, roles and tolerances before the project starts assessing anything. KinetiRisk captures those parameters in project settings, in one place, so the strategy is configuration rather than a file nobody reopens.

Scales
Each project defines what probability 1 to 5 and impact 1 to 5 mean in its own words. The AI scores against those definitions and they appear as tooltips wherever a score is chosen.
Risk tolerance
An escalation threshold expressed as a number. When probability times impact reaches it, the risk escalates. The default is 15 out of 25.
Categories
A two-level risk breakdown structure per project, named by you.
Roles
Project Manager, Viewer and Super Admin, scoped to project membership.

Identify

Risk creation uses structured fields that line up with a PRINCE2 risk register. Cause, event and effect go into the title, description and context fields; then there is the owner, the category path and the risk type of threat or opportunity.

Existing registers come across by CSV, with automatic column mapping for the common headers. During a full analysis the AI also flags interdependencies between open risks, with the causal chain stated rather than implied.


Assess

Assessment is qualitative. The AI proposes a probability and an impact score from 1 to 5 with a short explanation of its reasoning, and expected value is simply probability times impact on the 5 by 5 grid.

Proximity is a first-class field: imminent, within the stage, within the project, or beyond the project. It is the PRINCE2-specific dimension that most risk tools leave out entirely, and the AI assesses it alongside the scores. Every score can be overridden by a person, and the change is recorded.


Plan

Response strategies map directly onto the PRINCE2 vocabulary. For threats: avoid, reduce, transfer, accept, or prepare a contingency. For opportunities: exploit, enhance, share, or reject. The AI recommends one during a full analysis.

Alongside it, the AI drafts response actions, each with a suggested role and a weight showing its expected contribution to the residual score. Each action has an owner, a due date and a status.


Implement

Actions move through pending, in progress, complete and cancelled. A My Actions view gives each person their assigned actions across every project they work on. Progress updates automatically as actions close, and when the last mitigation on a risk completes KinetiRisk prompts the project manager to apply the AI's forecast residual score.


Communicate

PRINCE2 asks more of a tool at this step than at any other, and it is where a spreadsheet gives up. KinetiRisk covers it several ways.

Escalation emails
When a risk breaches the threshold, an email goes to the escalation contacts automatically. There is no acknowledgement or acceptance step for the recipient; the alert is the mechanism.
Dashboard
Heatmap, escalation feed and reviews-due alerts in one view.
Board narrative
A written summary with a RAG status, generated from the current register. Available from the Starter plan.
Programme rollups
Risks aggregate from project to programme to portfolio without re-entry. Portfolio risk clustering groups related risks across projects on the Team plan.
Review reminders
Set a review date per risk or a cadence for the project. Overdue risks appear on the dashboard and their owners are emailed, so the register does not drift. On every plan.
Risk change history
Every movement in a risk since it was raised, timestamped against who made it. On every plan.

What PRINCE2 Practitioners Look For That Most Tools Miss

Three things come up repeatedly.

  • Proximity. KinetiRisk has it as a real field, and the AI assesses it during a full analysis.
  • Separate threat and opportunity registers. There is a threat and opportunity toggle, with the response vocabulary and the heatmap filtered to match, so upside is managed rather than filed next to downside and forgotten.
  • Escalation to programme. Threshold-based escalation plus programme-level views maps onto PRINCE2's escalation governance directly.

KinetiRisk follows the PRINCE2 risk procedure by default, on a free tier with no expiry. Start free.

Start free See how it works

The Free plan includes proximity tracking, response strategies, review reminders and the hierarchical category tree, with one project, 25 AI analyses a month and automatic escalation alerts. No card, no time limit.

If your organisation works to the PMBOK Guide rather than PRINCE2, the process names differ but the mapping is just as close. See how KinetiRisk supports PMBOK risk management.


Frequently Asked Questions

Does KinetiRisk follow the PRINCE2 risk theme?

Yes. It follows the five-step risk procedure: identify, assess, plan, implement, communicate. Each step maps to a specific part of the product. What it does not provide is a formal stage-gate workflow or a generated risk management strategy document.

Does KinetiRisk support risk proximity?

Yes, as a dedicated field with four values: imminent, within the stage, within the project, and beyond the project. The AI assesses proximity during a full analysis alongside the probability and impact scores, and it is available on every plan including Free.

How does escalation to programme work?

Each project has an escalation threshold. When a risk's probability times impact reaches it, the risk escalates automatically and an email goes to the escalation contacts. There is no acknowledgement or acceptance flow for the recipient. Risks also roll up into programme and portfolio views without being re-entered.

Can KinetiRisk handle opportunities as well as threats?

Yes. Every risk is a threat or an opportunity. The response strategy options and the heatmap view change to match, so opportunities are assessed for upside and given exploit, enhance, share or reject responses rather than being treated as threats.

What does it cost to run PRINCE2 risk management in KinetiRisk?

The full procedure is on the Free plan: one project, 25 AI analyses a month, proximity, response strategies, automatic escalation, review reminders and risk change history, with no card and no expiry. The residual risk forecast score is on Starter at £5 a month; the full forecast, portfolio risk clustering and weighted mitigation progress are on Team at £25 a month for 10 seats.

PRINCE2 gives you a clear risk procedure and a governance structure to run it in. The difficulty has always been keeping a register that actually behaves the way the theme describes, week after week, without a dedicated risk resource. KinetiRisk makes the procedure the default behaviour of the tool, proximity and all, so a project manager in a PRINCE2 environment can work inside it from the first risk they log.

Start free →