What to Check Before Background Verification in India

Before a candidate goes to background verification in India, check four things: that you hold specific written consent, that the checks match the role, that the application agrees with itself on dates, names and employers, and that a person has looked at every inconsistency. Most avoidable delay starts there.

Those four checks take about ten minutes per candidate and sit before the referral, which is the only point at which a fix is cheap. The rest of this page says what each one involves, which numbers justify the effort, and where it stops being your job and becomes the verifier's.

You need consent that is free, specific, informed and given by a clear affirmative act, and you need it before the referral, not folded into an offer letter. The employer stays accountable for the candidate's data even when a vendor runs the checks. This is general information, not legal advice.

ThePeoplesBoard's July 2026 guide to BGV and the DPDP Act summarises the standard as consent that is free, specific, informed and affirmative, with the right to withdraw explained in the notice. It says the DPDP Rules were notified in November 2025, with full compliance expected by mid-May 2027, and that the employer remains accountable when the check is outsourced. Its separate list of common BGV mistakes (June 2026) adds that a one-line clause in an older offer letter is unlikely to meet that standard.

In practice, a pre-referral consent record names each check (employment, education, identity, address, and criminal record where the role justifies it), says why, names the vendor, says how long the data is kept, and says how to withdraw. Our post on what the DPDP Act means for AI screening in India covers the screening side of the same obligation.

Do the checks match the role?

Scope the checks to the role tier and write that scope down. Verifying a few high-impact data points before the offer and running the deeper, slower checks after it is the pattern most Indian BGV providers describe, and over-checking adds cost and privacy exposure without adding signal.

OnGrid's comparison of pre-offer and post-offer BGV (May 2026) describes pre-offer checks as early risk filtering on identity, criminal record, basic employment history and moonlighting, and post-offer checks as final compliance validation covering education, detailed employment, financial checks, police verification and drug testing. It recommends a hybrid and warns against running full checks on every applicant. Treat that as one vendor's view, but it matches the other guides.

A usable rule: write one line per role tier that says which checks run before the offer, which run after, and which never run. Then apply it the same way to every recruiter and every candidate, because inconsistent depth is both a fairness problem and a compliance one.

Does the application agree with itself?

Before referral, read the application against itself. Date overlaps, impossible timelines, name mismatches and employers that cannot be found are all visible without any outside record, and each one is a place a verifier will lose days or return an adverse finding you could have asked about first.

This is the part the current answers skip. The pages that rank for this question list consent, scope and vendor choice, and stop there. None gives a way to inspect the file you are about to send. That matters because the vendor's turnaround depends heavily on the quality of what you hand over: OnGrid's guide to BGV turnaround time names incomplete or incorrect candidate data and outdated employer contacts among its main causes of delay. Here is the ten-minute worksheet we would use.

Dates: overlaps, gaps and impossible sequences

List every role and degree with start and end months. Flag any two jobs that overlap by more than a notice period, any job that begins before the degree it is attributed to could have finished, and any gap longer than a few months with no explanation. An overlap is not proof of fraud. It can be a consultancy, a delayed relieving letter or a typo, and the right action is a question to the candidate, not a rejection. Overlap is also the signature of the moonlighting that vendors now check for, which is why our post on the overemployment blind spot in hiring is worth a read for senior roles.

Names: ID, degree and employer must reconcile

Compare the name and date of birth on the application with the identity documents the candidate will submit. The ThePeoplesBoard guide lists name or date-of-birth mismatches as the main delay driver for identity checks. Do the same for employers: a brand name such as a product or group company is not always the legal entity that issued the payslip, and a verifier will search for the legal name. Ask for it up front.

Contacts: a verifier needs a person who will answer

For each employer, ask for a current HR or manager contact, not just a company name. An old HR email that bounces sends the vendor hunting for another route, and employment checks are the slowest part of the process because they depend on someone else replying.

Add the location of the address, too. The same guide gives address checks 3 to 5 days, and names rural or Tier-3 locations as the usual cause of slippage.

What do the numbers say about why this is worth ten minutes?

Discrepancies are common enough to plan for and slow enough to hurt. AuthBridge's H1 FY26 Workforce Fraud Files reported a 4.33% discrepancy rate for white-collar hires and 5.61% for on-demand workers, with employment verification the most affected check for white-collar roles.

Two cautions apply. AuthBridge is a verification vendor, and the report as published does not state its sample size or how it defined a discrepancy, so treat the figures as indicative of the order of magnitude, not as a benchmark for your pool. And a discrepancy in a vendor's data covers everything from a minor date error to a fabricated employer. Read the rate as the share of files needing a human look.

Speed is the other half. ThePeoplesBoard puts typical turnaround at 7 to 15 business days overall, with employment checks at 3 to 7 days per employer and criminal record checks at 7 to 14 days, and recommends a buffer of three to four weeks in the hiring timeline (as of July 2026). If a mismatch forces a restart, you pay those days again. In a market where offers are held for a notice period, that is the time a candidate has to accept something else.

Who reads the flags before the referral goes out?

A person should, every time. A flag means "ask", never "reject". The ThePeoplesBoard mistakes guide makes the same point about clearing amber findings without investigation, such as a title that does not fit the salary claimed or a degree dated before the course existed.

A simple routine works for small teams. One recruiter fills the worksheet, writes a one-line note per flag, and the hiring manager sees the notes next to the shortlist. If the candidate explains it, the note says how. If not, the question goes to the vendor as a specific check, not a general one. Our post on why only 16% of HR teams trust AI screening alone is the evidence for keeping the person in the loop.

What does AgentR do here, and where does it stop?

AgentR reads every application in full and checks what the candidate claims against the public record, then gives your team a ranked shortlist with the evidence attached. Our pre-BGV filter page describes the part relevant here: inconsistencies in dates, titles and employers are surfaced for a human to review before a candidate is sent for formal verification. The wider approach is on our resume verification page.

It has clear limits. AgentR does not replace a BGV vendor: it cannot see an employer's HR records, court records, police clearance or any other source that needs the candidate's consent and a formal request. It does not decide anything, and nobody is auto-rejected. AgentR is in private beta, so we have no published data on how much a pre-referral check shortens BGV turnaround or lowers the discrepancy rate, and nothing here should be read as a claim about that.

Questions people ask

Should background verification happen before or after the offer?

Most guides recommend both, in stages: light, high-impact checks before the offer and the heavier, slower ones after acceptance. Where the offer is conditional on BGV, say so in writing at the offer stage. Regulated and high-trust roles, such as banking and healthcare, often need more before the offer.

Can I run a check before the candidate has consented?

You should not. Under the DPDP framework consent has to be specific and informed, and it is the employer's responsibility to obtain it even if a vendor does the work. Get a written, check-by-check consent before the referral and keep a record of it.

How long should I budget for BGV in India?

One guide puts the overall range at 7 to 15 business days and suggests a three to four week buffer (ThePeoplesBoard, July 2026). Employment checks usually set the pace, because each previous employer has to respond.

What do I do if the application has an overlap or a gap?

Ask the candidate for an explanation and a supporting document, note the answer, and send the vendor a specific check. Do not reject on the pattern alone, because an overlap has many ordinary explanations.

Does a pre-referral check replace the vendor?

No. It makes the file cleaner and catches self-contradictions. Only the vendor can verify claims against employer, institution and court sources.

Before your next referral, pull the application and write the start and end month of every job and degree on one line each. If two lines overlap, or a name differs from the ID, ask before you send. It takes ten minutes, and it is cheaper than a restart.

Do you have consent that would hold up under India's DPDP Rules?