---
title: "Party and Attorney Track Record"
description: "Use the Docket Navigator MCP to assemble a cross-case patent litigation history for a party, law firm, or attorney, then verify the decisions, patents, and outcomes behind it."
sidebar:
badge:
text: "Coming Soon"
variant: note
---
import PatentForumSwimlaneChart from '../../../../components/PatentForumSwimlaneChart.astro';
import SkillDownload from '../../../../components/SkillDownload.astro';
## Research a party, firm, or attorney's patent litigation track record
Use Docket Navigator through your organization's AI provider platform to assemble a cross-case view of a party, law firm, or individual attorney in patent litigation.
This workflow is useful when a case team needs to understand the history behind an opponent: who they have faced, which patents have been asserted or challenged, what courts and the PTAB have decided, where the entity has won or lost, what remedies have been awarded, and how that history has developed over time.
The value comes from connecting decisions, parties, attorneys, firms, patents, outcomes, remedies, and proceedings across matters that would otherwise need to be reconstructed one docket at a time.
:::note
**Important:** The Docket Navigator MCP connects Docket Navigator data and research tools to your organization's AI provider platform. The AI platform you use interprets your request, decides how to use those tools, and generates the response you see. Results may therefore vary depending on the AI provider and model your organization uses. Review important results for factual, doctrinal, and procedural relevance, and use the Docket Navigator citations and links to verify the underlying source material.
:::
## When to use this workflow
Party and Attorney Track Record research is useful when your strategy depends on understanding what has happened across an entity's prior patent cases.
You can use it to investigate:
- a repeat patentee or Patent Challenger;
- a competitor with a history of patent litigation;
- a law firm that regularly appears for one side of patent cases;
- an individual attorney with a substantial body of relevant matters;
- patents that recur across district-court and PTAB proceedings;
- motion types or legal issues that recur in an opponent's cases;
- Patent Determinations and Remedies associated with the entity's matters;
- case and filing activity over time; and
- representative wins, losses, settlements, and other outcomes that deserve closer review.
The workflow is especially useful when the question spans multiple cases or proceedings and the important facts are distributed across different Docket Navigator profiles and structured data sets.
## Who can use this workflow
The primary user is a litigator managing an active matter against a repeat player.
A partner or senior associate might use this research before recommending strategy against a patentee that has asserted the same patents against several defendants. A mid-level associate might use it to identify the decisions the team should read first or to trace how a particular patent has fared across district-court and PTAB proceedings.
In-house counsel can use the same workflow to understand litigation involving their company, a recurring adversary, or a group of patents that has surfaced repeatedly in their industry.
Research, knowledge management, and library professionals can also use it to assemble a structured history for a case team without manually searching each matter separately.
## How it works
Your AI provider platform can translate a natural-language request into Docket Navigator research across the relevant party, attorney, firm, case, patent, decision, and outcome data.
Depending on the assignment, the analysis may draw on:
- party, firm, attorney, case, and patent profiles;
- district-court and PTAB proceedings;
- asserted or challenged patents;
- motion and decision outcomes;
- hand-coded legal issues;
- Patent Determinations;
- Remedies;
- Party, Firm, and Case Outcomes;
- claim constructions;
- filing and termination dates; and
- source documents and Docket Navigator links.
The analytical object matters. A motion outcome answers a different question from a Litigation Milestone. A Patent Determination records a determination about infringement, validity or patentability, or enforceability. A Remedy records relief awarded. Party, Firm, and Case Outcomes summarize the resolution of Accusations at a broader level.
Keeping those categories distinct makes the resulting track record more useful.
The scope also matters for attorney and firm research. Docket Navigator can show what courts decided in cases where a lawyer or firm appeared. That does not establish which attorney made a particular argument or caused a particular result unless the underlying source supports that attribution.
## Example: Assess VB Assets before recommending a strategy for SoundHound
Suppose you represent SoundHound AI in a Delaware patent case brought by VB Assets.
You know VB Assets previously obtained a jury verdict against Amazon involving Alexa, but the headline result does not tell you how the asserted patents have fared across other proceedings, where VB Assets has lost, what happened at the PTAB, or which decisions matter most to the current defense.
### Example prompt
> I represent SoundHound AI. VB Assets sued us in Delaware over our voice assistant technology. I know they won a jury verdict against Amazon over Alexa, but I need the whole picture before we recommend a strategy.
>
> Walk me through VB Assets' patent litigation history: who they have sued and where, which patents they assert and how those patents have held up, what the courts and the PTAB have actually decided, what money has been awarded and whether it survived post-trial motions and appeal, and how their filing activity has changed over time. Tell me which decisions my team should read first, and be specific about where they have lost.
### What the MCP can help identify
A request like this requires several kinds of Docket Navigator research to be connected into one litigation history.
The AI provider platform can use Docket Navigator to identify:
- the relevant VB Assets party records and name variants;
- the district-court cases associated with the party;
- the patents asserted in those matters;
- PTAB challenges to those patents;
- Patent Determinations concerning infringement or patentability;
- Remedies entered in the district-court cases;
- the decisions associated with major wins and losses;
- changes in filing activity over time; and
- the source material behind the conclusions.
The user can begin with one broad assignment and then move into a specific patent, PTAB proceeding, damages order, or decision without rebuilding the research from the beginning.
## Build the track record across cases and proceedings
In the validated example, Docket Navigator research surfaced 18 asserted patents, 27 Patent Determinations, 11 Remedy rows, and 19 PTAB institution decisions associated with the VB Assets history reviewed in the scenario.
Those numbers are starting points for analysis rather than conclusions by themselves.
For example, the PTAB record showed 19 institution decisions. Two petitions were instituted and 17 were denied. The two instituted Amazon petitions produced different final outcomes: all challenged claims of one patent were found unpatentable, while the challenged claims of U.S. Patent No. 8,073,681 survived.
That distinction gives the case team a much more useful question than "Has VB Assets survived IPR?"
A natural follow-up is:
> Focus on the PTAB record. For every IPR filed against a VB Assets patent, tell me which patent it targeted, who petitioned, whether it was instituted, and what the Board finally decided. Separate the 2020 Amazon petitions from the 2025 Samsung petitions.
The same workflow can then trace one patent across proceedings:
> Take US 8,073,681, the patent that survived both the IPR and the trial. Trace it across every proceeding it has appeared in, and give me the four or five decisions my team should read before our response is due.
This lets the user move from an entity-level track record to a patent-specific litigation history while preserving the original assignment.
## Identify the losses behind the headline result
A useful opponent history should make adverse results easy to find.
In the Amazon litigation, one decision worth reading is *VB Assets, LLC v. Amazon.com Services LLC*, No. 19-1410 (D. Del. Sept. 30, 2024).
The post-trial decision matters because the jury's original infringement verdict did not remain intact as entered. The court granted judgment as a matter of law of noninfringement as to U.S. Patent No. 9,626,703 and reduced the damages reflected in the judgment by the amount attributed to that patent.
That makes the following verification request useful:
> You said the damages award was reduced after trial. Show me that order, tell me what the court actually granted and denied, and confirm the current figure and whether it is on appeal.
The important behavior is the move from a summarized track record back to the decision itself. The AI provider platform can use the Docket Navigator information associated with the matter to identify the relevant source, and the user can inspect the underlying order before relying on the characterization.
The same principle applies to PTAB outcomes, Patent Determinations, Remedies, and other results. A strong track record should show where the opponent succeeded, where it failed, and which source supports each important point.
## Refine or continue the work
Once the initial track record is assembled, keep refining the same assignment.
Useful follow-ups include:
> Show me only the decisions where VB Assets lost on infringement or patentability. Which ones are most relevant to the patents asserted against us?
> Separate merits-based PTAB denials from discretionary denials. I want to know where petitioners actually failed on the substance.
> Which asserted patents have been litigated the most, and what has happened to each of them?
> Show me the claim constructions for the patents asserted against SoundHound and flag any terms that were previously disputed.
> Which damages and royalty orders are distinct awards, and which records reflect the same award at different stages of the case?
> Create links to the decisions you think the team should read first.
These follow-ups let the analysis move among aggregate history, specific patents, contrary results, remedies, and source verification without losing the tracked entity.
## Save the research and monitor new activity
If the track record is likely to remain relevant throughout the matter, you can ask your AI provider platform to save focused 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 the VB Assets cases, PTAB proceedings, and key decision searches to a Docket Navigator binder so I can come back to them.
Binder results update when new Docket Navigator data matches the saved search criteria.
You can also ask for ongoing monitoring when appropriate:
> Set up weekly monitoring for new VB Assets patent cases and new decisions in the existing matters.
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 Party and Attorney Track Record research
- Name the party, firm, or attorney you want to track and explain why the history matters to the current case.
- State the role that matters when relevant, such as Patentee or Patent Challenger.
- Ask for both favorable and adverse results.
- Ask the platform to separate district-court outcomes from PTAB results.
- Ask for the patents behind the results when the same patents recur across proceedings.
- Be specific about whether you want motion decisions, Patent Determinations, Remedies, Party Outcomes, or a broader case history.
- Ask for a time period when recent behavior matters more than the entity's complete history.
- Ask the platform to identify name variants when you suspect the same entity may appear under more than one record.
- Ask for representative source decisions before relying on a generalized pattern.
## Verify important results
Before relying on a party, firm, or attorney track record in strategy or client advice:
1. Review the cited Docket Navigator source for each important win, loss, determination, or remedy.
2. Confirm that the party or client role is correct. A party's history as a Patentee should not be interpreted as if it were acting as a Patent Challenger.
3. Keep motion outcomes, Litigation Milestones, Patent Determinations, Remedies, and broader Party, Firm, or Case Outcomes separate.
4. Review the underlying orders before attributing a result to a particular attorney or firm. Docket Navigator's order-level data shows what the court decided in the matter, not which lawyer personally made a particular argument.
5. Check for name variants or related entities that may affect the population.
6. Do not add Remedy rows together without confirming that they represent distinct awards. The same relief can appear in more than one record as a case moves from verdict to post-trial orders and judgment.
7. Verify current appellate posture when finality matters. Docket Navigator's Case, Party, and Firm Outcomes reflect the original lower-court outcomes shown in the product and may not reflect later appellate changes.
The AI provider platform generates the analysis. Docket Navigator provides the structured patent litigation data and source material that let you evaluate it.
## Use the attached Party and Attorney Track Record skill
The attached **Party and Attorney Track Record skill** helps your organization's AI provider platform perform this workflow more consistently.
It can help the platform:
- recognize party-, firm-, and attorney-track-record assignments;
- identify the relevant entity and role;
- assemble the appropriate cross-case Docket Navigator research;
- preserve distinctions among motion outcomes, Patent Determinations, Remedies, and broader case outcomes;
- trace the litigation of patents across district-court and PTAB proceedings;
- identify meaningful favorable and adverse results;
- describe attorney and firm histories without unsupported argument attribution;
- preserve source support for important factual claims;
- refine the same opponent history 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.
## The key idea
**Build the opponent's track record from the decisions, patents, proceedings, and outcomes that shaped its prior cases, then use the underlying Docket Navigator sources to test every conclusion that matters.**