Ownership
Name the service owner
Keep service ownership clear from the first meeting. If a pilot has no person accountable for its output, escalation and correction both stall.
AI in the public sector — Estonia, 2026
Estonian public services use tehisintellekt in visible and careful ways. This page outlines citizen-facing help and the governance thinking behind it, using two documented RIA references: Bureaukratt and Reason Reserve.
The assistant citizens meet
Bureaukratt, developed by Estonia's Information System Authority (RIA), is positioned as a virtual assistant for citizens. It is part of Estonia's broader public-sector AI push into government services. Residents meet it inside official channels when they need direction to the right service or form.
Across the last few years the emphasis has moved from announcing AI projects to explaining what a person can actually do with them. Bureaukratt sits on the citizen side of that shift — a service that answers "which form, which office, which counter", and hands the visitor back to the official channel rather than becoming one.
We treat it as a documented reference, not a product we operate. Our summaries name the source, note the date we last checked the official wording, and stay quiet on anything the Information System Authority has not published itself.
Practice notes for staff
Secure use by design — RIA innovation project
Reason Reserve is listed by RIA as an innovation project for secure AI use in the public sector. It focuses on enabling AI assistants across government systems and sits at infrastructure level.
It is framed as a controlled environment rather than a consumer app. That framing matters: testing, access rules and review come before wider release. It shows how national initiatives pair service goals with AI governance. For anyone writing a tender or a policy note, the useful question is not "which model runs it", but "who signs the access decision, and where is it recorded".
What this means for local offices
Saue vald and the wider Harju maakond area run the same kind of front counter as the ministries do. The questions that decide whether a pilot survives year two are ordinary ones.
Ownership
Keep service ownership clear from the first meeting. If a pilot has no person accountable for its output, escalation and correction both stall.
Guidance
When guidance changes, update the source the same day. Citizens compare counters and phone scripts; stale wording is what erodes trust in a service.
Audit trail
Keep a log of automated replies that staff can audit. A record staff can read back is what lets a municipal office answer a query two weeks after it was given.
Consistency
Citizens trust consistency more than speed. A slower reply that matches the published rule reads better than a fast one that contradicts it.
How to follow national initiatives well
National programs in healthcare, education and government services move in stages. Read official RIA pages for status, scope and entry points. That habit avoids confusion between announcements and available services. We update our own summaries when official wording changes.
Note what is live, what is testing, and what is planning. When a programme moves between those stages, our summary of it moves with the official wording.
Questions we hear from public teams
Teams ask about data handling, review roles and citizen redress. Our guidance stays general and practical, and it applies to municipal and central offices alike.
If a use case cannot name its reviewer, it is not ready for citizen contact.
Read how we verify informationA pilot that collects more fields than its task needs is harder to explain in a review. Take the minimum, and write down why each field exists.
Reviews work when the role is written into the process. A pilot without a named reviewer for automated output stays in internal testing.
At any point a citizen should be able to reach a person instead of an assistant. That path is part of the service, not an exception to it.
Keep privacy notices easy to find, in plain language, next to the service they describe rather than three clicks deeper in the footer.
Where this page closes
Each cell names something you can check yourself against official RIA wording before you act on it.
Straight answers
The two references on this page get confused often. The distinction matters if you are writing about services or briefing a committee.
Still have a question about public-sector AI in Estonia, or about how a pilot in your office should be reviewed?
No. Bureaukratt is described as a citizen-facing virtual assistant developed by RIA. Reason Reserve is described as an innovation project for secure AI use across government systems. One is the service people see, the other supports safe deployment behind it.
Use Estonian government sites and official apps for service tasks. They carry current instructions and correct entry points. Our pages explain context, they do not replace official service channels.
How we keep this page honest
We cite only RIA material we can point at, note when the official wording last changed, and keep our summaries short of anything the authority has not published. When RIA pages move, our wording moves with them — a date we can name beats a claim we cannot.
More about BOLTCAT OÜ
Secure adoption is a process, and a process can be checked.