Companies in India do background verification by obtaining candidate consent, collecting relevant details, and checking them against sources such as former employers, universities and court records. HR can run the checks internally or use a specialist provider. The provider reports what it verified; the employer decides what the findings mean for the hire.
A useful background verification (BGV) programme answers three questions: what needs checking for this role, which source can confirm it, and who will resolve any mismatch?
HR owns the screening policy and hiring decision. An external background verification company can handle document collection, source checks, follow-ups and reporting. Employers can also split the work, keeping reference conversations in-house while outsourcing checks that need specialist access or coordination.
| Responsibility | Employer's role | Verification provider's role |
|---|---|---|
| Select the checks | Define the package, employment lookback and job-related requirements | Explain available methods, coverage and limitations |
| Inform the candidate | Explain the purpose and approve the notice and consent process | Collect consent and documents through the agreed workflow |
| Verify the information | Supply accurate candidate details and resolve internal questions | Contact sources, check records and document results |
| Resolve discrepancies | Give the candidate an opportunity to respond and apply company policy | Recheck evidence and correct or clarify the report |
| Make the decision | Decide whether to proceed, pause or take another action | Provide findings, not the employer's final hiring judgement |
| Protect the records | Set access, retention and deletion requirements | Apply the agreed controls to data it processes |
In-house checks can work when your team has the time and source access. Outsourcing helps when HR is chasing several former employers, institutions and candidates at once. Either way, ask to see the evidence behind each result, not only a green or red status.
Companies start by defining the checks, then collect consent and information, verify with the relevant sources, and review a report. Set the decision rules before the first candidate enters the process.
List the facts you need to establish. For a graduate role, academic qualifications may matter more than employment history. For an experienced hire, specify which previous employers and qualifications to verify. Add checks such as credit, professional registration or drug screening only where the role and applicable requirements justify them.
Avoid ordering every available check for every hire. Agree which results must be complete before joining and who can approve an exception if a source is still responding.
Tell the candidate what you will check, why, who will handle their information and how to raise a question. Record their consent before starting the agreed screening workflow.
Ask separately about contacting a current employer. An early verification request can reveal a job search before the candidate has resigned. Record an agreed contact date or use suitable supporting evidence while that check waits.
Request a defined document set through a controlled upload process. Typical inputs include:
Check names, dates and document readability before submitting requests. A maiden name or a different legal employer name should be explained early, rather than discovered after several unsuccessful searches.
Run independent checks in parallel once their inputs are ready. Employment verification needs employer or supporting employment records; education verification needs the institution or an issuer-backed academic record. One cannot substitute for the other.
Track pending checks by cause: candidate input needed, source response awaited, or a finding under review. That tells HR whom to follow up with.
Read the candidate's claim, the source's response and the verifier's conclusion together. Ask for clarification where a result lacks evidence or where the source could confirm only part of the claim.
Document the decision, its reason and the approver. If a required check remains open at joining, give it an owner and a follow-up date. Restrict report access and apply the agreed retention schedule rather than leaving copies in shared folders indefinitely.
Companies check specific claims about a candidate, using a different method for each. The strength of a result depends on the source, the match to the candidate and the limits of that source.
| Check | How companies verify it | What the result does not establish by itself |
|---|---|---|
| Identity | Validate an accepted document through a permitted method and compare its details with the candidate's information | Employment history, qualifications or current residence |
| Employment | Contact previous employers and review supporting records, including EPFO-linked evidence where applicable | Every job the person has ever held |
| Education | Obtain confirmation from the awarding institution or verify an institution-issued digital award | Authenticity based only on a certificate's appearance |
| Address | Use the agreed digital process or a physical visit, supported by relevant documents | Permanent residence from a single location capture |
| Court records | Search relevant court records and review matching cases | Guilt from a name match or a pending case |
| References | Speak to an appropriate former manager or colleague about work-related questions | Independent confirmation of every factual claim on the CV |
Companies contact an independently validated HR or employer contact to confirm employment dates, designation and other agreed details. Relieving letters, experience letters and payslips provide supporting evidence, but uploading a letter does not make its contents independently verified.
EPFO records linked to a Universal Account Number (UAN) can support employment checks where relevant records exist. They do not replace employer confirmation of job title, duties or performance. Do not assume that an employment record missing from EPFO proves the job did not exist.
Likewise, overlapping contribution periods need explanation before HR draws a conclusion about simultaneous employment. Compare the dates with employer responses and the candidate's documents. Keep account passwords out of your collection process; candidates should complete authentication themselves through the authorised workflow.
SpringVerify's employment verification service describes using direct HR contact alongside PF/EPFO records and company-registration sources. Company registration helps establish that an organisation exists; it does not, by itself, prove that a particular candidate worked there.
Companies ask the awarding institution to confirm the qualification or use an institution-issued digital record where available. The check should match the candidate's identity, qualification, institution and relevant year.
The government's DigiLocker National Academic Depository FAQs explain that institutions publish academic awards and verifying partners can view records with the holder's permission. This is different from a candidate uploading a scan. If an award is not available on NAD, request confirmation from the institution rather than treating its absence as an adverse finding.
An Aadhaar-based identity check validates identity information through a permitted method. An address check asks whether the candidate's stated residence can be verified. An address printed on an identity document may not be their current address.
UIDAI's paperless offline e-KYC guidance describes a voluntary, consent-based process using digitally signed XML. It also makes clear that online Aadhaar e-KYC is not available to every agency. Employers should ask which method their vendor uses, rather than assume that a BGV platform has unrestricted access to Aadhaar data.
For residence checks, agree whether digital verification is sufficient or whether a field visit is needed. A candidate away from home may need another appointment, not an adverse result.
Companies or their providers search relevant court records and assess potential matches against the candidate's identifying details. They then review the person's role in the case, the case status and available orders.
The official eCourts case-status service allows searches by party name. Its guidance says a party can be a petitioner, complainant, respondent, defendant, accused or another party. A search hit therefore does not establish that the candidate committed an offence.
Ask the verifier to state the courts searched, the match evidence and the case outcome where available. A pending case is not a conviction, and “disposed” alone does not explain the outcome. Police verification and court-record searches are different services; specify which one your policy requires.
Use a documented, consent-based workflow with a clear purpose, limited data collection and controlled access. Check the applicable law and source-specific requirements for each method rather than treating a signed form as permission to collect anything.
The DPDP rollout is phased. As of October 2026, the core processing provisions of the Digital Personal Data Protection Act, 2023 have not all commenced. MeitY's commencement notification, G.S.R. 843(E), dated 13 November 2025, schedules sections 3 to 5, most of section 6, and sections 7 to 17 to commence eighteen months after Gazette publication.
The DPDP Act sets out notice, consent, accuracy, security and erasure duties. Section 7(i) also provides an employment-related legitimate-use ground. It would be inaccurate to describe consent as the Act's only possible basis for every employment-related activity, or to present all these duties as already in force. For a specific case, take legal advice.
For your BGV programme:
The time depends on the checks ordered and how quickly candidates, employers and institutions respond. A completed identity check does not mean the full BGV package is complete.
SpringVerify publishes the following figures on its service pages. These are service-specific estimates, not universal Indian averages or guarantees for every candidate.
| Check | SpringVerify's published timing | Planning consideration |
|---|---|---|
| Employment verification | Most checks: 5 to 6 working days | Depends on HR responsiveness |
| Digital address verification | Usually 24 to 48 hours | Candidate participation and usable evidence matter |
| Physical address verification | 3 to 7 business days | Location, availability and document completeness affect completion |
| Official education verification | Typically 15 to 90 days | Institution responsiveness can determine the timeline |
Agree when the turnaround clock starts, which delays pause it and what counts as completion. Ask for separate dates for checks that depend on outside responses. A quick document screen should not be reported as final university confirmation.
HR should establish what differs, check the source and invite the candidate to explain before deciding what action is appropriate. Missing evidence and contradictory evidence need different responses.
| Finding | Next action |
|---|---|
| Previous employer has not replied | Ask for follow-up history and assess alternative evidence; keep the result unresolved |
| Employment dates differ | Compare joining, payroll and last-working-day records; request an explanation |
| Candidate's name matches a court record | Confirm identity and party role before treating it as the candidate's case |
| University cannot locate the record | Recheck registration number, name and year, then seek the institution's clarification |
| Issuer confirms a document is not authentic | Obtain the supporting response, allow the candidate to respond and escalate under company policy |
For example, suppose a candidate lists their last month as June but a former employer reports May. Ask whether one date refers to the last working day and the other to a payroll or exit-processing date. That is an illustrative review question, not proof that either account is correct.
Record the finding and the decision separately. A provider's discrepancy flag should prompt a review, not an automatic rejection.
SpringVerify brings candidate consent, document collection, checks and status tracking into one platform. Its website lists 20+ background checks, 100+ HRIS, ATS and HR platform integrations, and an API.
That gives your team a way to coordinate the work described above without tracking every request in a separate email thread. SpringVerify combines automated checks with human expertise, while your company keeps control of check selection and hiring decisions.
For a useful demo, bring one real hiring package: the role, employers or qualifications to verify, expected monthly volume and joining-date requirements. Ask the team to show how a missing document, an unresponsive employer and a disputed finding move through the platform. Review a redacted sample report before agreeing the package.
No. The package depends on the role, company policy and applicable requirements. Define a consistent package for comparable roles, with a documented reason for additional checks.
They can complete other checks and review suitable supporting documents while current-employer contact is deferred. Record what remains unverified and agree when contact can take place. Do not describe supporting documents as direct employer confirmation.
Do not assume so. UAN-linked records support checks of EPFO-covered employment; they are not a complete record of every kind of work. Confirm the employment history your package requires through appropriate sources.
Record that direct employer confirmation is unavailable. Assess alternative evidence, such as relevant employment documents and a validated former manager's response, under your policy. State the limitation in the report.
A company can design its process to begin before joining, with some checks continuing afterwards when needed. Make the offer conditions clear and assign responsibility for unresolved checks. A pending check should remain visible until it is closed.
No. “Unable to verify” means sufficient evidence was not obtained. A confirmed discrepancy means the evidence conflicts with the claim. HR should not treat those as the same result.
Ask for a quote against a defined package. Specify the checks, number of employers or qualifications, locations and hiring volume, and ask about institution fees or rechecks. SpringVerify does not publish a standard price list.
Define the checks one role needs, then test whether your current process can produce clear evidence for each. Book a SpringVerify demo with that package to review the workflow, sample reports and check-specific timelines before your next hiring round.
.png)
