Skip to content

Judge and Court Intelligence

Coming Soon

Use the Docket Navigator MCP to understand how a judge or court has handled a recurring patent-litigation issue, compare procedural postures, and verify the decisions behind the statistics.

Understand how a judge handles motions to stay pending IPR

Section titled “Understand how a judge handles motions to stay pending IPR”

Use Docket Navigator through your organization’s AI provider platform to understand how a judge has handled a recurring patent-litigation issue, compare different procedural postures, review the records behind the statistics, and turn the research into something you can revisit or monitor.

For questions about judicial behavior, the value often comes from combining several layers of Docket Navigator data. A single percentage may be useful, but the fuller picture can include the type of motion, whether the PTAB had instituted review, whether the motion was contested or stipulated, the underlying decisions, and how the judge’s history compares with a court-wide benchmark.

Judge and Court Intelligence is useful when a case team needs to understand how a judge or court has handled a recurring patent-litigation question.

You can use it to ask about:

  • motion outcomes by type;
  • differences in outcomes based on procedural posture;
  • judge-level experience with a particular issue;
  • court-wide benchmarks;
  • timing to major litigation events;
  • prior claim constructions;
  • remedies awarded;
  • filing or decision trends over time; and
  • the individual decisions behind an aggregate statistic.

This workflow is especially useful when the answer depends on structured distinctions that would take time to assemble manually across many cases.

A litigator may use this research when advising a client about motion strategy, evaluating the significance of an assigned judge, or preparing for a case-team discussion.

Knowledge management, research, and library professionals can use the same workflow to build judge reference material, create comparison charts, and answer recurring questions from case teams.

Your AI provider platform can translate a natural-language question into the relevant Docket Navigator research, then combine the results into a cited explanation.

For judge analytics, that may involve structured data about:

  • judges and courts;
  • motion types and outcomes;
  • procedural posture;
  • decision dates;
  • PTAB activity connected to district-court litigation;
  • underlying orders and editorial annotations; and
  • saved searches and alerts.

The useful unit of analysis depends on the question. For example, a motion-outcome question should be based on coded motion decisions, while a litigation milestone only indicates that a defined stage or event occurred. Keeping those analytical objects distinct is essential to interpreting the result correctly.

Example: How Judge Gilstrap handles motions to stay pending IPR

Section titled “Example: How Judge Gilstrap handles motions to stay pending IPR”

Suppose a patent litigator is evaluating whether to seek a stay pending inter partes review in a case assigned to Judge James Rodney Gilstrap.

The attorney wants to know whether timing matters. In particular, the attorney wants to compare contested motions decided before PTAB institution with contested motions decided after institution, while keeping stipulated or agreed motions separate.

How has Judge Gilstrap handled motions to stay pending IPR? Break out contested motions before PTAB institution, contested motions after institution, and stipulated or agreed motions after institution. Show me the differences in percentages, explain what they suggest, and give me the Docket Navigator sources behind the numbers.

A request like this involves several distinctions that materially affect the answer.

The AI provider platform can use Docket Navigator to separate:

  • motions to stay pending IPR from other stay requests;
  • contested rulings from stipulated or agreed motions;
  • rulings issued before PTAB institution from those issued after institution; and
  • the aggregate percentages from the individual coded decision documents behind them.

That lets the user ask one strategic question while Docket Navigator supplies the structured patent-litigation data needed to answer it.

In the validated example, the research produced three all-time comparison groups:

PostureCoded rulings
Contested, pre-institution32
Contested, post-institution73
Stipulated or agreed, post-institution39

The stipulated or agreed post-institution group showed a 95% grant rate.

The pre-institution group was dominated by denials without prejudice. Twenty-six of the 32 coded rulings fell into that category, which is important context for interpreting the raw result. A denial without prejudice can reflect a court’s decision to defer the question until the PTAB’s institution decision rather than a definitive rejection of a stay.

The post-institution group produced a different outcome pattern and gave the attorney a better basis for evaluating what happens once PTAB institution is no longer uncertain.

For a client-facing presentation, the same results can be rendered as a percentage chart with the three procedural postures side by side. The chart is most useful when the underlying counts remain visible or readily available, because the denominator matters as much as the percentage.

Aggregate results should remain traceable to the underlying Docket Navigator records.

A useful follow-up is:

Show me the pre-institution denials without prejudice. Which decisions best illustrate why Judge Gilstrap deferred the stay question?

The AI provider platform can use the Docket Navigator information associated with those orders to identify representative decisions, summarize the coded result, and direct you to the underlying Docket Navigator source.

You can continue the same analysis with questions such as:

Which post-institution denials are most representative?

Are there post-institution grants that cut against the overall pattern?

How does Judge Gilstrap compare with the Eastern District of Texas overall?

Put the three Gilstrap postures into a client-ready chart and keep the sample sizes with the percentages.

These follow-ups stay within the same assignment while moving between aggregate analytics, contrary examples, source verification, and presentation.

Outcomes of motions to stay pending IPR before Judge GilstrapStacked bar chart comparing outcomes across three postures. Contested pre-institution: 3 percent granted, 81 percent denied without prejudice, 16 percent denied (32 coded rulings). Contested post-institution: 22 percent granted, 11 percent denied without prejudice, 56 percent denied, 11 percent other (73 coded rulings). Stipulated post-institution: 95 percent granted (39 coded rulings).GrantedDenied without prejudiceDeniedOtherContested,pre-institutionContested,post-institutionStipulated,post-institution0%25%50%75%100%
Judge Gilstrap, E.D. Tex. All coded rulings on motions to stay pending inter partes review. Percentages of coded decision documents within each posture.

You can ask your AI provider platform to save the research to a Docket Navigator binder so you can return to it and review current results that match the saved search criteria.

For example:

Save this research to a Docket Navigator binder so I can come back to it.

A research binder can preserve the different comparison views as separate tabs, such as pre-institution rulings, post-institution rulings, stipulated matters, and court-wide benchmarks.

Binder results update when new Docket Navigator data matches the saved search criteria.

You can also ask for ongoing monitoring:

Set up monitoring so I get notified when Judge Gilstrap issues a new ruling on a motion to stay pending IPR. Weekly is fine.

For monitoring, a focused binder can be useful when the broader research binder also contains comparison tabs that would generate unrelated activity. The alert can then watch the narrower judge-and-motion search while the broader binder remains available for analysis.

Creating a binder or alert changes your Docket Navigator account, so your AI provider platform should perform those actions only when you ask.

Tips for better Judge and Court Intelligence research

Section titled “Tips for better Judge and Court Intelligence research”
  • Name the judge or court and the specific litigation question you care about.
  • State the procedural distinction if it matters, such as pre-institution versus post-institution.
  • Ask for the denominator behind a percentage.
  • Keep stipulated or agreed matters separate when they would distort a contested-motion comparison.
  • Ask for contrary examples when an aggregate statistic looks strong.
  • Ask for court-wide or peer comparisons only when they use a comparable population and time basis.
  • Ask the AI provider platform to show the records behind the chart before using it in client-facing work.

Before relying on judge analytics in work product or client advice:

  1. Review the cited Docket Navigator sources behind the important statistics.
  2. Confirm that the motion category, procedural posture, date period, and comparison population match the question you asked.
  3. Check the numerator and denominator behind any percentage.
  4. Review representative decisions when the strategic conclusion depends on how the court applied the rule in practice.
  5. Remember that coded decision-document counts may not always equal the number of distinct motions if more than one decision document addresses the same motion.

The AI provider platform generates the analysis and presentation. Docket Navigator provides the structured data and source material that let you test that analysis.

Use the attached Judge and Court Intelligence skill

Section titled “Use the attached Judge and Court Intelligence skill”

The attached Judge and Court Intelligence skill helps your organization’s AI provider platform perform this workflow more consistently.

It can help the platform:

  • recognize judge- and court-analysis assignments;
  • choose the Docket Navigator data that matches the strategic question;
  • preserve distinctions among motion outcomes, procedural posture, and litigation milestones;
  • choose appropriate comparison populations;
  • include denominators and time periods with statistics;
  • identify when a chart communicates the comparison clearly;
  • preserve source support for important factual claims;
  • refine the same analysis through follow-up questions; and
  • move from one-time research into a user-requested binder or alert.

The skill supports a more consistent research process, while the user remains responsible for reviewing important results and the underlying sources.

Ask what the judge actually does, then use Docket Navigator to inspect the data and decisions behind the answer.