Insurance risk managers in the UK should be trained to test an agent the way they test any control: what it may do, what evidence earned that authority, and what the record shows when it acts. Consumer Duty, the Senior Managers and Certification Regime and UK GDPR set the frame. Accountability stays with named people, not with the agent.
What does a UK insurance risk manager spend time on?
The UK market mixes large personal lines carriers, commercial insurers, life and pensions providers and a specialty market in London that writes much of its business through delegated authority. Risk managers in that last group spend a great deal of time overseeing coverholders and third-party administrators who bind risks and settle claims on the insurer's behalf.
Across the market, the second line runs the risk register and appetite framework, reviews outsourcing and operational resilience, monitors conduct and customer outcomes, supports the own-risk and solvency assessment, and reports to the board and to both the FCA and the PRA. Consumer Duty has pushed risk teams to evidence good outcomes for retail customers, not just compliant processes.
Which agent uses matter most to the risk function?
- Claims handling in personal lines, depth 3 to 4. An agent that validates and settles small home or motor claims within bounds acts at depth 3. Releasing payments is depth 4 and should be held above the insurer's own limits. The risk manager's question is whether outcomes for customers in vulnerable circumstances are as good as for everyone else.
- Delegated authority bordereaux review, depth 1 to 2. The agent reads coverholder bordereaux, checks risks bound against the binding authority's limits and drafts exceptions. A person decides what to raise with the coverholder.
- Consumer Duty outcome monitoring, depth 1. The agent reads complaint, claims and cancellation data and drafts the outcome indicators for the board report.
- Operational resilience mapping, depth 2. The agent drafts the dependencies of each important business service, including any agent the service relies on, for the risk team to confirm.
A certification run that clears no depth drops the agent to depth 1 the same day. A risk manager should know how that would affect an important business service and what the fallback is.
What must risk managers learn, and what stays with them?
Start with what risk managers should learn before working with AI agents. For a UK insurer the emphasis falls on three things.
Evidence over assurance. An agent's depth is earned from replaying it against the insurer's own claims, not configured by a vendor. The risk manager should be able to read which gates came closest to their floor and whether the replay included customers flagged as vulnerable.
The minimum chain. Every action meets five bounds at once, and the lowest wins. When a claim is held, the verdict names the bound that decided. That is what lets a risk manager tell a policy problem from a data problem.
Accountability mapping. Under SM&CR, a named senior manager is accountable for each area. Agents do not change that. The risk manager should be able to show, for each agent, which senior manager owns the outcome and which certified staff approve its held actions.
What stays with people:
- risk appetite and acceptance of residual risk;
- conclusions about whether customers received good outcomes;
- any decision to decline a claim on the grounds of misrepresentation or fraud;
- reporting to the board, the FCA and the PRA.
Which UK rules shape oversight and literacy?
The UK takes a principles-based, regulator-led approach to AI rather than a single AI law. The FCA supervises conduct and the PRA supervises insurers prudentially; both apply their existing rules to agents. Consumer Duty requires firms to deliver good outcomes for retail customers, which means an agent's decisions on claims, renewals and cancellations will be judged by their outcomes. The Senior Managers and Certification Regime fixes individual accountability, so the competence of the people who oversee agents is a regulatory matter, not only an internal one.
UK GDPR and the Data Protection Act 2018 govern policyholder data, and the ICO enforces them. Health data in life and protection products is special-category data. Where an agent's output produces a decision with legal or similarly significant effects, such as declining a claim, without a person deciding, the rules on solely automated decisions apply; our piece on UK GDPR Article 22 and AI agents covers this, and the wider UK GDPR regime sets out the rest.
Insurers writing EU business through subsidiaries will also meet the EU AI Act, which lists life and health insurance risk assessment and pricing as high-risk.
This is an explanation of the rules, not legal advice; confirm how they apply to you with counsel.
A 90-day plan for a UK insurer
Days 1 to 30. Foundations for the risk function, claims leadership and delegated authority teams. Build an inventory of agents, their depth, certificates and the senior manager accountable for each. Pryme Intelligence Academy's Foundations track is free and tested in insurance, which makes it an easy common baseline.
Days 31 to 60. Write the insurer's own limits for each agent, with particular attention to claims involving vulnerable customers. Map agents into important business services. Approvers sit the operator exam.
Days 61 to 90. Two-week practicum of logged review decisions on live claims and bordereaux exceptions. Calibrate on ten claims where vulnerability was flagged. Present the board with a page showing agents, depth, accountable senior managers, certified approvers and lapse dates. The full role map is in AI agent skills by role.
Questions people ask
Does a coverholder's agent fall under our oversight?
If it binds risks or settles claims on your behalf, its outcomes are your outcomes under Consumer Duty. Ask the coverholder for the agent's depth, certification evidence and record access, as you would for any delegated process.
Is a certified approver the same as a certified person under SM&CR?
No. The Certification Regime concerns specific regulated functions. An agent-approval certificate shows competence to review agent decisions; map it into your fitness and propriety process if you wish, but do not treat one as the other.
How should vulnerability be handled in agent bounds?
Flag vulnerability in the customer record and make it a bound: decisions for flagged customers are held for a person. The record then shows that every such decision had human review.