Legal Services Offshore blog
Run a docket change review before the weekly case meeting
A weekly docket review that compares court entries with the internal case record and gives the meeting a short, dated exception agenda.

Define the docket sources the review covers
A docket review starts with a written list of the sources the team will check, such as the court's electronic filing system, the internal calendar, and the matter file. Name the person who is allowed to add a source and the date a new source takes effect. If a court provides a public docket and a subscription service, record which one the reviewer uses for each matter. Do not blend sources without saying so, because a missing entry may simply mean the source was not checked. The list should be short enough to follow on a busy morning.
Record the matter identifier, court, case number, and the last date the docket was reviewed. If a matter is inactive or sealed, say so and give the reason the review still applies. A support worker needs a stable starting point, not a general instruction to check the docket. Include the review window and the time zone used for filing deadlines. The same fields should appear in every row so exceptions stand out.
Compare new entries with the internal record
For each new docket entry, compare the filing date, document title, filing party, and any stated deadline with the internal matter record. Record a match, a discrepancy, or an item that needs a lawyer's reading. Do not correct the internal calendar from a docket entry until the responsible person approves the change. If the entry is hard to classify, quote the docket text and route the question. The review is a comparison exercise, not a legal interpretation of the filing.
Pay attention to entries that change a date already recorded, such as an order granting an extension or a notice of rescheduling. Link the new entry to the earlier record so the history stays visible. If a document is listed but not yet available, record that state and check again on the next review. Do not assume an unavailable document has no effect. A dated note about the missing file is better than a silent gap in the log.
Give the weekly meeting a short exception agenda
The output of the review should be a short list of items that need a decision, not a full copy of the docket. Group exceptions by matter and state the question, the source, and the person who can answer it. Put the most time-sensitive items first and note the date of the next scheduled review. If there are no exceptions, say so in one line and record who checked. A clear empty result is still a result.
Send the agenda before the meeting and keep it with the meeting notes. During the meeting, record the decision and the owner for each item, including a decision to wait. If a new question appears, add it to the next review rather than resolving it from memory. The agenda should show that the docket was checked, not just that the team met. That distinction matters when a deadline is later questioned.
Keep a change log for the review process itself
Record changes to the docket sources, the review schedule, and the fields captured in the tracker. If a court changes its filing system, note the date and the first matter reviewed under the new system. If a reviewer changes, record the handoff and the last review completed. A process change can look like a missing entry if the log does not explain it. The change log protects the team from false conclusions about the record.
Review the change log at the start of each month and confirm that the written procedure still matches the work. If a source is unavailable, record the outage and the fallback used. Do not let a temporary workaround become an undocumented permanent process. Assign one owner to keep the log current and check it during the weekly review. A short, dated log is enough to make the process auditable.
Close the loop when a matter ends
When a matter closes, mark the docket review as complete and record the final review date. Keep the last docket check with the matter file so a successor can see what was known at closing. If the court can still issue orders after closing, note the period the team will continue to monitor. Do not assume that a closed matter has no further docket activity. The file should state the monitoring decision explicitly.
If the matter reopens, start a new review row rather than editing the closed one. Carry forward the court, case number, and last known review date, then check for entries during the gap. Record the person who reopened the file and the reason. The history should show both the closed state and the new activity without overwriting either. A clear closing record makes the next review faster and safer.
Use a short checklist for each review
A one-page checklist keeps a weekly docket review consistent when the person doing it changes. List the sources to open, the fields to compare, and the place to record an exception. Add the question that must go to a lawyer and the person who receives it. Keep the checklist beside the review log so a new reviewer can follow the same steps. The checklist should be short enough to use, not a policy manual that nobody opens.
Review the checklist at the end of each month and remove any step that no longer matches the work. If a new court source is added, update the checklist and record the effective date. If a step is consistently skipped, ask whether it is necessary or whether the instruction is unclear. A living checklist is more useful than a perfect one written once. The goal is a review that another person can repeat.
A supervised support lane can prepare the comparison and exception list while counsel keeps every interpretation and deadline decision. litigation document review support.
Sources
- U.S. Courts, electronic filing and CM/ECF
Used for the court-filing and docket-record context of the review.
- PACER, public access to court electronic records
Used for the distinction between public docket access and internal matter records.
- American Bar Association, Litigation Section
Used for general litigation practice context and supervision boundaries.