Docket Report Monitoring

Coming Soon

Use the Docket Navigator MCP to turn the Patent Docket Report into a personalized morning brief based on the clients, matters, patents, judges, and firms your group tracks.

Create a personalized daily Docket Report brief

Use the Docket Navigator MCP to turn the Patent Docket Report into a personalized morning brief based on the clients, matters, patents, judges, firms, and other entities your group actually tracks.

Instead of reviewing every item in the report yourself, you can give your organization’s AI provider platform a watch list and ask it to identify the developments that touch those interests. The resulting brief can explain what happened, why the item matched, and where to verify the underlying Docket Navigator source.

If your AI provider platform supports persistent files and scheduled tasks, the same workflow can become a recurring morning routine. Your watch list remains the control surface, and the brief can be regenerated from the current Docket Report each day.

When to use this workflow

This workflow is useful when you already have a recurring set of patent litigation interests and want to know whether today’s Docket Report contains anything that deserves attention.

A watch list might include:

current or prospective clients;
opposing parties or repeat litigants;
patents from active or recently completed matters;
judges your group regularly appears before;
law firms or attorneys you track in patent cases; and
a short explanation of why each item matters to the group.

The strongest watch lists are based on identifiable entities. Legal issues, determinations, remedies, and other Docket Navigator coding can then help explain the significance of a matched item.

This makes the Docket Report useful as a trigger for action. A new filing may lead into a Case Pitch Builder workflow. A repeat plaintiff may lead into Party and Attorney Track Record research. A ruling in an active matter may lead directly to the underlying order and the filings that preceded it.

Who can use this workflow

A knowledge management, research, or library professional can use the workflow to triage the Docket Report for an entire practice group. The watch list can represent several attorneys’ clients and matters, while the resulting brief gives the group one consolidated view of what changed.

An attorney can use the same workflow for a smaller personal list of active matters, clients, patents, and judges.

The practical advantage is the same in both cases: the user maintains the interests that matter, and the AI provider platform uses Docket Navigator to check the day’s patent litigation activity against them.

How it works

A simple implementation starts with a spreadsheet in the AI provider platform’s working folder. Each row identifies something to track and explains why it is on the list.

For example:

Type	Name	Relationship	Priority	Active
Party	Uber Technologies, Inc.	Active defense client in the Yillio matter	High	Yes
Party	Samsung Electronics America, Inc.	Active defense client	High	Yes
Patent	8285696	Asserted against Uber in an active E.D. Tex. matter	High	Yes
Judge	Roy S. Payne	Assigned to an active client matter	Normal	Yes

The user can then ask the AI provider platform to review the current Patent Docket Report against that file.

Docket Navigator contributes the report itself and the structured patent litigation data behind it, including cases, parties, judges, patents, coded rulings, PTAB proceedings, determinations, remedies, annotations, profiles, and source links where available.

The AI provider platform uses that information to decide which report items match the watch list and to generate the brief.

Some matches require more than reading a report caption. A client may be hidden behind “et al,” or a ruling entry may omit a judge or counsel field. In those situations, the AI provider platform can use the Docket Navigator case record to verify whether a tracked entity is actually involved.

Example: Triage today’s report for a patent litigation group

In a validated production run, a knowledge management professional used a 30-row watch list to review the August 28, 2026 Patent Docket Report.

The report contained 28 entries across district court, PTAB, and ITC activity. Eight items matched the watch list.

Example prompt

There’s a spreadsheet in this folder, watchlist.xlsx, with the clients, opposing parties, patents, judges and firms my group tracks. The column next to each one says why we care about it. Go through today’s Docket Navigator patent Docket Report and tell me which of today’s activity touches anything on that list. I need the whole report covered, not a sample of it. For each thing you surface, tell me what happened, which row it matched and why that row is on my list, and give me the link back to Docket Navigator. Save it as a file in this folder.

What the MCP can help identify

The request combines several kinds of Docket Navigator information:

the full set of activity in the current Patent Docket Report;
party identities and roles;
asserted or challenged patent numbers;
judges associated with district court matters;
law firms or attorneys where the underlying case record provides them;
coded rulings and PTAB outcomes;
and Docket Navigator profiles and source records needed to verify a match.

The AI provider platform can then connect a report item to the specific watch-list row that caused it to surface.

See why an item matched

One of the most useful parts of this workflow is the ability to ask why something appeared in the brief.

During the validated run, the brief surfaced Vasu Holdings, LLC v. Samsung Electronics Co., Ltd. et al, No. 2:24-cv-00034-JRG-RSP (E.D. Tex. 2026), even though the user did not recognize the case from the report caption.

The user asked:

Where did the Vasu one come from? We’re not in that one and I don’t recognize the parties.

The answer traced the match to the watch-list row for Samsung Electronics America, Inc. The report caption showed Samsung Electronics Co., Ltd. “et al” and did not expose the watch-listed entity directly. Opening the Docket Navigator case record showed Samsung Electronics America as a separately captioned co-defendant.

That distinction matters. The AI provider platform could explain that the item matched because a tracked client was in the case, identify where that fact came from, and direct the user back to the Docket Navigator source.

This is also a useful verification pattern for firm, attorney, judge, or patent matches that are not obvious from the headline alone.

Move from the digest into the underlying litigation

A surfaced ruling can become the starting point for deeper research without requiring the user to reconstruct the case from scratch.

For example, the same August 28 run surfaced a claim construction order in Yillio, Inc. v. Uber Technologies, Inc., No. 2:25-cv-00533-JRG-RSP (E.D. Tex. Aug. 25, 2026).

The watch list matched:

Uber Technologies as an active client;
three asserted patents from the active matter;
Magistrate Judge Roy S. Payne; and
additional case information available through the underlying Docket Navigator record.

The brief explained that the order addressed indefiniteness challenges and construed the disputed term “advertising” as “promotional business information.” Docket Navigator recorded the three patents as not invalid in connection with those indefiniteness determinations. That is a specific determination tied to the issue before the court, not a general merits conclusion that the patents are valid.

A user can then ask:

Show me what led up to the Yillio ruling. What was filed and by whom.

The AI provider platform can use the Docket Navigator docket to reconstruct the filing sequence. In this example, the chain included the joint claim construction statement, opening brief, response, reply, Markman hearing, and the resulting claim construction order.

The filing sequence is useful even when the underlying motion papers or briefs are not available for the AI platform to read. Docket Navigator can identify filings by title, docket number, date, and filer, and the resulting order can be reviewed directly when available.

The AI platform should not attribute arguments to a motion or brief that it did not read. If a court order describes a party’s position, that description should be attributed to the order.

Update the watch list conversationally

The spreadsheet can also act as the control surface for future runs.

During testing, the user said:

Let’s stop tracking Katana Silicon, that matter settled last month. Update the sheet and run it again.

The row was deactivated rather than deleted, preserving the explanation of why the entity had originally been tracked. The AI provider platform then re-read the watch list and re-ran the matching logic against the same report.

This pattern also works in the other direction:

We’ve just taken on Acme Corp. Add them to the watch list and tell me if anything today touches them.

Keeping the reason for each row is important. It gives the AI provider platform useful context for explaining why a matched development deserves the user’s attention.

Schedule the morning brief

If your organization’s AI provider platform supports recurring tasks, you can ask it to run the workflow on a schedule after you are satisfied with the brief.

For example:

Run this every weekday morning at 8:30.

The scheduled task should continue to use today’s Docket Report and the current version of the watch list rather than a fixed historical date or a copy of the spreadsheet captured when the task was created.

Scheduling is a capability of the AI provider platform, not Docket Navigator. Complete any connector permission or workspace setup required by your provider before relying on an unattended run.

A useful persistent setup may include:

watchlist.xlsx for the entities and relationships you maintain;
a current daily brief;
an archive of prior briefs; and
the workflow skill or instructions used by the AI provider platform.

These files live in the AI provider platform’s workspace. The underlying report, case records, profiles, rulings, and other patent litigation data remain Docket Navigator sources.

Refine or continue the work

Useful follow-ups stay tied to the same monitoring assignment.

You might ask:

Why did this case match my list?

Which of today’s items would I have missed if I had only skimmed the report?

Show me what led up to this ruling. What was filed and by whom?

Stop tracking this party. The matter has resolved.

Add this new client to the watch list and check today’s report again.

Give me this plaintiff’s broader patent litigation track record.

Build the pitch foundation for this new case.

The last two prompts move naturally into Party and Attorney Track Record and Case Pitch Builder while preserving the case or party already identified in the digest.

Tips for better Docket Report monitoring

Keep the watch list focused on entities you can identify reliably. Parties, patent numbers, judges, firms, and attorneys give the AI provider platform a concrete basis for explaining a match.

Add a short relationship note to each row. “Active defense client,” “opposing party in current matter,” or “asserted patent in the Uber case” is more useful than a name alone.

Treat court or district preferences as scope when appropriate. Tracking an entire high-volume district as a relevance trigger can produce a large amount of contextual activity.

List patents by exact patent number when you want them matched. A related family member will not necessarily match unless it is separately listed or another tracked entity causes the matter to surface.

Deactivate rows when an interest ends instead of deleting them if you want to preserve why the entity had been tracked.

Ask why an unexpected item appeared. Provenance questions are one of the fastest ways to distinguish a genuine watch-list match from an overly broad inference.

Know the current coverage boundaries

The information available for matching can differ by report section and proceeding type.

For example:

a district court caption may abbreviate parties with “et al,” requiring the case record to confirm a client or adversary;
some district court report entries may not expose judge or counsel information directly;
PTAB and ITC case records may not provide the same counsel information available from district court docket headers;
a Schedule A defendant group may not expose every member needed to confirm a particular party match;
and exact patent-number tracking does not automatically expand to every member of a patent family.

Your AI provider platform should state these limitations when they materially affect a result.

Verify important results

Before relying on a development surfaced in the brief:

Confirm which watch-list row caused the match.
Open the cited Docket Navigator report, case, profile, or ruling.
Check that the underlying source supports the AI platform’s description of the event and the entity relationship.
Preserve distinctions among filings, rulings, PTAB petitions, institutions, preliminary guidance, final written decisions, determinations, and case outcomes.
Review the underlying order or source document before using a legal proposition in work product or client-facing advice.

The Docket Report is the starting point for the workflow. The source record determines what the development actually establishes.

Use the attached Patent Docket Watch skill

The attached Patent Docket Watch skill helps your organization’s AI provider platform perform this workflow more consistently.

It can help the platform:

recognize a Docket Report monitoring assignment;
read the watch list and preserve the reason each entity is tracked;
cover the full current report rather than a sample;
check supporting Docket Navigator case records when the report entry alone is not enough to resolve a match;
preserve party roles and Docket Navigator analytical distinctions;
explain the provenance of every surfaced item;
build a concise daily brief;
maintain the watch list as the user’s control surface;
reconstruct filing sequences when the Docket Navigator docket supports them; and
carry a surfaced case, party, or patent into the next research workflow.

The skill does not replace review of important results or the underlying Docket Navigator sources.

Download Claude Skill Learn more about Claude Skills

The key idea

Maintain the watch list once, then let each day’s Docket Report tell you what changed that matters to your group.