Auditable, Clerk-Run Random Selection for Substitution of Montana District Judges (Geographically Limited Pool)
1. Introduction
This administrative proceeding concerns contemplated revisions to the statutory/rule framework governing
substitution of district judges in Montana, anchored in § 3-1-804, MCA. The record provided is a detailed
memorandum from the Office of the Court Administrator (OCA) responding to an information request from
Justice Bidegaray (email dated 2/24/2026). The OCA memorandum (dated 3/2/2026) describes how “random selection”
is understood under the legislation—“selection from a larger group by chance”—while also recognizing a geographic
constraint that the selection pool be limited “to a reasonable distance from the original judicial district.”
The practical problem driving the revisions is institutional: ensuring that reassignment after substitution is
genuinely random (and perceived as random), while remaining workable for clerks, judges, and court administration.
The memorandum also reflects a governance catalyst: the “Judicial Oversight legislative commission” review during
the 2024 interim, which perceived that the status quo did not guarantee randomness.
Because this is an “In re” rules/administrative matter rather than an adversarial dispute, there are no traditional
litigating parties in the provided text. The primary institutional actors are the Montana Supreme Court (as rulemaker),
the OCA (as implementing administrative office), district courts and clerks of court (as operational users), and the
Legislature (through the definition of “random selection” and constraints embedded in § 3-1-804, MCA).
2. Summary of the Opinion / Record
The provided “OpinionText” functions as an implementation-focused administrative record rather than a merits opinion:
it sets out assumptions, operational design, known data limitations, and proposed safeguards for a revised substitution
process.
-
Core policy direction described: implement a random selection mechanism from a “larger pool,” while limiting
the pool geographically to a “reasonable distance” from the original judicial district.
-
Operational change: development of an IT application enabling clerks of court to perform random judge selection
and record substitution events; the app captures “who selected the judge, when the judge was selected, and who was selected.”
-
Work-shift identified: the proposed rule “moves the requirement from the original district court judge or their staff
(original rule (6)) to the clerk’s office and the OCA (new rule (3)(b)).”
-
Data limitations candidly acknowledged: existing systems (FullCourt Enterprise case management and SABHRS fiscal)
were “not designed with this policy in mind,” leaving gaps in historical metrics—especially travel cost attribution.
-
Quantitative snapshot provided: substitution/judge-change counts for cases opened from Jan. 1, 2020 through Feb. 26, 2026,
including within-district vs different-district counts.
3. Analysis
3.1. Precedents Cited
The text does not cite judicial precedents (case law). Instead, it relies on statutory/rule references and
institutional sources:
-
§ 3-1-804, MCA — Treated as the codified baseline governing substitution and reassignment mechanics. The memorandum
expressly interprets “random selection” language “in conjunction with the existing rules codified at § 3-1-804, MCA.”
This indicates continuity: the revision is framed as an evolution of the existing statutory scheme rather than a break
requiring common-law justification.
-
Legislative definition of “random selection” — “selection from a larger group by chance.” The memorandum treats this
as the controlling conceptual constraint, while emphasizing that the pool must be “limited geographically to a reasonable distance.”
-
Judicial Oversight legislative commission (2024 interim) — Not a legal precedent, but an institutional impetus. The OCA
explains that the policy was “promoted as a response” to that commission’s review and its perception that the “status quo did not
guarantee randomness.”
In effect, the “precedent” function in this record is performed by statute (and existing internal rules referenced as “original rule (6)”
and “new rule (3)(b)”), rather than by prior judicial decisions.
3.2. Legal Reasoning
Although presented as an administrative implementation memo, the record reveals a coherent legal-policy rationale consistent with
rulemaking in court administration:
-
Randomness as both a legal requirement and legitimacy safeguard.
The memorandum treats “random selection” as a mandated attribute (“by chance”) and also as a legitimacy tool—responding to concerns that
existing practice could be perceived as non-random. This aligns with the broader due-process value that adjudicators should be assigned in a
manner that is neutral and not manipulable.
-
Geographic limitation as a constraint on the “larger pool.”
The record accepts that random selection cannot be unbounded statewide if the governing framework requires limiting the pool to a “reasonable distance”
from the originating district. The legal reasoning is administrative proportionality: randomness is pursued, but not at the expense of workable geography.
-
Auditability and traceability as functional guarantees.
The proposed application’s capture of “who/when/whom” is a concrete integrity mechanism. Rather than relying solely on professional norms,
it creates an auditable data trail—an administrative substitute for what, in other contexts, might be litigated as a transparency/due-process issue.
-
Separation of duties: shifting selection from judge/staff to clerk/OCA.
The memo highlights that the proposed structure relocates the selection responsibility from chambers (original rule (6)) to the clerk/OCA (new rule (3)(b)).
The implicit reasoning is to reduce perceived conflicts and increase standardization, because clerk-driven selection through a defined tool can be more uniform
than judge/staff-driven ad hoc practices.
-
Feasibility and administrative burden as limiting principles.
The memo repeatedly underscores that historical fiscal and travel metrics cannot be reliably extracted without significant manual work (reviewing “900 to 1000 travel vouchers”
plus mileage logs) and even then “not with 100% accuracy.” This supports a pragmatic rulemaking posture: adopt a forward-looking system that can track what the old systems did not.
3.3. Empirical Signals in the Record (2020–Feb. 26, 2026 cases)
The attached tables provide a partial but informative baseline for substitution and judge-change activity (with explicit limitations:
they cover only cases opened since Jan. 1, 2020, and non-substitution change-type labels may vary by county).
| Metric (cases opened 1/1/2020–2/26/2026) |
Count |
What it suggests for the revised rule |
| All judge changes (Table 2) — Grand Total |
7,938 |
Judge reassignment events are frequent; a standardized, auditable workflow has system-wide significance beyond substitutions alone. |
| All judge changes: Different District vs Same District (Table 2) |
1,286 vs 6,652 |
Most reassignment stays within-district, but a meaningful share crosses districts—raising travel/logistics and pool-definition questions. |
| Substitutions (Table 3) — Grand Total |
2,662 |
Substitutions constitute a large subset of judge changes, making substitution-specific safeguards (randomness, audit logs) high impact. |
| Substitutions: Different District vs Same District (Table 3) |
487 vs 2,175 |
Cross-district substitution is substantial; any “reasonable distance” pool rule will materially affect operational patterns and potential costs. |
The district-by-district distribution also signals that substitution burdens are uneven, which can matter for how a geographically limited pool is drawn.
For example, Table 3 reports District 13 with 387 substitutions, all recorded as “Different District,” while several other districts show the inverse
(predominantly “Same District”). The memo itself cautions that certain within-district counts may occur even in single-judge districts due to judge turnover
and subsequent reassignment.
3.4. Impact
-
Standardization and defensibility of randomness. A clerk-operated tool with a recorded selection trail makes the process easier to explain,
review, and defend against claims of manipulation—particularly important given the 2024 oversight concerns referenced in the memo.
-
Administrative transparency through logs (but not necessarily public transparency). The memo describes an auditable record internally
(“who/when/whom”), but does not specify whether or how litigants/public can view the selection process or logs. Future implementation details may determine
whether transparency is merely retrospective (audit) or also participatory/observable.
-
Travel-cost uncertainty and future measurement. The record explicitly concedes the inability to link SABHRS travel reimbursements to substitution travel.
The likely impact is a shift toward prospective coding/reporting if cost containment becomes a policy objective.
-
Workload migration to clerks/OCA. The memo anticipates minimal time to “select a new random judge” (less than 5 minutes) and modest annual support
(“less than 40 hours per year”), but it also acknowledges a structural shift: the clerks and OCA take on a duty previously situated with judges/staff.
-
Pool-design litigation risk (future-facing). Because the rule concept pairs a “larger pool” with “reasonable distance,” disputes may arise over what
“reasonable distance” means in practice—especially in sparsely populated regions where the nearest available judges may still be far away.
4. Complex Concepts Simplified
-
Substitution of judge: A procedural mechanism by which a case is reassigned from the originally assigned judge to another judge. The memo treats “substitution”
as a distinct, comparatively uniform category in clerk-entered data.
-
Recusal / disqualification: Reasons a judge does not hear a case (e.g., conflict). The memo references multiple judge-change types but warns that labels other than
“substitution” may vary by county practice.
-
Random selection: Defined here as “selection from a larger group by chance.” The key administrative challenge is ensuring that the randomness is real and verifiable.
-
Geographically limited pool (“reasonable distance”): Randomness applies within a constrained set of eligible judges; the constraint is meant to keep substitutions workable
given Montana’s geography and travel burdens.
-
Audit trail: A record showing who performed a selection, when it occurred, and which judge was selected—useful for oversight and dispute resolution even if not public-facing.
-
System constraints (FCE, SABHRS): FullCourt Enterprise (case management) and SABHRS (fiscal accounting) were not built to tag travel costs as “substitution-related,” limiting
retrospective fiscal analysis unless manual review is done.
5. Conclusion
The record in IN RE REVISED RULES ON SUBSTITUTION OF DISTRICT JUDGES reflects an administrative-law style modernization of judicial assignment mechanics under
§ 3-1-804, MCA: implementing random selection “by chance” from a larger pool while imposing a geographic “reasonable distance” constraint,
and operationalizing those requirements through a clerk-run software tool that produces an auditable selection log.
The most significant doctrinal/administrative takeaway is the move from informal or locally varied substitution practices toward a centralized, standardized, traceable method—aimed at
strengthening both the reality and appearance of neutral assignment. The memo simultaneously highlights the principal open issues for future refinement: defining and administering the geographic
pool, making transparency choices explicit, and building prospective fiscal coding so the judiciary can measure travel and administrative costs that existing systems cannot reliably capture.