A name match is not a criminal record

A criminal record check in India starts with a name search. That single fact determines almost everything about how the result should be handled, and it is the thing most often glossed over.

The eCourts index and the district court registers are searchable by party name, sometimes with a father's name or a year. They are not searchable by a national identity number. There is no Aadhaar field on a cause list. So what a search returns is not "this person's cases" — it is "cases involving somebody with a similar name."

For a common Indian name across a metropolitan jurisdiction, that can be a large number of results, none of which necessarily relate to your candidate.

The error that matters

The consequential mistake is reporting an unresolved name match as though it were a finding.

It is technically accurate — a matching name does appear in a register — and it is close to useless as a hiring signal. Worse, it is actively harmful: it attaches a criminal implication to a candidate on the basis of a coincidence that is more likely than not for common names.

A report that says "match found" without saying how the match was corroborated has transferred the hard part of the work to the reader, who has less information than the searcher did.

Closing the gap

Between a name hit and a defensible finding sits identity corroboration. In practice that means matching on attributes the register does happen to carry:

• Father's name, which appears in many filings and is a strong discriminator.
• Date of birth or stated age, where recorded.
• Address at the time of filing, checked against the candidate's declared address history for the same period.
• Case type and jurisdiction, checked against where the candidate actually lived. A case in a district they have never lived in warrants scepticism, not inclusion.

Most raw hits fall away at this stage. That narrowing is the actual work of a criminal check, and it is invisible in a report that only shows the final number.

Name variants cut the other way

The same looseness that produces false positives also produces false negatives. Indian names transliterate inconsistently — the same person may appear as Rahul, Rahoul, or with initials only. Surname and given name are sometimes reversed. A search that only tries the exact declared spelling will miss genuine records.

So a competent search expands variants deliberately, then narrows on identifiers. Both halves are necessary. Expanding without narrowing produces noise; narrowing without expanding produces false comfort.

Coverage is uneven, and should be stated

Digitisation varies significantly by state and by court tier. Some jurisdictions are well represented in the online index; others require a physical search at the court complex, and some older records are not reliably searchable at all.

A report that quietly presents a partial search as complete is misleading in a way that is difficult for the reader to detect. The honest form states which jurisdictions were searched, by what method, and where coverage is limited — so a hiring manager knows what the absence of a finding is actually worth.

What a defensible report looks like

• The name variants searched, and the jurisdictions covered.
• The number of raw hits, and how many survived identity corroboration.
• For any surviving match, which identifiers corroborated it.
• For anything ruled out, why.
• An explicit statement of coverage limits.

None of that is exotic. It is the difference between a search result and a verification — and for the candidate on the other side of it, that difference is the whole thing.

• criminal check
• eCourts
• adjudication