Meera ran HR at a mid-sized logistics company in Pune. In March, she hired a warehouse supervisor with a strong resume, a confident interview and glowing references. His documents looked clean. Her team had checked his Aadhaar and PAN, called his last employer, and sent him an offer letter within a week, because the client was waiting and the shift needed a lead.
Six weeks later, inventory started disappearing from the night shift. It wasn’t dramatic, just a few cartons at a time. When the company finally dug into it, they found out that the supervisor had left his previous employer after a theft complaint. There was a case, and it was on record. Nobody had looked.
I’ve changed the names and details, but this story is a composite of situations that come up again and again in hiring conversations. What strikes me every time is that the hiring team wasn’t careless. They just believed that “verified documents” and “clean background” meant the same thing. They don’t.
This is what a criminal record check in India actually covers, where it falls short, and how employers can use it properly.
Identity checks and criminal checks answer different questions
Verifying someone’s identity tells you the person is who they say they are. A criminal record check asks a separate question: does anything in the court or police system attach to this person?
It’s an easy distinction to blur, because both usually sit inside one background verification package. A candidate can have a perfectly genuine Aadhaar and still have a pending criminal case in a district court. Meera’s team confirmed the first and never asked the second.
What a criminal record check in India really looks at
There’s no single national database you can type a name into and get a verdict. Records are spread across several places, and a good check combines them.
The first is court records. Many district and high court cases are digitized and searchable, and a court record check looks for criminal and civil matters that match the candidate’s name, parentage, and address details. OnGrid describes this as matching the information a candidate furnishes against registered cases in digitized court databases, which is a fair summary of how the process works in practice.
The second is police verification. This is a different route. It involves the police authority for the area where the person lives, and it can be done directly or through partners such as law firms who handle the on-ground coordination. It tends to take longer, but for some roles it’s the more appropriate check.
The third is the candidate’s own declaration, which matters more than people realise. A signed declaration gives you a baseline. If the candidate says “no cases” and the check says otherwise, the mismatch itself is the finding.
A thorough check usually draws on more than one of these, because each one has blind spots.
The part nobody tells you: records are messy
Here’s where experience matters. India’s record-keeping is improving fast, but it isn’t uniform. Some of the problems I see employers run into:
Names are spelled differently across documents and courts. “Mohd.”, “Mohammad” and “Mohammed” can be the same person. A common name like “Rakesh Kumar” can return dozens of unrelated cases, so a responsible provider cross-checks with father’s name, date of birth and address before reporting anything, because falsely linking a candidate to someone else’s case is a serious harm.
Jurisdiction matters. A check is only as good as the places it searches. Someone who has lived in three cities over ten years may have records in any of them, so the address history you collect decides how far the check reaches.
Not every court’s records are equally digitized. A clear result means “nothing found in the sources searched.” It doesn’t mean “nothing exists anywhere.” The honest way to read a report is with that limit in mind.
Cases have stages. An FIR, a pending trial, an acquittal and a conviction are very different things. A report that lumps them together invites bad decisions.
Back to Meera
After the theft, Meera did something I think more HR leaders should do. She didn’t blame the supervisor first. She mapped her own hiring process and found three gaps. Verification started only after the offer. Criminal checks were “optional” for roles under a salary threshold, even for roles with access to inventory. And nobody had defined what would count as disqualifying.
That third gap is where most employers get stuck. They run the check, receive a report with a flagged case, and then freeze, because there’s no policy for what to do next.
Decide in advance what a “hit” means
Before you order a single check, write down how your company will respond to different results. It doesn’t have to be elaborate. A few principles are enough.
Link the decision to the role. A pending case for a cheque-bounce dispute means something different for a delivery executive than for a finance manager handling payments. A financial-fraud case matters a lot for a cashier and less for a graphic designer. Relevance to the job is the fairest test, and it’s also the most defensible one.
Separate allegations from outcomes. Treat a pending case, an acquittal and a conviction differently, and consider how old the matter is and how serious.
Give the candidate a chance to respond. Records can be wrong, belong to someone else, or have an explanation. A short conversation before you withdraw an offer protects the candidate and protects you from a bad decision.
Be consistent. If you apply different standards to different people without a reason, you’re creating legal and reputational risk.
Consent and the law: don’t skip this
Running a background check on someone without their knowledge is a bad idea ethically and, increasingly, legally. India’s Digital Personal Data Protection Act, 2023 puts consent and purpose limitation at the centre of how personal data is handled. In practice, that means telling the candidate what you’re checking and why, getting their clear consent, collecting only what’s needed for the role, storing it securely, and not keeping it forever.
The details of the Act and its rules keep evolving, so have your legal counsel confirm what applies to your organization. I’m not a lawyer, and nothing here is legal advice. But the direction is clear: transparency and consent are the baseline, not the extras.
Some sectors go further. Private security agencies, schools, financial institutions, and cab and delivery platforms often face sector-specific expectations around staff verification. If you operate in one of these, check the regulator’s current requirements rather than relying on a general guide.
When to run the check
Timing is a quiet source of trouble. Many companies verify after the candidate has already resigned from their old job, which makes any bad result painful for everyone. A cleaner approach is to make the offer conditional on successful verification and say so in the offer letter. The candidate knows what to expect, and you aren’t stuck deciding under pressure.
For high-volume hiring, speed matters too. Digital platforms have shortened what used to take weeks. OnGrid, for instance, says it completes preliminary checks within hours and most full cases in under five working days. Your own turnaround will depend on the check type, the jurisdictions involved, and how quickly the candidate submits their details. Police-based verification in particular often takes longer than a digital court search, so plan for it.
Choosing a verification partner without getting dazzled
If you outsource, ask pointed questions instead of accepting a glossy sales deck.
Ask where the data comes from and how matches are confirmed. Ask how they handle common names and what their process is when a record is ambiguous. Ask whether consent is built into the workflow and whether reports are audit-ready. Ask about information security: certifications like ISO 27001 and SOC 2 are a reasonable signal that someone has taken it seriously, though they’re a starting point, not a guarantee. And ask what happens if a candidate disputes a finding, because they will sometimes, and a good provider has a process for it.
A provider that’s vague about any of these is telling you something.
Common mistakes I’d steer you away from
Treating the check as a formality for senior hires only. Some of the highest-risk roles, like people with physical access to premises, customers’ homes, or cash, sit at junior levels.
Using a single source and calling it done. One database is one view.
Rejecting on a name match alone. Always confirm identity details before acting.
Having no policy, then deciding emotionally when a flag appears.
Collecting data you don’t need. More isn’t better; relevant is better.
What Meera does now
Her company now starts verification at the conditional-offer stage for every role with access to stock, cash or customer premises. Candidates sign a clear consent form. Reports go to a small group within HR, not to the hiring manager’s WhatsApp. And there’s a one-page guideline on how to read a result, which she shared with me, saying it’s the most valuable document she wrote last year.
It cost her a few cartons of inventory and some sleep to learn that lesson. It doesn’t have to cost you.
The takeaway
A criminal record check in India won’t give you certainty, and no honest provider will claim it does. What it gives you is a documented, consent-based, reasonably thorough look at the part of a candidate’s history that the law actually records. Used with a clear policy, fair judgment and respect for the candidate, it’s one of the most useful tools an employer has. Used carelessly, or skipped, it’s an expensive gap.
If you’re building or tightening your screening process, start with the policy, then pick the checks that match the role, and then choose a partner who can explain their method in plain language.
Leave a Reply