> 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/agents-output/candidate-profile-verification.md).

# Candidate Profile Verification

Bring an extra layer of confidence to every candidate you review

When a candidate applies, their resume is a self-reported document. A resume and a LinkedIn profile may look like they belong to the same person because both were provided by the candidate — but that alone doesn't confirm whether their companies, job titles, dates, education, or location are accurate.

Candidate Profile Verification automates the cross-check by comparing the candidate's resume with information from an external professional profile. It gives you a clear, structured view of what is supported, what differs, and what couldn't be checked — so your team can make more informed decisions without manually googling every applicant.

It is a **decision-support tool, not a decision-maker.** It never rejects, blocks, or auto-advances a candidate. It surfaces discrepancies and then a human always makes the call.

### What gets verified

Profile Verification checks four areas, comparing what's on the resume against an external professional profile:

* **Identity** — whether the external profile appears to belong to the same person as the candidate
* **Employment** — the candidate's companies, roles, work history, and employment dates. Clear conflicts may be shown as Contradicted
* **Education** — the institutions, degrees, and majors listed by the candidate
* **Location** — the candidate's country and city compared with the location on the external profile

### Where to find it

<figure><img src="https://1117388020-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGO7J9uIHFkn8y0ZeBqYC%2Fuploads%2FO1q9qVRWG7NPNW39p1m2%2FCandidate%20Profile%20Verification.gif?alt=media&amp;token=678e2c97-120a-453b-921c-b76a72252106" alt=""><figcaption><p>Verify Profile</p></figcaption></figure>

There are three 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)
* **From the report card** — open any candidate's report card and click the **Profile Verification** tab to trigger verification directly from within the candidate's profile

<figure><img src="https://1117388020-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGO7J9uIHFkn8y0ZeBqYC%2Fuploads%2FOH7Bq3QxAkwqdHBcYvfr%2FScreenshot%202026-10-16%20at%2018.02.07.png?alt=media&amp;token=5258b26c-e697-4a50-84ea-45b97b439d87" alt=""><figcaption><p>Verify Profile From Report Card</p></figcaption></figure>

{% hint style="info" %}
Nothing in the pipeline triggers verification automatically.
{% endhint %}

**When verification is available:**

* Available for candidates who have actively applied and are in an active pipeline stage
* 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 shows **Profile Verified** instead of the button.

<figure><img src="https://1117388020-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGO7J9uIHFkn8y0ZeBqYC%2Fuploads%2FZCrkYXZ3fFlctrVArdFq%2FScreenshot%202026-10-16%20at%2018.00.06.png?alt=media&amp;token=8c925954-51c0-4232-8daf-4d1f4357e497" alt=""><figcaption><p>Profile Verified</p></figcaption></figure>

### Automating profile verification

Candidate Profile Verification can also be triggered automatically as part of your hiring workflow, so you don't have to manually initiate it for each candidate. Instead of selecting candidates one by one or in bulk, you can set up a rule that runs verification automatically when a candidate completes a specific stage.

**Setting it up**

Add **Profile Verification** as an action in your hiring workflow automation rules. You can configure it to trigger after any of the following stages complete:

* Resume Matching
* AI Prescreening
* AI Interview

Once a candidate reaches the configured stage, the system checks whether verification can run and, if all conditions are met, triggers it automatically in the background, with no manual action needed from your team.

**Before verification runs, the system checks that:**

* Profile Verification is enabled for your organisation
* The candidate has not already been verified — verification is designed to run only once per candidate
* The candidate has a LinkedIn URL on their profile — verification uses this as the anchor for matching against external data
* No verification is already in progress for the candidate

If any of these checks fail, the candidate is skipped and the reason is logged. Other automation actions in the workflow continue to run as normal. A skipped verification does not block the rest of the pipeline.

### Understanding the verification report

When a check is complete, the candidate's report card shows a full verification report covering every entry that was checked.

<figure><img src="https://1117388020-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGO7J9uIHFkn8y0ZeBqYC%2Fuploads%2FJR5eQ9jwzQYzsXWefm79%2Fdownload.gif?alt=media&amp;token=8dbb3574-4a44-4a70-a959-658bc09f91ff" alt=""><figcaption><p>Verification Report</p></figcaption></figure>

**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

**Category breakdown**

Each of the four categories (Identity, Employment, Education, Location) is broken down into individual checks. For each entry, you can see:

* The information provided by the candidate
* The matching information from the external profile, when available
* The result for that entry
* A short explanation of the result

### What the individual checks compare

**Identity**

| Check | What we compare                                                                                                                                                   |
| ----- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Name  | The candidate's name and the name on the external profile. Reasonable differences such as initials, nicknames, or spelling variations may still count as a match. |
| Email | The candidate's email and emails on the external profile.                                                                                                         |

**Employment**

| Check              | What we compare                                                                                                                                                                                                              |
| ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Latest company     | The candidate's most recent company and the company on the external profile. A company rename or acquisition may still count as a match.                                                                                     |
| Latest title       | The candidate's latest job title and the title on the external profile. Differences in seniority (e.g. "Engineer" vs "Senior Engineer") do not currently fail this check.                                                    |
| Employment history | The companies listed on the resume and the companies on the external profile. Each job is considered separately. A claim missing from an otherwise available history is **Not Found**. A clear conflict is **Contradicted**. |
| Employment dates   | The start and end dates for each job. Small differences in month may be acceptable. Large or clearly conflicting gaps may be **Contradicted**. Missing dates are **Unverifiable**.                                           |

**Education**

| Check           | What we compare                                                                                                                                                                      |
| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Institution     | The institutions listed on the resume and the institutions on the external profile. Common abbreviations, renamed institutions, and valid affiliated institutions may be recognised. |
| Degree or Major | The candidate's qualifications and fields of study. A matching degree or a matching major can be enough. Missing degree information is not automatically treated as a mismatch.      |

**Location**

| Check   | What we compare                                                                                                         |
| ------- | ----------------------------------------------------------------------------------------------------------------------- |
| Country | Whether both sources show the same country.                                                                             |
| City    | The city on the resume and the city on the external profile. A nearby or related place may be shown as a partial match. |

### Understanding the results

| Result                | What it means                                                                                         |
| --------------------- | ----------------------------------------------------------------------------------------------------- |
| **Matched**           | The external information supports the candidate's claim.                                              |
| **Partially matched** | Some information supports the claim, but there is also a difference or missing detail.                |
| **Not Found**         | The external profile has no record of a specific candidate claim.                                     |
| **Contradicted**      | The external profile clearly shows information that conflicts with the candidate's claim.             |
| **Not matched**       | The available information does not support the claim or shows a clear difference.                     |
| **Unverifiable**      | There is not enough information to make a fair comparison. This does not mean the candidate is wrong. |

**How the overall result is calculated:**

* Each matched or partially matched 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** (a distinct, non-judgmental outcome — not a low score)

### Missing information vs. conflicting information

These two situations look similar but mean very different things:

**Missing information** — the external profile simply doesn't have a record of something. For example, it may not list an old employer or may not include a degree. In that situation the result is **Unverifiable** or **Partially matched** — not a red flag.

**Conflicting information** — the external profile clearly shows something different. For example, a different company, a different country, or employment dates that clearly don't line up. This may result in **Not matched** or **Contradicted**.

**Contradicted** is the strongest signal — it means there is a clear, direct conflict between what the candidate claims and what the external profile shows. It is different from **Not Found** (no record exists) and **Unverifiable** (not enough information to compare).

{% hint style="warning" %}
**Note:** The identity check runs first. If the external profile clearly belongs to someone else, all other checks are shown as **Unverifiable,** even if some company, education, or location details happen to look similar. If the external profile has no name information, the result is also **Unverifiable**; missing information is not treated as a mismatch.
{% endhint %}

### What verification does not do

* **It never auto-rejects a candidate** — a Not Matched or Contradicted 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 external public data; the candidate is not asked for anything new
* **It doesn't trigger automatically** — verification only runs when a recruiter deliberately requests it


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.senseloaf.ai/agents-output/candidate-profile-verification.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
