Manage risk.
Drive confidence.
One governed register for risks, controls, claims, and reporting. Built for public-sector and institutional teams.
Risk activity
Last 12 monthsNew and updated risks per month
AI review
AssistiveDrafts awaiting owner approval
Govern
Appetite, policy, ownership
Identify + Assess
Registers, ratings, severity
Mitigate
Owners, treatments, evidence
Report
Board and council views
From first entry to final report
Every lifecycle stage works against the same connected register, so nothing is rebuilt by hand between phases.
Identify
Capture enterprise, operational, project, and strategic risk in one structured register, with an owner and a rating on every entry.
- Enterprise, operational, project, and strategic risk types
- Owner and department tagging
- Inherent and residual rating
- Next-review scheduling
Assess
Score likelihood and impact on a five-level severity scale, and keep inherent and residual ratings side by side on each risk.
- Five-level severity scale
- Likelihood and impact scoring
- Inherent and residual tracked per risk
- Heat-map positioning
Mitigate
Controls and treatments carry owners, due dates, and evidence, so follow-up never depends on who remembered.
- Control and treatment owners
- Due dates and review cadence
- Evidence attachment
- Residual rating updates as treatments progress
Report
Board, council, and committee views draw from the live register instead of a spreadsheet rebuilt each cycle.
- Trend and exposure dashboards
- Treatment-progress views
- Overdue control and review surfacing
- Board and council report formats
Registers and controls, side by side
Illustrative views from the workspace. Every surface draws from the same governed register.
- 6
- Lifecycle modulesGovern through Report
- 5
- Severity levelsDedicated accessible colors
- 2
- Ratings per riskInherent and residual
- 1
- Governed systemRegisters to reporting
Controls
EffectivenessOne risk, the control that treats it
What the work looks like
Four roles, one governed register. Illustrative observations of the daily work.
The register reads the way the committee asks about it. Inherent, residual, owner, next review date.
Replaced a shared spreadsheet rebuilt each quarter.
Treatments carry owners and due dates, so follow-up does not depend on who remembered what.
Previously tracked through meeting notes and email threads.
Claims context sits next to the operational risk it relates to, ready when renewal conversations come.
Claims records used to sit in a separate system.
Reporting draws from the live register, with the trail intact when questions come.
Board packs were rebuilt by hand every cycle.
Plans that scale with your register
Start where your program is. Expand as departments, claims, and reporting come online.
Notes from the practice
Practical notes on public-sector risk, controls, claims, and reporting from the RiskCurb practice.
Questions, answered directly
Bring risk into view
RiskCurb is onboarding early teams now. Leave your work email and we will reach out when your slot opens.