Claude for Legal setup for the in-house legal team

After the engagement the playbook is in place and adapted to Swedish law, and data protection is documented. HOVR Legal then follows along on real matters and makes adjustments.

Who it is for

In-house legal departments that have or are considering Claude Team or Enterprise.

What you contribute

  • Claude licences. They are not included, and you sign the contract with Anthropic yourselves.
  • A person in the department with a mandate to decide on the playbook and escalation.
  • Ten to twenty representative contracts.
  • Access to IT for the connectors.

In time: a half day for the interview, two check-ins a week during the follow-up and two hours per user for the training.

What is not included

Legal advice on individual matters, development of custom skills or artifacts, licences, and negotiation with Anthropic beyond review and recommendation. More than three connectors, or skills built specifically for you, are agreed separately. The data protection documentation is also available on its own, see AI for legal.

What it is

Every plugin in Claude for Legal starts with a short setup interview about the department's playbook, escalation chain and risk calibration [5]. The playbook, escalation rules and contract rules have to be added before the plugins are of any use. That is what this engagement does, with the playbook adapted to Swedish law and your contract patterns, and with data protection documented before the first matter goes in.

Step by step

Step What happens What you have at the end of the step
1 Needs interview, review of the signed contract with Anthropic, assessment of the transfer Requirements, data protection documentation and the list of matters that stay out of the tool
2 Playbook and escalation added, systems connected, policy written, two-hour training An environment that reviews contracts against your own rules, and users who know how to use it
3 Two check-ins a week, adjustments based on real matters A written handover and a date for the next review

What is included

  1. Needs interview. A half day with the department on contract types, volumes, where the time goes, which systems you use and what may and may not go in. You get a set of requirements and a first list of matter types to keep out of the tool.
  2. Plan, contract and data protection. Custom retention periods are only available on Enterprise, and the choice of routing location only on Enterprise with usage-based billing [1] [2], so the plan is chosen in the first conversation, before the engagement starts. HOVR Legal then goes through Anthropic's data processing agreement, assesses the transfer to a third country in a transfer impact assessment and carries out a data protection impact assessment under the GDPR where one is needed. The assessments are reviewed with your data protection officer and delivered in your template.
  3. Playbook and escalation. The department's standard terms, fallbacks and escalation rules are added to Claude for Legal and adapted to Swedish law: notice periods, limitations of liability, data processing agreements, choice of law and forum. From the contracts the team provides, HOVR Legal builds a tracking list for renewals and notice periods as an artifact, and adds to it from the archive through a connector or an import.
  4. Connectors. The systems in Anthropic's directory that the team uses, such as a contract archive, e-signature and document management, are connected with a documented data path for each connector. On Team and Enterprise an Owner adds the connector for the organisation [4]. HOVR Legal does this together with your IT team. No custom systems are built.
  5. Policy and training. A policy for generative AI in the department, covering permitted tools, what may go in, fact-checking and responsibility, and two hours of training for all users. The training is documented as one of the measures that Article 4 of the AI Act requires of your organisation, with a proposal for annual follow-up [3].
  6. Follow-up. Two check-ins a week with the person who owns the tool on your side, adjustments to the playbook and escalation based on real matters, and a written handover.

Matters that stay out of the tool

The most concrete deliverable is the list of matter types that do not go into Claude. It starts in the needs interview and is settled after the transfer assessment. It covers matters where processing in clear text by a US vendor cannot be accepted, matters with information under special access controls, and matters where the risk of a request from an authority is not acceptable. The list is part of the policy and is looked at again at every review.

What you get

  • A configured Claude for Legal environment with a playbook, an escalation matrix and a tracking list for renewals.
  • Data protection documentation: the data processing agreement with notes, the transfer impact assessment, the data protection impact assessment if one was carried out, and the list of matter types that stay out of the tool.
  • A policy for generative AI and training material.
  • A list of connectors with the data path for each system.
  • A handover document setting out what remains to be decided, when the next review should take place and what applies if you switch tools. The policy, assessments and list of matters are documents in your template and go with you to the next tool. The playbook is your text and can be added to another system.

Before the start

The plan is chosen in the first conversation, before the engagement starts. Before day one, the contract with Anthropic should be signed, the licences in place, an IT contact appointed and the representative contracts chosen. If you want the transfer assessment and the data protection impact assessment before the contract is signed, so that the data protection officer and IT security have time to read them, HOVR Legal delivers them first.

How your contracts are handled during the engagement

HOVR Legal signs a confidentiality agreement with you before the needs interview and, where HOVR processes personal data on your behalf, a data processing agreement. A conflict check against ongoing engagements is done before the start. Your contracts are handled in your own environment as far as possible, and copies held by HOVR Legal are deleted at handover.

Time

Scope and time are agreed in the first conversation.

Next step

One hour to go through the department's situation and whether the engagement fits. Write to hello@hovrlegal.com.

Read also Claude Team or Enterprise for a legal department and projects, skills, plugins and connectors in Claude.

Ask a question or choose a time for a conversation.

Get in touch

Back to Claude for Legal

More under Claude for Legal