Public sector
Public bodies are held to a standard of explainability that most commercial AI deployments never face. Sovereignty, procurement transparency and the ability to explain a decision to a citizen are not add-ons — they are the design constraints.
Ministries, agencies, councils and GLCs
Organisations governed by circulars rather than policies, where an officer's answer can be appealed, reviewed and published — and where the data may not be permitted to leave the country, let alone the organisation.
You will recognise yourself if
- Circulars issued faster than any officer can absorb them
- The same question answered differently at two counters
- A requirement to show the basis of a decision on request
What actually hurts
Circulars accumulate faster than they are absorbed.
Each new pekeliling amends, supersedes or partially repeals earlier ones. Working out what currently applies is genuine research, and the officer at the counter does not have time to do it.
Inconsistent answers become appeals.
Two officers, two interpretations, two different outcomes for citizens in the same position. Every inconsistency is a potential appeal, and appeals cost far more than the original enquiry.
Sovereignty rules out most of the market.
Where data must remain in-country or in-premises, a cloud AI service is not a procurement question — it is simply out of scope, and the requirement has to be designed for rather than negotiated away.
What it reads.
Published and internal instruments alike, indexed with their amendment history — because "which version applied on that date" is the whole question.
- Circulars and service instructions
- Acts and subsidiary legislation
- Departmental standard operating procedures
- Procurement guidelines and thresholds
- Grant and scheme eligibility rules
- Precedent decisions and appeal outcomes
One question, answered
A representative exchange for this sector. Every figure and instruction is traced back to the document it came from — including the revision and the date it took effect.
Applicant renewing late by four months. Is the penalty waivable and who approves it?
Late renewal beyond three months attracts a compounded fee of 30% of the licence fee.1 A waiver is available only on documented medical or bereavement grounds, and must be approved by the Director of the division, not the counter or the unit head.2 Note the approval level was raised from unit head to Director in the 2025 amendment — earlier guidance still in circulation shows the old level.2
Illustration only. This exchange is a written example of how AIMY Expert behaves — not a recording of a live system, and not a claim about any real organisation's data.
What changes, and what we would measure.
The figures below are what a deployment is scoped against, not audited results from your organisation. Each one states its basis, because a number without one is marketing.
One answer
to the same question, across every counter
Basis: consequence of a single governed index replacing local interpretation
100%
of answers cite the instrument, clause and date
Basis: architectural guarantee — required for appeal and review
In-country
or fully on-premise deployment supported
Basis: deployment option, chosen at scoping
What it means for the business
- Fewer appeals arising from inconsistent front-counter interpretation
- Officers reach the applicable circular without a research detour
- A reviewable basis for any answer given, years after it was given
- New circulars take effect at the counter on the day they are issued
Where the work usually starts.
Not an exhaustive list — these are the engagements that most reliably clear the value-versus-risk bar in this sector.
Internal policy navigation
Officers find the applicable circular and its current amendments in seconds, with superseded versions clearly marked.
Citizen enquiry assistance
Answers drawn strictly from published policy, with references the citizen can verify independently.
Grant and scheme eligibility
Criteria retrieved and explained, with the adjudication left entirely to the officer.
Records and FOI response
Faster retrieval across archives, with redaction support built in.
Designed around the constraints, not despite them.
These requirements shape the architecture from the first design session. Retrofitting them after a successful pilot is the most common reason AI programmes in this sector never reach production.
- Sovereign hosting, on-premise or national-cloud
- Complete decision auditability for appeal and review
- Accessibility conformance across all interfaces
- Open reporting on model behaviour and limitations
One organisation. Every department. This is the order.
Your organisation is in one sector, and inside it sits every department below. The platform is the same for all of them — what the sector decides is which one goes first, and that choice matters more than any model decision.
-
01 Administration Usually first
Internal circular navigation for officers — entirely internal, entirely defensible.
-
02 Legal & Compliance Then
Policy interpretation and the decision-audit record an appeal will rely on.
-
03 Customer Service Then
Citizen enquiries, once the internal deployment has a track record to point at.
-
04 Human Resources Later
Scheme rules and entitlements across a large workforce.
And then the rest of the organisation.
These departments exist in your organisation too. Once the platform is live and reviewed, each one is a scope and an evaluation set — not another procurement cycle.
What we would deploy.
If the constraints above rule out anything leaving your premises, the same platform ships on hardware you own.
Talk to someone who has shipped in public sector.
A first call is a working session, not a pitch. Bring your constraint list and we will tell you which parts are genuinely hard.