Pre-joining
Background Verification: What to Check, When, and How to Handle a Discrepancy
Deciding your verification scope in advance, running it consistently for every candidate at the same stage, and responding proportionately when something does not match.
Background verification goes wrong in two opposite directions. Some employers skip it and discover a fabricated employment history after someone has been in the role for months. Others run it inconsistently — thoroughly for candidates who made someone uneasy, lightly for those who did not — which is both unreliable and unfair. The fix in each case is the same: decide the scope before you start hiring, apply it to every candidate at the same stage, and have a written response for discrepancies before you encounter one.
This is not legal advice
This is operational guidance on running a consistent verification process, not legal advice. Obligations around consent, data handling, retention and adverse action vary by jurisdiction and are changing as data protection law develops. Have your verification scope, consent wording and discrepancy policy reviewed by qualified counsel before use.
Decide the scope before you post the role
Verification scope should follow from the role, not from how a candidate came across in interview. A finance role handling payments and a junior support role do not need the same checks, and deciding that in advance is what keeps the process consistent.
- Employment history — dates, designation and reason for leaving, from the employer directly
- Education — degree, institution and year, from the university or its verification service
- Identity and address — against government-issued documents
- Reference checks — with people whose identity and relationship you can establish
- Role-specific checks — only where the role genuinely warrants them
Run it at a defined stage, for everyone
Verification usually runs post-offer and pre-joining, with the offer made conditional on satisfactory checks. What matters is that the stage is fixed and the same for every candidate at that level.
Selective verification driven by an interviewer's hunch is the failure mode to design out. It produces inconsistent evidence, it is difficult to justify if challenged, and it tends to fall unevenly across candidates in ways nobody intends.
Tell the candidate what you are doing
Candidates should know what will be verified, when, and with whom, and should give written consent before it happens. This is both good practice and increasingly a compliance expectation as data protection obligations tighten.
It also improves the outcome. Candidates told that employment dates will be verified with HR frequently correct an approximation themselves — which is a much better outcome than a discrepancy report you then have to adjudicate.
- State the scope in the offer letter or a separate consent form
- Take written consent before contacting anyone
- Say when checks will run and roughly how long they take
- Give a named contact for the candidate to raise context proactively
- Do not contact a current employer without explicit permission
Not every discrepancy is a lie
This is where most verification processes behave badly. A mismatch is a fact requiring explanation, not a verdict. Employment dates recorded differently in two HR systems, a designation that differed informally from the one on record, a company that has since been acquired and cannot confirm — all are routine and none indicate dishonesty.
Grade discrepancies by materiality before responding. A one-month date variance and a fabricated degree are not the same event and should not trigger the same response.
- 1Establish the specific mismatch, in writing, from the source
- 2Put it to the candidate and ask for their explanation, with a reasonable deadline
- 3Check whether the discrepancy is material to the role you offered
- 4Decide against your written policy, not against the mood of the moment
- 5Record the decision and the reasoning, whichever way it goes
Common failure modes
Verification processes tend to fail in predictable, avoidable ways.
- Verifying only the candidates someone had a bad feeling about
- Contacting a current employer before the candidate has resigned
- Treating an unreachable former employer as evidence of dishonesty
- Withdrawing an offer over an immaterial variance with no policy behind it
- Running checks after joining, when the leverage and the options are both gone
Frequently asked questions
- When should background verification run?
- Commonly post-offer and pre-joining, with the offer expressly conditional on satisfactory checks. Running it earlier burns effort on candidates you may not hire; running it after joining leaves you with a problem and no clean options.
- Can we contact a candidate's current employer?
- Not without explicit permission. Most candidates have not resigned at the point of verification, and an unauthorised approach can cost them their existing job. Verify current employment through documents such as payslips and appointment letters until they have resigned.
- What if a former employer no longer exists?
- Treat it as an unverifiable record, not a red flag. Companies close, get acquired and lose records routinely. Ask the candidate for documentary evidence — appointment letter, relieving letter, payslips, PF records — and record what you were and were not able to establish.
- Should a small date discrepancy fail a candidate?
- Almost never on its own. Decide materiality thresholds in your policy before you start hiring, so the answer does not depend on who happens to be reviewing the report. A month's variance in dates from five years ago is not the same as an overlapping employment claim.
- Do we need the candidate's consent?
- Take written consent as standard practice, covering what will be checked and with whom. Beyond being fair, consent and data-handling requirements are tightening, and a documented consent step is far easier to produce later than to reconstruct.
Keep going
More hiring guides, templates and recruiter tooling.
Offer letter format
The components a job offer letter usually carries, the difference between an offer letter and an appointment letter, and the omissions that cause offers to be declined or disputed later.
Resume screening guide
A working method for shortlisting at scale: build the scorecard first, run two passes, know which filters are real and which are proxies, and calibrate before you trust anyone's judgement
Interview scorecards
Unstructured interviews measure interviewer confidence, not candidate ability. This is how to define criteria, write questions against them, score independently, and calibrate before anyone argues.
Salary structure
Why the number in the offer letter is not the number in the bank, what each component of CTC actually is, and how to explain the difference before a candidate feels misled.
Notice & joining
The weeks between acceptance and joining are where offers are lost. What notice periods and buyouts actually involve, and how to keep a candidate engaged until day one.
Campus hiring guide
How campus recruitment actually runs in India
Job description templates
Six complete, role-specific JDs you can copy
Software Engineer JD
Stack depth over stack breadth. The JD that attracts engineers who ship and filters out keyword collectors.
Data Analyst JD
The role most often mis-scoped as a data scientist. Fix the scope and the pipeline fixes itself.
JD Screening
Score applications against your own job description
Screen consistently, from the first pass
JD screening applies the same requirement-level criteria to every application, so the consistency you want at verification stage starts at the top of the funnel.