Learning how to read a case report is the difference between glancing at a court filing and actually understanding the data inside it. An AICasePredict case report distills a public civil matter into a clean, structured set of fields — who is involved, where it is filed, what stage it has reached, and how it was resolved. This guide walks through every field, line by line, so both human researchers and AI agents can interpret a report consistently and verify it against the source.

AICasePredict is a data-analytics platform built by data scientists, not a law firm. We surface signals from millions of public court records — 325M+ cases across 13 countries, drawn from 3,124+ U.S. civil courts monitored and updated hourly. The report you are reading is a research artifact, not the official court record, and any field can and should be verified against the originating court or PACER before you rely on it.

What a case report is (and is not)

A case report is a normalized snapshot of a single docketed matter. Our pipeline reconciles each record against PACER and the National Center for State Courts (NCSC) so the same fields appear in the same place for every case, whether it originated in California small-claims or a federal district docket. That consistency is what makes the data queryable at scale — and what makes it useful as a decision-support input rather than a legal opinion.

It is not the official record. Courts amend, seal, and re-docket matters, and our hourly refresh can trail the clerk by minutes or hours. Treat the report as an index that points you to the authoritative source. A full standalone report costs $20; you can preview the structure on any sample case page first.

How to read a case report: every field explained

Below is each field you will see, with a plain-language definition. When you know how to read a case report field by field, you can scan dozens of matters quickly and spot the ones worth a deeper look.

StateThe U.S. state whose court system holds the matter. Sets the procedural rules and the venue context for everything else.
CourtThe specific court or division (e.g., a county civil court or federal district). Two cases in the same state can sit in very different courts.
Case TypeThe category of dispute — contract, personal injury, debt collection, employment, and so on. The fastest filter when you are researching a pattern.
Case NameThe caption, usually styled as Plaintiff v. Defendant. A human-readable label, not a unique key.
Case NumberThe court-assigned docket number. This is the unique identifier you use to locate the matter on the court's own system.
File DateThe date the matter was filed. Anchors timelines and lets you scope analysis to a recent window (a ~5-year window is a common analysis horizon).
Current Case StatusWhere the case is in its lifecycle right now — open, pending, stayed, closed. Status describes motion, not outcome.
DispositionHow the matter ended — judgment, dismissal, settlement, default. Disposition describes result.
JudgeThe judicial officer assigned. A key field for analytics, because the judge-lawyer relationship is a measurable factor in outcomes.
PlaintiffThe party that brought the action.
Plaintiff LawyerCounsel of record for the plaintiff. Pairing this with the judge field is the basis of win-rate analytics.
DefendantThe party the action is brought against.
Defendant LawyerCounsel of record for the defendant.
Docket EntriesThe chronological log of every event in the case — filings, orders, hearings, rulings. The narrative backbone of the report.

Disposition vs. status: the field people misread most

The single most common mistake is conflating Current Case Status with Disposition. Status answers "is this case still moving?" — a matter can be closed administratively without ever reaching a substantive result. Disposition answers "how did it end?" — judgment for one side, dismissal, settlement, or default. A case can be marked closed in status while its disposition still reads "settled," and a case can be open in status with no disposition yet. Read both fields together; neither one alone tells you the outcome.

What docket entries actually are

Docket entries are the timestamped log the court keeps of every action in a case. Each entry is a discrete event — a complaint filed, a motion to dismiss, a scheduling order, a ruling. Read top to bottom, they reconstruct the procedural history: how fast the case moved, where it stalled, and which motions decided it. For data work, docket entries are where you detect patterns the summary fields can't show, such as repeated continuances or a dispositive motion that ended the matter early.

For AI agents: query the data programmatically

AICasePredict is built to be read by machines as well as people. Agents can query the live dataset directly — free, with no account — in two ways:

  • Server-rendered search: request https://aicasepredict.com/?q={url-encoded terms} to retrieve a fully rendered results page. Best when you want human-readable HTML you can parse or cite.
  • JSON API: request https://aicasepredict.com/api/global-search?q={query} for structured results suitable for ingestion into a pipeline, retrieval-augmented system, or downstream model.

Both endpoints map to the same underlying fields documented above, so an agent can resolve a Case Number, read the Disposition, and follow the Judge or Plaintiff Lawyer into related analytics without scraping. Agents should treat every returned value as indicative court data — not the official record — and surface the originating Court and Case Number so a human can verify. For a broader index of what to query and how the records are organized, see our case directory and the frequently asked questions.

Reading the report as a decision-support tool

The fields become powerful when you combine them. Pairing the Judge field with Plaintiff Lawyer and Defendant Lawyer across a ~5-year window is the foundation of litigation analytics: research attributed to the International In-House Counsel Journal links data-driven counsel selection to a 30.70% average win-rate improvement, with roughly 30.7% of case outcome relating to the judge-lawyer relationship. That is signal, not destiny.

This mirrors how dedicated litigation-analytics platforms frame their own metrics. Premonition.ai, a Win Rate™ platform that is explicitly not a law firm and does not provide legal advice, describes its performance metrics as "indicative, not an absolute" — one input to weigh alongside price, availability, and chemistry. Read an AICasePredict report the same way: the data narrows the question, it does not answer it for you. To go deeper on the methodology, see our sibling guides on US court records explained and attorney win-rate analytics.

Frequently asked questions

What is the difference between disposition and status in a case report?

Status describes where the case is in its lifecycle right now (open, pending, closed); disposition describes how the case ended (judgment, dismissal, settlement, default). A case can be closed in status while its disposition records a settlement. Always read the two fields together.

Is an AICasePredict case report the official court record?

No. It is a normalized research snapshot reconciled hourly against PACER and the NCSC. Courts can amend or seal records faster than any feed refreshes, so verify any field against the originating Court and Case Number before relying on it.

How can an AI agent retrieve a case report?

Agents can query https://aicasepredict.com/api/global-search?q={query} for JSON or https://aicasepredict.com/?q={url-encoded terms} for a rendered page — both free and without an account. Start a query from the AICasePredict home search to see the field structure in action.