Works councils and AI meeting transcription in Germany: what international companies need to know
If your German entity has a Betriebsrat, an AI notetaker is not an IT decision. It is a negotiation, and it starts before anyone switches the tool on. Here is what applies and what the council will ask for.
If your German entity has a works council (Betriebsrat), introducing an AI meeting transcription tool is subject to co-determination. Section 87(1)(6) of the Works Constitution Act (Betriebsverfassungsgesetz, BetrVG) covers technical devices "intended" to monitor the conduct or performance of employees, and German labour courts read "intended" as "objectively suitable". Your team's lack of monitoring intent does not remove the right. In practice that means you agree the rollout with the council before the tool is switched on, not after.
On the legal side: this article is orientation, not advice. A works agreement (Betriebsvereinbarung) has to match your sites, your meeting types and your data protection concept. Get German employment counsel and involve your data protection officer early.
The statute, and the twist
Section 87(1) BetrVG gives the works council co-determination in listed matters "soweit eine gesetzliche oder tarifliche Regelung nicht besteht" (unless a statutory or collective rule already applies). Number 6 covers "Einführung und Anwendung von technischen Einrichtungen, die dazu bestimmt sind, das Verhalten oder die Leistung der Arbeitnehmer zu überwachen" (gesetze-im-internet.de, accessed September 2026).
Non-German readers usually read "dazu bestimmt" (intended) as a statement about purpose. The Federal Labour Court (BAG) reads it as a statement about capability. In its decision of 16 July 2024 on a headset system, the First Senate held that a device is "intended" to monitor when it is objectively suitable for collecting or recording conduct or performance data, and the employer's subjective intent is irrelevant (BAG, 1 ABR 16/23, accessed September 2026). A transcript is plainly suitable: it records who spoke, for how long, and who said nothing for an hour. Whether anybody plans to look does not change the analysis.
Work out who your counterpart is before the first meeting. Where a system is introduced company-wide, competence can sit with the central works council (Gesamtbetriebsrat) rather than the local ones, as the BAG held for company-wide Microsoft 365 use (1 ABR 20/21, accessed September 2026). Agreeing with the wrong body means negotiating twice.
What the council will ask for
Bring answers, not a brochure. Expect: who may start a recording, whether other participants can tell, who may read a finished transcript, where audio and text are stored, how long they are kept, whether performance can be derived from them, what automatic speaker separation (diarisation) does, what happens to live translation output, what can be exported, and whether access is logged. Diarisation and live translation are the two points teams underestimate: once every line is attributed to a person, speaking-time statistics are trivial to produce, and a translated copy doubles the data your deletion concept has to cover.
Expect the council to bring in an expert, too. Since the 2021 reform of section 80(3) BetrVG this is the statutory default whenever the council must assess AI, not a sign of distrust (section 80 BetrVG). Separately, section 90 BetrVG requires the employer to inform and consult the council in good time about planned technical installations "einschließlich des Einsatzes von Künstlicher Intelligenz" (section 90 BetrVG), meaning while alternatives are still open, not after you have signed with a vendor.
What the agreement has to do, and what it cannot do alone
A works agreement can supply the legal basis that consent in an employment relationship often cannot: it is a collective agreement within the meaning of Article 88(1) GDPR, and section 26(4) BDSG expressly permits processing employee data on that basis. This matters because individual consent is fragile here, since section 26(2) BDSG requires the employee's dependency to be weighed against how the consent was obtained.
It is not automatic, though. Article 88(2) GDPR requires suitable and specific safeguards for dignity and fundamental rights, and the agreement still has to satisfy Articles 5, 6 and, where special category data is involved, Article 9 GDPR. An agreement that permits the tool and regulates nothing else carries nothing, so never tell a team that a Betriebsvereinbarung removes the need for a lawful basis in general. It also only binds the people the council represents: once customers, candidates or external partners are in the room, the ordinary rules apply again, announce the recording, get agreement, and check the platform's terms. What to say before you record has wording you can use.
Emotion analysis in the workplace is banned, not merely sensitive. Article 5(1)(f) of the EU AI Act prohibits inferring emotions of a natural person in the workplace, except for medical or safety reasons, and has applied since 2 February 2025 (Article 5, AI Act). A vendor selling "sentiment analysis" or a "mood score" on meeting audio is describing a prohibited practice. Ask explicitly and get the answer in writing. Article 4 of the same Act, in force since the same date, also requires a baseline level of AI literacy among the people operating the system, worth a short briefing during rollout.
What you can tell the council about Kalima
Keep it factual; marketing language works against you in this room. Recording runs on the device of the person who starts it; Kalima does not join the meeting as a participant, so nobody extra appears in the list, but the duty to tell the room sits with that person, not the software. A session belongs to whoever recorded it, stays private until actively shared, and sharing can be revoked at any time; organisation roles govern member management and billing, not blanket read access to other people's recordings (roles and permissions). Employees can delete their own sessions, request their data, and delete their account (your data and privacy). Audio and transcripts sit in the EU, connections are encrypted, and nothing trains a model (trust and security). Kalima sets no automatic deletion period, so a retention period in your agreement is a process someone on your side has to own.
There is no emotion or sentiment detection, and no scoring, ranking or rating of individuals. Two features deserve an honest mention regardless: speaker separation can attach real names to voices, and an AI summary can list who contributed what once names are assigned. Both are useful, and both are exactly what a ban on performance analysis is aimed at.
Frequently asked questions
Does this apply if only a few employees use the tool for their own meetings?
Once the employer tolerates, procures or pays for the use, there is a strong argument this is an "introduction and application" under section 87(1)(6) BetrVG regardless of who presses the button. It changes what the agreement should say, not whether you need one.
Can we rely on employee consent instead?
Consent is weak in an employment relationship and answers a different question. Data protection law governs whether you may process the data; the Works Constitution Act governs whether you may introduce the system. One does not substitute for the other.
What happens if we cannot reach agreement?
Under section 87(2) BetrVG a conciliation committee (Einigungsstelle) decides, and its ruling replaces agreement between the parties. Proceeding without the council is not only risky, it is usually slower.
Does a US or UK parent company change anything?
No. Co-determination attaches to the German establishment regardless of where the decision was made. Budget several months for the German entity in any global rollout plan.
We have no works council. Are we done?
Co-determination falls away; nothing else does. The GDPR applies unchanged, § 201 StGB still protects the spoken word, and the AI Act ban on workplace emotion recognition still applies. A written usage policy is worth having anyway.
Related
Try Kalima on your next call.
Live transcription and translation, no bot in the meeting. Free to start.
Keep reading.
Your Company Blocked AI Notetakers. What You Can and Cannot Do Next
A blocked notetaker is either a switched-off transcription policy, a lobby that refused a bot, or a network that refuses the service itself. Only one of those is about something joining your call, and only one is a question you can answer without asking somebody first.
Can you record a job interview? Consent, state law and the AI Act question nobody answers
Five vendor blogs answer this with a state list and a consent form. None of them mention that a voice recording can trigger a biometric statute, none cover an EU employer interviewing a US candidate or the reverse, and none say what happens to the recording after the decision is made.
The Google Meet Transcript Exists and You Still Cannot Open It
You were in the meeting, the transcript was made, and Drive still shows you a Request access screen. Meet ties the transcript to the Calendar invite, cuts off meetings with more than 200 invitees, and leaves external guests out entirely. Here is each rule, and why the file came out in the wrong language.