Sector playbooks
AI for KYC and client take-on in trust and corporate services
Client take-on is the most manual, least billable week in a trust administrator’s month. AI can collect the documents, extract the data, run the screening and draft the risk assessment. The decision stays human, and the audit trail is there from the first click.
By Seb Lawson · 11 June 2026 · 5 min read
Client take-on is the slowest, least billable stretch of a trust administrator’s month, and it is the one AI shortens most. Collect the documents, read them, extract the data points, run the screening, draft the risk assessment: almost all of it is structured, repeatable work sitting behind a human decision. Automate the assembly and the drafting, keep the judgement and the sign-off with a person, and a take-on that used to run over days lands in hours. In our experience the manual effort on a standard onboarding drops by 60 to 70 percent, and the wait is measured in hours rather than a fortnight of chasing.
This is the workflow we build most often for trust and corporate services firms, because the pain is universal and the shape of the fix is well understood. Here is how it breaks down, and where the human has to stay.
Document collection stops being a chase
Most take-on delay is not analysis. It is waiting. Waiting for a passport, a proof of address, a structure chart, a source-of-funds explanation that never arrives in one go. An automation can send the request list, track what has come back, read each document on arrival, and chase the gaps on a schedule without an administrator holding the whole thing in their head. The system knows what a complete file looks like and tells you exactly what is still missing. That single change, turning a manual chase into a tracked queue, often recovers more time than the clever extraction that follows.
Extraction and verification, checked not trusted
Once a document arrives, AI reads it and pulls out the fields your onboarding system needs: names, dates, addresses, ownership percentages, the shape of the structure. This is the same document extraction engine that powers the rest of the back office, tuned to the forms you actually receive. The important word is verification. The model proposes; it does not decide. Where a passport photo is unreadable or an address does not match, the case is flagged rather than guessed. High-confidence fields flow through, low-confidence fields wait for a human. Getting that threshold right is most of the work, and it is why we test against your own historic files before anything goes live.
Screening and risk-scoring, assembled for a reviewer
Screening against sanctions, PEP and adverse-media lists is already largely automated in most firms. The value AI adds is upstream and downstream: pulling the right names and entities out of the structure so nothing is screened by hand, and then assembling the hits into an evidence pack a reviewer can actually work through. Instead of a raw list of 40 possible matches, the reviewer sees each one summarised, ranked by relevance, with the underlying source one click away. A first-pass risk assessment gets drafted from the same inputs, in your house rating logic, ready for a human to accept, adjust or reject. The draft is a starting point, never the verdict.
The decision stays human, and that is the point
Nothing here approves a client. The system does the collection, the reading, the screening and the drafting; a named person makes the call. This is not a compliance nicety, it is the design. The JFSC expects meaningful human oversight that scales with how much damage a use case could do, and onboarding a client is about as high-stakes as it gets. So the human checkpoint is real: the reviewer sees the evidence, can override any machine output, and signs the decision themselves. If a wrong output could reach a regulator or open the door to dirty money, a person stands between the model and the outcome.
The audit trail is there from the first click
Every take-on leaves a complete record: which documents came in and when, what the model extracted, what it flagged, which screening ran against which lists, the draft risk assessment, and who approved the final decision, with the prompt and model version logged alongside. Built in from the start this is nearly free. Bolted on after a supervisor asks, it is painful and often impossible to reconstruct. We covered exactly what to capture in building an AI audit trail. For a regulated firm this is the difference between a system a supervisor nods at and one that gets you a finding.
Periodic reviews reuse the same machine
The best part is that take-on and periodic review are the same workflow pointed at different moments. Once the collection, extraction, screening and drafting are built for onboarding, a trigger-event or scheduled review reuses all of it: refresh the documents, re-run the screening, pull out what has changed since last time, and draft the review pack ready for sign-off ahead of the deadline. Firms that dread the periodic review backlog find it stops being a backlog. The pack assembles itself; the administrator reviews and approves. Build once, use twice.
What it takes to stand up
Before you build a take-on assistant, it is worth mapping the whole process first so you automate the right client type in the right order. Start narrow. Pick your highest-volume, most painful onboarding flow, prove the pattern with the audit trail and the human checkpoint working properly, then extend it to the next structure and to periodic reviews. That is how the numbers land and how the regulator stays comfortable.
If client take-on is eating your team’s week, a 30-minute review will get you a candid read on which part to automate first and what it is worth. No deck, no hype. Just the smallest painful workflow and a number against it.