Risk anchored to business objectives — a register with screening and review, a heat map before and after controls, indicators against approved thresholds.
The spreadsheet is drawn up in January and reviewed in December. By then the business context has shifted several times.
There is only one assessed level, so nobody can see how much the controls are actually reducing risk.
Indicators are tracked in isolation, with no threshold and no link to any specific risk.
An incident happens and still nobody adjusts the corresponding risk level in the register.
Two representative screens illustrating the product interface. The figures shown are sample data.
Position risks by likelihood and impact, comparing before and after controls. Click a cell to open the risks inside it.
Each indicator is tied to a specific risk, with a threshold, an update schedule and an owner; three states: within threshold, warning, breached.
| Who it fits | When to use it | Data to prepare |
|---|---|---|
| Organisations starting to build a risk framework | When leadership asks for periodic risk reporting | Business objectives per unit |
| 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 |
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.
This scenario explains how the product is used; it is not the result of a rollout at a specific client. Once we have a real client scenario with written consent to publish, this section will be updated.
A 30-minute demo following the role you hold. No data preparation needed beforehand. We respond within one business day.
