, Nils-Erik Jansson
AI policy for the legal department: what it should contain
An AI policy for lawyers is a short document in nine points. It answers which tools may be used, what may be entered into them, how the output is reviewed, who is responsible and what happens when something goes wrong. Here is the outline I use, with what the Swedish Bar Association's guidance requires of Swedish law firms and what the EU AI Act requires of everyone.
Updated by Nils-Erik Jansson
What the policy is for
The policy should contain nine points, as the outline below shows. It refers to the risk assessment, the contract and the training, and is therefore short.
The policy is needed as soon as anyone in the department uses AI, whether under an Enterprise agreement or on a personal account. It does three things. It sets out what is permitted, so that those who want to do the right thing can do it. It draws the line for what may never be entered. And it places responsibility where it belongs, with the lawyer who uses the output.
The risk assessment, the contract with the vendor and the training are separate documents. The policy refers to them. That is why it can be short.
The outline
Scope. Who is covered (everyone in the department, consultants, trainees) and which tools the policy applies to: both those the company has bought and those anyone can open in a browser.
Permitted tools. A list with names and plans. "Claude Enterprise under the company's agreement" is a permitted tool. "Claude" is not, because a personal account is governed by different terms and is not covered by the undertaking not to train on the content [4]. The list is owned by a named person and updated when agreements are signed or terminated.
What may be entered. Start with what is allowed: public information, your own templates, anonymised contracts, information about counterparties to the extent the matter requires it. Then set out what may never be entered, and link it to the list of matters kept out of the tool. For law firms, client information without a data processing agreement and a transfer assessment is such a limit [1].
Matters kept out. The list itself, by type of matter. It is drawn up in the risk assessment and set out in the policy so that everyone can see it. Possible entries: matters with information subject to special access controls, disputes where a request from a US authority cannot be accepted, and matters where the client has said no.
Review of output. Responsibility for advice is the same whether or not the advice is based on output from a tool [1]. The policy says how this applies: case law, statutory references and factual statements are checked against the source before they are used, and whoever passes a document on is responsible for its content. Nobody sends an AI generated draft to a counterparty without having read it.
Transparency. When does the department tell the client or the business that AI has been used? The guidance names transparency as one of the questions the guidelines should answer [1]. My advice is a simple rule: always when asked directly, in the terms of engagement as standard, and never as an excuse for a mistake.
Contracts and data protection. A reference to where the data processing agreement, the transfer assessment and any data protection impact assessment are kept, and who owns them. The policy does not repeat them.
Incidents. What a member of staff does after entering something that should not have gone in: whom to tell, how quickly, and what the department then does with the vendor. This requires the vendor's deletion procedure, so it is included.
Training and follow-up. Who is trained and when, and that the training is documented as one of the measures that Article 4 of the EU AI Act requires of the organisation [3]. The date of the next review of the policy. The guidance says that guidelines and training should be kept up to date [1].
Mistakes to avoid
- The policy prohibits everything. The tools are then used anyway, privately and without a trace. A policy that only says no has controlled nothing.
- The policy is written for IT. It covers encryption and access rights but says nothing about what a lawyer may write in a prompt about a dismissal. The lawyers do not read it because it is not about their work.
- The policy names a tool the company has no agreement for. A permitted tool without a data processing agreement is a contradiction. Check that every entry in the list has an agreement behind it.
- Nobody owns the lists. Permitted tools and matters kept out change. Without an owner, the policy goes out of date.
How to keep it up to date
One review a year is the minimum, with another when an agreement is signed or terminated, when the vendor changes its terms, or when an incident has shown that a rule did not work. The training is repeated for new joiners and when tools change. The document itself changes little. The lists change often.
How HOVR Legal works with this
The guidelines are one of five parts of the data protection package, together with the transfer assessment, the data protection impact assessment, the draft supplementary agreement and the training. For organisations introducing Claude, they are part of the setup. Which matters are kept out is decided by the transfer assessment, see the guide on transfer impact assessments for AI tools.
Read also the AI policy template.
Download
Free. No sign-up and no email address.
AI policy template for the legal department
AI-policymall för juristavdelningen
Frequently asked questions
- Must a Swedish law firm have an AI policy?
- The Swedish Bar Association's guidance on generative AI says that the firm should adopt and implement guidelines on which tools may be used, how they may be used, which legislation may apply, fact checking, transparency and ethics, and that staff should be trained [1]. It is a recommendation, but it is linked to the principal's responsibility for staff under the Bar's Code of Professional Conduct. Without guidelines, each member of staff's own judgement becomes the firm's policy.
- How long should the policy be?
- I suggest two to four pages. Longer policies are harder to read, and what fills them out belongs in the risk assessment or in the contract with the vendor. The policy should take ten minutes to read and answer the question of what I may do today.
- Is the company's general IT policy enough?
- Not if it only covers tools and access rights. The legal department also needs rules on what a lawyer may enter about a counterparty, an employee or a client, and on how an AI generated draft contract is reviewed before it leaves the department. The legal department's policy can be an annex to the IT policy, but it needs to exist.
Sources
- [1]Vägledning om användning av generativ AI i advokatverksamhet, Sveriges advokatsamfund, 12 juni 2025, in Swedish; Swedish Bar Association guidance on generative AI, sections 3 and 5
- [2]Uppdaterad vägledning om användningen av externa IT-tjänster i advokatverksamhet, Sveriges advokatsamfund, 15 april 2026, in Swedish; Swedish Bar Association guidance on external IT services
- [3]Regulation (EU) 2024/1689 (the AI Act), Article 4, consolidated text of 27 July 2026, EUR-Lex, read 2026-11-17
- [4]Commercial Terms of Service, Anthropic
Insights on the topic
Back to AI for legal
More under AI for legal
- Data protection package for AI tools in legal work
Fixed-scope engagement: transfer impact assessment, impact assessment where needed, draft addendum, policy and training. For the AI tool you use or consider.
- AI operating model for the legal department
Fixed-scope engagement for legal departments. You get an operating model for how AI is used, governed and followed up, whatever the tool.
- AI literacy training for lawyers: two hours
Two hours of training for your legal department or firm on your own tools and documents, documented as a measure under Article 4 of the AI Act.
- Data protection checklist for generative AI in legal work
A checklist for law firms and legal departments: five questions to answer before the first client data goes into an AI tool, and what counts as a pass.
- AI policy template for the legal department
An editable AI policy template for a legal department or law firm in nine sections, with comments on what to adapt and why.
- The EU AI Act for in-house counsel: what applies to users
What the EU AI Act requires of a legal department that uses generative AI: AI literacy since 2025, transparency since 2026 and when the high-risk rules apply.
- Transfer impact assessment for AI tools, step by step
The six steps of a transfer impact assessment for a US AI tool: map, choose a transfer tool, assess the country, supplement, document, review.
- DPIA for generative AI: when it is required and how
When a legal department or law firm must carry out a DPIA under Article 35 GDPR for an AI tool, using the Swedish regulator IMY's nine criteria.
- Personal data in prompts: legal basis and information
When a lawyer writes about an employee, a counterparty or a customer in an AI tool, personal data is processed.
- AI incident response for legal teams
What a legal department does within 72 hours when a member of staff has entered data into an AI tool that should not have gone in.
- Anonymise before prompting: what works
How a lawyer removes personal data before text goes into an AI tool, and the difference between anonymisation and pseudonymisation.
- Swedish MBL and AI tools: must you negotiate first?
Swedish law: when an AI tool triggers the duty to negotiate under section 11 MBL, when informing under section 19 is enough, and with no collective agreement.
- Shadow AI in the legal department: one week of work
Staff use ChatGPT and Claude on private accounts for work. The legal department's week: map it, stop the worst, offer an approved tool, write the rule.
- Legal privilege and AI: the Swedish Bar guidance
What the Swedish Bar Association's guidance on generative AI requires for confidentiality: tools that do not train on client data, and terms read in full.
- Contracts with AI vendors: asking beyond standard terms
What a legal department or law firm asks of an AI vendor beyond the standard terms: authority requests, sub-processors, deletion, anonymisation, exit.
- On-premise or cloud AI for legal work
When a legal department or law firm should run AI locally and when the cloud is right: what local operation solves, what it costs, what it leaves open.
- Reviewing an AI answer in ten minutes: five steps
How a lawyer reviews an answer from Claude, Legora or ChatGPT before using it: sources, case law and statutes, figures, what is missing, and tone.
- AI literacy training for the legal department
What a two-hour training for lawyers using generative AI covers: what the tool does and does not do, your rules, practice on your own documents.
- AI guidance for lawyers in the EU and the UK
What the CCBE, the SRA, the Law Society, the Bar Council and the Swedish Bar Association require of lawyers using generative AI, and where they differ.
- The general counsel's AI report to the board: two pages
What the board needs to know about the company's AI use once a year, and what the general counsel can answer for.