Business case and benefits
- Building control manager
- A · Accountable
- Product owner
- R · Responsible
- Solutions architect
- C · Consulted
- Technical PM
- C · Consulted
- Engineers
- I · Informed
- Information governance
- C · Consulted
- Lead RBI
- C · Consulted
Every application and notice registered within a day, gaps found before an inspector opens the file, inspections booked and charges chased without phone tag. A registered building inspector makes every technical decision.
At a glance
An illustrative scenario. Linked to a real, anonymised case study below; the numbers here are still typical examples. The cloud services and UK rules were checked on 9 November 2026.
A local authority building control team receives work in several shapes: full plans applications, building notices, regularisation applications, competent person scheme notifications, and initial notices from registered building control approvers. Each arrives through the national submission portal, by email, or on paper. An admin officer registers it, checks the form, the fee, the site address, the drawings and the supporting documents, and works out whether anything is missing before an inspector sees it.
Inspector time is the scarce resource, and the law protects how it is used. Since the Building Safety Act reforms, checking plans for compliance with the building regulations, carrying out inspections and scheduling the stages for inspection are restricted activities that only a registered building inspector of the right class may do. Passing or rejecting plans, issuing completion certificates and giving enforcement notices are restricted functions that need an inspector's advice. So the useful job for AI is the admin around the inspector, not the inspector's judgement. In our example team, around a third of full plans applications are missing something on arrival, and inspectors often find the gap only when they open the file.
Then comes the long tail. Builders ring or email to book inspections, often the day before. Visits are rebooked when work isn't ready. Charges are invoiced, chased and reconciled by hand. Since 1 October 2026, the Building Safety Levy applies to many new residential developments, and the levy position has to be checked with the collecting authority before a completion certificate is issued. Every hand-off is a chance for delay, and none of it is a building safety decision.
Agree these, and measure the baseline, before anything is built. Example targets are typical, not promises.
Working days from receipt to registered and acknowledged, with a request sent if something is missing.
ExampleFrom 5 working days to 1
The share of missing documents found by the registration check rather than by the inspector at plan check.
ExampleMost gaps found on day one
Inspector hours spent on chasing documents, bookings and payments, measured by timesheet sample.
ExampleDown by a third
Inspection requests confirmed the same working day, and aborted visits where work wasn't ready.
ExampleSame day, aborted visits falling
How often admin officers change a completeness finding or a draft request. Very high means it isn't helping; near zero can mean people have stopped checking.
ExampleStable, and reviewed weekly
Charges unpaid after 60 days, and the time from final inspection to completion certificate.
ExampleMeasured against last year
Cross-sector rules are on the UK regulation map.
Under the Building (Restricted Activities and Functions) (England) Regulations 2023, checking plans for compliance, carrying out inspections and scheduling inspection stages may only be done by a registered building inspector (RBI). Determining applications, completion certificates and enforcement notices need an RBI's advice. The AI checks completeness and extracts data. It never says whether work complies, never sets inspection stages, and never drafts a decision on plans. This playbook covers England; Wales runs its own building control regime.
RBIs work only within their registered class and follow the BSR's code of conduct. Building control bodies must meet the Operational Standards Rules and submit monitoring data to the BSR, which has been a standalone body under MHCLG since 27 January 2026. Every task is logged with who did it, so the body can show that restricted work was done by the right person.
Each route (full plans, building notice, regularisation, initial notice) has its own requirements and statutory deadlines. These live as dated rules in code, not in a prompt. Building control for higher-risk buildings (at least 18 metres or seven storeys, with at least two homes, plus hospitals and care homes in design and construction) sits with the BSR, so any sign of one is routed to a person straight away.
Councils set charges to recover their costs as far as possible. The government's response on charges reform (updated 16 October 2026) widens what can be charged for. The Building Safety Levy has applied since 1 October 2026 for in-scope residential work, and building control bodies check with the collecting authority before a completion certificate is issued. Charges and levy rules are configuration with dates, and chasing money never holds up a safety decision.
Applications contain names, addresses and sometimes health information, for example for disabled adaptations. That means a DPIA, processing in the UK, a clear retention period, and a contract that stops providers training their models on your data. Since 5 February 2026, every significant automated decision needs safeguards. Here a person makes every decision about an application or an account.
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: portal feed, email, scanned post, booking requestsPick work up from the back-office system once it arrives, rather than building another front door. | API Gateway, S3, Amazon SES | API Management, Blob Storage, Logic Apps email connector | Kong, Ceph or IONOS S3 Object Storage, your mail server |
| Reading forms and drawingsIn London, Bedrock Data Automation now processes requests in London only; confirm this again at build time, or use Textract and an in-region model. Test on real householder drawings and scanned forms. | Bedrock Data Automation, or Amazon Textract plus a Bedrock vision model | Azure Content Understanding (includes Document Intelligence) | Open-source parsing (e.g. Docling) plus an open-weight vision model |
| Completeness and routing rulesWhat each application type needs, the higher-risk building indicators and the levy flags, as tested code with a version and a start date. The model doesn't decide what is required. | Rules as code in AWS Lambda | Rules as code in Azure Functions | Rules as code on Kubernetes |
| Reasoning and draftingReads, compares and drafts requests. 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 |
| 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 stay open for years between commencement and completion. | 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 |
| Messages to applicants and buildersBooking confirmations and payment reminders only, from approved templates, logged against the application. | Amazon SES, AWS End User Messaging | Azure Communication Services | Your existing mail server and SMS gateway |
| Human reviewOfficers and inspectors review where they already work, including the inspectors' site app. | In the team's existing building control back-office system | In the team's existing building control back-office system | In the team's existing building control back-office system |
| GuardrailsIncluding a check that no draft says work complies or fails. | 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 check, draft, booking and reminder, and who approved it. This feeds the Operational Standards Rules evidence. | 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 building control back-office system, the finance system, the document store and the address gazetteer stay where they are, whether in the council's data centre or hosted by a supplier. Nothing in this design needs them to move.
Uses cloud AI
Reading documents and the two agents can run in a UK cloud region, or on the council's own GPUs with open-weight models. The completeness rules are plain code and can run next to the back-office system on-prem.
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 documents and fields for the case in hand are sent, and results come back as events onto the council's queue.
If the link drops
Applications keep arriving in the back-office system and builders can still phone. The admin team registers by hand, and queued work is checked when the link returns. Nothing in the safety chain depends on the link.
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.
Registration agent
Where a person signs offThe admin officer approves every registration and sends every request. A registered building inspector of the right class checks compliance and gives every decision or advice the law reserves to them. A person confirms where any possible higher-risk building goes. The agent's permissions are enforced by the platform's identity and policy controls, not by instructions in a prompt.
Bookings and charges agent
Where a person signs offInspectors own their inspection plans and every site judgement. The credit control officer decides every escalation, waiver and write-off. The manager approves the templates. The agent's permissions are enforced by the platform's identity and policy controls, not by instructions in a prompt.
The building control back-office system stays the record. Applications, notices, inspections and certificates live there. The AI reads and writes through the system's API or the integration layer the council already runs, never directly to its database.
Events decouple the AI from the systems of record. A new application, a new document, a booking request or a payment becomes a message on a queue. If the back-office or finance system is down, work waits safely, and every message carries an ID so a retry never books a visit or sends a reminder twice.
Payments are reconciled before every reminder. If the finance system hasn't confirmed an account's position that day, no reminder goes out.
The AI can be switched off without stopping the service. If it's paused, applications go to the admin team and bookings to the phone line, exactly as before.
Map today's process from receipt to completion certificate, measure the baseline, write the completeness rules, agree the restricted-activity line with the lead inspector, and check back-office and finance access.
Gate · must be true to passBaseline agreed, rules signed off by the building control manager, restricted-activity line agreed, DPIA started.
Householder full plans and building notices in shadow mode: the AI registers and drafts, officers work as normal, and the two are compared. Bookings and reminders run for one inspector's patch.
Gate · must be true to passAccuracy within agreed limits, no compliance language in any draft, no duplicate bookings or reminders, manager content.
Registration checks, requests, bookings and reminders go live for householder work, with monitoring, support and a rollback plan.
Gate · must be true to passMonitoring, support model, rollback plan, training and transparency record in place.
Add larger schemes, initial notices and regularisations, then the completion pack, and reuse the pattern for planning validation.
Gate · must be true to passEach new application type passes the same pilot gate.
| Activity | Building control manager | Product owner | Solutions architectI can fill this | Technical PMI can fill this | EngineersI can fill this | Information governance | Lead RBI |
|---|---|---|---|---|---|---|---|
| Business case and benefits | Accountable | Responsible | Consulted | Consulted | Informed | Consulted | Consulted |
| Completeness rules and restricted-activity line | Accountable | Responsible | Consulted | Informed | Responsible | Informed | Responsible |
| Target architecture | Informed | Consulted | Accountable and Responsible | Consulted | Consulted | Consulted | Consulted |
| DPIA and transparency record | Accountable | Consulted | Consulted | Informed | Informed | Responsible | Informed |
| Build and integration | Informed | Consulted | Accountable | Responsible | Responsible | Informed | Consulted |
| Accuracy testing on real applications | Informed | Accountable | Responsible | Consulted | Responsible | Informed | Responsible |
| 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 completeness rules, the document reading, the agents, the integration with your back-office and finance systems, and the gates. I've designed and built a building control management system covering scheduling, payment and credit control, so the chain from first booking to final payment is familiar ground. 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 document reading and the back-office and finance integration under their lead, and give them a second senior opinion on the rest, especially where admin checks end and an inspector's work begins.
Goes wrong
The registration check starts saying things like 'complies with Part B', and inspectors begin to lean on it.
How the design avoids it
Completeness only, written into the agent's permissions, checked by a guardrail, and sampled weekly. Compliance is the inspector's call.
Goes wrong
A higher-risk building slips into the local queue because the height was only on one drawing.
How the design avoids it
Indicators checked across every document, and any doubt goes to a person the same day.
Goes wrong
The booking agent books visits at stages nobody asked for, or misses one.
How the design avoids it
The inspector sets the stages in the back-office system; the agent only fills diary slots against them.
Goes wrong
A reminder goes to someone who paid yesterday, because the finance feed was a day behind.
How the design avoids it
Reconcile before every reminder, and send nothing when the position is unconfirmed.
Goes wrong
The demo used a tidy architect's set. Real householder submissions are phone photos and scans.
How the design avoids it
Pilot on last quarter's real applications, every channel, not a curated sample.
Changes already announced or under way that affect this design. More in the UK horizon scan.
The panel reported on 20 May 2026. The government agreed its principles, including a single system with fewer, stronger statutory bodies, and will set out fuller proposals after further work and consultation. Keep rules, templates and data per body and portable, so a merger or change of role is a configuration change.
The government has said it will publish a roadmap on efficiency, consistency and data sharing, backed by £1m for a council-led digital consortium, and is considering whether building control registers need consistent rules. Keep application data structured and exportable, not locked in documents.
A consultation that closed on 11 June 2026 proposed full plans for new homes on the council route and plans certificates on the RBCA route, not before 1 October 2026. Keep application-type rules as dated configuration.
The charges reform response widens what councils can charge for, with some changes starting in March and September 2027. Keep charges as dated configuration in the finance integration.
The government expects implementation to start from 2028, subject to legislation, with the BSR as its foundation. Keep the audit trail and monitoring data in a form a new regulator could ask for.
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.