, Nils-Erik Jansson
AI policy template for the legal department
The template is an editable four page document in nine sections, with comments in the margin on what to adapt and why. It includes the two lists that keep the policy up to date: permitted tools and matters kept out. Download it as a Word document. The outline is shown below, and the reasoning behind each section is in the guide. The law firm addendum is based on the Swedish Bar Association's guidance.
Updated by Nils-Erik Jansson
Download
Free. No sign-up and no email address.
AI policy template for the legal department
AI-policymall för juristavdelningen
What the template contains
Nine sections, the same as the outline in the guide on an AI policy for the legal department:
| Section | What it sets out |
|---|---|
| 1. Scope | Who is covered and which tools the policy applies to |
| 2. Permitted tools | Only tools in Annex 1, no personal accounts |
| 3. What may be entered | What is allowed and prohibited, and anonymisation |
| 4. Matters kept out | The types of matter in Annex 2, with reasons |
| 5. Review of output | The user of the output is responsible, sources are checked, quarterly spot checks |
| 6. Transparency | A truthful answer when asked directly, AI use stated in the terms of engagement |
| 7. Contracts and data protection | Data processing agreement, transfer assessment, impact assessment, settings |
| 8. Incidents | Contact the same day and assessment within 72 hours |
| 9. Training and follow-up | Training before use and at least once a year, annual review |
Each section has ready text and a comment on what to adapt: where your tool is entered, where the list of matters kept out comes from, who owns what.
Two annexes in table form: permitted tools with plan, agreement and owner, and matters kept out with reasons and review date. These are the two parts that change often and keep the policy up to date.
A law firm addendum: the consent rule from the Swedish Bar Association's guidance on generative AI, with a consent assessment for each type of matter and a consent text, see the guide on client confidentiality and AI. Legal departments skip the addendum.
Four pages excluding the annexes. Written in the same style as this site: short sentences, no value words, nothing that cannot be followed.
What it does not contain
The risk assessment, the transfer assessment and the data protection impact assessment. The policy refers to them. Without them, the list of matters kept out is a guess, and that list is what makes the policy more than a ban. See the checklist for what should be in place before the first matter is entered.
How HOVR Legal works with this
If you want the policy written in full together with the lists, the risk assessment and the supplementary agreement, it is part of the data protection package, and for Claude part of the setup. The training on the policy is available as two hours for the department.
Frequently asked questions
- Does the template cost anything?
- No. It may be used and changed freely within your organisation.
- Is the template enough, or do we need help?
- For a department that has a tool under an enterprise agreement and knows which matters must stay out, the template is enough. The list of matters kept out follows from the transfer assessment, and the supplementary agreement with the vendor is a separate piece of work. Both are part of the data protection package under AI for legal.
- Which languages is the template available in?
- English and Swedish. The English version is the same template, for groups and law firms that work in English, with the same comments.
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 for the legal department: what it should contain
Outline of an AI policy for a legal department or law firm: permitted tools, what may be entered, review, responsibility, excluded matters and training.
- 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.