False Positives in Name Matching: The Similar-Name Problem (2026)
Why a court-record search on a name throws up cases that are not your party's, the India-specific reasons it happens, what a false positive actually costs, and how a good search cuts them down. Last verified October 2026.
Explainer · Name Matching
When you search court records for a name and get back a list of cases, some of those cases are not your party's at all. They belong to a different person or company that happens to share the name or something close to it. These wrong hits are called false positives, and in India they are common, because many people share names and court records rarely carry a unique identifier to tell them apart. This explainer sets out why the similar-name problem happens, what a false positive actually costs you, and how a careful search cuts them down without hiding the real matters. Last verified October 2026.
- What it is: a case returned for a searched name that actually belongs to a different, same-named party.
- Why it is common in India: shared names, spelling variation, and court records that rarely carry a unique identifier.
- What it costs: wrongly blocked clean parties, inflated risk, wasted time and lost trust in the search.
- How to cut it: search by identifiers, score every hit with a match confidence, and confirm serious low-confidence hits.
01What a false positive is
A false positive is a case that a search returns for your searched name but that belongs to someone else. You search for a supplier called "Sharma Traders", and back come matters filed against a different "Sharma Traders" in another state, or against a "Sharma Trading Co" that is a stranger. The name matched; the party did not.
This is the flip side of a search that is thorough. A loose search that catches every spelling variant will catch unrelated parties too; a strict search that avoids them will miss your party's own cases under a slightly different name. The art is separating the real matches from the noise, which is what match confidence is for. See match confidence in litigation search and entity matching and name collisions.
02Why it is so common in India
Several features of Indian names and court records make false positives more frequent here than many people expect:
- Shared names at scale. Common first names, surnames and business words mean thousands of people and firms share a name or a close variant.
- Spelling and transliteration variation. The same name is written many ways across registries, so a single party appears under several spellings and several strangers appear under one.
- Few unique identifiers in cause lists. Court records often carry only a name, not a PAN, CIN or DIN, so there is nothing hard to anchor the match to.
- Repeated generic entity words, such as "Enterprises", "Traders" or "Industries", which recur across unrelated businesses.
- Initials and abbreviations used inconsistently for the same person across different matters.
Phonetic matching, which catches names that sound alike, helps find a party's real cases but also widens the net, so it has to be paired with a confidence signal. See what phonetic name matching is.
03What a false positive costs
False positives are not just noise; they do real damage if they are not caught:
- A wrongly blocked party. A clean supplier, borrower or hire gets rejected because a stranger's serious case was pinned to them. That is unfair to the party and a lost opportunity for you.
- Inflated risk and wasted time. A report padded with unrelated matters looks alarming and takes far longer to read, burying the few findings that are real.
- Lost trust in the process. If a team is burned by false positives a few times, it starts ignoring the search altogether, which is worse than no search.
A false positive is not a harmless extra row. It can wrongly cost a clean party a contract, and it can bury the one case that was real.
04How a good search cuts them down
You cannot remove false positives entirely while court records lack unique identifiers, but a careful process cuts them sharply:
- Anchor on identifiers where they exist. Searching by PAN, CIN or DIN, not just a name, pins a match to the right entity. See how to search litigation by PAN or CIN.
- Score every hit with a match confidence, so a weak name-only hit is flagged rather than silently counted as your party's.
- Use corroborating details, such as address, co-parties, directors or the forum's location, to confirm or rule out a match.
- Keep a human in the loop on the serious, lower-confidence hits, because the cost of a wrong block is high enough to justify a check.
05The false negative on the other side
Chasing false positives too hard creates the opposite error, a false negative, where a search is tuned so tight that it misses your party's own cases filed under a variant spelling or an initial. That is the more dangerous mistake, because a missed serious matter is the whole failure the search was meant to prevent.
The honest answer is to search wide, then rank by confidence, so you see both the strong matches and the weaker ones you can resolve, rather than quietly dropping either. A good workbook shows you the low-confidence hits; it does not hide them.
06Reading matches honestly
Two caveats keep name matching fair. First, a match is a candidate until it is confirmed. A high confidence score makes it very likely your party's, but on serious matters the right move is still to confirm identity before acting. Second, a case being on the list is not a finding of wrongdoing. Court records show what was filed, not who is right, and any criminal matter carries the presumption of innocence until a court decides. Treat a flagged match as a reason to look, not a conclusion.
07Where Claw fits
Claw is an all-in-one legaltech platform for Indian advocates, law firms, and corporate legal teams, combining AI-based case search, an AI legal assistant (Legal GPT), case management, and compliance automation across all Indian courts and tribunals.
ClawScore (at clawscore.clawlaw.in) is Claw's litigation and criminal-risk intelligence service, and the similar-name problem is exactly what its match-confidence design is built around. You name a company or a person, and ClawScore searches across 9,102 courts, benches and forums and returns a scored Excel workbook: a Summary carrying a ClawScore risk band of Clean, Low, Moderate or High, a Matters sheet listing each case, a Related parties sheet covering directors and guarantors, and a Coverage sheet showing what was searched. Every finding on the Matters sheet carries a match confidence that flags similar names, so a weak name-only hit on a common name is marked rather than silently counted, and the band is not quietly inflated by a same-named stranger's case. Searching by identifiers such as PAN, CIN or DIN where they exist anchors matches to the right entity, and the Related parties sheet uses connected names and roles to help confirm or rule out a hit. Constant Monitoring can then watch a list of names and report New, Changed and Closed matters on a daily, weekly or monthly scan without re-flooding you with the same resolved false positives. Results come back in under 5 seconds, judgment search spans 30 crore+ judgments with Supreme Court decisions from 1950 and High Court decisions from 1990, and Claw does not use your case documents or searched names to train its AI models. A low or nil result means nothing was found in these registries on the date searched under the names searched, a match is a candidate until confirmed, and the output is a triage signal, not legal advice.
To see matches ranked by confidence instead of a flat name-only list, run a case search across Indian courts by party name and identifier.
08Sources and further reading
- eCourts (district and High Court case status): ecourts.gov.in
- National Judicial Data Grid (official pendency data): njdg.ecourts.gov.in
- Ministry of Corporate Affairs (company and director records): mca.gov.in
- Claw: clawlaw.in
This is a general explainer for an Indian B2B audience, not legal advice. Confirming identity on a serious match is a judgement call, so take advice where it counts before you act on a finding.
09Frequently asked questions
What is a false positive in a litigation search?
It is a case that comes back for the name you searched but does not actually belong to your party. It belongs to a different person or company with the same or a similar name. False positives happen because many parties share names and court records rarely carry a unique identifier to tell them apart.
Why are false positives so common in India?
Because common first names, surnames and generic business words are shared at scale, the same name is spelled and transliterated many ways, and court cause lists usually carry only a name, not a PAN, CIN or DIN. Phonetic matching that catches sound-alike names helps find real cases but also widens the net.
What harm does a false positive do?
It can wrongly block a clean supplier, borrower or hire because a stranger's serious case was pinned to them, it inflates the apparent risk and buries the few real findings, and repeated false positives make a team stop trusting the search altogether.
How can false positives be reduced?
Search by identifiers such as PAN, CIN or DIN where they exist, score every hit with a match confidence so weak name-only hits are flagged, use corroborating details such as address, co-parties and directors to confirm or rule out a match, and keep a human check on serious lower-confidence hits.
Is it better to tune a search very strict to avoid false positives?
No. Tuning too strict creates false negatives, where the search misses your party's own cases filed under a variant spelling, which is the more dangerous error. The better approach is to search wide and then rank by confidence, so both strong and weak matches are visible and can be resolved rather than hidden.