Business licences software selection: an evidence method

For business licences software selection, a decision matrix keeps the choice honest. Put the controls the work cannot do without above every preference, and score each kind of evidence separately. A supplier then cannot buy back a failed control with points elsewhere.

This is desk research dated 5 September 2026. No commercial product was purchased or tested, and no supplier is recommended.

What to take away

Set mandatory controls first

Write the mandatory controls before looking at any product. Mandatory items might include a usable export, role-based access, auditable status changes and recovery of the source evidence. A supplier cannot compensate for failing a mandatory control by collecting points elsewhere.

Treat each one as pass, fail or unknown, never as a score. Put mandatory controls above scored preferences, which could include interface layout or configurable views. A pleasant screen does not repair an export nobody can read.

Tie the controls to the case lifecycle

Controls only mean something against the work. Write the steps from discovery to renewal, then check that the system stores the later authority confirmation, not merely a search result from a discovery service.

Define states such as researching, authority confirmed, submitted, acknowledged, decided and conditions implemented. Require a source, owner and date for each material transition, and test them with a synthetic case. Keep the lifecycle consistent with the operating workflow the team already runs, and with the gates in the quality checklist.

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, so the tool should link inspection, decision and conditions. Do not generalise that process to another activity.

Score three kinds of evidence separately

Give each criterion its own row and each evidence type its own column. The table shows how the mandatory rows read once documentation, a test and the contract are kept apart.

If a feature was mentioned in a sales meeting but not demonstrated or written into the agreement, leave its evidence status unresolved. Mark functions not demonstrated as unknown rather than guessing.

Weight what remains

Weight the remaining criteria by the consequence of failure and record the rationale. A criterion whose failure would leave a case unrecoverable deserves more weight than one that only slows a user. Say why in a sentence, so a reader can disagree with the reason instead of the number.

Score public documentation, observed test results and contract commitments in separate columns, and add them only inside a column. A feature that exists on paper but fails the test has a documentation score and a test result, and the two should not blur. Check the supplier itself through vendor due diligence, not through the matrix.

Check data and exit before selecting

Two controls need outside evidence. For data, Article 5 of the UK GDPR sets out seven key principles, including purpose limitation, data minimisation, accuracy, storage limitation and security. Review data fields and permissions, exports and deletion against the proposed use, and keep real applicant documents out of demonstrations.

For exit, export the complete test case and ask a colleague to recover the authority, submitted version, decision, conditions and next date without the application. Record proprietary formats or missing context. Test what happens when the main administrator leaves.

Score independently, then decide

Ask two people to score independently, then discuss material differences. A case manager may notice workflow ambiguity that procurement misses, while an information specialist may identify an unnecessary data field.

Select only after the lifecycle, data, contract and exit checks are complete. Record the decision-maker, unresolved items and planned reassessment date. The decision should explain why the system fits the workload and consequence of failure, with no claim that it improves approval chances.

Before you act

Common questions

Why put mandatory controls above scored preferences?

A supplier cannot compensate for failing a mandatory control by collecting points elsewhere. Mandatory items might include a usable export, role-based access, auditable status changes and recovery of the source evidence.

Why keep documentation, tests and contract commitments in separate columns?

A feature mentioned in a sales meeting but not demonstrated or written into the agreement has unresolved evidence status. Separate columns show what is only claimed, what was observed and what the supplier is bound to provide.

What should be recorded when a system is selected?

The decision-maker, unresolved items, the reasons behind each score and a planned reassessment date. The record should explain why the system fits the workload and consequence of failure, with no claim that it improves approval chances.