Claude Works Agreement for AI Assistants: Sample Clauses and Tool Annex

Claude works agreement – IT manager and works council member discussing sample clauses on a laptop – AURUM GmbH Nuremberg

A Claude works agreement sets out what Claude is used for, who may see chats and logs, and which evaluations are excluded. If your German entity has a works council, its consent is usually required and is normally recorded in a works agreement (Betriebsvereinbarung). This applies even on the smaller Team plan, because there the Primary Owner can already export every chat in the organisation. A framework agreement for all AI assistants plus one tool annex per system has proved its worth. New tools then need only a new annex instead of a new negotiation. This guide sets out the building blocks of the framework, sample clauses for the Claude annex and the matching Claude settings. It complements our article on the works agreement for Microsoft Copilot (in German). Note: this is not legal advice. All Claude details as of 17 November 2026.

Why introducing Claude requires works council co-determination

Introducing Claude is subject to co-determination under Section 87(1) No. 6 BetrVG of the German Works Constitution Act. The provision covers technical equipment capable of monitoring employees’ behaviour or performance. Under settled case law, the objective capability counts, not the employer’s intention. A works council (Betriebsrat) is the body employees can elect in German establishments with at least five permanent employees.

For Microsoft 365, the Federal Labour Court (Bundesarbeitsgericht, Germany’s highest labour court) has confirmed co-determination (Federal Labour Court, 8 March 2022, 1 ABR 20/21). The same logic applies to an AI assistant with usage statistics and a chat history. The Hamburg Labour Court, a first-instance court, found no co-determination right for ChatGPT used through employees’ private, self-paid accounts (24 BVGa 1/24, 16 January 2024). There, the employer received no data. With company accounts on Claude Team or Enterprise, this does not apply. In addition, the employer must inform the works council in good time about the use of AI under Section 90(1) No. 3 BetrVG. To assess it, the works council may call in an expert under Section 80(3) BetrVG.

What data Claude Team and Enterprise generate about employees

Both plans generate personal usage data: on Team and Enterprise, the Primary Owner can export all chats, and Owners also see usage analytics per person. Audit logs, the Compliance API, custom retention periods and roles per connector, however, exist only on Enterprise. The table shows what matters for the works agreement.

FeatureClaude TeamClaude EnterpriseWhat to regulate
Organisation data export with all chatsYes, Primary Owner onlyYes, Primary Owner onlyReason, four-eyes principle, documentation
Usage analytics per personOwners and Primary OwnerAdmins as wellAggregated evaluation only
Audit logs (no chat content)NoYes, export covers 180 daysLimit the purpose to security
Compliance API with chat contentNoYes, enabled by the Primary OwnerEnable only after approval
Custom retention periodsNo, chats stay until deletedYes, at least 30 daysSet a deletion period
Roles for connectors and featuresNoYes, per role and connectorApproval process for new features

According to Anthropic, deleted chats are removed from the back end within 30 days. Exceptions apply to submitted feedback and to chats flagged for usage policy violations (Anthropic’s retention information). Moreover, Anthropic does not use content from Team and Enterprise for training by default. Our guide to Claude and the GDPR explains the data protection details.

Sample works agreement for Claude and AI assistants: the building blocks

A sample works agreement for AI assistants consists of ten building blocks that apply equally to all tools. System-specific details such as roles, exports and deletion periods, by contrast, go into the tool annex. That way, you negotiate the principles only once. If another tool is added later, you simply add an annex and inform the works council in good time. For a group-wide rollout, the central or group works council may be responsible rather than each local one.

Building blocks 1 to 5: purpose, use and control

  1. Scope and definitions: Which AI assistants, which employees, which sites. Define terms such as prompt, log and connector.
  2. Purpose and permitted use cases: For example drafting texts, summarising documents, reviewing code. An annex adds new use cases later.
  3. Prohibited use: No HR decisions without human review, no special categories of personal data without approval.
  4. No monitoring of performance or behaviour: The employer does not use usage data to assess individual employees. Disciplinary measures may not be based on it.
  5. Access to logs and content: Named roles only, only for a documented reason, under the four-eyes principle and with the works council informed.

Building blocks 6 to 10: data, training and changes

  1. Retention and deletion: Periods for chats, logs and exports, per system in the annex.
  2. Data protection: Reference to the data processing agreement, the data protection impact assessment and information duties. If the agreement itself is to serve as a legal basis for processing, it must meet the requirements of Article 88 GDPR in full.
  3. Training: AI literacy training, as required by Article 4 of the EU AI Act. More in our article on the EU AI Act for mid-sized companies (in German).
  4. Changes and new features: New models, connectors or agent features are announced before they are switched on and added to the annex where needed.
  5. Pilot, evaluation and termination: Time-limited test phases, a joint committee, a review date and rules on whether the agreement continues to apply after termination.

Tool annex to the Claude works agreement: clauses and settings

The Claude annex translates the principles into concrete settings, because a clause without a technical counterpart cannot be checked. It names the Owner roles, regulates exports and analytics and sets deletion periods. It also defines which features are switched on. The wording below consists of proposals for the negotiation, not finished legal texts.

Sample clauseImplementation in Claude
“Usage analytics are only evaluated for groups of five or more people.”Keep Owner roles few, do not enable the Analytics API
“Organisation data is only exported with the approval of the works council and data protection.”Primary Owner as a shared role account, not a personal one, with a four-eyes process
“Audit logs serve exclusively security and troubleshooting.”Enterprise: limit export rights to IT security
“The Compliance API is only enabled for the purpose named in Annex X.”Enterprise: document the Primary Owner’s activation
“Chats are deleted after 90 days.”Enterprise: custom retention period; Team: organisational deletion rule
“Memory, connectors and web search are only used after approval.”Memory can be controlled organisation-wide; Enterprise: roles per connector
“Claude Code metrics are not evaluated per person.”Review Claude Code reports at team level only

What is different on the Team plan

The Team plan lacks custom retention periods, audit logs and role-based approvals. The agreement must close these gaps organisationally, for example with a deletion rule for users and few Owner accounts. If you need technical proof that the rules are kept, choose Enterprise. Record the organisational fallback rules in writing: a list of Owner accounts, a log of every export and a deletion rule with a deadline. That way, the works council can check compliance on the Team plan too. Our guide Claude Team vs Enterprise compares both plans.

Pilot agreement: testing Claude for a limited time

A pilot is generally also subject to co-determination, so agree it for a limited time and with its own rules. A short pilot agreement is enough if it fixes four points: participants, duration, permitted use cases and an automatic end. In our pilots, usually 5 to 10 people work with Claude for about two weeks. Afterwards, evaluate the results in aggregate only. Once the pilot ends, the lessons feed into the tool annex before the rollout begins.

Benefits of a framework agreement for mid-sized companies

A framework agreement saves negotiation time, because every further AI tool needs only an annex. In mid-sized companies, departments often use several assistants in parallel, such as Microsoft 365 Copilot and Claude. Without a framework, you would renegotiate the same principles for every tool. Three benefits therefore matter most:

  • Faster rollout: The principles stay fixed; you negotiate only system-specific settings.
  • Less shadow AI: A clear, approved route makes private accounts unattractive.
  • Verifiable rules: Every clause has a technical counterpart that IT and the works council can check.

Common mistakes in a Claude works agreement

The most common mistake is to transfer the Copilot agreement to Claude without checking it. Claude has different roles, exports and logs from Microsoft 365. As a result, clauses on Purview or Viva Insights have no effect on Claude. We regularly see four further mistakes:

  • Underestimating the Team plan: Even without audit logs, the Primary Owner can export all chats.
  • Too many Owners: Every Owner role sees personal usage analytics.
  • Forgetting new features: Connectors, memory and agent features arrive via updates.
  • Involving the works council too late: Informing it only after purchase can delay the start by weeks.

What AURUM does for you

AURUM delivers the technical part of the works agreement: what data Claude generates, who can see it and which setting implements which clause. We have already supported companies with works agreements for Microsoft 365 Copilot and for Claude. Your legal advisers draft the contract text; we make sure it can be checked technically. As an Anthropic (Claude) Partner, we also use Claude ourselves every day.

  • Data flows and logs: We document what data your Claude plan stores and evaluates.
  • Clause review: We check every clause of the draft for a technical implementation.
  • Setup: We configure roles, retention and approvals to match the agreement.
  • Works council meetings: We explain the technology clearly and answer questions.

You can find more on our service page for AI data protection and EU AI Act consulting (in German). If you would like to discuss your draft or our sample clauses, you can get in touch directly.

Frequently asked questions about a Claude works agreement

Do we need a works agreement for Claude?

If your German entity has a works council, co-determination under Section 87(1) No. 6 BetrVG very likely applies to company accounts. This covers Claude Team and Enterprise. This note is not legal advice.

Is our existing Copilot works agreement enough?

Usually not without an addition. This is because Claude has different roles, exports and logs from Microsoft 365. If your agreement is built as a framework with tool annexes, a new Claude annex is enough.

Can the employer read employees’ chats?

Technically yes: the Primary Owner can export all chats on Team and Enterprise, and on Enterprise also via the Compliance API. The works agreement defines when and with whose approval this is permitted.

More questions about a Claude works agreement

May we test Claude before the agreement is signed?

Generally only with the works council’s agreement, because a pilot is also subject to co-determination. The usual route is a short, time-limited pilot agreement covering participants, duration and use cases.

How long does coordination with the works council take?

That depends on the relationship with the works council and the scope. If a framework agreement for AI already exists, a Claude annex is often agreed in a few meetings.

Conclusion: one framework, one annex per tool

A Claude works agreement is quickest as an annex to a framework agreement for all AI assistants. Regulate exports, usage analytics, retention and new features concretely and with a technical counterpart. Then start with a time-limited pilot and involve the works council before you buy.

Post teilen: