Scan the documents.
Flag the mismatches.
A first look at AI-assisted BPSS screening QA for CV Insight, built around your own process.
This document contains
One analyst. A rising pile.
We build an AI system to automate it.
Processing thousands of applications per minute, while your analyst signs off.
Watch it check.
Choose how the documents arrive. The machine does the comparing; your analyst signs off the flags.
Check one candidate
Drop their right-to-work and reference documents here. CV Insight reads every field and compares it to what's on record.
No file handy? Run it on a sample. Illustrative, dummy data only.
Reading the documents…
Comparing every field against the record.
Verification report
| Field | On the document | On record | Result |
|---|---|---|---|
| Name | Jordan A. Michaels | Jordan Michaels | Match |
| Date of birth | 14 Mar 1991 | 14 Mar 1991 | Match |
| Address | 48 Pelham Rd, Brighton | 48 Pelham Road, Flat 2 | Review |
| NI number | QQ 12 34 56 C | QQ 12 34 56 C | Match |
| Employer dates | Jan 2019 – present | Jan 2019 – Aug 2023 | Mismatch |
Run the same checks across 1,000 cases
The exact checks you just saw, applied to a full batch. Watch each case clear or get flagged.
Each square is one case. Green cleared, amber & red were flagged for a human. Illustrative, dummy data.
Batches flow in and get checked around the clock. Every flagged case still lands in the queue, where a human signs off before any decision.
Four stops from one real case to a tool in production
Map the process
Record one real case end to end. We map every document, what it's checked against, where it comes from and how we open it. That's the build blueprint.
What step one delivers: the matrix.
By the end of step one you'll have two things in hand: a clear, documented understanding of how every check is done, and the matrix below, version 0.1: what we check, how we check it, and where each answer comes from. This is my first draft from your SOP. Step one turns it into the real, agreed version we build against.
Matrix v0.1 · drafted from your SOP · click any row for how & why · amber ? = needs your confirmation
How we'd approach this together.
A low-risk path, taken one step at a time. You only commit to the next stage once the last one has earned it.
Map it, prove it, prototype it
I map your real process, confirm there's a viable solution, and build a working prototype, so we both have confidence before committing to a full build.
Fixed feeScope & fix the price
Once you've signed that off, I scope the full build and quote a single fixed fee for everything. No open-ended bills, and you approve it before any build starts.
Fixed quote for the buildLaunch & keep improving
We launch it into your workflow, then keep it running and refine it as we go, with a low monthly maintenance fee.
Low monthly feeYou're never locked in: each stage is a separate, clear decision, and you only move on when the value is obvious.
Built for the data you hold.
You handle passports, NI numbers, HMRC records and DBS results. Anything I add has to clear the same bar you already hold. These are the considerations I'd design around from day one.
Synthetic data until you're satisfied
I build and demo on synthetic or redacted data only. No live candidate data enters the system until your security assessment and DPA are signed.
Inside your compliance, not around it
The tool passes your UK GDPR & ISO/IEC 27001-aligned assessment before go-live. I work as your data processor under a signed DPA, with sub-processor approval for any AI provider.
Never used to train models
Your data is processed only for the comparison in front of it, and kept no longer than the task needs. It is never used to train a model.
Least privilege & a full audit trail
Access is limited to what each check needs, processing stays in approved UK/EU regions, and every comparison is traceable to its source document and page.
A human always decides
The AI compares and flags. It never approves, rejects, or issues a report, your analyst signs off every case. The tool speeds the work; it doesn't make the call.
Two things, and you can send them from here.
Before we build anything, we need to see your real process. The recording is the fastest way; the questions fill in the rest. Answer inline and hit Submit responses, it comes straight to Matt.
-
01Record one real case, end to end REC~10 min
A screen-share with your voice. Walk through a single case and, for each check, tell us which document you're looking at, what you check it against, and where each one comes from (and how you open it). That video becomes our blueprint.
-
02Answer a few quick questions
Click a question to open it. Short replies are perfect, no essays, and answers save as you type.
Anything else?
Thank you, Michelle.
Your answers are on their way to Matt. He'll review them and come back to you to line up the recording. Talk soon.
An approximate timeline, and how to reach me.
A rough shape below; we'll firm up real dates after the discovery. Whenever you're ready, I'm one message away.
Discovery & prototype
Map the process, build a working prototype on dummy data.
Scope & fixed quote
Once we've seen the real process, one fixed price.
Build & deploy
The full build, into your workflow.
Launch & iterate
Live, then refined month to month.