Risk Assessment Matrix
Score risks on 1 to 5 probability and impact scales, see them placed on a colour-banded 5x5 grid, and keep a risk list with mitigations you can export.
The interactive tool loads here when JavaScript runs.
About this toolWhat is the Risk Assessment Matrix?
The Risk Assessment Matrix places each risk on a 5x5 grid by probability (rows, 5 at the top) and impact (columns). You add a risk with a name, description, probability from 1 to 5, impact from 1 to 5, a category and a mitigation, and its name appears in the matching cell. Hover a name to see its description.
Each cell is coloured by its score, probability multiplied by impact: 1 to 4 is Low (green), 5 to 9 Medium (yellow), 10 to 16 High (orange) and 20 or 25 Critical (red). The Risk List below the grid repeats every risk with its score out of 25, its level badge and its mitigation.
The register is saved in this browser and is still there when you come back on the same device. Use Export to download it as JSON and Import to open it elsewhere. Everything runs in your browser.
- 5x5 grid with Low, Medium, High and Critical colour bands
- Score out of 25 and level badge for every risk
- Five risk categories and a mitigation field per risk
- JSON export and import, with ratings clamped to 1-5 on import
- Sample register for a product launch
Updated
How to use the Risk Assessment Matrix
- Set the assessment title, for example "Mobile app launch, Q1 2027".
- Click Add Risk, fill in the risk name and description, then pick Probability (1-5), Impact (1-5) and a Category: Operational, Financial, Strategic, Compliance or Technical.
- Write a mitigation strategy and click Add Risk in the form. The risk appears in its grid cell and in the Risk List with its score and level.
- Click Load Sample to see six scored risks for a mobile app launch.
- Use Export to save the register as JSON and Import to load it again; Clear All empties it.
Worked example
The sample mobile app launch register
Input
Low User Adoption: P4 x I5 Development Delays: P3 x I4 Data Privacy Breach: P2 x I5 Budget Overrun: P3 x I3 App Store Rejection: P2 x I3
Output
Low User Adoption: 20/25 Critical Development Delays: 12/25 High Data Privacy Breach: 10/25 High Budget Overrun: 9/25 Medium App Store Rejection: 6/25 Medium
The privacy breach is unlikely but sits in the High band because impact 5 pulls it up. Many teams add a rule that any impact-5 risk needs a named owner regardless of score, because the multiplication alone understates rare catastrophic events.
Background and insight
Likelihood times impact is the oldest shortcut in risk management, and the 5x5 version is the one most project and operational risk registers use. ISO 31000 (the risk management guidelines, last revised in 2018) asks organisations to analyse likelihood and consequence but does not require a matrix or any particular bands; the bands here are a common convention, not a standard.
Because the scales are ordinal, a score of 12 is not "twice as risky" as 6. Only fourteen distinct scores are possible (1, 2, 3, 4, 5, 6, 8, 9, 10, 12, 15, 16, 20, 25), and a 5x1 risk (near certain, trivial) scores the same as a 1x5 risk (rare, catastrophic) even though most boards would treat them very differently. Louis Anthony Cox Jr. set out these problems in his 2008 paper "What's Wrong with Risk Matrices?" in Risk Analysis.
The practical fix is to define the scales before anyone scores. Write down what a 4 for impact means in money, days of delay or customers affected, and what a 3 for probability means as a rough percentage over a stated period. Without that, two people will score the same risk two levels apart and the grid becomes a record of who was in the room.
Common use cases
Project risk registers
Project managers score launch, migration or construction risks and review the red and orange cells at each steering meeting.
Operational and vendor risk
Ops and procurement teams rate supplier failure, outages and key-person dependencies on one grid.
Compliance and audit prep
Show auditors a dated register with scores and mitigations, exported as JSON for the evidence file.
Board and investor updates
Summarise the top risks visually instead of a long table.
Tips and limitations
- Agree written definitions for each probability and impact level before scoring; it matters more than the bands.
- Score the risk as it stands today, then note the mitigation. If you want a residual score after mitigation, add the risk again with "(residual)" in the name.
- Treat any impact-5 risk as needing an owner even if its score lands in Medium or High.
- The saved copy only reflects the latest state. Export the JSON after each review and keep the files dated to see how scores moved.
- Hover a name in the grid to read its description without scrolling to the list.
Sources and further reading
- ISO 31000:2018 Risk management: Guidelines, International Organization for Standardization. The risk management guidelines, which ask for likelihood and consequence but prescribe no grid
- IEC 31010:2019 Risk management: Risk assessment techniques, International Electrotechnical Commission. The companion standard that describes the consequence and likelihood matrix among other techniques
- What's Wrong with Risk Matrices?, Risk Analysis. Louis Anthony Cox Jr.'s 2008 paper on how matrices can misrank risks
Frequently asked questions
How is the risk score calculated in a 5x5 risk matrix?
The score is probability multiplied by impact, each rated 1 to 5, so it ranges from 1 to 25. In this tool 1 to 4 is Low, 5 to 9 Medium, 10 to 16 High and 20 to 25 Critical. A risk rated probability 3 and impact 4 scores 12, which is High.
Why does a risk with impact 5 only show as High?
Because the score multiplies the two ratings, a rare but severe risk such as probability 2 and impact 5 scores 10, which sits in the High band. That is a known limitation of risk matrices. Many organisations add a rule that any maximum-impact risk gets an owner and a plan regardless of its score.
Is the 5x5 risk matrix an ISO standard?
No. ISO 31000 sets out risk management principles and asks you to analyse likelihood and consequence, but it does not prescribe a 5x5 grid or fixed colour bands. The bands in this tool are a widely used convention; your organisation may use different thresholds.
What do the risk categories in the matrix do?
Operational, Financial, Strategic, Compliance and Technical are labels that appear as a badge in the Risk List so you can group and assign risks. They do not change the score or the colour of the grid cell.
How do I keep my risk register between sessions?
It is saved automatically in this browser under the key risk-matrix, so a reload keeps the grid. To move it to another computer or share it, click Export to download a JSON file and use Import there. Keeping one dated export per review also gives you a history of how scores changed.
Should I score inherent or residual risk?
Score inherent risk first, meaning the risk with only the controls you have today, and write the planned mitigation alongside. Once mitigations are in place, add a residual version of the risk so you can show the reduction. Mixing the two in one register makes scores impossible to compare.
Is there an in-depth guide to the Risk Assessment Matrix?
Yes. “How to Use a 5x5 Risk Matrix (and Where Its Scores Mislead)” covers the background, how it works, common pitfalls and worked examples. Read the full guide.
Related Tools You May Like
Free, in-browser tools that pair well with this one.