For employers
Know where your candidates actually are
Most programmes find out a candidate is behind when the submission deadline arrives. A structured record, updated as work happens, changes when you find out.
What you see
Cohort views built from real activity
Exposure gaps
Which required areas of experience nobody in the cohort has been given work in yet.
Review latency
How long confirmed drafts have been waiting for a mentor, by mentor and by programme.
Mentor workload
Capacity against current load, so you can see who is over-committed before reviews stall.
Training outcomes
Attempts, passes and where people repeatedly struggle — tied to preparation themes.
Intervention queue
Every recommendation with the facts behind it, an owner and a due date.
Cohort CSV export
Download the current filtered summary. Denominators and date ranges travel with it.
Boundaries
What employers deliberately cannot see
- No raw voice recordings and no transcript text in any aggregate view.
- No single score that predicts whether someone will register. We do not produce one.
- No ranking of individuals against each other. Comparison is against the requirements, not colleagues.
- No personality, emotion, accent or demographic inference. Nothing of that kind is computed anywhere.
- Where data is missing, it is labelled insufficient information rather than counted as zero.
The cohort in this build is synthetic
Every candidate, mentor and outcome in the employer view is generated sample data, clearly labelled in the interface. No real programme data has been imported, and no notification is ever sent to anyone from this review version.