Why a background check takes as long as it takes
Turnaround is set by the slowest source in the package, not by the provider. Which sources are slow, why, and the four things you actually control.
- Checks run in parallel, so a package is as fast as its slowest single component, not the sum of its parts.
- The slow components are the ones where a human at another organisation has to do something.
- The biggest fixable delay sits on the employer's side: an incomplete candidate submission.
- Interim reporting solves more turnaround problems than switching provider does.
The shape of the problem
A verification package is not a queue. The checks go out to their sources at the same time and come back whenever those sources answer. That has one consequence worth internalising: the case closes when the last source answers.
So the arithmetic that matters is not how many checks you ordered. It is which of them is slowest. Adding four fast checks to a package changes almost nothing. Adding one slow one changes everything, because it sets a new floor for the entire case.
This is also why "how long does a background check take" has no useful general answer. It is not a property of background checks. It is a property of the specific package you bought and the specific institutions your candidate's history points at.
What is fast, and why
The quick checks share one feature: the record holder answers a query without a person having to decide anything.
- Identity. Numbers put to issuing authorities. This is the one check GVS states a figure for: it typically closes in about an hour from the point a candidate submits their documents.
- UAN and EPFO. A central record, queried rather than requested.
- Directorship and DIN. The MCA register is public and searchable.
- Global database screening. A compiled database, so it returns at the speed of a query.
If your package is only these, you have a fast case. Most packages are not only these, because most exposures are not covered by them.
What is slow, and why
The slow checks share the opposite feature: somebody at another organisation has to receive a request, decide to act on it, and act on it.
| Check | What it is waiting on | What drives the variation |
|---|---|---|
| Previous employment | A former employer's HR or payroll desk | Disclosure policy, whether it is routed via a paid agency, whether the company still exists |
| Education | A university records or verification office | Whether they answer third parties at all, whether a physical visit is required, whether the request must go to the affiliating university rather than the college |
| Court record | Court records across each relevant jurisdiction | Number of jurisdictions, digitisation coverage, how common the candidate's name is |
| Physical address | An associate travelling to the address | Distance, how precisely the address was described, whether anyone is there |
| Police verification | State police | Entirely state-dependent. This is the widest spread of any check |
| Professional reference | A named individual answering a call | Whether the referee's own employment can be confirmed first, and whether they pick up |
Look at the middle column. Not one of those is something a verification provider can compress by working harder. What a provider can do is reach the right desk the first time, escalate properly when nobody answers, and tell you honestly where a case is stuck. What it cannot do is make a university answer faster.
This is why a quoted turnaround should make you more careful, not less. There are only two ways to beat what the sources allow. One is to accept the documents the candidate supplied instead of going to the record holder. The other is to close an unanswered check as verified. Both produce a fast report. Neither produces a check. The provider evaluation questions include the ones that surface this.
The four things you actually control
Most employers who are unhappy with turnaround are looking at the wrong end of the process. These four sit entirely on your side, and together they usually matter more than the provider does.
1. Order at offer, not at joining
A case that starts when the offer goes out has the whole notice period to run in. A case that starts on the joining date is racing somebody who is already inside your systems, and every day of it is visible to the business.
2. Fix the submission form
This is the biggest single fixable delay and it costs nothing but attention. The form should capture what the checks will actually need: the employer's legal entity and location rather than a brand name, an employee code where the candidate has one, an address with a landmark and a pin code, the awarding university rather than the college, and documents in a legible format. Every field missing from the form is an email later, and every email is at least a day.
3. Scope the package honestly
Every check you added that does not map to a real exposure is a source that can be slow for no benefit. This is the practical payoff of scoping by role: a shorter package is a faster package, and it is only shorter because you removed things you were not going to use.
4. Decide who owns an amber finding, in advance
A flagged finding that sits for a week while nobody wants to own the decision shows up in your turnaround number as verification delay. It is not. Name the owner before the first case.
Interim reporting is the actual answer
The best solution to a turnaround problem is usually not a faster case. It is not needing the whole case to make a decision.
If identity, employment and education are back and clear, and the only thing outstanding is a police verification in a state that takes its time, you already know almost everything you were going to learn. Waiting for the last component before anyone can act treats every check as equally decisive, which they are not.
What that needs in practice is a case view that shows per-check status as it moves rather than a report that appears at the end, and a written internal position on which checks must be clear before joining and which may complete afterwards. The first is a platform question and the second is a policy question, and the policy one is the harder of the two.
What honest reporting of a slow case looks like
The last piece is being told the truth while you wait. A case that is stuck should say what it is stuck on, what has been attempted, and what the realistic options are: escalate again, fall back to EPFO corroboration where an employer will not answer, or accept it as unanswered and record why.
Silence followed by a completed report is the pattern to be suspicious of, because it is the pattern that also fits a check that was quietly closed rather than completed.
Questions we get asked
Why will GVS not quote a turnaround for most checks?
What is the single biggest cause of delay?
Does adding one more check slow the whole case?
Can a report be issued before every check is back?
Why are court record checks slower for some candidates?
Is a faster provider a better provider?
Read next
Sixteen questions to ask, including the ones that expose a quietly closed check.
Read the research Candidate experienceA better submission form is the cheapest turnaround gain available, and candidates prefer it too.
Read the guide The client portalPer-check status as it moves, with the evidence attached as it lands.
See the portalTell us where your cases get stuck
We will say which part is the source, which part is the package, and which part is yours.
Talk to sales