Skip to main content
Curvestone AI
Definition

Can an automated compliance check use your own checklist?

Updated

Why buyers ask this first

On calls with mortgage networks, lenders and brokers, this question comes up early and often. A compliance team lead at a UK mortgage network put it simply: "So for example, if we evolve our case checking question sets, how easy is it to change?"

The worry is fair. A network's question set reflects how it reads the rules, what its file reviews have found and where its risk appetite sits. A tool that throws that away, or that needs a change request every time a question moves, creates more work than it saves.

Are FCA rules built in?

Not in the way buyers hope. In its AI Update, the FCA describes itself as "a technology-agnostic, principles-based and outcomes-focused regulator". It also says its "rules, regulations and core principles do not usually mandate or prohibit specific technologies".

So there is no official FCA checklist for a mortgage file that a vendor can load and keep up to date. MCOB, Consumer Duty and the Principles set the obligations. How your firm tests a case against them is your call, and your question set is where that call is written down.

Responsibility stays with the firm. Under Principle 3, firms must "take reasonable care to organise and control their affairs responsibly, effectively and with adequate risk management systems". A checklist you cannot read, explain or change does not help you show that.

Treat any claim that a tool "has the FCA rules built in" as a prompt for questions. Which rules, written by whom, tested against what, and updated when?

What "your own checklist" should mean in practice

A check that runs your checklist should:

  • review every document in the case file against your question set, question by question
  • grade every answer and cite the evidence it relied on, so a reviewer can see why
  • run on every case, not a sample
  • start from standard checks for each advice type (mortgage, protection, wealth) that you tailor to your in-house rules, so you are not writing every question from scratch

For the questions themselves, our guide to the MCOB suitability points advisers most often get wrong is a useful place to test your current set.

How changes to the checklist should work

Your question set will change as rules move and file reviews and Consumer Duty monitoring find new issues. FG22/5 says firms need processes to "adapt and change products and services, or policies and practices, to address any risks or issues identified".

For a checklist, that means:

  1. No engineering project. A question set should be configuration, not code, so a change does not wait for a vendor's development cycle.
  2. Versions with an author. Every change gets a version number, a named author and a changelog entry.
  3. Results tied to a version. Each case result should show which version of the checklist it was checked against. When a regulator or a board asks why a case passed in March, you can show the question as it stood in March.
  4. Disagreements feed the next version. When reviewers keep overriding the same answer, that pattern should become a proposed change to the question, inspected before it goes live.

The FCA expects firms, if asked, "to be able to explain how they reached a decision on the most appropriate intervention". A versioned checklist with a changelog is part of that explanation.

Human review stays in the loop

An automated check does the first read. A person reviews the result, overrides what is wrong and makes the decision, and the case carries that decision alongside the check's answer. The overrides show where the question set needs work.

Questions to ask any vendor about checklists

  1. Does the check run our question set, or a fixed list of its own?
  2. If it says FCA rules are built in, which rules, and who keeps them current?
  3. Who changes a question, and does it need a development project?
  4. Is every change versioned with an author and a changelog?
  5. Does each case result show which checklist version it was checked against?
  6. What happens when our reviewers disagree with an answer?

If you are still deciding whether to build this in-house, our post on whether to build or buy AI compliance covers the wider trade-offs.

Curvestone checks every document in the case file against your firm's own standard and checklist, question by question, with every answer graded and the evidence cited, on every case. Standard checks for mortgage, protection and wealth advice work out of the box and can be tailored to your in-house rules. Changing a question set needs no engineering project, every change is a numbered version with an author and a changelog, and reviewer disagreements can become a proposed change that is inspected before it goes live. To see it run against a checklist like yours, book a call or a demo.

Questions

Frequently asked questions

Can an automated compliance check use our own checklist?
It should. Ask whether the check runs your firm's question set, question by question, or a fixed list of the vendor's own. Standard checks for each advice type are a useful starting point, but you should be able to tailor them to your in-house rules, and each answer should cite the evidence it relied on.
Does compliance checklist software come with FCA rules built in?
Be careful with that claim. The FCA describes itself as principles-based and outcomes-focused, and its rules do not usually mandate specific technologies. There is no official FCA case checklist a vendor can load. Ask which rules a tool says it covers, who wrote the questions, how they were tested and how often they are updated.
How often should a case-checking question set change?
Whenever your reading of the rules, your file review findings or your Consumer Duty monitoring says it should. FG22/5 expects processes to change policies and practices when issues are identified. What matters is that each change is versioned, has a named author and a changelog, and that every case result shows which version it used.
What happens when a reviewer disagrees with the automated check?
The reviewer overrides the answer and the case carries their decision. Those overrides are useful data. When reviewers keep disagreeing with the same answer, it usually means the question is unclear or out of date, and that pattern should become a proposed change, inspected before it goes into the live question set.
Sources
  1. 01AI Update (FCA)
  2. 02FG22/5 Final non-Handbook guidance for firms on the Consumer Duty (FCA)
Related reading
Dawid Kotur
Written by

Dawid Kotur

CEO and co-founder, Curvestone

Dawid co-founded Curvestone in 2024 after a decade working at the intersection of financial services and applied machine learning. He writes about the strategic direction of regulated-industry AI, the FCA's evolving approach to model risk, and the operational changes UK lenders are making in response to Consumer Duty. He sits on the FCA Smart Data Accelerator advisory cohort.

LinkedIn

Compliance that thinksahead. Automatically.

Join mortgage networks, lenders, and legal firms using Curvestone to review cases at scale.