Skip to content
Spark
Writing

Governance and compliance

The JFSC’s AI guidance: what it actually means for your firm

The Jersey regulator has set out how it expects firms to adopt AI. It is principles-based, proportionate, and lands the responsibility firmly with the board. Here is what it means in practice, and the four moves worth making now.

By Seb Lawson · 13 July 2026 · 5 min read

The headline is simple. The JFSC is not going to stop you using AI. It is going to ask who signed it off, whether you can explain what it does, and what happens when it gets something wrong. If you can answer those three questions on any given system, you are most of the way there.

The Commission set out its position in AI in financial services: enabling innovation with confidence, and it sits inside a wider 2026 to 2030 strategy that pairs strong regulation with a deliberately business-friendly stance. The tone is pragmatic. AI is already reshaping how firms operate, Jersey competes internationally for the same work, and the regulator would rather help firms adopt it well than watch them either freeze or wing it. It is principles-based rather than a prescriptive rulebook, which is good news and a trap at the same time. Good, because it is proportionate. A trap, because principles put the thinking back on you.

The four things it expects

Strip out the framing and the guidance leans on four ideas that recur across the Commission’s public statements and the broader work of the Jersey AI Council.

  1. Governance and accountability. Someone senior owns the AI, by name. The board understands what is running, why, and what it could get wrong. This is not a committee you convene once. It is a standing line of responsibility.
  2. AI-literate leadership. The people accountable actually understand the technology’s limits. You cannot govern what you do not understand, and ‘the vendor said it was fine’ is not a control.
  3. Explainability. You can describe, in plain terms, how a system reaches an output and why. Large language models return the most likely answer given the input, not the same answer every time, so consistency and traceability have to be engineered in rather than assumed.
  4. Meaningful human oversight. A person can review, override, and stop the system, and that oversight is real rather than a tick-box. The level of oversight should scale with how much damage the use case could do.

None of this is exotic. If you run a regulated firm, you already apply the same logic to outsourcing, to your AML framework, and to any material third-party dependency. AI is a new object inside an old discipline.

Proportionate is the operative word

The guidance does not treat every use of AI the same, and neither should you. A model that drafts an internal file note is not the model that decides whether to onboard a client. The oversight, testing, and documentation you put around a system should track the harm it could cause if it fails. A useful test: sort every AI use case into three buckets. Low stakes, where a wrong output is an inconvenience. Medium, where a human catches it before it matters. High, where a wrong output reaches a client, a regulator, or a payment. Most firms find 80 percent of their genuinely useful cases sit in the first two buckets, which is exactly where you should start.

What this does not mean

It does not mean you need an AI policy the length of your AML handbook before you switch anything on. It does not mean every tool needs a bespoke risk assessment signed in triplicate. And it does not mean waiting. The Commission has been explicit that it welcomes early conversations and would rather engage with firms that are moving thoughtfully than reward those sitting on their hands. Standing still is its own risk, and it is not the one the guidance is worried about.

Four moves worth making in the next 90 days

  1. Name an owner. Put one senior person’s name against AI adoption. Not IT alone, not a working group. A person with a seat at the table.
  2. Build an AI register. A single list of every AI tool in use, what it does, what data it touches, and which risk bucket it sits in. Most firms are surprised by what is already running once they look. A first pass takes about a day.
  3. Write one page, not fifty. A short AI use policy that says what is allowed, what needs sign-off, and what is off limits. One page people read beats fifty nobody opens.
  4. Make oversight and audit real on your highest-stakes case. Pick the one use case that could actually hurt if it failed, and build the human checkpoint and the audit trail properly. Prove the pattern once, then reuse it.

We wrote separately about building an AI audit trail and about what human-in-the-loop actually requires, because those two are where firms most often wave their hands. Both are worth getting right before a supervisor asks.

How we read it

This guidance rewards firms that treat AI as an operational discipline rather than a science project. That is the whole of our approach. We scope the smallest painful workflow, build it so the audit trail exists from day one, log every change, and keep a human in the loop where it counts. The regulator nods rather than flinches, because the governance was not bolted on at the end.

If you want a grounded view of your own position, our AI governance work for Channel Islands firms covers the framework in more depth, and a 30-minute review will get you a candid read on where you actually stand. No deck, no hype. Just what to fix first and what it is worth.

One caveat, stated plainly. Regulatory guidance evolves, and the exact wording and scope of what the JFSC publishes may move. Treat this as our interpretation of the Commission’s stated direction, not as legal advice, and check the primary source before you rely on any specific point.

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.