How verification works
Elsin checks a little at every stage, so real candidates barely notice and fakes meet a check at each step.
The stages
| Stage | The candidate | Elsin |
|---|---|---|
| Apply | Nothing extra. No account needed. | Scores device, network, contact and résumé signals in the background. |
| Shortlist | One ID and face check on their phone, about two minutes. | Reads the ID, checks liveness and matches the face on the device. |
| Interview | Scans the same ID and turns their head twice. | Confirms the person interviewing is the person who verified. |
| Offer | Optionally confirms past jobs. | Checks claimed jobs through a work inbox, a referee or a document. |
| Day one | The same short check. | Confirms the person starting is the person who applied. |
Apply scoring always runs. The shortlist check is sent automatically when a candidate reaches an interview, assessment or offer stage, unless you turn that off. The interview check is sent when an interview is scheduled, and the day one check when someone is marked hired. The work history check is off by default.
What your team sees
Each candidate carries one verdict, such as Verified or Needs review, with the reasons written out. Nobody sees the raw signals unless they open the assessment. See verdicts.
Rules that do not bend
- Elsin never rejects anyone. The strongest thing a signal can do is send a candidate to your review queue.
- Face images and video stay on the candidate's device. See biometrics.
- The camera does not start until the candidate has agreed to a versioned consent notice.
- Anyone who cannot or will not scan their face can send their ID to a person instead.
- Only keyed hashes cross between employers, never another employer's candidates.
The face match thresholds and the behaviour thresholds have not yet been tuned on real-world data. Treat a grey-band result as a reason to look, not as an answer.