What Is a Risk Rating? Definition, Formula and How to Calculate It

If you manage risk in a regulated firm, you will hear "risk rating" constantly - in RCSAs, risk registers, committee packs, and regulator conversations. It sounds simple: score how likely something is, score how bad it would be, multiply the two, and you have a priority.

In practice, risk rating is one of the most inconsistently applied concepts in enterprise risk management. Two risk owners can look at the same risk and produce different ratings because they are using different mental models of "likely" and "severe". Boards see heat maps where every risk sits in the middle. Registers carry scores that have not moved in eighteen months despite material incidents.

This article defines what a risk rating is, how to calculate it, how rating bands work, and - importantly - what separates a rating that actually drives decisions from one that is just a number in a spreadsheet.

What Is a Risk Rating?

A risk rating is the classification of a risk's criticality based on how likely it is to occur and how severe the consequences would be if it did. It answers a prioritisation question: relative to everything else on the register, how much attention does this risk deserve right now?

Most ERM and GRC frameworks express risk rating as a number produced by multiplying likelihood and impact, then translate that number into a category - Low, Medium, High, or more granular bands. The methodology is qualitative at its core: you are using structured judgement, not a statistical model, unless your programme has explicitly adopted quantitative methods for specific risk types.

Risk rating is not an end in itself. It exists to support decisions: where to invest in controls, which risks to escalate, what goes on the principal risk page of the board pack, and whether current exposure sits inside risk appetite. If the rating does not change any of those outcomes, it is decoration.

Risk Rating vs Risk Score

Vendors and frameworks use both terms. In most mid-market programmes they mean nearly the same thing, with a slight emphasis difference:

Pick one vocabulary and use it consistently in your risk register, RCSA templates, and board reporting. Auditors and regulators are far more interested in consistent definitions and evidence than in whether you call the output a "score" or a "rating".

The Risk Rating Formula

The standard qualitative formula used across ISO 31000-aligned programmes, COSO ERM, and most UK regulated-firm frameworks is:

On a 5×5 risk matrix, each axis is scored from 1 to 5. The product ranges from 1 to 25. Some organisations use a 1–10 scale on each axis (product range 1–100); the 5×5 model is the mid-market default because it is simple enough for boards to read and granular enough for triage.

Where Risk Positions Come From: Financial and Non-Financial Matrices

The multiplication is the easy part. What actually determines whether a risk rating is defensible - and whether two assessors would score the same risk the same way - is what sits underneath the grid: your impact and likelihood matrices.

In a well-run ERM programme, risk positions (the gross and net likelihood × impact scores on the register) are not plucked from intuition. They are derived by scoring each risk against published matrices that define what each level means in practice. Most frameworks separate impact into two layers:

• Financial impact matrix - anchors each impact level to monetary bands sized to your organisation's materiality. For example: Level 1 = up to £50k residual loss; Level 2 = £50k–£250k; Level 3 = £250k–£1m; and so on. The exact thresholds should reflect your ICAAP, management reporting, or board materiality - not a generic template copied from a consultant deck.
• Non-financial impact matrix - describes operational, regulatory, conduct, and reputational harm at each level. Level 3 might mean "regulatory notification required, local supervisory interest"; Level 5 might mean "national enforcement action, franchise-level reputational damage, or loss of licence to operate". Without this layer, two risks can share the same impact score while one implies a manageable fine and another implies existential harm.
• Likelihood matrix - defines credible frequency bands in testable language: less than once in twenty years; once in ten years; multiple events within five years. This lets you compare owner assessments against incident history, loss data, and external benchmarks rather than debating what "unlikely" feels like.

When a risk owner scores impact as 4 and likelihood as 3, they should be able to point to the matrix row and say: "Impact 4 means £250k–£1m financial exposure plus regulatory notification; Likelihood 3 means we expect something in this category roughly once in the assessment period." That is what makes the resulting position - 12 on a 5×5 grid - explainable to a second-line challenger, an auditor, or a non-executive director.

The same matrices apply whether you are setting a gross (inherent) position or a net (residual) position. The difference is the scenario you are scoring against: gross asks "how bad and how likely with no controls?"; net asks "how bad and how likely given controls as they actually operate?" Both positions should be traceable back to the same published definitions - otherwise gross and net scores become incomparable across risks and across quarters.

For judgement-based assessment, well-understood financial and non-financial matrices are what let a risk owner set a residual position directly and still defend it. For formula-based assessment, the matrices provide the anchor points the formula works from. Either way, the matrices are the foundation. For the four assessment approaches built on top, see how to assess enterprise risk.

Risk Rating Categories (Low, Medium, High)

After calculating the numeric rating, organisations map it to pre-defined bands. There is no single universal cut-off - firms define bands to match their risk appetite and reporting needs. A typical 5×5 banding looks like this:

Some firms use five bands (Very Low through Very High) or split Medium into two tiers. That is fine - document the thresholds in your ERM framework and apply them the same way every quarter. The failure mode is not choosing 6–12 vs 6–15 for Medium; it is having no written definition at all, so every assessor invents their own cut-offs.

Gross vs Net Risk Ratings

A single risk usually carries two ratings, not one:

• Gross (inherent) rating - likelihood × impact before controls. Shows the raw severity of the risk.
• Net (residual) rating - likelihood × impact after controls, reflecting how controls reduce likelihood, impact, or both.

The gap between inherent and residual ratings is one of the most informative outputs in an RCSA or risk register review. A risk with inherent 20 and residual 6 tells a very different story to a risk with inherent 8 and residual 6 - even though both residual ratings are identical. For full definitions, see inherent vs residual risk vs appetite explained.

How to Calculate a Risk Rating: Step by Step

Whether you are running an RCSA workshop or updating the principal risk register, the sequence is consistent:

1. Publish your matrices. Document financial impact bands, non-financial harm descriptors, and likelihood frequency statements in one place - your ERM framework or GRC tool. Do this once, not ad hoc per risk or per workshop.
2. Identify the risk. Write it as cause → event → consequence, not as a vague theme ("cyber" or "people risk").
3. Score gross likelihood and impact. Ignore controls for this step. Ask: if nothing mitigated this, how likely and how bad?
4. Multiply to get the gross rating. Record the number and the band.
5. Map controls and score net likelihood and impact. Reflect which controls actually reduce exposure and by how much.
6. Multiply to get the net rating. Compare to appetite. If outside appetite, define actions with owner and date.
7. Review on a cadence. Re-rate when something material changes - not only when the board meeting is due.

For a full walkthrough of the first-line assessment process, see how to run an effective RCSA step-by-step.

What Makes a Risk Rating Defensible?

Regulators and auditors rarely challenge the formula. They challenge whether the rating can be explained. A defensible rating has:

• Published financial and non-financial matrices - so "impact 4" means the same monetary band and the same non-financial harm descriptor to operations, compliance, and the board.
• A named owner - someone who can explain why the rating is what it is without reading from a script.
• Evidence or rationale - incident data, control test results, KRI trends, or documented judgement where data is limited.
• Movement tracking - a record of when the rating changed and why, visible quarter to quarter in board-ready risk reporting.
• Consistency - the same methodology applied across business units, not a different mental model in every workshop.

Where Risk Ratings Break Down

Most programmes have ratings. Fewer have ratings that anyone trusts. The patterns are predictable:

The fix is rarely a better formula. It is making the rating live in a system the first line actually uses - where controls, assessments, and movement history sit on the same record as the score. That is the gap most generic "how to calculate risk rating" guides skip: the arithmetic is easy; keeping ratings honest over time is the hard part.

Qualitative vs Quantitative Risk Ratings

Everything above describes qualitative risk rating - structured scales and expert judgement. That is what most mid-market ERM programmes run on, and what boards expect to see in principal risk reports.

Quantitative risk rating uses statistical models, loss data, and probability distributions to produce financial risk figures (VaR, expected loss, scenario outputs). It is appropriate for market risk, credit portfolios, and capital modelling - not for every operational risk on the register.

A mature programme is deliberate about which risks get qualitative ratings and which warrant quantitative treatment. Trying to quantify everything usually produces false precision; rating everything qualitatively without definitions produces false consistency. The right answer is usually a blend, documented in the ERM framework.

How Initia Risk Handles Risk Ratings

Initia Risk is built around the gross-to-net rating model: each risk carries inherent and residual positions on your configured matrix, linked to controls and assessments. The financial and non-financial impact matrices and likelihood matrix are fully customisable in the tool - so the definitions that drive positions live in one place, not scattered across framework PDFs and workshop slides.

When a risk owner scores a position, they are scoring against those published matrices. The platform supports both formula-driven residual ratings (derived from control type, importance, and effectiveness) and judgement-based ratings where the owner sets the position directly - grounded in the same matrix definitions either way, with a full audit trail. Heat maps and board-ready exports show movement over time, so "what changed this quarter" is visible without rebuilding slides from spreadsheets.

If your ratings live in a workbook that nobody updates between board cycles, the problem is not the formula - it is the operating model. Book a conversation if you want to see what connected ratings look like in practice.

Key Takeaways

• A risk rating classifies criticality from likelihood and impact - usually Likelihood × Impact on a 5×5 scale.
• Positions come from matrices - financial impact bands, non-financial harm descriptors, and testable likelihood frequency. Without these, the rating is just a number.
• Score vs rating - use consistent vocabulary; the number and the band both matter.
• Gross and net - capture both; the gap shows control effectiveness.
• Bands are yours to define - but they must be written down and applied consistently.
• Defensibility comes from definitions, owners, evidence, and movement - not from the multiplication itself.
• The hard part is keeping ratings current and connected to decisions - not calculating them once.

Related reading: how to assess enterprise risk, how to build a risk appetite statement, inherent vs residual risk vs appetite, and the GRC glossary for quick definitions.