
Day one, 10 am. Your new hire has a laptop, an ID card and a welcome lunch booked. Then HR asks her to scan her degree certificate and three payslips, and she spends her first morning hunting for a printer.
The best onboarding experience with background verification is one the new hire barely notices. Start BGV the day the offer is accepted, not after joining. Send one secure link for consent and documents, run the fast checks first, tell the candidate what is pending and why, and don't read a delay as a red flag. Done this way, most checks finish during the notice period.
We're SpringVerify, and this is how we run background verification for HR teams across India. Your candidate gets one secure link with no app to download, gives consent online and uploads documents in a guided form that takes about five minutes. Basic checks come back in under 60 seconds, 80% of verifications are complete within 48 hours, and you watch every check move on one dashboard instead of chasing emails.
Pick SpringVerify if you want new hires verified before they walk in, so their first morning goes on the work instead of the printer.
Before joining, wherever you can. Start BGV as soon as the candidate accepts the offer and gives consent, so the checks run during the notice period and finish before day one. BGV after joining puts paperwork into a new hire's first week and leaves you handling any problem with someone who is already on payroll.
If you run BGV after joining, you pay twice. The new hire's first task is document submission instead of meeting the team. And if a check comes back with a real problem, you're handling it with an employee who has system access, a manager and a salary, not a candidate who hasn't resigned yet.
Teams often wait because something in their process needs the employee to have joined first. Loina Dhal, Executive Human Resources at Signeasy, hit exactly that wall. "The background verification starts as soon as the offer is accepted, but a UAN number is created only after the candidate joins the firm," she said in SpringVerify's case study. With earlier vendors she had to wait for joining day. With SpringVerify: "My favorite aspect about SpringVerify is how it allows me to skip the UAN and directly initiate candidate verification." This account comes from Signeasy's 2022 case study.
Plan for two exceptions:
Most checks finish well inside a 30-day notice period if you start them at offer acceptance. Identity and court checks take minutes to hours, digital address checks 24 to 48 hours and employment checks 5 to 6 working days. Official education confirmation is the slow one, at 15 to 90 days, because it depends on the university.
Here's the joining-date plan we use, built on the turnarounds published on SpringVerify's service pages:
| Check | SpringVerify's published turnaround | When to start | Done before a 30-day notice period ends? |
|---|---|---|---|
| ID (Aadhaar, PAN) | Within minutes of the candidate's submission | Offer accepted | Yes |
| ID (Driving Licence, Voter ID) | Within 24 hours | Offer accepted | Yes |
| Court record (digitised eCourts) | 1 to 2 hours | Offer accepted | Yes |
| Digital address | Usually 24 to 48 hours | Offer accepted | Yes |
| Physical address (field agent visit) | 3 to 7 business days | Offer accepted | Yes |
| Previous employers | Most checks 5 to 6 working days, depending on the past employer's HR | Offer accepted | Usually |
| Current employer | 5 to 6 working days, once you may contact them | After the candidate resigns | Depends on the notice period |
| Education (instant document screen) | Flags obvious fraud within hours | Offer accepted | Yes |
| Education (official university confirmation) | Typically 15 to 90 days | Offer accepted | Sometimes. Plan for it to run past joining |
Source: SpringVerify's identity, court record, address, employment and education verification pages, November 2026. They are published service figures, and no provider can promise them for every candidate. A past employer that doesn't reply, or a document that has to be uploaded again, adds time.
The table tells you two things. Start everything on the day of acceptance, because the slowest check sets your finish line. And decide now what happens on joining day if a university hasn't replied, so nobody makes that call in a hurry while the new hire waits in reception.
A great BGV experience asks for each document once, through one link, with a clear list of what to keep ready, and the candidate always knows what's pending and who to ask. Anything slower or vaguer starts to feel like suspicion, at the exact moment they're deciding whether they made the right choice.
On SpringVerify, the candidate's side takes four steps, as set out on our identity verification page:
Before tools like this, BGV ran on scanned attachments and inboxes. Prathima Shetty, HR Manager at Pazcare, told us she used to handle 100 to 200 BGV emails a day, which took most of her working hours. Her version now: "The candidate themselves upload the documents, and all I need to do is initiate a background verification." This account comes from Pazcare's 2022 case study.
| The candidate's experience | Manual BGV (email and scans) | SpringVerify |
|---|---|---|
| Getting started | An email listing attachments to send | One secure link, no app |
| Consent | A PDF to print, sign and scan | Online, timestamped and stored with the check |
| Documents | Scanned and emailed, sometimes to two teams | Uploaded once, or fetched through DigiLocker |
| Knowing what's pending | They ask HR, HR asks the vendor | HR sees each check's live status and can answer at once |
| A common name in court records | A raw name hit can look like their case | Matches graded against father's name and address |
That last row matters more than it looks. A name match in India's public court records proves nothing on its own. SpringVerify grades each match against the candidate's father's name and address, so a stranger's case doesn't become your candidate's problem, and an inconclusive match goes through a Police Clearance Certificate process to a definite answer instead of sitting in limbo.
For the wider case on why this stage shapes how candidates see you, read why candidate experience matters in background verification.
At every stage, tell candidates what's happening, whether they need to do anything, and when they'll next hear from you. Most BGV anxiety comes from silence. "Your past employer hasn't replied yet, nothing needed from you" calms a candidate down. Ten days of nothing makes them wonder.
SpringVerify's dashboard shows where each check stands and what is blocking it, so each update takes a couple of minutes. Here's the message plan we suggest:
| Stage | What the candidate needs to hear | Who acts next |
|---|---|---|
| Offer accepted | Which checks apply and why, who SpringVerify is, which documents to keep ready | Candidate gives consent and uploads |
| Documents received | That the upload worked, or exactly which item needs another look | HR, only if something is missing |
| Waiting on a source | Which check is pending, and that they don't need to do anything | SpringVerify follows up with the source |
| Something doesn't match | The specific detail that differs, and a chance to explain | Candidate responds, then HR reviews |
| All checks done | The joining decision and the next onboarding step | HR |
Two short templates cover most cases. Adapt them to your policy.
Invitation: Congratulations again on accepting our offer. As part of joining, we verify a few details through SpringVerify, our background verification partner. Your checks cover [list]. You'll get a secure link from SpringVerify today. It takes about five minutes, and you can fetch some documents straight from DigiLocker. If a document is hard to find, tell [HR name] and we'll work out an alternative. We'll update you by [date].
Waiting on a source: Your [employment] check is waiting for a reply from [company]. There's nothing you need to do. We're following up and will update you by [date].
A delay and a mismatch are different problems. A delay means a document is missing or a source hasn't replied, and it says nothing about the candidate. A mismatch means a source disagrees with what the candidate told you, and it deserves a neutral question before anyone draws a conclusion.
| What happened | What it usually means | What SpringVerify does | What HR does |
|---|---|---|---|
| A document is missing or unreadable | The candidate couldn't find it or the scan failed | Flags the check with a clear reason code | Ask for that one item again, or agree an alternative |
| The past employer's HR doesn't reply | A busy HR desk | Follows up, then escalates to the candidate's reporting manager over WhatsApp | Tell the candidate it's pending and nothing is needed from them |
| The past employer has shut down | Nobody left to answer | Checks PF/EPFO records, MCA archives and other statutory filings | Wait for the result. It isn't the candidate's fault |
| Dates or designation differ | Anything from a typo to an inflated CV | Flags the discrepancy in the report | Show the candidate the exact detail and ask for an explanation |
| A court record match | Possibly a namesake | Grades the match on father's name and address, and sends inconclusive matches to a PCC | Decide only on a graded result, never a raw name hit |
One rule protects both sides: SpringVerify reports what the sources say, and your team decides. In the words of our identity verification page, "SpringVerify does not make hiring decisions - that remains with your team." When a check needs the candidate to act, you choose whether to raise an insufficiency, ask them to re-submit or send it for manual review. Our guide to resolving amber and insufficient BGV cases walks through each route.
If a check turns up a real problem after the employee has joined, your BGV policy and the offer letter decide what happens next, which is why the offer letter should make employment conditional on satisfactory verification. Before acting, show the employee the specific finding and let them explain. A "failed" check is often a wrong date, a namesake or a past employer's error.
This is the strongest argument for finishing BGV before day one. A problem found during the notice period is a conversation with a candidate. The same problem found in month two is an employment decision, with access to revoke and a team to reshuffle. For a specific case, take legal advice.
Collect the candidate's consent before any check starts, use their documents only for verification, and keep them in your BGV platform rather than in email threads and shared drives. In India, the Digital Personal Data Protection Act, 2023 sets these duties, and its core provisions apply from 13 May 2027 under the government's G.S.R. 843(E) notification of 13 November 2025.
You don't need to wait for 2027 to work this way. SpringVerify's flow is consent-first: every candidate completes an explicit digital consent step before any verification starts, and that consent is timestamped and stored with the check. Aadhaar numbers are masked after processing and never stored in raw form, access to reports is role-restricted, and SpringVerify is certified to ISO/IEC 27001:2022 and SOC 2 Type II.
Inside your own team, decide who sees full reports, what the hiring manager needs to know and how long you keep records. For a specific case, take legal advice.
HR teams choose SpringVerify because new hires get verified before joining day without anyone on the team chasing documents. Here are the reasons, with the proof behind each.
Joining dates hold. Basic checks come back in under 60 seconds and 80% of verifications are complete within 48 hours. At Signeasy, Loina Dhal reported that an ID, address and employment check is "mostly complete within seven days", after waiting 15 days to a month for a status update with a previous partner. This account comes from Signeasy's 2022 case study.
Your team stops chasing. "There is nothing manual in background verification; everything happens online and on a system," said Prathima Shetty of Pazcare. When a past employer's HR goes quiet, our employment verification escalates to the candidate's reporting manager over WhatsApp, so one silent inbox doesn't hold up a joining date.
Checks start from the HR tools you already use. SpringVerify connects with 100+ HRIS, ATS and HRMS platforms, including Keka, Darwinbox, Zoho People, Zimyo, greytHR and Workday. Lumel grew from 210 to 350 employees in under two years, and Designated Partner Brinda Jayaraman said: "Our recruitment team is all praises for Keka's Hiring and Onboarding features, and very happy with the SpringVerify integration. They told us their work has reduced by nearly 50%, especially in rolling out offer letters." This account comes from Lumel's 2025 case study.
No surprises in court records. "SpringVerify gave us what we were missing - the ability to actually see court case risks clearly. It has meaningfully reduced our BGV delays and given our HR team the visibility to move faster with confidence," said Ritika Raj, Senior Manager I, HR Shared Services at LoadShare Networks.
An audit trail you can show anyone. Consent is timestamped, employment reports are timestamped and source-cited, and reports export as PDFs ready for a compliance audit.
"We've been using SpringVerify since March 2025 and the experience has been smooth so far. What we appreciate most is how proactive and solution oriented they are," said Govindprasad Goankar, Executive VP and HR Head at Kotak Mahindra Asset Management.
SpringVerify is right for you if you hire in India, want BGV finished before joining day, and want candidates to do their part in one short online session while your team tracks progress on a dashboard. Our customers range from startups like Signeasy and Pazcare to enterprises like Kotak Mahindra Asset Management.
SpringVerify is a good fit if:
SpringVerify is not the right fit if:
The quickest way to judge it is to see your own hardest case. Book a SpringVerify demo and ask us to walk through a candidate with a missing document, a past employer that won't reply and a common name in court records.
Yes. Background verification is the last step of hiring and the first step of onboarding. We recommend starting it when the offer is accepted, so the checks finish during the notice period and the new hire joins already verified.
At some companies it does, but it doesn't need to. BGV after joining adds paperwork to the new hire's first week and means any problem lands on someone already on payroll. With online consent and document upload, you can start at offer acceptance instead.
It depends on the checks. On SpringVerify, ID and court checks take minutes to hours, digital address checks 24 to 48 hours and most employment checks 5 to 6 working days, while official education confirmation typically takes 15 to 90 days.
Usually a government ID (Aadhaar, PAN, Driving Licence, Voter ID or passport), proof of address, degree certificates and marksheets, and employment records such as relieving letters or payslips. Ask only for what the role's checks need, and give the candidate the list up front.
Yes, if your policy allows it, and official education confirmation is the check most likely to still be open. Record which check is pending, who will review it and by when, and don't let "pending" quietly become "passed".
Yes. SpringVerify integrates with 100+ HRIS, ATS and HRMS platforms, including Keka, Darwinbox, greytHR, Zoho People and SAP SuccessFactors, and offers a documented REST API for custom setups. Our identity verification page says most teams are live within one week.
.png)