In this article8 sections
  1. Public bodies are not spectators in the EU AI Act
  2. Why public sector deployers face stricter rules
  3. The mandatory Fundamental Rights Impact Assessment
  4. Citizen-facing transparency: what Article 50 requires
  5. Procurement: the hidden compliance problem
  6. What this means for government employees day to day
  7. Register, monitor, and report
  8. References

Public bodies are not spectators in the EU AI Act

AI act public sector compliance is not optional, and it is not a distant concern. Under the EU AI Act, government bodies that deploy AI systems carry obligations that are, in several cases, heavier than those placed on private-sector deployers of equivalent tools. If your municipality uses an automated scoring system to prioritise social benefit applications, or your ministry deploys an AI tool to assess permit eligibility, you are in scope. The question is whether you are prepared.

The Act entered into force on 1 August 2024. The first hard deadline, covering prohibited AI practices under Article 5, passed on 2 February 2025. High-risk obligations, including Article 26 and the FRIA, apply from 2 December 2027 for Annex III systems. High-risk systems already in use by public authorities before then must comply by 2 August 2030. That is not far away for organisations that run on procurement cycles measured in years.

Why public sector deployers face stricter rules

The EU AI Act classifies AI by use: systems used for the purposes listed in Annex III are high-risk, unless a narrow exception in Article 6(3) applies. Many of those uses are typical of public authorities. They include AI used in the administration of justice and democratic processes, essential private and public services, law enforcement, migration and border control, and the management of critical infrastructure.

Consider what this covers in practice. A Dutch gemeente (municipality) using AI to rank social assistance claimants is in Annex III. A regional employment service using AI to match jobseekers to vacancies: also Annex III.

This matters because high-risk deployers carry obligations under Article 26 that go well beyond simply turning a tool on. From 2 December 2027, you must use the system according to its instructions, assign competent human oversight, keep logs, and monitor how it performs. Already today, Article 4 requires you to take measures to support the AI literacy of the staff who use it. You also bear direct responsibility for the decisions the system informs, even if a private-sector vendor built the model.

The mandatory Fundamental Rights Impact Assessment

This is the obligation that catches most public-sector organisations off guard. From 2 December 2027, Article 27 requires certain deployers of high-risk AI systems to carry out a Fundamental Rights Impact Assessment (FRIA) before putting the system into use. It applies to bodies governed by public law, private operators providing public services, and deployers who use AI for credit scoring or life and health insurance pricing.

A FRIA is not a checkbox exercise. It requires you to identify which categories of people are affected by the AI system, assess how the system could produce discriminatory or disproportionate outcomes, and document what safeguards are in place. You must consider intersecting characteristics: age, disability, ethnicity, gender, and socioeconomic status all warrant examination.

Article 27(3) requires the deployer to notify the market surveillance authority of the results, and public bodies must register their use of the system in the EU database (Art 26(8), Art 49(3)). In the Netherlands the AP is the intended supervisor under the draft implementing law; it has no AI Act powers until that law is in force.

If your organisation has already conducted a GDPR Data Protection Impact Assessment (DPIA) for the same system, you do not start from zero. Since the AI Omnibus, the FRIA may cross-reference the relevant parts of the DPIA (Art 27(4)), and the AI Office is developing a questionnaire template (Art 27(5)). But the DPIA alone does not satisfy Article 27. A FRIA has a broader scope, examining fundamental rights beyond privacy, including the right to effective remedy under Article 47 of the EU Charter and the right to non-discrimination under Article 21.

Citizen-facing transparency: what Article 50 requires

When a public body deploys AI in a way that interacts directly with citizens, Article 50 applies. Citizens must be informed that they are interacting with an AI system, not a human, unless this is obvious from context.

This is not about adding a footer to a webpage. If your municipality operates an AI-powered chatbot handling benefit queries, or a virtual assistant managing appointment scheduling, the disclosure must be active and clear at the latest at the first interaction. The provider must build the notice in; you must not disable it.

For decisions that significantly affect citizens, transparency goes further. Under Article 86, people subject to a decision based on the output of a high-risk AI system listed in Annex III, with legal or similarly significant effects on them, have the right to a clear and meaningful explanation of the role the AI played. Public authorities are not exempt from this; they are directly bound. The right is tied to high-risk systems, whose rules apply from 2 December 2027 (Annex III).

Plan for it now. If your housing department uses AI to score social housing applications, rejected applicants can request an explanation of the AI-assisted decision. Your staff need to be able to provide one. That requires both the vendor's instructions for use and trained human reviewers who understand the system's outputs.

Procurement: the hidden compliance problem

Many public bodies assume their vendor carries the compliance burden. This is not how the AI Act works. Deployers are responsible for what they deploy.

When a central government ministry or regional authority procures a high-risk AI system, it should verify that the system has gone through the conformity assessment required under the Act (from 2 December 2027 for Annex III systems). That means checking for a CE marking and EU declaration of conformity, that the system is registered in the EU database established under Article 71, and that instructions for use are supplied (Art 13). Public bodies may not use an unregistered high-risk system (Art 26(8)).

Current public procurement frameworks in most EU member states were not designed with these requirements in mind. Tender documents typically specify functional requirements and price. They rarely include clauses requiring vendors to provide conformity assessment records, technical documentation under Article 11, or audit log access under Article 12.

The practical fix is to build AI Act compliance requirements into your procurement specifications now. From now on, every new AI-enabled contract your organisation signs should include: a warranty that the system meets Annex III obligations where applicable, contractual access to technical documentation, notification obligations if the vendor modifies the model, and the right to audit logs for the duration of the contract.

What this means for government employees day to day

Government employees who use AI tools in their work fall under the Article 4 AI literacy obligation. Article 4 requires measures to support staff AI literacy; for high-risk systems, Article 26(2) (from 2 December 2027) requires overseers with the necessary competence, training and authority.

In practice, this means HR and learning and development teams in public bodies need to design and document training programmes for AI-using staff. Good training covers what the system does, how it reaches outputs, where it can fail, and how to escalate concerns. Keep records of the training: they are your evidence.

For front-line staff in social services, employment agencies, immigration services, and justice administration, this is especially pressing. These are the employees whose daily decisions are most directly shaped by AI-generated recommendations. They must be equipped to apply meaningful human oversight, as required by Article 26(2). An employee who rubber-stamps every AI output without review is not fulfilling that obligation, and neither is the organisation that trained them to do so.

Register, monitor, and report

Once a high-risk AI system is deployed, the obligations do not stop. Public-sector deployers must monitor systems for performance changes and inform the provider and the authority of serious incidents (Art 26(5); Article 73). Fines reach €35 million or 7% for prohibited practices and €15 million or 3% for other duties, per Article 99. Whether public bodies can be fined is for each Member State to decide (Art 99(8)).

Keep an up-to-date inventory of every AI system your organisation uses. Classify each one against Annex III. Where a system is high-risk, assign a named internal owner, prepare the FRIA, and set a calendar reminder for annual review.

Start with your inventory today. If you are unsure which of your current AI tools are in scope, run a free 2-minute compliance check at comply.khairos.ai to get an immediate picture of where your organisation stands before the high-risk rules apply on 2 December 2027.

References

  1. Article 5

  2. Article 26

  3. Annex III

  4. Article 4

  5. Article 27

  6. Article 50

  7. Article 86

  8. EU database

  9. Article 73

  10. Article 99

  11. comply.khairos.ai

Not sure where your company stands?

Answer 15 questions about how your team uses AI. You get a compliance score and the gaps to close first, as a PDF.

Am I compliant? Check in 2 minHow Khairos Comply works