State Court Rules Are Now Live for California and Illinois

We have started adding state trial court rules to CourtRules.app. The first release focuses on California and Illinois, including Los Angeles Superior Court, Cook County Circuit Court, DuPage County, and Kane County.

This is not just a new set of holiday pages. The new coverage includes source-linked rules and filing guidance drawn from official court materials. The first California and Illinois import includes 57 official state-court sources and 1,000 structured rules.

What is new

The first state-court rule pages are now live for these courts:

• Los Angeles Superior Court rules and filing guidance
• Cook County Circuit Court rules
• DuPage County 18th Judicial Circuit rules
• Kane County 16th Judicial Circuit rules

These pages sit beside the court holiday pages, so a filing team can check both the procedural rule and the calendar that may move the deadline.

Why state courts are harder than federal courts

Federal court procedure has its own fragmentation problem, but at least the structure is recognizable: district rules, judge pages, standing orders, and CM/ECF procedures. State courts do not always publish information in those clean buckets.

Los Angeles Superior Court is a good example. A lawyer may need to know a court-wide e-filing order, a civil division instruction, a courthouse-specific practice, and a department-specific courtroom information sheet. Many judicial officers do not appear to have personal standing orders in the federal-court sense. The rule that matters may live at the court, division, or department layer instead.

That distinction matters for filing integrations. A filing portal can accept a document that still creates a courtroom problem. The useful question is not only whether the document can be filed electronically. It is also what this court, division, or department expects the filing to look like.

Los Angeles needs layered rules

In Los Angeles, the initial public coverage includes court-level and division-level material, plus courtroom information where official source documents were available. We are treating that as layered coverage rather than pretending every judge has a standalone rule page.

That is the right mental model for many state courts. The rule hierarchy often looks like this:

1. Statewide rules of court
2. Local court rules
3. Division or case-type instructions
4. Courthouse or department procedures
5. Judge-specific standing orders, when the court publishes them

If a judge has no published individual practice document, that does not mean there are no filing rules. It usually means the rule is inherited from a higher layer, or appears in a department-level source instead of a judge profile.

Illinois is more judge-order heavy

Illinois courts gave us a different pattern. Cook County has many standing orders and division-level materials, especially in Law, Chancery, Probate, Municipal, and Domestic Relations contexts. DuPage and Kane include local-rule materials that can be turned into structured filing guidance.

The practical problem is the same across states: lawyers and legal technology teams need court-specific filing expectations in a form that can be checked before submission. PDFs and HTML pages are useful source documents, but they are not enough when the job is to validate a filing workflow.

What this means for CourtRules.app

The state-court work changes the product in three ways.

First, court pages now need to support layered rule coverage. A state-court page can have court-wide rules, division instructions, department procedures, and judge-specific rules side by side.

Second, our API and MCP surfaces need to return the source layer clearly. If an agent or filing workflow asks about a Los Angeles department, the answer should identify whether the rule came from the court, the civil division, a department sheet, or a judge order.

Third, coverage needs to say what is missing. State court websites change shape often. Some publish PDFs, some publish dynamic pages, and some publish courtroom information through forms. A useful rule database should distinguish three states: no rule found, rule lives at another court layer, and source exists but has not been normalized yet.

This is the beginning of state-court coverage, not the finish line. The useful version is not a pile of PDFs. It is a rule set that tells you which court layer applies, where the rule came from, and what needs to be checked before the filing goes out.