Inherent risk vs residual risk: the core distinction
Inherent risk is the level of risk that exists before any controls are applied — the raw exposure. Residual risk is what remains after your existing controls are taken into account. The gap between the two is, by definition, a measure of how effective your controls actually are.
Conflating the two is one of the most common mistakes in risk management. A heat map that quietly mixes inherent and residual scores across different risks is not comparable and will mislead the board.
Scoring inherent risk
Score inherent risk by asking: if no controls existed at all, how likely is this event and how severe would the impact be? This should be assessed independently of what you currently have in place — it is a theoretical ceiling, not a prediction of what will actually happen.
- Likelihood: based on historical frequency, industry benchmarks, and threat intelligence where relevant.
- Impact: based on financial, operational, regulatory, and reputational consequences, using a consistent scale across the organization.
Scoring residual risk and control effectiveness
Residual risk starts from the inherent score and adjusts downward based on control effectiveness. A useful practical method:
- Rate each linked control's effectiveness (e.g. ineffective, partially effective, effective) based on actual testing results — not design intent.
- Reduce likelihood and/or impact proportionally to the combined effectiveness of all linked controls, not just the strongest one.
- Re-score residual risk every time a control test result changes, not just annually.
This is where a Second Line of Defense testing cycle matters: an untested control should never be treated as an effective one. Our guide on the Three Lines of Defense model covers how testing responsibility should be assigned.
Common mistakes to avoid
- Scoring residual risk first and reverse-engineering inherent risk — this hides how much you actually depend on controls.
- Letting risk owners self-rate control effectiveness without independent testing evidence.
- Never revisiting residual scores after a control fails a test, leaving stale "green" ratings on the heat map.
- Mixing scales across business units, making organization-wide heat maps meaningless.
How Reesk supports this workflow
Reesk's assessment UX is built specifically around this inherent-to-residual flow: score inherent risk, link controls, record testing results, and watch residual risk update with full history and audit trail — not a static snapshot. Try it on the free plan or check the pricing page for teams that need more risks and AI-assisted scoring rationale.
