Project Toolkitby Maxime Lab
Risk · tool 1 of 7

Risk · tool 1 of 7

Risk Register & Heat Map

Risk Register & Heat Map: identifies what could go wrong early, and decides what to do before it happens.

Best for: Every project · Time: Workshop + 15 min/week
Domain: Risk · Focus area: Planning

5
5
10
15
20
25
4
4
8
12
16
20
3
3
6
9
12
15
2
2
4
6
8
10
1
1
2
3
4
5
1
2
3
4
5
Rows = probability, columns = impact, score = P × I. Dark (15 and up): act now. Yellow (8–14): watch. Grey (under 8): accept.

How it works

A living log of risks. Each risk is scored on probability and impact (1–5); the product gives a priority score plotted on a heat map. Each significant risk gets a response and an owner.

  • Write risks as “Because of [cause], [event] may occur, leading to [effect]”.
  • Responses: Avoid, Reduce, Transfer (insurance, contract) or Accept.
  • Columns: ID, risk, P, I, score, response, owner, due date, status.

How to apply it

  1. Run a 60-minute risk workshop using the WBS, assumptions and lessons from past projects.
  2. Write each risk in cause–event–effect form.
  3. Score probability and impact, and plot them on the heat map.
  4. Every red risk gets a response, an owner and a date.
  5. Review the top 5 risks in every status meeting; rescore or close them.
In practice

“Because our supplier has one factory, a production stop may occur, delaying hardware delivery by 6 weeks.” P3 × I5 = 15 → find a second supplier (Reduce).

Pro tip

A risk register that is only filled at kick-off is a document, not a tool. The weekly review is what makes it work.

Use it

Quick check

Probability 3, impact 5. What is the score, and what do you do?

Sources

  • PMBOK® Guide, 8th edition, and The Standard for Project Management (PMI, 2025)

Last reviewed 2026-11-02 against the PMBOK® Guide, 8th edition · Practitioner review pending · How this guide is made