Skip to content
Spark
Writing

Governance and compliance

The EU AI Act and UK AI rules: what professional services firms actually have to do

The EU AI Act sorts systems into risk tiers and regulates the high-risk ones hard. The UK and Jersey lean on principles instead. If you serve regulated clients, you may sit under both. Here is what that actually requires.

By Seb Lawson · 17 March 2026 · 4 min read

Two regimes, two philosophies. The EU AI Act sorts AI systems into risk tiers and regulates the high-risk ones hard, with prescriptive obligations. The UK and Jersey lean on principles, leaving existing regulators to apply proportionate judgement. If your firm serves clients in both, you may sit under both at once. This is what that actually requires, without the alarmism.

Start with a calming fact. Most professional services firms are users of AI, not builders of it. That matters, because the heaviest obligations in the EU regime fall on the people who develop and place high-risk systems on the market. As a firm using a vendor’s tool inside your own workflow, your duties are real but lighter, and mostly about governance rather than engineering.

The EU AI Act in one paragraph

The Act ranks AI by risk. A small set of uses is banned outright. A defined group is treated as high-risk and carries obligations around risk management, data quality, documentation, human oversight, and transparency. Most business tools fall into a limited-risk band where the main duty is disclosure, telling people they are dealing with AI. And a large remainder is minimal-risk with no specific obligations. The obligations phase in over time rather than landing all at once, so treat any specific date or clause as something to verify against the primary text, not as gospel from a blog.

Who is actually caught

A UK or Channel Islands firm can be pulled into the EU regime by reach, not just by location. In broad terms, you may be in scope if you provide or deploy an AI system whose output is used in the EU, or if you serve EU-based clients through an AI-driven process. Being outside the EU is not automatic exemption. The practical trigger is where your AI’s effects land, not where your office is.

For most professional services work the honest answer is: you are probably a deployer of limited-risk or minimal-risk systems, with a smaller number of use cases that could edge toward high-risk if they materially affect a person’s access to a service. The work is to identify which is which, rather than to assume the whole firm is caught or that none of it is.

The UK and Jersey contrast

The UK has favoured a principles-based, pro-innovation approach, asking existing regulators to apply cross-cutting principles within their own remits rather than passing one omnibus AI law. Jersey is aligned in spirit. The JFSC’s guidance is proportionate and outcomes-focused, landing accountability with the board rather than prescribing controls line by line.

The contrast is real but the destination is similar. Whether a rule tells you to keep records and maintain human oversight, or a principle expects you to, you end up building the same handful of controls. In our experience a firm that governs AI well for its own sake satisfies both regimes with one framework, rather than running two compliance projects in parallel.

What to actually do

Five steps cover most professional services firms, and none of them require a legal department.

  1. Inventory your AI. List every system in use, what it does, whose data it touches, and where the output lands. You cannot tier what you cannot see. A first pass takes about a day.
  2. Tier by risk. Sort each use into minimal, limited, or high-stakes by what a wrong output could reach. This is the spine of both regimes and it tells you where to spend effort.
  3. Handle disclosure. For anything client-facing, be ready to tell people when they are interacting with AI. This is often the only hard EU obligation a limited-risk deployer carries.
  4. Build oversight and an audit trail on the high-stakes cases. A named human who can override, and a record of every material decision. This satisfies the demanding parts of both regimes at once.
  5. Check jurisdiction on EU-touching work. Where your AI’s output reaches EU clients or users, take a proper view on scope. This is the one place worth a specialist’s read rather than a rule of thumb.

That is a four to six week piece of work for a firm of 20 to 250 people, and it doubles as the governance foundation you would want regardless of regulation. It is also why the systems we build tend to survive contact with either regime.

One caveat, stated plainly. AI regulation is moving quickly, and the exact tiers, dates, and obligations shift as guidance and case law develop. Treat this as our practical read of the landscape, not as legal advice, and verify any specific point against the primary source before you rely on it.

If you want a grounded view of which of your AI uses are caught and what to fix first, book a review. We will map your systems to the tiers, flag the EU-touching cases, and put a number on the work. No deck, no hype.

Let’s map how your business works

A free 30-minute call with Seb or Mark. Bring the spreadsheet you hate most and we’ll tell you honestly whether a system would fix it.