Petitioners, Respondents and Advocates: How to Read an Indian Court Case Record

If your work involves background verification, lending, insurance or compliance, you will eventually be handed a court case record and asked what it means. The problem is that Indian court case records speak a specialised vocabulary of case types, party designations and procedural stages. This guide is a plain-English, field-by-field walkthrough of how to read an Indian court case record so that a non-lawyer can tell what kind of case it is, who is on each side, where it stands and — most important — whether it actually belongs to the person you are checking.

Before going further, a quick note on sources. Under the eCourts Mission Mode Project, court information is published on the official portal at services.ecourts.gov.in, with the Supreme Court’s own records on the judiciary site at main.sci.gov.in. Anyone who needs to know how to read an Indian court case record in depth should start from those primary sources, and cross-check anything your screening depends on against the human-verified layer that tools like NeevLegal add on top of raw court data.

This article covers the fields you will actually see on a typical cause list, case status screen or judgment: the cause title, the parties and their designations, the advocates, the court and bench, the case type code, the filing and registration dates, the stage and sub-stage, the status and disposition, and the orders and recent listings. We close with a practical checklist for deciding whether a record really matches the person you are checking.

Why knowing how to read an Indian court case record matters for verification

Names are not unique. There are thousands of people named “Rahul Kumar” or “Satish Sharma” in Indian court records, and a generic name search can surface cases that have nothing to do with your candidate or borrower. The whole skill of how to read an Indian court case record is really about extracting the identifying and status fields that let you narrow a list of matches down to the one record — or to conclude, correctly, that there is no match at all.

For an HR or risk analyst, the cost of getting this wrong is asymmetrical. A false positive could block an otherwise clean hire or loan; a false negative could let a material criminal or civil matter slip through. So when you learn how to read an Indian court case record, approach it the way a screening analyst would: read the identifiers first, then assess the substance, then check the disposition.

The cause title: the top of the case

Every court record opens with a cause title — the formal name of the case, sometimes abbreviated as “CT” or listed as the “case title”. It looks roughly like this:

State of Maharashtra v. Salim Khan & Ors.

or

Rukmini Devi v. Union of India

The cause title tells you which two (or more) sides are litigating. In Indian practice it is almost always written with the letter “v.” (or “vs.”) for “versus”. Knowing how to read this line matters because the order of names carries legal meaning — the first party is not always the more important one, and nobody is automatically “the bad guy” just because they are named first.

Common abbreviations in cause titles

• v. / vs. — versus, separating the parties.
• & Ors. — “and others”, meaning there are additional parties not named in the title.
• & Anr. — “and another”, a single additional party.
• In re — “in the matter of”, used in certain petitions.
• State / Union of India — a government party, common in criminal and public-law matters.

The parties: who is on each side

Indian courts use specific words for who fills each side of a case, and those words depend on the type of proceeding. The single most common reason someone misreads a record is mistaking which role label applies to which type of matter.

Petitioner vs. respondent

In most writ petitions and in many appeals, the person who brings the matter is the petitioner (sometimes titled “Petnr.”) and the person or authority responding is the respondent (“Resp.”). A person filing a writ petition against a government body is a petitioner; the government department is the respondent.

Applicant vs. opponent / non-applicant

In miscellaneous applications, the mover is the applicant and the other side the opponent or non-applicant. You will see this most often within a civil or criminal matter where a side asks the court to do something procedural — an interim application, an exemption application, a recall application.

Plaintiff vs. defendant

In an original civil suit (a CS or civil suit), the person who sues is the plaintiff and the person sued is the defendant. This is the terminology of traditional civil litigation and is distinct from the petitioner/respondent labelling used in writ petitions and appeals.

Accused / appellant in criminal records

In criminal matters, the party facing trial appears as the accused; if they have filed an appeal against their conviction, they become the appellant and the prosecution side is the respondent. A single criminal record can therefore show the same person re-labelled across stages — accused at trial, appellant on appeal.

Here is the practical point when it comes to parties: whichever label is used, confirm that the party you care about is actually on the record, in the right role, and correctly linked to that person by the identifying details we cover below.

Advocates and appearing counsel

Records usually list the advocates on record for each side — the lawyers representing the petitioner/plaintiff/appellant and the respondent/defendant. This field is less important for verification substance, but it has real value:

• It confirms the matter was actively contested or actively pursued (a represented matter is a live one).
• The presence of a senior lawyer or a specific government advocate can hint at the matter’s importance.
• It is a useful cross-check that the record is real and complete rather than a fragment.

Some records also name the advocate for the state or the public prosecutor in criminal matters. None of these advocate names prove or disprove anything about the party themselves, so do not over-weight them during verification — use them as corroboration, not as evidence of materiality.

The court and the bench or judge

The record will name the court (for example, a specific district court, a specific High Court, or the Supreme Court of India) and usually the bench — a single judge or a Division Bench of two or more judges hearing the matter. Depending on the system, you may see a judge’s name, a bench designation, or simply a court code and case number.

Why this matters: the court and bench tell you the record’s jurisdiction and level. A matter before a magistrate’s court is a very different thing from a matter before the Supreme Court, even where names overlap. When you are matching a record to a person, always record the court alongside the case number — two records in different courts that otherwise look alike are two different cases, not one case in two places.

Case type codes: the vocabulary of Indian litigation

Every case carries a case type code (sometimes called a “case category” or “case type short code”) that appears in its number, such as CRL.APPEAL 42/2020 or WP (C) 101/2021. Learning these codes is arguably the fastest route to gaining fluency in how to read an Indian court case record, because the code alone tells you most of what the case is about.

The table below summarises the codes you are most likely to encounter across Supreme Court, High Courts and district courts. Note that exact abbreviations vary slightly by court and by the eCourts software the court uses, so always confirm against the specific record.

Glossary of common Indian case type codes

For a fuller reference, consult a reputable legal glossary of Indian case codes — for example the widely used list of case categories published alongside eCourts reference materials, such as the case-type tables on eCourts and the case category guides maintained by High Courts.

Dates: filing vs. registration, first hearing, next hearing

Dates are where misreading is most common. A record can show several distinct dates, and each means something different:

• Filing date / Diary number: when the case material was first submitted to the court registry. This is not the same as it being officially registered.
• Registration date / Case number date: when the case was formally numbered and registered. The case number is tied to this registration.
• First hearing date: the first date the matter was listed before a judge.
• Next hearing date / Next listed date: the next scheduled date for the matter to be heard.
• Order date: the date of the most recent substantive order or judgment.

When you read a record, treat the registration date and the case number as the anchors, because together they are the most precise identifiers after the parties’ names. A long gap between filing and registration (a common reality with heavy registries) is not itself a red flag about the case’s substance.

Stage, sub-stage and status

The stage (and its sub-stage) tells you where in the procedural journey the matter sits. Common stages in criminal matters include investigation, framing of charges, trial, arguments, and judgment; in civil matters they include service, written statements, evidence, arguments, and decree. The sub-stage narrows it further — for example “trial — examination of witnesses” versus “trial — final arguments”.

The status line is the headline answer to “is this case over?” and typically reads one of:

• Pending / Not Disposed: the case is still live before the court.
• Disposed / Judgement: the matter has been decided, with a final order or judgment.
• Transferred: the matter has been moved to another court, and the record now points elsewhere.
• Abated / Withdrawn / Dismissed as not pressed: the matter ended without a decision on the merits.
• Appealed: the decision was challenged in a higher forum.

This is the single field that verification consumers care about most. A pending criminal matter implies ongoing exposure; a disposed one still deserves review of the outcome (acquittal versus conviction matters enormously). How to read an Indian court case record responsibly means never reading “disposed” as automatically clean — read the judgment and the disposition to see what actually happened.

Orders, judgments and recent listings

Most systems also expose the orders — the list of orders or directions passed at each hearing — and the judgment where the matter is decided. Recent listings show which dates the case was called up before the bench, which tells you how active the matter is.

For verification, the value hierarchy is:

1. The final disposition — convict/acquit, decree, dismissal.
2. The nature of the dispute — what the case is actually about (fraud, recovery, matrimonial, offence category).
3. The currency — is it pending, recent, or decades old?

Do not try to be a lawyer. Your job is to extract the facts the record states, and if the case is material but unclear, escalate it for a legal review rather than interpreting the order yourself.

Does this record belong to the person you are checking?

The most valuable question in how to read an Indian court case record is identity matching. A court record that merely shares a common name is not a match. Confirm a record belongs to your subject by checking as many of the following as the record and your inputs allow:

• Full name: first name, middle name and surname, exactly as they appear, allowing for initials and common spelling variants.
• Father’s name / parent’s name: courts record the party’s parentage where available; this is the single strongest disambiguator on a court record.
• Date of birth: where present in the record, a precise match on DOB is highly probative.
• Address: partial or full address can corroborate identity.
• CNR number: the Case Number Record number is the unique identifier for a case in the eCourts system — if you have it, use it directly.
• Case number and court: the combination of case number, court and registration date should line up.
• Dates: filing/registration dates consistent with the relevant period of the subject’s activity.

If the record lacks a father’s name or DOB and relies only on a common name, treat it as a possible match only, not a confirmed one. A mismatch on any strong identifier (father’s name or DOB) is usually enough to reject the match. This is exactly the kind of reasoning that turns raw keyword search results into defensible verification decisions.

How NeevLegal normalises and summarises these fields

Tools like NeevLegal exist because reading raw court data reliably is hard and error-prone at scale. NeevLegal is an Indian court record verification API for BGV/HR, lending/fintech, insurance and compliance teams. It returns structured data on criminal and civil litigation across the Supreme Court, all High Courts and district courts, searchable by CNR, case number or party name.

NeevLegal helps a reviewer apply exactly the reading discipline described above. It does this by:

• Normalising party fields into consistent role labels, so the petitioner/respondent/plaintiff/defendant/appellant/accused variety collapses into a clean schema.
• Standardising case type codes into a consistent taxable vocabulary, so you are not tripped up by court-to-court abbreviations.
• Summarising stage, status and disposition into a reviewable summary, and flagging pending, disposed, transferred and appealed states.
• Adding a human-verified layer that checks the record against the underlying court sources, so a reviewer gets corroboration rather than raw, possibly stale, scrapes.
• Attaching the identifiers — CNR, case number, court, dates, and party details — that let your reviewer decide whether a record actually belongs to the subject.

The point is not that software replaces analytical judgement. It is that when you can read the record’s fields yourself, you can quickly judge whether the structured output of an API genuinely reflects what the official record says — and that is the combination that makes screening decisions defensible.

Practical checklist before you rely on a record

• Have I recorded the cause title and all party names?
• Have I confirmed the party role (petitioner/respondent/appellant/accused)?
• Have I recorded the case type code and do I understand what it implies?
• Have I anchored the case number, court, and registration date?
• Have I read the stage, sub-stage, status and disposition?
• Have I verified identity on name + father’s name + DOB + CNR/case number + court + dates?
• Is the match confirmed, or only possible?
• Have I checked the outcome (acquittal vs. conviction, decree vs. dismissal)?

Reading an Indian court case record is a skill, not a talent. Master the vocabulary — the case types, the party roles, the dates, the stages and the status fields — and you will stop guessing and start verifying. Use the official eCourts portal, the Supreme Court’s website, and the NeevLegal blog to keep sharpening that skill, and lean on normalised, human-verified data whenever a hiring, lending or compliance decision depends on the answer.