Risk anchored to business objectives — a register with screening and review, a heat map before and after controls, indicators against approved thresholds.
It is the module that manages risk across the enterprise following ISO 31000. Risks are always anchored to a unit's business objectives, screened and reviewed before entering the register, positioned on a 5×5 heat map before and after controls, then monitored with indicators against approved thresholds.
Who is it for?
The risk function operates the register and the monitoring indicators. Risk owners in business units update assessments and treatment actions. Leadership and the board track risk levels against the approved appetite.
What problems does it solve?
Three problems: the risk register is a spreadsheet updated once a year and therefore always out of date; there is no distinction between risk before and after controls; and without alert thresholds, problems only surface once a loss has occurred.
How is it different from a risk spreadsheet?
New risks must pass screening and review before they are recorded, so the register does not bloat with duplicates. Monitoring indicators have explicit thresholds and update schedules. Actual loss data feeds back into the assessed level.
How is it rolled out?
The module runs on its own and is often the starting point, because reporting reaches leadership from the earliest stage. Initial data covers business objectives per unit, the identified risk catalogue and the approved risk appetite.
The business problem
When data is scattered, material risk slips through
01
The register is updated once a year
The spreadsheet is drawn up in January and reviewed in December. By then the business context has shifted several times.
02
No distinction before and after controls
There is only one assessed level, so nobody can see how much the controls are actually reducing risk.
03
No alert thresholds
Indicators are tracked in isolation, with no threshold and no link to any specific risk.
04
Losses never feed back into assessments
An incident happens and still nobody adjusts the corresponding risk level in the register.
Risk management
Risk anchored to objectives, monitored against approved thresholds.
End-to-end process
Manage risk from identification through to monitoring
Input
Business objectives, context, approved risk appetite
Activity
Identify · screen · assess · position on the heat map
Control and approval
Review before entry; approve the treatment plan
Output
Heat map, breached indicators, board reporting
Risk management lifecyclesix steps, following ISO 310006 steps
1Objectives and context
Establish the context and business objectives the risk attaches to.
2Risk identification
Record new risks, screen and review them before entry.
3Risk assessment
Likelihood and impact, positioned on the 5×5 heat map.
4Response and treatment
Treatment plan, progress, cost and completion deadline.
5Indicator monitoring
Key risk indicators against thresholds, checked against appetite.
6Periodic review
Update the register each period and against actual loss data.
Product screens
See risk management working in practice
Two representative screens illustrating the product interface. The figures shown are sample data.
5×5 heat map
Screen 1
Position risks by likelihood and impact, comparing before and after controls. Click a cell to open the risks inside it.
app.risktech.asia / erm/heatmap
Risk management
Risk overview
Risk register
Heat map
Treatment & actions
Indicators
Risk appetite
Heat mapResidual risk
54321
3
4
2
5
8
6
7
14
9
11
16
10
4
12345
Impact →
Legend
Critical11 risks
High23 risks
Medium38 risks
Low56 risks
Risk appetite
9 risks over limit
Key risk indicator monitoring
Screen 2
Each indicator is tied to a specific risk, with a threshold, an update schedule and an owner; three states: within threshold, warning, breached.
app.risktech.asia / erm/kri
Risk management
Risk overview
Risk register
Heat map
Indicators
Risk appetite
Loss data
Indicator monitoring18 indicators · 4 breached
Information security incidents / month
7
threshold ≤ 3
Files missing documents
4.2%
threshold ≤ 3%
Remediation time
21 days
threshold ≤ 30
Code
Indicator
Risk
Status
IS-01
Information security incidents
R-024
Breached
CR-04
Credit files missing documents
R-018
Warning
VEN-02
Suppliers with no fallback option
R-042
Breached
HR-01
Mandatory training completion
R-055
Within threshold
Feature groups
Every role sees exactly what they are responsible for
Objectives and context
Leadership, risk function
Business objectives per unit
Every risk tied to at least one objective
Internal and external context
Risk register
Risk function, risk owners
New risks pass screening and review before recording
Assessment before and after controls
Clear owner, unit and point of contact
5×5 heat map
All roles
Positioned by likelihood and impact
Compare risk levels before and after controls
Click a cell to open the matching risk list
Risk appetite
Leadership, board
Approved limits per risk category
Alerts for risks above their limit
Total risk level checked against appetite
Indicator monitoring
Risk function
Key risk indicators with thresholds and update schedules
Organisations with a risk register that lives in a spreadsheet
When the number of risks outgrows manual tracking
The identified risk catalogue
Organisations that need a risk-based audit plan
When you want to link with the internal audit module
The approved risk appetite
Platform linking
Connect risk with compliance and internal audit
This module runs on its own. Once linking is on, all three share the risk register, control library and evidence store — see the platform architecture diagram.
RiskTech supports organisations operating to the standards below. This is not a certification claim for the software or for the organisations using it.
ISO 31000
Risk management — guidelines
5×5 matrix
Likelihood and impact
Three lines of defence
Responsibility model
Frequently asked questions
Risk management
The standard build uses a 5×5 matrix, the common practice in Vietnam. If your organisation uses a different scale, raise it in the demo so the product team can discuss the options.
New risks must pass a screening and review step before entering the official register, so it does not bloat with duplicates or unclear descriptions.
The named owner updates them on each indicator's set schedule. Automated feeds from source systems are discussed in the demo.
Limits per risk category are approved in the system by leadership or the board, and every change is logged.
Actual loss events feed back into the assessment step, helping calibrate risk levels with what has really happened rather than judgement alone.
Once linked, material risks steer the annual audit plan, and control testing results update residual risk levels in return.
See how RiskTech supports enterprise risk management
A 30-minute demo following the role you hold. No data preparation needed beforehand. We respond within one business day.