Measurement
Part of Business licences measurement: how to judge licensing services in 2027
A licensing dashboard that puts exceptions above totals and owners beside decisions
Build an England licensing dashboard around exceptions, owners and decisions, with clear definitions, safe drill-down and source-aware reporting.
A licensing dashboard should help someone act on a case, not reward the number of charts produced. Begin with the decisions managers make: resolve an authority question, complete evidence, assign a condition, review a renewal or pause an activity.
What to take away
- Start dashboard design from the decisions managers make, not from the number of charts produced.
- Show exceptions such as missing owners and evidence above totals, because those drive action.
- Keep case states separate and never colour an acknowledged case as approved.
- Do not merge several establishments into one green organisation row if each needs separate treatment.
- Assign every data-quality exception to an owner and record whether it affects historical reports.
Design metric cards first
Each card needs a definition, denominator, period, data source, owner, refresh time, threshold and limitation. Government Digital Service guidance on using data to improve a service supports linking measures to user needs and improvement choices. Keep licensing-law claims tied to the responsible authority.
Metric card requirements
- Definition
- Denominator
- Period
- Data source
- Owner
- Refresh time
- Threshold and limitation
Show case states accurately
Separate possible route, authority confirmed, submitted, acknowledged, decided and conditions implemented. Do not colour an acknowledged case as approved. Display counts beside percentages where small denominators may distort the picture.
Put exceptions above totals
Show cases without owners, missing evidence, conditions with no operational control and renewals requiring review. The Department for Environment, Food and Rural Affairs' animal activity licensing process includes decision, renewal and enforcement for that English activity. It illustrates a lifecycle without supplying universal status rules.
Preserve activity and location
The Food Standards Agency's food business registration guidance explains covered activities and multiple establishments in its stated jurisdictions. A dashboard should not merge several sites into one green organisation row if each establishment needs separate treatment.
For local routes, identify the authority through the GOV.UK council finder using the actual postcode. Segment English areas rather than presenting one council process as national.
Protect case detail
Use drill-down to a controlled record for authorised users. Do not copy identity documents or sensitive correspondence into a widely viewed summary. Show only the fields needed for the decision and log access where appropriate.
Test with a failure scenario
Insert a synthetic case with a wrong status, absent owner and approaching review. Ask a manager to identify the consequence and next action. If the visual encourages the wrong decision, change the definition or layout before connecting live data.
Validate data and access
Reconcile dashboard totals to a small set of complete case records before every major release. Include a submitted case, a refused or withdrawn case, a conditional decision and a renewal. Check that missing evidence remains visible and that an updated status does not erase the earlier event.
Limit access according to the decisions users make. Senior managers may need aggregate exposure, while case owners need controlled drill-down. An analyst does not require identity documents simply to calculate a routing rate. Test exports and shared links so the dashboard does not create an uncontrolled copy of licensing information.
Assign every data-quality exception to an owner and record whether it affects historical reports. If a definition changes, add a visible break and provide the old and new calculation. Do not silently restate previous periods under a rule that did not exist at the time.
Review every dashboard card on a schedule. Ask its decision owner what action followed during the last period. If no action is possible, replace the card with an operational exception or retire it. Record the outcome of each review, including measures kept only for statutory or contractual reporting. Confirm that the current users still need access to the underlying data.
Retire decoration, annotate definition changes and retain enough history for a reviewer to reproduce the reported result.
Before you act
- Define each card's owner, source, threshold and limitation.
- Show counts beside percentages where denominators are small.
- Identify the local authority using the actual postcode.
- Test the dashboard with a synthetic failing case.
- Reconcile totals against complete case records before release.
- Retire any card whose owner reports no action.
Common questions
What should come before totals on a licensing dashboard?
Exceptions. The article says to show cases without owners, missing evidence, conditions with no operational control and renewals requiring review. These are the items that prompt someone to act on a case rather than admire a chart.
How should a dashboard handle several sites under one organisation?
It should not merge them into one green organisation row if each establishment needs separate treatment. The Food Standards Agency guidance on food business registration covers multiple establishments, so activity and location should be preserved in the display.
What should happen when a dashboard definition changes?
Add a visible break and provide the old and new calculation. Do not silently restate previous periods under a rule that did not exist at the time. Record whether the change affects historical reports and assign the exception to an owner.
