Licensing service standards for scope, routing, response and escalation that promise no outcome

Service standards for licensing support should cover performance the team can control. They should not promise approval, legal certainty or a council response time. A useful standard tells applicants what the service does, when it responds and how uncertain or urgent cases are escalated.

What to take away

Service standards should cover what the licensing team controls, not approval or legal certainty.
Routing should use the actual postcode and show the authority page and source date.
Separate the team's response time from the authority's response time in every standard.
Recovery standards should protect the applicant's position, preserve evidence and assign a person to correct the record.
Measure confirmed routing, avoidable returns and successful handover with definitions and baselines.

Scope standard

State the activities, English areas and service stages covered. The Department for Business and Trade's Find a licence service searches by activity and place but warns that its UK catalogue may not be exhaustive. A support service should explain how it confirms routes and when it cannot answer.

Scope standard essentials

State activities, English areas, service stages
Explain how routes are confirmed
Explain when service cannot answer
Use Find a licence by activity and place
Warn UK catalogue may not be exhaustive

Routing standard

For locally administered work, use the GOV.UK council finder with the actual postcode. The service record should show the authority page and source date. Do not promise one national form where councils own the process.

Response standard

Define when an enquiry is acknowledged, when the user receives a substantive next step and how absence is covered. Separate the team's response from the authority's. If a deadline is supplied by the applicant, verify its source before calling the case urgent.

Evidence and quality standard

Explain which facts and documents are checked, who approves declarations and what remains the applicant's responsibility. Retain the exact submitted version and distinguish acknowledgement from grant. A quality reviewer should be able to stop an incomplete pack.

Accessibility and privacy standard

Offer an assisted route and alternative communication where the service supports them. Collect only the information needed for the task, restrict sensitive case access and explain retention. Consistency does not require every person to use the same channel.

Escalation standard

Define triggers for authority clarification, specialist advice, complaint and operational pause. Staff must not guess a material legal answer to meet a service target.

Recovery and correction standard

Explain what happens when the service sends a user to the wrong route, loses access to a case or publishes an outdated instruction. The immediate response should protect the applicant's position, preserve evidence and assign a person to correct the record. Do not hide the incident merely to maintain a performance figure.

Set an internal time for acknowledging the service error and giving the user a responsible contact. Keep this commitment separate from any authority response. Where the mistake may have legal or financial consequences, escalate it through the organisation's approved process and obtain qualified advice.

Test recovery with a synthetic scenario. Remove the main case owner, make the platform unavailable and ask a deputy to find the source, submitted version and next deadline. Record gaps and retest after correction.

Complaint standard

Give users a visible route to challenge factual accuracy, service conduct and accessibility. Log the issue, evidence, outcome and change made. A complaint target should not pressure staff to offer an unsupported licensing answer simply to close the case.

Measurement standard

Government Digital Service guidance on using data to improve a service recommends measures linked to user needs and decisions. Track factors such as confirmed routing, avoidable returns and successful handover, with definitions and baselines.

Government Digital Service guidance on planning user research can support testing standards with relevant participant groups. Record which applicants could not use the standard route and why. Assign every proposed change to a service owner and measure the revised journey. Publish limitations and revise the standard when evidence shows that a promise is unclear or unachievable.

Before you act

State the activities, areas and service stages covered.
Confirm routes with the actual postcode and record the source date.
Define acknowledgement and substantive next step times separately from the authority.
Explain which facts and documents are checked and who approves declarations.
Define escalation triggers for clarification, specialist advice, complaint and pause.
Test recovery with a synthetic scenario and retest after correction.

Common questions

What should a licensing service standard promise?

It should cover performance the team can control, such as what the service does, when it responds and how uncertain or urgent cases are escalated. It should not promise approval, legal certainty or a council response time, because those sit outside the team's control.

How should a service handle routing for locally administered work?

Use the GOV.UK council finder with the actual postcode. The service record should show the authority page and source date. Do not promise one national form where councils own the process, because the authority controls that route and its requirements.

What should happen when the service sends a user to the wrong route?

The immediate response should protect the applicant's position, preserve evidence and assign a person to correct the record. Set an internal time for acknowledging the service error and giving a responsible contact. Do not hide the incident to maintain a performance figure.