A BGV form is the form a new hire fills in so you can run their background verification. It collects who they are (name, date of birth, one ID), where they have lived, where they studied and where they have worked, plus referees if you check references. It ends with the part that carries the most weight: a signed consent that names each check, who will run it, how long you will keep the results and how the candidate can withdraw. Below is a free template you can copy today, field by field, with the reason each field is there.
Most BGV delays don't start at a slow university or a silent ex-employer. They start on the form. A roll number left blank. A flat the candidate lived in for a year between jobs that nobody asked about. A previous company listed with nothing but a generic HR inbox. Each gap becomes a follow-up email, the follow-up sits unanswered for days, and a perfectly good offer quietly goes stale.
If you would rather not build and police a form at all, use SpringVerify's employee background verification. The candidate gets a secure link, signs consent digitally before any check starts, and fills in a BGV form that already asks for what the checks need: an HR contact and a reporting-manager contact at every past employer, and every address they have lived at within the lookback window you choose. HackerEarth's HR team put the difference plainly: "You just had to upload the candidate's CV, and the process was initiated."
A BGV form (background verification form) is the document a candidate completes so an employer, or a verification partner working for the employer, can confirm the claims on their CV. It records the details each check needs and the candidate's consent to run those checks. Some companies call it a candidate declaration form, a BGV consent form or a letter of authorisation, but they all do the same job.
The form is not the same as the documents. The form says "I studied B.Com at this college, roll number 1234, passed in 2019". The degree certificate and marksheet are the evidence. A verifier then confirms the claim with the source, such as the university or the past employer.
A BGV form should include six sections: personal details, address history, education, employment history, references (only if you check them) and a consent and declaration section. The table below shows what to ask in each section, which check uses it, and what to leave out.
| Section | Fields to ask for | Used by | When to skip it |
|---|---|---|---|
| Personal details | Full name as on certificates, other names used, date of birth, mobile, email | Every check, to match records to the right person | Never |
| Identity | One government ID: PAN, passport, voter ID, driving licence or Aadhaar (masked copy or DigiLocker) | ID verification | Never, but ask for one ID, not all of them |
| Parent's name | Father's or parent's name | Court record or police checks, to tell apart people with the same name | You are not running a court or police check |
| Addresses | Current and permanent address with PIN code, plus every address in your lookback window, with from and to dates | Address verification | Ask for the current address only if that is all your policy verifies |
| Education | Qualification, college, university or board, roll or registration number, year of passing, mode (full-time, part-time, distance) | Education verification | Ask for the highest qualification only if that is all you verify |
| Employment | Employer's registered name, city, employee ID, designation, dates, reason for leaving, HR contact, reporting-manager contact, UAN (optional) | Employment verification, gap check | The candidate is a fresher with no work history |
| Current employer | "Do not contact before" date | Employment verification | The candidate is not currently employed |
| References | Name, designation, organisation, relationship, email, phone | Reference check | You are not running reference checks |
| Consent and declaration | Check-by-check consent, notice, declaration, signature or e-sign, date | All checks | Never |
Two fields earn their place more than most. The reporting-manager contact matters because employment is usually the slowest check: another company has to reply. SpringVerify's form asks for both an HR contact and a reporting-manager contact at every past employer, so the verifier reaches the right person fast, even at small companies. The UAN is useful but optional: SpringVerify's employment verification can start at offer acceptance without one, and uses PF/EPFO records as a backup source where they are available.
Copy the template below into Word or Google Docs, replace everything in square brackets, and delete the sections your checks don't use. It is written for Indian employers and follows the notice and consent points of the DPDP Act and Rules.
[COMPANY NAME] BACKGROUND VERIFICATION (BGV) FORM AND CONSENT PART A. WHY WE ARE ASKING Your offer from [Company Name], dated [Offer Date], is subject to background verification. This form explains what we will check, who will check it, how long we keep the results and how to reach us. You can ask for this form in English or [another language]. PART B. YOUR DETAILS Full name (exactly as on your education certificates): Other names used (maiden name, spelling changes), or "None": Date of birth (DD/MM/YYYY): Father's or parent's name (only if Part G includes a court or police check): Mobile number: Email: ID you are submitting (tick one): PAN / Passport / Voter ID / Driving licence / Aadhaar (masked copy or DigiLocker only) ID number (for Aadhaar, last 4 digits only): PART C. ADDRESSES Current address with PIN code: Living here since (MM/YYYY): Permanent address with PIN code (or "Same as current"): Every other address in the last [2 / 5 / X] years: Address and PIN code | From (MM/YYYY) | To (MM/YYYY) [Add one row per address] Best time and phone number for an address check: PART D. EDUCATION (highest qualification first) Qualification and specialisation: College or institute: University or board: Roll or registration number: Year of passing: Mode: Full-time / Part-time / Distance [Repeat only for the qualifications we verify: e.g. highest degree only] PART E. EMPLOYMENT (most recent first) Employer's registered name: City: Employee ID: Last designation: From (MM/YYYY): To (MM/YYYY): Reason for leaving: HR contact (name, email, phone): Reporting manager (name, designation, email, phone): UAN (optional, helps confirm dates through EPFO records): [Repeat for each employer in the last [X] years] Gaps of more than [X] months between jobs, and the reason: Current employer only: please do not contact before [date / my resignation is accepted]. PART F. REFERENCES (only if Part G includes a reference check) Name | Designation | Organisation | How you worked together | Email | Phone PART G. THE CHECKS YOU ARE AGREEING TO Tick Yes or No for each check. If you say No to a check, we will tell you in writing what that means for your offer before we decide anything. Identity: we confirm your ID with the issuing authority's records. Yes / No Address: [digital check by secure link and GPS / visit by a field agent]. Yes / No Education: we confirm your qualification with the university or board. Yes / No Employment: we confirm dates, designation and exit details with each employer in Part E, and may use EPFO records. Yes / No Court records: we search court records in your name. Yes / No References: we speak to the people you name in Part F. Yes / No [Other check]: because [why this role needs it]. Yes / No PART H. NOTICE: HOW WE USE YOUR INFORMATION Data we collect: the details in Parts B to F and the documents in Part I. Purpose: to verify what you have told us before we confirm your appointment. We will not use it for any other purpose. Who runs the checks: [Company Name] and our verification partner [Vendor Name], working on our instructions. Who sees the results: [HR team]; the hiring manager sees flagged results only. How long we keep it: if you join, for your employment plus [period]. If you do not join, we delete it [period] after our decision, unless a law requires us to keep it longer. If something does not match: we will tell you what was found and where it came from, and give you [X] working days to explain before we decide. Withdrawing consent: email [address] or use [link]. Withdrawing is as easy as giving consent. Checks already completed remain valid, and we will tell you how withdrawing affects your offer. Your rights: to access, correct or erase your data, or to ask a question, contact [name, designation, email, phone]. You may also complain to the Data Protection Board of India. PART I. DOCUMENTS TO UPLOAD [List only what your checks need, e.g. ID, degree certificate and final marksheet, relieving letter, last payslip or Form 16 for each employer] PART J. DECLARATION AND CONSENT I confirm that the information in this form is true and complete. I have read Part H. I consent to [Company Name] and [Vendor Name] processing my personal data for the checks I marked Yes in Part G, and I authorise the employers, institutions and referees I have named to share the information those checks need. Signature or e-sign: Name: Date:
A template only works if someone checks every form before verification starts. That is the hidden cost of a Word or PDF form: you, or your vendor, find the blank roll number on day three, not when the candidate is still on the page.
The consent part should say, in plain language, what personal data you will collect, the purpose (verifying the candidate before appointment), which checks you will run, who runs them, how long you keep the results, and how the candidate can withdraw consent, use their rights and complain. The candidate then agrees with a clear action, such as ticking each check and signing.
That list is not a style preference. It tracks India's data protection law, which is phased in:
Here is how that turns into wording on the form:
| Weak wording | Why it fails | Better wording |
|---|---|---|
| "I authorise the company to conduct any checks it deems fit." | Not specific; the candidate can't know what they agreed to | "I consent to the checks I have marked Yes in Part G." |
| Consent clause on page 9 of the offer letter | The notice should be understandable on its own | A separate consent section or form, with its own signature |
| "Records will be retained as per company policy." | No period stated | "If you do not join, we delete it [period] after our decision." |
| No withdrawal route | Withdrawal must be as easy as giving consent | "Email [address] or use [link] to withdraw." |
| "I waive my right to raise any complaint." | Section 6(2) makes consent invalid to the extent it breaks the Act; the Act's own illustration is a waiver of the right to complain | Name the person to contact and mention the Data Protection Board |
A note on the "employment" route. Section 7(i) of the Act lets an employer process personal data without consent "for the purposes of employment". For a candidate who hasn't joined yet, consent is still the safer basis. For a specific case, take legal advice. For the full journey from job post to deletion, see how to build a DPDP consent flow for hiring.
SpringVerify builds this into the product. Every candidate completes an explicit digital consent step before any verification is initiated, and that consent is timestamped, logged and stored in the audit trail for each check. When section 6(10) asks you to prove consent, the proof is already in your dashboard rather than buried in an inbox.
India has no single law that says "every employer must use a BGV consent form". But if consent is your basis for processing a candidate's personal data, the DPDP Act requires a proper notice and consent from 13 May 2027, and you must be able to prove both. In practice you need a signed authorisation anyway: the past employers, universities and referees you approach will often want to see it before they answer.
Treat the form as your evidence. If a candidate ever asks "who told you that you could call my old manager?", the answer should be a signed page with a tick next to "Employment", not a memory of a phone call.
Send the BGV form after the candidate accepts the offer, not with the job application. At application stage you would be collecting addresses, IDs and employment details from hundreds of people you will never hire, which is the opposite of collecting only what the purpose needs.
Timing has two more rules of thumb:
The mistakes that slow BGV down most are missing details the verifier needs: an unrecorded past address, an employer with no reachable contact, a blank roll number or a document that never got uploaded. In SpringVerify's reports, a missing document or detail shows up as an "Insufficiency", and the check waits until someone supplies it.
| Mistake on the form | What happens next | The fix |
|---|---|---|
| Name written differently from the certificates | A "Minor Discrepancy" for a name spelling variation, plus questions | Ask for the name as on certificates and "other names used" |
| Only current and permanent address asked | The verifier chases the candidate mid-check for an old address | Ask for every address within a set lookback window |
| Past employer given as a generic HR email | The check sits waiting on an inbox | Ask for an HR contact and a reporting-manager contact |
| Roll or registration number left blank | The university can't match the record | Make the field mandatory |
| Document not uploaded | "Insufficiency": the check can't proceed | Make the uploads your checks need mandatory |
| Consent buried in the offer letter | Weak proof of what the candidate agreed to | A separate consent section with a tick per check |
| Full Aadhaar photocopy requested | You hold data you don't need | Masked Aadhaar or DigiLocker |
| Every field asked of every hire | Over-collection, longer forms, more drop-off | Map each field to a check, as in the table above |
The address gap is the one that surprises teams most. Most BGV forms ask for the current and permanent address only, but candidates move cities for college, for a first job and between roles. SpringVerify reports that cases used to stall for three to five days waiting for candidates to reply about addresses like these. Its BGV form now lets you set a lookback window, such as two years, five years or a custom period, and asks the candidate for every address in that window before verification begins. You also choose how each address is checked: digital, physical or postal. If you are weighing those methods, see digital or physical address verification.
On masked Aadhaar: UIDAI's masked Aadhaar hides the first 8 digits and shows only the last 4. If a candidate offers their full Aadhaar copy, you rarely need it. SpringVerify masks Aadhaar numbers after processing and never stores them in raw form.
A Word or PDF template is fine for a handful of hires a year. Once you are hiring every week, a digital BGV form wins because it stops incomplete submissions at the source, records consent with a timestamp and shows you where every case stands.
| Word or PDF BGV form | SpringVerify digital BGV form | |
|---|---|---|
| Consent record | A scanned signature in an email thread | Explicit digital consent before any check, timestamped and logged in the audit trail |
| Incomplete answers | Found when someone reads the form | Address history validated as the candidate types; mandatory document collection |
| Past addresses | Whatever the candidate remembers to add | Every address in the lookback window you set |
| Past employer contacts | Often one HR email | An HR contact and a reporting-manager contact for every employer |
| ID | Photocopies to store and protect | ID checked against government sources, with a DigiLocker option for candidates |
| Follow-ups | Your team's emails and calls | Automated reminders and a real-time dashboard |
| Starting a case | Email the form, wait, re-key the data | Invite from the portal, or trigger checks from your ATS or HRMS |
Customers point to the form and consent step first. Rohit Nair, Project Lead and Program Manager at Zinnov: "The ability to digitally get a consent form signed by the candidate, upload basic candidate details, and completely automate the process was the highlight."
HackerEarth's Senior Human Resources Generalist, Asmita Paul, described the switch from a vendor where "initiating the checks was manual" and, for a couple of candidates, reports arrived six months after they had joined. With SpringVerify: "The automated platform, interim reports, and the quick turnaround time easily saved us 3-4 hours daily." Her team now steps in only "to talk to the candidate about an issue with their documentation."
At Greedy Game, a lean HR team kept verification complete as hiring grew with "mandatory document collection to ensure completeness", and SpringVerify "ensured candidate consent and documentation were handled systematically."
SpringVerify's BGV form works in four steps: you invite the candidate, they give consent and fill in the form, the checks run, and you review a clear report and decide.
If you are the candidate, fill in the BGV form slowly and once. Write your name exactly as it appears on your certificates, list every employer in the period asked (short stints included), and give a reporting manager who will pick up the phone. Keep your ID, degree certificate, marksheets and relieving or experience letters ready before you start, and explain any gap in a sentence rather than leaving it blank.
You are also entitled to know what will be checked, who will check it and how long the results will be kept. A good form tells you without being asked. If yours doesn't, ask HR.
SpringVerify is a strong fit if you hire every week or in batches, and the time your team spends chasing forms is starting to show in joining dates. It suits:
It is probably not for you if:
Pick SpringVerify if you want every candidate's BGV form complete and consented on the first pass, so your new hires start on the date you planned instead of the date the last follow-up came back.
BGV stands for background verification. In hiring, it means confirming a candidate's identity, address, education, employment history and other claims with the original sources before or soon after they join.
They are often one document. The BGV form collects the details each check needs; the consent section records the candidate's agreement to those checks. Some employers use two separate documents. Either way, the consent should name each check, who runs it, the retention period and how to withdraw.
Yes. Copy the template in this article into Word or Google Docs, fill in your company's details and save it as a PDF. If you hire often, a digital form such as SpringVerify's saves you checking every submission by hand.
Only if you run a compensation check. Many older templates ask for last drawn CTC by default, but if no check uses it, leave it out. Every field you collect is a field you must protect, keep for a stated period and then delete.
It depends on the checks. With SpringVerify, basic checks finish in under 60 seconds and 80% of verifications are completed within 48 hours. Employment checks usually take 5 to 6 working days, and official university verification can take 15 to 90 days.
Not always. Many employers accept another government ID such as PAN, passport, voter ID or driving licence. If Aadhaar is used, you can share a masked Aadhaar, which shows only the last 4 digits, or verify through DigiLocker if the employer offers it.
A well-designed BGV form lets you set a date before which your current employer won't be contacted, such as the day your resignation is accepted. If the form has no such field, tell HR your preferred date in writing.
Tell HR or the verification partner straight away and send the correct detail. A small mismatch, such as a spelling variation in a name, is recorded as a minor discrepancy, and your employer can accept the explanation under its own policy. Leaving a known error uncorrected is what turns it into a problem.
Ready to stop chasing forms? See how SpringVerify runs employee background verification, from consent to report.
.png)