The CAO/Tarifvertrag AI-VA trap: collective agreements at four employees

If you run a Dutch, German, or Austrian SMB and you have started using an AI virtual assistant to handle work that used to belong to an admin or front-desk role, the question we keep getting is whether the AI deployment is “just a tool” or whether it pulls collective-agreement obligations into a business that thought it operated outside that frame. The honest answer is: in many sectors, the AI-VA deployment does pull collective-agreement obligations even at four employees, even at one employee plus one freelancer, and the owner-operator usually does not know until a union approaches.

The structural reason: sectoral collective agreements (CAO in the Netherlands, Tarifvertrag in Germany and Austria, Convention Collective in France and Belgium) typically apply to all employers in the named sector regardless of company size, where the agreement is declared generally binding (algemeen verbindend verklaard in NL, allgemeinverbindlich in DE). The agreement governs employee classification, compensation floors, working time, and increasingly, the introduction of new technologies that affect employee work. The fact that the SMB has four employees and no HR function does not exempt it from the substantive obligations.

For a 1-to-25-employee SMB owner-operator in a CAO-covered sector, the practical implication is that the AI-VA deployment is a labour-relations decision as well as a tooling decision, and the labour-relations frame has not been part of the typical SMB AI rollout discussion in 2025-2026.

Where the obligation actually comes from

Three pieces of statute create the substrate, all of them publicly documented and all of them unchanged by the rise of AI tooling.

The Netherlands. CAO and the AVV declaration. Sectoral collective agreements in the Netherlands are negotiated between sector employer associations and trade unions, then published as a CAO. When the Minister of Social Affairs and Employment declares a CAO “algemeen verbindend verklaard” (generally binding), the agreement applies to all employers in the sector regardless of association membership. The list of currently-AVV CAOs is published by the Ministry of Social Affairs and Employment. The CAO often includes provisions on the introduction of new technologies that materially affect work, with rights for the works council or (in smaller employers without a works council) for the union to be consulted before deployment.

Germany. Tarifvertrag and Allgemeinverbindlicherklärung. The German equivalent: sector-level Tarifverträge negotiated between employer associations and unions, with the Federal Ministry of Labour able to declare a Tarifvertrag generally binding under §5 of the Tarifvertragsgesetz. The Tarifvertrag governs wage groups, working time, leave entitlements, and increasingly the conditions for introducing technical systems that affect employees. Combined with the Betriebsverfassungsgesetz (covered in our enterprise piece on works councils), the floor of obligation is high.

The 1-to-25-employee SMB context. Many SMB owners assume that “we are too small for the union” or “we are not part of the employers’ association so the CAO does not apply.” Both assumptions are often wrong. AVV/allgemeinverbindlich declarations apply at the sector level not the membership level; once declared, every employer in the sector is bound. The size threshold for works-council-rights specifically is higher (typically 5 or more employees in NL, 5 in DE), but the CAO/Tarifvertrag substantive obligations apply regardless.

The AI-VA deployment as a CAO trigger

The AI-VA deployment becomes a CAO/Tarifvertrag matter through two specific channels.

Job-classification displacement. The CAO assigns wage groups by job content; when an AI-VA takes over the substantive content of a covered job role, the residual human role often shifts to a different wage group. If the displacement is informal (the human keeps the title but the work content has materially changed), the CAO classification can be challenged retroactively, with back-pay implications.

Technology-introduction consultation. Some CAOs specifically address the introduction of new technologies that affect employee work, requiring consultation or consent from the employee representative side before deployment. The AI-VA implementation that the SMB owner treated as an internal tooling decision is in scope of the consultation right where the CAO has the provision.

The combination produces three concrete failure modes for the unaware SMB owner. The first is back-pay exposure when an audit finds that AI-aided employees should have been classified at a higher wage group than they were actually paid. The second is invalid implementation when consultation rights were skipped and the union obtains a court order to suspend or roll back the deployment. The third is reputational exposure when the matter becomes a sectoral-press story, with the operator named.

What unions have started doing

The pattern that most concerns the unaware SMB owner: union activity in this space has shifted from theoretical to operational since 2024.

FNV (Netherlands) and the sector-specific unions under the FNV umbrella have started auditing AI deployments in CAO-covered sectors, with particular attention to the technology-introduction provisions. The audits typically begin with a written question to the employer and escalate from there.

DGB and IG Metall (Germany) and the relevant sectoral German unions have similarly increased attention on AI-related Tarifvertrag obligations, with public statements throughout 2024-2026 framing AI deployment as a co-determination matter that crosses both Betriebsverfassungsgesetz and Tarifvertrag surfaces.

CFDT and CGT in France treat AI-related deployments under the existing Convention Collective and CSE framework, with similar audit patterns.

The pattern is consistent: published union statements name AI as a CAO/Tarifvertrag-relevant deployment category; the published audit cadence has increased; the SMB targets have become more visible. The 4-person Dutch agency or the 8-person German Handwerk firm is no longer too small to be in scope.

The 1-to-25-employee compliance test

For an SMB owner in a CAO/Tarifvertrag-covered sector considering or already running an AI-VA deployment, four questions in order.

Is your sector covered by a generally-binding CAO or Tarifvertrag? The list is published. If you are not sure, look up your business’s NACE/SIC code on the relevant ministry’s published list. Most SMB owners are surprised to find they are covered.

Does the CAO or Tarifvertrag include a provision on the introduction of new technologies, or on the classification of work content? Read the agreement specifically. The provisions vary by sector and the relevant clause is rarely the headline one.

Has the AI-VA deployment materially changed the content of any covered job role? Honest answer needed. If the human still does some of the work and the AI does some, the answer is often yes.

Have you consulted the union (where the CAO requires it) or documented the reasoning if you did not? The documented reasoning matters at audit; the absence of any record is the exposure.

Three out of four affirmative is the bar. Two affirmative is repairable with a quarter of focused work and ideally local employment-law counsel. One or zero is the territory where the union’s first letter will arrive without warning and the operator’s position is weak.

What this means for the AI deployment plan

The practical implication for the SMB owner is not “do not deploy AI-VA tooling.” The implication is that the deployment plan needs to include a labour-relations workstream alongside the tooling and process workstreams.

The labour-relations workstream is short for most SMBs: identify which CAO/Tarifvertrag applies, read the relevant provisions, communicate the planned deployment to affected employees and (where required) to the union, document the reasoning, and adjust either the deployment or the role classification as needed. The work takes a few hours per quarter for an SMB owner who handles it from the start. The work takes weeks of remediation when handled after a union approach.

The local employment-law counsel cost for SMBs in the relevant jurisdictions is modest and worth budgeting once at the start of the AI program rather than as an emergency response when an audit lands.

What we are not claiming

We are not claiming that all CAOs and Tarifverträge include explicit AI provisions. The provisions vary; some sectors are explicit, many sectors handle AI through general technology-introduction language. The per-sector reading matters.

We are not claiming that union audit activity is uniform. Some unions are more active in this space than others; the cadence varies by sector and by national union strategy.

We are not citing specific union audit outcomes by name because most are confidential resolutions between employer and union. The pattern of audit increase is published commentary in the Dutch and German labour press; the per-case data is private.

What changes this read

Cadence on this piece is 60 days because the union activity, the case law, and the CAO renewal cycles all move on multi-quarter timescales. The three things that would change the verdict:

A landmark CAO or Tarifvertrag renewal that explicitly addresses AI tooling at the sectoral level would crystallise the obligation set and shift the analysis from “general doctrine applies” to “specific clause applies.” A coordinated union position across the major Dutch, German, French, and Belgian federations on AI-related sectoral obligations would standardise the audit pattern and reduce the per-employer variance. A material EU-level regulation on AI and labour relations would override the national-CAO frame and require unified compliance handling.

We will re-test against FNV, DGB, and the Dutch CAO database on or before 30 Jun 2026.