A page limit decides how much argument fits in a brief. The number can change by judge, by motion and by court. We counted the limits we could read in the source text. Here is how we did it.
The unit and the population
The unit is a judge-court entry. It is the database judge row within its court listing, identified by judge_id. The associated documents can include an inherited predecessor's order, a court policy reproduced on a judge's page or a proposed scheduling-order template. The count shows found wording associated with an entry. Personal authorship or adoption by the named judge stays unverified.
The active roster holds 574 entries across 19 covered federal district listings. Of those, 516 entries have their own rule-bearing documents. We read production on October 22, 2026, in America/Los_Angeles. The reads are separate HTTP GETs, each translating to SELECT. No database write, RPC or DDL ran. We excluded the synthetic court owner and entries typed as court. A covered court listing has an active source whose newest active document version has at least one extracted rule. An own-document entry has a rule-bearing source associated with its own (district_id, judge_slug). We excluded the statewide California rulebook and the merged Texas court redirect stubs. State page-limit rules were outside this federal-district search scope. A state count of zero means outside scope, not absence of a rule.
The fields we searched
The extraction type is content.structured_data.logic_type = PageWordLimitRule. Relevant optional fields include document_type, trigger.document_types, trigger.motion_types, role_limits[].role, role_limits[].limit_type, role_limits[].limit_value, format and document conditions, exclusions, line spacing, font requirements and margins. Top-level content.case_type_applicability and document-version case_types help identify restricted contexts. Missing structured scope is not a default or a negative finding.
The candidate union starts from the structured logic type. A separate SELECT then unions rows whose content.source_text matches pages?|words?, joined by rule ID. The joins run from court to judge, source ownership by (district_id, judge_slug), document version to source ID and rule to document version ID. We restrict the search to the newest active version of each active source. The exact SELECTs are in build.py and search-audit.json.
The review step
We did not accept a structured value without reading the quotation and context. A quotation can mention several limits, refer to a different filing or conflict with the extracted value. The headline match is a federal active judge-court entry with at least one unambiguous numeric page ceiling for the initial supporting brief or memorandum for an ordinary civil motion to dismiss or a motion for summary judgment. A generic civil motion-brief ceiling can apply to both targets. An explicit motion-specific ceiling takes priority over a generic ceiling. We compare each motion separately within its court listing.
Word limits and page alternatives limited to handwriting, typewriting or unrepresented parties are out. The screen kept word limits separate from page limits. Replies, sur-replies, opposition-only limits, pre-motion letters, discovery submissions, trial briefs, proposed findings, factual statements, exhibits, courtesy-copy thresholds and tables-of-contents triggers are out. Combined cross-motion briefs, collective budgets across several motions and combined motion-plus-memorandum totals are out. Criminal, bankruptcy, social-security, prisoner and other special-case-only provisions are out. Patent-only and case-specific docket orders are out. General templates associated with an entry can qualify. Conditional fallback limits that parties may replace by agreement are out, along with passages without a numeric ceiling, incomplete passages whose scope cannot be established and internally contradictory numbers.
Human decisions, including scope and exceptions, are saved in internal/reviews.json and guarded by a SHA-256 digest of the complete candidate record. An unseen or changed record stops a build before replacing the CSV.
What the numbers mean
We found an eligible opening-brief page ceiling in 122 of the 516 federal entries with their own documents. Among the 10 districts with measurements for the same target motion in at least two entries, 6 have different ceilings across entries. Eleven of the 19 covered districts have any eligible measurement. In the Eastern District of Pennsylvania, 14 district and senior judge entries are measured out of 28 own-document entries. Summary-judgment briefs range from John M. Gallagher's 20 pages to Anita B. Brody's 35 pages. Motion-to-dismiss briefs have the same endpoints among 13 measured district-judge entries.
Pages state a filing constraint. Typography, front matter, exhibits and application conditions differ. The counts are database entries from extracted text and lower bounds. A missing match leaves the question open for that entry. The per-court counts are on the data page at https://www.courtrules.app/data/page-limits?utm_source=devto&utm_medium=post&utm_campaign=brand
