Regulation (EU) 2024/1689 · Artificial Intelligence Act ● Annex III: — days

Works Councils and Workplace AI: Consultation Duties Before You Deploy

Article 26(7) hands your workers' representatives a formal say before workplace AI goes live — and national co-determination law often hands them more. What triggers consultation, who holds it up, and how to sequence deployment so the timeline survives.

Renomira Team · 10 min read

A workplace AI deployment can be perfectly classified, documented and conformant — and still stall for a quarter at the door of a works council. Consultation is not a communications nicety in the EU: for workplace systems it is a legal step with sequencing consequences, running on two rails that must both be satisfied.

Colleagues in discussion in an office — consultation before deployment
Photo: EU2017EE Estonian Presidency / CC BY 2.0 via Wikimedia Commons

Rail one — the AI Act. Article 26(7): before putting a high-risk AI system into service or use at the workplace, the deployer must inform workers’ representatives and give them the opportunity to consult on the system’s use. Inform-plus-consult, prior to deployment — a deadline the Act fixes relative to go-live, not to your project plan.

Rail two — national labour law. Germany, the Netherlands, France and others give representative bodies rights that are older, sharper and sometimes suspensive: advice rights, consent rights, veto rights. Where national law provides a stronger procedure, the stronger procedure governs the rollout.

The German case: co-determination by default

Germany’s Works Constitution Act makes this concrete:

  • § 87(1) No. 14 BetrVG — co-determination over technical devices objectively suitable to monitor performance or behaviour. The test is suitability, not intent: an AI that could score employees — even if you promise not to configure it that way — is in scope. Works-council agreement is required.
  • § 90/§ 91 BetrVG — information and consultation on planning new workplaces and technical and economic changes; if the deployment changes working procedures materially, the council is involved in the design, not just notified of the outcome.

The practical translation: deploying an AI meeting summariser, a ticket-routing model that shapes workloads, or a scheduling system in a German entity is a negotiation, planned in weeks, not an announcement made on launch day. Treat it like you would treat introducing a monitoring camera — because legally, it is that class of decision.

The Netherlands and France

  • Netherlands — the Works Councils Act (WOR) gives the ondernemingsraad advice rights over important organisational and staffing decisions; introducing systems that structure or monitor work routinely lands in that set, with the advice procedure carrying its own timelines.
  • France — the CSE must be informed-consulted on measures affecting working conditions, health and safety; introducing AI that organises, evaluates or monitors work triggers the consultation, and monitoring-flavoured systems additionally sit under the CNIL’s employer-monitoring guidance.

Both systems share the German logic: the introduction is the trigger, and the right attaches to the decision — so consulting after go-live is not late consultation, it is none.

Where the two rails intersect

Article 26(7) applies to high-risk systems at the workplace (Annex III 4 being the common one). National law is often broader — covering any system objectively suitable to monitor, including ones the AI Act classifies as minimal. So the sequencing rule:

System tier AI Act National works-council law Practical trigger to plan for
High-risk (Annex III) Inform + consult, Art. 26(7) Full rights as applicable Both — plan the longer one
Monitoring-suitable, not high-risk No Art. 26 duty § 87(1)14 DE / advice NL / CSE FR National law alone
Genuine back-office, no person-affecting or monitoring angle Nothing Usually nothing Document why

Documenting the third row honestly is the discipline: why this system cannot monitor performance or behaviour is a paragraph that prevents a surprise escalation.

Sequencing a deployment that survives the calendar

  1. Screen at design, not at launch. Two questions per system at intake: Annex III 4? Monitoring-suitable? Either answer puts a consultation lane in the plan.
  2. Package the information. What the system does, what data it touches, what it scores or influences, oversight arrangements, logging and retention. Article 26(7)’s “inform” needs substance; a policy link fails.
  3. Book the consultation before the release train. Six to ten weeks is a normal German runway for agreement on a §87 system; the consultation right (Art. 26(7)) runs faster, but national procedures set the real clock.
  4. Write the works agreement tight. Purpose limitation, no autonomous decisions on personnel, retention, human review, access controls, and a change-review clause — so the next model version does not reopen negotiation from zero.
  5. Log the consultation in the register: dates, participants, outcome. Auditors ask; deployers who have the minutes answer in one line.

The pattern that fails is ordering the other way: contract signed, system configured, deadline announced — then consultation becomes a blocking step with a date attached to a promise you already made publicly.

One question decides the lane

At intake, ask: could this system, as configured or reconfigured, influence how a person is treated at work — evaluation, allocation, access, opportunity? If yes, assume both rails and plan the runway. The companies that hit Q4 surprises are the ones that treated consultation as change management; the ones that don’t, treated it as a build step.

How to check your own position in four minutes

The free exposure scan asks twelve questions about your AI usage and governance and returns an exposure score, your ranked exposures with the exact article that fired, and your first three moves — mapped to the dates that apply. Confirm your email and the full report unlocks.

Frequently asked questions

Does the AI Act require works council approval for workplace AI?

Article 26(7) requires deployers to inform workers’ representatives and give them the opportunity to consult before putting a high-risk AI system into service at the workplace — a consultation right, not a formal approval veto. Whether approval is actually required comes from national law: Germany’s § 87(1) No. 14 BetrVG co-determination covers any technical device objectively suitable to monitor performance or behaviour, which most workplace AI is.

When does German co-determination apply to AI tools?

When the tool is objectively suitable to monitor performance or behaviour — the statutory test is capability, not configured use. AI scheduling, productivity scoring, ticket-metric models, even meeting summarisers with individual attribution can qualify. § 90/§ 91 adds consultation rights where the deployment changes workplace design materially. Plan a negotiation, not an announcement.

What must we tell workers’ representatives about an AI system?

Enough to consult meaningfully: what the system does, its intended purpose, what data it processes, what it scores or influences about people, human oversight arrangements, logging and retention, and how outputs are used in decisions. “We are introducing an AI assistant” fails the inform duty; a two-page system sheet satisfies the practical bar.

Can we deploy first and consult afterwards?

Sequencing “consult before putting into service or use” under Article 26(7) means post-hoc consultation breaches the Act — and under German or French national procedure, deploying before the required agreement or advice completes can make the introduction itself challengeable. The overlap is the trap: a system may violate national law, the Act, or both, depending on tier — so plan for the longer of the two clocks.

How long does works council consultation for AI take?

German co-determination on a §87 system typically runs six to ten weeks to agreement when the scope is agreed at the start; Dutch advice procedures carry statutory response windows; French CSE consultations follow the information-consultation calendar. The variability comes from content, not law — a complete system sheet with a draft works agreement closes faster than a vague introduction that forces the council to request everything twice.

Next step

Put this guide to work on your own estate.

Run the free exposure scan to see which of these articles actually apply to your company — 12 questions, four minutes, no card. Confirm your email and the full report unlocks.

  • Free forever plan
  • No credit card
  • EU-hosted · GDPR-native
Run a free scan Sign up free

Build a live AI register in minutes — upgrade only when you need the audit pack.

works council AI deployment GermanyBetrVG section 87 AI monitoringAI Act Article 26(7) worker consultationworks council approval AI toolsworkplace AI consultation Netherlands Franceemployee representative AI system deploymentdeploying AI at work legal requirements EU

Keep reading