, Nils-Erik Jansson
AI operating model for the legal department
A fixed-scope engagement in which HOVR Legal draws up an operating model for how the department uses AI, whatever the tool. When the engagement ends, you have the operating model in a document the department owns and can run itself.
Who it is for
Legal departments that already have one or more AI tools in use and notice that use is uneven: some use it for everything, others not at all, and nobody knows what is good enough to rely on. Also departments that are about to choose a tool and want to know what to require of it.
What you contribute
- A contact person with a mandate.
- Time for interviews: one hour per lawyer and half an hour per person instructing legal.
- Access to the tool you have.
- Decisions within the agreed time in step two.
What is not included
The data protection documentation, which is a separate package under AI for legal. Configuration of the tool, which for Claude is part of the setup. Choice of tool, see legal technology selection. Legal advice on the department's matters.
What it is
Data protection answers whether a tool may be used. The operating model answers how:
- Which workflows go through the tool, and which do not?
- Who may use it for what?
- How is the output reviewed before it is used?
- Who owns the playbooks, templates and settings?
- How do new staff learn it, and how does the department know whether it is worth it?
A tool that is right 98 times out of 100 sounds good. Run the work through five such steps and it is right all the way through about 90 times out of 100. That is why governance and review are needed.
The engagement ends in a document of ten to fifteen pages that the department owns and can change itself. It does not depend on the tool.
Step by step
| Step | What happens | What you have afterwards |
|---|---|---|
| 1 | Mapping: interviews with the lawyers and three to five of the people who instruct legal | A picture of the department's workflows with current AI use marked |
| 2 | Decisions with the department on where AI is used, with review and responsibility per workflow | A decision per workflow and the list of matters that stay out of the tool |
| 3 | The operating model is written up and reviewed with the general counsel | The operating model, a twelve-month plan and a date for the next review |
What is included
- Mapping, step one. HOVR Legal interviews the lawyers and three to five of the people in the business who instruct legal. Where does the time go, which matter types recur, where is AI already used and with what result? The result is a picture of the department's workflows with current AI use marked.
- Decisions, step two. Together with the department, HOVR Legal decides in which workflows AI is used by default, in which it is allowed but not the default, and in which it is not used. For each workflow: what goes in, what review is required before the answer is used, and who is responsible. This is where the list of matters that stay out of the tool belongs, if it exists, and otherwise it is drawn up.
- Governance and roles. Who owns the tool in the department, who changes playbooks and settings, and how are decisions on new uses made? How does it fit with the company's wider AI governance? Roles are written down with names.
- Skills. What each role needs to know, how it is taught, and how it is documented as a measure under Article 4 of the AI Act [2]. A two-hour training session is included.
- Measurement. Three to five measures that can be produced without new systems: lead time per matter type, share of matters that go through the standard workflow, number of review deviations, time in the tool. And a date for the first reading.
- The operating model, step three. Everything above in one document, reviewed with the general counsel, with a plan for the next twelve months and the next review.
Add-on: a reading after ninety days
The operating model sets the measures and the baseline. Ninety days later HOVR Legal goes through, if you want, what the measures show: which workflows work as intended, where use is low and why, which rules need changing, and whether a tool or a flow should be discontinued. You get a two-page reading with the adjustments made to the operating model and the decisions the general counsel needs to take. The add-on can be done with the engagement or later.
What you get
- The operating model as a document in your template, with workflows, roles, review rules and measures.
- The list of matters that stay out of the tool, if it did not already exist.
- Training material and documentation of the training.
- A twelve-month plan with prioritised next steps.
Time
Scope and time are agreed in the first conversation.
Next step
One hour about how the department uses AI today and whether the engagement fits. Write to hello@hovrlegal.com.
Read also AI literacy training for lawyers and an AI policy for the legal department.
Insights on the topic
Ask a question or choose a time for a conversation.
Get in touchBack 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 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 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.