Workshop · Municipalities & government

AI workshop for municipalities.

A tailored AI workshop for municipal organisations, aligned with the AI Act, the BIO, the Algorithm Register obligation and the administrative reality of public decision-making. No generic training, no vendor pitch: a session run by people who build AI systems for the public sector and understand what an objection procedure or a Wmo (Social Support Act) application involves.

AudienceCivil servants & administrators
SectorMunicipality · government
FormatIn-house or online
LanguageDutch
ModulesSeven public-sector blocks
CustomPer municipality

What is an AI workshop for municipalities?

An AI workshop for municipalities is a half-day or full-day session in which we take a municipal organisation through the practical, legal and ethical sides of AI in public-sector work. We deliberately work with examples from municipal processes — Wmo (Social Support Act) case handling, objection handling, preliminary permit assessments, council documents — and not with generic corporate use cases. For government, AI is a considerably stricter game than for private organisations: the EU AI Act classifies many public-sector applications as high-risk by default, the Algorithm Register demands active transparency, and the Baseline Information Security Government (BIO) sets tight limits on data processing.

We design every workshop around the current legal reality of a municipality, not around the marketing of a tool vendor. We spend as much time on the AI Act, the Algorithm Register and the DPIA obligation as on prompt engineering or ChatNL. We are also honest about when an AI application in the public sector simply won't clear the legal bar — for example, when a social-domain algorithm risks making the same mistakes we know from SyRI and the childcare benefits scandal.

The second distinguishing feature: we come from software development, not from management consultancy. We build custom software for municipalities ourselves and know how BIO-compliant infrastructure is put together, how DigiD and eHerkenning integrations work, and what separates a production system from a prototype. Our examples come from code, not from a slide deck.

We build the content from seven blocks: an up-to-date picture of AI in 2026, the AI Act and the Algorithm Register for municipalities, BIO and GDPR overlap, bias evaluation for social-domain algorithms, a responsible-AI framework, hands-on prompting for local policy tasks, and a closing roadmap. Which blocks are covered, and in what proportion, depends on the audience. A session for the CIO office and legal affairs puts more weight on compliance; a session for customer contact, communications or policy advisers leans more towards the hands-on and use-case side. For longer-running programmes, we refer you to our AI implementation programmes, in which we follow up the workshop with guided pilots.

What we don't do: pretend the AI Act is a non-binding framework. For public organisations, the time for "we'll see" is over — legislators, the Dutch Data Protection Authority and the Netherlands Court of Audit no longer accept it. A good workshop ensures your organisation doesn't just know what AI can do, but also gets a clear view of the accountability chain that comes with it.

AI Act + Algorithm Register
Two parallel obligations — we treat them as one coherent governance challenge
BIO-aware
How to run AI experiments without undermining your information security status
Public sector focus
Examples from municipal processes — not generic corporate cases
Vendor-independent
No reseller deal with Microsoft, OpenAI or Google — honest advice per use case

When is this workshop relevant for your municipality?

01
Obligation

AI Act literacy (Art. 4) must be demonstrable

Since February 2025, Article 4 requires all staff who work with AI systems to be sufficiently AI-literate. For municipalities, that applies not only to CIOs and data specialists, but also to civil servants in civil affairs, social services, permits and communications. A targeted workshop is a pragmatic way to build that literacy for an entire department at once — and to document it in a report you can show to a regulator if needed. See also our standalone AI literacy training.

02
Algorithm register

Your municipality has to register algorithms and make them explainable

The Algorithm Register requires municipalities to publicly register high-impact algorithmic decision-making systems, with explainable information on how they work, the dataset used and how to object. Many organisations don't yet know which of their existing systems fall under this obligation. The workshop kicks off that mapping internally.

03
Leadership

The council or the mayor and aldermen ask for an AI direction

The municipal council sees neighbouring municipalities experimenting with chatbots, objection classification or generative AI for council documents, and wants to know where its own municipality stands. A management team or leadership session provides the framework for making strategic choices, without councillors and aldermen first having to work out for themselves what the AI Act or the Algorithm Register means.

04
Social domain

You're considering AI in social services

Social support (Wmo) applications, youth care, debt assistance, enforcement — seemingly logical AI applications are everywhere, but so are the lessons from SyRI, the childcare benefits scandal and municipal risk-profiling projects. A workshop with serious bias evaluation and public-values assessment prevents a municipality from building itself into a new scandal. This isn't a distant risk: it is the central test for every high-risk application.

What sets our workshop for municipalities apart.

Difference 01

Builders with public sector experience

We build custom software for municipalities and know the difference between an ordinary SaaS integration and a BIO-compliant architecture with DigiD/eHerkenning, archive integration and objection-procedure logic. The examples come from real municipal work, not from a generic corporate sample set.

Difference 02

Vendor-independent and critical

No partnership with Microsoft, OpenAI, Google or the big consultancy firms. We give you an honest picture of what ChatNL, Copilot, Claude or an open-source model such as Mistral means for your situation — including data residency, vendor dependency and whether a self-hosted solution is sometimes wiser than a hyperscale API.

Difference 03

Code ownership as a principle

What we recommend is in line with how we work ourselves: the municipality owns the code, no vendor lock-in, transparent data flows. For regulators, councillors and auditors, that is a much easier story than an AI running as a black box at an external party — especially when a resident soon asks for an explanation of a decision.

Seven modules — built for municipal practice.

These modules are the building blocks. We combine them depending on your audience, the format (half day, full day or multi-day) and the scoping conversations beforehand. There is no fixed script, but there is a solid substantive foundation.

Module 1 — AI in 2026

The current state of LLMs, RAG, agents and multimodal models. What is hype, and what can realistically be deployed in a civil service context. Includes an overview of ChatNL and EU-focused models.

Module 2 — AI Act & Algorithm Register

What the European AI Act and the Dutch Algorithm Register obligation mean in practice for your municipality. Risk classification, registration duty, transparency, human oversight.

Module 3 — BIO & GDPR DPIA

How an AI experiment relates to the Baseline Informatiebeveiliging Overheid (BIO, the Dutch government information security baseline). When an adapted DPIA is needed. What a data protection impact assessment looks like for municipal AI specifically.

Module 4 — Bias evaluation

Lessons from SyRI, the childcare benefits scandal and municipal risk profiling. How to test a social domain algorithm for proxy discrimination, and how to build a feedback loop with the target group itself.

Module 5 — Responsible AI framework

Translate the concepts from the AI Act, the Algorithm Register and internal frameworks into a workable decision-making structure for your municipality: who approves what, at which moment, with which documentation requirements.

Module 6 — Hands-on prompting

Practical work on official documents — policy memos, council papers, letters to residents, draft decisions. Working with ChatNL and frontier models within what is permitted on your workplace.

Module 7 — Roadmap for your municipality

To finish, we design a first roadmap together: which pilots, which registrations in the Algorithm Register, which governance structure, which short-term investments and which longer-term lines.

Pre-workshop scoping

A conversation with the CIO, legal affairs and the subject-matter lead. Which departments, which sensitivities, which recent decisions by the mayor and aldermen or the council are relevant. Based on that, we put together the programme.

Which roles within your municipality is this workshop for?

Municipalities are broad organisations with very different relationships to AI. We have designed the modules so that we can shift the emphasis per target group — sometimes a session per role group, sometimes a mixed day with sub-sessions.

Civil affairs & contact centre

Civil affairs, customer contact and public services

Staff who help residents every day with applications, questions and objections. Focus: safe prompting for generating letters to residents, the difference between an official decision and an AI suggestion, handling personal data within the BIO.

Social domain

Social support, youth, participation, debt assistance

A domain where AI can in theory do a lot, but in practice has to be handled with extreme care. Focus: bias evaluation, lessons from SyRI, when a social domain algorithm counts as high-risk under the AI Act, and what a DPIA and Algorithm Register entry look like.

Spatial planning & permits

Spatial planning, environmental services, permits

Permit processing, BAG data, zoning plans, the environmental plan. Focus: AI for preliminary research, support with large case files, the link with DSO integrations and what the Environment and Planning Act requires in terms of transparency.

Communications & governance

Communications, press office, executive secretariat

Press releases, council letters, summaries of council papers, social media. Focus: hands-on prompting for public-facing language, fact-checking, and how AI generation can support official neutrality and care without undermining them.

Legal & CIO

Legal affairs, CISO, CIO office

Strategic owners of compliance, security and architecture. Focus: AI Act classification, the Algorithm Register process, DPIA template, BIO impact, supplier assessment, model risk and in-control statement.

Executive & council

Mayor and aldermen, councillors, council clerk's office

Political and executive decision-makers who take strategic decisions on AI investments and the associated risks. Focus: setting frameworks, auditability, public accountability, council powers in AI decisions.

Municipal use cases we cover.

During the workshop, we work with use cases that municipalities will recognise. We don't present them as "success stories" — for some we are deliberately cautious — but as concrete situations to apply legal, technical and ethical analysis to. That is more instructive than an abstract discussion about "AI possibilities": participants discover for themselves where the line falls between a useful assistant and a high-risk system.

A first classic is WMO application triage. A municipality wants to shorten processing times by having AI assist with incoming applications: completeness checks, an initial indication of the allocation category, and automatic requests for missing information. The question is not whether this is technically possible — it is — but under what conditions it is permissible. A suggestion to the case handler is fundamentally different from an automated preliminary decision. We go through what that distinction means for the DPIA, for the Algorithm Register and for the objection procedure.

A second is objection classification. AI supports the sorting and summarising of incoming objections so that the legal department can respond to the substance more quickly. Here the bias question comes straight to the table: a classification that weighs postcode, surname or writing style can unknowingly push entire groups of residents to the back of the queue. We cover which evaluation steps are mandatory before such a system may go into production — and how you keep monitoring it afterwards.

A third is permit pre-screening. A spatial planning department has AI carry out a first check on a permit application: complete documentation, an indicative test against the zoning plan, flagging of risk areas. There are opportunities here, but also pitfalls — an incorrect pre-screening conclusion can wrongly send an application down the wrong track. We discuss the architecture that makes such a system auditable, including integrations with BAG, DSO and the archive.

A fourth is summarising council documents. A clerk's office or executive secretariat uses AI to draft summaries of council documents, mayor and aldermen letters or implementation documents. This is a relatively low-risk application — no decision is made about a resident — but it does come with points of attention around accuracy, hallucination and political bias. We practise with prompts that make the output more usable and easier to verify.

A fifth, and the most critical, is a civil affairs chatbot. Many municipalities are experimenting with them, but under the AI Act a chatbot that answers questions about residents' rights and obligations quickly becomes a high-risk system. We discuss the conditions under which such a chatbot can be justified, what a safe scope looks like, and what alternatives exist — for example, an internal assistant for customer contact centre staff instead of AI that residents interact with directly.

Sixth, we cover generating customer letters and decisions: AI as an assistant for staff who regularly have to draft letters and standard replies. Combined with human review and checked for plain language, this generally saves time without major legal risks. Do pay attention to archiving and traceability of AI contributions.

These use cases serve as analysis material. We go through each case in terms of AI Act classification, BIO requirements, Algorithm Register implications and practical feasibility. By the end, your team has a shared view of what it makes sense for your municipality to investigate first — and what it does not (yet).

How we work on compliance and public accountability.

Pillar 01

AI Act classification first

For every application we discuss, we start with the classification under the AI Act. Prohibited, high-risk, limited risk, minimal — and what the consequences are for your municipality. For most public-sector applications, the bar is higher than in the private sector.

Pillar 02

Algorithm Register discipline

We walk through which of your existing and planned systems belong in the Algorithm Register, what information you need to include, and how to build explainability for citizens and councillors without writing a PR text.

Pillar 03

Handling BIO and GDPR together

Many municipal AI questions sit at the intersection of BIO and GDPR. We treat them as a single governance issue — data flows, authorisations, DPIA extension, records management — rather than two separate chapters.

Lessons from SyRI and the childcare benefits scandal.

There is no responsible AI workshop for the public sector without an honest conversation about SyRI and the childcare benefits system. Algorithmic decision-making that failed on several levels at once: technically (proxy discrimination, lack of evaluation), in its legal embedding (no DPIA in the spirit of the law) and in administrative accountability. What began as "more efficient enforcement" became a mechanism that disproportionately and unlawfully affected entire groups of citizens.

The relevance is immediate: the technology now in the hands of any policy adviser — generative AI, automated text analysis, classification models — is far more accessible than the SyRI infrastructure ever was. That widens the risk. A good AI programme ensures that every new application undergoes a serious assessment: which variables, which proxies, which exclusion effects, which feedback loop with the target group, which explainability, which options for objection.

We don't treat those lessons as a cautionary paragraph but as an assessment tool: a set of questions we put alongside every AI use case. By the end of the workshop, your team has that assessment in hand — not as a form that disappears into a drawer, but as a habit. For municipalities that work with this type of decision on a structural basis, it ties in with our broader practice in AI consultancy.

Format options for your organisation.

Format 01

In-house at your town hall

We come to your town hall with a team of two. Suitable for dedicated sessions with a department, a management team or a broader group with representatives from different domains. A room with a projector and a laptop per participant is enough.

Format 02

Online with recording

A live video call for distributed teams, also useful for regional partnerships in which several municipalities take part. Hands-on blocks work in your own browser; a recording is available for absent colleagues.

Format 03

Series of half days

For larger organisations, sometimes better than one long day: a series of, say, three half-days in which we serve the target groups separately — CIO/CISO and legal affairs in session one, social services and civil affairs in session two, communications and leadership in session three.

How an engagement works in practice.

It starts with an intake conversation — usually with the lead on the subject matter, a representative from the CIO portfolio and someone from legal affairs. We discuss the target group, existing AI activities, the Algorithm Register process, ongoing DPIAs and relevant decisions of the mayor and aldermen or the council. Based on that, we propose a programme with modules, format and schedule — sent in advance, so nobody has to guess what is coming on the day itself.

The workshop then takes place. We work in clear blocks: a short introduction to the subject matter, a longer hands-on or analysis exercise, and at the end a first outline of a follow-up roadmap. For the hands-on blocks, we ask in advance which official documents you would like to use — a draft decision, a council paper, a set of citizen queries or a policy memo — and build the exercises around them.

Afterwards, you receive a written wrap-up: which modules were delivered, which participants attended, which priorities came up and which follow-up steps we agreed. That material can be used as documentation for the AI literacy obligation under Article 4 of the AI Act, and as a starting point for an Algorithm Register mapping. For ongoing programmes, we link up with an AI implementation programme or with our municipal software practice.

For us, the workshop is a starting point, not an end goal. For some municipalities that is enough: a solid foundation, a shared understanding and a set of follow-up questions for their own management team. For others it becomes the reason to keep going: a first pilot, an Algorithm Register process or an extension of existing municipal software with an AI component. Both outcomes are legitimate; we won't steer you towards a follow-up project if it isn't needed.

Frequently asked questions.

Does the AI Act apply to municipalities too?
Yes, and more strictly than for many private organisations. The AI Act treats public decision-making as a sector where AI systems more readily fall into the high-risk category. Social domain applications, fraud detection, enforcement, permit classification, biometrics and migration/asylum processes are explicitly named. In addition, the AI literacy obligation under Article 4 applies to all staff who work with AI, in municipalities as well as central government bodies and implementing organisations.
What is the difference between the Algorithm Register and the AI Act?
They are two parallel obligations that partly overlap. The AI Act is European legislation that classifies AI systems by risk level and imposes corresponding obligations. The Algorithm Register is a Dutch transparency obligation under which municipalities and other public bodies publicly register their high-impact algorithmic decision-making systems, including an explanation that citizens can understand. A system can fall under both frameworks, in which case you need to complete both. In the workshop we treat them as one coherent governance question, because that is more workable in practice than running two parallel processes.
Can a municipality use ChatGPT or Claude at all?
It depends on the use case and the configuration. For general productivity tasks (summarising meeting minutes, drafting texts, open-ended searches) it can usually be set up properly, provided you use the right type of licence (business, with no training on your input), don't share personal data you aren't allowed to share, and have clear working agreements. For supporting decisions that affect citizens, much higher thresholds apply, and a ChatNL-style Dutch or EU-hosted solution or a privately hosted open-source option is often the wiser choice. In the workshop we cover this scenario by scenario, including the impact on the BIO and the overlap with the GDPR.
What do you cover on bias and public values?
A whole module. We go through what bias is technically (skew in training data, proxy variables, evaluation blind spots), how it shows up specifically in the public sector (think of SyRI, the childcare benefits scandal and municipal risk profiling), and which evaluation and monitoring steps you should build in. This is not an abstract talk about bias: we work through concrete social domain use cases with you to practise the assessment questions. For municipalities that work with social algorithms on a structural basis, we recommend a follow-up AI consultancy engagement alongside the workshop.
Does this suit regional partnerships?
Yes, and it is often particularly efficient. Municipalities in a partnership, for example in the social domain, ICT or taxation, face comparable AI questions. A joint workshop with participants from different organisations not only gives you a shared foundation, but also room to discuss coordination questions (joint supplier assessment, a shared Algorithm Register approach, common DPIA templates). This works well in the online format; in-house with several municipalities is also possible, at a central location.
How many participants take part?
It depends on the format. Hands-on modules work best with groups of roughly six to twelve participants: large enough for exchange between participants, small enough that everyone gets a turn. Board sessions actually work better in a smaller setting. For larger organisations we split the group up or run the same module several times. We'll agree the exact split during the intake.
Do participants need technical knowledge?
No. We start every module with a short levelling exercise and adjust the pace to the group. For the hands-on blocks a working laptop is handy, plus access to an AI tool that your municipality provides (for example ChatNL, Copilot or a comparable business solution). We provide instruction during the session itself — nobody is overwhelmed with technology before they can place it in context.
Does this workshop cover the AI Act literacy obligation?
Yes, for the session's participants. Modules 1, 2, 3 and 5 together amply cover what Article 4 minimally requires. You receive a written report stating which modules were delivered, who took part and what level was reached — usable as documentation for a regulator. For refresher training, new employees or departments we haven't seen, we often recommend an additional AI literacy training as a recurring programme.
What is the difference from a general AI corporate training?
Our general AI corporate training is broader and sector-independent: AI strategy, prompt engineering, AI Act compliance, technical deep-dives for development teams, and sector modules on request. The municipality workshop on this page is a specific variant with a public-sector context: the Algorithm Register, the BIO, high-risk classification in public decision-making and bias evaluation of social algorithms are not separate modules but the common thread. If you work in a municipality, this variant is the right one; if you work in a private organisation with government as a client or as part of the context, we'll look together at which combination fits.
What happens after the workshop?
You receive a written wrap-up with priorities, agreements made and recommended next steps. Optionally, we schedule a follow-up sparring session to look at how the first experiments are landing. For municipalities that want to continue — a first pilot in the social domain, an AI application in civil affairs, an Algorithm Register programme or a broader transformation — we connect to an AI implementation programme, an AI consultancy engagement or our municipal software practice. There is no obligation after the workshop — some municipalities do one session and continue on their own, others work with us for years.

Talk to us about an AI workshop for your municipality.

A half-hour introduction in which we go through which departments will take part, which Algorithm Register work you already have under way and where the first need lies. Afterwards we send a concrete proposal with modules, format and planning.

Reply within 1 working day
No-obligation conversation
Westerdoksdijk 599, Amsterdam
Share LinkedIn Email

Edit content