Official licensing services and public-sector workflow tools

In business licences product research, start with the job the product must do. Official services discover or route a requirement. Commercial workflow products organise evidence, decisions and renewal. Do not combine them into one best-tool score.

This article is desk research completed on 5 September 2026. No commercial product was bought, accessed or tested, so every product claim rests on vendor documentation. No application was submitted.

What to take away

Official discovery services

The Department for Business and Trade's Find a licence service searches by activity and place and warns that its UK catalogue may not be exhaustive. Evaluate it for discovery and routing, not for case management or advice. It is free to use.

Record the search terms, nation, result and later authority confirmation. An empty result is not clearance.

Task-specific public licensing services

The Food Standards Agency's Register a Food Business service collects operator, establishment and activity details for routing. It is free. The GOV.UK council finder returns a council website from a postcode. The Environment Agency's permit guidance addresses specified activities and environmental effects in England.

Each performs a different documented job. A fair test uses the relevant activity rather than asking which one is best overall.

Public-sector workflow products and documented scope

Commercial licensing and case workflow products are bought for different tasks. A shortlist can include Accela, Idox, Civica and Salesforce Public Sector Solutions. It can also include ServiceNow, Microsoft Power Platform and Laserfiche. The table compares their public documented scope.

Use the documented scope as the inclusion rule. A product without a first-party page for the named function and legal entity stays off the shortlist. Mark untested functions unknown. Test with synthetic cases containing two sites, revised evidence, an acknowledgement and a decision. Add conditions and a review date.

Check whether the product stores primary sources, distinguishes case states, controls access, preserves versions and reopens the right record when facts change.

On the documented scope above, a short decision rule. Idox or Civica first for a UK council that needs licensing with environmental health, planning or revenues. Microsoft Power Platform or Salesforce Public Sector Solutions for a custom build the council maintains itself. Laserfiche for document and records workflow rather than case decisions.

Accela for an agency running code enforcement outside the UK council pattern.

Testing a workflow with three scenarios

First, create a new case from a deliberately incomplete brief. The product should show which facts are absent without inventing an answer. Record whether a user can link an uncertainty to an owner. Record whether the product can prevent an unverified assumption from becoming an approved requirement.

Second, upload an original document and a corrected version. A colleague should identify which one was submitted, when it changed and which decision relied on it. Look for an audit trail that is understandable without help from the vendor's sales team.

Third, change a material fact after the case appears complete. Moving premises, adding an activity or changing an operator should reopen the relevant check. The test asks whether the workflow exposes the change and prompts a fresh authority review. Software need not decide the legal effect.

Worked example using a synthetic district council case. An incomplete brief omits the number of food premises and the opening hours. The corrected document test uploads a revised layout plan, so the reviewer must say which version went to the authority.

The material fact change adds late-night refreshment once the file looks complete. At that point the product should reopen the noise and hours check and name the new activity.

Time each task, but treat the timings as observations from the stated scenario rather than universal productivity claims. Capture errors and workarounds alongside successes. One clean demonstration is not enough to establish reliability.

Export the case in a usable format. Ask a colleague to find the authority, submitted document, decision and next date outside the product. Simulate account loss and administrator departure. A strong interface does not offset trapped or ambiguous evidence.

Compare commercial pricing and contracts

Public list prices exist for some building blocks. Microsoft lists Power Apps Premium at about $20 per user per month and Power Automate Premium at about $15 per user per month. Salesforce lists Sales Cloud from about $25 per user per month. Accela, Idox, Civica and ServiceNow do not publish standard prices.

Enterprise licensing suites are quoted annually. The figure depends on modules, user numbers, sites, data migration and support. Contracts Finder publishes UK award notices for council licensing and regulatory system contracts. The contracted value for a comparable council is the figure that matches the buyer's scope. Treat any range as typical, not as a quote.

Map the quoted plan to the scenario's users, sites, storage, support and export needs. Record implementation work and migration separately from recurring fees. Do not compare headline prices when one option excludes a necessary module or professional service.

Ask what happens at renewal, downgrade and termination. A usable exit includes the case data and the documents needed to interpret it. Obtain contract or data-protection review where the information or commitment justifies it. A feature checklist cannot settle those obligations.

Reporting a product assessment

Publish the scenario, inclusion rule, first-party links and evidence level. Add commercial relationships and date. Avoid claims about usability or support without a real test. The conclusion should recommend a route for the stated task. Avoid an unexplained universal winner.

Before you act

Use the checklist above before any procurement conversation. Confirm the task, record the inclusion rule and evidence level, and name the person who signs off the recommended route.

Common questions

Why should official services and commercial workflow products not be scored together?

They do different jobs. A discovery service returns a requirement or a council website. A workflow product stores the case, the decision and the renewal. Scoring them together would rank a free routing tool against a bought case system.

What should a commercial shortlist require before any testing?

A first-party page for the named function and legal entity. Then the synthetic case that covers two sites, revised evidence, an acknowledgement, a decision, conditions and a review date.

What does the third test check when a material fact changes?

Whether the workflow reopens the relevant check after a move, a new activity or a change of operator. It should flag that a fresh authority review is needed. Software need not decide the legal effect.