Germany’s Works Councils Can Block Your AI Screening Tool. Most India GCCs Haven’t Budgeted For That.

Germany doesn’t have a standalone AI-hiring law the way South Korea does. What it has is older and, for anyone building or operating a screening tool for a German entity, arguably stricter: Section 87(1) No. 6 of the Betriebsverfassungsgesetz (BetrVG), Germany’s Works Constitution Act, gives every works council, a Betriebsrat, a binding co-determination right over any technical system “capable of” monitoring employee behavior or performance. Courts and practitioners read that threshold broadly. A recruiting tool doesn’t need to be designed for surveillance to trigger it; if it can log candidate comparisons, scoring rationale, or evaluation metrics, that’s usually enough. For an AI voice-screening or resume-scoring system, that’s most of what it does by default.

This is a veto right, not a disclosure rule

Most of the AI-hiring compliance conversation Indian HR and vendor teams have been having this year is about disclosure: tell the candidate, log the decision, keep an audit trail. Germany’s BetrVG works differently, and the difference matters. Where a works council exists, an employer cannot unilaterally deploy an AI system that meets the Section 87(1) No. 6 threshold. It has to negotiate a Betriebsvereinbarung, a formal works agreement, before rollout. Section 95 extends the same co-determination requirement specifically to AI used in setting hiring criteria or selection guidelines. This isn’t a paperwork step you complete after the fact. It’s a negotiation you need to win before the tool goes live, and the works council can hold up the rollout until you do.

That’s not a theoretical friction cost. Roughly 60% of AI projects at German enterprises stall or fail over unresolved works council objections, while companies that bring the Betriebsrat in early report roughly three times higher adoption rates. Compare that to the compliance conversation we walked through for the EU AI Act’s August 2 deadline: that’s a documentation and audit-trail exercise. This is a stakeholder who can say no.

Where India’s GCCs sit in this

Germany runs one of the largest Global Capability Centre relationships with India of any European economy. SAP Labs India alone employs 8,000-10,000 people and builds a large share of SAP’s global product line; Bosch’s GCC in Bengaluru and Chennai runs 4,000-5,000; Siemens, Deutsche Bank, Continental, and others maintain sizeable India operations of their own. Some of that India-based engineering and HR-ops capacity builds or operates recruiting and screening tooling that gets deployed for hiring into the German parent entity, or for managing German-based teams’ hiring pipelines. The BetrVG doesn’t distinguish between a screening system a German employer built in-house and one an India GCC built or operates on its behalf. If the tool is used to make or inform a hiring decision covered by a German works council’s remit, the co-determination obligation attaches to the deployment, not to which country wrote the code.

That’s the detail worth sitting with: an India GCC team can ship a fully EU AI Act-compliant, fully audit-logged screening tool, and still have it blocked or delayed at the German entity because nobody looped in the Betriebsrat before rollout. The two obligations are cumulative, not interchangeable. The EU AI Act’s Article 26(7) already requires informing workers’ representatives before deploying high-risk AI once the Act’s provisions take effect on August 2, 2026. Satisfying that notification requirement does not satisfy Section 87 BetrVG’s separate, and more demanding, negotiated-consent standard.

What this changes in practice

For a screening vendor or an India GCC building this internally, the practical shift is sequencing. Compliance documentation, bias audits, and disclosure language, the checklist most teams are already working through for the EU AI Act, can be built entirely in India without a German stakeholder in the room. A Betriebsvereinbarung cannot. It requires the works council’s engagement from the design stage, not a document dropped on them for sign-off after the tool is already built and demoed to German hiring managers. Teams that treat the Betriebsrat as a late-stage approval step are the ones most likely to land in the 60% that stall.

The honest limit

This applies specifically where a German works council exists and has jurisdiction, private-sector companies with at least five eligible employees generally qualify, and where the tool is used in decisions affecting that German workforce. It doesn’t reach an India GCC’s own internal India-based hiring, and not every German entity has an active, engaged works council in practice. But for any India-built screening or recruiting tool that touches a hiring decision inside a German entity, the question isn’t whether German law applies. It’s whether the Betriebsrat was in the room before the tool shipped.

The take

Most of the compliance runway Indian teams have been building this year is documentation: logs, disclosure text, bias reports, an auditable rubric. Germany’s works councils ask a different question entirely, not “can you show us what the AI did” but “did you ask us before you deployed it.” For India GCCs building or operating screening technology that reaches a German entity, that’s not a checklist item. It’s a stakeholder relationship that needs to start before the build, not after the demo.

If your team is building or evaluating a screening tool for a Germany-facing GCC and want to know what an audit-ready, works-council-aware deployment actually looks like, talk to us.

Sources: AI Agents & Works Council Germany: Co-Determination Rights Under BetrVG — Paperclipped, Top 10 GCC Companies in India by Headcount 2026 — GCCX Global