> For the complete documentation index, see [llms.txt](https://docs.senseloaf.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.senseloaf.ai/candidate-listing/candidate-profile-verification.md). # Candidate Profile Verification When a candidate applies, their resume is a self-reported document. Candidate Profile Verification automates the cross-check — comparing what's on the resume against external, publicly-derived data and giving you a clear checklist of what matches, what partially matches, what conflicts, and what couldn't be checked. It is a **decision-support tool, not a decision-maker.** It never rejects, blocks, or auto-advances a candidate. It surfaces discrepancies, a human always makes the call. ### What gets verified Candidate Profile Verification checks **10 individual facts** across four categories, comparing what's on the resume against external, publicly-derived data: * **Identity** — does the candidate's name and email match external records? * **Employment** — do their current company, title, job history, and tenure dates align? * **Education** — does their claimed school, degree, and major match externally? * **Location** — does their claimed country and city match external records? Each fact is given a plain-language outcome, matched, partial, not matched, or unverifiable, and rolled up into an overall verification result. {% hint style="warning" %} Candidate Profile Verification is a subscription feature. If you don't see the option in your account, contact your Senseloaf admin or reach out to to enable it. {% endhint %} ### Where to find it The feature lives on the **Candidate Listing page** — the same screen you already use to see applicants, grades, and pipeline status.

Profile Verification on Candidate Listing page

There are two ways to start a verification: * **One candidate at a time** — open the ⋯ menu on a candidate's row and click **Verify Profile** * **Multiple candidates at once** — tick the checkboxes next to several candidates and click the **Profile Verification** button in the bulk action bar (up to 50 candidates per request) Both are entirely manual, nothing in the pipeline triggers verification automatically. **When verification is available:** * Verification is available for candidates who have actively applied and are in an active pipeline stage * It is not available for sourced candidates (who haven't applied yet) or candidates marked as archived, expired, or deleted * Candidates without a LinkedIn URL on their profile will be skipped — verification uses LinkedIn as the anchor for matching against external data **Verification runs once per candidate.** Once a result is complete, the option to re-verify is unavailable. The row will show **Profile Verified** instead of the button. #### Verifying one candidate

Verifying one candidate

* Open the ⋯ menu on a candidate's row and click **Verify Profile** * The menu item becomes disabled and the row's Verification column shows **Verifying...** — you can keep working on other candidates while this runs in the background * If you open the candidate's report card during the check, you'll see a live progress state — a pulsing dot and a status line that updates as the system works through each category * When complete, a toast notification appears with the result — for example *"Ashish's profile is verified"* or *"...partially verified"* * The report card fills in with the [full verification report](#understanding-the-verification-report) and the Verification column on the candidate list updates automatically #### Verifying multiple candidates

Verifying multiple candidates

* Tick the checkboxes next to the candidates you want to verify (up to 50) * Click the **Profile Verification** button in the bulk action bar * A confirmation dialog shows exactly what will happen — for example *"38/50 candidates' profiles will be verified"* — with a breakdown of what's being skipped and why (already verified, no LinkedIn, already in progress) * Click **Confirm** to start * A floating progress panel tracks each candidate's verification status in real time — you can minimise it and keep working while checks run in the background * As each check completes, the candidate's row on the listing updates independently — you don't need to wait for the full batch to see results come in #### Understanding the verification report When a check is complete, the candidate's report card shows a full verification report.

Profile Verification Report

**Overview** * A **match score gauge** (e.g. 7/10 matched) * An **overall status badge** — Verified, Partially Verified, Not Verified, or Insufficient Information * A short **plain-language summary** calling out anything notable — for example a title that appears inflated or an employment gap the resume doesn't explain **Category breakdown** Each of the four categories (Identity, Employment, Education, Location) appears as its own card, listing the individual checks with a clear icon: * ✅ **Matched** — external data confirms the resume's claim * ⚠️ **Partial** — probably the same, but with a notable difference worth a second look * ❌ **Not matched** — the resume's claim conflicts with what's found externally * **—** **Unverifiable** — not enough external data to check this one either way {% hint style="warning" %} Unverifiable is not a red flag. It's an honest "we don't know," not "something's wrong." Only Not Matched results are direct discrepancies. {% endhint %} **How the overall result is calculated:** * Each matched or partial fact = 1 point (out of 10 total) * **7–10** = Verified * **3–6** = Partially Verified * **0–2** = Not Verified * If every single fact is unverifiable = **Insufficient Information** (shown as a distinct, non-judgmental outcome) ### What verification does not do * **It never auto-rejects a candidate** — a Not Matched result is a prompt for a human to ask a question, never an automatic disqualification * **It doesn't contact the candidate** — it only compares what's already on file against public external data; the candidate is not asked for anything new * **It doesn't trigger automatically** — verification only runs when a recruiter deliberately requests it, either for one candidate or a batch --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.senseloaf.ai/candidate-listing/candidate-profile-verification.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.