Operations
Part of Running licensing operations with case states that have fixed meanings
Business licences quality checklist: five gates and a defect log
A business licences quality checklist for England with five named gates, the defects each one should catch and a log that closes them on evidence.
A quality checklist earns its place when it records what went wrong, not only that a box was ticked. Log each defect with its type, where it entered the case and whether a gate caught it. Then correct the case, fix the cause and close the defect on evidence.
What to take away
- Log every defect with its type, where it entered the case and whether a gate caught it.
- Correct the case first, then decide whether instructions, training or system validation should change.
- Close a defect only when the evidence is repaired and preventive action has an owner.
- If a colleague's reproduction of the file differs from yours, hold the gate.
- Re-run the gate after any material change, and at least annually.
The five gates and the defects they catch
The checklist runs five gates in the order a case moves. Each gate asks fixed questions, and a failed question becomes a defect in the log.
| Gate | What it asks |
|---|---|
| Route and jurisdiction | Is the activity described clearly, is the nation explicit and is the authority right for the real location? |
| Applicant facts and evidence | Do names, addresses, activities and dates agree, and are declarations approved by the authorised person? |
| Submission status | Was the official channel used and is the exact submitted version retained? |
| Decision and conditions | Does the planned operation fit the granted scope and does every condition have an owner? |
| Handover and change | Can a deputy find the evidence, and do new sites, activities or hours reopen the review? |
Log the defect when it is found
Write the log entry at the gate, while the file is still open. A wrong postcode points to a different process failure from a missing attachment or an incorrect status, so the entry must name the type, not just the case.
| Log field | What to record | Why it matters |
|---|---|---|
| Defect type | A wrong postcode, a missing attachment or an incorrect status, for example | Different types come from different process failures |
| Where it entered | The step at which the error first appeared in the case | Shows which gate should have caught it |
| Caught or missed | Whether the gate caught it | Lets later reviewers see whether the problem returns |
| Cause | Unclear language, stale guidance, missing evidence or a training problem | Points to instructions, training or validation |
| Reviewer, date, failed item | Who found it, when, and which checklist item failed | Makes the entry reproducible |
| Correction | What was repaired, and who owns preventive action | A defect closes only when both exist |
Keep the original observation so later reviewers can measure whether the same problem returns, and keep the log beside the planning template register so each row links to its defects. A defect type recorded loosely cannot be counted or compared afterwards.
Gate one: route defects
A route defect can start with the wrong authority. A food business registration sent with a postcode from a neighbouring council area may be checked against the wrong authority's form, so hold the gate until the correct council confirms the route.
Confirm route and authority
Is the activity in plain language?
Is the nation explicit?
Is the responsible authority identified?
GOV.UK's guidance says that if you operate in more than one location, you need to register each site in which they are located. Reject a pack based on another authority's form unless the responsible council confirms that route.
The reviewer records the confirmed route and the responsible authority in the file, not just a tick. The Department for Business and Trade's Find a licence service supports discovery by activity and place, but warns that it may not contain every licence.
Gate two: fact and evidence defects
A pack can look complete while names, addresses, activities and dates disagree. Compare them across every document, and check that each declaration was approved by the person authorised to make it, with drafts, approved records and submitted versions distinguishable.
A food business registration is made to the local council using the Food Standards Agency's registration service, which asks for operator, establishment and activity information. In a food case, compare those facts with source records, and keep adjacent permission questions separate.
Applicant facts and evidence
- Names, addresses, activities and dates agree
- Declarations approved by authorised person
- Drafts, approved records and submitted versions distinguishable
- Compare food operator facts with source records
- Keep adjacent permission questions separate
Gates three and four: submission, decision and condition defects
Log a defect whenever one of these is true at the gate:
- The official channel was not used.
- The exact submitted version was not retained.
- A reference or acknowledgement was called approval.
- An authority request has no owner or response date.
- The case was marked complete at inspection.
- A material condition has no staff action or record.
- Expiry or review dates are not supported by the decision.
In the animal activity licensing process under the Animal Welfare (Licensing of Activities Involving Animals) (England) Regulations 2018, a local authority that receives an application to grant or renew a licence must appoint a suitably qualified inspector to visit the site.
Inspection is a stage, not the end, so verify the actual decision and later controls, and test the planned operation against the granted scope.
Close the defect properly
A defect is closed by repair and by prevention, not by a note saying it was seen. Work through the steps in order, and keep the cause in the quality log.
- Correct the case first, so the file is accurate before anything else changes.
- Record the causeunclear language, stale guidance, missing evidence or a training problem.
- Decide whether instructions, training or system validation should change, and name an owner using clear team roles.
- Ask a colleague who did not prepare the file to reproduce one route and one condition from the source evidence.
- If their conclusion differs, hold the gate and resolve the discrepancy.
- Record the reviewer, date, failed item and correction.
Full review suits declarations and other high-consequence facts where sampling would not be proportionate. For repetitive low-risk fields, document the sample size and selection method, and expand the review if the sample exposes repeated errors.
Gate five: handover and change
A deputy should be able to find the authority, evidence, decision and next step without the case owner. Keep sensitive records access-controlled, and reopen the review when a new site, activity, operator, layout or set of hours appears.
Re-run the gates
Schedule another check after any material authority, activity or ownership change. Re-run the gates at least annually, or sooner if the authority changes its process.
A monthly quality summary should show causes and consequences, not a count of completed boxes. Pair it with licensing metrics that keep discovery, submission, decision and operating control apart.
Before you act
- Confirm the route and responsible authority for the real location.
- Check names, addresses, activities and dates agree across the pack.
- Keep the exact submitted version and record references without calling them approval.
- Assign every material condition to a staff action or record.
- Record the defect type, where it entered and whether the gate caught it.
- Ask a colleague to reproduce one route and one condition from source evidence.
Common questions
What should a defect log entry contain?
The defect type, where it entered the case, whether the gate caught it, the cause, the reviewer, the date, the failed item and the correction. Keep the original observation so later reviewers can see whether the same problem returns.
When is a defect closed?
When the evidence is repaired and the preventive action has an owner. A colleague who did not prepare the file should be able to reproduce one route and one condition from the source evidence, and any difference holds the gate.
When should sampling be replaced by full review?
Full review suits declarations and other high-consequence facts where sampling would not be proportionate. Sampling is for repetitive low-risk fields, and repeated errors in a sample mean the review should expand.
