Business case and benefits
- Head of service
- A · Accountable
- Product owner
- R · Responsible
- Solutions architect
- C · Consulted
- Technical PM
- C · Consulted
- Engineers
- I · Informed
- DPO & equalities
- C · Consulted
- Counter fraud lead
- C · Consulted
Every application read, checked against the scheme rules and made ready for an officer within a day. Missing evidence asked for early, fraud and error checks done fairly, and an officer deciding every award and every refusal.
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.
People applying for local support send what they have: online forms with free-text answers, phone photos of payslips and bank statements, tenancy agreements, letters about other benefits, and sometimes a GP letter about a disability. Businesses and community groups applying for grants send accounts, quotes, constitutions and project plans. Before an officer can assess anything, they have to read it all, work out what is missing, chase it, and re-key the figures into the benefits or grants system.
In a typical council, that reading and chasing takes more of an officer's day than the assessment itself. Applications wait days for a first look. When a new grant scheme opens, hundreds arrive in a week and the queue grows faster than the team can read. Applicants who struggle with forms, often the people the scheme is for, are the ones most likely to submit incomplete evidence and wait longest.
The decisions matter, and so does public money. A wrong refusal can leave a household in arrears or a small charity without its project. A wrong award is money the council can't spend elsewhere, and fraud against grant schemes is a known risk. The council has to treat people fairly, show it has thought about equality, and be able to explain any decision if it is challenged, while spending less time on admin and more on the cases that need judgement.
Agree these, and measure the baseline, before anything is built. Example targets are typical, not promises.
How long an applicant waits before anyone acts on their application.
ExampleFrom 5 working days to under 1
The share of applications needing more evidence, and how many rounds it takes.
ExampleOne round, not three
Time moved from reading and re-keying to assessment and judgement.
ExampleDown by 30–40%
How often officers change the draft assessment. Very high means it isn't helping; near zero can mean people have stopped checking.
ExampleStable, and reviewed weekly
Overpayments and wrong awards found after payment, and the share of fraud flags that turn out to be genuine.
ExampleFewer wrong awards, no rise in false flags
Award rates, refusal rates and flag rates by protected characteristic and by channel, where the data allows.
ExampleNo group worse off
Cross-sector rules are on the UK regulation map.
Since 5 February 2026, the strict limit on solely automated significant decisions applies mainly where special category data is involved, and applications often include health or disability evidence. Every other significant automated decision needs safeguards: telling people, letting them make representations and contest it, and human intervention. An officer making every award and refusal keeps the design clearly within the rules.
The lawful basis is the council's public task, not consent. That means a DPIA before the pilot, using evidence only for the scheme it was given for unless the law allows more, processing in the UK, a clear retention period, and a contract that stops providers training their models on applicants' data.
The council must have due regard to equality when it designs and runs the service. Record an equality impact assessment before the pilot, test outcomes and fraud flags by group, and keep a non-digital route for people who can't use the online form.
The ATRS is mandatory for central government departments and arm's-length bodies that serve the public, for tools that significantly influence decisions about people. Councils aren't yet required to use it, but many publish records voluntarily. Publish one before go-live: it's the simplest way to show residents what the tool does and doesn't do.
The counter fraud standard expects fraud risk to be assessed and managed. The grants standard requires a proportionate fraud risk assessment and due diligence for every central government scheme. Councils use the same approach as good practice. Checks run on every application, flags are explained, and a trained person decides what happens next.
Royal Assent on 2 December 2025, with most provisions commenced in stages during 2026. It gives the Public Sector Fraud Authority powers to investigate and recover fraud against public bodies outside tax and social security, with codes of practice and independent oversight. Its benefits measures keep a member of staff involved in every entitlement decision. Design the same way: data can raise a question, but a person answers it.
A grant to a business or a trading charity can be a subsidy. The scheme's subsidy basis, any cumulative allowance per enterprise, and the duty to publish larger awards on the subsidy database (currently those over £100,000) all become rules in code and fields in the case record.
Public money must be spent with regularity, propriety and value for money. Keep a clear trail from each award to the scheme rules and the evidence, and keep the approval limits in the platform's permissions, not in a prompt.
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: forms, uploads, scanned postKeep the paper and phone routes. Scan post into the same flow so nobody is disadvantaged by the channel they use. | API Gateway, S3, Amazon SES | API Management, Blob Storage, Logic Apps email connector | Kong, Ceph or IONOS S3 Object Storage, your mail server |
| Reading evidenceTest on real phone photos of payslips and bank statements, not clean PDFs. Every extracted figure links back to the page it came from. | Amazon Textract, or Bedrock Data Automation | Azure Content Understanding (includes Document Intelligence) | Open-source parsing (e.g. Docling) plus an open-weight vision model |
| Eligibility rulesThe model never decides eligibility. The scheme owner signs off the rules and a set of worked examples, and every change is tested against them. | Rules as code in AWS Lambda, versioned and tested | Rules as code in Azure Functions, versioned and tested | A rules engine (e.g. OpenFisca or Drools) on Kubernetes |
| Reasoning and draftingUsed to read, summarise and draft, not to decide. AWS and Azure both offer a choice of models, including Claude. | Amazon Bedrock | Microsoft Foundry | Open-weight models served with vLLM on your own GPUs, or IONOS AI Model Hub |
| Scheme guidance (retrieval)So drafts quote the council's own scheme policy and guidance, at the version in force on the date of the application. | Bedrock Knowledge Bases | Foundry IQ, built on Azure AI Search | OpenSearch, or PostgreSQL with pgvector |
| Agent runtimeNew builds use AgentCore; the original Bedrock Agents closed to new customers on 30 July 2026. | Amazon Bedrock AgentCore | Foundry Agent Service | An open-source agent framework (e.g. LangGraph) on Kubernetes |
| WorkflowLong-running: an application can wait weeks for evidence without losing its place. | 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 |
| Data matchingFor the council's own matching rules, alongside national exercises it already takes part in. Results are leads for a person, never decisions. | AWS Glue and Amazon Athena | Microsoft Fabric | Apache Spark or PostgreSQL on Kubernetes |
| Human reviewOfficers review and decide where they already work, not in a new screen. | In the officers' existing benefits or grants system | In the officers' existing benefits or grants system | In the officers' existing benefits or grants system |
| Guardrails | Bedrock Guardrails | Foundry guardrails (Azure AI Content Safety) | Open-source guardrails (e.g. NeMo Guardrails, Llama Guard) |
| Identity, keys, data protectionApproval limits by role (who can award what) are enforced here. | 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 extraction, rule result, draft and officer 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 revenues and benefits system, the grants system and the document store stay where they are, whether in the council's own data centre or hosted by its supplier. Nothing in this design needs them to move.
Uses cloud AI
Evidence reading, scheme guidance retrieval and the two agents can run in a UK cloud region, or on the council's own GPUs with open-weight models if evidence must not leave its estate. The rules engine can run in either place.
How they connect
A private link (AWS Direct Connect or Azure ExpressRoute) or the council's existing network connection, through the API layer. Only the evidence and fields the assessment needs are sent, and results come back as events onto the council's queue.
If the link drops
Applications keep arriving and queue safely on the council's side. Officers assess them exactly as they did before, and the backlog is read and checked 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.
Assessment agent
Where a person signs offAn officer decides every award and every refusal, and sends every evidence request. Refusals and awards above a set value go to a senior officer. The agent's permissions are enforced by the platform's identity and policy controls, not by instructions in a prompt.
Fraud and error check agent
Where a person signs offA trained counter fraud officer reviews every flag and decides what happens next. A flag is a question, not a finding, and the assessment officer still makes the award decision.
The benefits and grants systems stay the record. The AI reaches them only through their published APIs or the integration layer the council already runs, never directly into the database.
Events decouple the AI from the systems of record. Each new application or piece of evidence becomes a message on a queue. If the benefits system is slow or down for its overnight run, work waits safely, nothing is lost, and every message carries an ID so a retry never creates a duplicate case.
The rules engine is its own service with its own tests. When a scheme changes in April, the new rules go live on a date, and applications are assessed against the rules in force when they were made.
The AI can be switched off without stopping the service. If it's paused, applications go straight to officers, exactly as they did before.
Map today's process for each scheme, measure the baseline, check data access, write down the rules, and pick the first scheme.
Gate · must be true to passBaseline agreed, rules and worked examples signed off, DPIA and equality impact assessment started, counter fraud and finance involved.
One scheme, in shadow mode: the AI drafts, officers work as normal, and the two are compared.
Gate · must be true to passExtraction accuracy and rule results within agreed limits, no group worse off, fraud flags explainable, DPO and section 151 officer content.
Drafts go live for the first scheme, with monitoring, support, a rollback plan and the ATRS record published.
Gate · must be true to passMonitoring, support model, rollback plan, officer training and ATRS record in place.
Add schemes one at a time, starting with the next grant round, and reuse the rules engine and evidence reading.
Gate · must be true to passEach new scheme passes the same pilot gate, with its own rules sign-off.
| Activity | Head of service | Product owner | Solutions architectI can fill this | Technical PMI can fill this | EngineersI can fill this | DPO & equalities | Counter fraud lead |
|---|---|---|---|---|---|---|---|
| Business case and benefits | Accountable | Responsible | Consulted | Consulted | Informed | Consulted | Consulted |
| Scheme rules and worked examples | Accountable | Responsible | Consulted | Informed | Responsible | Consulted | Consulted |
| Target architecture | Informed | Consulted | Accountable and Responsible | Consulted | Consulted | Consulted | Consulted |
| DPIA, equality impact and ATRS record | Accountable | Consulted | Consulted | Informed | Informed | Responsible | Consulted |
| Build and integration | Informed | Consulted | Accountable | Responsible | Responsible | Informed | Informed |
| Accuracy and fairness testing on real applications | Informed | Accountable | Responsible | Consulted | Responsible | Consulted | Consulted |
| 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 rules engine, the evidence reading, the integration with your benefits and grants systems, and the gates. The DPIA, the equality work and the ATRS record would sit in the plan from the start, not be added before go-live. 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 rules as code, the agents and the integration with your systems of record under their lead, and give them a second senior opinion on the rest, especially where the AI stops and an officer starts.
Goes wrong
The model is asked whether someone is eligible, and gives a different answer on a different day.
How the design avoids it
Eligibility runs as tested code from signed-off rules. The model reads and drafts; it never decides.
Goes wrong
A data match is treated as proof, and a genuine applicant is refused or left waiting.
How the design avoids it
Every flag goes to a trained person with the evidence behind it. No refusal, suspension or delay happens because of a flag alone.
Goes wrong
The online route works well, so the phone and paper routes are quietly run down.
How the design avoids it
Keep every channel feeding the same flow, and report outcomes by channel as well as by group.
Goes wrong
A new grant scheme opens with rules nobody has written down precisely.
How the design avoids it
Write the rules and worked examples before the scheme opens, and test the code against them.
Goes wrong
Information governance and equalities see it a week before go-live.
How the design avoids it
DPIA, equality impact assessment and ATRS record at the discovery gate, not the production gate.
Changes already announced or under way that affect this design. More in the UK horizon scan.
Regulations in force since May 2026 require the ICO to produce a statutory code. Keep the decision log, the explanations and the officer review records in a form you could show the ICO.
The Public Sector Fraud Authority's new powers and codes of practice came into force in stages during 2026, with independent oversight and published reports. Expect closer scrutiny of how public bodies find and act on fraud and error. Keep every flag, its evidence and the officer's decision on record.
The government has said it intends to extend the mandatory standard across the wider public sector over time. Publishing a record now means the council is ready if the requirement reaches it.
Most two-tier areas are being replaced by new unitary councils, with most vesting days in April 2028. Schemes, rules and systems will be merged. Keep each council's scheme rules as separate, versioned code so they can be compared and combined, not untangled.
Medium and large managed service providers come into regulation for the first time. Expect your IT and AI suppliers to face new duties, and your contracts and supplier assurance to need updating.
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.