Verified Prep and defensibility on a candidate
Candidate-consented prep signals plus a per-bullet evidence ledger — what they did to prepare, and what they can defend in an interview.
The Verified Prep panel
On a candidate profile, the Verified Prep panel appears only when the candidate explicitly shared their prep — it carries a "Shared by candidate" chip. It summarises:
- CV Tailored — whether they tailored for this role, at which intensity, and the Authenticity N/100 score (or "not yet graded").
- Which CV variant they applied with — Raw CV, Parsed CV or Tailored CV — when recorded.
- Cover Letter — generated or not, word count, and a Read cover letter expander.
- Interview Drills — drills completed and average coverage. You never see their actual answers.
The privacy default — read it correctly
When there's no panel you'll see one grey line: "Candidate has not shared their prep signals." This renders identically whether the candidate prepped privately or didn't prep at all — by design, you cannot tell the difference, so non-sharing can't be held against anyone. CVs you uploaded yourself read "Candidate applied via recruiter upload; no prep signals available."
The Defensibility panel
Below the notes sits Defensibility — "Per-bullet evidence ledger — what the candidate can defend in an interview." The header gives the plain-English aggregate ("N of M bullets grounded") and each bullet carries a chip:
- Grounded (green) — supported by the source CV.
- Verified (amber) — the ledger flagged it, and the candidate explicitly confirmed they can defend it. Candidate-confirmed, not independently verified.
- Unsupported (red) — no source match and not confirmed.
- Ungraded — not yet graded by the authenticity check.
Click any bullet to load the source-CV excerpt that grounds it — the evidence is the candidate's own CV text.
The badge and the frozen snapshot
When a candidate shares a pack, its public page carries the A1 Verified badge and a "Verify the badge ↗" link to the signed, tamper-evident record. The authenticity snapshot is frozen at the moment the candidate approved, so what you see is exactly what they signed off — later re-tailoring doesn't rewrite it. To pull a shared pack into your own pipeline, see claiming a verified pack.