What problem does it solve?
Permits and licences (planning and building permits, environmental permits, trade and wildlife licences, trade marks) sit on the critical path of housing, infrastructure and business. Many applications arrive incomplete or wrong, so officers spend their first pass on validation: checking documents against a checklist, chasing missing plans and fees, and searching several systems for site history, policies and constraints before they can assess the merits. Applicants often learn that something was missing only after the application has been filed; at the UK Intellectual Property Office, trade mark applications that missed essential criteria used to be rejected automatically.
Much of this is document and rules work that AI can prepare. The decision itself weighs policy, objections and local judgment, and applicants have appeal rights, so the officer has to stay the decision maker and be able to show how the AI's input was used.
How does it work?
- Help the applicant before submission. An assistant explains which permit is needed and what to submit, and pre checks (such as a trade mark similarity search) show likely problems before the application is filed.
- Validate on arrival. Documents are read and checked against a checklist tailored to the application type; missing or inconsistent items are flagged with the reason and source.
- Assemble the context. The system retrieves site history, policies and constraints from GIS and document stores and proposes which apply.
- Triage. Simple applications that meet published rules (for example a categorical exclusion in environmental review) are separated from those that need detailed assessment.
- Draft the report. The system drafts sections of the officer's report and letters to the applicant for the officer to edit.
- Decide and record. The officer decides; an audit log shows what the AI suggested and what the officer kept.
- Audience
- Employee facing
- Autonomy
- Copilot
- Adoption
- Emerging
- Channels
- Web chat, Internal tools, API and system to system
What is it worth?
Benchmarks are computed from the public deployments below: one data point per organization per KPI, with who made each claim.
| KPI | Median | Reported range | Data points | Claimed by |
|---|---|---|---|---|
| Accuracy | Too few to pool | at least 85% | 1 | 1 organization |
| Interactions handled | Not pooled | about 42 | 1 | 1 organization |
Value drivers: Speed and cycle time, Employee productivity, Customer experience, Compliance quality.
Indicative value
A local planning authority that receives 5,000 applications a year
USD 100,000 to USD 450,000
Officer time released, valued at cost per year
How this is calculated
Formula: applications * hoursSaved * hourlyCost. The low scenario uses every low input, the high scenario every high input.
| Input | Low | High | Basis |
|---|---|---|---|
| Applications received per year applications, applications per year | 5,000 | 5,000 | The reference authority. |
| Officer hours saved per application on validation, research and report drafting hoursSaved, hours per application | 0.5 | 1.5 | Editorial assumption. Leeds reports only a design aim (30% faster determination), not a measured saving; replace with your own time study. |
| Fully loaded planning officer cost per hour hourlyCost, USD per hour | 40 | 60 | Editorial assumption. Replace with your own cost. |
What it leaves out: Values officer time only. It leaves out faster decisions for applicants, fewer invalid applications, fewer appeals from errors and the cost of the tool; released time in stretched planning teams usually goes to backlog.
Who already uses it?
5 public deployments, strongest evidence first. Grades: A regulator or audit, B the organization itself, C vendor case study, D anonymous or estimate.
Intellectual Property Office
United Kingdom · Government and public sector · 2025
Before filing, applicants can use the IPO's free "Check if you could register your trade mark" tool. Using text and image embeddings, it matches the goods and services the applicant enters to approved terms, searches for similar earlier marks (including logos) and flags elements that may not be acceptable, such as offensive words or protected symbols. It needs no personal details. Previously, applications were filed without meeting essential criteria and were rejected automatically. The tool gives indicative guidance only: every full application is still assessed and examined by the IPO. The tool receives an average 3,000 visits per month, and the IPO says it supports about 20% of filings.
No outcome disclosed.
Leeds City Council
United Kingdom · Government and public sector · 2025
Leeds City Council's planning service is running a proof of concept pilot of Xylo Core, which ingests a planning application when an officer opens the case, redacts personal data, builds a tailored validation checklist, flags missing documents or wrong information, suggests the relevant site history, policies and constraints from GIS data, and drafts routine correspondence and report sections. Models from OpenAI, Anthropic and Google are called through APIs, with EU data residency and zero data retention. Officers must accept or reject every suggestion, sources and reasoning are shown for each, an audit log records what the officer kept, and the tool never recommends approval or refusal. The pilot starts with about ten officers on householder applications, the simplest type, with more types to be added once accuracy is proven.
- Accuracy: at least 85%, initial testing across validation and policy recommendation prompts
"Initial testing is delivering accuracy of 85%+ across the different prompts used for the different validation and policy recommendation workflows"
Claimed by: organization
U.S. Department of Agriculture (Office of the Chief Information Officer)
United States · Government and public sector · 2025
USDA is piloting AI at several steps of its environmental review process for permits. At the evaluation stage the model predicts whether an application is a simple categorical exclusion (a project class that needs no detailed environmental assessment) or needs more human attention; AI is also used to process public comments. The aim is faster permit issuance with fewer staff hours before a project can break ground. It is developed in house. The use case was presumed high impact and then determined not to be, because the AI makes recommendations for authorized staff and no final decisions.
No outcome disclosed.
U.S. Fish and Wildlife Service
United States · Government and public sector · 2025
The Fish and Wildlife Service is preparing AI for ePermits, its online permit system. A chatbot and application wizard will answer questions, give dynamic help on the application form, draw on a knowledge base and escalate to a human; a cognitive search layer adds semantic search, document summaries and natural language answers. The agency states that it does not use agentic AI in permit processing, that every AI assisted recommendation is reviewed and approved by a person, and that no permit decision rests on AI output alone.
No outcome disclosed.
West Berkshire Council
United Kingdom · Government and public sector · 2025
West Berkshire Council assesses online applications for a larger household rubbish bin against the minimum criteria in its policy with a rules based tool built in house. Applications that miss the criteria are rejected and the applicant is told automatically; those that meet them go to the Waste Management team for review. In many cases staff time per application drops to recording the outcome, and every application and decision is stored so the team can scrutinise them. The tool was tested before launch to confirm it reached the same decisions as a person applying the same policy, production decisions are sampled periodically, and applicants can appeal to the waste team. It is a small but real example of automated decisions on a simple council permission.
- Interactions handled: about 42, decisions per month on average
"An average of 42 decisions are made per month using the algorithmic tool."
Claimed by: organization
How do you implement it?
A model agnostic playbook: what to prepare, the order to build in, and what goes wrong.
Data you need
- Validation checklists and requirements per application type
- Local policies, constraints and planning history in searchable form
- GIS layers for sites and constraints
- A sample of past applications with validation outcomes for testing
Systems to integrate
- Permitting or planning case management system
- Document management and applicant portal
- GIS and address data
- Correspondence and fee systems
Complexity: Medium
Document extraction and checklist validation are mature; the effort is in encoding local validation requirements, connecting GIS and planning history, and building an audit trail that stands up in an appeal.
- 1
Start with validation of simple applications
Pick the simplest, highest volume type (the Leeds pilot starts with householder applications and about ten officers) and automate the validation checklist first.
- 2
Show sources for every suggestion
Every flag, policy reference and draft sentence needs its source and reasoning, so the officer can accept or reject it quickly and defend the decision later.
- 3
Log what officers keep
Record each suggestion and the officer's action; this is your audit trail and your accuracy measure.
- 4
Move checks upstream
Offer applicants the same checks before they submit, as the UK IPO does with its trade mark pre check, to cut invalid applications at source.
- 5
Automate decisions only for simple published rules
Automated outcomes fit narrow permissions with clear rules and a way to appeal: West Berkshire rejects larger bin applications that miss its policy criteria automatically and sends the rest to its waste team. Keep discretionary permits with officers.
Guardrails
- No automated recommendation to approve or refuse a discretionary permit
- Sources and reasoning shown with every suggestion; officers accept or reject each one
- Audit log of AI suggestions and officer actions for every case
- Personal data redacted before documents are sent to external models
- Fully automated decisions only for rule based permissions, with notice and a route to challenge
KPIs to instrument
- Share of AI validation flags accepted by officers, by application type
- Time from receipt to valid application and to decision
- Share of applications returned as invalid, before and after applicant pre checks
- Appeals and complaints citing errors in validation or reports
- Officer time per application from time studies
Human in the loop
Validation and planning officers review every suggestion and make every decision. Team leaders review accuracy of suggestions each month; policy owners approve checklist and rule changes; appeals are handled entirely by people with access to the audit log.
Common failure modes
- Rubber stamping
- Officers accept suggestions without reading them. Measure acceptance rates, sample cases and show sources prominently.
- Local rules missed
- A generic model misses a local policy or constraint. Retrieve from the authority's own policy index and test with local cases.
- Pilot never scales
- A tool that saves time on householder cases stalls on complex ones. Add application types only when accuracy on each is proven.
- Automation without recourse
- Automated decisions on permissions without a way to challenge can breach data protection rules on solely automated decisions. Provide notice and human review.
What are the risks and rules?
EU AI Act
Depends on design
Permit and licence decisions are not listed as such in Annex III, so officer decision support is usually minimal risk, and an assistant that talks to applicants carries the Article 50 transparency duty. The exceptions are permits in an Annex III area: examining applications for visas and residence permits (point 7) and evaluating eligibility for essential public assistance benefits and services (point 5(a)) are high risk. Solely automated decisions with legal or similarly significant effects on a person fall under GDPR Article 22 whatever the tier.
Rules that apply
Guidance
- AI Playbook for the UK Government (UK Government, Europe). Guidance for civil servants and government organisations; principle 4 asks for meaningful human control at the right stages.
- Algorithmic Transparency Recording Standard Hub (Government Digital Service, Europe). Leeds, the IPO and West Berkshire publish records for the tools on this page.
- Directive on Automated Decision-Making (Treasury Board of Canada Secretariat, North America). A model for impact assessment, notice and human intervention in automated administrative decisions.
Controls to put in place
- Transparency record for each tool, stating it does not decide discretionary permits
- Data protection impact assessment covering applicant documents sent to models
- Audit trail retained for the appeal period
- Monthly accuracy review by application type
- Notice to applicants when a decision is automated, with a route to human review
Frequently asked questions
- Does AI decide planning or permit applications?
- Not in the public examples for discretionary permits. Leeds' Xylo Core gives no approve or refuse recommendation and officers accept or reject every suggestion; the US Fish and Wildlife Service states no permit decision rests on AI alone. Narrow rule based permissions can be partly automated: West Berkshire rejects larger bin applications that miss its policy criteria automatically, with a route to appeal, and sends the rest to staff.
- How accurate is AI validation?
- Early figures only. Leeds reports initial accuracy of 85% or more across its validation and policy prompts, with a target of 99% or more, starting with householder applications. Measure acceptance of suggestions on your own cases.
- Where should an authority start?
- With validation of the simplest, highest volume application type, and with checks applicants can run before submitting. The UK IPO says its trade mark pre check supports about 20% of filings.
How to cite this page
Blits.ai AI Use Case Library, "AI for permit and licence application processing", last verified 26 September 2026, https://www.blits.ai/ai-use-cases/permit-and-licence-application-processing. Licensed under CC BY 4.0. Method: how we verify use cases.
Changelog
- 27 September 2026: First published