Built for
Operations & complianceFor operations and compliance leads
If a rejected candidate asks why, somebody has to answer. That answer needs to have existed at the time, not been written afterwards.
What you are held to
Whether a decision can be explained six months later.
Built from the application’s own components rather than screenshotted. Illustrative data.
The week you actually have
Four things that go wrong before lunch.
The reason lives in a person, not a record
Ask why a candidate was rejected and you get a recollection. UK GDPR gives that candidate the right to a real answer, and a recollection is not one.
AI screening tools do not show their working
A score with no evidence behind it is not defensible. It is a number somebody has to take on faith, in a process where faith is exactly what a regulator will not accept.
The bar moves and nobody notices
If the standard is remembered rather than written, it drifts. Drift is how a process that was fair in January stops being fair by June.
Candidate data goes somewhere and you cannot say where
You are the controller. Your processor's sub-processors are your problem, and "it uses AI" is not a data map.
What answers it
The modules that touch your day.
The rubric is written on the role before the first CV is read, and every score carries the lines of the CV it came from.
Decisions and their reasons are recorded as they are made, so the record of why is contemporaneous rather than reconstructed.
The distribution of scores per role, so a bar that has drifted is visible as a shape rather than a feeling.
What changes
Every rejection has a written reason that existed at the time it was made, tied to a rubric that existed before the pile did.
What you will ask on the call
The objections, answered straight.
Somebody else in the room
The same product, their reasons.
The offer
See it on a role you are working today.
Twenty minutes, your own job description, your own CVs. You judge it on the shortlist it produces.
- 1Twenty minutesYou bring one live hiring workflow and the real inputs it uses. We look at it together—no deck or discovery questionnaire.
- 2Set up on the callWe configure the module you intend to buy and run the first real step with you while you watch.
- 3Then 7 days aloneYour team runs it on live work and judges the outcome you agreed upfront—not anything we said.