Court rules as data: the official text, not memory

Filings are often sent back for reasons that have nothing to do with the argument: a missing certificate, the wrong caption, a companion document nobody knew was required, a word limit, a copy count. Each of those requirements is written down somewhere in the court's own rules. The engine's approach is to fetch that text, keep a receipt for it, and check the filing against it at more than one point, instead of relying on anyone's recollection of what a court usually wants.

Court rules are primary law, and the engine treats them that way; see rule text as primary law.

Court rules read before strategy

When the filing type is being chosen, the official rules for the filing court and for that filing type are fetched. An empty result, or a rule book that is only a list of links with no text behind it, is refused. The choice of filing is made with the rules in hand, not decided first and checked later.

• A model's memory is not the rule.
• A summary or a checklist is not the official text.
• An empty result means the book isn't loaded, never that no rule exists.
• A page of links is not a rule book.

If the official text isn't there, the engine says so in plain words and does not proceed. State and federal rule books are never mixed: using the wrong court system's book is treated as a fatal error in every phase that touches the rules.

Court rules read before drafting

After the strategy sign-off, the court-rules check runs again, and each format requirement the filing depends on is tied back to the official text. The binding outline for the filing is regenerated at this point, so an outline written before sign-off cannot drive the build.

Court rules read during drafting

A scaffold lists every required component of the filing in rule order, with the court's own certificate wording filled in where the court prescribes it. The governing rule lines for each component are captured and travel with that component into drafting, so each part is written against its own rule text.

Court rules read before final review

Before the final read, the components are swept against the court's rules and the rule text again. The engine keeps its own map of each court's requirements and also reads them from the rule text; the two are compared both ways, and when they disagree the rule is read and the difference is settled and recorded. A warning is never silenced. That is why the text is re-checked before final review.

Templates are useful until the rule changes, or the court differs, or the filing type needs a component the template never had. A template also cannot tell you which of its parts a given court requires. The engine builds each filing's outline from the rule text for that court and that filing type, at the time of the matter, so the outline reflects the rule text the engine read for that filing, and the receipts show which version was read.

Many filings cannot be filed alone. Depending on the court and the filing type, a filing may need an appendix, a certificate of service, a certificate of compliance, a particular cover form, or a step in another court. The engine computes the required companion documents from court data, not from memory, when the filing type is chosen. The glossary has companion filings defined.

Each court rule the engine relies on carries a receipt:

• the court and the rule;
• the version of the rule that was read;
• when it was retrieved.

Every rule book the engine loads carries its version and retrieval date, and each matter's rules receipt records what was retrieved and when. The rules are re-checked before drafting and before the final read, and anyone checking the matter can see exactly which text the filing was built against.

Before a filing packet is ready, several rule-driven checks run:

• Court-format lint. A court-format check and a barred-words check run on every document in the filing.
• No leftovers. A placeholder check confirms that no unfilled field, draft note or bracketed gap survives in the filing text.
• Components against rules. Every required component is swept against court data and rule text.
• Every exhibit present. The packet's structure is checked, and every exhibit the filing references must be in the packet.
• The clerk-rejection scan. A quick clerk-style scan checks caption, deadline, copies, fees and format, the common reasons clerks send filings back.

Illustration, fictional filing.

The clerk-rejection scan

1. 1Captionpassed
2. 2Deadlinepassed
3. 3Copiespassed
4. 4Feespassed
5. 5Formatpassed

Illustration, fictional matter. The court, its local rules and the matter are invented.

Filing: response to a motion to dismiss · Avery v. City of Example (fictional) · U.S. District Court for the District of Example (fictional)

RULES PACKET
court ........... District of Example (fictional)
books ........... Federal Rules of Civil Procedure; Local Rules (fictional); judge's standing order (fictional)
filing type ..... response to a motion
retrieved ....... 2026-10-06 14:32 UTC · class: full text

COMPANIONS (calculated)
- certificate of service
- certificate of compliance with the word limit, L.R. 7.1(e) (fictional)
- proposed order, L.R. 7.1(f) (fictional)

COMPONENTS (rule order)
caption · introduction · statement of facts · argument · conclusion · signature block · certificates

CROSS-CHECK
1 warning: requirements map says 25 pages; rule text says 7,000 words → rule read, word limit governs, map corrected, recorded

CLERK SCAN
caption ✓ · deadline ✓ (Tue 15 Dec 2026) · copies ✓ · fees: none due ✓ · format ✓

None of that is legal judgment about the merits. It is the part of the work where one missing page can cost days that some deadlines do not have.

The rule text that governs format also governs time. The docket side of the engine computes deadlines from the document's face and the rule text, and a second computation checks each one by default. See deadlines from the rule text.

Appellate rules are especially exacting about form, record citations, appendices and certificates. The same approach applies: the official text, fetched and receipted, checked at more than one point. See the page on appellate rules.

Some courts and individual judges now require a statement about the use of generative AI in filings, or limit its use. Where such an order applies, it governs the filing, and the attorney of record remains responsible for any statement it requires.

3,400 courts are matched to their official federal or state court rules, in 57 U.S. jurisdictions, as of 7 October 2026. Local court rules are not loaded yet. We give one dated total rather than a list. If a court's rule book is not loaded, the engine does not work from memory instead: the empty result is refused, and the matter does not proceed. Tell us your court when you email us.

• We do not claim a filing will be accepted. Clerks and courts decide that.
• We do not claim coverage of any particular court on this page.

When are the court's rules read? Before strategy, when the filing type is being chosen; again before drafting, after the strategy sign-off; and again before the final read. The rule lines for each component also travel with it through drafting.

How are companion filings worked out? From court data, when the filing type is chosen. They are computed, not remembered, so a required certificate or appendix is on the list from the start.

What does the clerk-rejection scan check? Caption, deadline, copies, fees and format: the common reasons clerks send filings back.

Are exhibits checked? Yes. The packet's structure is checked, and every exhibit the filing references must be in the packet.

Does the engine know every court's local rules? Not yet. Local court rules are not loaded yet. It uses only official rule books it has loaded, and it will not proceed on a court whose book is missing. 3,400 courts are matched to their official court rules, in 57 U.S. jurisdictions, as of 7 October 2026.

Does it check page and word limits? It checks the format requirements the court's rules set, including length, as part of the component and clerk checks, with the rule text as the authority when two sources disagree.

Email us with questions about the rules fetch, the scaffold and the clerk-rejection scan.

Start a request (opens the main site) Deadlines and the docket

Legal Ops Depot is not a law firm and does not give legal advice.