Business case and benefits
- Claims director
- A · Accountable
- Product owner
- R · Responsible
- Solutions architect
- C · Consulted
- Technical PM
- C · Consulted
- Engineers
- I · Informed
- Compliance & DPO
- C · Consulted
- Security
- I · Informed
Every claim read, sorted and routed within minutes. Simple claims ready for one-click approval, complex ones flagged early, and people making every decision that matters.
At a glance
An illustrative scenario. The numbers are typical examples, not a client case study. The cloud services and UK rules were checked on 9 November 2026.
Claims arrive in every shape: emails with photos attached, PDFs of handwritten forms, web forms with free-text descriptions, and broker submissions in their own formats. Before anyone makes a decision, a handler has to read it all, work out what kind of claim it is, find the policy, and re-key the details into the claims system.
In a typical mid-sized insurer, that reading and re-keying takes around 40% of a handler's day. Simple claims, such as a lost phone or a cancelled flight, wait in the same queue as complex ones. Signs of fraud or of a vulnerable customer are often spotted late, after the money has gone or the customer has already had a poor experience.
Claims handling is also under the regulator's spotlight. The FCA's 2026 insurance priorities put claims handling at the top of its supervisory focus. Following the Which? super-complaint, it is reviewing claims service quality in home and travel insurance during 2026. Any change to how claims are handled has to show it improves customer outcomes, not just costs.
Agree these, and measure the baseline, before anything is built. Example targets are typical, not promises.
How long a customer waits before anyone acts on their claim.
ExampleFrom 2 days to under 2 hours
Time moved from copying details to making decisions.
ExampleDown by half
The share of simple claims a handler approves without editing.
Example60–70% of simple claims
How often handlers disagree with the AI's recommendation. Very high means it isn't helping; near zero can mean people have stopped checking.
ExampleStable, and reviewed weekly
Money paid that shouldn't have been, including fraud caught late.
ExampleMeasured against last year
Complaints, claim acceptance by product, and satisfaction, split out for vulnerable customers.
ExampleNo group worse off
Cross-sector rules are on the UK regulation map.
There's no AI-specific rulebook. The FCA applies the Duty to AI like any other change. Every recommendation carries a plain-English reason, outcomes are monitored by customer group, and the firm can explain any decision if challenged.
Claims must be handled promptly and fairly. The AI can speed claims up and route them, but it never rejects a claim on its own. Every decline is a person's decision.
Signs of vulnerability in the claim text, such as bereavement, illness or financial difficulty, are flagged to a trained handler, never acted on automatically.
Claims often contain health and other special category data. That means a DPIA before the pilot, collecting only what's needed, processing in UK regions, a clear retention period, and a contract that stops providers training their models on your data.
Since 5 February 2026, the strict limit on solely automated significant decisions applies mainly where special category data is involved, and claims often include health data. Every other automated decision needs safeguards: telling people, letting them challenge it, and a person who can step in. A person on every adverse decision keeps the design clearly within the rules.
Showing AWSAzuresovereign / on-prem services. Switch with the toggle; every diagram and table on this page follows it.
01Channels
02Intake
03Intelligence
04Orchestration
05Systems of record
06People
| Layer | AWS | Azure | Sovereign / on-prem |
|---|---|---|---|
| Intake: email, forms, files | Amazon SES, API Gateway, S3 | Logic Apps connectors, API Management, Blob Storage | Your mail server, Kong, Ceph or IONOS S3 Object Storage |
| Reading documentsTest on real phone photos of handwritten forms, not clean PDFs. | Amazon Textract | Azure Content Understanding (includes Document Intelligence) | Open-source parsing (e.g. Docling) plus an open-weight vision model |
| Reasoning and summariesAWS and Azure both offer a choice of models, including Claude. On-prem and sovereign options run open-weight models. | Amazon Bedrock | Microsoft Foundry | Open-weight models served with vLLM on your own GPUs, or IONOS AI Model Hub |
| Policy knowledge (retrieval)So the agent answers from your policy wordings, not from general knowledge. | Bedrock Knowledge Bases | Foundry IQ, built on Azure AI Search | OpenSearch, or PostgreSQL with pgvector |
| Agent runtimeThe original Bedrock Agents closed to new customers on 30 July 2026; new builds use AgentCore. | Amazon Bedrock AgentCore | Foundry Agent Service | An open-source agent framework (e.g. LangGraph) on Kubernetes |
| Workflow | AWS Step Functions | Logic Apps or Durable Functions | Temporal, or n8n |
| Middleware and events | Amazon EventBridge, SQS | Event Grid, Service Bus | Apache Kafka or RabbitMQ |
| Link to the core claims systemReuse the integration layer you have. Don't buy a new one for this. | API Gateway, plus your existing integration platform if you have one | API Management, plus your existing integration platform if you have one | Kong or your existing API gateway, plus your existing integration platform if you have one |
| Human reviewPeople review where they already work, not in a new screen. | In the handlers' existing claims workbench | In the handlers' existing claims workbench | In the handlers' existing claims workbench |
| Guardrails | Bedrock Guardrails | Foundry guardrails (Azure AI Content Safety) | Open-source guardrails (e.g. NeMo Guardrails, Llama Guard) |
| Identity, keys, data protection | IAM Identity Center, KMS, Macie | Entra ID, Key Vault, Purview | Keycloak or your existing Active Directory; OpenBao or HashiCorp Vault; an HSM |
| Monitoring and auditLog every recommendation and every human decision, with the reason. | CloudWatch, CloudTrail | Azure Monitor, Log Analytics | Prometheus, Grafana, OpenTelemetry |
| UK data residencyIONOS AI Model Hub runs in German data centres: EU, not UK, residency. | eu-west-2 (London) | UK South / UK West | Your own UK data centre, or a UK or EU provider |
On a phone, the table shows the platform you pick. Sovereign / on-prem means open, portable components you can run in your own data centre or with a UK or European provider; IONOS is shown as one example, and others exist. What sovereign cloud means →
Many organisations keep core systems and sensitive data on their own servers. This is how the same design works across both.
Stays on-prem
The core claims system, the policy admin system and the fraud engine stay where they are. Many insurers still run these on their own servers, and nothing in this design needs them to move.
Uses cloud AI
Document reading, the policy knowledge index and the triage agent can run in AWS or Azure, or on your own GPUs with open-weight models if claim data must not leave your estate.
How they connect
A private link (AWS Direct Connect or Azure ExpressRoute) and the API layer. Only the fields the AI needs are sent, and results come back as events onto your queue.
If the link drops
Claims keep arriving and queue safely on your side. Handlers work them exactly as they did before the AI, and the backlog is triaged when the link returns.
What each agent may do through its tools, what it may not, and where a person signs off. The limits are enforced by the platform, not the prompt.
Triage agent
Where a person signs offA person signs off every payment, every decline, and every claim flagged as suspicious or vulnerable. The agent's permissions are enforced by the platform's identity and policy controls, not by instructions in a prompt.
The core claims system is reached only through an API layer, never directly. If you already run an integration platform, the AI uses it like any other system does.
Events decouple the AI from the systems of record. Each new claim becomes a message on a queue. If the claims system is slow or down, claims wait safely in the queue, and nothing is lost or processed twice. Every message carries an ID, so a retry never creates a duplicate claim.
The AI can be switched off without stopping the business. If it's paused, claims flow straight to handlers, exactly as they did before.
Map today's process, measure the baseline, check data access, and pick the first claim type.
Gate · must be true to passBaseline measures agreed, data access confirmed, DPIA started, and compliance involved.
One claim type, in shadow mode: the AI recommends, handlers work as normal, and the two are compared.
Gate · must be true to passAccuracy and override rate within agreed limits, no customer group worse off, and compliance sign-off.
Recommendations go live for the first claim type, with monitoring, support and a rollback plan.
Gate · must be true to passMonitoring, support model, rollback plan and handler training in place.
Add claim types one at a time, then reuse the pattern for complaints and underwriting referrals.
Gate · must be true to passEach new claim type passes the same pilot gate.
| Activity | Claims director | Product owner | Solutions architectI can fill this | Technical PMI can fill this | EngineersI can fill this | Compliance & DPO | SecurityI can fill this |
|---|---|---|---|---|---|---|---|
| Business case and benefits | Accountable | Responsible | Consulted | Consulted | Informed | Consulted | Informed |
| Target architecture | Informed | Consulted | Accountable and Responsible | Consulted | Consulted | Consulted | Consulted |
| DPIA and Consumer Duty review | Accountable | Consulted | Consulted | Informed | Informed | Responsible | Consulted |
| Build and integration | Informed | Consulted | Accountable | Responsible | Responsible | Informed | Consulted |
| Accuracy testing on real claims | Informed | Accountable | Responsible | Consulted | Responsible | Consulted | Informed |
| Go-live decision | Accountable | Responsible | Consulted | Responsible | Informed | Consulted | Consulted |
| Run, monitor and improve | Informed | Accountable | Consulted | Consulted | Responsible | Consulted | Consulted |
R ResponsibleA AccountableC ConsultedI Informed· not involved
Option A
If there's no architect on the programme, I'd own the design end to end: the target architecture, the integration with your claims system, and the gates. I'd report to your programme board.
Option B
If your partner or your own team already has an architect, I'd take on the document AI, the agent and the claims-system integration under their lead, and give them a second senior opinion on the rest.
Goes wrong
The demo used clean PDFs. Real claims are phone photos of handwritten forms.
How the design avoids it
Pilot on last month's real claims, every channel, not a curated sample.
Goes wrong
The AI talks to the claims system directly, so one outage stops everything.
How the design avoids it
An API layer and a queue in between, and a switch that sends claims straight to handlers.
Goes wrong
Nobody owns the prompts or policy documents, so quality drifts quietly.
How the design avoids it
A named owner for each, change control, and a weekly sample review.
Goes wrong
Handlers don't trust it and re-check everything, so nothing is saved.
How the design avoids it
Shadow mode first, override reasons fed back, and handlers involved in setting the rules.
Goes wrong
Compliance sees it a week before go-live.
How the design avoids it
DPIA and Consumer Duty review at the discovery gate, not the production gate.
Changes already announced or under way that affect this design. More in the UK horizon scan.
The FCA has been analysing claims service quality in home and travel insurance. Expect sharper expectations on claim acceptance, delays and communication. Build the outcome reporting now, split by product and customer group.
Regulations in force since May 2026 require the ICO to produce a statutory code. Keep the decision log, the explanations and the human review records in a form you could show the ICO.
Medium and large managed service providers come into regulation for the first time, with faster incident reporting. Expect your IT and AI suppliers to face new duties, and your contracts and supplier assurance to need updating.
The NCSC asks organisations to have a full migration plan by 2028. Claims data is sensitive and long-lived, so record which encryption the new platform uses and keep it easy to change.
Good answers are specific. Vague answers to any of these are worth following up.
Whether you need someone to lead the design or to support the architect you already have, let's talk it through.