Property, construction and housing · Playbook 44

I've worked in this sector

Building control application processing

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.

  • Document AI
  • Agents with tools
  • Human in the loop
  • Building Safety Act 2022
  • Building Safety Regulator
  • Building Regulations 2010
  • RBI code of conduct
  • UK GDPR

At a glance

The problem
Admin officers register every application by hand, inspectors find missing documents late, and bookings and charges are chased by phone and email
Typical volume
Around 3,500 applications and notices a year, 14,000 site inspections, and a few hundred overdue charges at any time
Who's involved
The building control manager, registered building inspectors, the admin team, finance and credit control, information governance, IT, the back-office system supplier
Pilot
8–10 weeks on householder full plans and building notices, after a 3-week discovery
Platforms
AWS, Azure, or a sovereign or on-prem stack

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.

The business problem

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.

What AI changes

  • Every application and notice is read within minutes of arriving: the form, drawings, specifications, structural calculations and energy information, with the key details extracted into the back-office system.
  • Completeness is checked against the rules for that application type, and a specific request for missing documents is drafted for the admin officer to send.
  • Signs that the work may be a higher-risk building, such as height, storeys and number of homes, are flagged at once, so that work goes to the Building Safety Regulator and not into the local queue.
  • The inspector opens a prepared file: documents indexed, key values extracted and inconsistencies between documents highlighted. There is no compliance verdict. Checking compliance is the inspector's job.
  • Builders book inspections by web form, email or text, and visits are booked into the right inspector's diary against the inspection stages the inspector has set.
  • Charges are invoiced through the finance system, payments matched and approved reminders sent. Overdue accounts go to a credit control officer, who decides what happens next.

How success is measured

Agree these, and measure the baseline, before anything is built. Example targets are typical, not promises.

Time to register

Working days from receipt to registered and acknowledged, with a request sent if something is missing.

ExampleFrom 5 working days to 1

Gaps found at registration

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 time on admin

Inspector hours spent on chasing documents, bookings and payments, measured by timesheet sample.

ExampleDown by a third

Booking response

Inspection requests confirmed the same working day, and aborted visits where work wasn't ready.

ExampleSame day, aborted visits falling

Override rate

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

Aged debt

Charges unpaid after 60 days, and the time from final inspection to completion certificate.

ExampleMeasured against last year

UK regulation and controls

Cross-sector rules are on the UK regulation map.

  • MHCLGBuilding Safety Act 2022 and Building Act 1984, sections 46A and 54B (restricted activities and functions)

    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.

  • Building Safety RegulatorCode of conduct for registered building inspectors and the Operational Standards Rules

    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.

  • MHCLGBuilding Regulations 2010 and the Building (Higher-Risk Buildings Procedures) (England) Regulations 2023

    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.

  • MHCLGBuilding control charges and the Building Safety Levy

    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.

  • ICOUK GDPR, the Data Protection Act 2018 and automated decisions

    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.

The solution

Showing AWSAzuresovereign / on-prem services. Switch with the toggle; every diagram and table on this page follows it.

Building control application processing: reference architecture
  1. 01Channels

    • National submission portal
    • Email and post (scanned)
    • Builders booking inspections
    • RBCAs giving initial notices
  2. 02Intake

    • API GatewayAPI ManagementKong, or your existing API gatewayAPI for portal feed and bookings
    • Amazon S3Blob StorageCeph, or IONOS S3 Object StorageDocument store
  3. 03Intelligence

    • Bedrock Data AutomationContent UnderstandingDocling plus an open-weight vision modelRead forms and drawings
    • AWS LambdaAzure FunctionsRules as code on KubernetesCompleteness and routing rules
    • Agent
      Bedrock AgentCoreFoundry Agent ServiceLangGraph on Kubernetes, with open-weight models via vLLMRegistration agent
    • Agent
      Bedrock AgentCoreFoundry Agent ServiceLangGraph on Kubernetes, with open-weight models via vLLMBookings and charges agent
  4. 04Orchestration

    • Step FunctionsLogic Apps / Durable FunctionsTemporalApplication workflow
    • EventBridge + SQSEvent Grid + Service BusApache Kafka or RabbitMQEvents and queues
  5. 05Systems of record

    • Building control back-office system
    • Finance and payments
    • Inspectors' diaries and site app
    • Address gazetteer and GIS
  6. 06People

    • Person
      Admin officer: registration and requests
    • Person
      Registered building inspector: every technical decision
    • Person
      Credit control officer
  • Cloud or platform service (AWSAzuresovereign / on-prem)
  • AI agent
  • A person decides
  • Your existing systems
  • Outside your organisation

Components, side by side

Building control application processing: components on AWS, Azure and a sovereign or on-prem stack
LayerAWSAzureSovereign / 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 SESAPI Management, Blob Storage, Logic Apps email connectorKong, 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 modelAzure 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 LambdaRules as code in Azure FunctionsRules as code on Kubernetes
Reasoning and draftingReads, compares and drafts requests. AWS and Azure both offer a choice of models, including Claude.Amazon BedrockMicrosoft FoundryOpen-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 AgentCoreFoundry Agent ServiceAn open-source agent framework (e.g. LangGraph) on Kubernetes
WorkflowLong-running: an application can stay open for years between commencement and completion.AWS Step FunctionsLogic Apps or Durable FunctionsTemporal, or n8n
Middleware and eventsAmazon EventBridge, SQSEvent Grid, Service BusApache 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 MessagingAzure Communication ServicesYour 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 systemIn the team's existing building control back-office systemIn the team's existing building control back-office system
GuardrailsIncluding a check that no draft says work complies or fails.Bedrock GuardrailsFoundry guardrails (Azure AI Content Safety)Open-source guardrails (e.g. NeMo Guardrails, Llama Guard)
Identity, keys, data protectionIAM Identity Center, KMS, MacieEntra ID, Key Vault, PurviewKeycloak 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, CloudTrailAzure Monitor, Log AnalyticsPrometheus, Grafana, OpenTelemetry
UK data residencyIONOS AI Model Hub runs in German data centres: EU, not UK, residency.eu-west-2 (London)UK South / UK WestYour 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 →

Hybrid and on-prem

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.

The agents

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

May do

  • Read the application or notice and every attached document
  • Run the completeness rules for that application type and list what is missing, each item with the rule it comes from
  • Extract the site address, description, applicant, agent, number of homes, height and storeys into the back-office system as a draft
  • Match the address to the gazetteer and flag signs of a higher-risk building or levy-liable work
  • Index the documents and highlight inconsistencies between them for the inspector
  • Draft the request for missing documents for the admin officer

May not do

  • Say whether any work complies with the building regulations
  • Pass, reject or add conditions to plans
  • Accept, reject or cancel an initial notice
  • Set or change the inspection stages
  • Send anything to the applicant or agent
  • Change the fee or the charge on the account

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

May do

  • Read inspection requests from the web form, email or text
  • Book visits into the inspector's diary for the stages the inspector has set, and rebook when work isn't ready
  • Send booking confirmations and approved payment reminders from agreed templates
  • Raise invoices through the finance system and match payments to accounts
  • Ask the collecting authority's records for the levy position and attach it to the completion task
  • Flag overdue accounts to the credit control officer, with the history

May not do

  • Decide what stages to inspect, or record any inspection result
  • Waive, refund, discount or write off a charge
  • Refer an account to debt recovery, or stop any service for non-payment
  • Issue or hold back a completion certificate
  • Send any message outside the approved templates

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.

Middleware and integration

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.

Process and people

  • A named owner for the completeness rules, the higher-risk building indicators and the charges configuration, with change control and start dates.
  • A written line between admin checks and restricted activities, agreed with the lead inspector and the technical manager, and reflected in the agents' permissions.
  • An exception queue for documents the AI can't read and for anything that might be a higher-risk building, with a clear owner.
  • A weekly review of a sample of registrations, requests and bookings, including applications later found incomplete by an inspector.
  • Plain-English request and reminder templates agreed with officers and tested with local agents and builders.
  • Admin officers, inspectors and credit control trained before go-live, including what the AI can't see on a drawing.
  • An Algorithmic Transparency Recording Standard record published before go-live (voluntary for councils, and good practice).

Delivery plan

  1. 3 weeks

    Discovery

    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.

  2. Gate · must be true to passBaseline agreed, rules signed off by the building control manager, restricted-activity line agreed, DPIA started.

  3. 6–8 weeks

    Pilot

    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.

  4. Gate · must be true to passAccuracy within agreed limits, no compliance language in any draft, no duplicate bookings or reminders, manager content.

  5. 4–6 weeks

    Production

    Registration checks, requests, bookings and reminders go live for householder work, with monitoring, support and a rollback plan.

  6. Gate · must be true to passMonitoring, support model, rollback plan, training and transparency record in place.

  7. Ongoing

    Scale

    Add larger schemes, initial notices and regularisations, then the completion pack, and reuse the pattern for planning validation.

  8. Gate · must be true to passEach new application type passes the same pilot gate.

Roles and RACI

Who is responsible, accountable, consulted and informed, by activity
ActivityBuilding control managerProduct ownerSolutions architectI can fill thisTechnical PMI can fill thisEngineersI can fill thisInformation governanceLead RBI
Business case and benefitsAccountableResponsibleConsultedConsultedInformedConsultedConsulted
Completeness rules and restricted-activity lineAccountableResponsibleConsultedInformedResponsibleInformedResponsible
Target architectureInformedConsultedAccountable and ResponsibleConsultedConsultedConsultedConsulted
DPIA and transparency recordAccountableConsultedConsultedInformedInformedResponsibleInformed
Build and integrationInformedConsultedAccountableResponsibleResponsibleInformedConsulted
Accuracy testing on real applicationsInformedAccountableResponsibleConsultedResponsibleInformedResponsible
Go-live decisionAccountableResponsibleConsultedResponsibleInformedConsultedConsulted
Run, monitor and improveInformedAccountableConsultedConsultedResponsibleConsultedConsulted

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

Completeness rules and restricted-activity line

Building control manager
A · Accountable
Product owner
R · Responsible
Solutions architect
C · Consulted
Technical PM
I · Informed
Engineers
R · Responsible
Information governance
I · Informed
Lead RBI
R · Responsible

Target architecture

Building control manager
I · Informed
Product owner
C · Consulted
Solutions architect
A/R · Accountable and Responsible
Technical PM
C · Consulted
Engineers
C · Consulted
Information governance
C · Consulted
Lead RBI
C · Consulted

DPIA and transparency record

Building control manager
A · Accountable
Product owner
C · Consulted
Solutions architect
C · Consulted
Technical PM
I · Informed
Engineers
I · Informed
Information governance
R · Responsible
Lead RBI
I · Informed

Build and integration

Building control manager
I · Informed
Product owner
C · Consulted
Solutions architect
A · Accountable
Technical PM
R · Responsible
Engineers
R · Responsible
Information governance
I · Informed
Lead RBI
C · Consulted

Accuracy testing on real applications

Building control manager
I · Informed
Product owner
A · Accountable
Solutions architect
R · Responsible
Technical PM
C · Consulted
Engineers
R · Responsible
Information governance
I · Informed
Lead RBI
R · Responsible

Go-live decision

Building control manager
A · Accountable
Product owner
R · Responsible
Solutions architect
C · Consulted
Technical PM
R · Responsible
Engineers
I · Informed
Information governance
C · Consulted
Lead RBI
C · Consulted

Run, monitor and improve

Building control manager
I · Informed
Product owner
A · Accountable
Solutions architect
C · Consulted
Technical PM
C · Consulted
Engineers
R · Responsible
Information governance
C · Consulted
Lead RBI
C · Consulted

R ResponsibleA AccountableC ConsultedI Informed· not involved

Where I'd fit

Option A

Lead the architecture

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

Support your architect

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.

Where this goes wrong

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

On the horizon

Changes already announced or under way that affect this design. More in the UK horizon scan.

  1. 2026–2027
    Reform after the Building Control Independent Panel

    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.

  2. Expected soon
    A Digital Building Control Roadmap

    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.

  3. Decision awaited
    Plan approval for new homes

    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.

  4. From 24 March 2027
    Revised building control charges

    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.

  5. From 2028
    The Single Construction Regulator

    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.

Questions to ask your partner or vendor

Good answers are specific. Vague answers to any of these are worth following up.

Copy them into your next supplier meeting

  1. Where exactly does the AI's check stop and an inspector's restricted activity begin, and how is that enforced?
  2. How will we measure accuracy on our own applications, including scanned forms and hand-drawn plans?
  3. What happens if the AI misses a higher-risk building?
  4. Which actions can the agents take without a person, and can they ever send a message outside an approved template?
  5. Where are applications processed and stored, and is the data used to train anyone's model?
  6. Who owns the rules, templates and prompts after you leave, and how do we update them when the regulations change?

Planning something like this?

Whether you need someone to lead the design or to support the architect you already have, let's talk it through.

Sam Naseem
Sam NaseemBirmingham, UK · UK & Europe
Available now