A risk register fails in one of two ways: it is a spreadsheet nobody opens between audits, or it is a list of worries with no link to anything real. The register in Simson Desk is built to avoid both.
What a risk records
- What could happen, and to what.
- The asset, vendor or information asset it is linked to.
- Likelihood and impact, each on a five-point scale.
- The treatment chosen, and the plan for it.
- The residual rating once the treatment is in place.
- An owner and a review date.
Linked risks have a minimum impact
When a risk is linked to an item that is rated High or Moderate, its impact cannot be set below a floor. The value of the thing at risk limits how small you can call the consequence.
Four treatments
| Treatment | Meaning |
|---|---|
| Mitigate | Reduce the likelihood or the impact with a control |
| Transfer | Pass it to another party, such as an insurer or a supplier |
| Avoid | Stop the activity that creates the risk |
| Accept | Live with it, with management’s recorded agreement |
The heat map
Risks are plotted on a five-by-five grid of likelihood against impact, so the cluster in the top-right corner is visible at a glance. It is the page a management review actually looks at.
Reviews that fall due
Each risk has a review date. Overdue reviews and risks with no residual rating are listed separately, because those are the first two things an auditor asks about.
The export
A manager can export the register as a PDF: an overview with counts and the heat map, the points a reviewer should look at, the register as a table, a detail card for each risk, the method used, and sign-off lines. Every export is logged, with who made it and when.
- Who can export the risk register?
- Compliance managers and administrators. Each export is recorded in the audit log.
- Can a risk be linked to a vendor?
- Yes — to an asset, a vendor or an information asset.
- How often are risks reviewed?
- Each risk carries its own review date, and overdue reviews are listed.