# The JFSC’s AI guidance, applied to ten real use cases

Published 15 September 2026 by Spark · Governance and compliance · 6 min read
Canonical: https://hellospark.co.uk/writing/jfsc-ai-guidance-ten-use-cases

> The JFSC has said which AI needs light-touch controls and which needs more. We took ten use cases a Jersey trust or fund business actually runs, sorted them against the guidance, and wrote down the controls each one needs.

The JFSC’s AI guidance gives you a sorting test, and most firms have not run it yet. Low-impact productivity tools need only light-touch controls. Anything that touches regulated activity, customer outcomes, confidential data or regulatory submissions needs more. That one line is the most practical thing in the document, because it turns ‘proportionate’ from a mood into a method.

The Commission published its [Guidance on the use of AI in Jersey’s financial services sector](https://www.jerseyfsc.org/industry/guidance-and-policy/guidance-on-the-use-of-ai-in-jersey-s-financial-services-sector/) in July. It creates no new regime. It explains how the obligations you already carry apply when AI is involved, and it is clear that the firm stays accountable for the outcome, whoever built the tool. We wrote about [the direction of travel](/writing/jfsc-ai-guidance-what-it-means) just before it landed. This is the practical follow-up: ten use cases a Jersey trust or fund business actually runs, sorted against the guidance, with the controls each one needs.

## The five principles, in plain English

The guidance rests on five principles. None of them will surprise anyone who has lived through an outsourcing review.

- **Governance and accountability.** A named, senior person owns each AI system and answers for what it does.
- **Cybersecurity.** AI tools are new doors into your systems and your data. Treat them that way.
- **Privacy and data quality.** Know what data goes in, where it goes, and whether it is fit for the job.
- **Regulatory compliance, consumer protection and fair treatment.** AI does not suspend the Handbook or the duty to treat customers fairly.
- **Transparency and explainability.** You can explain an AI-assisted decision to a reasonable degree, matched to its risk and complexity.

The Commission expects the guidance to matter most for higher-impact uses, and names customer onboarding, lending decisions and investment advice. Where appropriate, material AI use cases and their controls belong in your business risk assessment.

## The four-trigger test

Here is how we turn the guidance into a decision. For any AI use case, ask four questions. Does it touch regulated activity? Does it affect a customer outcome? Does it handle confidential data? Does it feed a regulatory submission? The four triggers come from the Commission. The three levels below are our working method for applying them, not JFSC terminology.

- **Light touch.** No triggers. An approved tool, no client data, sensible staff guidance. Done.
- **Controlled.** Confidential data only, and the output stays internal as a draft a person owns. The controls are about the data: an enterprise tool, data kept inside your own environment and not used to train anyone’s model, access that mirrors your existing permissions, and retention you have set on purpose.
- **Material.** Regulated activity, a customer outcome or a regulatory submission. Now it goes in the business risk assessment, with a named owner, testing before go-live, a human sign-off, a log of every run and a plain-English account of how it works.

One more rule sits on top. Within Material, anything that acts on its own, by sending, paying or deciding without a person in between, gets the heaviest treatment of all. Do not build one of those first.

## Ten use cases, sorted

These are the ten we see most often in Jersey trust companies and fund administrators. Your list will differ in the detail, not the shape.

1. **Summarising public regulatory updates.** Light touch. Public material in, internal briefing out. No triggers.
2. **Drafting marketing copy and job adverts.** Light touch. Check the facts, as you would for any draft.
3. **Internal meeting notes.** Controlled. In a trust business almost every meeting mentions a client, so the confidential data trigger fires. The fix is the tool, not a ban: use the enterprise version inside your own environment, never a free app on someone’s phone.
4. **Drafting routine client emails that a person reviews and sends.** Controlled, with a warning. The moment the drafts contain advice, they affect a customer outcome and move up to Material.
5. **Searching your own document system for precedents.** Controlled. The risk is access, not output. The search must never show a junior a file they could not open themselves.
6. **Policy and procedures Q&A.** Material, and this is the one that surprises people. It looks like a staff convenience. But if an administrator uses it to decide how to apply your AML procedures, it touches regulated activity. Test it against the real manual and log what it answers.
7. **KYC document extraction with a human check.** Material. Customer due diligence is regulated activity. Worth doing anyway: our [KYC write-up](/writing/ai-for-kyc-client-take-on) shows how it takes hours out of every case. The human check is the control.
8. **Sanctions and PEP alert triage.** Material. The AI can rank and summarise alerts. A person closes every one, and the log shows who and why.
9. **Preparing data for regulatory returns.** Material by definition, because it feeds a regulatory submission. Reconcile the output to source before anyone signs.
10. **A client-facing chatbot answering account questions.** Material, and it acts on its own. Customer outcome, confidential data, no person in between. If you build this, build it last.

The tally is two Light touch, three Controlled and five Material. Do not read that as five red lights. Material is not a ban. It is a list of controls, and the most valuable work in a regulated firm lives there, because that is where the hours are.

## What the register needs

Your business risk assessment needs to see the material use cases, which means you need a register first. It does not need software. A spreadsheet with eight columns will do.

- **Use case**, in one sentence a director would understand.
- **Owner**, by name. A person, not a team.
- **Triggers**: which of the four it hits.
- **Level**: Light touch, Controlled or Material.
- **Tool and vendor**, including where the data is processed.
- **Controls**, as they actually run today, not as the policy hopes.
- **Human checkpoint**: who reviews, and at which step.
- **Last reviewed**, with a date. Material entries get reviewed every quarter.

If that looks like your outsourcing register, good. Same discipline, new object. Our guide to [building an AI audit trail](/writing/building-an-ai-audit-trail) covers what the logs behind each Material entry should hold, and [human-in-the-loop AI](/writing/human-in-the-loop-ai) covers where the checkpoints go.

## Guernsey reached the same place

Groups with a Guernsey business can run one register for both islands. The GFSC’s [January 2026 policy statement](https://www.gfsc.gg/news/policy-statement-use-artificial-intelligence) also declines to write AI-specific rules. It asks firms to treat AI like any other technical or strategic project under the Finance Sector Code of Corporate Governance, and points to NIST’s AI Risk Management Framework, ISO/IEC 42001 and NCSC guidance for reference. Different words, same questions. We will map the wider picture, the UK and EU included, in a later post.

## The 30-day plan

Thirty days is enough. Week one, find everything: ask every team what AI they use, including the free tools on their phones, because the unofficial ones are the ones that hurt. Week two, run the four-trigger test on each and name an owner. Week three, write down the controls for every Material entry and add them to the business risk assessment. Week four, take one page to the board: the register, the three biggest risks, and the decisions you need from them.

The target is simple. Every AI use case in the firm on one register, with a named owner, inside 30 days. The point is speed, not paperwork. Once the sorting is done, nobody has to reargue what is allowed every time someone has a good idea.

If you want the register built for you, or would rather sort it yourself and talk through the Material entries, [book a review](/book-a-review). Either way: sort first, build second.
