Judge and magistrate intelligence reports

A report on each federal district judge and magistrate judge: how motions were ruled on, how civil cases ended and how long they took, beside the district median. It also covers pro se cases, referrals, consent and reassignments.

The judge pages stay free. The reports open with an API key, issued by request.

The terms these reports use

A district judge presides over federal cases in one district. A magistrate judge works beside them: district judges refer parts of cases to a magistrate judge (discovery, settlement conferences, a report and recommendation on a motion, which the district judge then adopts, changes or rejects), and a magistrate judge presides over a whole civil case only when the parties consent. Pro se means a party has no lawyer. A case is removed when a defendant moves it from state court to federal court, and remanded when the federal court sends it back. Multidistrict litigation (MDL) gathers similar cases from many districts before one judge; those member cases are left out of these figures, because one MDL can close thousands of cases at once.

How many judges have a report

1,311 of the 2,654 judges and magistrate judges with a judge page (49 percent) have 20 or more rulings, the floor for a report: 1,071 of 1,817 district judges and 240 of 837 magistrate judges. The rulings behind them are 169,182 cases the court itself ended from January 2024 to June 2026, from the Federal Judicial Center (FJC) Integrated Database, and 2,106 rulings classified from public docket entries.

Rulings come from those two public records, not from PACER, the courts' paid records system. The docket entries are 3,696 entries on 2,068 dockets from the courts' daily case lists, dated November 2, 2026 to November 20, 2026. 23 judges and magistrate judges have 20 or more rulings in them, and their reports give the counts by motion; a rate needs 20 rulings that state the outcome. 99 percent of the civil cases on judges' dockets filed by the FJC's coverage date are found in the FJC records by case number.

What a report contains

SectionWhat it shows
Motion rulings by typeOrders read from the docket entries, by kind of motion and the outcome the entry states.
How cases endedCivil cases that ended in the window, by the Federal Judicial Center (FJC) disposition, against the district median.
Case-ending rulingsCases the court ended by its own act, the side a motion judgment was for, and removed cases sent back to state court.
Time to the end of a caseMedian days from filing to the end of the case, by how it ended, leaving out same-day closings.
Pro se casesCases where the plaintiff had no lawyer (pro se, as the FJC records it) beside cases where the plaintiff was represented.
Referrals and consentCivil cases referred to a magistrate judge, and cases a magistrate judge presided over with the parties' consent.
Reports and recommendationsOrders on a magistrate judge's report and recommendation, read from the docket entries.
ReassignmentsDocket entries that record a case being reassigned.
By yearCases ended, settled, dismissed and ended on a motion, and the median days to the end, each year since 2015.

Each figure is one statement with its count, its n, its window and the district median, as in the sample report: "100 of the 1,883 civil cases that ended from January 2024 to June 2026 settled (5 percent; district median 6 percent, 14 judges)." A figure with fewer than 20 cases behind it reads too few to rate. A report describes the record and makes no claim about a judge's leanings. See the sample report (Judge Jennifer L. Thurston), open to everyone.

From code

Each report is also JSON at its page address plus report.json, with the key in a header: curl -H "Authorization: Bearer rlk_..." https://repleader.net/judges/<judge>/intelligence/report.json. Each figure in it carries n, the window, the district median and the source dockets. The MCP server will offer the same report to a keyed session as three tools: judge_report, judge_motions and magistrate_report.

Request access

A person reads each request. We keep the request, your contact and a hash of your network address, only to answer it.