A tiered background verification process gives each role a package of checks that matches its risk, and starts each check at a set hiring stage. A practical model has three tiers: a baseline tier for most hires, an enhanced tier for roles that touch money, personal data or production systems, and a specialist tier for directors, signatories and regulated roles. With SpringVerify, each tier becomes a package built from its 20+ checks, triggered from your ATS or HRMS and tracked in one dashboard.
This guide gives you the tier table, a five-question test for placing roles, a stage plan, SpringVerify's published turnaround for each check, and the DPDP points your candidate notice should cover.
Tiered background verification means grouping checks into packages by the risk a role carries, so each hire gets the checks their job needs and no more. A staged process then sets when each check starts as the candidate moves from interview to joining. Risk-based screening is another name for the same idea: the depth of checks follows the role's access and authority.
Guides use "tier" for two different things. Some sort checks by role risk; others sort them by hiring stage (preliminary screening, shortlist, finalist, post-joining monitoring). You need both answers, so treat them as separate decisions:
| Decision | The question it answers | Example |
|---|---|---|
| Role tier | Which checks does this role need? | A payroll executive gets full employment history because they handle salary data. |
| Hiring stage | When does each check start? | The package starts at offer acceptance; the current employer is contacted only after the candidate resigns or agrees. |
| Joining condition | What must be clear before day one, or before access? | Payment-approval access waits until the employment and court record checks are clear. |
No Indian law sets standard BGV tiers. "Tier 1", "Tier 2" and "Tier 3" are your own policy labels, and the model below is a template to adapt to your roles. If your search showed "Tier 1 to Tier 5 investigations", those are US federal vetting levels for government jobs and security clearances; they do not apply to private employers in India.
Tier 1 confirms who the person is, where they live and the one claim their job depends on most. Tier 2 adds the full history for roles with money, data or system access. Tier 3 adds governance and financial checks for directors, signatories and regulated roles. Each tier keeps the lower tier's checks that still apply.
| Tier | Typical roles | SpringVerify checks to include | Scope to write down |
|---|---|---|---|
| Tier 1: Baseline | Most roles with no payment authority and limited data access | ID verification, digital address verification, court record check, and the latest employer (experienced hires) or the highest qualification (freshers) | Accepted ID documents (Aadhaar, PAN, passport), which address, court search coverage, which employer or degree |
| Tier 2: Enhanced | Roles handling payments, payroll or customer data; production or admin access; safety-critical work | Tier 1, plus employment verification for every employer you name, education verification, reference check and gap check; physical address verification, or digital plus physical, for high-risk roles | Lookback period and employers, the qualification the job needs, reference questions, checks that must be clear before access |
| Tier 3: Specialist | Directors, authorised signatories, senior finance, roles under regulator or client due-diligence rules (for example in BFSI) | The Tier 2 checks the role needs, plus directorship check, DIN verification, economic default check, global database verification and, where justified, credit check | The responsibility or rule behind each added check, and who reviews the findings |
Some checks depend on the job itself, whatever the tier. Order a drug test, pre-employment medical test, police clearance certificate or social media verification when the work or a client contract calls for it. A court record check and a police clearance certificate are different records, so do not swap one for the other when a contract names one.
The employment check is where tiers differ most. SpringVerify's employment verification asks you to specify which employers to verify. It confirms tenure and designation with each one, asks about exit formalities and rehire eligibility, and uses direct HR contact, PF/EPFO records, MCA/ROC company data and TAN data as sources. For Tier 1 you name the latest employer; for Tier 2, every employer in your lookback period.
Freshers need no past-employment check; verify the qualification the role needs and any internship your policy includes. For experienced hires, a gap check finds breaks between jobs and records the candidate's reasons. Treat a gap as a question for the candidate; on its own it proves nothing.
Yes. Two of SpringVerify's checks come with a lighter default method and a deeper one, so you can tier inside a check as well as across the package.
| Check | Default for most roles | Deeper option for Tier 2 and 3 |
|---|---|---|
| Address | Digital address verification | Physical visit, or digital plus physical |
| Education | First-pass screen of the certificate | Official confirmation through the institution |
| Employment | Latest employer | Every employer in the lookback, plus a gap check |
Place each role by what the person can touch and approve; title and salary do not decide it. Five questions settle most roles. Agree the answers with the hiring manager and with whoever owns the money, data or systems involved.
A simple rule: a yes to any of questions 1 to 4 puts the role in Tier 2, and a yes to question 5 puts it in Tier 3. Then drop any added check that does not relate to the yes.
Here is how that plays out at a mid-size Indian fintech. The table is an illustration to adapt.
| Role | What the role can touch | Tier | Checks that make the difference |
|---|---|---|---|
| Customer support associate | Limited customer records, no refunds | Tier 1 | ID, digital address, court record, latest employer |
| Senior sales manager | Client relationships, no payment authority | Tier 1 | Same as above: seniority alone does not move a role up |
| Payroll executive | Salary data and payout files | Tier 2 | Every employer in the lookback, education, references |
| Backend engineer with production access | Live systems and customer data | Tier 2 | Every employer in the lookback, education, gap check |
| Finance controller and signatory | Approves payments, signs for the company | Tier 3 | Credit check, economic default check, global database |
| Board director | Governance and statutory duties | Tier 3 | DIN verification, directorship check |
Re-check the tier when someone's job changes. A move into payment approval calls for the Tier 2 checks the new access needs; there is no need to rerun the whole package.
Start each check when you have a reason, the candidate's consent and enough time before joining. In practice that means little or nothing before interviews, the tier's package at conditional offer or offer acceptance, and later checks only on set triggers. A conditional offer is an offer that states employment depends on a satisfactory background check.
| Hiring stage | What to run | What to record |
|---|---|---|
| Application and interviews | Nothing by default; at most an identity check for remote interviews | Why any check before an offer is needed |
| Final round or conditional offer | Explain the tier's checks, take consent, start the package | Which employers may be contacted, and when |
| Offer acceptance to joining | Chase source-dependent checks and missing documents | What must be clear before day one; who approves exceptions |
| After joining or a role change | Close pending checks; re-check on set triggers | Owner, review date, any access held back |
Request the slow, source-dependent checks (official education verification, older employers) as soon as consent is in. A full document set from every applicant before interviews is data you do not need.
Do not let one document block the start. Signeasy's HR executive told SpringVerify that their previous vendor needed the candidate's UAN before it would begin, so checks waited until the candidate joined. On SpringVerify, they start verification as soon as the offer is accepted.
Agree when the current employer can be contacted. A candidate who has not resigned should know if and when their employer will hear from you, and that limit belongs in the case so an automatic trigger cannot override it.
If you hire through an ATS or HRMS, map each package to a stage. SpringVerify's Darwinbox integration guide has you define which checks trigger at which stages, and in ZingHR, HR selects the BGV package from the candidate's profile and SpringVerify sends the candidate the form. Confirm which triggers your own system supports before you rely on them.
After joining, re-verify when something changes: a promotion into payment approval, a licence renewal the job depends on, or an address change for a role that needs a verified address.
A tier takes as long as its slowest check, so the checks you include set the timeline more than the tier label does. A Tier 1 package of instant checks, digital address and the latest employer is planned around the employment check's 5 to 6 working days. Adding official university verification can stretch a Tier 2 package to between 15 and 90 days.
SpringVerify's published figures, read on its service pages on 27 October 2026:
| Check | SpringVerify's published turnaround | What sets the pace | Usual tier |
|---|---|---|---|
| Basic-level checks | Under 60 seconds (homepage) | Instant database lookups | All tiers |
| Digital address verification | Usually 24 to 48 hours | The candidate completing the link | Tier 1 |
| Employment verification | Most checks: 5 to 6 working days | How fast the past employer's HR replies | Tier 1 (latest employer), Tier 2 (all) |
| Physical address verification | 3 to 7 business days | Location, candidate availability, documents | Tier 2, high-risk roles |
| Official education verification | Typically 15 to 90 days | The institution's responsiveness | Tier 2 and 3, where the degree is essential |
Across all its checks, SpringVerify's homepage reports 80% of verifications completed within 48 hours; the slow tail is the source-dependent checks above. They are expectations for each check, and a package finishes when its slowest check does.
When a past employer's HR goes quiet, SpringVerify escalates to the candidate's reporting manager over WhatsApp. For companies that have shut down, it relies on PF/EPFO records and MCA data.
If the joining date is fixed, compare it with the tier's slowest check on the day you make the offer. If official education confirmation cannot land in time, decide then whether a clean first-pass screen plus a pending registrar check is enough to join, and record who approved it.
Each tier collects different personal data, so each needs a clear notice, a stated purpose and data limited to that purpose. India's Digital Personal Data Protection Act, 2023 is commencing in phases, and the duties that matter most for background checks are scheduled to apply from May 2027.
Under the G.S.R. 843(E) notification of 13 November 2025, the Data Protection Board provisions applied from publication, the consent manager provision (section 6(9)) applies one year later, and sections 3 to 17 (apart from section 6(9)) apply 18 months after publication. Those sections hold the notice, consent, legitimate-use and data fiduciary duties.
What the DPDP Act requires once those sections apply, and how each point maps to tiers:
| Provision | What it requires | What it means for tiers |
|---|---|---|
| Section 5(1) | A notice stating the personal data, the purpose, and how to exercise rights and complain to the Board | The notice lists the checks in the candidate's tier |
| Section 6(1) | Consent that is free, specific, informed, unconditional and unambiguous, limited to the data needed for the purpose | Tier 3 data from a Tier 1 hire is hard to justify |
| Section 6(4) | Consent can be withdrawn as easily as it was given | Give candidates a contact for questions and withdrawal |
| Section 7(i) | Lists employment-related processing among "certain legitimate uses" | Consent is not the Act's only ground; your legal team decides which applies |
| Section 8(1) | The data fiduciary stays responsible for compliance, including processing a data processor does on its behalf | If your BGV provider processes data for you, the duty stays with you |
| Section 8(3) | Data used for a decision about the person must be complete, accurate and consistent | Confirm a court record match before it counts |
| Section 8(7) | Erase data once consent is withdrawn or the purpose is served, unless a law requires retention | Set a retention period per tier with your provider |
If a candidate moves to a higher tier, review what they agreed to before you add checks. For a specific case, take legal advice.
On the provider side, SpringVerify's security page says candidate data is collected with explicit consent and used only for the stated verification purpose, and lists ISO/IEC 27001:2022 and SOC 2 Type II. Candidates give consent and upload documents online, and SpringVerify says Aadhaar numbers are masked after processing and never stored in raw form. For identity checks, UIDAI describes Aadhaar Paperless Offline e-KYC as a voluntary way for the holder to share digitally signed data, so confirm which identity method your package uses.
Treat pending, insufficient and discrepant results as three different states, and let the candidate explain before you decide. Only a confirmed discrepancy that matters to the role should change a hiring decision.
| State | What it means | What HR does |
|---|---|---|
| Pending | The source has not replied yet | Keep the tier's joining rule; do not treat silence as a failure |
| Insufficiency | The check cannot proceed because a document or detail is missing | Ask the candidate for the missing item |
| Discrepancy | The source contradicts what the candidate declared | Share the exact issue, ask for an explanation, judge relevance to the role |
A red flag is a confirmed discrepancy that matters to the job: different employment dates or designation, a forged certificate or one the institution does not recognise, or a court case that matches the candidate's identity details. A name match alone is a lead to check. Confirm identity, the case type, the person's role in it and its status, because a civil dispute, a pending criminal case and a conviction are different findings.
SpringVerify's employment reports show green for clear and flag discrepancies, and each verification is timestamped and source-cited, so you can show the candidate exactly what the source said. Pazcare's HR manager told SpringVerify the report shows document copies, email conversations and verification summaries. LoadShare Networks' HR shared services manager says SpringVerify gave them "the ability to actually see court case risks clearly."
Whether someone can join with checks still pending is a per-tier rule you set in advance. A Tier 1 hire might join while an old employer has yet to reply; for Tier 2 and 3, hold back the sensitive access until the checks tied to it are clear. Record the pending items, the approver and the review date.
Start with one page of policy, then turn each tier into a package. Most of the work is deciding the tiers; the setup follows from them.
Different groups can run different check sets. Zinnov helps global companies set up India centres and runs their hiring; its clients that use SpringVerify each run the checks their own compliance requires, and Zinnov's project lead uses the dashboard filters to check status quickly.
SpringVerify fits when you hire into several kinds of roles in India and want each tier set up once and run from the tools you already use. It is a weaker fit when your hiring is small and uniform, or when you need something its published figures do not promise.
A good fit if:
Probably not a fit, or tiering will not help, if:
There is no fixed number in India. This guide uses three role-based tiers (baseline, enhanced, specialist). Guides that list four usually add post-joining monitoring as a fourth level, which works better as re-checks on set triggers.
In an Indian employer's policy, Tier 1 is the baseline package for roles without special access. In the model above it covers ID verification, address verification, a court record check and the latest employer or highest qualification. In the US, "Tier 1" is the federal government's investigation level for non-sensitive positions.
No. Use what the role can access and approve. A senior sales manager with no payment authority can sit in Tier 1, while a junior payroll executive needs Tier 2 because of the salary data they handle.
No. SpringVerify's digital address verification usually completes in 24 to 48 hours, so in a package with employment or education checks it is rarely the last item. The last open check is usually a past employer's reply or a university's confirmation.
Yes, if your tier's joining rule allows it. Record the pending checks, who approved the start, the review date and any access held back until the checks clear.
Review what the candidate already agreed to. If the new checks add data or a purpose outside that notice, update the notice and take consent for the added checks. For a specific case, take legal advice.
It can, by not running checks a role does not need and by starting full packages only for candidates who reach the offer stage. Measure it against your own check volumes; no fixed saving applies to every employer.
Take one role family, run it through the five questions and write down its tier, checks and joining rule. Then book a demo of SpringVerify's employee background verification and ask to see that package triggered from your ATS or HRMS, with the dashboard view your team would use.
.png)
