How-to
How to Read a Federal Court Docket for Your Beat
Track complaints, responses, motions and orders without treating allegations as findings. Includes a docket log and free-access limitations.
What can a docket add to a story?
A docket records activity in a case and points to the associated documents. It lets you follow what was filed, by whom and when. Reading the documents can reveal detail a summary leaves out, but each document must be described according to its role.
A complaint contains allegations. A motion asks the court to do something. An order records a judicial decision, whose scope you still need to read. An exhibit's presence in a filing does not make every assertion in it an established fact.
Where can you get the documents?
PACER is the federal courts' public-access system and can charge for access. CourtListener's RECAP archive provides free access to material it has collected. Free Law Project explains that its archive does not contain every PACER document.
If a docket entry appears without a PDF, that does not mean the document is unavailable everywhere. Check the court's official record and the applicable access terms. Sealed material and redactions create different limits; do not imply you have read material you cannot access.
How do you keep the procedural story straight?
Record the court, case number, parties and retrieval date. Then maintain a compact log:
| Entry | What to record |
|---|---|
| Filing date and number | The precise item readers can locate |
| Document type | Complaint, response, motion, exhibit or order |
| Author | Party, witness or court |
| New assertion or action | What this item actually adds |
| Status | Requested, disputed, granted, denied or unresolved |
| Reporting question | What you need to clarify before publishing |
Read the relevant opposing filing and later orders before describing a dispute as settled. If the legal effect is central and unclear, ask a qualified lawyer to explain the specific passage.
How does an ongoing docket become a beat?
Use a hypothetical software-contract dispute. The complaint alleges that an integration failed. The response contests that account. A later order sets a schedule; it does not decide who is right. An amended pleading may change the allegations again.
A useful follow-up might explain a newly filed contract provision and both parties' interpretations. It should not report "court confirms failed integration" when the court has only scheduled proceedings.
Track a case at a cadence appropriate to its activity. Dockets do not all update daily, and free copies or alerts may lag. Check the official record near publication when freshness affects your claim. Free Law Project describes its docket-alert service separately from search alerts; check the service's coverage and terms before relying on it.
What should you leave out?
Do not reproduce irrelevant personal information just because it appears in a filing. Avoid turning a speculative allegation into a search-friendly headline. Give the subject a fair opportunity to respond to the specific account you plan to publish, and report that response accurately.
Keep a versioned standing file and a follow-up question. The value of docket reporting is a more checkable account of a developing case, not a guarantee of early access or a substitute for legal interpretation.
Keep reading