
Your biggest client's vendor questionnaire has one line you can't answer: "Attach your background verification policy." You check every new hire. You have done it for years. But there's no document, no owner and no sign-off, and the client wants all three.
A background verification (BGV) policy is a short, approved document that says who gets checked, which checks each role needs, when they run, how candidates consent, what happens when a check finds a problem or stalls, and how long you keep the records. To build one from scratch, name an owner, map checks to roles, set your joining rule around the slowest check, write the consent and discrepancy steps, agree retention with Legal, then get it signed and set up in your hiring system. A copy-ready template for Indian employers is below.
We're SpringVerify, and we run background verification for HR teams across India. Our advice is simple: write the policy first, then use a provider that runs it exactly as written. SpringVerify does that. You set a check package for each role, your HRMS or ATS starts it, candidates consent and upload documents online, and every status and source lands in one dashboard with a report you can hand to an auditor. Pazcare's HR manager, who once spent her days on 100 to 200 BGV emails, put it this way: "There is nothing manual in background verification; everything happens online and on a system."
A BGV policy is the approved rulebook for how your company verifies candidates and employees. A practice is what your team does when it remembers. A policy is what you have committed to, signed and can be audited against, and that's what clients, auditors and investors ask for.
The difference shows up at the worst moments. An auditor asks why one finance hire had a court record check and another didn't. A hiring manager wants a star candidate to join on Monday with a check still open, and nobody knows who can say yes. Without a policy, each of these becomes an argument. With one, it's a lookup.
A written policy also protects candidates. Most candidates are honest, and a policy makes sure every one of them in the same role is checked the same way, told what's being checked, and given a fair chance to explain a mismatch before anyone decides anything.
SpringVerify makes the written version hold in practice. Once your role packages sit in your HRMS, a check can't be skipped because a recruiter forgot, and every check leaves a record you can show.
A BGV policy should include ten sections. Most free templates online are written for US law and lean on American "adverse action" rules that don't apply in India. Here is what an Indian employer's policy needs. The rows on checks, timing, consent and reading results are the ones SpringVerify sets up for you, so they run the same way on every hire.
| Section | The question it answers | Who signs it off |
|---|---|---|
| Purpose | Why do we verify candidates at all? | HR head |
| Scope | Who is covered: employees, contractors, interns, rehires, internal moves? | HR head, Procurement for contractors |
| Owners | Who runs checks, who reviews findings, who decides? | HR head |
| Checks by role | Which checks does each role group get, and how far back? | HR, Legal, the business head for sensitive roles |
| Timing | When do checks start, and what must clear before joining? | HR, hiring managers |
| Notice and consent | What do we tell candidates, and how do we record consent? | Legal or privacy lead |
| Reading results | What does each report status mean, and who acts on it? | HR |
| Discrepancies | How do we confirm a finding, hear the candidate and record a decision? | HR, Legal |
| Exceptions | Who can approve joining with a check still open, and on what terms? | Named approver |
| Data handling | Who can see reports, where they live, how long we keep them, who deletes them | Legal, Information Security |
Add a misrepresentation clause too: a material misrepresentation found during or after hiring can lead to an offer being withdrawn or employment ending. Put the same line in the offer letter, and have your lawyer check any wording that goes into an appointment letter.
You build a BGV policy in eight steps, and most of them are decisions rather than writing. Get four people in a room: HR, Legal or your privacy lead, Information Security, and one business head who hires for sensitive roles.
Step 8 is where policies quietly fail. A PDF on a shared drive changes nothing on a busy Monday. SpringVerify connects with 100+ HRIS, ATS and HRMS platforms, including Darwinbox, Keka, Zoho People, Zimyo and Workday, and checks can start automatically from your ATS or HRMS, so the role package your policy names is the one that runs.
Each role should get the checks that match what it can touch, and nothing more. A blanket "everything for everyone" package slows every hire, collects data you don't need and is harder to justify under the data-minimisation principle that India's privacy law is built on.
Use this as a starting matrix and adjust it with Legal. Every check named here is one SpringVerify runs; it is an illustration, not a legal minimum.
| Role group | Example roles | Checks to consider |
|---|---|---|
| A. Every hire | All new joiners | ID verification, current address (digital), court record check; highest education for freshers |
| B. Experienced professionals | Engineers, sales, operations managers | Group A plus employment verification for the last [number] employers and highest education |
| C. Money, data or client systems | Finance, payroll, IT admins, client-site staff | Group B plus reference check and global database check; credit check only where the role handles money and Legal agrees |
| D. Leadership | CXOs, directors, senior hires | Group C plus directorship check and DIN verification; social media screening only with Legal's agreement |
| E. Frontline, field and gig | Delivery, warehouse, security, drivers | ID, address (digital or physical by a field agent), court record; Police Clearance Certificate where a client or the role requires one; drug test only for safety-critical work |
Two rules keep the matrix fair. First, every check needs a written reason tied to the role. Second, everyone in the same role group gets the same package, so nobody can claim they were singled out.
Write the history scope as a number, such as "last two employers" or "last five years", rather than "relevant employment". For employment checks, our employment verification confirms joining date, last working day, last designation and exit details with each past employer, using direct HR contact, PF/EPFO records, MCA/ROC company data and TAN records. When a past employer's HR goes quiet, we escalate to the candidate's reporting manager over WhatsApp. Your policy should say whether those other sources count when a past employer never replies. We'd suggest it says they do.
Set your joining rule around the slowest check in each package, not the average. If your policy says no one joins until every check is green, and you verify degrees directly with universities, some joiners will wait months.
Here are the turnaround times SpringVerify publishes on its own pages, and what we'd write into a policy for each:
| Check | Published SpringVerify turnaround | What to write in the policy |
|---|---|---|
| Basic checks | Under 60 seconds (homepage) | Run at offer acceptance; must clear before joining |
| Address, digital | Typically 24 to 48 hours | Must clear before joining |
| Address, physical (field agent) | 3 to 7 business days | Before joining for roles that need it; otherwise within [number] days of joining |
| Employment | Most checks 5 to 6 working days, depending on how fast past employers respond | Start at offer acceptance; current employer only after relieving or with written permission |
| Education, instant screen | Flags obvious fraud within hours | Must clear before joining |
| Education, official university confirmation | Typically 15 to 90 days, depending on the institution | Joining allowed on a clean instant screen; official result due within probation |
| Court record | Starts automatically when the case is submitted | Must clear before joining; Inconclusive matches follow the PCC route |
Across all checks, SpringVerify's homepage reports that 80% of verifications are completed within 48 hours. That figure helps you plan, but write the policy around the slowest check you order.
One clause saves a lot of awkward calls: current-employer contact. Many candidates don't want their current employer told before they resign. Your policy should record whether the candidate allows that contact, and when. If they don't, verify the current job later, using the relieving letter and the past employer once the candidate has left, and keep the check open with a named owner until then.
No single Indian law sets out what a private employer's BGV policy must contain, but privacy law decides how you collect and keep the data. On 3 November 2026 the SPDI Rules under the IT Act apply, and the DPDP Act's core duties apply from 13 May 2027. Write the policy so it works under both.
| Law | Status | What it means for your BGV policy |
|---|---|---|
| IT (SPDI) Rules, 2011, under section 43A of the IT Act | In force now | Rule 5: get written consent (letter, fax or email) for the purpose before collecting sensitive personal data, and keep it no longer than needed. That covers bank account details, medical records and biometrics, so it touches credit checks, medical tests and face match. Rule 4: publish a privacy policy. |
| DPDP Act, 2023: definitions and Data Protection Board | In force since 13 November 2025 (G.S.R. 843(E)) | The Board exists; the duties below are still to come. |
| DPDP Act sections 3 to 17, including notice (s.5), consent (s.6), legitimate uses (s.7), employer duties (s.8) and candidate rights (s.11 to 14) | From 13 May 2027 | Itemised notice before consent; consent that can be withdrawn; reasonable security safeguards; erasure when the purpose ends; the right to correct and erase data; a grievance contact. Section 44(2) removes section 43A of the IT Act at the same time. |
Three points matter most when you write the policy.
Consent. Section 7(i) of the DPDP Act lets an employer process data "for the purposes of employment". Whether that covers checks on a candidate who hasn't joined yet is a question for your lawyer. Recorded consent is the simpler footing, and it's what the SPDI Rules require today for sensitive data.
Your vendor's copies. Under section 8, the employer stays responsible for processing a vendor does on its behalf, and section 8(7) requires the employer to make its vendor erase data when the purpose ends. Your policy, and your vendor contract, need to cover the vendor's copies as well as yours.
The stakes. Once those provisions apply, the DPDP Act's Schedule sets penalties of up to ₹250 crore for failing to take reasonable security safeguards, and up to ₹200 crore for failing to report a personal data breach. Those duties sit with the employer.
For a specific case, take legal advice.
SpringVerify's security page states that candidate data "is collected with explicit consent, used only for the stated verification purpose", and lists ISO/IEC 27001:2022 and SOC 2 Type II certification. That gives your Information Security team the evidence it will ask for when it reviews your vendor.
The policy should treat a stalled check and a real discrepancy as two different things, because they are. A past employer who never replied tells you nothing about the candidate. A university that confirms a different degree tells you a lot. Mix the two up and a fair candidate gets rejected, or a real problem gets waved through.
Every check on a SpringVerify report carries a named status as well as a colour. Here's how we'd map each one to a policy rule:
| Report status | What it means | What your policy should say |
|---|---|---|
| Completed (Verified) | The check finished and matched | Proceed |
| Insufficiency | Something is missing from the candidate's side | HR asks for the specific item; candidate has [number] working days to supply it |
| Unable to Verify | A source didn't give an answer | Try another source; the decision owner decides whether the hire can proceed; never treated as a discrepancy |
| Minor Discrepancy | A small mismatch, such as a name spelling | HR reviews against the role; usually proceed with a note on file |
| Major Discrepancy | A major mismatch, such as fake employment details | Tell the candidate the specific finding; allow [number] working days to respond; [role] decides and records why |
| Court record: Inconclusive | A possible match that can't be confirmed | No decision on a name match; resolve through a Police Clearance Certificate |
Indian law doesn't set an "adverse action" timetable the way US law does, so set your own response window with Legal and use it every time. The candidate should always hear the specific finding and get a chance to explain it. An apparent mismatch can be a designation that was renamed, a company that was acquired, or a typo in a date.
Court records need special care, because a name match proves nothing on its own. Our court record check grades every match against the candidate's father's name and address, and lets you set how strict that grading is. You can flag only exact name-and-address matches, or escalate every partial match for review. That means your policy's threshold becomes the system's setting. Inconclusive matches go to a Police Clearance Certificate instead of a guess, and every grading decision is logged.
For the step-by-step on clearing stalled checks, see our guide to resolving amber and insufficient BGV cases.
Keep each type of BGV record only as long as its purpose needs, and set those periods with Legal rather than copying another company's number. The SPDI Rules already limit retention of sensitive data to what's needed, and from 13 May 2027 section 8(7) of the DPDP Act requires erasure once the purpose is served, unless another law requires you to keep it.
Split the schedule by record type, because each one has a different reason to exist:
| Record | Why you keep it | Deletion trigger to agree with Legal |
|---|---|---|
| Candidate's raw documents (ID copies, certificates) | To run the check | Once the check is complete and the result is recorded |
| Final verification report | To prove what was checked | A set period after employment ends |
| Consent record | To prove the candidate agreed | The same period as the report it supports |
| Decision record and candidate correspondence | To show how a decision was made | The same period, or longer if a dispute or legal hold applies |
| Records of candidates who didn't join | To answer questions about the decision | A short, set period after the decision |
Two habits break most retention schedules. The first is reports downloaded into inboxes and chat groups, where no deletion rule reaches them. The second is forgetting the vendor's copy. Your policy should say reports stay in approved systems only, and your contract should say how and when your BGV provider deletes its copy.
SpringVerify keeps every verification timestamped, source-cited and stored in one place, with exportable PDFs for audits, so your team has no reason to keep copies in email.
This template is a starting draft for an Indian employer using SpringVerify. Fill every bracket, attach your role matrix as Annexure A and get it approved by the people named in it. It is not legal advice and isn't an approved policy until your company signs it.
[Company name] Background Verification PolicyVersion [number] | Effective [date] | Owner: [HR role] | Approved by: [role] | Next review: [date]
1. Purpose. [Company] verifies information that candidates and employees provide, to the extent relevant to their role, so that hiring decisions rest on accurate facts and our people, clients and data are protected.
2. Scope. This policy covers full-time and fixed-term employees, interns, rehires, employees moving into roles in Annexure A groups C or D, and contractors with access to our premises, systems or clients. For contractors supplied by a partner, [our company / the partner] runs the checks and [role] reviews the results.
3. Responsibilities. [HR role] owns this policy and starts checks. Hiring managers do not see full reports. [Decision owner role] decides on discrepancies. [Legal/privacy role] advises on findings that may be legally sensitive. SpringVerify, our verification provider, runs checks under contract.
4. Checks by role. Each role is assigned a group in Annexure A, which lists the checks and history scope for that group. Everyone in a group gets the same checks. An additional check needs [role]'s written approval and a recorded reason.
5. Candidate notice. Job posts and offer letters state that the offer is conditional on background verification. Before checks begin, the candidate receives a notice listing the checks, their purpose, the provider, how long data is kept and a contact for questions or corrections.
6. Consent. Checks begin only after the candidate's recorded consent for the stated scope. If a candidate refuses or withdraws consent, HR refers the case to [role]; checks do not continue.
7. Current employer. HR records whether and when the candidate permits contact with their current employer. Without permission, that check waits until the candidate has left, and stays open with a named owner.
8. Timing and joining. Checks start at [offer acceptance]. Checks marked "before joining" in Annexure A must be complete before day one. Checks marked "within probation" must be complete by [date or number of days].
9. Reading results. HR reads each check's status and reason, not its colour. Insufficiency, Unable to Verify and Inconclusive results are not discrepancies. A report colour or automated flag never decides an outcome on its own.
10. Discrepancies. HR confirms the finding relates to the candidate, then tells the candidate the specific finding and allows [number] working days to respond with an explanation or documents. [Decision owner] decides, considering the evidence, the candidate's response and its relevance to the role, and records the reason.
11. Exceptions. A candidate may join with a pre-joining check open only with [approver]'s written approval, which records the reason, the open check, any access restrictions, the case owner and a review date.
12. Misrepresentation. A material misrepresentation found during or after hiring may lead to withdrawal of the offer or action under [disciplinary policy], after the candidate has had a chance to respond.
13. Confidentiality and retention. Only [roles] may access reports, and reports stay in [approved systems]. Records are kept and deleted under the retention schedule in Annexure B. HR arranges deletion of SpringVerify's copies under our contract. Sharing a report outside approved systems is a breach of this policy.
14. Re-screening. Employees moving into a group C or D role complete that group's checks before the move. [Any periodic re-screening rule.]
15. Review. [Owner] reviews this policy every [period], and after any change in law, client requirements, role groups or verification provider.
The single most useful line in that template is clause 9. It stops the panic that follows an orange status on a Friday afternoon.
HR teams choose SpringVerify because it turns the policy they signed into what happens on every hire. Each reason below comes with its proof.
Your role packages run on their own. Set one package for each role group and trigger checks from your ATS or HRMS. SpringVerify connects with 100+ HRIS, ATS and HRMS platforms, including Darwinbox, Keka, Zoho People, Zimyo and Workday, so recruiters can't pick the wrong checks by accident.
Consent you can show an auditor. Candidates sign consent and upload documents online, so every consent record sits with the check it covers. Rohit Nair, Project Lead and Program Manager at Zinnov: "The user interface caught our attention the most during the demo. However, the product's highlight was the ability to digitally get a consent form signed by the candidate, upload basic candidate details, and completely automate the process."
No more chasing past employers, universities or candidates. Automated reminders handle candidate follow-ups, and when a past employer's HR goes quiet we go to the reporting manager over WhatsApp. Pazcare's HR Manager Prathima Shetty, on doing BGV five years earlier: "I used to have 100 -200 emails to attend to daily." On SpringVerify: "I have to barely spend a couple of mins initiating a check and only check back if I need updates."
Court results you can defend. Our court check grades matches against father's name and address, at the strictness your policy sets, and sends unclear matches down a PCC route. Ritika Raj, Senior Manager I, HR Shared Services at LoadShare Networks: "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."
Joining dates that hold. Basic checks take under 60 seconds and 80% of verifications are completed within 48 hours, according to SpringVerify's homepage. The employment and address times are in the turnaround table above.
An audit trail and data you can trust. Every verification is timestamped, source-cited and exportable as a PDF. SpringVerify is certified to ISO/IEC 27001:2022 and SOC 2 Type II, as listed on its security page.
A team that answers. Govindprasad Goankar, Executive VP and HR Head at Kotak Mahindra Asset Management: "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."
Pick SpringVerify if you want the policy you wrote to be the process that runs, so every hire is checked the same way and every decision has a record behind it.
SpringVerify is a strong fit if you hire in India, need different checks for different roles, and want consent, status and reports in one place that an auditor or client can review. It suits fast-growing companies writing their first policy, and larger teams moving off email and spreadsheets.
Not the right fit if:
There's no general Indian law that makes a written BGV policy compulsory for every private employer. In practice, clients, auditors and sector regulators ask for one, and the SPDI Rules and DPDP Act require you to handle candidate data with notice, consent and limited retention, which is far easier to prove with a policy.
Yes. A candidate can refuse or withdraw consent. Your policy should say that checks stop, and that a named person decides what happens to the offer, which is usually conditional on verification.
Yes, with the employee's consent and a clear reason, such as a move into a sensitive role or a client requirement. Write those triggers into the scope and re-screening clauses so post-joining checks aren't ad hoc.
Follow the same steps as before joining: confirm the finding, tell the employee the specific issue, give them time to respond, and record the decision. What action you can take depends on their appointment letter and your disciplinary policy. For a specific case, take legal advice.
Review it at least once a year, and straight away after a change in law, a new client requirement, new role groups or a change of verification provider. The DPDP Act's core duties starting on 13 May 2027 is one review you can already put in the calendar.
Yes. You set check packages per role, choose how strict court record grading is, and configure check sequences, SLA alerts and report formats to match your hiring process. Bring your draft policy and role matrix to a demo and we'll show you each rule running.
Fill in the template, draft your role matrix, and then book a SpringVerify demo. Bring your hardest cases: a candidate who won't allow current-employer contact, a past employer that has shut down, and a common name with a court match. We'll show you how each one runs under your policy, before you sign it.
.png)