Say two engineers hired for a client ramp starting on the 1st won't join until the 15th. The tracker gives one reason for both: background verification pending. That is two unbilled seats for two weeks, and the delivery head wants to know why, and whether the next ramp will slip too.
Before you answer, go back over last quarter's hiring in India. Wherever background verification delayed a joining date, how many of the lost days did the vendor spend checking? Its turnaround report tells you. How many days did each case wait for documents before the vendor saw it, or sit on an open flag afterwards? Usually nobody can say. The dates exist, but no report adds them up.
So the vendor takes the blame, and the fix becomes a tougher vendor review or a new vendor. That is right when the vendor's own checking days are the biggest share. Often they aren't. The days on either side of its work belong to no one, so a faster vendor fixes less than you'd expect, and you can win those days back without changing vendors.
Before the vendor starts. A case reaches the vendor only when the last document arrives. If documents are requested in one batch after the candidate resigns, the candidate spends the notice period chasing a relieving letter from a job six years ago.
With the vendor. This is the time vendors compete on and report, and when it runs long it costs real money. In a case study of its own managed BGV service for a global MNC, EY India writes that "high turnaround times and vendor issues in pre-hiring checks delayed chargeable project deployment" (EY India, Oct 2026).
After a flag. When the vendor can't complete a check, it raises a BGV insufficiency: something is missing, or what it found doesn't match what the candidate said. Closing it needs the candidate, sometimes a former employer, and someone on your team chasing both. If that person is never named, the case sits as "insufficiency" while each party assumes another has it.
Take a case where the documents take 24 days to arrive complete, the slowest check takes 20 days at the vendor, and an employment flag then sits open for 23 days. The vendor's report shows a reasonable 20 days. The candidate waited 67, and 47 of those days were outside the vendor's clock. All three clocks have to fit inside the notice period, often 60 to 90 days in IT services, or the joining date moves.
None of this needs a client ramp. A branch role at a bank or a hire into a GCC runs on the same three clocks, and a slip there leaves an empty seat and a hiring manager asking you why.
The split tells you which fix comes first. List every joiner whose start slipped on BGV last quarter and pull each case's dates from three places:
Where a date is missing, check the email that carried it. Failing that, leave the case out rather than guess. Before-vendor days run from offer acceptance to the case going out, and after-flag days from each flag raised to its clearance. The rest, up to the report, is the vendor's. If most days went before the vendor, start with document timing. If most went after a flag, start with ownership.
If the vendor's clock is the biggest, take three things into your next vendor review. First, its median and worst-case closure times by check type over the last two quarters, because one blended turnaround hides the slow checks. Second, how the contract counts time while an insufficiency is open. If that clock pauses, the vendor can meet every service level while your joiner waits. Third, a written limit on how many days the vendor may take to tell you it has found a gap.
A name spelled one way on the PAN card and another on the degree certificate costs a five-minute conversation at offer stage. Found in week seven of a notice period, it costs a joining date. So give your recruiters one rule: by offer acceptance, every document that doesn't come from the current employer is in and checked. Only the current employer's papers, such as the relieving letter, can wait, because the candidate can't get them until they leave.
Two more changes bring dates forward. Have one named person on your team compare names, dates of birth and the dates of each degree and job across the documents and the resume before a case goes out, which clears the cheapest flags. And ask the vendor to start each check as soon as its documents are ready, so education and previous-employment checks run during the notice period.
Why not collect at interview, earlier still? Because PAN or Aadhaar copies from every interviewee are sensitive data about people you will reject, which raises the questions in our post on how the DPDP Act affects talent acquisition in India. At interview, ask only for the name exactly as it appears on the candidate's ID, which surfaces a mismatch without holding anything sensitive.
An insufficiency with a status and no owner is how a joining date slips without anyone deciding it should. Make each flag a task with one named owner, a due date and a next action, and have it escalate to you or a named deputy when the date passes.
Decide the owner by type of flag, in advance. A missing document belongs to the recruiter, who has the relationship with the candidate. A former employer that won't reply belongs to whoever manages the vendor, because the vendor needs another source or an escalation contact. A discrepancy, where the record contradicts what the candidate said, needs someone with the authority to decide it: you, or the HR or risk approver your policy names, never the recruiter alone.
If BGV sits with HR Ops or shared services, agree this list with that team's head. Their named people own vendor and discrepancy flags, your recruiters own missing documents, and one of theirs joins the weekly review you run.
Record each flag's reason from a short fixed list: name mismatch, missing relieving letter, former employer not replying, university pending, candidate not responding. After a quarter, the list shows whether your after-flag days come from document gaps, which earlier collection fixes, or from slow employers, which the vendor has to fix.
A candidate with five checks cleared and one pending has not cleared. As Indian HRM's 2026 guide puts it, "the slowest component sets the overall turnaround" (Indian HRM, Jan 2026). So, the date you give the delivery head or hiring manager should come from the hire's slowest check, not from the offer date plus an average.
One check sits outside that calculation: the current employer. It can't close before the candidate's last working day, when the relieving letter is issued, so unless you leave a gap between that day and joining, it will still be open when the person joins. The joining rule in the next section has to cover it. Among the other checks, you can usually name the slowest at offer stage from the profile.
| Check | Why it can finish last | Most likely to hold up |
|---|---|---|
| Previous employment | The former employer's HR replies slowly, or the company has merged or shut down | Laterals with several past employers |
| Education | A university may verify by hand, and the name on the certificate may not match the ID | Freshers, and anyone with an older degree |
| Address | A physical visit has to be scheduled, and the candidate may be moving for the role | Hires relocating to join |
For each hire with a committed date, note that check and its expected close date: the vendor's worst-case time for it, plus a buffer. If a date slips anyway, you know early which check is open and who owns it, which leaves the delivery head time to wait, start the person on work with no client access (if your policy allows it), or fill the seat from the bench.
The alternative to waiting is to let the person join and finish the checks afterwards. Write that rule yourself and have HR, risk and legal sign it, because you give the business its joining dates. OnGrid, a BGV vendor, wrote in June 2026 that among HR teams handling a pending BGV at joining, "very few have an actual policy written down anywhere" (OnGrid, Jun 2026). That is one vendor's impression, not data. But if your rule today is a call between a recruiter, a hiring manager and a delivery lead two days before joining, you don't have one.
Waiting has a cost. Indian HRM's guide notes that pre-joining BGV "gives a clean start but can delay joining and lose the candidate to other offers" (Indian HRM, Jan 2026), the same risk of candidate withdrawal before joining you already track through the notice period. Joining first has a cost too: if a check fails later, you are handling an exit after the person has had access to client systems or customer data. So set the rule by role, starting from what your client contracts and regulators require:
Once a week, take every joiner due in the next 30 days, sorted by slowest open check and with each open flag's owner, to a short review with the delivery or hiring managers whose dates depend on them. Dates get confirmed or moved there. Three numbers show whether the changes are working, and the first two usually move before the third.
| Number | How it is calculated | What it tells you |
|---|---|---|
| Accepted first time | Share of cases the vendor accepts without raising a flag for a missing or mismatched document | Whether documents arrive early and checked |
| Flag to closure | Median days from a flag being raised to its closure, split by reason | Whether flags have owners, and which reasons need a different fix |
| Cleared before joining | Share of joiners whose BGV cleared on or before their joining date | Whether the dates you commit are holding |
For a reference point, EY India's case study of its managed service reports that for the global MNC, "84% of the cases were cleared within 30 days" (EY India, Oct 2026), and "47% of employee verification was completed even before the employee joined, and another 42% were completed within 20 days from the date of joining" (EY India, Oct 2026). That is a provider describing one client's result, not a benchmark.
The weekly review is what changes the next call. When a start slips, you already know which check is open and who owns it, and you ring the delivery head before they ring you.
At low volume, a spreadsheet and WhatsApp reminders can run all of this. It breaks as volume grows, because document status, BGV status and the joining date sit in three places, and flags arrive as emails nobody is assigned to. In RippleHire:
Explore RippleHire Onboarding →
If your vendor's turnaround report looks healthy but joining dates still slip, the missing days usually sit on either side of the vendor. Book a RippleHire demo and we will walk through how document kits, staged collection and flag follow-up tasks with named owners would fit your offer-to-joining window.
For fresher hiring, GetWork wrote in May 2026 that third-party BGV checks add another 2 to 6 weeks after an offer letter is issued (GetWork, May 2026). IDfy, a BGV vendor, reported in February 2026 that the typical median turnaround for BGV companies in India is 21 days for standard checks (IDfy, Feb 2026). Use it to question a vendor's claims, and plan joining dates from your own slowest checks.
That depends on your written rule, if you have one. Either the joining date moves, or the person joins on a conditional offer that lists each open check with a deadline. Either way, tell the candidate which check is open and what happens next as soon as you know, not on the morning of joining, because a candidate left waiting is still open to other offers.
Yes, every check except the current employer's can start at offer acceptance. Candidates who hesitate are usually worried that their employer will hear. Tell them which checks start when, and confirm in writing that the current employer won't be contacted until the agreed point. Record the candidate's consent for each check before it starts, so you can show later what they agreed to and when.
An insufficiency is any gap that stops the vendor finishing a check. A discrepancy is the kind where the record contradicts what the candidate stated, such as different employment dates or a designation that doesn't match. Many discrepancies have ordinary explanations, like a name changed after marriage or an employer renamed after a merger. Give the candidate a fixed window to explain with evidence before anyone rules on it. Then record the decision and the reason, so the next similar case gets the same answer.
It depends on the checks you order. An identity check uses photo ID such as a PAN card, Aadhaar or a passport. An education check needs the certificate for each degree. An employment check needs proof from each past employer, such as payslips, the offer letter and the relieving letter, and an address check needs proof of the current address. Ask for nothing a check doesn't use, because every extra item is one more thing a candidate has to find during the notice period.