Start with the question you're actually trying to answer
Before listing checks, it helps to be specific about what a background verification is meant to answer:
- Is this person who they say they are? → identity verification
- Did they actually work where and when they say they did? → employment verification
- Is there anything in their legal history relevant to this role? → legal/court-record verification
Treating these as three separate questions — rather than one vague "run a background check" instruction — makes it much easier to decide what's actually needed for a given role.
The core checklist
1. Identity verification
At minimum, verify the primary identity document a candidate has submitted:
- PAN verification — confirms the PAN is valid and returns the registered name for a match check
- Voter ID verification or Driving Licence verification — useful as a secondary identity confirmation
- UAN verification — where relevant, links a candidate to their EPF employment history
2. Employment verification
Confirm what's on the resume against what the previous employer actually reports:
- Dates of employment
- Designation held
- Whether the exit was voluntary
Employment verification on VerifyAll runs this as a consent-based workflow — the candidate consents, the employer receives a structured request, and the response is tracked with reminders rather than left to an unanswered email thread.
3. Legal / court-record verification
For roles with financial authority, legal signing rights, or public-facing responsibility, a legal verification check surfaces litigation or court records tied to the candidate. This isn't necessary for every hire, but skipping it for a role where it matters is a real gap in the process, not a shortcut.
4. Business background verification (for non-employee relationships)
Not every "who are we bringing on" question is about an employee. When the person represents a vendor, franchisee or contracting business, business background verification checks the entity itself, not just the individual.
A quick reference table
| Check | What it confirms | Typical turnaround |
|---|---|---|
| PAN verification | Identity, name match | Seconds |
| Voter ID / Driving Licence | Secondary identity confirmation | Seconds |
| UAN verification | EPF-linked employment history | Seconds |
| Employment verification | Direct employer confirmation | Days (tracked) |
| Legal verification | Litigation / court records | Minutes to hours |
Common gaps in a checklist that "looks complete"
- No fallback when an employer doesn't respond. Build in a defined escalation — a UAN check, a documented number of reminder attempts, or a manager sign-off on proceeding without full confirmation.
- Legal checks applied inconsistently. If it's part of your policy for finance roles, it should be applied to every finance hire, not just the ones someone remembered to flag.
- No process for discrepancies. Decide in advance what happens when a check comes back with a mismatch — who reviews it, and what the range of outcomes is — rather than improvising when it happens.
- Consent treated as a formality. Candidates should know specifically what's being checked, not just sign a generic release buried in the offer letter.
Putting it into a repeatable workflow
Once you know which checks apply to which roles, the operational question is how to run them without adding manual work for every hire. On VerifyAll, HR teams run identity, employment and legal checks from one dashboard, and for high-volume hiring, bulk verification applies the same checklist across a whole candidate list in one upload. For the bigger picture on structuring a full verification process — not just the checklist — see our guide to background verification for employers in 2026.
Ready to put this checklist into practice? Talk to our team about setting up employee verification for your hiring volume.