Most of the EU AI Act's ink is spent on the companies that build AI. Law firms sit on the other side of the line: they are deployers - professional users of other people's systems - and deployer obligations are lighter, later, and more manageable than the provider set. They are not, however, optional, and they arrive on three separate dates. This guide - part of our EU AI Act timeline series - turns the deployer rulebook into a dated, practical to-do list for firms and legal departments.
Legal information, not legal advice: the analysis below is general, and deployer duties vary with the systems you run and the member state you operate in. Take advice on your own facts.
Are law firms deployers under the AI Act?
Yes. A deployer is any natural or legal person using an AI system under its authority in the course of a professional activity - the only carve-out is personal, non-professional use. A firm running AI research tools, a legal department using contract review software, a chambers piping transcripts through an AI summariser: all deployers. The Act applies extraterritorially too, so a London or New York firm whose AI use produces output used in the EU is not automatically outside the frame.
Role determines burden. Providers - the vendors - carry the conformity assessments, technical documentation, and CE marking for high-risk systems. Deployers carry a shorter list centred on using systems responsibly: per instructions, with oversight, with records. The distinction is why a firm's first AI Act document should be an inventory that names the role the firm plays for every system in the stack, using the classification approach from our high-risk classification guide.
The Article 25 traps: when a firm becomes a provider
Article 25 lists three ways a deployer of a high-risk system inherits provider obligations, and all three have law-firm analogues. Putting your name or trademark on a high-risk system - the white-label temptation, offering a rebadged tool to clients as the firm's own product. Making a substantial modification - re-engineering a system beyond configuration so that it works materially differently. And changing the intended purpose so that a system that was not high-risk becomes high-risk - repurposing an internal research assistant into a client-facing eligibility screener, for example.
None of this forbids innovation; it prices it. A firm that builds client-facing AI products is doing provider work and should budget for provider duties. A firm that uses vendor tools as shipped, under the vendor's name, for the vendor's stated purpose, stays a deployer. Keep that line visible in every AI project charter, because crossing it silently is how a firm acquires obligations nobody scoped.
Duties already in force: prohibitions and literacy
Two duty sets have bound every deployer since 2 February 2025. The first is negative: no prohibited practices, anywhere in the organisation. For professional firms the live one is emotion recognition in the workplace - AI inferring employees' emotional states in call monitoring, meeting analytics, or productivity tooling is banned outside medical and safety uses, and the ban binds the deployer directly, with fines up to EUR 35 million or 7% of worldwide turnover. Screening the stack against the Article 5 list is an afternoon's work that removes the Act's largest tail risk.
The second is positive: AI literacy under Article 4. Firms must take measures so that staff using AI systems have the understanding their role requires - technical knowledge, context of use, and the people affected all factor in. The duty is real but proportionate, and the Digital Omnibus reframed it as an obligation of effort; our dedicated spoke on Article 4 literacy requirements covers what a defensible programme looks like.
From 2 August 2026: transparency and live enforcement
The August 2026 wave matters to firms in two ways. First, Article 50 transparency becomes enforceable. If the firm deploys a client-facing chatbot - an intake assistant, a knowledge bot on the website - people must be informed they are interacting with AI, unless it is obvious. If the firm publishes AI-generated or AI-manipulated content outward, disclosure and machine-readable marking duties attach to the systems producing it (marking for systems already on the market moved to 2 December 2026 under the Omnibus). Internal drafting assistance whose output a lawyer reviews and owns is not the target; unreviewed automated publishing is.
Second, the enforcement machinery goes live: national market surveillance authorities gain their full powers, and the Commission can fine general-purpose AI providers. For deployers the practical consequence is that questions about AI use stop being theoretical - regulators, clients running vendor audits, and professional indemnity insurers all acquire a live framework to ask against. A firm that can produce its inventory, classification file, and literacy records answers those questions in a day; a firm that cannot starts an internal project under deadline.
There is an advisory upside to the same date. Every EU-exposed client faces the identical wave, most without in-house AI counsel, and the firms that documented their own compliance first are the ones credibly selling the workstream. Treating the firm's own AI Act file as a rehearsal for client work is the cheapest business-development investment this cycle offers.
From 2 December 2027: the high-risk deployer set
Where a firm does deploy a high-risk system - realistically, AI in recruitment and HR decisions, or work on behalf of courts and ADR bodies - Article 26 attaches the full deployer duty set from 2 December 2027 (moved from August 2026 by the Digital Omnibus; see the Article 26 text).
| Duty | What it means in a firm |
|---|---|
| Use per instructions | Operate the system within the provider's documented intended purpose and settings. |
| Human oversight | Assign named, trained people with real authority to intervene or stop the system. |
| Input data control | Ensure data the firm feeds the system is relevant and sufficiently representative for its purpose. |
| Monitoring and incidents | Watch operation, suspend use on serious risk, and report serious incidents to the provider and authority. |
| Log retention | Keep the system's automatically generated logs at least six months, data protection law permitting. |
| Worker notification | Tell affected staff and their representatives before using workplace high-risk AI. |
| Informing affected persons | Where the system makes or materially informs decisions about people, tell them. |
Public-sector legal teams and some private deployers also owe a fundamental rights impact assessment before first use - the subject of our FRIA vs DPIA spoke. Even for firms with no high-risk systems today, the Article 26 list is worth reading as a preview of client questions: every EU client deploying hiring or credit AI will be building exactly this file, and outside counsel who know the list get the work.
Five steps for a firm this quarter
- Inventory and classify. List every AI system and AI feature in use, name the firm's role for each, and record the risk-tier conclusion per system.
- Screen for the two live duties. Confirm nothing touches Article 5, and stand up documented literacy measures matched to roles.
- Assign the August 2026 duties. Give client-facing chatbots and outward AI-generated content an owner for disclosure and marking.
- Fix the paperwork. Update engagement letters and vendor contracts so instructions for use, log access, and incident notification flow to whoever owes the duty.
- Put governance around it. Fold the above into a standing policy - our governance policy template gives the structure - so compliance survives staff turnover.
Firms running shared AI platforms have an execution advantage here: a workspace with role-based access and an activity trail produces the oversight and monitoring evidence as a by-product of normal use. Judicio's collaboration and access controls were built on that pattern - Owner, Editor, and Viewer roles, project-scoped access, and a record of who ran what on which files.
How Judicio helps deployers
Judicio sits on the deployer-friendly side of every line in this article. The tools are lawyer-facing research, review, and drafting - outside the high-risk tier in ordinary use - with the properties deployer duties reward: outputs cited to sources a human can verify, review workflows that keep a lawyer in the loop, role-based access with an activity trail, and no training on client documents. Provider-side documentation lives on the methodology and security pages, which is where a deployer's classification file should point.
The mid-2026 status view in our earlier piece on what changed for law firms by mid-2026 pairs well with this obligation map. To see the workflow side, start a 7-day free trial - 500 credits, no card required - or contact us; EU-market context lives on the Europe hub.