Risk and compliance, on the same evidence spine
A separate module, sold separately. It shares the audit platform's evidence spine rather than sitting beside it, so a control tested in an audit and a control relied on in the risk register are the same control.
Design partners see the build early and shape what gets prioritised. That conversation is a call, not a form.
In the platform today
These are built and running now, inside the platform. They are listed here because ResiliRisk is a module boundary rather than a new codebase.
- Objectives
What the organisation is trying to achieve, which is what risk is measured against.
- The risk register
The register itself, in the same place as the audit evidence rather than beside it.
- The control library
The controls, held once and referenced everywhere they apply.
- Risk to control mapping
Which control addresses which risk, which is what makes coverage answerable.
- Jurisdiction packs
Regulatory content selected at onboarding rather than assumed. Provisional pending counsel review.
Being built
These are named and being worked on, and none of them carries a date. A date the build has not committed to is a promise somebody else has to keep.
- Bow tie analysis
Causes and consequences either side of an event, with the controls on both.
- The heat map
The register plotted by likelihood and impact.
- The objective risk profile
Risk rolled up to the objective it threatens.