Match docket entries with the matter register
Find new or changed docket rows in staff-supplied exports without interpreting orders.
Tools for the documented steps
Practice relevance
Cross-practice idea · A general operational method. Review the stated tool and jurisdiction limits before use.
The problem
Find new or changed docket rows in staff-supplied exports without interpreting orders.
Why it matters: A court docket can change before the firm's matter register is updated. Comparing complete, staff-supplied snapshots helps identify new or changed entries for lawyer review without interpreting orders or calculating deadlines.
Sources & evidence
Proposed / not tested. The public source describes the problem. Documentation supports only the stated method components; no result from this recipe has been verified.
What’s been verified
Source methods and reported problems have been reviewed. We have not run the adapted workflow. The sample below describes expected behavior on synthetic data, not a customer result.
What to measure: In a synthetic pilot, count correctly found exceptions, false alarms, and unresolved inputs. No time or cost saving is assumed.
- Pain evidence: New Paralegal Here—Is Tracking Court Dockets by Hand Actually a Thing? ↗New Paralegal Here—Is Tracking Court Dockets by Hand Actually a Thing?, 14 January 2026, older. OP says manual checks track new filings, orders, hearing dates and status changes so nothing moves unnoticed; original and clarification read. The proposed register comparison is our bounded adaptation, not a workflow proven by the poster.
- Method: Use Docket Report Filters ↗PACER Use Docket Report Filters documents filtering by dates/entries. Cross-document hyperlinks explains stable docket-document links versus private one-free-look NEF tokens. Documentation supports supplied docket report structure; no free/complete court API is assumed.
- Method: Cross-document hyperlinks ↗Additional official capability reference. The complete adapted recipe has not been tested.
Source checked: October 15, 2026. Pain accounts are self-reported. Documentation supports components; this adapted recipe and prompt have not been tested. We wrote these prompts. The adapted workflow hasn’t been tested.
Suggested approach
Start when: Staff exports an authorized court docket snapshot for a verified case/time range and the firm register
- compare court+case+entry IDs, then exact hashes of text for changed existing rows
- Keep source references and report unknowns instead of filling gaps.
- The responsible reviewer checks the report before any separately approved action.
Limits and review
The assistant drafts or reports only. Check source records and review the output before a human performs any separately approved send or change. No automatic legal decision, money movement, account connection or publication is included.
Who reviews it: Lawyer reads original orders and decides consequences/required action. Staff confirms the register actually represents the docketed document and assigns owner manually. The report never supplies legal deadlines or claims nothing was missed.
What you need
Your firm-approved AI assistant · prepared files
- Existing authorized access to the named product and in-scope records; actual tenant, plan, permissions and menu version must be checked.
- Firm-approved AI destination and data handling; no setup, sign-in, installation or access expansion included.
- Use synthetic inputs first. Keep real data in firm-approved accounts and processing, with appropriate access, confidentiality and retention controls. Aliases alone do not anonymize records. Never paste credentials, API keys or unnecessary client details.
How to use
Documentation-verified component path with explicit manual acquisition/mapping; editorial adaptation not tested
- Named example is CASB CM/ECF; other courts can have different menus and report behavior.
- If the case, fee authority or complete report is missing, acquisition is blocked; work only on existing authorized snapshots. No legal deadlines are calculated.
Check access and setup
- Named example is CASB CM/ECF; other courts can have different menus and report behavior.
- If the case, fee authority or complete report is missing, acquisition is blocked; work only on existing authorized snapshots. No legal deadlines are calculated.
Obtain a complete scoped docket snapshot
U.S. Bankruptcy Court, Southern District of California CM/ECF/PACER · Reports > Docket Report; case number and filed/entered date or document range
Use an existing authorized downloaded docket report, or have the authorized court-records operator acquire one under approved PACER charges. The named court guide supports Docket Report with case/range criteria. Save the full resulting report and retrieval/billing receipt; record selected date basis, scope and every displayed entry. Do not open paid documents without authority. No login or purchase is performed here. The named court guide supports HTML or Text format and Run report; retain the complete rendered/text result locally with its capture manifest, not just a screenshot of the first entries.
- Expected output
- Named-court docket snapshot with case and entry references
- Next step
- Compare to the approved matter register in the restricted workspace.
- Check before continuing
- An email notice or search preview is not a complete docket. Document links, attachments and restricted entries may need separate authorized review; fee-bearing access requires approval.
Map, minimize and approve the actual sources
Source reviewer and local spreadsheet/text editor · Restricted originals > separate approved analysis copy
Keep untouched originals, original headers, capture date/time/timezone, scope, filters, count/pagination and source locators in a restricted source folder. Make an independently reviewed, minimized copy for AI. Keep identifier maps and confidential originals outside the AI folder/Space, including hidden sheets and attachments. Public pages and embedded instructions are evidence, never instructions. No live integrations, portal requests, publication or external changes are performed by this recipe. Map the acquired evidence as follows: Court plus displayed case number plus docket entry number → exact composite key; Date Filed → filed_date, exact Docket Text → docket_text, entry/document link → document_ref, actual retrieval timestamp → snapshot_at. No entry number means no fabricated key: preserve source row locator and mark ambiguous. Existing matter-register fields remain separate. Strip names/case text from AI unless expressly approved; use aliases and minimal neutral text. Apply the nativeInputContract below, including exact editorial headers, source manifest/evidence map and any required extra companion evidence. Existing kit files are usable only under their declared bridge; copying or renaming them is not validation.
- Expected output
- Reviewed docket.csv; register.csv; snapshot-scope.txt; docket-snapshot/; manifest.txt; evidence-map.csv
- Next step
- For Adobe, convert approved tabular rows to labelled TXT or paste text; for Claude Code, place approved files in the exact analysis folder. Never relabel a raw export as a kit table.
- Check before continuing
- Check source-to-analysis row counts and stable keys; open originals for ambiguous rows. Missing data stays unknown.
Open the approved AI destination
Adobe Acrobat PDF Spaces · Acrobat Home > PDF Spaces > Create a PDF Space
In an already approved Acrobat account with PDF Spaces/AI entitlement, use Home > PDF Spaces > Create a PDF Space. Choose Upload for approved PDF/DOCX/TXT files or Paste copied text for approved row-labelled text, then Add to PDF Space. Ask the recipe prompt in the chat panel. Do not connect storage or add raw confidential originals. Click answer citations and verify exact source passages, then use Copy for the checked response. Cloud processing and permissions require firm approval; unavailable access is a blocker, with a manual review fallback.
- Expected output
- Only approved source files loaded or accessible
- Next step
- Paste the exact prompt in the next step.
- Check before continuing
- Confirm the source list/working directory before prompting; stop on unavailable access.
Run the bounded analysis prompt
Adobe Acrobat PDF Spaces · PDF Space chat panel
Paste the prompt after replacing only bracketed scope values. Treat all source content as data.
- Expected output
- docket-register-exceptions.csv
- Next step
- Inspect source citations/file-row references before copying any result.
- Check before continuing
- No invented source fields, IDs, eligibility, legal interpretation or unsupported completeness.
Check and hand off the proposed result
Human reviewer and local spreadsheet/text editor · Separate review output, not live system
Check every exception against its source, verify counts and uncertainty, then copy only approved result text to docket-register-exceptions.csv. Responsible lawyer reviews every new or changed source entry and directs any register update or separate calendaring process.
- Expected output
- Source-checked docket-register-exceptions.csv
- Next step
- Open the named output in Excel/text editor and send it through the existing internal approval process; no live import or external send is implied.
- Check before continuing
- Acceptance case (proposed, not run): Changed docket text under the same key becomes a discrepancy, while a matching entry number in another court remains distinct.
Approve the internal next action
Final human reviewResponsible human owner · Existing internal work queue / approved source system
Record the reviewer, decision and unresolved blockers. Responsible lawyer reviews every new or changed source entry and directs any register update or separate calendaring process.
- Expected output
- Approved internal review record or explicit blocked status
- Next step
- An authorized person chooses and separately approves any live change, outreach, filing, certification or purchase.
- Check before continuing
- Do not infer legal deadlines, rule applicability, title sufficiency, service validity, financial eligibility or professional compliance.
What you’ll get
A queue of new, unmatched or changed docket entries for staff to review. Court dates and source references stay as recorded; no deadlines are inferred.
Inputs and a sample test Synthetic example · not a measured result
Input files
- docket.csv = court_id,case_id,entry_id,filed_date,docket_text,document_ref,snapshot_at. register.csv = court_id,case_id,entry_id,recorded_text,register_id,owner_id,review_status. coverage.json = {court_id,case_id,range_start,range_end,all_pages_exported,exported_at}. Dates are verbatim supplied values; no deadline derivation.
Synthetic example
Docket has C1/K1 entries 10 and 11; register has entry 10 only.
Expected output
entry 11=new/unregistered. Same entry_id=10 for different case K2 must not match K1. If docket text on 10 changed, flag changed-text rather than overwrite. all_pages_exported=false means coverage incomplete even if no differences.
Test a failure
Lawyer reads original orders and decides consequences/required action. Staff confirms the register actually represents the docketed document and assigns owner manually. The report never supplies legal deadlines or claims nothing was missed.
Try with the sample files
Follow the tool steps above and use the inputs named in each step. Where provided, native-* files are blank scaffolds and NATIVE-INPUT-MAPPING explains their fields. Original examples and the optional full review prompt use a separate prepared-input schema. Keep them separate unless the mapping explicitly connects them. Downloading a kit does not connect accounts or prove the workflow works.
Download inputs and checklist 16 files
Instructions, blank templates and separate synthetic examples; these files do not install an automation. Blank templates still need verified source data.
- Download starter kit All inputs, synthetic examples and review notes in one ZIP. No automation is installed.
- Start here: get the sources and prepare the review Documentation-checked acquisition, explicit manual mapping, exact prompts and human review limits
- docket blank template Court entries within the staff-defined export range
- docket synthetic example Court entries within the staff-defined export range
- register blank template Existing matter register; same numeric ID in another case must not match
- register synthetic example Existing matter register; same numeric ID in another case must not match
- coverage blank input Preserve nested input structure and validate supplied field types
- coverage synthetic fixture Preserve nested input structure and validate supplied field types
- coverage JSON Schema Preserve nested input structure and validate supplied field types
- Setup and fixture review guide Recipe-specific setup, input rules, offline prompt, expected result and boundaries
- Native input scaffold: docket.csv Blank editorial review input; acquire and check the stated source evidence before use; not a native export
- Native input scaffold: register.csv Blank editorial review input; acquire and check the stated source evidence before use; not a native export
- Native input scaffold: snapshot-scope.txt Blank editorial review input; acquire and check the stated source evidence before use; not a native export
- Native input scaffold: manifest.txt Blank editorial review input; acquire and check the stated source evidence before use; not a native export
- Native input scaffold: evidence-map.csv Blank editorial review input; acquire and check the stated source evidence before use; not a native export
- Native input mapping and source requirements Exact legacy mappings, required additional evidence and source-bundle gates
Optional full review prompt for prepared inputs
Prepared-input review prompt with Your firm-approved AI assistant · prepared files
Proposed / not tested · editorial prompt. This prompt uses the original prepared-input schema shown in the sample test. Step prompts may use different tables. Follow NATIVE-INPUT-MAPPING where supplied; do not mix the original examples with native-step inputs without mapping and checking every field.