, Nils-Erik Jansson
AI literacy training for the legal department
AI literacy training for lawyers can be two hours in six blocks, built on the department's own tools and documents and documented as a measure under Article 4 of the AI Act. Neither the article nor the guidance of the Swedish Bar Association (Sveriges advokatsamfund), which requires training adapted to the firm's use, says what it should contain. Here is the plan for the two hours.
Updated by Nils-Erik Jansson
What the training should achieve
The aim is that after two hours each lawyer knows three things: what the tool can and cannot do in their own work, what your rules say about what may be entered, and how an answer is reviewed before it is used. Everything else is a bonus. The training is an introduction to your tool, your rules and your review, and it is held on your documents.
Article 4 requires measures for AI literacy that take into account the staff's technical knowledge, experience and training and the context the systems are used in [1]. The Swedish Bar Association's guidance on generative AI requires training adapted to the firm's use and kept up to date [2]. Training that covers your use and is documented is set up in line with both.
Six blocks in two hours
| Block | Time | Content |
|---|---|---|
| 1. What the tool is and is not | 20 minutes | How a language model works, in terms a lawyer can use: it predicts text, it has not read your archive unless you have given it access, it invents sources with the same confidence as it cites real ones, and it does not get better because you trust it. What your tool is configured with: projects, playbooks, integrations. |
| 2. Your rules | 20 minutes | The guideline in brief, the list of approved tools and the list of matters kept out, with the reasons. Why a private account is different from the company's. What happens if something goes in that should not have. See the guide on AI policy for the legal department. |
| 3. Practice on your own documents | 30 minutes | Each participant does two tasks in the tool on one of the department's own de-identified contracts: a review against the playbook and a summary with source references. The exercise uses the department's own documents rather than the vendor's examples. |
| 4. Review | 20 minutes | The five steps in the guide on reviewing an AI answer in ten minutes, applied to the answers from block three. The aim is that participants find for themselves the errors that look right. |
| 5. When it goes wrong and whom to ask | 15 minutes | The incident procedure, who owns the tool in the department, how to propose a change to the playbook, where the guideline is kept. |
| 6. Records and next steps | 15 minutes | What is documented and why, when the next session is, and questions. |
What is left out
The history of AI, model architecture, vendor comparisons, future trends and general discussions of ethics are left out, because they do not change what the lawyer does on Monday.
The records
One page per session: date, participants, the content in six lines, who ran it, which tool and which version of the guideline it covered, and the date of the next session. The page is kept where the guideline is kept. That is the record that shows Article 4 has been applied, and the one the guidance assumes when it says training should be kept up to date [2].
Repetition
New staff get the same two hours within their first month, ideally together with the person who owns the tool in the department. Everyone gets a new hour when tools change, when the guideline changes significantly, or once a year, whichever comes first. Repetition is recorded on the same page.
How HOVR Legal works with this
HOVR Legal runs the training as two hours on site or remotely, see the offer. It is also part of the Claude for Legal setup and of the data protection package. It assumes a tool under a company agreement and a first version of the rule on what may be entered. See also the guide on the AI Act for in-house counsel on what Article 4 does and does not require.
Frequently asked questions
- Are two hours enough for AI literacy under Article 4?
- Article 4 sets no scope. It requires measures adapted to the staff's knowledge, experience and use [1]. For lawyers who will use a configured tool in their own work, the format is two hours on their own documents. What matters is that the training covers what you actually do, that it is documented, and that it is repeated for new staff and when tools change.
- Should people outside the legal department take the same training?
- Not the same one. The business needs to know what it may enter, where to find templates and self-service, and when to ask the lawyer. That is one hour with different content. Link it to a legal front door if you have one. The legal department's training goes deeper on review and rules. Both are documented the same way.
- Can the training be bought separately from the setup?
- Yes. Two hours on site or remotely for the department, with your tools and your documents, documented under Article 4. It assumes the department has a tool under a company agreement and a first version of the rule on what may be entered. If that is missing, I start there.
Sources
- [1]Regulation (EU) 2024/1689 (the AI Act), Article 4, consolidated text of 27 July 2026, EUR-Lex, read 2026-11-17
- [2]Vägledning om användning av generativ AI i advokatverksamhet, Sveriges advokatsamfund (Swedish Bar Association), 12 June 2025 (in Swedish), section 5 on guidelines and training
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.
- 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 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.