Skip to main content
Curvestone AI
Point of view

Spot-checking case files was a workaround, not a strategy

Updated

The 10% was never a risk number

Ask a compliance team why it reviews around 10% of its files and you get one of two answers. The first is "it is risk-based". The second, said more quietly, is "it is what we can get through". The second is the honest one.

The maths explains it. A manual file review runs from under an hour to the best part of two. At that rate, checking every case would need a team few networks or lenders could fund. So the industry checked what it could, called the result a sample and built a process around it. A compliance director once described it to me as "compliance theatre".

That was a fair compromise while every file took an hour or more to read. It is a weak one now.

Why this matters now

The pressure is the Consumer Duty. The FCA says its rules require firms to "monitor and regularly review the outcomes their customers are experiencing" and to "identify where customers or groups of customers are not getting good outcomes and understand why". A firm's governing body has to review and approve its assessment of customer outcomes at least annually.

Groups of customers is where a small sample struggles. A 10% sample can show that one file was poorly advised. It cannot easily show that one adviser keeps missing the same vulnerability signal, or that one type of case keeps failing the same check, because the pattern sits in files nobody opened.

Then there is a line I think most firms skip. The FCA suggests firms ask themselves "whether they are using the same MI capabilities they use to inform other elements of their business, such as product development or sales, to also monitor outcomes." Sales MI usually covers every case. File review MI usually covers one case in ten.

The strongest objection: the FCA accepts sampling

It does, and I would not tell anyone otherwise. FG22/5 says that some monitoring may cover all customers, "while other types of monitoring, such as distributional analysis or file reviews will be based on a risk-based sample." It also expects file reviews to happen "at regular intervals or on an ad hoc basis" rather than all the time. A firm that samples is not breaking a rule.

But read the phrase again: a risk-based sample. A sample whose size comes from reviewer hours, and whose cases are mostly picked at random, is a capacity-based sample with a risk-based label. The difference is what a firm has to explain when something goes wrong in the 90% nobody read.

The guidance also says the FCA expects firms "to continually review and develop their frameworks", and it expects firms with more sophisticated data strategies to have more detailed monitoring strategies. A sample that was proportionate when every file took an hour to read does not stay proportionate when it no longer does.

So my argument is not that sampling is banned. It is that the reason for the sample size has changed, and the old reason no longer holds.

What most firms get wrong

  • They treat the sample as the control. The sample is one input into outcome monitoring, not the whole of it.
  • They pick cases at random and call it risk-based. Risk-based selection needs a risk signal, and most firms have none until a file is read.
  • They report the sample's pass rate as if it described the book. A 95% pass rate on one case in ten says little about the other nine.
  • They assume checking every case means a machine makes the call. It does not, and it should not.

What good looks like

A consistent check runs on every case, and every finding points to the page and document it came from. A person reviews the findings and approves or overrides them. The deep human file review then goes where the full check points: the advisers, case types and findings that need judgement. Only then is the sample risk-based, because the risk signal comes from every case, not from chance.

The MI changes too. Instead of a pass rate on a sample, the board sees which advisers miss which checks, how often and on what kind of case. That is the "groups of customers" view the Duty asks for.

This is how we built Curvestone: each finding shows its reasoning and source evidence, a person approves or overrides it, and every step goes into the audit trail. The software does the reading. The accountable person does the judging.

What to do next

  1. Write down why your sample is the size it is. If the honest answer is capacity, say so in your next board pack.
  2. Look at how cases are selected. If selection is random, the sample is not yet risk-based.
  3. Compare the coverage of your sales MI with the coverage of your file review MI.
  4. Work out what one manual file review costs you today, so the comparison with checking every case is honest.
  5. Ask what your next annual outcomes assessment would say if it covered every case, not one in ten.

An earlier version of this argument appeared in Mortgage Solutions (July 2026).

Questions

Frequently asked questions

Does the FCA require firms to check every mortgage file?
No. The FCA's Consumer Duty guidance, FG22/5, says file reviews "will be based on a risk-based sample". It does expect firms to monitor outcomes, find groups of customers getting poor outcomes, understand why, and keep developing their monitoring. The fair question is whether a firm's sample is truly risk-based or simply sized by reviewer hours.
Does checking every case remove the need for human file reviewers?
No. An automated check can read every file and show where evidence is missing or inconsistent, with the source page attached. A person still decides whether the outcome was right for the customer and approves or overrides each finding. Reviewers spend less time searching files and more time judging the cases that need judgement.
Sources
  1. 01FG22/5 Final non-Handbook guidance for firms on the Consumer Duty (FCA)
  2. 02Why spot-checking case files can no longer be a compliance strategy, Dawid Kotur, Mortgage Solutions, 27 July 2026
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.