Want your procedures as a map?
Tell us which process gives you the most trouble. We will show you how it would look on the map, using Halden as the starting point.
You run the processes and own the procedures. The risk team needs evidence that they work. CoVi Analytics puts both on one map, so a failed control shows where it happened. Single incident reporting to the PRA and FCA begins on 18 March 2027.
Halden is a fictitious Lloyd's managing agent. We run it in CoVi Analytics and publish its reports one at a time.
Somewhere there is a folder full of Word documents that nobody opens, because the work moved on. When the risk team needs evidence, your team stops and goes looking. Meanwhile the hard parts of the job sit with partners: coverholders, fronting insurers and outsourcers. The FCA said it plainly on 28 May 2024: if a partner breaks impact tolerance, the failure is yours.
Halden's operating model as a tube map. Lines are processes and stops are key activities. Select a pulsing ring to open its process flow.
A failed step on your map is a problem the board feels too. At Halden, DA oversight, where the coverholder audit failed, feeds three of the board's appetites: conduct, counterparty and operational.
ExploreSelect a pulsing stop, or open a line below, to see its process flow.
Everything that touches brokers and policyholders: winning business, writing it, servicing it and paying claims.
Front office lines · open one to see its stops
Loops back to the start and runs continuously.
Everything that keeps the business planned, funded, invested, controlled and staffed, with IT and people running underneath.
Back office lines · open one to see its stops
Loops back to the start and runs continuously.
Loops back to the start and runs continuously.
How we approve, monitor and audit the coverholders who write business on our behalf.
Process flow · open a step
Red badges count failed controls. Outlined badges count active incidents raised against a control mapped to that step. Dashed boxes are decisions; committee steps are tagged where they sit in the flow.
How a claim turns into a booked reserve: case reserves from claims, IBNR from actuarial, signed off by committee.
Process flow · open a step
Red badges count failed controls. Outlined badges count active incidents raised against a control mapped to that step. Dashed boxes are decisions; committee steps are tagged where they sit in the flow.
Halden is fictitious. Source: front and back office process maps, controls by team, incident log, action log at 30 Sep 2026
Step 1 · DA oversight
Inputs
Outputs
What happens
Due diligence on ownership, financial standing, licences, sanctions and systems before Lloyd's approval is sought.
Active incidents
Risks mapped
Rating shown is residual risk: likelihood A to E, impact 1 to 5.
Controls mapped
Source: process map, risk register, controls by team, incident log at 30 Sep 2026
Step 2 · DA oversight
Inputs
Outputs
What happens
Agree classes, territories, limits and premium caps, then load them into the policy system.
Risks mapped
Rating shown is residual risk: likelihood A to E, impact 1 to 5.
Controls mapped
Source: process map, risk register, controls by team, incident log at 30 Sep 2026
Step 3 · DA oversight
Inputs
Outputs
What happens
Bordereaux are loaded, mapped and checked against authority limits and data standards.
Active incidents
Risks mapped
Rating shown is residual risk: likelihood A to E, impact 1 to 5.
Controls mapped
Source: process map, risk register, controls by team, incident log at 30 Sep 2026
Risks outside authority found? Yes
Inputs
Outputs
What happens
The class underwriter reviews each breach, agrees cancellation or endorsement and logs it as an incident.
Risks mapped
Rating shown is residual risk: likelihood A to E, impact 1 to 5.
Controls mapped
Source: process map, risk register, controls by team, incident log at 30 Sep 2026
Risks outside authority found? No
Inputs
Outputs
What happens
Clean bordereaux are accepted and premium is booked to the ledger.
Risks mapped
Rating shown is residual risk: likelihood A to E, impact 1 to 5.
Controls mapped
Source: process map, risk register, controls by team, incident log at 30 Sep 2026
Step 4 · DA oversight
Inputs
Outputs
What happens
Each coverholder is scored on profitability, data quality, conduct and audit results.
Risks mapped
Rating shown is residual risk: likelihood A to E, impact 1 to 5.
Controls mapped
Source: process map, risk register, controls by team, incident log at 30 Sep 2026
Step 5 · DA oversight
CommitteeReports to the Underwriting committee
Inputs
Outputs
What happens
Monthly committee reviews coverholder performance, breaches and audit results, sets the watch list and recommends renewals.
Risks mapped
Rating shown is residual risk: likelihood A to E, impact 1 to 5.
Controls mapped
Source: process map, risk register, controls by team, incident log at 30 Sep 2026
Step 6 · DA oversight
Inputs
Outputs
What happens
On-site or remote audit of underwriting, claims handling, conduct and client money.
Active incidents
Risks mapped
Rating shown is residual risk: likelihood A to E, impact 1 to 5.
Controls mapped
Source: process map, risk register, controls by team, incident log at 30 Sep 2026
Renew the binding authority? Renew
Inputs
Outputs
What happens
Terms, limits or classes are adjusted to reflect performance and findings before renewal.
Risks mapped
Rating shown is residual risk: likelihood A to E, impact 1 to 5.
Controls mapped
Source: process map, risk register, controls by team, incident log at 30 Sep 2026
Renew the binding authority? Exit
Inputs
Outputs
What happens
The coverholder is notified and in-force policies and claims are managed to expiry.
Risks mapped
Rating shown is residual risk: likelihood A to E, impact 1 to 5.
Controls mapped
Source: process map, risk register, controls by team, incident log at 30 Sep 2026
Step 1 · Reserving
Inputs
Outputs
What happens
The claim is registered against the policy, cover is checked and an initial reserve is set.
Active incidents
Risks mapped
Rating shown is residual risk: likelihood A to E, impact 1 to 5.
Controls mapped
Source: process map, risk register, controls by team, incident log at 30 Sep 2026
Large loss above threshold? Yes
CommitteeReports to the Underwriting and Reserving committees
Inputs
Outputs
What happens
Claims above the large loss threshold are reviewed fortnightly and the reserve is agreed by committee.
Risks mapped
Rating shown is residual risk: likelihood A to E, impact 1 to 5.
Controls mapped
Source: process map, risk register, controls by team, incident log at 30 Sep 2026
Large loss above threshold? No
Inputs
Outputs
What happens
The adjuster sets and updates the case reserve within their authority.
Risks mapped
Rating shown is residual risk: likelihood A to E, impact 1 to 5.
Controls mapped
Source: process map, risk register, controls by team, incident log at 30 Sep 2026
Step 2 · Reserving
Inputs
Outputs
What happens
Third-party claims data is reconciled to the ledger and checked for timeliness.
Active incidents
Risks mapped
Rating shown is residual risk: likelihood A to E, impact 1 to 5.
Controls mapped
Source: process map, risk register, controls by team, incident log at 30 Sep 2026
Step 3 · Reserving
Inputs
Outputs
What happens
Actuarial projects ultimate losses by class and adds IBNR for claims not yet reported.
Risks mapped
Rating shown is residual risk: likelihood A to E, impact 1 to 5.
Controls mapped
Source: process map, risk register, controls by team, incident log at 30 Sep 2026
Step 4 · Reserving
CommitteeReports to the Audit and Risk & capital committees
Inputs
Outputs
What happens
Claims, actuarial, finance and underwriting agree booked reserves and any margin.
Risks mapped
Rating shown is residual risk: likelihood A to E, impact 1 to 5.
Controls mapped
Source: process map, risk register, controls by team, incident log at 30 Sep 2026
Step 5 · Reserving
Inputs
Outputs
What happens
Reserves are booked and flow into the financial statements, technical provisions and Lloyd's returns.
Risks mapped
Rating shown is residual risk: likelihood A to E, impact 1 to 5.
Controls mapped
Source: process map, risk register, controls by team, incident log at 30 Sep 2026
We start from the procedures you already have and draw them as lines and stops.
To the risks in your register, the controls that hold them and the partners it depends on.
The map is the procedure, so there is one thing to update, not two.
A map people use every day does.
A failed control turns its activity red on the map. An incident appears on every process its control touches. In March 2026 the FCA found some firms lacked owners or target dates for remediation actions. Here each action shows its owner and date.
The large loss committee appears inside the reserving flow, not in a separate governance chart.
A coverholder bound 23 risks outside its territory, found in an audit four months late. The same failed control shows on the process map, the incident log and the controls board.
What Halden is doing: the Head of Delegated Authority owns ACT-038, to remediate the breaches the failed coverholder audit let through.
Tell us which process gives you the most trouble. We will show you how it would look on the map, using Halden as the starting point.
One email a month, plus an alert for each new report.
The first "This month at Halden" arrives on the first Tuesday of the month.
Built by Context Visualised, in London since 2016, Lloyd's Lab Cohort 2. Founded by Waleed Sarwar, former interim Head of Risk at Liberty Mutual, Markel and Bupa, who worked on Solvency II policy at the Bank of England.