A regulatory docket is the official, numbered, continuously developing record of a proceeding before a commission. It contains the application or petition, notices, service list, motions, discovery materials where public, testimony, exhibits, procedural orders, hearing records, briefs, settlements, and final orders that together show what the case is, who is participating, what changed, and what the commission decided.
If a rate case is the substantive dispute, the docket is the record in which that dispute lives. This guide explains how to read and operate from that record. It is part of Statecraft’s Regulatory Operations learning path.
The case is the matter being adjudicated or investigated. The docket is its official record and administrative identity. The Illinois Commerce Commission makes the same distinction in its official e-Docket guidance: a case is the matter; a docket is the ongoing record plus details such as number, status, dates, assigned staff, reports, testimony, and exhibits.
The Anatomy of a Regulatory Docket
| Record element | What it tells you | Practitioner question |
|---|---|---|
| Application or petition | Requested action, legal basis, initial evidence, and proposed relief | What is actually being requested and why now? |
| Notice | Public notice, participation instructions, deadlines, and hearing information | Who must know, and what deadline starts the clock? |
| Motion or petition to intervene | Who seeks party status and the interest asserted | Which interests have entered the field? |
| Procedural order | Schedule, process, issue scope, and filing requirements | What changed operationally and who owns each date? |
| Discovery | Questions, data requests, objections, and supporting detail where public | Which assumptions are being tested? |
| Direct testimony | A party’s affirmative evidence and proposed findings | What position is this party asking the commission to adopt? |
| Rebuttal or surrebuttal | Responses to earlier testimony and narrowing disputes | Whose position moved, strengthened, or fractured? |
| Hearing record | Transcript, admitted exhibits, and examined testimony | What entered the formal evidentiary record? |
| Briefs | Arguments connecting evidence, law, and requested outcome | Which issues remain contested and how are they framed? |
| Settlement | Negotiated resolution among some or all parties | Who joined, who did not, and what tradeoffs produced agreement? |
| Final order | Commission findings, authorized relief, directives, and compliance obligations | What changed, what is precedential, and what happens next? |
Not every docket contains every document, and not every item is public. Confidential, proprietary, critical-infrastructure, or personally sensitive material may be withheld or filed under seal. A docket index can therefore show that a filing exists without exposing its full content. Treat the public record as authoritative for what it contains, not as proof that no additional protected record exists.
How to Read a Docket Chronologically
Start with the docket detail page: caption, docket number, filing date, case type, status, assigned administrative law judge or examiner, staff, and service list. Then read the initiating filing and the first procedural order. Those two documents usually establish the request and the operating clock. Without them, later filings are easy to misread.
Next, build a dated chronology rather than opening documents at random. Record each filing date, filing party, document type, issue affected, and practical consequence. A useful one-line summary is not “testimony filed.” It is “Consumer advocate recommends disallowing X and shifting Y costs; utility rebuttal due September 12.” That formulation preserves source, position, significance, and next trigger.
Finally, compare each important filing with what came before. Regulatory meaning often lives in the delta. Did a procedural order move the hearing? Did rebuttal abandon an adjustment? Did a settlement remove a party from active litigation? Did the final order adopt staff’s number but reject its reasoning? Reading chronologically converts a document repository into a story of movement.
How to Determine What Actually Changed
For each new entry, ask five questions: What is new? Who caused the change? Which issue or deadline does it affect? What decision or action follows? What is the source? The answers belong in a structured record linked back to the official filing. This is more reliable than copying a title into a spreadsheet and hoping someone remembers why it mattered.
Source: filing and date. Change: the new fact, position, deadline, or order. Impact: why it matters to the organization. Owner: the person accountable for response. Next action: the smallest concrete follow-through. Confidence: confirmed fact, interpretation, or working assumption.
Which Docket Filings Matter Most
Importance depends on the case and your role, but initiating filings, intervention deadlines, procedural orders, staff and consumer-advocate testimony, major intervenor testimony, settlement documents, recommended decisions, final orders, compliance filings, rehearing requests, and appeal notices deserve systematic review. Routine appearances, certificates of service, and duplicate administrative notices may require less analysis, but even a routine filing can reveal a new attorney, party, or service-list change.
The best filter is consequence, not document length. A two-page order changing a deadline may be more operationally important than 400 pages of testimony. A short intervention petition may introduce the party that changes the settlement. A notice of rehearing may keep an issue alive after the order. The practitioner’s question is always: what does this entry change?
What Government Affairs Tracks Versus Legal and Regulatory
| Function | Primary docket responsibility | Shared handoff |
|---|---|---|
| Legal | Procedural compliance, evidentiary record, privilege, legal arguments, hearing and appeal strategy | Flags restrictions, contested issues, and decisions that require stakeholder or executive context |
| Regulatory | Technical analysis, revenue requirement, testimony, discovery, tariffs, compliance filings | Explains substantive movement and the operational meaning of positions |
| Government affairs | Stakeholder map, issue posture, permitted engagement, coalition movement, briefings, commitments | Connects record movement to relationships, ownership, leadership decisions, and external context |
| Communications/community | Public narrative, community implications, customer explanation, hearing participation | Coordinates factual consistency, timing, audiences, and commitments |
These are working boundaries, not walls. The exact model varies by organization. What matters is explicit ownership and a shared record. Government affairs should not substitute its interpretation for counsel’s procedural advice or the regulatory team’s technical analysis. Legal and regulatory teams should not have to reconstruct stakeholder history from inboxes when the case turns toward settlement, public hearings, or executive attention.
Common Docket-Monitoring Mistakes
Watching the news instead of the source. Reporting is downstream of the docket. Saving documents without recording movement. A folder is not analysis. Tracking only the final deadline. Intervention, testimony, discovery, settlement, and compliance dates can be equally consequential. Failing to distinguish party position from commission action. Testimony is a request; an order is a decision. Using one jurisdiction’s terminology everywhere. Commission systems, numbering conventions, party rules, and document labels vary.
Another common mistake is treating alerts as completed work. An alert answers “something changed.” It does not answer who owns the response, which stakeholder is affected, what leadership needs to know, or whether a commitment was made. Monitoring becomes an operating capability only when every material change reaches a decision, owner, or documented “no action” conclusion.
Tracking One Commission Versus Twenty
One commission can often be monitored through its own email lists, daily filings, calendars, and docket searches. Multi-state coverage introduces a different problem: each commission uses different systems, labels, update rhythms, search quality, and document formats. The work scales by jurisdictional variation, not merely docket count. Teams need a commission-source map, a normalized proceeding model, jurisdiction-specific rules, and clear criteria for which events trigger human review.
RegulatorIndex is an evidence layer for discovering public utility commissions, commissioners, proceedings, hearings, and regulatory movement. The official commission docket remains the source of record. Statecraft’s role is different: preserve what the organization knows and is doing in response. This distinction mirrors the broader difference between tracking software and a government affairs CRM.
A Practical Docket-Monitoring Workflow
| Step | Output |
|---|---|
| 1. Register | Commission, docket ID, caption, case type, source URL, owners, status |
| 2. Baseline | Requested relief, initiating filing, governing schedule, known parties |
| 3. Monitor | Source-specific alerts plus scheduled review appropriate to materiality |
| 4. Triage | Material, informational, duplicate, administrative, or no-action classification |
| 5. Interpret | Change note with affected issue, position, deadline, and confidence |
| 6. Assign | Owner, next action, due date, dependencies, and escalation rule |
| 7. Brief | Audience-specific summary grounded in linked primary filings |
| 8. Close | Outcome, precedent, implementation obligations, and retained record |
For the complete operating method, continue to How to Track a Utility Rate Case. To understand the other actors, read What Is an Intervenor? and What Is a Public Utility Commission?. To evaluate the system that connects proceedings to stakeholders, interactions, and commitments, use the Government Affairs CRM Buyer’s Guide.
Michael-Christopher Warren is a government affairs practitioner and the founder of StatecraftCRM. He writes practical frameworks for how government affairs work actually gets done — from stakeholder relationships and institutional memory to executive briefings, strategy, and team operations.
Start Statecraft without a sales process.
Choose your plan and users, see the exact price, and start online.