Follow each incident back to what caused it.
Risk Incidents links each incident to the control, risk, process and policy behind it, with an owner on each action.
Shown on Halden, our fictitious Lloyd's managing agent. See how Halden runs it
What has gone wrong this year?
- 8Incidents in 2026
- 4Still open
- 2High severity, open
- Coverholder bound 23 risks outside its territoryINC-031 · control failed · Lloyd's notifiedHigh
- Sanctions alert cleared without evidenceINC-026 · sanctions screeningHigh
- UAE fronted claims settled lateINC-028 · under investigationMedium
Incident reporting changes on 18 March 2027.
Our reading: the facts for a report should already sit on the incident record, not be gathered after the event.
- 18 Mar 2027 · FCANew rules on operational incident and third-party reporting come into force on 18 March 2027.Source: FCA PS26/2, Operational incident and third party reporting (opens in a new tab)
- Apr 2026 · PRASenior individuals "remain accountable for the actions of those to whom they delegate responsibilities", including where firms outsource to third parties.Source: PRA SS35/15, April 2026 update, para 2.33 (opens in a new tab)
- 2026 · Lloyd'sLloyd's began collecting cyber metrics from managing agents "for the first time by June 2026", and now collects them "on a 6-monthly basis".Source: Lloyd's Market Oversight Plan 2026, p8 (opens in a new tab)
What you get
-
Open an incident and see the control, risk and step behind it, in one click.
Each record holds the root cause, the control involved, the risk it touches and the step where it happened.
- Today
- A list with a status column
- With CoVi Analytics
- Each incident linked to its cause
IncidentINC-031 · 23 risks outside territoryControlC-137 · coverholder audits, failedRiskOR-06.1 · binding outside authorityStepDA oversight · annual coverholder audit -
Count root causes as they happen, not at year end.
Each incident carries a root cause, so a pattern shows while there is still time to act on it.
- Today
- Root causes found at year end
- With CoVi Analytics
- Counted as each incident lands
Root causes in 2026Halden · 8 incidentsAll three third-party incidents are still open.
-
Start a regulator notification from a record that already holds the facts.
Impact, root cause, control, policy, regulator status and actions sit on one record, so the story does not have to be rebuilt under pressure.
- Today
- Facts gathered after the event
- With CoVi Analytics
- One record, ready when a report starts
Halden's incidents report, open incidents first.
Fix the cause, not only the incident.
Each incident leads back to the control and step that let it happen, so the fix lands where it started.
Bring your incident log. See where each one leads.
Tell us how you log incidents today, and leave knowing where to start.
We'll walk you through how it all comes together with Halden.