Some court rules encourage newer attorneys to argue. The wording can sit in a standing order, a courtroom procedure or a local rule. We counted where the database shows that kind of invitation. Here is the method.
The unit and the population
The unit is a judge row inside its court listing, identified by v2_judges.id. A person can appear in several court listings. A document can be inherited from a predecessor or reproduce court policy on a judge's page.
We include entries whose status is active, whose retired_at is null and whose slug and type are not court. A covered court listing has extracted rules on the latest active document version of an active source. We exclude the statewide California rulebook and the redirect stubs in the site's duplicate-court-stubs.json. An entry has its own rule-bearing document when a source belongs to its (district_id, judge_slug) and the source's latest active version has at least one stored extracted rule.
The federal search population is 574 active roster entries in 19 covered district listings. The state population is 4,591 active roster entries in 455 covered state listings. After the own-document filter, 516 federal entries and 1,741 state entries remain.
The fields we searched
The structured type is JuniorLawyerIncentive. It stores trigger.experience_years_max, an optional role, a description and optional benefits fields: oral_argument_likelihood_increased, pre_motion_conference_will_be_scheduled, multiple_attorneys_may_argue and other_benefit. A threshold or benefit flag alone is not enough. The review reads content.source_text, because structured summaries can overstate a benefit or assign a threshold absent from the quote. We make no experience-threshold headline.
Candidate queries take the union by rule ID of the dedicated logic type, the legacy structured_data.junior_lawyer_incentive=true flag, case-insensitive phrase matches and a case-insensitive proximity regex. Terms cover junior, newer, inexperienced and less-experienced lawyers, recent admission, early career, and experience or year wording near argument. Joins run from court to judge, sources to (district_id, judge_slug), versions to rule_source_id and extracted rules to document_version_id. The source view selects the newest active version of each active source. We restrict the index and candidate union to that version, even if another version is still marked active. No summary-only hit establishes a match. The exact terms and regex are in build.py and search-audit.json.
The review step
The analyst read each eligible candidate passage. A headline match needs operative wording that explicitly invites, encourages or creates courtroom speaking or participation opportunities for junior, newer or less-experienced attorneys. The wording can concern motion argument, conferences, witness examination or trial. An express requirement to plan meaningful courtroom opportunities also qualifies. An invitation addressed to senior counsel or a firm counts, even when the junior lawyer has no personal right to demand a hearing.
The procedural-benefit subset requires an express experience-linked provision for a hearing, an increased likelihood of argument or a conference, extra time, shared argument, senior-lawyer assistance, a choice of in-person argument or another relaxation of ordinary courtroom practice. Conditional and discretionary provisions count, with their conditions kept in the quote. Conditions and discretion apply, and the quote keeps them. We excluded general oral-argument procedures, ordinary permission for multiple lawyers without an experience link, supervision duties alone, experience qualifications for mediators and contact details for junior law clerks.
Each decision binds to the SHA-256 of its exact database source text. An unseen or changed eligible passage stops a build before replacing the CSV. A source-scope rejection is separate from its topic classification. That distinction lets a reviewer see what was excluded and why.
What the numbers mean
Documents linked to 149 of the 516 eligible federal entries and 37 of the 1,741 eligible state entries carry such wording. Within the 186 matching entries, 127 offer an express procedural benefit. The federal split is 110 of 149 and the state split is 17 of 37.
These are counts of found wording in extracted source text. They are lower bounds. A missing match leaves the question open for that entry. Extraction can drop text and OCR can misread it. Some documents are inherited orders or reproduced court policy. The counts describe database entries. The per-court counts are on the data page at https://www.courtrules.app/data/junior-lawyer-incentives?utm_source=devto&utm_medium=post&utm_campaign=brand
Top comments (1)
honestly, the most impressive part of this is how transparent you are about the limits. saying "these are lower bounds" and admitting that extraction can drop text or OCR can misread it is so rare in data projects. most people would just present the 149 number as gospel. also, the SHA-256 binding of each decision to the exact source text is a genius way to make the whole pipeline auditable.