Running licensing operations with case states that have fixed meanings

The work starts with an accurate activity description and continues through authority research, evidence, submission, decision, conditions, renewal and change.

This guide leads with England and uses wider UK sources only where their scope is stated. It reflects pages checked on 5 September 2026. Reopen every live route before a material decision because authority instructions, forms and services can change.

What to take away

A fast application is not a successful operation if the route is wrong or conditions never reach staff.
Case states need fixed meanings, and each transition should require named evidence and an accepting person.
After grant, capture each material condition and assign an operational control drawn from the decision.

Open a case with the facts

Record the activity, site, nation, operating hours, public involvement, responsible people and any relevant environmental effects. Avoid business labels that hide several regulated tasks. A venue, mobile trader or multi-site operator should have separate rows where activities or authorities differ.

The Department for Business and Trade's Find a licence service on GOV.UK searches official records by activity and place, with filters for the four UK nations. It warns that the catalogue may not include every licence. Use it to identify possible routes, then retain the later authority confirmation in the case.

For local permissions, the GOV.UK council finder takes a postcode and identifies a council website. This matters in England because many routine licensing processes are locally administered. Record the exact postcode used and do not substitute a neighbouring authority's form.

Use case states with fixed meanings

A workflow needs more than open and closed. Define possible route found, authority confirmed, evidence preparing, submitted, acknowledged, decided, conditions implemented and renewal scheduled. Each transition should require a named piece of evidence and a person who accepts it.

Licensing case states

Route found
Authority confirmed
Evidence preparing
Submitted
Acknowledged
Decided
Conditions implemented
Renewal scheduled

Case state	Entry evidence	Accepting role
Possible route found	Activity description and search result from GOV.UK Find a licence	Case owner
Authority confirmed	Written or published confirmation from the relevant council or regulator	Compliance lead
Evidence preparing	Evidence pack index with owners and due dates	Case owner
Submitted	Submission reference and retained version	Applicant or authorised person
Acknowledged	Authority acknowledgement or receipt	Case owner
Decided	Decision notice or refusal with reasons	Compliance lead
Conditions implemented	Condition-to-control mapping and staff briefing record	Operations manager
Renewal scheduled	Calendar entry with owner, deputy and review date	Case owner

For example, a cafe in Leeds describes its activity as food service and on-sales alcohol until 22:00. The case owner finds food registration and a premises licence and confirms Leeds City Council as the authority. The owner prepares the floor plan and menu, submits through the council portal, logs the acknowledgement and records the granted conditions.

Staff are briefed on hours and age checks before the launch gate passes.

An acknowledgement proves receipt, not permission. A decided case still needs review of the granted scope and conditions. A closed row should show why no further action is required, with the facts and source that supported the conclusion.

Keep uncertainty visible. If the team cannot identify the authority or interpret a material instruction, assign the question rather than allowing a blank field to appear harmless. Escalate disputed or high-consequence matters to the authority or an appropriately qualified adviser.

Build evidence in the order the route requires

The case owner should open the current official application or registration route and list the required facts and documents. Assign owners and due dates based on real dependencies. Keep drafts, approved versions and submitted versions distinct.

Build evidence in order

Open current official route
List required facts and documents
Assign owners and due dates
Keep drafts, approved and submitted versions distinct
Run second-person check against live instructions

The Food Standards Agency's Register a Food Business service collects operator, establishment and activity information for routing. It provides a concrete example of a task whose data must be accurate. Completion does not prove acceptance or resolve permissions outside food registration.

Run a second-person check on names, addresses, dates, activities, declarations and attachments. The reviewer should compare the pack with the live authority instructions rather than an old internal checklist.

Control submission and correspondence

Submit through the verified official channel and retain the exact version, reference and acknowledgement. Log authority requests with an owner, response date and link to the revised evidence. Do not let material exchanges remain only in a private inbox.

Submission and correspondence controls

Submit via verified official channel
Retain exact version, reference and acknowledgement
Log authority requests with owner and response date
Record telephone clarifications with date and facts
Store personal information under role-based access

Where telephone contact clarifies a route, record the date, published contact route, facts discussed and next step. Seek written confirmation when the answer supports an irreversible commercial decision. Store personal information under role-based access and avoid copying sensitive attachments into meeting notes.

If a case stalls, distinguish an authority wait from an internal missing item. Do not promise a regulator response time unless the current official source supports that wording.

Prepare for inspection and decision

Some regimes include inspection or further review. The Department for Environment, Food and Rural Affairs' animal activity licensing process describes application, inspection, decision, renewal and enforcement within that English framework. Use it for those animal activities, not as a generic timeline for every permission.

The case record should connect inspection evidence, corrective actions and the final decision. If the authority requires changes, preserve the original issue and the evidence showing how it was addressed. Do not mark the case complete because an inspection occurred.

Translate permission into daily work

Premises operations show the need to compare the planned service with the decision. GOV.UK's premises licence page routes applicants in England and Wales to the relevant local authority and identifies covered activities. The Home Office's alcohol licensing guidance describes several authorisations and the wider England-and-Wales framework.

England also licences street trading, taxi and private hire vehicles and drivers, and scrap metal dealers through separate council or agency routes.

After grant, capture each material condition and assign an operational control. Examples may include staff instructions, supervision, records, notices or limits on hours, but the actual control must come from the decision. Give supervisors access to what they need without circulating the full application file.

Brief staff before the regulated activity begins. Ask them to explain the limit back in their own words and show where an incident or uncertainty is escalated.

Define team roles

The case owner coordinates the record and next action. The applicant or authorised person approves facts and declarations. Subject specialists resolve technical or legal questions within their competence. Operations implement conditions. A quality reviewer challenges evidence before submission, while a deputy provides continuity.

Use a RACI-style record only if it clarifies who acts, approves, advises and receives information. A shared mailbox cannot be accountable. In a small business, one person may hold several roles, but the decisions should remain explicit.

At handover, the incoming owner should locate the authority, submitted version, decision, conditions, next date and open question unaided. Missing information is a quality failure, not a reason to rely on memory.

Set service standards the team can control

Service standards should concern response, accuracy, handover, privacy and escalation. They should not promise approval or an authority timetable. Define when a customer receives acknowledgement, how urgent questions are triaged, what evidence is checked and when a matter is sent for qualified review.

For example, set acknowledgement of a new enquiry within two working days and triage urgent questions on the same working day.

Include accessibility and assisted routes. Record the participant's communication need only where necessary and handle it through the approved information process. A consistent service does not mean forcing every applicant through one channel.

The Government Digital Service's guidance on using data to improve a service recommends measures linked to user needs, baselines and improvement decisions. Use it to measure the support service, while keeping licensing-law claims tied to their regulatory sources.

Run quality gates at consequential points

Check route and jurisdiction before evidence work starts. Check the pack before submission. Check the decision before launch. Check conditions after operational changes. Check renewal evidence before the deadline window. Each gate needs criteria, evidence, reviewer and outcome.

For example, a pre-submission gate might use criteria of a complete evidence pack, evidence from the pack index, the compliance lead as reviewer and an outcome of pass, hold or escalate.

Sampling can supplement full checks for low-risk administrative fields, but high-consequence facts and declarations may need complete review. Record the sampling method and correct the process when repeated errors appear.

Do not let a target volume override the gate. An incomplete application should remain held even if a throughput metric suffers.

Conduct a real launch review

Compare the proposed opening activity, site, hours and responsible people with granted permissions and conditions. Confirm that required authorisations are decided, not merely submitted. Walk through the premises or service with the people who will operate it.

Test a realistic exception: a customer request outside approved hours, an absent supervisor, a changed menu, a new event location or a system outage. Staff should know what stops, who decides and where the authoritative record lives.

Record a go, conditional go or no-go decision with the accountable person and evidence. A commercial deadline does not turn an unresolved permission into acceptable risk.

Manage renewals and change

Put expiry dates and review lead times in a controlled calendar with an owner and deputy. Also use event triggers for new sites, activities, operators, layouts, hours or environmental effects. Reopen the affected licence rows before the change begins.

Review the portfolio for orphaned conditions, missing authority records and outdated sources. A green dashboard should not conceal a principal site whose key decision is still unknown.

Improve the service from evidence

Track avoidable returns, unresolved handovers, conditions without owners, renewal recovery and time to find a confirmed route. Pair counts with case review so the team understands cause. Government Digital Service guidance on planning user research can help connect participant groups and methods to an improvement decision.

Do not treat application volume or approval as a simple service-quality score. Authority decisions depend on the merits and facts of each case. Publish definitions, exclusions and negative findings.

The immediate next step is to choose one live English case and test it from activity description through evidence recovery. Repair the first broken handoff and assign the unresolved questions. Then schedule the launch gate review with the accountable person.

Before you act

Record the exact postcode used for local permissions.
Open the current official route and list required facts and documents.
Run a second-person check against live authority instructions.
Log authority requests with an owner, response date and revised evidence.
Brief staff on each condition before the regulated activity begins.
Record a go, conditional go or no-go decision with evidence.

Common questions

What should a case record show when a row is closed?

A closed row should show why no further action is required, with the facts and source that supported the conclusion. Uncertainty should stay visible, and disputed or high-consequence matters should be escalated to the authority or a qualified adviser.

How should a team handle a telephone call that clarifies a licensing route?

Record the date, published contact route, facts discussed and next step. Seek written confirmation when the answer supports an irreversible commercial decision. Store personal information under role-based access and avoid copying sensitive attachments into meeting notes.

What does a launch review compare before the regulated activity starts?

Compare the proposed opening activity, site, hours and responsible people with granted permissions and conditions. Confirm required authorisations are decided, not merely submitted. Test a realistic exception, then record a go, conditional go or no-go decision with the accountable person and evidence.