Works Council (Betriebsrat) Engagement Guide

📘
About this guide
This guide helps Leena AI customers and their implementation teams prepare for and navigate the works council (Betriebsrat) co-determination process required under German law when introducing AI-driven HR technology. It covers the legal framework, what the works council has the right to review, common questions you will be asked, and how to answer them accurately and confidently.

01 · Why This Matters

The Legal Obligation

In Germany, the Works Constitution Act (Betriebsverfassungsgesetz, BetrVG) gives elected works councils (Betriebsräte) enforceable co-determination rights over the introduction and use of technical systems capable of monitoring employee conduct, performance, or behaviour. Leena AI — as an AI-powered HR assistant that processes employee queries and interactions — falls within the scope of BetrVG §87 and §80.

Co-determination is not a procedural formality. Works councils have the right to:

Request complete technical documentation before the system goes live
Negotiate a Betriebsvereinbarung (works agreement) governing the system's use
Block deployment until their concerns are addressed
Engage independent technical expertise at the employer's cost (§80 Abs. 3)

⚠️
Key principle
Works council engagement should begin during the design and configuration phase — not after deployment decisions are locked in. Early involvement reduces legal risk, builds trust, and improves adoption outcomes.

Relevant Legal Provisions

Provision	Relevance to Leena AI Deployment
BetrVG §87(1)(6)	Co-determination right over the introduction and use of technical devices designed to monitor employee conduct or performance. Applies to any system that logs, processes, or could process individual-level interaction data.
BetrVG §87(1)(1)	Co-determination right over rules of conduct and order in the workplace — including acceptable use policies for AI tools.
BetrVG §80(1)(1)	General monitoring right to ensure that laws, works agreements and other regulations in favour of employees are observed.
BetrVG §80(2)	Employer must provide information and documentation necessary for the works council to carry out its tasks — including system architecture, data flows, and vendor contracts.
BDSG / GDPR Art. 88	Processing of employee personal data requires a legal basis — typically a works agreement or individual consent. Conversation logs and usage analytics are personal data.
DSGVO Art. 35 (DPIA)	A Data Protection Impact Assessment is required where data processing is likely to result in high risk to individuals — AI-driven HR tools typically meet this threshold.

02 · What to Prepare Before First Engagement

Documentation the Works Council Will Expect

Before or at the first formal works council session, the employer should be prepared to provide:

✅ System overview — What Leena AI is, its purpose, and the specific use cases being deployed
✅ Data architecture — What employee data is accessed, where it is stored, how long it is retained, and who has access — including the vendor
✅ Integration map — How Leena AI connects to existing systems (e.g. SAP HCM, Active Directory, identity provider)
✅ Conversation logging policy — Whether and how employee queries are recorded, at what level of granularity, and access controls
✅ Monitoring capability declaration — A clear statement of whether the system is technically capable of profiling individual behaviour, even if that capability is currently inactive
✅ Access and channel plan — Which employee groups can use the system, through which channels (desktop, Teams, mobile app), and how frontline or non-desk workers are included
✅ Data Processing Agreement (Auftragsverarbeitungsvertrag) — The contractual terms with Leena AI as a vendor, including data residency and exit provisions
✅ DPIA status — Whether a Data Protection Impact Assessment has been completed or is in progress
✅ Knowledge base governance plan — Who maintains content, how accuracy is assured, and the approval process for legally sensitive topics

Configuring Leena AI to Support Co-determination

Several Leena AI configuration decisions directly affect works council requirements. These should be resolved before the first formal session.

Data minimisation

Configure Leena AI to surface only data the requesting employee is already authorised to view under the permission architecture of connected systems (e.g. SAP role assignments). Do not expose data beyond existing access rights.

Logging and analytics

Define clearly which interaction data is retained. Aggregate query volumes, topic categories, escalation rates, and satisfaction signals are generally supportable. Individual-level conversation transcripts linked to identifiable employees are the trigger point for BetrVG §87(1)(6) rights — and must be explicitly negotiated in a works agreement.

Escalation and fallback

Ensure the system always offers a clear, accessible route to a human HR contact. This is both a works council expectation and a design quality requirement. Configure automatic escalation for queries classified as sensitive (complaints, disability, distress).

Channel governance for BYOD and frontline access

If Leena AI is to be delivered through a BYOD-dependent channel (such as a mobile employee app), ensure that the relevant data privacy and ISO approvals are in place before including that channel in works council discussions. Committing to a channel that lacks approvals creates credibility risk and may delay the process.

03 · Anticipated Questions & Recommended Answers

The questions below reflect what works councils typically ask when AI-driven tools are introduced into HR service delivery. Answers are written from the perspective of the employer (Leena AI customer) — not Leena AI as vendor. Adapt them to reflect your specific configuration and any commitments made during the procurement process.

Understanding the System

Q1. What exactly is Leena AI? What can it do — and what can't it do?

Leena AI is an AI-powered HR assistant that answers routine employee questions and, for configured use cases, initiates transactions such as leave requests or document submissions — available 24 hours a day, without requiring a phone call or waiting for HR office hours. It handles repetitive, high-volume queries so HR colleagues can focus on complex cases that require human judgement.

What it cannot do: override a manager decision, amend an employment contract, or take any action that bypasses existing approval workflows. Every write-back to a system of record (such as SAP or Workday) still goes through the same validation and approval logic that exists today. That boundary is designed into the system and will be reflected in the Betriebsvereinbarung.

Q2. Is this a chatbot, or something more? Can it learn from what employees tell it?

Leena AI uses large language model technology to understand natural language queries and route them to the appropriate response or workflow. The deployed system is configured against a defined knowledge base and a defined set of use cases. It does not continuously learn from individual employee interactions in a way that modifies its behaviour between conversations. Configuration changes to the knowledge base and use case scope are made by authorised administrators, not by the system autonomously. Changes to the knowledge base that affect employee-facing content will be subject to the review process agreed in the Betriebsvereinbarung.

Q3. Will this system make decisions about employees, or is it purely informational?

For information retrieval — answering questions about leave balances, pay slips, policies — the system provides a response drawn from the knowledge base and connected HR systems. For transactional use cases, the system facilitates a request that still requires the same human approvals it requires today. The system does not make employment decisions, performance assessments, or any determination that affects an employee's terms and conditions. Those remain with managers and HR.

Data Access, Logging, and Privacy

Q4. What employee data will the system access?

Leena AI accesses only the data required to answer a query or fulfil a transaction for the employee who made the request. For personal data (such as leave balances or pay components), it retrieves this via authenticated API calls to the connected HR system. The design principle — and a requirement we hold ourselves to — is that the system surfaces only information the employee is already entitled to see under the access rules of the connected system. We will demonstrate this technically, not simply assert it.

Q5. Will the system log what employees ask? Who can see those logs?

Interaction data is processed to enable the system to function and to allow quality monitoring. The specific retention policy, the level of granularity at which conversations are stored, and the access controls on that data are a core subject of the Betriebsvereinbarung. Individual-level query transcripts linked to identifiable employees will not be accessible to line managers or other employees. The terms under which aggregated analytics (topic volumes, escalation rates, satisfaction indicators) are reported — including to the works council itself — will be negotiated as part of that agreement.

Q6. Can the system be used to monitor employees — now or in future?

The system is not deployed or configured for employee monitoring. However, we recognise the legal principle here: if a system is technically capable of profiling individual behaviour, even if that capability is currently inactive, the works council has the right to address it in the Betriebsvereinbarung before the system goes live. We will provide a written declaration of the system's technical monitoring capabilities — active and inactive — and the Betriebsvereinbarung will include explicit prohibitions on use cases the works council does not approve.

Q7. Where is employee data hosted? Does any data leave Germany or the EU?

Data residency terms are governed by the Data Processing Agreement (Auftragsverarbeitungsvertrag) with Leena AI as a processor. We will provide the full DPA to the works council's data protection representatives before approval is requested. Any change to data residency terms during the contract period would require notification and, where applicable, a renegotiation of the works agreement.

Q8. What happens to the data if the vendor relationship ends?

Data portability and exit provisions are governed by the vendor contract. We will make the relevant exit and deletion clauses available to the works council before the co-determination procedure is concluded. Employees' HR data remains in the systems of record (SAP, or equivalent) at all times — it is not migrated to Leena AI's infrastructure.

Access, Equity, and Frontline Workers

Q9. Will all employees have equal access? How will production workers without computer access use this?

Equal access across all employee groups is a legitimate condition and one we take seriously as a design requirement, not a nice-to-have. Office workers with Teams or browser access benefit from day one. For production and frontline workers without company devices or email access, the route is through mobile app or kiosk access points. We will not deploy a model that serves only part of the workforce, and we commit to documenting the timeline for full coverage — including any dependencies such as mobile app governance approvals — before the Betriebsvereinbarung is signed.

Q10. What about employees who use personal devices (BYOD)? What are the conditions?

Any channel that requires employees to use personal devices will be governed by explicit BYOD terms agreed with the works council. Employees will not be required to install work applications on personal devices as a condition of accessing HR services. The BYOD channel will only go live after data privacy and any applicable security approvals are confirmed and the terms are documented in or annexed to the Betriebsvereinbarung.

Q11. How will the system handle sensitive situations — disability, complaints about a manager, emotional distress?

For any query the system identifies as potentially sensitive, the default configuration is to escalate to a human HR contact rather than attempt to resolve it. The route to a human contact will be clearly signposted, not buried in the interface. We commit to demonstrating this in a live walkthrough before approval is given — not merely describing it in documentation. The works council is entitled to review the escalation trigger configuration.

Quality, Accuracy, and Liability

Q12. What happens if the system gives incorrect information — especially on collective agreement or statutory entitlements?

The knowledge base is the critical quality lever, and maintaining it accurately is one of the most demanding ongoing responsibilities of this deployment. Our governance model for the knowledge base includes: defined content ownership, a review and approval process before any change goes live, and a version history. Legally sensitive topics — collective agreement provisions, statutory entitlements, data privacy information — will not be made available to employees until the content has been reviewed and cleared by the relevant internal owners. The works council has the right to review the governance model before approval and to request re-review if concerns arise after go-live.

Q13. What is the fallback if the system is unavailable?

Leena AI is not a replacement for existing HR service channels — it is an additional channel. Existing contact routes (HR helpdesk, direct HR contact, manager escalation) remain available and will not be decommissioned as a direct result of this deployment. The bar for any future decision to decommission a legacy channel would include demonstrated performance evidence and, where applicable, a further works council consultation.

Employment Impact

Q14. Will this lead to job cuts in HR?

This deployment is designed to redirect HR capacity from high-volume transactional queries toward more complex advisory and case management work — not to reduce headcount. We will not use this system as a justification for redundancies in HR. We commit to providing the works council with a written statement of intent on this point, and to consulting the works council under the applicable statutory procedure before any change to HR staffing levels that relates to this deployment.

Q15. Will roles change? What requalification support is available?

As the volume of routine queries handled by the system grows, the expected shift is toward more complex, relationship-based HR work. We will provide training and support for HR staff whose roles are affected by the deployment, and will work with the works council to agree the form and timeline of that support before go-live.

Process, Governance, and Works Council Rights

Q16. What existing Betriebsvereinbarungen cover HR processes? Will Leena AI override them?

We have reviewed the existing works agreements that govern HR processes at affected locations. Where those agreements specify process steps, approval requirements, or employee rights, Leena AI will be configured to support those requirements — not to bypass them. If any use case creates a conflict with an existing agreement, we will pause that use case and consult with the works council before proceeding. This obligation will be written into the Betriebsvereinbarung for the system.

Q17. At what point do you need our formal approval — and what does the process look like?

The formal co-determination procedure under BetrVG §87 requires works council approval before the system goes live in any configuration that processes employee interaction data. We will not go live without that approval. The current phase — design, configuration, and consultation — is preparatory. We will provide a formal introduction and documentation package to the works council, allow the statutory deliberation period, and negotiate the Betriebsvereinbarung in good faith. We have engaged legal counsel experienced in works council procedures to support this process.

Q18. Will the works council have an ongoing role after deployment?

Yes. The Betriebsvereinbarung will establish a regular review mechanism. This will include: periodic reporting on aggregate system performance metrics (escalation rates, query volumes by topic, quality flags), notification of any material changes to system configuration or use case scope, and a process for the works council to raise concerns between scheduled reviews. Individual employee query data will not be shared with the works council in any form that enables identification.

Q19. What if the works council says no, or requests significant changes?

Co-determination is a legal right, not a procedural hurdle. If the works council withholds approval or requests changes, the deployment does not proceed as planned. We are committed to engaging with works council concerns substantively — which means bringing them into the design process early enough that their input can actually shape the outcome, not just delay it. We ask the works council to engage in good faith with the evidence and documentation we provide, and to identify specific concerns clearly so we can address them directly.

04 · Betriebsvereinbarung: Key Provisions to Include

A Betriebsvereinbarung (BV) for an AI-driven HR tool should address the following minimum provisions. This is not a template — it requires legal review and negotiation specific to your organisation. Use it as a checklist.

Mandatory Provisions

✅ Purpose and scope — The specific use cases covered, and an explicit list of use cases excluded from the BV's scope
✅ Data access rules — Which employee data categories are processed, and confirmation that no data is processed beyond what is required for the stated purpose
✅ Logging and retention — What interaction data is stored, at what granularity, for how long, and under what access controls
✅ Monitoring prohibition — An explicit prohibition on using the system to monitor individual employee conduct, performance, or sentiment — including disabling any such technical capability
✅ Individual-level data access — Confirmation that no line manager, HR business partner, or peer employee can access another employee's individual query history
✅ Knowledge base governance — The process for content changes, approval authority for legally sensitive content, and the works council's right to review
✅ Escalation design — The trigger rules for escalation to a human, and the requirement that a human contact route is always available and accessible
✅ BYOD and channel terms — If personal devices are used, the specific BYOD conditions including voluntary participation, data minimisation, and removal on termination
✅ Employment commitment — A statement that the deployment will not be used as a direct basis for HR headcount reduction
✅ Change notification — The employer's obligation to notify the works council before any material change to system configuration, use case scope, or vendor arrangement

Governance Provisions

✅ Review cadence — A regular review meeting (typically quarterly or annual) at which aggregate performance data is shared with the works council
✅ Incident process — How the works council is notified in the event of a data incident, system failure, or material quality failure
✅ Suspension right — The conditions under which the works council can request system suspension pending investigation
✅ Termination — What happens to all employee data processed by the system upon termination of the Betriebsvereinbarung

05 · Engagement Principles

The following principles reflect what works councils have responded to most positively in AI tool introductions. They are equally relevant as risk mitigants.

Principle 01 — Start Early

The most common works council complaint about technology introductions is that they are consulted after decisions are locked in. Works council engagement should begin at the point when use cases are being scoped — not when the system is ready to go live. Early consultation allows genuine co-design and reduces the risk of late-stage objections that delay deployment.

Principle 02 — Be Specific and Honest

Works councils are experienced in identifying vague or evasive answers. If you do not yet know the answer to a question (for example, the full logging architecture of the vendor platform), say so clearly, and commit to a date by which you will provide the information. Do not make assertions you cannot demonstrate technically.

Principle 03 — Treat Frontline Access as a Real Requirement

Works councils representing production and blue-collar workers will scrutinise whether the system serves their members equally. A deployment model that benefits only office workers is a legitimate objection under the equal treatment principle. Plan the frontline access path, resolve any channel governance dependencies, and include a timeline commitment in the Betriebsvereinbarung.

Principle 04 — Do Not Conflate Design Sessions with Approval

Workshops, sandbox demonstrations, and co-creation sessions are design activities. They do not constitute or substitute for the formal co-determination procedure. Be clear about the difference at all times. The formal procedure has its own timeline and requirements.

🚧
Disclaimer
This document is published by Leena AI as general guidance for organisations deploying Leena AI in jurisdictions subject to the German Works Constitution Act (BetrVG). It does not constitute legal advice. Employers should engage German employment law counsel experienced in works council negotiations before commencing the formal co-determination procedure.
For questions about Leena AI's technical architecture, data handling, or configuration options relevant to works council engagement, contact your Leena AI implementation lead or visit docs.leena.ai.